ERS 3500 lost vlan management
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
11-20-2018 01:16 PM
ERS3500 running release 5.3.9 secure (ERS3500_539011s.img) lost the IP address configured in vlan mgmt, the symptom is that the IP address left to be "in use" (it isn´t deleted from the config).
Reboots the device and works again, but a few minutes after the issue reproduce.
Has anyone a similar problem?
Regards,
EF
Reboots the device and works again, but a few minutes after the issue reproduce.
Has anyone a similar problem?
Regards,
EF
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
11-22-2018 01:00 PM
I found the problem, duplicated IP in mgmt VLAN.
Regards,
EF
Regards,
EF
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
11-20-2018 01:52 PM
I would recommend you to create a case with GTAC as 5.3.9 is the latest software available. I have checked some 3500 we are running and they are still on 5.2 version. Uptime over one year and no troubles with mgmt connectivity.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
11-20-2018 01:42 PM
I tried the same, deleting and reconfigring the IP again, but it didn´t work. I´m thinking to enable the ip routing because it´s a very big problem to lose the management of it.
Regards,
EF
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
11-20-2018 01:28 PM
Not with 3500, but I have seen this issue on different series. I have never tried to solve it by rebooting the switch. Just simply configured the IP address again and it went to "in use" again.
What I have seen on 3500 was that switch stopped responding from networks reachable via default gw. Only way to fix this was reboot. But I do not remember what sw version the switch was running.
What I have seen on 3500 was that switch stopped responding from networks reachable via default gw. Only way to fix this was reboot. But I do not remember what sw version the switch was running.
