Cisco Nexus 5000 Series Switch Fabric Manager Software Configuration Guide, NX-OS 4.0 (OL-16598-01, June 2008)

Send comments to [e-mail]
27-6
Nexus 5000 Series Switch Fabric Manager Software Configuration Guide
OL-16598-01
Chapter 27 Configuring Port Tracking
Configuring Port Tracking
Tracking Multiple Ports
To track multiple ports, see the “Operationally Binding a Tracked Port” section on page 27-4.
The following example shows how to enable port tracking for multiple interfaces:
switch# configure
switch(config)# interface fc 2/3
switch(config-if)# port-track interface fc 2/3
switch(config-if)# port-track interface san-port-channel 2
About Monitoring Ports in a VSAN
You can optionally configure one VSAN from the set of all operational VSANs on the tracked port with
the linked port by specifying the required VSAN. This level of flexibility provides higher granularity in
tracked ports. In some cases, when a tracked port is a TE port, the set of operational VSANs on the port
can change dynamically without bringing down the operational state of the port. In such cases, the port
VSAN of the linked port can be monitored on the set of operational VSANs on the tracked port.
If you configure this feature, the linked port is up only when the VSAN is up on the tracked port.
Tip The specified VSAN does not have to be the same as the port VSAN of the linked port.
Monitoring Ports in a VSAN
To monitor a tracked port in a specific VSAN, see “Operationally Binding a Tracked Port” section on
page 27-4.
About Forceful Shutdown
If a tracked port flaps frequently, then tracking ports using the operational binding feature may cause
frequent topology change. In this case, you may 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.
Tip 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
To forcefully shut down a tracked port, see “Operationally Binding a Tracked Port” section on page 27-4.