This feature provides the following counters for a RSVP P2MP LSP instance:
per forwarding class forwarded in-profile packet count
per forwarding class forwarded in-profile byte count
per forwarding class forwarded out of profile packet count
per forwarding class forwarded out of profile byte count
The above counters are provided for the following LSR roles:
At ingress LER, a set of per P2MP LSP instance counters for packets forwarded to the P2MP LSP instance without counting the replications is provided. In other words, a packet replicated over multiple branches of the same P2MP LSP instance counts once as long as at least one LSP branch forwarded it.
At BUD LSR and egress LER, per ILM statistics are provided. These counters include all packets received on the ILM, whether they match a L2/L3 MFIB record or not. ILM stats work the same way as for a P2P LSP. In other words, they count all packets received on the primary ILM, including packets received over the bypass LSP.
When MBB is occurring for an S2L path of an RSVP P2MP LSP, paths of the new and old S2L both receive packets on the egress LER. Both packets are forwarded to the fabric and outgoing PIM/IGMP interfaces until the older path is torn down by the ingress LER. In this case, packet duplication should be counted.
No branch LSR statistics are provided.
The P2MP LSP statistics share the same pool of counters and stat indexes the P2P LSP share on the node. Each P2P/P2MP RSVP LSP or LDP FEC consumes one stat index for egress stats and one stat index for ingress stats.
The user can retrieve the above counters in four different ways:
In CLI display of the output of the show command applied to a specific instance, or a specific template instance, of a RSVP P2MP.
In CLI display of the output of the monitor command applied to a specific instance, or a specific template instance, of a RSVP P2MP.
Via an SNMP interface by querying the MIB.
Via an accounting file if statistics collection with the default or user specified accounting policy is enabled for the MPLS LSP stats configuration contexts.
OAM packets that are forwarded using the LSP encapsulation, for example, P2MP LSP Ping and P2MP LSP Trace, are also included in the above counters.
The user can determine if packets are dropped for a specific branch of a P2MP RSVP LSP by comparing the egress counters at the ingress LER with the ILM counters at the egress LER or BUD LSR.
Octet counters are for the entire frame and so include the label stack and the L2 header and padding similar to the existing P2P RSVP LSP and LDP FEC counters. As such, ingress and egress octet counters for an LSP may slightly differ if the type of interface or encapsulation is different (POS, Ethernet NULL, Ethernet Dot1.Q).