12-250-dc Switch Unresponsive, (sort of)

[kennaster]

Hi All,
I have a Netonix 12-250-dc (1.5.2; F; 70; B). It's not behaving has expected. I have an AF5XHD on port 1 that is unresponsive and need to restore the link.

Symptoms:
I am unable to turn off and save POE on port one. It loses comm with switch and reverts.
I am unable to disable ethernet on port one and save. Switch loses comm with network and reverts.
I am unable to set the Power settings to have the port power cycle at a particular time (that command is ignored).
I am able to reset counters
I am unable to bounce the port. When I try this I lose connection to the switch.


I'm wondering if sending a new configuration (restore) file might bring this switch out of its funk. Anything else I might try? Has anyone heard of this happening before?

Side note: this switch is inside the Holiday Farm fire perimeter so unreachable due to forest wide closure. Other than this, the switch seems to be working okay. I'm trying to get comms back to a main site because most other communication is down in the valley.


Thanks in advance,
AK

Logs attached:
Sep 28 17:45:14 UI: Configuration changed by fadmin (::ffff:10.197.133.206)
Sep 28 17:45:14 UI: Port 1 PoE: changed from '48V' to 'Off'
Sep 28 17:45:19 Port: link state changed to 'down' on port 1
Sep 28 17:45:19 STP: msti 0 set port 1 to discarding
Sep 28 17:50:21 fadmin: Reverting to last known good configuration
Sep 28 17:50:23 switch[1166]: PoE enabled on port 1, PoE Smart is starting cable check
Sep 28 17:50:27 switch[1166]: Port 1 cable check results: Open, Open, Open, Open
Sep 28 17:50:27 switch[1166]: Port 1 passed PoE Smart cable check, turning on power
Sep 28 17:50:31 Port: link state changed to 'up' (1G) on port 1
Sep 28 17:50:31 STP: msti 0 set port 1 to discarding
Sep 28 17:50:33 STP: msti 0 set port 1 to learning
Sep 28 17:50:33 STP: msti 0 set port 1 to forwarding
Sep 28 17:50:44 Port: link state changed to 'down' on port 1
Sep 28 17:50:44 STP: msti 0 set port 1 to discarding
Sep 28 17:50:47 Port: link state changed to 'up' (1G) on port 1
Sep 28 17:50:47 STP: msti 0 set port 1 to discarding
Sep 28 17:50:50 STP: msti 0 set port 1 to learning
Sep 28 17:50:50 STP: msti 0 set port 1 to forwarding
Sep 28 17:50:51 Port: link state changed to 'down' on port 1
Sep 28 17:50:51 STP: msti 0 set port 1 to discarding
Sep 28 17:50:54 Port: link state changed to 'up' (1G) on port 1
Sep 28 17:50:54 STP: msti 0 set port 1 to discarding
Sep 28 17:50:56 STP: msti 0 set port 1 to learning
Sep 28 17:50:56 STP: msti 0 set port 1 to forwarding
Sep 28 18:00:20 UI: Configuration changed by fadmin (::ffff:10.197.133.206)
Sep 28 18:00:20 UI: Port 1 Shutdown_Time: changed from '' to '6:10PM'
Sep 28 18:00:20 UI: Port 1 Startup_Time: changed from '' to '6:15PM'
Sep 28 18:16:30 UI: Configuration changed by fadmin (::ffff:10.197.133.206)
Sep 28 18:16:30 UI: Port 1 Shutdown_Time: changed from '6:10PM' to ''
Sep 28 18:16:30 UI: Port 1 Startup_Time: changed from '6:15PM' to ''
Sep 28 18:18:36 UI: Configuration changed by fadmin (::ffff:10.197.133.206)
Sep 28 18:18:36 UI: Port 1 Enable: changed from 'Enabled' to 'Disabled'
Sep 28 18:18:39 Port: link state changed to 'down' on port 1
Sep 28 18:18:39 STP: msti 0 set port 1 to discarding
Sep 28 18:23:47 fadmin: Reverting to last known good configuration
Sep 28 18:23:51 Port: link state changed to 'up' (1G) on port 1
Sep 28 18:23:51 STP: msti 0 set port 1 to discarding
Sep 28 18:23:53 STP: msti 0 set port 1 to learning
Sep 28 18:23:53 STP: msti 0 set port 1 to forwarding

Linux:
Sep 28 17:45:16 syslogd exiting
Sep 28 17:45:17 syslogd started: BusyBox v1.19.4
Sep 28 17:50:21 syslogd exiting
Sep 28 17:50:22 syslogd started: BusyBox v1.19.4
Sep 28 18:00:22 syslogd exiting
Sep 28 18:00:23 syslogd started: BusyBox v1.19.4
Sep 28 18:16:32 syslogd exiting
Sep 28 18:16:33 syslogd started: BusyBox v1.19.4
Sep 28 18:18:38 syslogd exiting
Sep 28 18:18:39 syslogd started: BusyBox v1.19.4
Sep 28 18:23:48 syslogd exiting
Sep 28 18:23:49 syslogd started: BusyBox v1.19.4

[kennaster]

Bottom line is I'm unable to power cycle port 1. When I set POE to OFF and Save, it reverts after 300 seconds. I have tried the following:

touch /tmp/poe_override/1
/etc/init.d/lighttpd restart

killall ssmtp



I don't really know what I'm doing in there so if this symptom is common, I would love a link to proper troubleshooting docs.


Thanks again,
AK

[kennaster]

ISSUE RESOLVED

I don't know why it was doing that but I got a person on site who was able to move the radio to different port and then energize the radio. I could then connect to the radio and turn the original port off.

Maybe it's a combination of the AirFiber endlessly looking for its offline mate, or something else. No further action required.

[kennaster]

So after thinking about this more, and realizing that I had one of the ports mis-labeled, I have another question.

Does this switch have a built in safety feature that won't allow you to turn off the POE on a port if you're connecting in through that radio? This is the behavior that I was seeing - by accident.

Thanks again,
AK

[Stephen]

If the airfiber was how you where accessing the switch from the UI, then yes there is a feature like that but it doesn't work based on port.

In essence, when you are using the web UI, when changes are saved, the switch will then wait for the web UI to connect to it again, if that connection doesn't happen after a certain amount of time (which is configurable, go to Device->Config then under Switch look for Revert Timer, the number represents the time in seconds that it waits for the UI to regain contact)

Then the switch reverts to the previous configuration.

[kennaster]

Thanks, This is what it was doing, and since the port was mis-labeled, I was trying to power cycle the wrong radio. Mystery solved.

Thanks again,
AK

[Stephen]

Glad that was helpful.