VIP not re-established upon reboot

[Joe Davidson]

We've established a VIP interface, and it works fine when establishing it manually via the ifconfig command, but it does not re-establish following a reboot.

We're using APA to configure our primary interface, and I believe the netconf file is set up properly; the APA interface plumbs up fine, but the VIP does not. Following reboot, a manual plumbing of the VIP interface works fine, so I can't understand why it does not during the network configs at boot time. Is there a place where I can see logs of any errors that occurred during the startup?

Here is the excerpt from the netconf file; any help would be greatly appreciated....

IP_ADDRESS[0]="150.234.133.17"
SUBNET_MASK[0]="255.255.255.0"
INTERFACE_NAME[0]="lan0"
BROADCAST_ADDRESS[0]=150.234.133.255
INTERFACE_STATE[0]=up

# VIP's Added 5-27-2005 for Remedy arsdev.sbcdo.sbc.com
INTERFACE_NAME[7]=lan900:1
IP_ADDRESS[7]=150.234.133.90
SUBNET_MASK[7]=255.255.255.0
BROADCAST_ADDRESS[7]=""
INTERFACE_STATE[7]=up
DHCP_ENABLE[7]=0

Thanks in advance

[Jeff_Traigle]

Only place I know to look for errors at startup is /etc/rc.log. It can possibly point to the other locations to look, but that's the starting point.

As for the VIP setup in netconf... shouldn't INTERFACE_NAME[7] be set to lan0:1 instead of lan900:1? If these are the only two entries, you don't have a lan900 defined for the VIP to attach to. You didn't give the command line you're using to set it up manually so tough to say if that's it or not, but it's what looked off to me offhand.

[Joe Davidson]

Thanks; I'll look in the log.

As for the lan0 vs. lan900 naming, I thought of that, ans checked another server where VIP IS working using APA. It is set up the same way.

Also, you're right; I should have posted the command to start the VIP; it is:

ifconfig lan900:1 150.234.133.90 netmask 255.255.255.0 up

...so it IS taking the APA name.

I believe in the netconf, the lan0 is specified in the event that if the server comes up with only 1 interface, it will still work, whereas if we specify the APA interface name (lan900) and there's a problem, then no interface will start. Is this correct?

Thanks again for taking the time....

[Alzhy]

Jose,

The problem lies in the fact that the VIP routine is executed way before the APA aggregate is in existence.

It works on another server because the config on that server is not APA Failover Mode and it is possible the Aggregate (lan90x) is already active when the VIP routine is called.

A "workaround" is to have an rc script to specifically plumb this VIP up right before the subsystem that needs it.

Glad you're in the forums sir.

Gracias!