traceroute ethernet

Syntax

Description

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.

Options

local-mep `mep-id`	(Required when multiple MEPs are configured) Identifier for the local maintenance endpoint.
detail	(Optional) Provide detailed information of the responder hostname, ingress port name, egress port name, TTL, and relay action.
mac-address	Destination unicast MAC address of the remote maintenance point.
`mep-id`	MEP identifier of the remote maintenance point. The range of values is 1 through 8191.
maintenance-association `ma-name`	Specifies an existing maintenance association from the set of configured maintenance associations.
maintenance-domain `md-name`	Specifies an existing maintenance domain from the set of configured maintenance domains.
ttl `value`	Number of hops to use in the linktrace request. The range is 1 to 255 hops. The default is 4.
wait `seconds`	(Optional) Maximum time to wait for a response to the traceroute request. The range is 1 to 255 seconds. The default is 5.

Required Privilege Level

network

Output Fields

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
Field Name	Field Description
`Linktrace to`	MAC address of the destination maintenance point.
`Interface`	Local interface used to send the linktrace message (LTM).
`Maintenance Domain`	Maintenance domain specified in the traceroute command.
`Level`	Maintenance domain level configured.
`Maintenance Association`	Maintenance association specified in the traceroute command.
`Local Mep`	The local maintenance end point identifier.
`Transaction 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.
`Hop`	Sequential hop count of the linktrace path.
`TTL`	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.
`Responder Hostname`	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.
`Flags`	The configurable flags can include: 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.
`Relay Action`	The associated relay action. Relay action can be one of the following: RlyHit— Relay hit; target MAC address matches the MP mac address. RlyFDB— Relay FDB; output port decided by consulting forwarding database. RlyMPDB— Relay MIP; output port decided by consulting MIP database.