user@host# set file all-packets-trace
user@host# set flag all
2. Configure the filename for the PIM trace file.
[edit protocols pim traceoptions]
user@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 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”
7. View the trace file.
user@host> file list /var/log
user@host> file show /var/log/pim-trace
Related
Documentation
PIM Overview on page 672•
• Tracing and Logging Junos OS Operations
Disabling PIM
By default, when you enable the PIM protocol it applies to the specified interface only.
To enable PIM for all interfaces, include the all parameter (for example, set protocol pim
interface all). You can disable PIM at the protocol, interface, or family hierarchy levels.
The hierarchy in which you configure PIM is critical. In general, the most specific
configuration takes precedence. However, if PIM is disabled at the protocol level, then
any disable statements with respect to an interface or family are ignored.
687Copyright © 2017, Juniper Networks, Inc.
Chapter 22: Configuring Multicast Listener Discovery and Protocol-Independent Multicast
To Next Page
Loading...
Need help?
General
