Configuring network service topology components

Managing network services > Configuring network service topology components

Configuring network service topology components

You can configure network components, connections, and interfaces added to the topology of a network service template or an individual network service. Before you can configure topology components, you must open the topology.

To open the topology:

In the menu, go to the Catalog section.
The network service management page is displayed.
Open the topology:
- If you want to open the topology of a network service template, select the template in the Catalog panel.
- If you want to open the topology of a network service, select the network service in the Network services panel.

The graphical design tool with the network service topology is displayed.

Use the following instructions to configure topology components:

Configuring a VNF in the network service topology
To configure a VNF in the topology:
1. Click the VNF.
  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 button .
  
  By default, the Flavours tab is selected, which displays the flavours of virtual machines for the network function. Flavours are described in the VNF package.
2. Select the Connection points tab and configure the VNF interfaces:
  1. In the Type drop-down list, select how you want to assign an IP address and subnet mask to the interface:
    - DHCP reservation to assign an IP address and subnet mask using DHCP.
    - AUTO to automatically assign an IP address and subnet mask. This is the default setting.
  2. If in the Type drop-down list, you selected DHCP reservation, follow these steps:
    1. In the IP field, enter the IP address of the interface.
    2. In the Mask field, enter the subnet mask.
  3. In the Description field, enter a brief description of the interface.
  4. If you want to make the interface a trunk port for processing traffic from multiple VLANs simultaneously, select the Trunk check box. When the check box is selected, the VNF interface is capable of transmitting and receiving tagged VLAN traffic, which contains an additional identifier (VLAN tag) that lets you identify and filter different VLANs in the network. This check box is cleared by default.
3. Select the VNF settings tab and specify general VNF settings:
  1. In the Name field, enter the name of the VNF.
  2. In the Description field, enter a brief description of the VNF.
  3. In the Order field, enter the sequence number for deploying the VNF on the OpenStack cloud platform. When you deploy a network service, the VNF with the lowest number is the first to be deployed. If none of the VNFs added to the network service topology have a sequence number specified, all VNFs are deployed simultaneously.
4. Specify the required settings on the remaining tabs. The number of tabs with settings that you can specify depends on the contents of the VNF package. Tabs are added to the package as variables.
  If you are having difficulty configuring certain settings, we recommend that you refer to the technical documentation provided by the VNF vendor or contact Kaspersky technical support.
5. Click Save in the upper part of the settings area.
Configuring a PNF in the network service topology.
To configure a PNF in the topology:
1. Click the PNF.
  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 button .
  
  By default, the Flavours tab is selected, which displays the flavours of virtual machines for the network function. Flavours are described in the PNF package.
2. Select the PNF settings tab and specify general PNF settings:
  1. In the Name field, enter the name of the PNF.
  2. In the Description field, enter a brief description of the PNF.
  3. In the Order field, enter the sequence number for deploying the PNF. When you deploy a network service, the PNF with the lowest number is the first to be deployed. If none of the PNFs added to the network service topology have a sequence number specified, all PNFs are deployed simultaneously.
3. Select the DC placement tab and select the data center that is hosting the PNF:
  1. In the Data center field, enter the name of the data center and select a value from the drop-down list.
  2. Click Apply.
4. Go to the Management IP tab and in the IP fields, enter the IP addresses of the VDU control interfaces within the PNF. To check the availability of an address, click Test connection.
5. Specify the required settings on the remaining tabs. The number of tabs with settings that you can specify depends on the contents of the PNF package. Tabs are added to the package as variables.
  If you are having difficulty configuring certain settings, we recommend that you refer to the technical documentation provided by the PNF vendor or contact Kaspersky technical support.
6. Click Save in the upper part of the settings area.
Configuring a P2P service in the network service template topology
To configure a P2P service in the topology:
1. Click the P2P service.
  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 button .
2. In the Name field, enter the name of the transport service.
3. If necessary, in the Description field, enter a brief description of the transport service.
4. Click Save in the upper part of the settings area.
Configuring a P2M service in the network service template topology
To configure a P2M service in the topology:
1. Click the P2M service.
  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 button .
