
If you do not configure a delay, a notification is sent when a change in the state of a tracked object is detected. The time delay in
communicating a state change is specified in seconds.
VRRP Object Tracking
As a client, VRRP can track up to 20 objects (including route entries, and Layer 2 and Layer 3 interfaces) in addition to the 12
tracked interfaces supported for each VRRP group.
You can assign a unique priority-cost value from 1 to 254 to each tracked VRRP object or group interface. The priority cost is
subtracted from the VRRP group priority if a tracked VRRP object is in a DOWN state. If a VRRP group router acts as owner-master,
the run-time VRRP group priority remains fixed at 255 and changes in the state of a tracked object have no effect.
NOTE: In VRRP object tracking, the sum of the priority costs for all tracked objects and interfaces cannot equal or
exceed the priority of the VRRP group.
Object Tracking Configuration
You can configure three types of object tracking for a client.
•
•
•
For a complete listing of all commands related to object tracking, refer to the
Dell Networking OS Command Line Interface
Reference Guide
.
Tracking a Layer 2 Interface
You can create an object that tracks the line-protocol state of a Layer 2 interface and monitors its operational status (UP or DOWN).
You can track the status of any of the following Layer 2 interfaces:
•
1 Gigabit Ethernet: Enter
gigabitethernet
slot/port
in the
track interface
interface
command (see Step 1).
•
10 Gigabit Ethernet: Enter
tengigabitethernet
slot/port
.
•
Port channel: Enter
port-channel
number
, where valid port-channel numbers are from 1 to 128:
•
SONET: Enter
sonet
slot/port
.
•
VLAN: Enter
vlan
vlan-id
, where valid VLAN IDs are from 1 to 4094
A line-protocol object only tracks the link-level (UP/DOWN) status of a specified interface. When the link-level status goes down,
the tracked object status is DOWN; if the link-level status is up, the tracked object status is UP.
To remove object tracking on a Layer 2 interface, use the
no track
object-id
command.
To configure object tracking on the status of a Layer 2 interface, use the following commands.
1.
Configure object tracking on the line-protocol state of a Layer 2 interface.
CONFIGURATION mode
track
object-id
interface
interface
line-protocol
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
]}
Valid delay times are from 0 to 180 seconds.
The default is
0
.
568
Object Tracking
Содержание 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 ...