MPLS and RSVP
7450 ESS MPLS Guide Page 285
Point-to-Multipoint MPLS (P2MP) Commands
p2mp-id
Syntax p2mp-id id
Context config>router>mpls>lsp
Description This command configures the identifier of an RSVP P2MP LSP. An RSVP P2MP LSP is fully
identified by the combination of: <P2MP ID, tunnel ID, extended tunnel ID> part of the P2MP
session object, and <tunnel sender address, LSP ID> fields in the p2mp sender_template object.
The p2mp-id is a 32-bit identifier used in the session object that remains constant over the life of the
P2MP tunnel. It is unique within the scope of the ingress LER.
The no form restores the default value of this parameter.
Default 0
Parameters id — Specifies a P2MP identifier.
Values 0 — 65535
primary-p2mp-instance
Syntax [no] primary-p2mp-instance instance-name
Context config>router>mpls>lsp
Description This command creates the primary instance of a P2MP LSP. The primary instance of a P2MP LSP is
modeled as a set of root-to-leaf (S2L) sub-LSP’s. The root, for example a head-end node triggers
signaling using one path message per S2L path. The leaf sub-LSP paths are merged at branching
points.
Default none
Parameters instance-name — Specifies a name that identifies the P2MP LSP instance. The instance name can be
up to 32 characters long and must be unique.
s2l-path
Syntax [no] s2l-path path-name to ip-address
Context config>router>mpls>lsp>primary-inst
Description This command creates a root-to-leaf (S2L) sub-LSP path for the primary instance of a P2MP LSP.
The primary instance of a P2MP LSP is modeled as a set of root-to-leaf (S2L) sub-LSPs. The root, for
example, head-end node, triggers signaling using one path message per S2L path. The leaf sub-LSP
paths are merged at branching points.
To Next Page
Loading...
