Alcatel-Lucent 7450 Manual page 215

If there are no stat indices available at the time the session of the P2P LSP matching a template
context is signaled and the session state installed by the egress LER, no stats are allocated to the
session.
Furthermore, the assignment of stat indices to the LSP names that match the context will also be not
deterministic. The latter is due to the fact that a stat index is assigned and released following the
dynamics of the LSP creation or deletion by the ingress LER. For example, a multicast stream crosses
the rate threshold and is moved to a newly signaled S-PMSI dedicated to this stream. Later on, the
same steam crosses the threshold downwards and is moved back to the shared I-PMSI and the P2MP
LSP corresponding to the S-PMSI is deleted by the ingress LER.
The no form deletes the ingress statistics context matching on the RSVP session name.
Parameters
rsvp-session-name SessionNameString — Specifies the name of the RSVP P2MP session in the
sender sender-address — Specifies a string of 15 characters representing the IP address of the
p2mp-template-lsp
Syntax [no] p2mp-template-lsp rsvp-session-name SessionNameString sender sender-address
Context config>router>mpls>ingress-stats
Description This command configures an ingress statistics context matching on the RSVP session name for a
RSVP P2MP LSP at the egress LER.
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:
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 that matches on the template name and
the service-id as configured at the ingress LER.
When the matching is performed on a context, the user must enter the RSVP session name string in
the format "templateName-svcId" to include the LSP template name as well as the mVPN VPLS/B-
VPLS service ID as configured at the ingress LER. In this case, one or more P2MP LSP instances
signaled by the same ingress LER could be associated with the ingress statistics configuration and the
user is provided with CLI parameter max-stats to limit the maximum number of stat indices that can
7450 ESS MPLS Guide
• An accounting policy cannot be configured or de-configured until the ingress statistics context
matching a template name is shut down.
• After deleting an accounting policy from an ingress statistics context matching a template name,
the policy is not removed from the log until a no shut is performed on the ingress statistics con-
text.
format of "templateName-svcId". This field can hold up to 64 characters.
ingress LER for the LSP.
• P2MP LSP via user configuration for L3 multicast in global routing instance: "LspNameFrom-
Config"
• P2MP LSP as I-PMSI or S-PMSI in L3 mVPN: templateName-SvcId-mTTmIndex
• P2MP LSP as I-PMSI in VPLS/B-VPLS: templateName-SvcId-mTTmIndex
MPLS and RSVP
Page 215