Adjusting the Interval for Sending PIM Trap Messages
Context
After Protocol Independent Multicast (PIM) is enabled on a switch, you can set the PIM-MIB notification interval to determine the interval at which PIM events are reported. In this way, you can monitor various PIM events on the switch, including neighbor loss, presence of new neighbors, invalid Join/Prune messages received, RP-mapping changes, DR elected on an interface, failures to join multicast groups because the number of PIM entries reaches the limit, and invalid Register messages received.
Perform the following steps on the switch managed by the network management system.
Procedure
- Run system-view
The system view is displayed.
- Run multicast-mib
The multicast MIB view is displayed.
- Run pim mib-notification interval { interface-election-dr election-value | invalid-join-prune jp-value | invalid-register register-value | neighbor-loss loss-value | new-neighbor new-value | rp-mapping-change change-value | mrt-limit mrt-value }
The interval for sending PIM trap messages is set.
By default, the interval for sending trap messages about neighbor loss and new neighbor presence events is 0 seconds. That is, a trap message is sent immediately when such an event occurs.
The default interval for sending trap messages about invalid Join/Prune messages, RP-mapping changes, DR elected on an interface, failures to join multicast groups because the number of PIM entries reaches the limit, and invalid Register messages is 65535 seconds. That is, no trap messages are sent when these events occur.
To configure PIM to report these events, run the pim mib-notification interval command to set an interval smaller than 65535 seconds.