- Preface
- Product Overview
- Command-Line Interfaces
- Configuring the Switch for the First Time
- Administering the Switch
- Configuring Virtual Switching Systems
- Programmability
- Configuring the Cisco IOS In-Service Software Upgrade Process
- Configuring the Cisco IOS XE In Service Software Upgrade Process
- Configuring Interfaces
- Checking Port Status and Connectivity
- Configuring Supervisor Engine Redundancy Using RPR and SSO on Supervisor Engine 6-E and Supervisor Engine 6L-E
- Configuring Supervisor Engine Redundancy Using RPR and SSO on Supervisor Engine 7-E, Supervisor Engine 7L-E, and Supervisor Engine 8-E
- Configuring Cisco NSF with SSO Supervisor Engine Redundancy
- Environmental Monitoring and Power Management
- Configuring Power over Ethernet
- Configuring Cisco Network Assistant
- Configuring VLANs, VTP, and VMPS
- Configuring IP Unnumbered Interface
- Configuring Layer 2 Ethernet Interfaces
- Configuring EVC-Lite
- Configuring SmartPort Macros
- Configuring Cisco IOS Auto Smartport Macros
- Configuring STP and MST
- Configuring Flex Links and MAC Address-Table Move Update
- Configuring Resilient Ethernet Protocol
- Configuring Optional STP Features
- Configuring EtherChannel and Link State Tracking
- Configuring IGMP Snooping and Filtering, and MVR
- Configuring IPv6 Multicast Listener Discovery Snooping
- Configuring 802.1Q Tunneling, VLAN Mapping, and Layer 2 Protocol Tunneling
- Configuring Cisco Discovery Protocol
- Configuring LLDP, LLDP-MED, and Location Service
- Configuring UDLD
- Configuring Unidirectional Ethernet
- Configuring Layer 3 Interfaces
- Configuring Cisco Express Forwarding
- Configuring Unicast Reverse Path Forwarding
- Configuring IP Multicast
- Configuring ANCP Client
- Configuring Bidirectional Forwarding Detection
- Configuring Campus Fabric
- Configuring Policy-Based Routing
- Configuring VRF-lite
- Configuring Quality of Service
- Configuring AVC with DNS-AS
- Configuring Voice Interfaces
- Configuring Private VLANs
- Configuring MACsec Encryption
- Configuring 802.1X Port-Based Authentication
- X.509v3 Certificates for SSH Authentication
- Configuring the PPPoE Intermediate Agent
- Configuring Web-Based Authentication
- Configuring Wired Guest Access
- Configuring Auto Identity
- Configuring Port Security
- Configuring Auto Security
- Configuring Control Plane Policing and Layer 2 Control Packet QoS
- Configuring Dynamic ARP Inspection
- Configuring the Cisco IOS DHCP Server
- Configuring DHCP Snooping, IP Source Guard, and IPSG for Static Hosts
- DHCPv6 Options Support
- Configuring Network Security with ACLs
- Support for IPv6
- Port Unicast and Multicast Flood Blocking
- Configuring Storm Control
- Configuring SPAN and RSPAN
- Configuring ERSPAN
- Configuring Wireshark
- Configuring Enhanced Object Tracking
- Configuring System Message Logging
- Onboard Failure Logging (OBFL)
- Configuring SNMP
- Configuring NetFlow-lite
- Configuring Flexible NetFlow
- Configuring Ethernet OAM and CFM
- Configuring Y.1731 (AIS and RDI)
- Configuring Call Home
- Configuring Cisco IOS IP SLA Operations
- Configuring RMON
- Performing Diagnostics
- Configuring WCCP Version 2 Services
- Configuring MIB Support
- Configuring Easy Virtual Networks
- ROM Monitor
- Acronyms and Abbreviations
- Index
- Understanding Enhanced Object Tracking
- Configuring Enhanced Object Tracking Features
Configuring Enhanced Object Tracking
This chapter describes how to configure enhanced object tracking on the Catalyst 4500 series switch. This feature provides a more complete alternative to the Hot Standby Routing Protocol (HSRP) tracking mechanism. which allows you to track the line-protocol state of an interface. If the line protocol state of an interface goes down, the HSRP priority of the interface is reduced and another HSRP device with a higher priority becomes active. The enhanced object tracking feature separates the tracking mechanism from HSRP and creates a separate, standalone tracking process that can be used by processes other than HSRP. This allows tracking other objects in addition to the interface line-protocol state. A client process, such as HSRP, can register an interest in tracking objects and request notification when the tracked object changes state.This feature increases the availability and speed of recovery of a routing system and decreases outages and outage duration.
Note Enhanced object tracking is not supported on switches running the LAN base feature set.
Unless otherwise noted, the term switch refers to a Catalyst 4500 series switch.
The chapter includes these sections:
- Understanding Enhanced Object Tracking
- Configuring Enhanced Object Tracking Features
- Monitoring Enhanced Object Tracking
Note For more details on enhanced object tracking, refer to this URL:
http://www.cisco.com/en/US/docs/ios/ios_xe/ipapp/configuration/guide/ipapp_eot_xe.html
For complete syntax and usage information for the switch commands used in this chapter, see the
Cisco IOS Command Reference Guides for the Catalyst 4500 Series Switch.
If a command is not in the Cisco Catalyst 4500 Series Switch Command Reference , you can locate it in the Cisco IOS Master Command List, All Releases.
Understanding Enhanced Object Tracking
Each tracked object has a unique number that is specified in the tracking command-line interface (CLI). Client processes use this number to track a specific object. The tracking process periodically polls the tracked object for value changes and sends any changes (as up or down values) to interested client processes, either immediately or after a specified delay. Several clients can track the same object, and can take different actions when the object changes state.
You can also track a combination of objects in a list by using either a weight threshold or a percentage threshold to measure the state of the list. You can combine objects using Boolean logic. A tracked list with a Boolean “AND” function requires that each object in the list be in an up state for the tracked object to be up. A tracked list with a Boolean “OR” function needs only one object in the list to be in the up state for the tracked object to be up.
Configuring Enhanced Object Tracking Features
- Default Configuration
- Tracking Interface Line-Protocol or IP Routing State
- Configuring a Tracked List
- Configuring HSRP Object Tracking
- Configuring Other Tracking Characteristics
- Configuring IP SLAs Object Tracking
- Configuring Static Routing Support
Default Configuration
Tracking Interface Line-Protocol or IP Routing State
You can track either the interface line protocol state or the interface IP routing state. When you track the IP routing state, these three conditions are required for the object to be up:
- IP routing must be enabled and active on the interface.
- The interface line-protocol state must be up.
- The interface IP address must be known.
If all three of these conditions are not met, the IP routing state is down.
To track the line-protocol state or IP routing state of an interface, perform the following task:
This example configures the tracking of an interface line-protocol state and verifies the configuration:
Configuring a Tracked List
You can configure a tracked list of objects with a Boolean expression, a weight threshold, or a percentage threshold. A tracked list contains one or more objects. An object must exist before it can be added to the tracked list.
- You configure a Boolean expression to specify calculation by using either “AND” or “OR” operators.
- When you measure the tracked list state by a weight threshold, you assign a weight number to each object in the tracked list. The state of the tracked list is determined by whether or not the threshold was met. The state of each object is determined by comparing the total weight of all objects against a threshold weight for each object.
- When you measure the tracked list by a percentage threshold, you assign a percentage threshold to all objects in the tracked list. The state of each object is determined by comparing the assigned percentages of each object to the list.
Configuring a Tracked List with a Boolean Expression
Configuring a tracked list with a Boolean expression enables 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.
To configure a tracked list of objects with a Boolean expression, perform this task:
Use the no track track-number global configuration command to delete the tracked list.
This example configures track list 4 with a Boolean AND expression that contains two objects with one object state negated. If the list is up, the list detects that object 2 is down:
Configuring a Tracked List with a Weight Threshold
To track by weight threshold, configure a tracked list of objects, specify that weight is used as the threshold, and configure a weight for each of its objects. The state of each object is determined by comparing the total weight of all objects that are up against a threshold weight for each object.
You cannot use the Boolean “NOT” operator in a weight threshold list.
Beginning in privileged EXEC mode, follow these steps to configure a tracked list of objects by using a weight threshold and to configure a weight for each object:
Use the no track track-number global configuration command to delete the tracked list.
The example configures track list 4 to track by weight threshold. If object 1 and object 2 are down, then track list 4 is up because object 3 satisfies the up threshold value of up 30. But if object 3 is down, both objects 1 and 2 must be up in order to satisfy the threshold weight.
This configuration can be useful if object 1 and object 2 represent two small bandwidth connections and object 3 represents one large bandwidth connection. The configured down 10 value means that once the tracked object is up, it will not go down until the threshold value is equal to or lower than 10, which in this example means that all connections are down.
Configuring a Tracked List with a Percentage Threshold
To track by percentage threshold, configure a tracked list of objects, specify that a percentage will be used as the threshold, and specify a percentage for all objects in the list. The state of the list is determined by comparing the assigned percentage of each object to the list.
You cannot use the Boolean “NOT” operator in a percentage threshold list.
To configure a tracked list of objects by using a percentage threshold, perform this task:
Use the no track track-number global configuration command to delete the tracked list.
This example configures tracked list 4 with three objects and a specified percentages to measure the state of the list:
Configuring HSRP Object Tracking
To configure a standby HSRP group to track an object and change the HSRP priority based on the object state, perform this task:
|
|
|
---|---|---|
|
||
|
(Optional) Creates a tracking list to track the configured state and enter tracking configuration mode.
The default up threshold is 254 and the default down threshold is 255.
– For boolean, see the “Configuring a Tracked List with a Boolean Expression” section. – For threshold weight, see the “Configuring a Tracked List with a Weight Threshold” section. – For threshold percentage, see the “Configuring a Tracked List with a Percentage Threshold” section. |
|
|
||
|
||
|
Creates (or enable) the HSRP group by using its number and virtual IP address.
|
|
|
Configures HSRP to track an object and change the hot standby priority based on the state of the object.
|
|
|
||
|
||
|
Configuring Other Tracking Characteristics
You can also use the enhanced object tracking for tracking other characteristics.
- You can track the reachability of an IP route by using the track ip route reachability global configuration command.
- You can use the track ip route metric threshold global configuration command to determine if a route is above or below threshold.
- You can use the track resolution global configuration command to change the metric resolution default values for routing protocols.
- You can use the track timer tracking configuration command to configure the tracking process to periodically poll tracked objects.
Use the show track privileged EXEC command to verify enhanced object tracking configuration.
Configuring IP SLAs Object Tracking
Cisco IOS IP Service Level Agreements (IP SLAs) is a network performance measurement and diagnostics tool that uses active monitoring by generating traffic to measure network performance. Cisco IP SLAs operations collects real-time metrics that you can use for network troubleshooting, design, and analysis.
For more information about Cisco IP SLAs on the switch, see Chapter78, “Configuring Cisco IOS IP SLA Operations” For IP SLAs command information see the Cisco IOS IP SLAs Command Reference, Release 12.4T.
Object tracking of IP SLAs operations allows clients to track the output from IP SLAs objects and use this information to trigger an action. Every IP SLAs operation maintains an SNMP operation return-code value, such as OK or OverThreshold, that can be interpreted by the tracking process. You can track two aspects of IP SLAs operation: state and reachability. For state, if the return code is OK, the track state is up; if the return code is not OK, the track state is down. For reachability, if the return code is OK or OverThreshold, reachability is up; if not OK, reachability is down.
To track the state of an IP SLAs operation or the reachability of an IP SLAs IP host, perform this task:
This example shows how to configure and display IP SLAs state tracking:
This example output shows whether a route is reachable:
Configuring Static Routing Support
Static routing support using enhanced object tracking provides the ability for the switch to use ICMP pings to identify when a preconfigured static route or a DHCP route goes down. When tracking is enabled, the system tracks the state of the route and informs the client when that state changes. Static route object tracking uses Cisco IP SLAs to generate ICMP pings to monitor the state of the connection to the primary gateway.
For more information about Cisco IP SLAs support on the switch, see Chapter78, “Configuring Cisco IOS IP SLA Operations”
- For more information about static route object tracking, see:
http://www.cisco.com/en/US/docs/ios/dial/configuration/guide/dia_rel_stc_rtg_bckup_support_TSD_Island_of_Content_Chapter.html
You use this process to configure static route object tracking:
Step 1 Configure a primary interface for static routing or for DHCP.ex
Step 2 Configure an IP SLAs agent to ping an IP address using a primary interface and a track object to monitor the state of the agent.
Step 3 Configure a default static default route using a secondary interface. This route is used only if the primary route is removed.
Configuring a Primary Interface
To configure a primary interface for static routing, perform this task:
To configure a primary interface for DHCP, perform this task:
Configuring a Cisco IP SLAs Monitoring Agent and Track Object
To configure network monitoring with Cisco IP SLAs, perform this task:
Configuring a Routing Policy and Default Route
- To configure a routing policy for backup static routing by using object tracking, perform the following task. For more details about the commands in the procedure, see:
http://www.cisco.com/en/US/docs/ios/dial/configuration/guide/dia_rel_stc_rtg_bckup_support_TSD_Island_of_Content_Chapter.html
For configuration examples, see:
http://www.cisco.com/en/US/tech/tk801/tk133/technologies_configuration_example09186a0080093f7e.shtml
Monitoring Enhanced Object Tracking
Use the privileged EXEC or user EXEC commands in Table 69-1 to display enhanced object tracking information.