Alcatel-Lucent 7450 - Configuring RSVP P2 MP LSP Ingress Statistics

MPLS and RSVP
7450 ESS MPLS Guide Page 53
config
router
[no] mpls
lsp-template template-name p2mp
no lsp-template template-name
[no] egress-statistics
accounting-policy policy-id
no accounting-policy
[no] collect-stats
If there are no stat indices available at the time an instance of the P2MP LSP template is signaled,
no stats are allocated to the instance, but the LSP is brought up. In this case, an operational state of
out-of-resources is shown for the egress stats in the show output of the P2MP LSP S2L path.
Configuring RSVP P2MP LSP Ingress Statistics
When the ingress LER signals the path of the S2L sub-LSP, it includes the name of the LSP and
that of the path in the Session Name field of the Session Attribute object in the Path message. The
encoding is as follows:
Session Name: lsp-name::path-name, where lsp-name component is encoded as follows:
1. P2MP LSP via user configuration for L3 multicast in global routing instance:
“LspNameFromConfig”
2. P2MP LSP as I-PMSI or S-PMSI in L3 mVPN: templateName-SvcId-mTTmIndex
3. P2MP LSP as I-PMSI in VPLS/B-VPLS: templateName-SvcId-mTTmIndex
The ingress statistics CLI configuration allows the user to match either on the exact name of the
P2MP LSP as configured at the ingress LER or on a context which matches on the template name
and the service-id as configured at the ingress LER.
config
router
[no] mpls
ingress-statistics
[no] lsp lsp-name sender sender-address
accounting-policy policy-id
no accounting-policy
[no] collect-stats
[no] shutdown
[no] p2mp-template-lsp rsvp-session-name
SessionNameString sender sender-address
accounting-policy policy-id
no accounting-policy
[no] collect-stats
max-stats integer<1-8192|max, default max>
no max-stats
[no] shutdown