WS-26-500DC switch, uptime of 26 days. Enabled syslog to a remote server and I can no longer access switch. I can ping it, but no webui.
I can establish an initial ssh session to the switch, but when I enter the creds, the screen just hangs. I enabled the syslog on 3 switches prior to this one and they all worked fine.
We are working on a maintenance window to power cycle the switch on site unless there are other suggestions.
Just wanted to report this gremlin.
1.50, enabled syslog=no access to switch
-
sirhc - Employee
- Posts: 7416
- Joined: Tue Apr 08, 2014 3:48 pm
- Location: Lancaster, PA
- Has thanked: 1608 times
- Been thanked: 1325 times
Re: 1.50, enabled syslog=no access to switch
Power cycle seems right thing to do.
I hope this is v1.5.0 or v1.5.1rc11
I hope this is v1.5.0 or v1.5.1rc11
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
-
sirhc - Employee
- Posts: 7416
- Joined: Tue Apr 08, 2014 3:48 pm
- Location: Lancaster, PA
- Has thanked: 1608 times
- Been thanked: 1325 times
Re: 1.50, enabled syslog=no access to switch
Wifimax wrote:yup it was 1.5.0 stable
Let me know how it goes
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
Re: 1.50, enabled syslog=no access to switch
Have not made it there yet... But issue #2...
WS-12-250B netonix on 1.5.0 crashed when I logged into it. the UI halfway loaded then the switch went down, and all devices were unpowered for a few seconds. Thankfully it booted back up. I realize this model is older, but I think I am going to just schedule to replace these.
So out of 12 switches I enabled syslog on, I lost access to one, and the other completely rebooted when I just logged into the UI.
I'm not going to lie I'm a little scared to log into these anymore lol......
WS-12-250B netonix on 1.5.0 crashed when I logged into it. the UI halfway loaded then the switch went down, and all devices were unpowered for a few seconds. Thankfully it booted back up. I realize this model is older, but I think I am going to just schedule to replace these.
So out of 12 switches I enabled syslog on, I lost access to one, and the other completely rebooted when I just logged into the UI.
I'm not going to lie I'm a little scared to log into these anymore lol......
-
sirhc - Employee
- Posts: 7416
- Joined: Tue Apr 08, 2014 3:48 pm
- Location: Lancaster, PA
- Has thanked: 1608 times
- Been thanked: 1325 times
Re: 1.50, enabled syslog=no access to switch
Well not sure what to say. I personally am not having this issue.
I would not replace the WS-12-250A units, I am still running WS-24-400A units which were from the original BETA productions in 90% of my towers.
All out current switches use the same SOC, same firmware, and basically same design (circuit wise).
But put into perspective you have had 2 issues, granted any issue SUCKS as a WISP;
1 unit that you lost access to after enabling SYS Log server, the switch is still operational you just can not get to it. - reason unknown. I would use a console cable when on site and look around before rebooting. Maybe plugging into the unit direct will work?
Another unit that rebooted when you logged into it but it came back up, again unknown reason.
If your running a large flat Layer 2 segments try Disable the Discovery TAB.
I would not replace the WS-12-250A units, I am still running WS-24-400A units which were from the original BETA productions in 90% of my towers.
All out current switches use the same SOC, same firmware, and basically same design (circuit wise).
But put into perspective you have had 2 issues, granted any issue SUCKS as a WISP;
1 unit that you lost access to after enabling SYS Log server, the switch is still operational you just can not get to it. - reason unknown. I would use a console cable when on site and look around before rebooting. Maybe plugging into the unit direct will work?
Another unit that rebooted when you logged into it but it came back up, again unknown reason.
If your running a large flat Layer 2 segments try Disable the Discovery TAB.
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
6 posts
Page 1 of 1
Who is online
Users browsing this forum: Google [Bot] and 49 guests