Alcatel-Lucent 7450 Manual page 214

MPLS Commands
The operator can enable statistics collection on a manual bypass terminating on the egress LER.
However all LSPs which primary path is protected by the manual bypass will not collect statistics
when they activate forwarding over the manual bypass. When, the operator disables statistics
collection on the manual bypass LSP, then statistics collection on the protected LSP, if enabled, will
continue when the bypass LSP is activated.
The no form of this command disables statistics for this RSVP LSP in the ingress data path and
removes the accounting policy association from the LSP.
Default
none
Parameters sender-address ip-address — A string of 15 characters representing the IP address of the ingress
lsp-name — A string of up to 32 characters identifying the LSP name as configured at the ingress
p2p-template-lsp
Syntax [no] p2p-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 P2P auto-LSP at the egress LER.
When the ingress LER signals the path of a template based one-hop-p2p or mesh-p2p auto-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 P2P
auto-LSP or on a context that matches on the template name and the destination of the LSP 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. In this
case, the user is provided with CLI parameter max-stats to limit the maximum number of stat indices
which can be assigned to this context. If the context matches more than this value, the additional
request for stat indices from this context will be rejected.
Note the following rules when configuring an ingress statistics context based on template matching:
Page 214
LER for the LSP.
LER.
1. P2MP LSP via user configuration for L3 multicast in global routing instance: "LspNameFrom-
Config"
1. P2MP LSP as I-PMSI or S-PMSI in L3 mVPN: templateName-SvcId-mTTmIndex
1. P2MP LSP as I-PMSI in VPLS/B-VPLS: templateName-SvcId-mTTmIndex.
• max-stats, once allocated, can be increased but not decreased unless the entire ingress statistics
context matching a template name is deleted.
• In order to delete ingress statistics context matching a template name, a shutdown is required.
7450 ESS MPLS Guide