The ACE Module crashed unexpected with a NP Control Store Parity Error which can be due to hardware. CSCsz65679
Bug Details ACE Crash due to NP Control Store Parity Error (place holder) Symptom:
The ACE Module crashed unexpected with a NP Control Store Parity Error which can be due to hardware.
None. Monitor the ACE Module and if this reoccurs a RMA should be considered (try to explain this to my customer will not be fun ;-(
In regard to your question about SVCLC:
Currently the SVCLC command on 6509 advertises the following VLAN: vlan 100-150,200-600
Customer VLAN is 84.
I was going to advertise the new VLAN 84, so it would have been like this:
svclc vlan-group 1 100-150,200-600
svclc vlan-group 1 84,100-150,200-600
When our implementation team applied the command, they were instructed to apply the ACE-admin configs which included the new VLAN 84, and Serverfarm VLAN, 484. After that they were going to apply the configs for the actual ACE that will do all the SLB services. This included the new VLAN's and the BVI info.
The Ops team indicated they could not ssh, telnet, or local session (session slot # proc 0). I requested to check the status of ACE module via
show mod in 6509, and they indicated they noticed unknown was the status.
Anyway, I don't want to make you fall a sleep with my boring explanation. The FT network kept the services running. I guess in the end we were able to truly test the failover/HA. ;-)