Netonix Forums

An SFP reset happened this morning and port 15 is mentioned in the log.
Not sure if that is the LAG or a port numbering error in the code.

Recall there was a numbering issue at one point, but couldn't find anything similar in other posts.

Version 1.4.9, Board rev F

Code: Select all

Mar 7 08:10:15 SFP: FAULT on SFP 0, resetting...
Mar 7 08:10:16 SFP: FAULT on SFP 0, resetting...
Mar 7 08:10:17 STP: set port 13 to discarding
Mar 7 08:10:17 STP: set port 14 to discarding
Mar 7 08:10:17 LACP: LACP changed state to Active on port 13 (key 4)
Mar 7 08:10:17 STP: set port 15 to discarding
Mar 7 08:10:17 STP: set port 13 to discarding
Mar 7 08:10:17 STP: set port 14 to discarding
Mar 7 08:10:17 switch[1286]: LACP changed state to Active on port 13 (Core A) (key 4)
Mar 7 08:10:18 STP: MSTI0: New root on port 15, root path cost is 10000
Mar 7 08:10:18 STP: set port 15 to learning
Mar 7 08:10:18 STP: set port 13 to learning
Mar 7 08:10:18 STP: set port 14 to learning
Mar 7 08:10:18 STP: set port 15 to forwarding
Mar 7 08:10:18 STP: set port 13 to forwarding
Mar 7 08:10:18 STP: set port 14 to forwarding
Mar 7 08:10:19 sSMTP[1289]: Creating SSL connection to host
Mar 7 08:10:20 sSMTP[1289]: SSL connection using AES256-SHA


Everything is working fine, just never saw that port # before.

Possibly a bad SFP module?

Since we use the same switch core for all switches (current models) SFP 0 and 1 are seen as ports 25 and 26 then Eric has to re-map the port numbers to the Log which SFP 0 becomes Port 13 and SFP 1 becomes Port 14 on a WS-12

When you create a LAG the switch now see that as a single Port which becomes Port 15

sirhc wrote:When you create a LAG the switch now see that as a single Port which becomes Port 15

Thank you, that is what I suspected and wanted to be certain.


Yeah I think that SFP is going. Will re-seat it later to see if it helps, and swap if it happens again.
Nothing wrong on the Netonix side as usual, just confused by the # 15. Thanks.

Closing the loop: it was a bad SFP