Configuring PIM Trace Options

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.

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.

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 each other.

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, first 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:

  1. (Optional) Configure tracing at the routing options level to trace all protocol packets.
    [edit]user@host# edit routing-options traceoptionsuser@host# set file all-packets-traceuser@host# set flag all
  2. Configure the filename for the PIM trace file.
    [edit]user@host# edit protocols pim traceoptionsuser@host# set file pim-trace
  3. (Optional) Configure the maximum number of trace files.
    [edit protocols pim traceoptions]user@host# set file files 5
  4. (Optional) Configure the maximum size of each trace file.
    [edit protocols pim traceoptions]user@host# set file size 1m
  5. (Optional) Enable unrestricted file access.
    [edit protocols pim traceoptions]user@host# set file world-readable
  6. Configure tracing flags. Suppose you are troubleshooting problems 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”
  7. View the trace file.
    user@host> file list /var/loguser@host> file show /var/log/pim-trace

Related Topics

Copyright© 1999-2010 Juniper Networks, Inc. All rights reserved.