Re: Two Network cards for redundancy

Guy,

That's a slam dunk to do.  It's not, however, a slam dunk to find the IBM 
documentation on it.  :)

It is called *VIRTUALIP and I'll include an example.

The IP address you give out to people is the 192.168.234.030.
The physical ethernet cards are .010 and .020 and are already setup and 
working fine.

GO CFGTCP, 1

Internet         Subnet              Line      Line
Address          Mask             Description  Type

192.168.234.030  255.255.255.255  *VIRTUALIP   *NONE
192.168.234.010  255.255.255.0    ETHLINE      *ELAN
192.168.234.020  255.255.255.0    ETHLINE2     *ELAN
127.0.0.1        255.0.0.0        *LOOPBACK    *NONE

The key when adding the .030 is the type and the seemingly incorrect subnet 
mask.

The part I cannot find, is where/how you associate the .010 and .020 with 
the .030.  I thought I recalled having to do something out in Operations 
Navigator instead of the green screen.  But then again, maybe when you start 
the virtual interface, it is smart enough to figure it out.  I can't try it, 
since my *VIRTUALIP is already in use. :)

The good news, is that because no one knows about your virtual ip yet, you 
can do what you want with it (starting, stopping, deleted, recreating), just 
leave .010 and .020 alone.  When I have done this in the past, I get the 
virtual IP working first, then worry about making people use it.

Last caveat is trading data with an interface engine server.  When TCP/IP 
traffic comes into the 400, it uses .030.  But when the 400 sends stuff out, 
it randomly selects .010 or .020.  .030 cannot actually send anything.  So, 
when thinking about who/what needs to be informed about the address change, 
let the interface group and firewall group know about all 3 addresses.

Good Luck,
Brian.
=====
Brian Dolinar | ACS Healthcare Solutions

"Guy Terry" <guy.terry@xxxxxxxxxxxxxxxxxxx> 
wrote in message news:44E41E8D.8030409@xxxxxxxxxxxxxxxxxxxxxx

Hi all,

The 520 we've got came with two ethernet cards, and as I understand they
were configured so that they both worked with the same IP address. This
to introduce redundancy in case one failed (and perhaps to spread the
load?). Then, when we restored our old system onto the 520, the network
config got broken and I just set it up with one network card.

I'm going to have a go tomorrow at setting up the dual-card option
tomorrow, but I can't work out how. I guess that you give each ethernet
line it's own TCP/IP interface with a unique IP address, but I can't
find where to specify the third IP address - the IP address you want
both cards to 'pretend' to be. Can anyone help?

Also, we have some fairly fancy HP switches - do I need to configure
them so that they know about this special setup?

Cheers

Guy