2. In the Name field, enter the name of the transport service.
3. If necessary, in the Description field, enter a brief description of the transport service.
4. In the Connection points field, enter the maximum number of connection points of the transport service. Range of values: 2 to 9,999. If you do not specify a value for this setting, the number of connection points is unlimited.
5. 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 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. If necessary, use OpenStack DHCP to automatically assign IP addresses and configuration parameters to virtual machines:
  1. In the OpenStack DHCP drop-down list, select Enabled.
  2. In the CIDR field, enter the OpenStack IP address and subnet mask.
  3. In the Gateway field, enter the IP address of the gateway that routes traffic leaving the virtual network. This gateway connects the virtual network to external networks, such as the internet. The gateway address must be on the same subnet as the virtual machines and other network devices for them to communicate with each other.
  4. If you want to create a range of IP addresses, under Pools, click + Pool and in the fields that are displayed, enter the start and end values of the range. If a virtual machine requests an IP address, the DHCP server assigns an address from this range.
    The range must belong to the same subnet as the gateway, virtual machines, and other network devices so that they can communicate with each other, and the size of the range must accommodate the number of virtual machines on the network. You can create multiple ranges or delete a range by clicking Delete next to it.
  5. If you want to add a DNS server, under DNS, click DNS, and enter the IP address of the server in the field that is displayed. The DNS server allows virtual machines to resolve domain names to IP addresses.
    Information from the DNS server is sent to virtual machines via DHCP options, after which they can interact with devices on the virtual network, as well as gain access to the internet and other external networks using domain names instead of IP addresses. You can add multiple servers or delete a server by clicking Delete next to it.
11. Click Save in the upper part of the settings area.
Configuring an M2M service in the network service template topology
To configure an M2M service in the topology:
1. Click the M2M service.
  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 button .
2. In the Name field, enter the name of the transport service.
3. If necessary, in the Description field, enter a brief description of the transport service.
4. In the Connection points field, enter the maximum number of connection points of the transport service. Range of values: 2 to 9,999. If you do not specify a value for this setting, the number of connection points is unlimited.
5. 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.
6. 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.
7. 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.
8. 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.
9. If necessary, use OpenStack DHCP to automatically assign IP addresses and configuration parameters to virtual machines:
  1. In the OpenStack DHCP drop-down list, select Enabled.
  2. In the CIDR field, enter the OpenStack IP address and subnet mask.
  3. In the Gateway field, enter the IP address of the gateway that routes traffic leaving the virtual network. This gateway connects the virtual network to external networks, such as the internet. The gateway address must be on the same subnet as the virtual machines and other network devices for them to communicate with each other.
  4. If you want to create a range of IP addresses, under Pools, click + Pool and in the fields that are displayed, enter the start and end values of the range. If a virtual machine requests an IP address, the DHCP server assigns an address from this range.
    The range must belong to the same subnet as the gateway, virtual machines, and other network devices so that they can communicate with each other, and the size of the range must accommodate the number of virtual machines on the network. You can create multiple ranges or delete a range by clicking Delete next to it.
  5. If you want to add a DNS server, under DNS, click DNS, and enter the IP address of the server in the field that is displayed. The DNS server allows virtual machines to resolve domain names to IP addresses.
    Information from the DNS server is sent to virtual machines via DHCP options, after which they can interact with devices on the virtual network, as well as gain access to the internet and other external networks using domain names instead of IP addresses. You can add multiple servers or delete a server by clicking Delete next to it.
  - If you want to allow sharing of the M2M service between different network services, select the Share network service check box. This check box is cleared by default.
10. Click Save in the upper part of the settings area.
Configuring a shared network (OS 2 SHARED) in the network service template topology
To configure a shared network in the topology:
1. Click the shared network.
  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 button .
2. In the Name field, enter the name of the shared network.
3. If necessary, in the Description field, enter a brief description of the shared network.
4. Click Save in the upper part of the settings area.
Configuring a virtual router (OS vRouter) in the network template service topology
To configure a virtual router in the topology:
1. Click the virtual router.
  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 button .
2. In the Name field, enter the name of the virtual router.
3. If necessary, in the Description field, enter a brief description of the virtual router.
4. To set the 'up' value for the operating state of the virtual router, select the Administrative state check box. This check box lets you manage the operating state of the router without having to delete and recreate it. When this check box is selected, the router can relay traffic. This check box is cleared by default.
5. Click Save in the upper part of the settings area.
Configuring a VLAN in the network service topology.
To configure a VLAN in the topology:
1. Click the VLAN.
  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 button .
2. In the Name field, enter the name of the VLAN.
3. If necessary, in the Description field, enter a brief description of the VLAN.
4. If necessary, use OpenStack DHCP to automatically assign IP addresses and configuration parameters to virtual machines:
  1. In the OpenStack DHCP drop-down list, select Enabled.
  2. In the CIDR field, enter the OpenStack IP address and subnet mask.
  3. In the Gateway field, enter the IP address of the gateway that routes traffic leaving the virtual network. This gateway connects the virtual network to external networks, such as the internet. The gateway address must be on the same subnet as the virtual machines and other network devices for them to communicate with each other.
  4. If you want to create a range of IP addresses, under Pools, click + Pool and in the fields that are displayed, enter the start and end values of the range. If a virtual machine requests an IP address, the DHCP server assigns an address from this range.
    The range must belong to the same subnet as the gateway, virtual machines, and other network devices so that they can communicate with each other, and the size of the range must accommodate the number of virtual machines on the network. You can create multiple ranges or delete a range by clicking Delete next to it.
  5. If you want to add a DNS server, under DNS, click DNS, and enter the IP address of the server in the field that is displayed. The DNS server allows virtual machines to resolve domain names to IP addresses.
    Information from the DNS server is sent to virtual machines via DHCP options, after which they can interact with devices on the virtual network, as well as gain access to the internet and other external networks using domain names instead of IP addresses. You can add multiple servers or delete a server by clicking Delete next to it.
