300-415 · Question #192
Which two sets of identifiers OMP carry when it advertises TLOC routes between WAN Edge routers? (Choose two.)
The correct answer is A. TLOC public and private address, carrier, and preference. OMP carries specific sets of identifiers in TLOC routes between WAN Edge routers, detailing tunnel endpoints and link characteristics.
Question
Options
- ATLOC public and private address, carrier, and preference
- Bsource and destination IP address, MAC, and site ID
- Csystem IP address, link color, and encapsulation
- DVPN ID, local site, network, and BGP next-hop IP address
- ETLOC public and private address, tunnel ID, and performance
How the community answered
(49 responses)- A92% (45)
- C2% (1)
- D4% (2)
- E2% (1)
Why each option
OMP carries specific sets of identifiers in TLOC routes between WAN Edge routers, detailing tunnel endpoints and link characteristics.
TLOC routes carry the TLOC public and private IP addresses, which are the endpoints for the data plane tunnels, along with the carrier (e.g., MPLS, Public Internet) and a preference value. This information is crucial for remote WAN Edge routers to establish tunnels and for vSmart to make informed path selection decisions.
Source and destination IP addresses and MAC addresses are attributes of data plane packets, not routing updates for TLOCs, although site ID is used in OMP routes.
VPN ID, local site, network, and BGP next-hop IP address are attributes primarily associated with OMP service routes (vRoutes), which describe prefixes reachable through a WAN Edge, rather than the TLOC routes themselves.
While TLOC public and private addresses are correct, 'tunnel ID' is not a standard distinct OMP attribute in this context, and 'performance' is a dynamically derived metric rather than a static identifier carried directly within the TLOC route.
Concept tested: OMP TLOC route attributes
Source: https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/sdwan-xe-gs-book/m-sdwan-config.html#C_ID_5757F3A5_00
Topics
Community Discussion
No community discussion yet for this question.