Auto Port Aggregation interfaces unavailable

[Karen Birkelbach]

I have installed APA package J4240AA (B.11.31.20) on a server that was upgraded from 11.23 to 11.31 recently. I set up three APA interfaces, each with three NICs. The IP addresses for the trunks are the same as the original single-NIC IP assignments. I diabled and took down the original NICs (lan0, lan1, and lan2), but when I tried to add them into the new trunks, the system refused to add them saying they were already in use. And periodically, the APA links go down and I am unable to access the server through the interfaces. The only way to recover the APA links is to down the lan interface and bring it back up (ifconfig lan901 down ; ifcnofig lan901 up). I'm not seeing anything in syslog.log. Where can I find out what may be causing this problem and solve it?

[rick jones]

When you say you brought down lan 0, lan1 and lan2 is that just an "ifconfig down" or did you also do an ifconfig unplumb to force the IP and ARP SAPs to be unbound from the interfaces.

When you say "unable to access the server through the (apa) interfaces" is that pinging the IPs from a system on the same IP subnet(s) or is that from a remote IP subnet - in the upgrade to 11.31 what became of the setting ip ip_ire_gw_probe?

[Karen Birkelbach]

I unplumbed each of the interfaces.

# ifconfig lan0
ifconfig: no such interface

As for being unable to access the interfaces, I am unable to ping from the same subnet from outside of the server or to the same subnet from inside the server.

The ip_ire_gw_probe is set to 1, enabled. Would disabling it keep the interfaces alive since we only have one gateway on the server?

[Jim Keeble]

If you are able to ping the gateway address, the GW probe shouldn't be the problem. But, some routers don't answer the "probe" (really a ping, or ICMP echo request). If not able to ping the gateway, disable the probeby setting the param to 0.