The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes how to configure object tracking on Cisco NX-OS switches.
This chapter includes the following sections:
Object tracking allows you to track specific objects on the switch, such as the interface line protocol state, IP routing, and route reachability, and to take action when the tracked object’s state changes. This feature allows you to increase the availability of the network and shorten recovery time if an object state goes down.
This section includes the following topics:
The object tracking feature allows you to create a tracked object that multiple clients can use to modify the client behavior when a tracked object changes. Several clients register their interest with the tracking process, track the same object, and take different actions when the object state changes.
Clients include the following features:
The object tracking monitors the status of the tracked objects and communicates any changes made to interested clients. Each tracked object is identified by a unique number that clients can use to configure the action to take when a tracked object changes state.
Cisco NX-OS tracks the following object types:
For example, you can configure HSRP to track the line protocol of the interface that connects one of the redundant routers to the rest of the network. If that link protocol goes down, you can modify the priority of the affected HSRP router and cause a switchover to a backup router that has better network connectivity.
An object track list allows you to track the combined states of multiple objects. Object track lists support the following capabilities:
Other entities, such as virtual Port Channels (vPCs) can use an object track list to modify the state of a vPC based on the state of the multiple peer links that create the vPC. See the Cisco Nexus 6000 Series NX-OS Interfaces Configuration Guide, Release 7.x, for more information on vPCs.
See the “Configuring an Object Track List with a Boolean Expression” section for more information on track lists.
Object tracking supports Virtual Routing and Forwarding (VRF) instances. By default, Cisco NX-OS places you in the default VRF unless you specifically configure another VRF. By default, Cisco NX-OS tracks the route reachability state of objects in the default VRF. If you want to track objects in another VRF, you must configure the object to be a member of that VRF (see the “Configuring Object Tracking for a Nondefault VRF” section).
For more information, see Chapter12, “Configuring Layer 3 Virtualization”
The following table shows the licensing requirements for this feature:
The following prerequisites are required for using this feature on Cisco DCNM. For a full list of feature-specific prerequisites, see the platform-specific documentation.
Object tracking has the following prerequisites:
Object tracking has the following configuration guidelines and limitations:
The following platform supports this feature. For platform-specific information, including guidelines and limitations, system defaults, and configuration limits, see the corresponding documentation.
|
|
---|---|
Table 19-1 lists the default settings for object tracking parameters.
|
|
---|---|
You can access object tracking from the Routing feature selection.
For more information about the Data Center Network Manager features, see the Cisco DCNM Fundamentals Configuration Guide, Release 5.x
This section includes the following topics:
Note If you are familiar with the Cisco IOS CLI, be aware that the Cisco NX-OS commands for this feature might differ from the Cisco IOS commands that you would use.
You can configure Cisco NX-OS to track the line protocol or IPv4 routing state of an interface.
2. track object- id interface interface-type number { ip routing | line-protocol }
To create a tracked object for an interface, follow these steps:
Step 1 From the Feature Selector pane, choose Routing > Gateway Redundancy > Object Tracking.
The available devices appear in the Summary pane.
Step 2 From the Summary pane, click the device that you want to configure object tracking on.
Step 3 From the menu bar, choose Actions > New Track Object.
The system highlights the new tracked object row in the Summary pane, and tabs update in the Details pane.
Step 4 From the highlighted Track Object ID field, enter the object ID.
Step 5 From the Details pane, click the Object Tracking Details tab.
The Object Tracking Details tab appears.
Step 6 From the Object Tracking Details tab, in the Tracking Object Type drop-down list, choose Interface.
Step 7 From the Instance drop-down list, choose the interface that you want to track.
Step 8 From the Parameter drop-down list, choose either IP Routing, IPv6 Routing, or Line Protocol.
Step 9 From the menu bar, choose File > Deploy to apply your changes to the device.
This example shows how to configure object tracking for the line protocol state on Ethernet 1/2:
This example shows how to configure object tracking for the IPv4 routing state on Ethernet 1/2:
You can configure Cisco NX-OS to track the existence and reachability of an IP route.
2. track object- id ip route prefix/length reachability
3. (Optional) show track [ object- id ]
4. (Optional) copy running-config startup-config
To create a tracked object for route reachability, follow these steps:
Step 1 From the Feature Selector pane, choose Routing > Gateway Redundancy > Object Tracking.
The available devices appear in the Summary pane.
Step 2 From the Summary pane, click the device that you want to configure object tracking on.
Step 3 From the menu bar, choose Actions > New Track Object.
The system highlights the new tracked object row in the Summary pane, and tabs update in the Details pane.
Step 4 From the highlighted Track Object ID field, enter the object ID.
Step 5 From the Details pane, click the Object Tracking Details tab.
The Object Tracking Details tab appears.
Step 6 From the Object Tracking Details tab, in the Tracking Object Type drop-down list, choose IP Route.
Step 7 In the Instance field, enter the prefix and network mask length that you want to track.
For IPv4, the format is A.B.C.D/length. For IPv6, the format is A:B:C::D/length.
Step 8 (Optional) From the VRF name drop-down list, choose the VRF where this route exists.
The default is the default VRF.
Step 9 From the menu bar, choose File > Deploy to apply your changes to the device.
This example shows how to configure object tracking for an IPv4 route in the default VRF.
You can configure an object track list that contains multiple tracked objects. A tracked list contains one or more objects. The Boolean expression enables two types of calculation by using either "and" or "or" operators. For example, when tracking two interfaces using the "and" operator, up means that both interfaces are up, and down means that either interface is down.
2. track track-number list boolean { and | or }
This example shows how to configure a track list with multiple objects as a Boolean “and”:
You can configure an object track list that contains a percentage threshold. A tracked list contains one or more objects. The percentage of up objects must exceed the configured track list up percent threshold before the track list is in an up state. For example, if the tracked list has three objects, and you configure an up threshold of 60 percent, two of the objects must be in the up state (66 percent of all objects) for the track list to be in the up state.
2. track track-number list threshold percentage
This example shows how to configure a track list with an up threshold of 70 percent and a down threshold of 30 percent:
You can configure an object track list that contains a weight threshold. A tracked list contains one or more objects. The combined weight of up objects must exceed the configured track list up weight threshold before the track list is in an up state. For example, if the tracked list has three objects with the default weight of 10 each, and you configure an up threshold of 15, two of the objects must be in the up state (combined weight of 20) for the track list to be in the up state.
2. track track-number list threshold weight
3. threshold weight up up-value down down-value
This example shows how to configure a track list with an up weight threshold of 30 and a down threshold of 10:
In this example, the track list is up if object 10 and object 20 are up, and the track list goes to the down state if all three objects are down.
You can configure a delay for a tracked object or an object track list that delays when the object or list triggers a stage change. The tracked object or track list starts the delay timer when a state change occurs but does not recognize a state change until the delay timer expires. At that point, Cisco NX-OS checks the object state again and records a state change only if the object or list currently has a changed state. Object tracking ignores any intermediate state changes before the delay timer expires.
For example, for an interface line-protocol tracked object that is in the up state with a 20-second donw delay, the delay timer starts when the line protocol goes down. The object is not in the down state unless the line protocol is down 20 seconds later.
You can configure independent up delay and down delay for a tracked object or track list. When you delete the delay, object tracking deletes both the up and down delay.
You can change the delay at any point. If the object or list is already counting down the delay timer from a triggered event, the new delay is computed as the following:
2. track object- id { parameters }
3. track track-number list { parameters }
4. delay { up up-time [ down down-time ] | down down-time [ up up-time ]}
This example shows how to configure object tracking for a route and use delay timers:
This example shows how to configure a track list with an up weight threshold of 30 and a down threshold of 10 with delay timers:
This example shows the delay timer in the show track command output before and after an interface is shut down:
You can configure Cisco NX-OS to track an object in a specific VRF.
2. track object- id ip route prefix/length reachability
This example shows how to configure object tracking for a route and use VRF Red to look up reachability information for this object:
This example shows how to modify tracked object 2 to use VRF Blue instead of VRF Red to look up reachability information for this object:
To display the object tracking configuration information, perform one of the following tasks:
|
|
---|---|
Displays the object tracking information for one or more objects. |
|
To view client details for a tracked object, follow these steps:
Step 1 From the Feature Selector pane, choose Routing > Gateway Redundancy > Object Tracking.
The available devices appear in the Summary pane.
Step 2 From the Summary pane, click the device that you want to view tracked objects on.
Step 3 Click the tracked object that you want to view clients for.
The system highlights the tracked object row in the Summary pane, and tabs update in the Details pane.
Step 4 From the Details pane, click the Object Tracking Details tab.
The Object Tracking Details tab appears.
Step 5 From the Object Tracking Details tab, click the Client Details section.
This example shows how to configure object tracking for route reachability and use VRF Red to look up reachability information for this route:
See the following topics for information related to object tracking:
This section includes the following field descriptions for Object Tracking:
|
|
---|---|
Display only. Time the parameter last changed status for this object. |
For additional information related to implementing object tracking, see the following sections:
|
|
---|---|
Cisco Nexus 6000 Series Command Reference, Cisco NX-OS Releases 7.x |
|
|
---|---|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |