Provision and Manage P2MP Groups
In the NorthStar Controller, you can provision P2MP groups; view and modify group attributes; and view, add, or delete sub-LSPs. This is a separate workflow from provisioning P2P LSPs, initiated from the P2MP tab in the network information table. Netconf is the only provisioning method supported for P2MP.
In Junos OS Release 15.1F6 and later, you can enable the router to send P2MP LSP information to a controller (like the NorthStar Controller) in real time, automatically. Without that configuration, you must run device collection for NorthStar to learn about newly provisioned P2MP LSPs.
In the Junos OS, the configuration is done in the [set protocols pcep] hierarchy for PCEs and for PCE groups:
set protocols pcep pce pce-id p2mp-lsp-report-capability
After provisioning P2P or P2MP LSPs, if there is a PCEP flap, the UI display for RSVP utilization and RSVP live utilization might be out of sync. You can display those utilization metrics by navigating to Performance in the left pane of the UI. This is a UI display issue only. The next live update from the network or the next manual sync using Sync Network Model (Administration > System Settings > Advance Settings) corrects the UI display. In the System Settings window, you toggle between General and Advanced Settings using the button in the upper right corner of the window.
The following sections describe viewing, provisioning, and managing P2MP groups in the NorthStar Controller.
Viewing P2MP Groups and Their Sub-LSPs
P2MP group information is displayed in the P2MP Group tab of the network information table, and is also reflected in the topology map.
To display P2MP Group information, use the following steps:
- On the tabs bar of the network information table, click
the plus sign (+) and select P2MP Group from the drop-down menu as shown in Figure 1.
When you launch the web UI, only the Node, Link, and Tunnel tabs are displayed by default; P2MP Group is one of the tabs you can optionally display.
- The P2MP Group tab is added to the tab bar and the contents
are displayed as shown in Figure 2.
Columns for group attributes are shown across the top. You can add columns and filter the display in the usual ways. See Sorting and Filtering Options in the Network Information Table for more information.
- Click a row in the table to highlight the path in the topology map.
- Right-click a row in the table to display either a graphical
tree view of the group, or a list of the sub-LSPs that make up the
group. Figure 3 shows these
The tree diagram opens as a separate pop-up as show in Figure 4.
When you select to view sub-LSPs, the sub-LSPs that make up the group are displayed in a new tab in the network information table. On the list of sub-LSPs, you have all the display options normally available on the Tunnel tab. See Network Information Table Overview for more information.
Provisioning a P2MP Group
On the P2MP Group tab of the network information table, click Add at the bottom of the table. The Add P2MP Group window is displayed as shown in Figure 5. Red asterisks denote required fields.
Table 1 describes the data entry fields in the Properties tab of the Add P2MP Group window.
Table 1: Add P2MP Group Window, Properties Fields
Required. A user-defined name for the P2MP group. Only alphanumeric characters, hyphens, and underscores are allowed. Other special characters and spaces are not allowed.
You can enter a prefix to be applied to all of the tunnel names that are created.
Required. Planned bandwidth immediately followed by units (no space in between). Valid units are:
Examples: 50M, 1000b, 25g.
If you enter a value without units, bps is applied.
Use the drop-down menu to select RSVP. This is the only provisioning type supported.
Required. 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.
Required. 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.
Required. The name or IP address of the source node. Select from the drop-down list.
At least one is required. The names or IP addresses of the destination nodes. To select nodes from the topology map, Shift-click the nodes on the map and then click the world button at the bottom of the Node Z field. To add all nodes in the network, click the plus (+) button. To remove a node, highlight it in the Node Z field and click the minus (-) button.
Table 2: Add P2MP Group Window, Advanced Fields
Coloring Include All
Double click in this field to display the Modify Coloring Include All window. Select the appropriate bits. Click OK when finished.
Coloring Include Any
Double click in this field to display the Modify Coloring Include Any window. Select the appropriate bits. Click OK when finished.
Double click in this field to display the Modify Coloring Exclude window. Select the appropriate bits. Click OK when finished.
Diverse P2MP is currently not supported via the web UI, so these fields are not used. You can use the REST APIs, however.
Free-form comments if needed.
The Design tab includes the Routing Method options shown in Figure 7.
For P2MP, the default routing method is routeByDevice (since it uses NETCONF as the provisioning method). You can select a different routing method in which the PC server calculates the path for all the sub-LSPs. The behavior for all routing methods is similar to P2P LSP provisioning.
The Scheduling tab is identical to the one you use to provision P2P LSPs.
For P2MP, the User Properties tab is used for P2MP tree to MVPN service mapping. See Templates for Netconf Provisioning for more information.
Once you are finished defining the group, click Submit. The group is added to the network information table, on the P2MP Group tab.
Naming of the sub-LSPs is automatic, based on the Prefix-ID if provided, and the A and Z node names.
If the routing method is routeByDevice, the path for all sub-LSPs is dynamic. If you select any other routing method from the drop-down menu, the path is preferred. This can be changed for individual sub-LSPs.
Modifying a P2MP Group
Modifying a P2MP Group
To modify a P2MP group, select the group in the P2MP Group tab of the network information table, and click Modify at the bottom of the table. The Modify P2MP Group window is displayed as shown in Figure 8.
Using the tabs on the Modify P2MP Group window, you can change the value of attributes (affects all sub-LSPs in the group), add or remove destination nodes (which adds or removes sub-LSPs), and set up or change scheduling for the group.
There are two ways you can remove sub-LSPs from a group:
In the Properties tab of the Modify P2MP Group window, select the destination node(s) in the Node Z field and click the minus sign (-).
Display the sub-LSPs by right-clicking the group in the P2MP Group tab and selecting View Sub LSPs. In the resulting list of sub-LSPs in the Tunnel tab, select the LSP(s) to delete and click Delete at the bottom of the table.
When you have finished making changes, click Submit.
The following six attributes must be the same for all sub-LSPs in a P2MP group, and can therefore only be modified at the group level, using the Modify P2MP Group window:
To modify other attributes on the individual sub-LSP level (such as path or Max Hop, for example), select the tunnel in the Tunnel tab of the network information table and click Modify at the bottom of the table. If you attempt to modify one of the six group-level-only attributes at the sub-LSP level, an error message is displayed when you click Submit and the change is not made.
Deleting a P2MP Group
When you delete a P2MP group, all sub-LSPs that are part of that group are also deleted.
To delete a P2MP group, select the group on the P2MP Group tab of the network information table and click Delete at the bottom of the table. Respond to the confirmation message to complete the deletion.
Alternatively, you can use the Tunnel tab of the network information table to delete all the sub-LSPs in the P2MP group, which also deletes the group itself.