CM6 Duplicated Servers: Standby Server Won't Initialize after Rebooting It

[CChambleeJr]

After rebooting my STANDBY server using its System Platform "Reboot/Shutdown" menu item, the server will not initialize. I can't ping its CDOM address, and the System Platform page will not load on my browser. If I go to the active server's CM page and do a Status Summary, I see the active server in good health, and the other server is shown in standby mode, but its Processor Ethernet link shows as DOWN and it is in major and minor alarm. I have tried to manually power-off then back on, but same results. VGA monitor plugged into server shows the Linux login prompt for the server, but I cannot ping the system platform (CDOM) IP address. Why will this server not reinitialize after reboot?

 

[SoundsLikeTheNetwork]

What state does the standby U-DOM/CDOM say it is in.

login to standby
su - (switch to root user)
run "xm list"
paste results

 

[CChambleeJr]

Name=Domain-0 | ID=0 | Mem=512 | VCPUs=4 | State=r----- | Time=4912.0
Name=cm | ID=1 | Mem=3504 | VCPUs=3 | State=-b---- | Time=1265.1
Name=udom | ID=2 | Mem=1024 | VCPUs=1 | State=-b---- | Time=674.0

Another bit of info... "ifconfig eth0" reports no ip address configured. "ethtool eth0" shows that the port speed is unknown, as if the ethernet cable was unplugged, yet the port indicator LEDs show activity (green). Same with eth2.

 

[SoundsLikeTheNetwork]

if ifconfig is ran from DOM-0 the ip address would show up under "avpublic"

try to access the standby UDOM/CDOM and run an ifconfig from there make sure the address is correct.

su -
"xm console udom"
su -
ifconfig

 

[CChambleeJr]

Yes, I see the IP address for DOM0 using the "ipconfig avpublic" command, and it is correct. I can also now see that "ifconfig eth0" displays my correct IP address for CDOM for that server. However, I cannot get the Avaya System Platform webpage when I navigate to that IP address, and the active server's "Status Summary" shows the standby server's Processor Ethernet as "down". It almost seems that some services are not running on the standby server.

 

[montyzummer]

If you log into the standby server cdom via putty and type server status , what do you see ??? , then if you can get in at this level reboot it from cli.

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[CChambleeJr]

From console root, the command "server status" cannot be found.

 

[montyzummer]

i have never done from root level just direct into cdom

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[SoundsLikeTheNetwork]

you have to run the "server" cmd from CM not CDOM

use "xm console cm"

then run the cmd "server" and paste results

 

[redphone]

What type of server do you have? Is it an S8800 server?

You may have a bad RAID controller battery.
You can check the battery condition by running the following command on the DOM0 through CLI using root
privileges:
# /opt/MegaRAID/MegaCli/MegaCli64 -AdpBbuCmd |more

MegaCli64 could also be MegaCli32 or MegaCli.

More info here.

 

[CChambleeJr]

Thanks all, Avaya diagnosed the issue as a "bond0" issue caused when the servers were STIG'd with an improper method of disabling ipv6. Problem resolved.