Creating a P2P service

To create a P2P 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 P2P services section.

    A table of P2P services is displayed.

  4. In the upper part of the page, click + P2P service.
  5. This opens a window; in that window, in the Name field, enter the name of the P2P service.
  6. In the Constraint drop-down list, select the created Manual-TE constraint or threshold constraint that you want to add to the P2P 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. If necessary, in the Description field, enter a brief description of the P2P service.
  9. In the Switch and Service interface drop-down lists on the left, select the CPE device and the created service interface that you want to use as the source service interface of the P2P service.
  10. 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 use as the destination service interface of the P2P service.
  11. If you want to display service interfaces that were added to transport services in the Service interface drop-down lists, select the Show used interfaces check box. This check box is cleared by default.
  12. If you want to swap the values selected in the Service interface drop-down lists, select the Switch interfaces check box. This check box is cleared by default.
  13. If you want to add a reserve service interface of the P2P service source through which traffic is transmitted if the primary service interface fails:
    1. Select the Use backup interface check box. This check box is cleared by default.
    2. 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 the reserve service interface.
    3. If you want to display service interfaces that were added to transport services in the Backup service interface drop-down list, select the Show used interfaces check box. This check box is cleared by default.

      If the primary source service interface of the P2P service goes up again, the P2P service keeps using the backup source service interface.

  14. In the Inbound filter drop-down lists on the left and right, select the created traffic filter for the source and destination interfaces of the P2P service.
  15. In the QoS drop-down list, select the created quality of service rule for the service interface of the P2P service source.
  16. If you want to track the status of the source and destination service interfaces of the P2P service and when one of the interfaces goes down, automatically disable the other, select the Propagate interface status check box. This check box is cleared by default. This check box cannot be selected when the Use backup interface check box is selected.

    When the service interface that was disabled first goes back online, the second service interface that was automatically disabled also resumes operation. This functionality works only on service interfaces with Access traffic classification. You can select the type of traffic classification when creating a service interface.

  17. Click Create.

The P2P 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