5. If you want to allow sharing of the network between different network services, select the Share network check box. This check box is cleared by default.
6. If you need to segment the network into multiple VLANs, in the Segmentation ID field, enter the VLAN ID.
7. Click Save in the upper part of the settings area.
Configuring a VXLAN in the network service topology.
To configure a VXLAN in the topology:
1. Click the VXLAN.
  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 button .
2. In the Name field, enter the name of the VXLAN.
3. If necessary, in the Description field, enter a brief description of the VXLAN.
4. If necessary, use OpenStack DHCP to automatically assign IP addresses and configuration parameters to virtual machines:
  1. In the OpenStack DHCP drop-down list, select Enabled.
  2. In the CIDR field, enter the OpenStack IP address and subnet mask.
  3. In the Gateway field, enter the IP address of the gateway that routes traffic leaving the virtual network. This gateway connects the virtual network to external networks, such as the internet. The gateway address must be on the same subnet as the virtual machines and other network devices for them to communicate with each other.
  4. If you want to create a range of IP addresses, under Pools, click + Pool and in the fields that are displayed, enter the start and end values of the range. If a virtual machine requests an IP address, the DHCP server assigns an address from this range.
    The range must belong to the same subnet as the gateway, virtual machines, and other network devices so that they can communicate with each other, and the size of the range must accommodate the number of virtual machines on the network. You can create multiple ranges or delete a range by clicking Delete next to it.
  5. If you want to add a DNS server, under DNS, click DNS, and enter the IP address of the server in the field that is displayed. The DNS server allows virtual machines to resolve domain names to IP addresses.
    Information from the DNS server is sent to virtual machines via DHCP options, after which they can interact with devices on the virtual network, as well as gain access to the internet and other external networks using domain names instead of IP addresses. You can add multiple servers or delete a server by clicking Delete next to it.
5. If you want to allow sharing of the network between different network services, select the Share network check box. This check box is cleared by default.
6. If you need to segment the network into multiple VXLANs, in the Segmentation ID field, enter the VXLAN ID.
7. Click Save in the upper part of the settings area.
Configuring a flat network in the network service template topology.
To configure a flat network in the topology:
1. Click the flat network.
  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 button .
2. In the Name field, enter the name of the flat network.
3. If necessary, in the Description field, enter a brief description of the flat network.
4. If necessary, use OpenStack DHCP to automatically assign IP addresses and configuration parameters to virtual machines:
  1. In the OpenStack DHCP drop-down list, select Enabled.
  2. In the CIDR field, enter the OpenStack IP address and subnet mask.
  3. In the Gateway field, enter the IP address of the gateway that routes traffic leaving the virtual network. This gateway connects the virtual network to external networks, such as the internet. The gateway address must be on the same subnet as the virtual machines and other network devices for them to communicate with each other.
  4. If you want to create a range of IP addresses, under Pools, click + Pool and in the fields that are displayed, enter the start and end values of the range. If a virtual machine requests an IP address, the DHCP server assigns an address from this range.
    The range must belong to the same subnet as the gateway, virtual machines, and other network devices so that they can communicate with each other, and the size of the range must accommodate the number of virtual machines on the network. You can create multiple ranges or delete a range by clicking Delete next to it.
  5. If you want to add a DNS server, under DNS, click DNS, and enter the IP address of the server in the field that is displayed. The DNS server allows virtual machines to resolve domain names to IP addresses.
    Information from the DNS server is sent to virtual machines via DHCP options, after which they can interact with devices on the virtual network, as well as gain access to the internet and other external networks using domain names instead of IP addresses. You can add multiple servers or delete a server by clicking Delete next to it.
5. If you want to allow sharing of the network between different network services, select the Share network check box. This check box is cleared by default.
6. Click Save in the upper part of the settings area.
Configuring interfaces in the network service topology.
To configure an interface in the topology:
1. Click the interface.
  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 button .
2. In the Name field, enter the name of the interface.
3. If necessary, in the Description field, enter a brief description of the interface.
4. Click Save in the upper part of the settings area.

Article ID: 260313, Last review: Aug 21, 2024

Page top