Problems with port dropping

[jhofford]

I've got a Netonix WS-12-250-DC that is constantly dropping a port. Does anyone know why port 9 is constantly dropping out? That port is connected to a Mimosa B5C that appears to be functioning normally.


Jun 10 17:03:43 Port: link state changed to 'down' on port 9
Jun 10 17:03:43 STP: msti 0 set port 9 to discarding
Jun 10 17:03:43 STP: MSTI0: New root on port 1, root path cost is 20000, root bridge id is 32768.74-4D-28-D7-D2-27
Jun 10 17:03:43 STP: msti 0 set port 2 to discarding
Jun 10 17:03:43 STP: msti 0 set port 2 to learning
Jun 10 17:03:43 STP: msti 0 set port 2 to forwarding
Jun 10 17:03:45 Port: link state changed to 'up' (1G) on port 9
Jun 10 17:03:45 STP: msti 0 set port 9 to discarding
Jun 10 17:03:46 STP: MSTI0: New root on port 9, root path cost is 20011, root bridge id is 4096.64-D1-54-82-FF-FF
Jun 10 17:03:46 STP: msti 0 set port 1 to discarding
Jun 10 17:03:46 STP: msti 0 set port 9 to learning
Jun 10 17:03:46 STP: msti 0 set port 9 to forwarding
Jun 10 17:03:46 STP: msti 0 set port 1 to learning
Jun 10 17:03:46 STP: msti 0 set port 1 to forwarding
Jun 10 17:05:39 Port: link state changed to 'down' on port 9
Jun 10 17:05:39 STP: msti 0 set port 9 to discarding
Jun 10 17:05:39 STP: MSTI0: New root on port 1, root path cost is 20000, root bridge id is 32768.74-4D-28-D7-D2-27
Jun 10 17:05:39 STP: msti 0 set port 2 to discarding
Jun 10 17:05:39 STP: msti 0 set port 2 to learning
Jun 10 17:05:39 STP: msti 0 set port 2 to forwarding
Jun 10 17:05:41 Port: link state changed to 'up' (1G) on port 9
Jun 10 17:05:41 STP: msti 0 set port 9 to discarding
Jun 10 17:05:42 Port: link state changed to 'down' on port 9
Jun 10 17:05:44 Port: link state changed to 'up' (1G) on port 9
Jun 10 17:05:44 STP: msti 0 set port 9 to discarding
Jun 10 17:05:46 Port: link state changed to 'down' on port 9
Jun 10 17:05:48 Port: link state changed to 'up' (1G) on port 9
Jun 10 17:05:48 STP: msti 0 set port 9 to discarding
Jun 10 17:05:51 Port: link state changed to 'down' on port 9
Jun 10 17:05:53 Port: link state changed to 'up' (1G) on port 9
Jun 10 17:05:53 STP: msti 0 set port 9 to discarding
Jun 10 17:05:54 STP: MSTI0: New root on port 9, root path cost is 20011, root bridge id is 4096.64-D1-54-82-FF-FF
Jun 10 17:05:54 STP: msti 0 set port 1 to discarding
Jun 10 17:05:54 STP: msti 0 set port 9 to learning
Jun 10 17:05:54 STP: msti 0 set port 9 to forwarding
Jun 10 17:05:54 STP: msti 0 set port 1 to learning
Jun 10 17:05:54 STP: msti 0 set port 1 to forwarding
Jun 10 17:09:32 Port: link state changed to 'down' on port 9
Jun 10 17:09:32 STP: msti 0 set port 9 to discarding
Jun 10 17:09:33 STP: MSTI0: New root on port 1, root path cost is 20000, root bridge id is 32768.74-4D-28-D7-D2-27
Jun 10 17:09:33 STP: msti 0 set port 2 to discarding
Jun 10 17:09:33 STP: msti 0 set port 2 to learning
Jun 10 17:09:33 STP: msti 0 set port 2 to forwarding
Jun 10 17:09:35 Port: link state changed to 'up' (1G) on port 9
Jun 10 17:09:35 STP: msti 0 set port 9 to discarding
Jun 10 17:09:36 STP: MSTI0: New root on port 9, root path cost is 20011, root bridge id is 4096.64-D1-54-82-FF-FF
Jun 10 17:09:36 STP: msti 0 set port 1 to discarding
Jun 10 17:09:36 STP: msti 0 set port 9 to learning
Jun 10 17:09:36 STP: msti 0 set port 9 to forwarding
Jun 10 17:09:36 STP: msti 0 set port 1 to learning
Jun 10 17:09:36 STP: msti 0 set port 1 to forwarding

[ahteran]

The problem is unfortunately on the mimosa side. the only thing to do is to see what happens using cat7 sftp

[jhofford]

Thanks for the info. I'll have my techs check out the Mimosa.