View Single Post
  #4  
Old 05-30-2014, 11:54 AM
whitt26 whitt26 is offline
Member
 
Join Date: May 2014
Posts: 3
whitt26 has 10 reputation points
Default similar issue

So I was having a similar issue will a few of my ERS 4500 series switches. On some of them I noticed the stacking cables went bad. I found this out by logging into the base switch and typing:
"show stack health"

It should show you if the stacking cables can see another device. Try replacing them with known good ones.

Another issue I have found is the auto-save feature is basically garbage. Sometimes it would fail/be corrupt and upon a restart it wouldn't load properly. Since then I have disabled this feature and ensured I saved the configuration manually. Haven't see this specific problem since.

Also, check to see if your stack recognizes that there are the right amount of switches. Type:
#"show stack-monitor"
ensure to change this with:
(config)# stack-monitor stack-size [number of switches]

If you have a syslog server, look for a "bsnStackConfiguationError" trap. I got my server throwing alarms every time it sees this message and it happens more than I expected. It means a switch in the stack didn't boot up properly, normally because the stack master booted up a little slower than the rest.

I am not an Avaya professional, but I hope this can give you some direction to head towards.
Reply With Quote