This command displays PIM anycast rp-set information.
The following output displays an example of a PIM anycast configuration.
Table 17 provides PIM anycast field descriptions
Label | Description |
Anycast Address | Displays the candidate anycast address. |
Anycast RP Peer | Displays the candidate anycast RP peer address. |
This command displays PIM candidate RP (CRP) information received at the elected Bootstrap router (BSR).
The following output is an example of a PIM CRP configuration.
Table 18 provides PIM CRP field descriptions.
Label | Description |
RP Address | The Candidate RP address |
Group Address | The range of multicast group addresses for which the CRP is the Candidate RP |
Priority | The Candidate RP's priority for becoming a rendezvous point (RP). This value is used to elect RP for a group range. A value of 0 is considered as the highest priority. |
Holdtime | The hold time of the candidate RP. It is used by the Bootstrap router to time out the RP entries if it does not listen to another CRP advertisement within the holdtime period. |
Expiry | The minimum time remaining before the CRP will be declared down. If the local router is not the BSR, this value is 0. |
Candidate RPs | The number of CRP entries. |
This command displays extranet interface information.
This command displays PIM source group database information.
The following displays an example of PIM group information. Table 19 provides PIM group field descriptions.
Label | Description |
Group Address | The IP multicast group address for which this entry contains information |
Source Address | The source address of the multicast sender. The value is 0 if the type is configured as starg. The address of the Rendezvous Point (RP) display when the type is configured as starRP. |
RP Address | The RP address |
Type | The type of entry, (*,*, rp)/(*,G) or (S,G). |
Spt Bit | Specifies whether to forward on (*,*, rp)/(*,G) or on (S,G) state. It is updated when the (S,G) data comes on the RPF interface towards the source. |
Incoming Intf | The interface on which the traffic comes in. It can be the RPF interface to the RP (if starg) or the source (if sg). |
Num Oifs | The number of interfaces in the inherited outgoing interface list. An inherited list inherits the state from other types. |
Flags | The different lists to which this interface belongs |
Keepalive Timer Exp | The keepalive timer expiration which is applicable only for (S,G) entries. The (S,G) keepalive timer is updated by data being forwarded using this (S,G) Forwarding state. It is used to keep (S,G) state alive in the absence of explicit (S,G) joins. |
MRIB Next Hop | The next hop address towards the RP |
MRIB Src Flags | MRIB information about the source. If the entry is of type starg or starstarrp, it will contain information about the RP for the group. |
Up Time | The time since this source group entry was created. |
Resolved By | The route table used for RPF check. |
Up JP State | The upstream join prune state for this entry on the interface. PIM join prune messages are sent by the downstream routers towards the RPF neighbor. |
Up JP Expiry | The minimum amount of time remaining before this entry will be aged out. |
Up JP Rpt | The join prune Rpt state for this entry on the interface. PIM join/prune messages are sent by the downstream routers towards the RPF neighbor. (S,G, rpt) state is a result of receiving (S,G, rpt) JP message from the downstream router on the RP tree. |
Up JP Rpt Override | The value used to delay triggered Join (S,G, rpt) messages to prevent implosions of triggered messages. If this has a non-zero value, it means that the router was in 'notPruned' state and it saw a prune (S,G, rpt) message being sent to RPF (S,G, rpt). If the router sees a join (S,G, rpt) override message being sent by some other router on the LAN while the timer is still non-zero, it simply cancels the override timer. If it does not see a join (S,G, rpt) message, then on expiry of the override timer, it sends its own join (S,G, rpt) message to RPF (S,G, rpt). A similar scenario exists when RPF (S,G, rpt) changes to become equal to RPF (*,G). |
Register State | The register state. The register state is kept at the source DR. When the host starts sending multicast packets and if there are no entries programmed for that group, the source DR sends a register packet to the RP (g). Register state transition happen based on the register stop timer and the response received from the RP. |
Register Stop Exp | The time remaining before the register state might transition to a different state |
Register from Anycast RP | The status of the register packet for that group received from one of the RP from the anycast-RP set |
RPF Neighbor | The address of the RPF neighbor |
Outgoing Intf List | A list of interfaces on which data is forwarded. |
Curr Fwding Rate | The current forwarding rate of the multicast data for this group and source. This forwarding rate is calculated before ingress QoS policing or shaping is applied. |
Forwarded Packets | The number of multicast packets that were forwarded to the interfaces in the outgoing interface list. This packet count is before ingress QoS policing or shaping is applied. |
Discarded Packets | The number of multicast packets that matched this source group entry but were discarded. For (S,G) entries, if the traffic is getting forwarded on the SPT, the packets arriving from the RPT will be discarded. |
Forwarded Octets | The number of octets forwarded |
RPF Mismatches | The number of multicast packets that matched this source group entry but they did not arrive on the interface. |
Spt threshold | The value of the SPT threshold configured for that group. 0 kb/s means that the switch to the SP tree occurs immediately. |
This command displays PIM interface information and the (S,G)/(*,G)/(*, *, rp) state of the interface.
If the type is starg, the value of this object is zero.
If the type is starstarrp, the value of this object is the address of the RP.
The following is an example of a PIM interface configuration. Table 20 provides PIM interface field descriptions.
Label | Description |
Admin State | The administrative state for PIM protocol on this interface |
Oper State | The current operational state of PIM protocol on this interface |
DR | The designated router on this PIM interface |
DR Priority | The priority value sent in PIM Hello messages and that is used by routers to elect the designated router (DR). |
Hello Intvl | The frequency at which PIM Hello messages are transmitted on this interface |
OperGroup | The OperGroup name associated with the PIM interface |
OprGrp Active oper | The OperGroup operation (add, set, subtract) to the DR priority |
Cfg OprGrp Priority | The configured OperGroup DR priority |
This command shows multicast balance information.
This command displays PIM neighbor information. This can be important if an interface has more than one adjacency. For example, a LAN-interface configuration with three routers connected and all are running PIM on their LAN interfaces. These routers then have two adjacencies on their LAN interface, each with different neighbors. If the address ip-address parameter is not defined in this example, then the show command output would display two adjacencies.
The following output is an example of a PIM neighbor configuration. Table 21 provides PIM neighbor field descriptions.
Label | Description |
Interface | The neighbor’s interface name. (W) indicates wildcard tunnels. |
Nbr DR Priority | The value of the neighbor's DR priority which is received in the hello message. |
Nbr Address | The neighbor’s address. |
Up Time | The time since this PIM neighbor (last) became a neighbor of the local router |
Expiry Time | The minimum time remaining before this PIM neighbor is aged out 0 — Means that this neighbor never ages out. This happens when the PIM neighbor sends a Hello message with holdtime set to `0xffff'. |
Hold Time | The value of the hold time present in the hello message |
DR Priority | The value of the neighbor's DR priority which is received in the hello message |
Tracking Support | Indicates if the T bit in the LAN prune delay option was present in the hello message. This indicates the neighbor's capability to disable join message suppression. |
LAN Delay | The value of the LAN delay field present in the hello message received from the neighbor |
Gen Id | A randomly generated 32-bit value that is regenerated each time PIM forwarding is started or restarted on the interface, including when the router itself restarts. When a hello message with a new GenID is received from a neighbor, any old hello information about that neighbor is discarded and superseded by the information from the new hello message. |
Override Intvl (ms) | The value of the override interval present in the Hello message |
This command displays the rendezvous point (RP) set information built by the router.
The following is an example of a PIM RP configuration.
Label | Description |
Group Address | The multicast group address of the entry. |
RP Address | The address of the Rendezvous Point (RP) |
Type | Displays whether the entry was learned through the Bootstrap mechanism or if it was statically configured. |
Priority | The priority for the specified group address. The higher the value, the higher the priority. |
Holdtime | The value of the hold time present in the BSM message |
This command hashes the RP for the specified group from the RP set.
The following is an example of a PIM RP-Hash configuration. Table 23 provides RP-Hash output field descriptions.
Label | Description |
Group Address | The multicast group address of the entry |
RP Address | The address of the Rendezvous Point (RP) |
Type | Specifies whether the entry was learned through the Bootstrap mechanism or if it was statically configured. |
This command displays information about selective provider multicast service interfaces that are currently active.
The following is an example of a PIM data MDT configuration. Table 24 provides PIM data MDT descriptions.
Label | Description |
MD Grp Address | The IP multicast group address for which this entry contains information |
MD Src Address | The source address of the multicast sender. The value is 0 if the type is configured as starg. The address of the Rendezvous Point (RP) displays if the type is configured as starRP. |
MT Index | The index number |
Num VP SGs | The VPN number |
This command displays statistics for a particular PIM instance.
Syntax: vprn-id-mt-grp-ip-address
Syntax: mpls-if-index
The following is an example of PIM statistics information. Table 25 provides PIM statistics output field descriptions
Label | Description |
PIM Statistics | The section listing the PIM statistics for a particular interface |
Message Type | The type of message. Hello — The number of PIM hello messages received or transmitted Join Prune — The number of PIM join prune messages received or transmitted Asserts — The number of PIM assert messages received or transmitted Register — The number of register messages received or transmitted Null Register — The number of PIM null register messages received or transmitted Register Stop — The number of PIM register stop messages received or transmitted BSM — The number of PIM Bootstrap messages (BSM) received or transmitted Candidate RP Adv — The number of candidate RP advertisements Auto-RP Announce — The number of auto-RP announce (224.0.1.39) messages received or transmitted Auto-RP Mapping — The number of auto-RP mapping (224.0.1.40) messages received or transmitted |
Message Type | PIM DM Grafts — The number of PIM graft messages received or transmitted PIM DM Graft Acks — The number of PIM graft acknowledgment messages received or transmitted Total Packets — The total number of packets transmitted and received. |
Received | The number of messages received |
Transmitted | The number of multicast data packets transmitted |
Rx Errors | The total number of receive errors |
General Interface Statistics | The section listing the general PIM interface statistics |
Register TTL Drop | The number of multicast data packets which could not be encapsulated in Register messages because the time to live (TTL) was zero |
Tx Register MTU Drop | The number of Bootstrap messages received on this interface but were dropped |
Rx Invalid Register | The number of invalid PIM register messages received |
Rx Neighbor Unknown | The number of PIM messages (other than hello messages) which were received and were rejected because the adjacency with the neighbor router was not already established |
Rx Bad Checksum Discard | The number of PIM messages received, and which were discarded because of bad checksum |
Rx Bad Encoding | The number of PIM messages with bad encodings received |
Rx Bad Version Discard | The number of PIM messages with bad versions received |
Rx CRP No Router Alert | The number of candidate-rp advertisements (C-RP-Adv) received, and which had no router alert option set |
Rx Invalid Join Prune | The number of invalid PIM join prune messages received |
Rx Unknown PDU Type | The number of packets received with an unsupported PIM type |
Join Policy Drops | The number of times the join policy match resulted in dropping PIM join-prune message or one of the source group contained in the message |
Register Policy Drops | The number of times the register policy match resulted in dropping PIM register message |
Bootstrap Import Policy Drops | The number of Bootstrap messages received that were dropped because of Bootstrap import policy |
Bootstrap Export Policy Drops | The number of Bootstrap messages that were not transmitted because of Bootstrap export policy. |
Source Group Statistics | The section listing the source group statistics |
(S,G) | The number of entries in which the type is (S,G) |
(*,G) | The number of entries in which the type is (*,G) |
(*,*,RP) | The number of entries in which the type is (*, *, rp) |
This command displays PIM status. The Oper Status reflects the combined operational status of IPv4 or IPv6 PIM protocol status. If both are down, then Oper Status is reflected as down. If IPv4 or IPv6 reflects up, the Oper Status reflects up.
If PIM is not enabled, the following message appears:
The following displays an example of a PIM status configuration. Table 26 provides PIM status output field descriptions.
Label | Description |
Admin State | The administrative status of PIM. |
Oper State | The current operating state of this PIM protocol instance. |
BSR State | The state of the router with respect to the Bootstrap mechanism. |
Address | The address of the elected Bootstrap router. |
Expiry Time | The time remaining before the router sends the next Bootstrap message. |
Priority | The priority of the elected Bootstrap router. The higher the value, the higher the priority. |
Hash Mask Length | The hash mask length of the Bootstrap router. |
Up Time | The time since the current E-BSR became the Bootstrap router. |
RPF Intf towards | The RPF interface towards the elected BSR. The value is zero if there is no elected BSR in the network. |
Address | The address of the candidate BSR OS. |
Expiry Time | The time remaining before the router sends the next Bootstrap message. |
Auto-RP | Displays if auto-RP functionality is enabled or disabled. |
Priority | The priority of the Bootstrap router. The higher the value, the higher the priority. |
Hash Mask Length | The hash mask length of the candidate Bootstrap router. |
Up Time | The time since becoming the Bootstrap router. |
Admin State | The administrative status of CRP. |
Oper State | The current operating state of the C-RP mechanism. |
Address | The local RP address. |
Priority | The CRP's priority for becoming a rendezvous point (RP). A 0 value is the highest priority. |
Holdtime | The hold time of the candidate RP. It is used by the Bootstrap router to time out the RP entries if it does not listen to another CRP advertisement within the holdtime period. |
Policy | The PIM policies for a particular PIM instance. |
Default Group | The default core group address. |
RPF Table | The route table used for RPF check. |
MC-ECMP-Hashing | Displays whether hash-based multicast balancing of traffic over ECMP links is enabled or disabled. |
SSM S,G Scaling (up to 256K) | The status of PIM SSM scaling. |
This command displays PIM tunnel interface information.
The following is an example of PIM tunnel interface information.
This command displays the list of multicast VPNs.
The following is an example of router MVPN list information.
This command clears IGMP or PIM database statistics on a specified interface or IP address.
Syntax: vprn-id-mt-grp-ip-address
Syntax: mpls-if-index
This command clears PIM selective provider multicast service interface cache.
This command clears PIM statistics on a specified interface or IP address.
![]() | Note: An interface and group or source cannot be specified at the same time. |
syntax: vprn-id-mt-grp-ip-address
This command clears PIM neighbor data on a specified interface or IP address.
This command enables debugging for PIM adjacencies.
The no form of this command disables debugging for PIM adjacencies.
This command enables debugging for all the PIM modules.
The no form of this command disables debugging PIM modules.
This command enables debugging for PIM assert mechanism.
The no form of this command disables PIM assert debugging.
This command enables debugging for PIM auto-RP.
The no form of this command disables PIM auto-RP debugging.
This command enables debugging for PIM/BGP-specific interoperation.
The no form of this command disables debugging for PIM/BGP-specific interoperation.
This command enables debugging for bier inband.
The no form of this command disables debugging for bier inband.
This command enables/disables debugging for the PIM bootstrap mechanism.
The no form of the command disables debugging.
This command enables debugging for PIM data exception.
The no form of this command disables PIM data exception debugging.
This command enables debugging for PIM database.
The no form of this command disables PIM database debugging.
This command enables debugging for dynamic MLDP.
The no form of this command disables dynamic MLDP debugging.
This command enables debugging for extranet PIM.
The no form of this command disables PIM extranet debugging.
This command enables debugging for PIM grafts.
The no form of this command disables PIM graft debugging.
This command enables debugging for PIM interface information.
The no form of this command disables PIM interface debugging.
This command enables debugging for PIM join and prune mechanisms.
The no form of this command disables PIM join and prune mechanisms debugging.
This command enables debugging for PIM multicast fast failover (MoFRR).
The no form of this command disables MoFRR debugging.
This command enables debugging for PIM MRIB.
The no form of this command disables debugging for PIM MRIB.
This command enables debugging for PIM messaging.
The no form of this command disables debugging for PIM messaging.
This command enables debugging for the PIM MVPN route cache.
The no form of this command disables debugging for the PIM MVPN route cache.
This command enables debugging for PIM packets.
The no form of this command disables debugging for PIM packets.
This command enables debugging for PIM redundancy messages to the standby CPM.
The no form of this command disables debugging for PIM redundancy messages to the standby CPM.
This command enables debugging for PIM register mechanism.
The no form of this command disables debugging for PIM register mechanism.
This command enables debugging for PIM RPF vector.
The no form of this command disables debugging for PIM RPF vector.
This command enables debugging for PIM RTM.
The no form of this command disables debugging for PIM RTM.
This command enables debugging for PIM selective provider multicast service interface.
The no form of this command disables the debugging.
This command enables debugging for PIM tunnel interfaces.
The no form of this command disables debugging for PIM tunnel interfaces.