12.6. SR P2MP Configuration Command Reference

The command enters the configuration context for a P2MP SR tree.

This command enables BFD tracking at the P2MP SR tree level, which means that all next-hops of the replication segments that use a BFD-enabled L3 interface register with the BFD module.

The no form of this command disables BFD tracking of the P2MP SR tree.

This command creates a P2MP policy entry.

The no form of this command deletes the specified policy entry.

This command configures a candidate path under the P2MP policy.

A P2MP policy can contain multiple candidate paths, which are redundant trees. Each candidate path represents a P2MP tree with its own traffic engineering constraints. Each candidate path has its own preference and the candidate path with the highest preference is the active P2MP tunnel.

The no form of this command removes the specified candidate path.

This command configures the active instance as a primary or a secondary instance. Before configuring the active instance ID, the candidate path instance must be configured using the instance command.

The no form of this command removes the active instance.

This command enters the context to configure the instance entries of the candidate path.

Multiple path instances can exist under a candidate path. Each path instance is a P2MP LSP and has an instance ID. Path instances can be used for global optimization of the active candidate path.

This command configures the candidate path instance as primary or secondary, and the instance identifier.

The no form of this command removes the candidate path instance.

This command sets the candidate path preference. The candidate path with the highest preference is the active candidate path.

The no form of this command removes the candidate path preference.

This command administratively disables an entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics.

When the operational state of an entity is disabled, the operational state of any entities contained within are also disabled. Many objects must be shut down before they may be deleted.

Services are created in the administratively down (shutdown) state. When a no shutdown command is entered, the service becomes administratively up and then attempts to enter the operationally up state.

The no form of this command places the entity into an administratively enabled state.

This command configures the IP address of the P2MP tree root node of the P2MP policy. The root tree ID and the root address uniquely identify the P2MP policy on the root node.

The no form of this command removes the root address entry.

This command configures the tree ID on the root node. The root tree ID and the root address uniquely identify the P2MP policy on the root node.

The no form of this command removes the root tree ID entry.

This command creates a replication segment entry for the P2MP LSP.

The no form of this command deletes the replication segment entry.

This command configures the incoming replication SID for this replication segment entry.

The no form of this command removes the incoming replication SID.

This command configures the instance ID for the replication segment entry.

The ID is a unique identifier for the P2MP LSP on the root. The combination of root ID, tree ID, and instance ID uniquely identifies a P2MP LSP throughout the network.

The no form of this command removes the instance.

This command configures the next-hop ID for the replication segment.

A replication policy can have multiple next-hop IDs used at a replication node where there are multiple outgoing interfaces or protection next-hops.

The no form of this command removes the next-hop ID.

This command configures the IP address of the next-hop for the replication segment.

The no form of this command removes the next-hop address.

This command provides the outgoing interface name.

The no form of this command removes the outgoing interface name.

This command provides the ID of the protection next-hop used for FRR.

The protection next-hop outgoing SID is pushed on top of the next-hop SID list.

The no form of this command removes the protection next-hop.

This command configures the replication SID for this next-hop.

The no form of this command removes the replication SID.

This command configures the replication segment with the IP address of the root node.

The no form of this command removes the root node address.

This command configures the root-tree ID for this replication segment.

The no form of this command removes the root-tree ID.

This command configures the action to take for this replication segment.

The no form of this command removes the SID action.

This command configures the reserved label block name for this P2MP SR tree. Before configuring for the P2MP SR tree, the reserved label block name must be configured on the root node of the P2MP policy in the config>router>mpls-labels context.

The no form of this command removes the reserved label block name for this P2MP SR tree.

This command enables P2MP SR for the MVPN provider tunnel.

The no form of this command disables P2MP SR.

This command enables a P2MP policy for the MVPN provider tunnel.

The no form of this command disables the P2MP policy.

This command administratively disables an entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics.

When the operational state of an entity is disabled, the operational state of any entities contained within are also disabled. Many objects must be shut down before they may be deleted.

Services are created in the administratively down (shutdown) state. When a no shutdown command is entered, the service becomes administratively up and then attempts to enter the operationally up state.

The no form of this command places the entity into an administratively enabled state.

This command assigns the specified static policy to the MVPN tunnel.

The no form of this command removes the static policy from the MVPN tunnel.