Monitoring Ports In A Vsan; Forcefully Shutting Down - Cisco Nexus 5500 Series NX-OS Configuration Manual

Configuring Port Tracking
The specified VSAN does not have to be the same as the port VSAN of the linked port.

Monitoring Ports in a VSAN

You can monitor a tracked port in a specific VSAN.
Procedure
Step 1
Step 2
Step 3
Step 4

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.
Cisco Nexus 5500 Series NX-OS SAN Switching Configuration Guide, Release 7.x
284
Command or Action
configure terminal
Example:
switch# configure terminal
switch(config)#
switch(config)# interface fc slot/port
port-track interface san-port-channel 1 vsan
2
Example:
switch(config-if)# port-track interface
san-port-channel 1 vsan 2
no port-track interface san-port-channel 1
vsan 2
Example:
switch(config-if)# port-track interface
san-port-channel 1 vsan 2
Configuring Port Tracking
Purpose
Enters global configuration mode.
Configures the specified interface and enters the
interface configuration mode. You can now
configure tracked ports.
If this is a QSFP+ GEM, the slot/port
Note
syntax is slot/QSFP-module/port.
Enables tracking of the SAN port channel in
VSAN 2.
Removes the VSAN association for the linked
port. The SAN port channel link remains in effect.
OL-30895-01