Multiple NIC's configuration HP-UX 11i v1

[Jared Rudy]

I have a RP7410 with HP-UX 11iv1 installed. We have 4 network interfaces. Two need to be on a 97.0.0.0 address range and two on a 192.168.0.0 address range. I understand that HP-UX is unable to handle more then one network interface configured with the same subnet without purchasing a piece of software.

I'm not a network guy so my question is how do I go about doing this and do I need to add special routes to the routing table to accomplish it?

Here's what we need or had before we found out it didn't work:

NIC1: 97.0.0.51 255.255.255.252.0
NIC2: 192.168.0.51 255.255.255.0
NIC3: 97.0.0.52 255.255.252.0
NIC4: 192.168.0.52 255.255.255.0

[Jeeshan]

obviously you need to change in routing table.

not only in OS but you need to ensure that, your network engineer also done their part to route in different subnet's.

[Torsten.]

This is what you need:

http://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=J4240AA

[T G Manikandan]

you need to use HP Auto Port Aggregation for this configuration.

[T G Manikandan]

http://docs.hp.com/en/J4240-90039/index.html

[rick jones]

You don't _have_ to buy Auto Port Aggregation, but it is considered the better solution.

If you configure multiple, physical (from the standpoint of the transport) interfaces into the same IP subnet, traffic will be accepted on both interfaces, but will only be sent-out one of them. The stack assumes that each interface configured in the same IP subnet has equal connectivity to whatever is beyond them.

You can change this by adding specific, static routes to your routing table and/or setting ip_strong_es_model in ndd to cause source IP address to be part of route lookup. Unless you have a late enough patch set to have an acceptable value of 2, setting ip_strong_es_model to 1 means that traffic will only be accepted on the interface with the matching IP address configured - eg traffic destined for 97.0.0.51 would not be accepted on the interface with 97.0.0.52 configured.

APA is IMO the better/cleaner way to go - it will wrap both NICs into one pseudo-NIC to be used by the transport and can hide a link failure from the apps and such. Otherwise, that sort of thing has to be done "by hand" with scripts and whatnot.

[Jared Rudy]

Thank you for the wonderful explanation. I convinced the boss to go ahead and purchase the software as I agree it sounded like the best solution. Thanks guys.