Page 1 of 1

Switch GUI / Ping dead but still sending SMTP emailss

Posted: Wed Jun 05, 2019 12:13 pm
by expohl
I have a ws26dc that's running 1.5.2 and this morning I had a backhaul go down that's connected to this switch, I arrived on site and it appears the radio is dead but the interesting thing is the switch GUI won't respond nor will ssh or pings even when directly connected after a power cycle. No config changes recently.

Interestingly the switch is able to send me alert emails about the watchdog...

I guess I'll need to default it?

Re: Switch GUI / Ping dead but still sending SMTP emailss

Posted: Wed Jun 05, 2019 1:02 pm
by sirhc
Or use console cable and see whats up with the configuration?

Re: Switch GUI / Ping dead but still sending SMTP emailss

Posted: Wed Jun 05, 2019 1:04 pm
by expohl
I don't have one with me, but why would the config change ?

Re: Switch GUI / Ping dead but still sending SMTP emailss

Posted: Wed Jun 05, 2019 1:11 pm
by sirhc
expohl wrote:I don't have one with me, but why would the config change ?


I do not think it changed but I have no idea what your config is, if you have ports in VLANs or not and so on.

Re: Switch GUI / Ping dead but still sending SMTP emailss

Posted: Wed Jun 05, 2019 4:50 pm
by expohl
I got it, I will fumble around and see if I can work the netonix cli. The switch has been on a persistent config for some time and this issue arose over night, a BH radio started showing a port flap and at the same time the switch is unresponsive via icmp, ssh and GUI although it's passing traffic completely normal is able to send SMTP email. I suspect it's a glitch of some sort just like the stack of ws12-250dc that were all not seeing the i2c PSU data and then suddenly work after a factory default.

Any ideas are greatly appreciated as I'm pretty positive it's not a config issue.

Re: Switch GUI / Ping dead but still sending SMTP emailss

Posted: Fri Jun 07, 2019 2:43 pm
by Stephen
You can get the switch log from the netonix cli, if you can access them please post them here it might help figure out what has happened.
Also, drop into the linux console and run the command
Code: Select all
ps

and paste the results here too. This will give us a view of what's going on inside of the switch right now.