Creating a P2M service

Before creating a P2M service, you must complete the following steps:

• Activate CPE devices.
• Create a constraint (Manual-TE or threshold).
• Create service interfaces.
• Define the topology of the transport service and assign roles to service interfaces.
• Create a traffic filter.
• Create a group of OpenFlow interfaces.
• Create a QoS rule.

To create a P2M transport service:

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

   The SD-WAN infrastructure management page is displayed. By default, the Network resources tab is selected, which displays the table of SD-WAN Controllers.

2. Click Management next to the SD-WAN Controller and in the drop-down list, select Configuration menu.

   This opens the SD-WAN 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 transport service.
6. In the Constraint drop-down list, select a previously created constraint that you want to add to the transport service.
7. In the Balancing mode drop-down list, select the balancing mode for evenly distributing traffic among the links to prevent congestion of individual links and prevent performance issues for users:
   • Per-flow — Balancing across flows (sessions). During transmission, flows are evenly distributed across the links. This is the default setting.
   • Per-packet — Per-packet balancing. During transmission, packets are distributed evenly across the links.
   • Broadcast — Packets are sent to all links simultaneously to prevent losses.
8. In the MAC learn mode drop-down list, select the action to apply to a series of frames when the first frame is sent to the SD-WAN 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 address table. If the destination MAC address is not in the table, the series of frames is sent to all service interfaces added to the transport service, except for the interface on which the series of frames originally arrived. This is the default setting.
   • 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 address table. If the destination MAC address is not in the table, the series of frames is dropped.

   In both cases, if the destination MAC address is present in the MAC address table, the series of frames is sent to the corresponding service interface.

9. In the MAC age (sec.) field, enter the time period in seconds during which entries are kept in the MAC table on the SD-WAN Controller. Range of values: 10 to 65,535. The default setting is 300.
10. In the MAC table overload drop-down list, select the policy for processing new MAC addresses when the MAC table SD-WAN Controller is full:
    • Flood means traffic with destination MAC addresses that have not been learned previously is transmitted as BUM traffic (Broadcast, unknown-unicast, and multicast). This is the default setting.
    • Drop means that traffic with previously destination MAC addresses that have not been learned previously is dropped.
11. In the MAC table size field, enter the maximum number of entries in the MAC table on the SD-WAN controller. Range of values: 0 to 65 535. 0 means the number of entries is not limited. The default setting is 100.
12. In the Mode drop-down list, select whether you want to use the Default Forwarding Interface (hereinafter referred to as DFI) in the transport service. If the DFI role is assigned to a service interface, all unknown unicast traffic is sent to that service interface. Possible values:
    • Classic if you do not want to use DFI. This is the default setting.
    • DFI with FIB on root and leafs if you want to use DFI on the service interface with the Root role. The number of service interfaces with the Leaf role is not limited. Backup service interfaces can be added for each service interface.
    • DFI with FIB on leaf if you want to use DFI on the service interface with the Leaf role. The number of service interfaces with the Leaf role is not limited. Service interfaces with the Leaf role must be on the same CPE device. Backup service interfaces can be added for each service interface. Backup service interfaces with the Leaf role must be on the same CPE device, which must be different from the device hosting the primary service interfaces.
13. If necessary, in the Description field, enter a brief description of the transport service.
14. Click Next to proceed to the next group of settings.
15. In the Switch and Port drop-down lists on the right, select the CPE device and the service interface that you want to add to the transport service.
16. To display service interfaces that were previously added to transport services in the Port drop-down list, select the Show used interfaces check box. This check box is cleared by default.
17. In the QoS drop-down list, select the previously created QoS rule for the service interface.
18. In the Inbound filter drop-down list, select the previously created traffic filter for the service interface.
19. In the Role drop-down list, select the role of the service interface:
    • Leaf
    • Root
20. If necessary, add a backup service interface through which traffic must be transmitted if the primary interface goes out of service:
    1. Select the Use backup interface check box. This check box is cleared by default.
    2. In the Backup switch and Backup port drop-down lists, select the CPE device and the service interface created on it that you want to use as the backup interface.
    3. To display service interfaces that were previously added to transport services in the Backup port drop-down list, select the Show used interfaces check box. This check box is cleared by default.

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

21. To assign the DFI role to the service interface, select the Default Forwarding Interface check box. This check box cannot be selected if in the Role drop-down list for the service interface, you selected Leaf.
22. Click + Add to add the service interface to the transport service.

    The service interface is displayed in the lower part of the window. You can delete a service interface by clicking Delete next to it.

23. Click Next to proceed to the next group of settings.
24. In the Group drop-down list, select the previously created group of OpenFlow interfaces that you want to add. A service interface is automatically created on top of each OpenFlow interface in the group, and that service interface is added to the transport service.
25. In the QoS drop-down list, select the previously created QoS rule for service interfaces created on top of OpenFlow interfaces.
26. In the VLAN ID field, enter the outer VLAN tag value for service interfaces created on top of OpenFlow interfaces. You must take into account the following limitations regarding automatic creation of service interfaces on top of OpenFlow interfaces:
    • Only service interfaces with the VLAN encapsulation type can be created.
    • The VLAN tag value must be the same on all service interfaces.
27. In the Role drop-down list, select a role for service interfaces automatically created on top of OpenFlow interfaces:
    • Leaf
    • Root
28. Click + Add to add the group of OpenFlow interfaces to the transport service.

    The automatically created service interfaces are displayed in the lower part of the window. You can delete a service interface by clicking Delete next to it.

29. Click Create.

The P2M service is created and displayed in the table.