Re: Two Network cards for redundancy -- MIDRANGE-L

Guy,

The third IP address must be configured in iNav and is created as a*VIRTUAL IP. You assign that address with a mask of 255.255.255.255.Then on the advanced tab you MUST check the Proxy Arp box and forperformance you must assign the frame size to be the smaller of the twolines (in case one is 10/100 at 1492 and the other GbE at 8996 you mustuse the 1492).

Once that is done you can start the interface and it will respond toPINGs etc.

Then you will want to add Schowler routes to your network for eachphysical IP. The route specifies the destination as the network


example: for network 192.168.1.0 with physical address 192.168.1.10 do:

ADDTCPRTE RTEDEST('192.168.1.0')SUBNETMASK('255.255.255.0')NEXTHOP('192.168.1.10')BINDIFC('192.168.1.10')DUPRTEPTY(7)

Repeat for the other physical.

NOTE: If one interface is GbE and the other is 10/100 you'll want alarger DUPRTEPTY for the GbE interface. Otherwise you'll want them tomatch. In NO CASE do you want to use priority of 5.


 - Larry

Guy Terry wrote:

Hi all,
The 520 we've got came with two ethernet cards, and as I understand theywere configured so that they both worked with the same IP address. Thisto introduce redundancy in case one failed (and perhaps to spread theload?). Then, when we restored our old system onto the 520, the networkconfig 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 optiontomorrow, but I can't work out how. I guess that you give each ethernetline it's own TCP/IP interface with a unique IP address, but I can'tfind where to specify the third IP address - the IP address you wantboth cards to 'pretend' to be. Can anyone help?
Also, we have some fairly fancy HP switches - do I need to configurethem so that they know about this special setup?
Cheers

Guy