I am facing a strange problem and after some unsuccessful research, I would like to request the help and advise from the community. I have looked for similar issues around the web but didn't find the solution so far.
My switch is configured as a MDF for my network with a .253 ip making the link between my router (.254) and the rest of the network.
The equipment is working very well but for some reasons, it becomes impossible to ping it or to access the GUI after some time : it varies from a few hours up to a few days after a boot.
Then the only way is to restart the switch physically or through the console port and ping & GUI will work back as normal for some time.
There is nothing in the log that would explain that the switch becomes unreachable.
During the time when the switch is unreachable : ALL the equipment connected to it are still working as normal (clients can access Internet, client can ping a server or another AP going through the switch...)
The configuration of the switch is very basic and I didn't find what can cause it.
What I have tried so far :
- Physical reboot
- Reboot through console
- Reset the switch to factory default and reconfigure from scratch
- Update to the last software version
Please see below the different details, if anyone has idea or input, feel free to share !
- Check current software being used. Consider upgrading to a recent and or advisory or gold-starred release , if applicable available and feasible. Verify the problem afterwards.
M.
-- ' 'Good body every evening' ' this sentence was once spotted on a logo at the entrance of a Weight Watchers Club !
- Also , use a syslog-server as a log collector. Keep an eye on messages from the device, als when everything is normal. Also enable all snmp-traps and idem ditto use a trap receiver and follow-up on snmp-trap-alerts.
M.
-- ' 'Good body every evening' ' this sentence was once spotted on a logo at the entrance of a Weight Watchers Club !
Thank you for the feedback & advise. I had the issue with 3 different software releases and the last one is a gold release so I would rather look at your suggestion to work on a log collector and see if I can find anything through the snmp as well.
check the interfaces connecting the switch and the router for anything such as input/output/drops (sh interfaces x). Actually, post the output of these commands:
We have similar problems. We have alot of 2960L with different software 15.2(7)E0, E2 and E3, sometimes a switch loses connection on SVI (Vlan1). It is not possible to connect to the switch with Telnet/SSH/Web or Ping. If we connect with console to the switch, it is not possible to telnet or ping anything else. Cant see anything special in the log and the SVI says UP and no STP blocking. If we do a "shutdown" and then a "no shutdown" on interface vlan 1 everything is good again. Traffic through the switch works all the time, it is just not possible to connect to the SVI.
We have a few C1000-switches to with latest software, 15.2(7)E3, and it has happend once on one of them too.
I have not found anything in the bug search tool, that could explain this, but I guess it is a bug.
It is interesting that the switch works ok for a while and then the problem develops. When I hear about things where a problem develops over time I tend to look for issues like memory leaks. Unless you have a syslog server looking at logs after the problem occurs is not helpful because log messages that are generated as the problem is developing are gone when the switch reboots. I would suggest that you check the logging level of messages on the switch itself - and the level of log messages sent to the server if a server is used. It would be good if the level were informational (and perhaps debug on the switch itself). If you can get access on the switch console while the problem is occurring then look in the logs for messages about the problem (especially any messages about memory allocation etc). It might also be interesting to see the output of show ip route and of show arp from the switch when the problem is occurring.
Since the initial post, I have made several tests trying to follow your advises, what I have covered :
Set up a syslog server to try to catch errors messages from the switch => I have not been able to see anything when the switch was becoming unreachable / unpingable
I have made a factory reset of the switch and restart the config from scratch => I was still getting the same issue with the switch becoming unreachable after some time
Finally, I think what seems to have solved the problem is to have the ports going to the APs using dynamic auto mode instead of any other modes (trunk...) => This is the only thing I have changed
Might be some luck but since this change, the switch is running perfectly and the WUI is reachable. It has been 6 weeks in a row for now.
I will keep you posted if anything new on this side.
Thank you for the update. Glad that the change that you made seems to have improved the situation. If there are any more developments in this please let us know.
HTH
Rick
Getting Started
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
