I realize you that you do not want to use EtherChannel, my question is why not?
Asking for another couple of adapters and an extra couple of switch ports
should not be a big deal these days.
EtherChannel on AIX will do exactly want you want with single IP address and
the TSM clients will not know that they are talking to the backup interface and
without the networking folks having to set up any thing on their end (i.e.
EtherChannel or what they also call bonding).
On AIX there are two ways to set up EtherChannel: EtherChannel or Link
Aggregation. You want EtherChannel. If you use Link Aggregation then you will
have to have the network folks bond the interfaces on their end on the same
switch - so you introduce a single point of failure - and sometimes there is
push back from them mostly because they are uncomfortable with it. When you,
on AIX, set up EtherChannel put one interface in the EtherChannel/Link
Aggregation Adapters field and the other adapter in the Backup Adapter field.
This will allow you to fail seamlessly with no impact to your clients. Do the
same for the other interface. This means that in your environment you will
need a total of 4-ethernet connections.
Once again, I realize you do not want EtherChannel, however I think are you are
just making yourself work too hard trying to figure out something that you
should just let the OS take care of.
Just my two cents worth.
Mahesh
>>> Andy Huebner <Andy.Huebner AT ALCONLABS DOT COM> 6/27/2007 9:37 AM >>>
I would use round robin DNS, put both addresses in DNS and let the luck
of the draw spread the load.
One problem you may have is you can only have one default gateway. All
traffic outbound for a different network, as defined by your subnet
mask, will use only on NIC. Should that NIC fail you may have to
restart something, NIC or OS, to move the default gateway.
Without Etherchannel or something similar, I do believe a human will be
needed if the primary NIC drops off the network. Do you trust all of
the humans there at 2am, which is the only time NICs are designed to
fail?
Andy Huebner
P.S. The preceding is based on using two NICs on Windows systems.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Rhodes
Sent: Wednesday, June 27, 2007 7:11 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Dual interface TSM server
I'm no expert in networking, but I do know that you have to be careful
with multiple
interfaces in that that they may not work as you expect.
For example . . . are the client nodes on the same network as the TSM
server? By
"network", I mean the network part of the ip address. If they are not
(ie:
their
traffic gets to TSM via a router), then you can get inbound traffic to
the
TSM server
arriving on one nic and outbound traffic from the TSM server on the nic
assigned
to the default route.
Rick
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 06/26/2007
06:14:32 PM:
> AFAIK yes ... just point your TCPSERVERADDRESS to working IP address,
> it should work /me thinks ...
>
> On 6/26/07, Daad Ali <daad_l AT yahoo DOT ca> wrote:
> > Hi ALL,
> >
> > I have a server that has two interfaces configured (Two IP
addresses
as well).
> >
> > Without using EtherChannel or any redunancy like that, is there a
way
to tell the client to use the 2nd interface incase the first one fails.
> >
-----------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.
This e-mail (including any attachments) is confidential and may be legally
privileged. If you are not an intended recipient or an authorized
representative of an intended recipient, you are prohibited from using, copying
or distributing the information in this e-mail or its attachments. If you have
received this e-mail in error, please notify the sender immediately by return
e-mail and delete all copies of this message and any attachments.
Thank you.
|
