Management Vlan lost connectivity in Avaya 4548GT stack

[stone32]

Hello,

I have a stack of (3) 4548GT-PWR switches that I have all of a sudden lost management access to. I can not ping the switch not can I telnet, HTTP and SNMP but I am able to connect via console. The switches are still passing traffic so it looks like its just the management vlan thats having an issue.

From my layer 3 core stack (5520-48T-PWR) I see the IP of the switch in question when I do a "sh autotopology nmm-table" but I cant ping or access it via telnet from the core switch.

This is the second set of switches this has happened to in the past 30 days. If I reboot the stack it works for about a week and happens again.

We are using FW:5.1.0.8 and SW:5.4.008

Any help resolving this world be much appreciated.

Thanks,

Stone

[sidneyd]

Some suggestions:
- Check the IP status, show ip address to see that management is in use.
- You can also issue a ping command & traceroute from the switch to aid in your diagnosis. For example if there is some device local to the switch in the management VLAN is that reachable, vs a device which is remote.
- You should also check that your access to the Management VLAN is not being blocked by Spanning Tree for example.

BTW the latest software available for ERS 4000 is
Firmware 5.3.0.3
Agent code 5.6.2

[stone32]

thanks sydneyd.
When I connect via console all of the devices plugged into the stack lose connectivity. I am also unable to ping or traceroute to any devices from the affected switch. At that point I have to reboot the stack to get everything to work again. Then I am able to regain access to the management VLAN via telnet and web. I will upgrade the to the latest software to see if that resolves the problem.

Stone

[abaxen]

Hi, I'm getting the same issue with a 3524GT-PwR. Were running FW 1006 and SW 501006.

Heppening every few weeks or so.

Did you find the cause for this?

[sidneyd]

Suggest that you work with customer support to troubleshoot the problem

[stone32]

Still having the same problem even after upgrading to the latest firmware. I'm going to call support to see if they can assist.

[abaxen]

Originally Posted by stone32

Still having the same problem even after upgrading to the latest firmware. I'm going to call support to see if they can assist.

Did you get anywhere with this?

[vdyke]

I am using the secure version of the code but this version fixes the problem. The management address is actually applied at the underlying operating system (vxWorks) and not the avaya overlay. An Avaya Engineer & I worked at a site to determine the cause and then it took a few months to be fixed. The non-secure version is 4000_563013.img I believe.

Victor