Cisco N5010P-N2K-BE, Software Configuration Manual

Page: 650 / 704

S e n d f e e d b a c k t o n x 5 0 0 0 - d o c f e e d b a c k @ c i s c o . c o m
48-2
Cisco Nexus 5000 Series Switch CLI Software Configuration Guide
OL-16597-01
Chapter 48 Configuring Port Tracking
Configuring Port Tracking
Figure 48-1 Traffic Recovery Using Port Tracking
The port tracking feature monitors and detects failures that cause topology changes and brings down the
links connecting the attached devices. When you enable this feature and explicitly configure the linked
and tracked ports, the switch software monitors the tracked ports and alters the operational state of the
linked ports on detecting a link state change.
The following terms are used in this chapter:
•
Tracked ports—A port whose operational state is continuously monitored. The operational state of
the tracked port is used to alter the operational state of one or more ports. Fibre Channel, VSAN,
SAN port channel, or a Gigabit Ethernet port can be tracked. Generally, ports in E and TE port
modes can also be F ports.
•
Linked ports—A port whose operational state is altered based on the operational state of the tracked
ports. Only physical Fibre Channel ports can be linked ports.
Port tracking has the following features:
•
The application brings the linked port down when the tracked port goes down. When the tracked port
recovers from the failure and comes back up again, the linked port is also brought up automatically
(unless otherwise configured).
•
You can forcefully continue to keep the linked port down, even though the tracked port comes back
up. In this case, you must explicitly bring up the linked port when required.
Configuring Port Tracking
Before configuring port tracking, consider the following guidelines:
•
Verify that the tracked ports and the linked ports are on the same Cisco switch.
•
Be aware that the linked port is automatically brought down when the tracked port goes down.
•
Do not track a linked port back to itself (for example, Port fc2/2 to Port fc2/4 and back to Port fc2/2)
to avoid recursive dependency.
This section includes the following topics:
•
Enabling Port Tracking, page 48-3
•
About Configuring Linked Ports, page 48-3
•
Operationally Binding a Tracked Port, page 48-3
•
About Tracking Multiple Ports, page 48-4