Command introduced in Junos OS Release 9.0.
mep-id option introduced in Junos OS Release 9.1.
local-mep option introduced in Junos OS Release 15.1
Triggers the linktrace protocol to trace the route between two maintenance points. The result of the traceroute protocol is stored in the path database. To display the path database, use the show oam ethernet connectivity-fault-management path-database command.
Before using the traceroute command, you can verify the remote MEP’s MAC address using the show oam ethernet connectivity-fault-management path-database command.
Required Privilege Level
List of Sample Outputtraceroute ethernet
traceroute ethernet detail
Table 1 lists the output fields for the traceroute ethernet command. Output fields are listed in the approximate order in which they appear.
Table 1: traceroute ethernet Output Fields
MAC address of the destination maintenance point.
Local interface used to send the linktrace message (LTM).
Maintenance domain specified in the traceroute command.
Maintenance domain level configured.
Maintenance association specified in the traceroute command.
The local maintenance end point identifier.
4-byte identifier maintained by the MEP. Each LTM uses a transaction identifier. The transaction identifier is maintained globally across all Maintenance Domains. Use the transaction identifier to match an incoming linktrace response (LTR), with a previously sent LTM.
Sequential hop count of the linktrace path.
Number of hops remaining in the linktrace message. The time to live (TTL) is decremented at each hop.
Source MAC address
MAC address of the 802.1ag node responding to the LTM or
the source MAC address of the LTR.
Next-hop MAC address
MAC address of the egress interface of the node to which the LTM is forwarded or
the next-hop MAC address derived from the next egress identifier in the Egress-ID TLV of the LTR PDU.
The hostname of the responding router. A valid hostname is received only when the responding system is a Juniper Networks router.
Ingress port name
The port name for ingress connections.
Egress port name
The port name for egress connections.
The configurable flags can include:
The associated relay action. Relay action can be one of the following:
user@host> traceroute ethernet maintenance-domain md1 maintenance-association ma1 00:01:02:03:04:05
Linktrace to 00:01:02:03:04:05, Interface : ge-5/0/0.0 Maintenance Domain: MD1, Level: 7 Maintenance Association: MA1, Local Mep: 1 Hop TTL Source MAC address Next hop MAC address Transaction Identifier:100001 1 63 00:00:aa:aa:aa:aa 00:00:ab:ab:ab:ab 2 62 00:00:bb:bb:bb:bb 00:00:bc:bc:bc:bc 3 61 00:00:cc:cc:cc:cc 00:00:cd:cd:cd:cd 4 60 00:01:02:03:04:05 00:00:00:00:00:00
traceroute ethernet detail
user@host> run traceroute ethernet maintenance-domain md6 maintenance-association ma6 mep 101 detail
Linktrace to 00:00:5E:00:53:CC, Interface : ge-1/0/0.1 Maintenance Domain: md6, Level: 6 Maintenance Association: ma6, Local Mep: 201 Transaction Identifier: 2077547465 Legend for RelayAction: RlyHit -- Relay hit, Target MAC address matches the MP mac address RlyFDB -- Relay FDB, output port decided by consulting FDB database RlyMPDB -- Relay MIP, output port decided by consulting MIP database Legend for Flags: H -- Hardware only,incoming LT frame has hardware bit set T -- Terminal MEP, responder is a terminating MEP F -- FWD yes, LTM frame is relayed further TTL Responder Hostname Ingress port name Egress port name RelayAction Responder Service Ingress MAC address Egress MAC address Flags 62 host1 ge-1/0/0.1 ge-2/3/0.1 RlyFDB br1 00:00:5E:00:53:00 00:00:5E:00:53:A0 HF- 63 host2 ge-2/3/0.1 ge-1/0/0.1 RlyFDB br1 00:00:5E:00:53:AA 00:00:5E:00:53:A2 HF- 61 host3 ge-1/0/0.1 --:-- RlyHit br1 00:00:5E:00:53:B0 --:-- H-T