P2MP RSVP-TE LSP Statistics
Page 52 7450 ESS MPLS Guide
4. The P2MP LSP statistics share the same pool of counters and stat indices 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. 
5. 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.
6. 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 given 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 thus include the label stack and the L2 header and 
padding similar to the existing P2P RSVP LSP and LDP FEC counters. Thus 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).
Configuring RSVP P2MP LSP Egress Statistics
At ingress LER, the configuration of the egress statistics is under the MPLS P2MP LSP context 
when carrying multicast packets over a RSVP P2MP LSP in the base routing instance. This is the 
same configuration as the one already supported with P2P RSVP LSP.
config
     router
        [no] mpls
            [no] lsp lsp-name p2mp-lsp
                 [no] egress-statistics
                      accounting-policy policy-id
                      no accounting-policy
                      [no] collect-stats
                 [no] shutdown
If there are no stat indices available when the user performs the ‘no shutdown’ command for the 
egress statistics node, the command will be failed. 
The configuration is in the P2MP LSP template when the RSVP P2MP LSP is used as an I-PMSI 
or S-PMSI in multicast VPN or in VPLS/B-VPLS.