[Contents] [Prev] [Next] [Index] [Report an Error]

Tracing MPLS and LSP Packets and Operations

To trace MPLS and LSP packets and operations, include the traceoptions statement:




traceoptions {
file filename <replace> <size size> <files number> <no-stamp>
<world-readable | no-world-readable>;
flag flag; 
}

For a list of hierarchy levels at which you can include this statement, see the statement summary section for this statement.

You can specify the following MPLS-specific flags in the MPLS traceoptions statement:

all—Trace all operations.
connection—Trace all circuit cross-connect (CCC) activity.
connection-detail—Trace detailed CCC activity.
cspf—Trace CSPF computations.
cspf-link—Trace links visited during CSPF computations.
cspf-node—Trace nodes visited during CSPF computations.
error—Trace MPLS error conditions.
graceful-restart—Trace MPLS graceful restart events.
lsping—Trace LSP ping packets and return codes.
state—Trace all LSP state transitions.

When you configure trace options to track an MPLS LSP using the cspf option, the CSPF log displays information about the MPLS LSP using the term “generalized MPLS” (GMPLS). For example, a message in the CSPF log might state that the “link passes GMPLS constraints”. Generalized MPLS (GMPLS) is a superset of MPLS, so this message is normal and does not affect proper MPLS LSP operation.

For general information about tracing and global tracing options, see the JUNOS Routing Protocols Configuration Guide.

[Contents] [Prev] [Next] [Index] [Report an Error]