Configuring PIM Trace Options

date_range 23-Nov-23

arrow_backward

arrow_forward

Tracing operations record detailed messages about the operation of routing protocols, such as the various types of routing protocol packets sent and received, and routing policy actions. You can specify which trace operations are logged by including specific tracing flags. The following table describes the flags that you can include.

Table 1: Flags to configure PIM trace options
Flag	Description
all	Trace all operations.
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.
autorp	Trace bootstrap, RP, and auto-RP messages.
bidirectional-df-election	Trace bidirectional PIM designated-forwarder (DF) election events.
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.
general	Trace general events.
graft	Trace graft and graft acknowledgment messages.
hello	Trace hello packets, which are sent so that neighboring routers can discover one another.
join	Trace join messages, which are sent to join a branch onto the multicast distribution tree.
mdt	Trace messages related to multicast data tunnels.
normal	Trace normal events.
nsr-synchronization	Trace nonstop routing synchronization events
packets	Trace all PIM packets.
policy	Trace poison-route-reverse 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.
route	Trace routing information.
rp	Trace candidate RP advertisements.
state	Trace state transitions.
task	Trace task processing.
timer	Trace timer processing.

In the following example, tracing is enabled for all routing protocol packets. Then tracing is narrowed to focus only on PIM packets of a particular type.

To configure tracing operations for PIM:

(Optional) Configure tracing at the [routing-options hierarchy level to trace all protocol packets.
```
[edit routing-options traceoptions]
user@host# set file all-packets-trace
user@host# set flag all
```
Configure the filename for the PIM trace file.
```
[edit protocols pim traceoptions]
user@host# set file pim-trace
```
(Optional) Configure the maximum number of trace files.
```
[edit protocols pim traceoptions]
user@host# set file files 5
```
(Optional) Configure the maximum size of each trace file.
```
[edit protocols pim traceoptions]
user@host# set file size 1m
```

(Optional) Enable unrestricted file access.

[edit protocols pim traceoptions]
user@host# set file world-readable

Configure tracing flags. Suppose you are troubleshooting issues with PIM version 1 control packets that are received on an interface configured for PIM version 2. The following example shows how to trace messages associated with this problem.
```
[edit protocols pim traceoptions]
user@host# set flag packets | match “Rx V1 Require V2”
```

View the trace file.

content_copy zoom_out_map
user@host> file list /var/log
user@host> file show /var/log/pim-trace

arrow_backward PREVIOUS Preserving Multicast Performance by Disabling Response to the ping Utility

NEXT arrow_forward Configuring BFD for PIM

Multicast Protocols User Guide

Configuring PIM Trace Options

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

Multicast Protocols User Guide

Configuring PIM Trace Options

Related Documentation

Stay in touch