Configuring a P2M service in the topology

To configure a P2M service in the topology:

1. Navigate to the topology in one of the following ways:
   • Start creating or editing a network service template.
   • Start creating or editing a network service.
2. In the topology, click the P2M service that you want to configure.

   The settings area is displayed in the lower part of the page. You can expand the settings area to fill the entire page by clicking the expand icon .

3. In the Name field, enter the name of the transport service.
4. If necessary, in the Description field, enter a brief description of the transport service.
5. In the Connection points field, enter the maximum number of transport service connection points. Range of values: 2 to 9999. If you do not specify a value for this setting, the number of connection points is unlimited.
6. In the Mode drop-down list, select whether you want to use the Default Forwarding Interface (DFI), to which unknown unicast traffic is sent, in the transport service:
   • 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. 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 root 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.

7. In the MAC age (sec.) field, enter the time period in seconds during which you want to keep entries in the MAC table on the controller. Range of values: 10 to 65,535. The default setting is 300.
8. 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 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. 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 address table. If the destination MAC address is not in the table, the series of frames is dropped.

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

9. 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 entries is not limited. The default setting is 100.
10. 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 previously is transmitted as BUM traffic (Broadcast, unknown-unicast, and multicast). Default value.
    • Drop means that traffic with previously destination MAC addresses that have not been learned previously is dropped.
11. If you want to configure the assignment of IP address to virtual network functions using DHCP:
    1. In the OpenStack DHCP drop-down list, select Enabled. The default setting is Disable.
    2. In the CIDR field, enter the IPv4 prefix of the OpenStack subnet that you want to assign IP addresses to virtual network functions.
    3. If you want the OpenStack subnet to assign a particular gateway to virtual network functions, enter the IPv4 address of the gateway in the Gateway field.
    4. Specify the range from which the OpenStack subnet must assign IP addresses to virtual network functions:
       1. Under Pools, click + Pool.
       2. In the fields that are displayed, enter the start and end values for the IP address range.

       The range of IP addresses is specified and displayed in the Pools section. You can specify multiple ranges of IP addresses; to delete a range, click Delete next to it.

    5. Specify the DNS server that the OpenStack subnet must assign to virtual network functions:
       1. Under DNS, click + DNS.
       2. In the field that is displayed, enter the IPv4 address of the DNS server.

       The DNS server is specified and displayed in the DNS section. You can specify multiple DNS servers; to delete a server, click Delete next to it.

12. In the upper part of the settings area, click Save to save P2M service settings.