Information About Port Tracking - Cisco N5010P-N2K-BE Software Configuration Manual

Nx-os software configuration guide
Table of Contents

Advertisement

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
Configuring Port Tracking
Cisco Nexus 5000 Series switches offer the port tracking feature on physical Fibre Channel interfaces
(but not on virtual Fibre Channel interfaces). This feature uses information about the operational state
of the link to initiate a failure in the link that connects the edge device. This process of converting the
indirect failure to a direct failure triggers a faster recovery process towards redundant links. When
enabled, the port tracking feature brings down the configured links based on the failed link and forces
the traffic to be redirected to another redundant link.
This chapter includes the following sections:

Information About Port Tracking

Generally, hosts can instantly recover from a link failure on a link that is immediately (direct link)
connected to a switch. However, recovering from an indirect link failure between switches in a WAN or
MAN fabric with a keepalive mechanism is dependent on several factors such as the timeout values
(TOVs) and on registered state change notification (RSCN) information (see the
Values" section on page 43-1
In
Figure
ISL 2 fails between the two switches, recovery depends on TOVs, RSCNs, and other factors.
OL-16597-01
Information About Port Tracking, page 48-1
Configuring Port Tracking, page 48-2
Displaying Port Tracking Information, page 48-6
Default Port Tracking Settings, page 48-7
and
48-1, when the direct link 1 to the host fails, recovery can be immediate. However, when the
C H A P T E R
"About RSCN Information" section on page
Cisco Nexus 5000 Series Switch CLI Software Configuration Guide
48
"Fibre Channel Timeout
41-5).
48-1

Advertisement

Table of Contents
loading

This manual is also suitable for:

Nexus 5000 series

Table of Contents