secondary connection lost when primary fails

[T-Mobile Tech Support]

I have an rp8400 running 11.23.
I had a primary ip on an add-on card at 100mb.
The secondary was using one of the built in GB connection. I wanted to move the primary to the other GB connection. When I changed the physical connection of the primary to the gig card, the secondary connection was lost. I replaced the cable to the original card and all was well. Next I went into sam and disabled the primary connection and again the secondary was lost. I enabled the gig card and both primary and secondary came up.
What's up with that?

[Steven E. Protter]

Shalom T-Mobile,

Former customer here.

lanadmin -x 0 (replace zero with actual lan number)

Before you do the switch.

Cable switching on a 100 BaseT lan card involves a connection that should be set manual.

GB cards speed and duplex speed must be set to autonegotiate.

So the problem here is your switch methodology.

Another thing to be careful of is you should never have two NIC cards in HP-UX on the same network at the same time. This will cause a complete network failure on older releases of HP-UX.

SEP

[T-Mobile Tech Support]

My question is why is secondary connection going out when the primary fails?

[Steve Lewis]

I think you need to post your routing table and ifconfig of both interfaces for us to help you more.

[T-Mobile Tech Support]

Here is my routing table.[root@tstqat03:/root]# netstat -rn
Routing tables
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 lo0 4136
192.168.190.21 192.168.190.21 UH 0 lan3 4136
10.73.21.58 10.73.21.58 UH 0 lan2 4136
10.73.20.58 10.73.20.58 UH 0 lan0 4136
10.73.20.0 10.73.20.58 U 2 lan0 1500
192.168.190.0 192.168.190.21 U 2 lan3 1500
10.73.21.0 10.73.21.58 U 2 lan2 1500
127.0.0.0 127.0.0.1 U 0 lo0 0
default 10.73.21.1 UG 0 lan2 0

And here is the ifconfig for the 4 devices:

[root@tstqat03:/root]# ifconfig lan0
lan0: flags=1843
inet 10.73.20.58 netmask ffffff00 broadcast 10.73.20.255
[root@tstqat03:/root]# ifconfig lan2
lan2: flags=1843
inet 10.73.21.58 netmask ffffff00 broadcast 10.73.21.255
[root@tstqat03:/root]# ifconfig lan1
lan1: flags=842
inet 10.73.21.58 netmask ffffff00 broadcast 10.73.21.255
[root@tstqat03:/root]# ifconfig lan3
lan3: flags=843
inet 192.168.190.21 netmask ffffff00 broadcast 192.168.190.255


lan 0 and 2 are the GB interfaces. lan 1 is the old 100mb interface which is currently disabled via sam.
When I disabled lan1 and lost connectivity I had not configured lan2.

[Florian Heigl (new acc)]

For clarification - are You using APA (port aggregation) or is this two separate interfaces?

From my experience, SAM will cause such hickups when multiple lan interfaces are in a system. I think this is dependant on the order in which one issues the configure/deconfigure up/down actions on the interfaces.

As I usually fail at working methodically I stopped using SAM for lan configuration on hosts with more than one interface.