Netonix Forums

Hey guys,

I'm needing some help and I'm wondering if if anything in these logs sticks out to you. We have a WS-12-400-AC powering up 8 Rocket Prizm AP's but we have a couple of them spread across the network that like to randomly reboot. We have replaced everything, tried different ports, replaced the switch, cable, radio, everything you can think of on the hardware side has been replaced. Would STP be causing this radio to reboot?

Jan 4 01:07:31 Port: link state changed to 'up' (100M-F) on port 10
Jan 4 01:07:31 STP: msti 0 set port 10 to discarding
Jan 4 01:07:31 switch[3858]: unexpected link change on port 10 (VNS-BVB-5.7-90) from 1G to 100M-F
Jan 4 01:07:34 STP: msti 0 set port 10 to learning
Jan 4 01:07:34 STP: msti 0 set port 10 to forwarding
Jan 4 01:07:52 Port: link state changed to 'down' on port 10
Jan 4 01:07:52 STP: msti 0 set port 10 to discarding
Jan 4 01:07:56 Port: link state changed to 'up' (1G) on port 10
Jan 4 01:07:57 STP: msti 0 set port 10 to discarding
Jan 4 01:07:59 STP: msti 0 set port 10 to learning
Jan 4 01:07:59 STP: msti 0 set port 10 to forwarding
Jan 5 02:10:52 STP: MSTI0: New root on port 1, root path cost is 20000, root bridge id is 32768.
Jan 6 03:09:08 STP: MSTI0: New root on port 1, root path cost is 20000, root bridge id is 32768.
Jan 6 05:25:57 STP: MSTI0: New root on port 1, root path cost is 20000, root bridge id is 32768.
Jan 6 09:33:04 STP: MSTI0: New root on port 1, root path cost is 20000, root bridge id is 32768.
Jan 10 07:59:05 STP: MSTI0: New root on port 1, root path cost is 20000, root bridge id is 32768.
Jan 11 06:37:15 STP: MSTI0: New root on port 1, root path cost is 20000, root bridge id is 32768.
Jan 13 23:38:23 Port: link state changed to 'down' on port 10
Jan 13 23:38:23 STP: msti 0 set port 10 to discarding
Jan 13 23:38:26 Port: link state changed to 'up' (100M-F) on port 10
Jan 13 23:38:26 STP: msti 0 set port 10 to discarding
Jan 13 23:38:26 switch[3960]: unexpected link change on port 10 (VNS-BVB-5.7-90) from 1G to 100M-F
Jan 13 23:38:28 STP: msti 0 set port 10 to learning
Jan 13 23:38:28 STP: msti 0 set port 10 to forwarding
Jan 13 23:38:46 Port: link state changed to 'down' on port 10
Jan 13 23:38:46 STP: msti 0 set port 10 to discarding
Jan 13 23:38:51 Port: link state changed to 'up' (1G) on port 10
Jan 13 23:38:51 STP: msti 0 set port 10 to discarding
Jan 13 23:38:53 STP: msti 0 set port 10 to learning
Jan 13 23:38:53 STP: msti 0 set port 10 to forwarding

No, STP would not cause the radio to reboot unless you have a ping watch dog in play.

A ping watch dog on the radio or on the switch port could cause radio to reboot if STP blocked traffic longer than the time set to reboot.

What version of firmware on the switch are you running? If not the latest RC version please upgrade to that version. This most likely is not the issue but I need a base line to start at.