Netonix Forums

We took an upgrade to WA V.8.4.0 software on our ubiquiti Litebeam radio's connected to WS6POE switches. The upgrade caused the radio's (running 24v POE) to drop. Turning POE off and on restarted the radio's however they dropped 1 hour later. I attempted to reboot the switches however I keep loosing connectivity. I could not find the correct CLI commands to reboot or restart the switches. Has anyone had this sort of issue with Ubiquiti/Netonix and how can I get the CLI commands?

Additional info
After reviewing logs it appears that the issue is with the 8.4.0 Ubiquiti software causing the port to change state constantly from 1g to 100m. Wondering if anyone else has experienced this? Below is a small sample of the logs:

Jan 10 06:42:07 STP: MSTI0: New root on port 4, root path cost is 40000
Jan 10 06:43:09 STP: MSTI0: New root on port 4, root path cost is 40000
Jan 10 06:43:27 STP: MSTI0: New root on port 4, root path cost is 40000
Jan 10 06:43:39 STP: MSTI0: New root on port 4, root path cost is 40000
Jan 10 06:44:29 STP: MSTI0: New root on port 4, root path cost is 40000
Jan 10 06:47:09 Port: link state changed to 'down' on port 3
Jan 10 06:47:09 STP: set port 3 to discarding
Jan 10 06:47:12 Port: link state changed to 'up' (100M-F) on port 3
Jan 10 06:47:12 STP: set port 3 to discarding
Jan 10 06:47:12 switch[1992]: unexpected link change on port 3 (OH_Haley_N5C to HE) from 1G to 100M-F
Jan 10 06:47:14 STP: set port 3 to learning
Jan 10 06:47:14 STP: set port 3 to forwarding
Jan 10 06:47:31 Port: link state changed to 'down' on port 3
Jan 10 06:47:31 STP: set port 3 to discarding
Jan 10 06:47:34 Port: link state changed to 'up' (1G) on port 3
Jan 10 06:47:34 STP: set port 3 to discarding
Jan 10 06:47:36 STP: set port 3 to learning
Jan 10 06:47:36 STP: set port 3 to forwarding
Jan 10 06:48:11 STP: MSTI0: New root on port 4, root path cost is 40000
Jan 10 06:53:44 Port: link state changed to 'down' on port 3
Jan 10 06:53:44 STP: set port 3 to discarding
Jan 10 06:53:46 Port: link state changed to 'up' (100M-F) on port 3
Jan 10 06:53:46 STP: set port 3 to discarding
Jan 10 06:53:46 switch[3254]: unexpected link change on port 3 (OH_Haley_N5C to HE) from 1G to 100M-F
Jan 10 06:53:49 STP: set port 3 to learning
Jan 10 06:53:49 STP: set port 3 to forwarding
Jan 10 06:54:05 Port: link state changed to 'down' on port 3
Jan 10 06:54:05 STP: set port 3 to discarding
Jan 10 06:54:08 Port: link state changed to 'up' (1G) on port 3
Jan 10 06:54:08 STP: set port 3 to discarding
Jan 10 06:54:11 STP: set port 3 to learning
Jan 10 06:54:11 STP: set port 3 to forwarding
Jan 10 06:54:46 STP: MSTI0: New root on port 4, root path cost is 40000
Jan 10 06:55:13 STP: MSTI0: New root on port 4, root path cost is 40000
Jan 10 06:58:59 STP: MSTI0: New root on port 4, root path cost is 40000
Jan 10 07:00:23 Port: link state changed to 'down' on port 3
Jan 10 07:00:23 STP: set port 3 to discarding
Jan 10 07:00:26 Port: link state changed to 'up' (100M-F) on port 3
Jan 10 07:00:26 STP: set port 3 to discarding

To reboot the switch, at the Netonix Switch# prompt:

Netonix Switch#: cmd
admin@switch$: reboot

not sure why you're having trouble, does locking the ports to 100mbit help?

I do not recommend locking port speed as this has many adverse effects as it will cause the link to drop if the locked speed can not be achieved.

Your can set to 100Mbps AUTO which means it will negotiate down if need be to 10Mbps but setting to 100M fixed is never a good idea.