
3.
(Optional) Identify the tracked object with a text description.
OBJECT TRACKING mode
description
text
The text string can be up to 80 characters.
4.
(Optional) Display the tracking configuration and the tracked object’s status.
EXEC Privilege mode
show track
object-id
Example of Configuring Object Tracking
Dell(conf)#track 100 interface tengigabitethernet 7/1 line-protocol
Dell(conf-track-100)#delay up 20
Dell(conf-track-100)#description San Jose data center
Dell(conf-track-100)#end
Dell#show track 100
Track 100
Interface TenGigabitEthernet 7/1 line-protocol
Description: San Jose data center
Tracking a Layer 3 Interface
You can create an object that tracks the routing status of an IPv4 or IPv6 Layer 3 interface.
You can track the routing status of any of the following Layer 3 interfaces:
•
For a 10-Gigabit Ethernet interface, enter the keyword
TenGigabitEthernet
then the slot/port[/subport] information.
•
For a port channel interface, enter the keywords
port-channel
then a number.
•
For a VLAN interface, enter the keyword
vlan
then a number from 1 to 4094.
For an IPv4 interface, a routing object only tracks the UP/DOWN status of the specified IPv4 interface (the
track interface
ip-routing
command).
•
The status of an IPv4 interface is UP only if the Layer 2 status of the interface is UP and the interface has a valid IP address.
•
The Layer 3 status of an IPv4 interface goes DOWN when its Layer 2 status goes down (for a Layer 3 VLAN, all VLAN ports
must be down) or the IP address is removed from the routing table.
For an IPv6 interface, a routing object only tracks the UP/DOWN status of the specified IPv6 interface (the
track interface
ipv6-routing
command).
•
The status of an IPv6 interface is UP only if the Layer 2 status of the interface is UP and the interface has a valid IPv6 address.
•
The Layer 3 status of an IPv6 interface goes DOWN when its Layer 2 status goes down (for a Layer 3 VLAN, all VLAN ports
must be down) or the IPv6 address is removed from the routing table.
To remove object tracking on a Layer 3 IPv4/IPv6 interface, use the
no track object-id
command.
To configure object tracking on the routing status of a Layer 3 interface, use the following commands.
1.
Configure object tracking on the routing status of an IPv4 or IPv6 interface.
CONFIGURATION mode
track
object-id
interface
interface
{ip routing | ipv6 routing}
Valid object IDs are from 1 to 65535.
2.
(Optional) Configure the time delay used before communicating a change in the status of a tracked interface.
OBJECT TRACKING mode
delay {[up
seconds
] [down
seconds
]}
Object Tracking
569
Содержание S4048-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 9 0 0 ...
Страница 146: ...Figure 14 BFD Three Way Handshake State Changes 146 Bidirectional Forwarding Detection BFD ...
Страница 477: ...Figure 68 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 477 ...
Страница 480: ...Figure 70 Inspecting a LAG Port on BRAVO Using the show interface Command 480 Link Aggregation Control Protocol LACP ...
Страница 481: ...Figure 71 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 481 ...
Страница 522: ...Figure 87 Configuring Interfaces for MSDP 522 Multicast Source Discovery Protocol MSDP ...
Страница 523: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 523 ...
Страница 524: ...Figure 89 Configuring PIM in Multiple Routing Domains 524 Multicast Source Discovery Protocol MSDP ...
Страница 528: ...Figure 91 MSDP Default Peer Scenario 1 528 Multicast Source Discovery Protocol MSDP ...
Страница 529: ...Figure 92 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 529 ...
Страница 530: ...Figure 93 MSDP Default Peer Scenario 3 530 Multicast Source Discovery Protocol MSDP ...
Страница 633: ...Policy based Routing PBR 633 ...
Страница 777: ...Figure 119 Single and Double Tag TPID Match Service Provider Bridging 777 ...
Страница 778: ...Figure 120 Single and Double Tag First byte TPID Match 778 Service Provider Bridging ...