1 Gbps or 10 Gbps copper transceivers in any port of the 8624XS IOC module continue to receive power even after you enter the no sys power slot command. This causes the remote end to declare the port UP and send traffic.
Note
This issue can cause a problem only if you use the no sys power slot command locally to power down and leave the module in the slot. Although all the ports are initially brought down gracefully as part of the execution of no sys power slot, the ports with 1 Gbps or 10 Gbps copper transceivers continue to receive power locally causing the PHY in the transceivers to renegotiate with the remote port. Eventually the port will be declared UP in the remote end. However, the local end will still stay operationally down. Traffic loss results when the remote switch tries to send traffic to these ports.
To resolve this issue, use one of the following workarounds:
Shut down the ports (shutdown port) in the remote switch before issuing the no sys power slot command locally.
Configure VLACP on the links connected through the copper transceivers above if the far end switch supports VLACP. This provides a logical link down notification at the far end and prevents traffic loss.
Remove the local IOC module that was powered down.