12-12-2016 07:46 AM - edited 03-08-2019 08:32 AM
I have three 2960S-24PD-L switches stacked together using ver 15.0.(2) SE8. The problem is after a short period of time (less than a day or two) the switches lose the ability to telnet to them. Everything in the switch is running and up. Taking a console to the same switches can be a problem during this time as well. The only way to get them back to normal is to reboot them. I need a way to fix the glitch without resorting to just rebooting them. I thought I saw somewhere in the pages of notes that it is related to the software version. If this is the case I will need a version of code that still allows stacking and one that doesn't have this problem. Does anyone know of a fix to this issue? Or a better version of software for this scenario?
Solved! Go to Solution.
12-12-2016 07:59 AM
A frequent cause of symptoms like this where it loses the ability to telnet to the switch is that there is a memory leak. The best way to confirm this is to establish a session to the console port. You may have problems in logging in on the console but that is ok. The important thing is that you should be seeing copies of console messages and can see if there are messages about low memory or about unable to allocate memory, or similar messages.
HTH
Rick
12-12-2016 07:59 AM
A frequent cause of symptoms like this where it loses the ability to telnet to the switch is that there is a memory leak. The best way to confirm this is to establish a session to the console port. You may have problems in logging in on the console but that is ok. The important thing is that you should be seeing copies of console messages and can see if there are messages about low memory or about unable to allocate memory, or similar messages.
HTH
Rick
12-12-2016 08:08 AM
Richard,
That is correct! I can't even get in to the console this time. The error states that it is low on memory, and to try again later. Do you have any suggestions on fixes? Thank you.
Mike
12-12-2016 08:25 AM
Mike
Thank you for the additional information. If the error states that is low on memory then it is pretty clear that the issue is a memory leak. If the error began as soon as the switch booted up then it might be an issue that the switch does not have sufficient memory to run that version of code. But if it runs ok for a day or two and then develops the problem it is almost certainly a memory leak. For a memory leak the solution is to update to a different version of code. I do not have a suggestion for a version to try but there are lots of options more recent than 15.0(2). The ability to upgrade the code depends on whether you have maintenance contracts for these switches. Are these switches covered by a maintenance contract?
HTH
Rick
12-12-2016 08:34 AM
Richard,
Unfortunately I do not have a maintenance contract with this stack. I have a contract with other distribution layer switches but not these access layer switches. I'll have to find a version of code that supports stacking and also doesn't have this problem. I'm guessing anything past 15.0 (2) will work better. Thank you for putting aside the time to hear me out. Thanks.
Mike
12-12-2016 08:50 AM
Mike
You are quite welcome. I am glad that my suggestions were helpful. Thank you for using the rating system to nark this question as answered.
HTH
Rick
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide