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

Configuring PIM Trace Options

To trace PIM protocol traffic, you can specify options in the global traceoptions statement at the [edit routing-options] or [edit logical-systems logical-system-name routing-options] hierarchy level. Options applied at the routing options level trace all packets, and options applied at the protocol level trace only IGMP traffic.




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

You can configure PIM-specific options by including the traceoptions statement at the PIM hierarchy level. For a list of the hierarchy levels at which you can configure this statement, see the statement summary section for this statement.

You can specify the following PIM-specific options in the traceoptions statement:

assert—Trace assert messages, which are used to resolve which of the parallel routers connected to a multiaccess LAN is responsible for forwarding packets to the LAN.
bootstrap—Trace bootstrap messages, which are sent periodically by the PIM domain's bootstrap router and are forwarded, hop by hop, to all routers in that domain.
cache—Trace the packets in the PIM routing cache.
graft—Trace graft and graft acknowledgment messages.
hello—Trace hello packets, which are sent so that neighboring routers can discover each other.
join—Trace join messages, which are sent to join a branch onto the multicast distribution tree.
packets—Trace all PIM packets.
prune—Trace prune messages, which are sent to prune a branch off the multicast distribution tree.
register—Trace register and register-stop messages. Register messages are sent to the RP when a multicast source first starts sending to a group.
rp—Trace candidate RP advertisements.

For general information about tracing, see the JUNOS System Basics Configuration Guide. For a PIM tracing example, see Example: Tracing PIM Protocol Traffic.

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