Cisco Nexus 5000 Series - Forcefully Shutting down; Forcefully Shutting down a Tracked Port

Forcefully Shutting down
If a tracked port flaps frequently, tracking ports using the operational binding feature may cause frequent
topology changes. You might choose to keep the port in the down state until you are able to resolve the reason
for these frequent flaps. Keeping the flapping port in the down state forces the traffic to flow through the
redundant path until the primary tracked port problems are resolved. When the problems are resolved and the
tracked port is back up, you can explicitly enable the interface.
If you configure this feature, the linked port continues to remain in the shutdown state even after the tracked
port comes back up. You must explicitly remove the forced shut state (by administratively bringing up this
interface) of the linked port once the tracked port is up and stable.
Forcefully Shutting Down a Tracked Port
You can forcefully shut down a tracked port.
SUMMARY STEPS
1.
configure terminal
2.
switch(config)# interface fc slot/port
3.
port-track force-shut
4.
no port-track force-shut
DETAILED STEPS
PurposeCommand or Action
Enters global configuration mode.configure terminal
Example:
switch# configure terminal
switch(config)#
Step 1
Configures the specified interface and enters the interface
configuration mode. You can now configure tracked ports.
switch(config)# interface fc slot/port
Step 2
Forcefully shuts down the tracked port.port-track force-shut
Example:
switch(config-if)# port-track force-shut
Step 3
Removes the port shutdown configuration for the tracked
port.
no port-track force-shut
Example:
switch(config-if)# no port-track force-shut
Step 4
Cisco Nexus 5000 Series NX-OS SAN Switching Configuration Guide, Release 5.2(1)N1(1)
OL-27583-01 293
Configuring Port Tracking
Configuring Port Tracking