Add a P2MP Group

To add a P2MP Group:

Click Network > Topology.
The Topology page is displayed with the topology map at the center and the network information table at the bottom of the page.
Hover over the More Tabs list and select P2MP Group.

The P2MP Group tab appears.
Click the add (+) icon.
The Add P2MP Group page appears on the right.
Configure the P2MP group as per Table 1.
Note:
Fields marked with asterisk (*) are mandatory.
Click Add.
A confirmation message appears stating that the Add P2MP request is successfully sent. The new P2MP group is displayed under the P2MP Groups tab.

Table 1: Fields on the Add P2MP Group Page
Field	Description
Properties
Provisioning Method	Select PCEP or NETCONF. The default is NETCONF.
Provision Type	The default is RSVP, which is the only option supported for P2MP groups.
P2MP Group Name	Enter a user-defined name for the P2MP group. Only alphanumeric characters, hyphens, and underscores are allowed. Other special characters and spaces are not allowed.
Node A	Click the Node A field and select the name of the ingress (source) node from the list.
Node Z List	Click the Node Z field and select one or more egress (destination) nodes from the list.
Planned Bandwidth	Enter the planned bandwidth value. You must enter a number immediately followed by K (Kbps), M (Mbps), or G (Gbps). For example, 10M signifying 10 megabits per second. Note: If you enter a value without units, bps is applied.
Planned Metric	Enter the metric value for static tunnel. Use the up and down arrows to increment or decrement the value. For more information, see Basic LSP Configuration in MPLS Applications User Guide.
Setup	Enter the RSVP setup priority for the tunnel traffic. Priority levels range from 0 (highest priority) through 7 (lowest priority). The default is 7, which is the standard MPLS LSP definition in Junos OS.
Hold	Enter the RSVP hold priority for the tunnel traffic. Priority levels range from 0 (highest priority) through 7 (lowest priority). The default is 7, which is the standard MPLS LSP definition in Junos OS.
Routing Method	Click the Routing Method list and select a routing method from the following: Admin Weight Constant Default Note: Do not change the routing method for PCEP-provisioned sub-LSPs; they should always have a routing method of “default”. Delay Distance ISIS OSPF Route by Device Note: For NETCONF-provisioned P2MP group, the default routing method is Route By Device and the path for all sub-LSPs is dynamic. For PCEP-provisioned P2MP group, default is selected as the routing method. The Route By Device routing method is not available for PCEP-provisioned P2MP group.
Bandwidth Sizing	Toggle the button to enable bandwidth sizing. By default, this option is disabled. Note: You cannot enable Bandwidth Sizing if the provisioning method is NETCONF. Once enabled, configure the following parameters: Adjustment threshold (in percentage): Controls the sensitivity of the automatic bandwidth adjustment. The new planned bandwidth is only considered if it differs from the existing bandwidth by the value of this setting or more. Minimum and Maximum (planned) Bandwidth: If the new planned bandwidth is greater than the maximum setting, PathFinder signals the LSP with the maximum bandwidth. If the new planned bandwidth is less than the minimum setting, PathFinder signals the LSP with the minimum bandwidth. If the new planned bandwidth value is in between the maximum and minimum settings, Pathfinder signals the LSP with the new planned bandwidth. Minimum Variation Threshold: Specifies the sensitivity of the automatic bandwidth adjustment when the new planned bandwidth is compared to the current planned bandwidth. The new planned bandwidth is only considered if the difference is greater than or equal to the value of this setting. This can be used to prevent small fluctuations from triggering unnecessary bandwidth changes. If both the adjustment threshold and the minimum variation threshold are greater than zero, both settings are taken into consideration. In that case, the new planned bandwidth is considered if: • The percentage difference is greater than or equal to the adjustment threshold and • The actual difference is greater than or equal to the minimum variation.
Constraints Enables you to configure administrative groups (link coloring) for bypass LSPs. For more information, see Assign Names to Admin Group Bits.
Admin Group Include All	Specifies the administrative groups whose links the bypass LSP must traverse. Select one or more bit-level link coloring options from the list.
Admin Group Include Any	Specifies the administrative groups whose links the bypass LSP can traverse. Select one or more bit-level link coloring options from the list.
Admin Group Exclude	Specifies the administrative groups to exclude for a bypass LSP. Select one or more bit-level link coloring options from the list.
Advanced
Description	Enter a description for the P2MP Group.
Diversity Group	Enter the name of a group of tunnels to which this tunnel belongs, and for which diverse paths is required.
Diversity Level	Select one of the following values for diversity level: Default (no diversity) Link Shared Risk Link Group (SRLG) Site Site diversity is the strongest—it includes SRLG and link diversity. SRLG diversity includes link diversity. Link diversity is the weakest.
Custom Attributes	Simple name-value pairs which can be used to add any arbitrary customer-specific information. For example, to differentiate between properties for different vendor nodes. To add custom properties associated with the node: Click add (+) icon to add a new row. Click the newly added row to enter the Name and Value. Click the √ icon to save your changes. Note: You can add multiple rows (properties). To delete an entry (row), select the row and click the delete (trash can) icon.
Service Note: This tab is available only when the provisioning method selected is PCEP. When provisioning method is NETCONF, this tab is unavailable (greyed out).
VPN Identifier	Select one of the following: MVPN instance: Select the multicast VPN instance as configured on the router. Route Distinguisher (RD): Populates automatically when you select the multicast VPN instance, if the information is available. If the field does not automatically populate, you can: Obtain the RD from the head-end router configuration. Run device collection for the head-end router from the Node tab of the network information table. Right-click the head-end router and select More > Run Device Collection. Once the collection completes, the RD field should auto-populate.
Flows	Define the (S,G) groups. For each flow you want to add, click the add (+) icon to display a new line. Enter the source and group (multicast traffic destination) IP addresses and mask. Note: To delete an entry, select the row and click the delete (trash can) icon. The maximum number of flows (S,G groups) that you can successfully associate with a P2MP LSP depends on the traffic rate and group type (SSM or ASM), and is therefore, not a fixed number. If you surpass the maximum number of flows for the P2MP group, all the flows go into “Inactive (mapping successful)” state as viewed in the output of the `show path-computation-client traffic-steering command` on the router. To recover, delete the P2MP group and recreate it.
Schedule
Plan	Select one of the following options: No Schedule Once: Enter start and end date and time for a single event. Click the calendar icon on the right to display a monthly calendar from which you can select the year, month, and day. Click Select Time to enter a custom start time by scrolling up or down to select the hour, minute, and second along with AM/PM selection. Note: You can also click Now to select the current date and time. Click Ok. Note: You can also manually enter date and time values. Recurring Daily: Enter the start and end parameters for a recurring daily event (similar to the Once schedule).

Add a P2MP Group

Related Documentation