3.2.16. tracker¶
Note
requires a Turbo Router Network License.
Track IP addresses.
vrouter running config# tracker
bfd¶
Configure a BFD tracker session.
vrouter running config# tracker bfd <bfd>
<bfd> |
An tracker name. |
type¶
Session type.
vrouter running config# tracker bfd <bfd>
vrouter running bfd <bfd># type TYPE
|
Description |
|---|---|
single-hop |
Single-hop session. |
multi-hop |
Multi-hop session. |
- Default value
single-hop
source¶
Local IP address.
vrouter running config# tracker bfd <bfd>
vrouter running bfd <bfd># source SOURCE
|
Description |
|---|---|
<A.B.C.D> |
An IPv4 address. |
<X:X::X:X> |
An IPv6 address. |
address (mandatory)¶
IP address of the peer.
vrouter running config# tracker bfd <bfd>
vrouter running bfd <bfd># address ADDRESS
|
Description |
|---|---|
<A.B.C.D> |
An IPv4 address. |
<X:X::X:X> |
An IPv6 address. |
interface¶
Interface to use to contact peer.
vrouter running config# tracker bfd <bfd>
vrouter running bfd <bfd># interface INTERFACE
INTERFACE |
An interface name. |
vrf (mandatory)¶
VRF name.
vrouter running config# tracker bfd <bfd>
vrouter running bfd <bfd># vrf VRF
|
Description |
|---|---|
main |
The main vrf. |
<string> |
The vrf name. |
echo-mode¶
Use echo packets to detect failures.
vrouter running config# tracker bfd <bfd>
vrouter running bfd <bfd># echo-mode true|false
detection-multiplier¶
Local session detection multiplier.
vrouter running config# tracker bfd <bfd>
vrouter running bfd <bfd># detection-multiplier <uint8>
- Default value
3
desired-transmission-interval¶
Minimum desired control packet transmission interval.
vrouter running config# tracker bfd <bfd>
vrouter running bfd <bfd># desired-transmission-interval <uint32>
- Default value
300000
required-receive-interval¶
Minimum required control packet receive interval (use disable to not receive any control packet).
vrouter running config# tracker bfd <bfd>
vrouter running bfd <bfd># required-receive-interval REQUIRED-RECEIVE-INTERVAL
|
Description |
|---|---|
<uint32> |
No description. |
disable |
Ths system will not receive any periodic BFD control packets. |
- Default value
300000
desired-echo-transmission-interval¶
Minimum desired control packet transmission interval.
vrouter running config# tracker bfd <bfd>
vrouter running bfd <bfd># desired-echo-transmission-interval <uint32>
discriminator (state only)¶
Local session identifier.
vrouter> show state tracker bfd <bfd> discriminator
last-down-time (state only)¶
Time and date of the last time session was down (in seconds).
vrouter> show state tracker bfd <bfd> last-down-time
last-up-time (state only)¶
Time and date of the last time session was up (in seconds).
vrouter> show state tracker bfd <bfd> last-up-time
session-down-count (state only)¶
Amount of time the session went down.
vrouter> show state tracker bfd <bfd> session-down-count
session-up-count (state only)¶
Amount of time the session went up.
vrouter> show state tracker bfd <bfd> session-up-count
control-packet-input-count (state only)¶
Amount of control packets received.
vrouter> show state tracker bfd <bfd> control-packet-input-count
control-packet-output-count (state only)¶
Amount of control packets sent.
vrouter> show state tracker bfd <bfd> control-packet-output-count
echo-packet-input-count (state only)¶
Amount of echo packets received.
vrouter> show state tracker bfd <bfd> echo-packet-input-count
echo-packet-output-count (state only)¶
Amount of echo packets sent.
vrouter> show state tracker bfd <bfd> echo-packet-output-count
zebra-notification-count (state only)¶
Amount of zebra notifications.
vrouter> show state tracker bfd <bfd> zebra-notification-count
remote (state only)¶
BFD remote operational state data.
discriminator (state only)¶
Remote session identifier.
vrouter> show state tracker bfd <bfd> remote discriminator
diagnostic (state only)¶
Local session diagnostic.
vrouter> show state tracker bfd <bfd> remote diagnostic
multiplier (state only)¶
Remote session detection multiplier.
vrouter> show state tracker bfd <bfd> remote multiplier
negociated (state only)¶
BFD negociated operational state data.
transmission-interval (state only)¶
Negotiated transmit interval.
vrouter> show state tracker bfd <bfd> negociated transmission-interval
receive-interval (state only)¶
Negotiated receive interval.
vrouter> show state tracker bfd <bfd> negociated receive-interval
echo-transmission-interval (state only)¶
Negotiated echo transmit interval.
vrouter> show state tracker bfd <bfd> negociated echo-transmission-interval
icmp¶
Note
requires a Turbo Router Network License.
List of tracked addresses using ICMP echo requests.
vrouter running config# tracker
vrouter running tracker# icmp <icmp> address ADDRESS vrf VRF source SOURCE \
... interface INTERFACE dhcp-interface DHCP-INTERFACE gateway GATEWAY period <uint16> \
... threshold <uint8> total <uint8> packet-size <uint16> packet-tos <uint8> timeout <uint16>
<icmp> |
An tracker name. |
address¶
The host to track.
address ADDRESS
|
Description |
|---|---|
<A.B.C.D> |
An IPv4 address. |
<X:X::X:X> |
An IPv6 address. |
<host-name> |
The domain-name type represents a DNS domain name. Fully quallified left to the models which utilize this type. Internet domain names are only loosely specified. Section 3.5 of RFC 1034 recommends a syntax (modified in Section 2.1 of RFC 1123). The pattern above is intended to allow for current practice in domain name use, and some possible future expansion. It is designed to hold various types of domain names, including names used for A or AAAA records (host names) and other records, such as SRV records. Note that Internet host names have a stricter syntax (described in RFC 952) than the DNS recommendations in RFCs 1034 and 1123, and that systems that want to store host names in schema nodes using the domain-name type are recommended to adhere to this stricter standard to ensure interoperability. The encoding of DNS names in the DNS protocol is limited to 255 characters. Since the encoding consists of labels prefixed by a length bytes and there is a trailing NULL byte, only 253 characters can appear in the textual dotted notation. Domain-name values use the US-ASCII encoding. Their canonical format uses lowercase US-ASCII characters. Internationalized domain names MUST be encoded in punycode as described in RFC 3492. |
vrf (mandatory)¶
The vrf in which the ping must be sent. Default is the current netns.
vrf VRF
|
Description |
|---|---|
main |
The main vrf. |
<string> |
The vrf name. |
source¶
Source address in the ping packet.
source SOURCE
|
Description |
|---|---|
<A.B.C.D> |
An IPv4 address. |
<X:X::X:X> |
An IPv6 address. |
dhcp-interface¶
The address, gateway and source will be taken from DHCP on this interface unless explicitly specified in the tracker.
dhcp-interface DHCP-INTERFACE
DHCP-INTERFACE |
An interface name. |
gateway¶
The gateway to use to send the packet.
gateway GATEWAY
|
Description |
|---|---|
<A.B.C.D> |
An IPv4 address. |
<X:X::X:X> |
An IPv6 address. |
<host-name> |
The domain-name type represents a DNS domain name. Fully quallified left to the models which utilize this type. Internet domain names are only loosely specified. Section 3.5 of RFC 1034 recommends a syntax (modified in Section 2.1 of RFC 1123). The pattern above is intended to allow for current practice in domain name use, and some possible future expansion. It is designed to hold various types of domain names, including names used for A or AAAA records (host names) and other records, such as SRV records. Note that Internet host names have a stricter syntax (described in RFC 952) than the DNS recommendations in RFCs 1034 and 1123, and that systems that want to store host names in schema nodes using the domain-name type are recommended to adhere to this stricter standard to ensure interoperability. The encoding of DNS names in the DNS protocol is limited to 255 characters. Since the encoding consists of labels prefixed by a length bytes and there is a trailing NULL byte, only 253 characters can appear in the textual dotted notation. Domain-name values use the US-ASCII encoding. Their canonical format uses lowercase US-ASCII characters. Internationalized domain names MUST be encoded in punycode as described in RFC 3492. |
threshold¶
Number of successful pings among <total> to consider peer as reachable.
threshold <uint8>
- Default value
1
total¶
Check the threshold among this number of last pings to consider peer as reachable.
total <uint8>
- Default value
1
timeout¶
Time during which a ping reply is considered as valid. If unset, it timeouts after a ping period.
timeout <uint16>
diagnostic (state only)¶
Local session diagnostic.
vrouter> show state tracker icmp <icmp> diagnostic