[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring Dynamic Point-to-Multipoint Flooding LSPs with the Default Template

The default-template option, specified at the [edit routing-instances routing-instance-name provider-tunnel rsvp-te label-switched-path-template] hierarchy level causes the point-to-multipoint LSPs to be created with the default parameters. The default parameters are for a minimally configured point-to-multipoint LSP. The name of this point-to-multipoint LSP is also generated automatically and is based on the following model:

id:vpls:router-id:routing-instance-name

The following show command output for show mpls lsp p2mp illustrates how a point-to-multipoint flood LSP name could appear if you configure the label-switched-path-template statement with the default-template option:

user@host> show mpls lsp p2mp ingress

Ingress LSP: 2 sessions P2MP name: static, P2MP branch count: 3
To              From            State Rt ActivePath       P     LSPname
10.255.14.181   10.255.14.172   Up     0                  *     vpn02-vpn11
10.255.14.177   10.255.14.172   Up     0 path2            *     vpn02-vpn07
10.255.14.174   10.255.14.172   Up     0 path3            *     vpn02-vpn04
P2MP name: 9:vpls:10.255.14.172:green, P2MP branch count: 2
To              From            State Rt ActivePath       P     LSPname
10.255.14.177   10.255.14.172   Up     0                  *     11:vpls:10.255.14.172:green
10.255.14.174   10.255.14.172   Up     0                  *     10:vpls:10.255.14.172:green
Total 5 displayed, Up 5, Down 0

The dynamically generated point-to-multipoint LSP name is 9:vpls:10.255.14.172:green.

[Contents] [Prev] [Next] [Index] [Report an Error]