Creating a P2M service

To create a P2M service:

  1. In the menu, go to the Infrastructure section.

    This opens the resource management page. By default, the Network resources tab is selected, which displays the table of controllers.

  2. Click Management → Configuration menu next to the controller.

    This opens the controller configuration menu. By default, you are taken to the Controller nodes section, which displays a table of controller nodes.

  3. Go to the P2M services section.

    A table of P2M services is displayed.

  4. In the upper part of the page, click + P2M service.
  5. This opens a window; in that window, in the Name field, enter the name of the P2M service.
  6. In the Constraint drop-down list, select the created Manual-TE constraint or threshold constraint that you want to add to the P2M service.
  7. In the Balancing mode drop-down list, select the balancing mode for distributing traffic among the links:
    • Per-flow means the traffic streams (5-Tuple) are distributed among the links in accordance with the link cost. Default value.
    • Per-packet means the traffic packets are distributed among the links in accordance with the link cost.
    • Broadcast means the traffic packets are duplicated and transmitted simultaneously through all links to avoid loss.

    You can manually specify link cost.

  8. In the Mode drop-down list, select whether the P2M service uses a DFI (Default Forwarding Interface), to which unknown unicast traffic is sent:
    • Classic if you do not want to use DFI. Default value.
    • DFI with FIB on root and leafs if you want to use DFI on the service interface with the root role.
    • DFI with FIB on leaf if you want to use DFI on the service interface with the root role. Service interfaces with the leaf role must be created on the same CPE device. Backup service interfaces with the leaf role must be created on the same CPE device, which must be different from the CPE device on which the primary service interfaces are created.
  9. In the MAC learn mode drop-down list, select the action that you want to apply to a series of frames when the first frame is sent to the controller to learn the source MAC address:
    • Learn and flood means the controller remembers the MAC address of the source and checks for the presence of the destination MAC address in the MAC table. If the destination MAC address is not in the MAC table, the series of frames is sent to all service interfaces added to the P2M service, except for the service interface on which the series of frames originally arrived. Default value.
    • Learn and drop means the controller remembers the MAC address of the source and checks for the presence of the destination MAC address in the MAC table. If the destination MAC address is not in the MAC table, the series of frames is dropped.

    If the destination MAC address is present in the MAC table, the series of frames is sent to the destination service interface.

  10. In the MAC age (sec.) field, enter the time period in seconds during which entries are kept in the MAC table of the controller. Range of values: 10 to 65,535. Default value: 300.
  11. In the MAC table overload drop-down list, select the policy for processing new MAC addresses when the MAC table of the controller is full:
    • Flood means traffic with destination MAC addresses that have not been learned is transmitted as BUM traffic (Broadcast, unknown-unicast, and multicast). Default value.
    • Drop means that traffic with destination MAC addresses that have not been learned is dropped.
  12. In the MAC table size field, enter the maximum number of entries in the MAC table on the controller. Range of values: 0 to 65,535. 0 means the number of records in the MAC table of the controller is not limited. Default value: 100.
  13. If necessary, in the Description field, enter a brief description of the P2M service.
  14. Click Next to proceed to the next group of settings.
  15. Add the service interface to the P2M service:
    1. Click + Add.

      The service interface settings are displayed.

    2. In the Switch and Service interface drop-down lists on the right, select the CPE device and the created service interface that you want to add to the P2M service.
    3. In the QoS drop-down list, select the created quality of service rule for the service interface.
    4. In the Inbound filter drop-down list, select the created traffic filter for the service interface.
    5. In the Role drop-down list, select the role of the service interface:
      • Root means the service interface can send traffic to service interfaces with any role.
      • Leaf means the service interface can send traffic only to service interfaces with the Root role.
      • Root, default forwarding interface means the service interface can send traffic to service interfaces with any role, and the DFI role is assigned to this service interface.
    6. If you want to add a backup service interface through which traffic must be sent when the primary service interface fails, in the Backup switch and Backup service interface drop-down lists, select the CPE device and the created service interface that you want to use as a backup service interface.

      If the primary service interface goes back online, the P2M service continues to use the backup service interface.

    The service interface is added and displayed in the lower part of the window. You can add multiple service interfaces or delete a service interface. To delete a service interface, click the delete icon cross_icon_3 next to it.

  16. Click Next to proceed to the next group of settings.
  17. If you want to add multiple network interfaces to a P2M service at the same time, you need to add a group of OpenFlow ports. To do so:
    1. Click + Add.

      Settings of the OpenFlow port group are displayed.

    2. In the Group drop-down list, select the created OpenFlow port group that you want to add to the P2M service. When you save the settings of the P2M service, service interfaces are automatically created that are mapped to OpenFlow ports in the OpenFlow port group, and then these service interfaces are automatically added to the P2M service.
    3. In the QoS drop-down list, select the created quality of service rule for automatically created service interfaces mapped to OpenFlow ports.
    4. In the VLAN ID field, enter the outer VLAN tag value for automatically created service interfaces mapped to OpenFlow ports. Service interfaces with the VLAN traffic classification type can only be created automatically. The same outer VLAN tag is assigned to each service interface.
    5. In the Role drop-down list, select the role for automatically created service interfaces mapped to OpenFlow ports:
      • Root means the service interface can send traffic to service interfaces with any role.
      • Leaf means the service interface can send traffic only to service interfaces with the Root role.

    The OpenFlow group is added and displayed in the lower part of the window. You can add multiple OpenFlow port groups or delete an OpenFlow port group. To delete a group of OpenFlow ports, click the delete icon cross_icon_3 next to it.

  18. Click Create.

The P2M service is created and displayed in the table.

See also

Scenario: Directing application traffic to a transport service

Scenario: Ensuring L2 connectivity between CPE devices
Page top