Was the port working previously? Was the module installed with the switch off? What is the output of show stack-port diag? If you select the port and do no shutdown does it come up?
Yes we had both switches off when we installed the modules and cables. we never noticed that one side wasn't working till the other day when I found the command #[tag:show] stack-port
Are you able to schedule downtime? We will want to isolate the issue. Try XG2 to XG2 and XG1 to XG1 and see which one stops working. Then we can see which switch and port is causing the problem and try to power off and reseat that module. If that doesn’t work we would want to swap the modules between the switches and see if the error stays with the module or the switch.
I will not be able to try these steps till production get caught up ( hopefully tomorrow ) . Is there any other commands I should try beside the ones I have used so far ?
mikeb2014
11 Posts
0
July 22nd, 2014 07:00
Hello Josh,
It turned that the stacking module in the Core switch was bad. We ordered another one swapped and I got up/ up
TX1-CORE-SW-STK01#show stack-port
Configured Running
Stack Stack Link Link
Unit Interface Mode Mode Status Speed (Gb/s)
---- ---------------- ---------- ---------- ------------ ------------
1 xg1 Stack Stack Link Up 12
1 xg2 Stack Stack Link Up 12
1 xg3 Ethernet Ethernet Link Down Unknown
1 xg4 Ethernet Ethernet Link Down Unknown
2 xg1 Stack Stack Link Up 12
2 xg2 Stack Stack Link Up 12
2 xg3 Ethernet Ethernet Link Down Unknown
2 xg4 Ethernet Ethernet Link Down Unknown
TX1-CORE-SW-STK01#
Thanks for all your help.
DELL-Josh Cr
Moderator
•
9.5K Posts
0
July 14th, 2014 17:00
Hi Mike,
Was the port working previously? Was the module installed with the switch off? What is the output of show stack-port diag? If you select the port and do no shutdown does it come up?
mikeb2014
11 Posts
0
July 15th, 2014 07:00
Hello Josh,
Yes we had both switches off when we installed the modules and cables. we never noticed that one side wasn't working till the other day when I found the command #[tag:show] stack-port
TX1-CORE-SW-STK01[tag:show] stack-port diag
Legend:
RBYT : Received Bytes RPKT : Received Packets
TBYT : Transmitted Bytes TPKT : Transmitted Packets
RFCS : Received Frame Check Sequence Errors RFRG : Received Fragment Errors
RJBR : Received Jabber Errors
RUND : Received Underrun Errors ROVR : Received Overrun Errors
TFCS : Transmit Frame Check Sequence Errors TERR : Transmit Errors
1 - xg1:
RBYT:0 RPKT:0 TBYT:0 TPKT:0
RFCS:0 RFRG:0 RJBR:0 RUND:0 ROVR:0
TFCS:0 TERR:0
1 - xg2:
RBYT:b068fd20 RPKT:4848101 TBYT:719dfc32 TPKT:bd44c2b
RFCS:0 RFRG:0 RJBR:0 RUND:0 ROVR:0
TFCS:0 TERR:0
2 - xg1:
RBYT:715dd8a2 RPKT:bd43e98 TBYT:b06750de TPKT:4847b93
RFCS:0 RFRG:0 RJBR:0 RUND:0 ROVR:0
--More-- or (q)uit
TFCS:0 TERR:0
2 - xg2:
RBYT:0 RPKT:0 TBYT:0 TPKT:0
RFCS:0 RFRG:0 RJBR:0 RUND:0 ROVR:0
TFCS:0 TERR:0
TX1-CORE-SW-STK01#
DELL-Josh Cr
Moderator
•
9.5K Posts
0
July 15th, 2014 10:00
Are you able to schedule downtime? We will want to isolate the issue. Try XG2 to XG2 and XG1 to XG1 and see which one stops working. Then we can see which switch and port is causing the problem and try to power off and reseat that module. If that doesn’t work we would want to swap the modules between the switches and see if the error stays with the module or the switch.
DELL-Josh Cr
Moderator
•
9.5K Posts
0
July 16th, 2014 10:00
Those commands were providing enough detail, so you don’t need to use any other ones, it was showing which ports were transmitting data.
mikeb2014
11 Posts
0
July 16th, 2014 10:00
OK Josh,
I will not be able to try these steps till production get caught up ( hopefully tomorrow ) . Is there any other commands I should try beside the ones I have used so far ?
#show stack-port
# show stack-port diag
Thanks Mike