Managing network services and virtualization of network functions

Network services

Network services relay traffic over the network and apply network functions to it, such as WAN optimization, shaping, and traffic protection. Each network service has a topology that you build using a graphical design tool. You can add components to the topology and connect them to each other.

You can build a topology in a network service template and then assign that network service template to a tenant. Components added to the template topology are automatically assigned to the tenant together with the network service template. A tenant can create and deploy network services, if necessary, using assigned network service templates, and edit network services that are already deployed.

You can use network services to deploy SD-WAN instances. The network service for deploying SD-WAN instances is called the SD-WAN network service (SD-WAN service).

An example of a network service topology is shown in the figure below.

Network service topology

Network function virtualization

Network function virtualization (NFV) lets you use virtualized storage, compute resources, and networks to provide network functions and combine these into network services.

You can deploy virtual network functions (VNF) and physical network functions (PNF) in network services. The difference between virtual and physical network functions is that the orchestrator does not manage the lifecycle of physical network functions. Third-party network functions are supported.

Kaspersky SD-WAN complies with the architecture specified in the ETSI NFV MANO specification (NFV Management and Network Orchestration), which defines the following main functional components:

• Orchestrator

  Controls the solution infrastructure, functions as an NFV orchestrator (NFVO), and manages network services and distributed VNFMs. You can manage the orchestrator via the web interface or REST API when using external northbound systems.

  .
• Virtual Network Function Managers (VNFM)

  Manages the lifecycle of virtual network functions using SSH, Ansible playbooks, scripts, and Cloud-init attributes.

  .
• Virtual Infrastructure Manager

  Manages computational, networking, and storage resources within the NFV infrastructure. Serves to connect network functions with virtual links, subnets, and ports.

  Can be deployed in the data center or on a uCPE device. Deploying the VIM in the data center implies centralized management of the VNF lifecycle, while a VIM deployed on a uCPE device allows delivering VNFs to remote locations and managing these VNFs locally. The deployed VIM must be added in the orchestrator web interface.

  The OpenStack cloud platform is used as the VIM.

  .
• The Zabbix monitoring system monitors the status of virtual and physical network functions and notifies the orchestrator when a network function needs to be restored or scaled.
• The NFV infrastructure consists of physical resources such as hardware storage, servers, and network devices.
• Controller

  Centrally manages the overlay network:

  • Builds the network topology.
  • Creates transport services.
  • Manages CPE devices using the OpenFlow protocol.
  • Balances traffic between links.
  • Monitors links and automatically switches traffic to a backup link if the primary link fails.

  To deploy the controller, you need to deploy the physical network function of the controller, which is contained in the installation archive. The controller is managed by the orchestrator.

  .

The figure below shows the relations between the solution components and the NFV infrastructure. Components of external solutions are marked in white, Kaspersky SD-WAN components are marked in green, and the red lines are connections between components.

NFV infrastructure

Managing network service templates

A list of network service templates is displayed on the administrator portal in the Infrastructure section, in the Catalog pane on the Templates tab.

Creating a network service template

To create a network service template:

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

   The network service management page is displayed.

2. In the upper part of the page, click + Template.

   The graphical design tool for building the topology is displayed.

3. Add network service components to the topology:
   1. Drag network server components from the Catalog pane into the graphical design tool. The pane displays the following network service components:
      • Network service templates — when you add a network service template to a topology, the topology is constructed in accordance with the network service template. You can add multiple network service templates to the topology.
      • Shared network services — you must add a shared network service to the topology of network services that you want to connect to the shared network service. You can specify a brief description of the shared network service.
      • Virtual and physical network functions. The actions that you can perform on virtual and physical network functions are described in the Managing virtual network functions and Managing physical network functions sections.
   2. Drag and drop links from the Links tab into the graphical design tool. The following links are displayed on this tab:
      • P2P is the Point-to-Point transport service (P2P service). You can configure a P2P service.
      • P2M is the Point-to-Multipoint transport service (P2M service). You can configure a P2M service.
      • M2M is a Multipoint-to-Multipoint transport service (M2M service). You can configure an M2M service.

      The remaining links are relevant to network communication at the VIM level and are established between VNFs hosted by the OpenStack cloud platform:

      • OS shared is the shared network through which the shared network service connects to network services. You can configure a shared network.
      • OS vRouter is the virtual L3 router. You can configure a virtual router.
      • OS VLAN is the VLAN for transmitting tagged L2 traffic of the 802.1Q standard You can configure a VLAN.
      • OS VXLAN is a VXLAN for tunneling. You can configure a VXLAN.
      • OS flat is the flat network for transmitting untagged L2 traffic You can configure a flat network.
   3. Select the UNI tab and drag CPE device UNIs to the graphical design tool. The tab displays two components, UNI and WAN. Both components designate abstract UNIs that the tenant must replace with real UNIs when creating or editing a network service. The WAN component refers to UNIs that connect to the WAN.

      You can configure a UNI in the topology.

   The components are added to the topology and displayed in the graphical design tool.

4. Connect the network service components added to the topology to each other:
   1. Click the link to which you want to connect a network service component.
   2. Click Add leaf to connect a network service component with the leaf role to the link. If you clicked a P2M service, you can click Add root to connect a network service component with the root role to the link.
   3. Click the network service component that you want to connect to the link. If you clicked a network function or shared network service, select the port to connect the link to in the displayed window.

   The network service component is connected to the link, and a line is displayed between them in the topology. For example, the figure below shows the VLAN to which a virtual network function is connected.

   

5. If you want to assign backup UNIs:

   A backup UNI can be assigned only for UNIs which are connected to at least one link.

   1. Click the UNI for which you want to assign a backup UNI.
   2. Click Reserve.
   3. Click the UNI that you want to use as the backup.

   The UNI is designated as the backup UNI, and a dotted line is displayed between the UNI, the backup UNI, and the link to which the UNI is connected. For example, in the figure below, the WAN is the backup interface for the UNI.

   

6. If you want to remove a network service component from the topology, click the component, then click Delete.

   The network service component is removed from the topology and is no longer displayed in the graphical design tool.

7. If you want to horizontally align the topology, click Arrange.
8. If you do not want to hide the descriptions of the added network service components in the topology, clear the Description check box. This check box is selected by default.
9. In the Name field, enter the name of the network service.
10. In the upper part of the graphical design tool, click Save.

The network service template is created and displayed in the Catalog pane, on the Templates tab.

Editing a network service template

When you edit a network service template, the changes are not applied to network services that have already been created and deployed using the network service template.

To edit a network service template:

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

   The network service management page is displayed.

2. In the Catalog pane, select the Templates tab.

   A list of network service templates is displayed.

3. Click the network service template that you want to edit.

   The graphical design tool for building the topology is displayed.

4. Edit the settings of the network service template. For a description of the settings, see the instructions for creating a network service template.
5. In the upper part of the graphical design tool, click Save.

The network service template is modified and updated in the Templates tab.

Deleting a network service template

Deleted network service templates cannot be restored.

To delete a network service template:

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

   The network service management page is displayed.

2. In the Catalog pane, select the Templates tab.

   A list of network service templates is displayed.

3. Click the delete icon next to the network service template that you want to delete.
4. In the confirmation window, click Delete.

The network service template is deleted and is no longer displayed in the Templates tab.

Managing network services

The list of network services is displayed on the self-service portal in the Infrastructure section, on the Network services pane. Before managing network services, you must log in to the tenant's self-service portal.

Creating a network service

To create a network service:

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

   The network service management page is displayed.

2. In the upper part of the Network services pane, click + Network service.

   The graphical design tool for building the topology is displayed.

3. Add network service components to the topology:
   1. Drag network server components from the Catalog pane into the graphical design tool. The pane displays the following network service components:
      • Network service templates — when you add a network service template to a topology, the topology is constructed in accordance with the network service template. You can add multiple network service templates to the topology.
      • Shared network services — you must add a shared network service to the topology of network services that you want to connect to the shared network service. You can specify a brief description of the shared network service.
      • Virtual and physical network functions. The actions that you can perform on virtual and physical network functions are described in the Managing virtual network functions and Managing physical network functions sections.
   2. Drag and drop links from the Links tab into the graphical design tool. The following links are displayed on this tab:
      • P2P is the Point-to-Point transport service (P2P service). You can configure a P2P service.
      • P2M is the Point-to-Multipoint transport service (P2M service). You can configure a P2M service.
      • M2M is a Multipoint-to-Multipoint transport service (M2M service). You can configure an M2M service.

      The remaining links are relevant to network communication at the VIM level and are established between VNFs hosted by the OpenStack cloud platform:

      • OS shared is the shared network through which the shared network service connects to network services. You can configure a shared network.
      • OS vRouter is the virtual L3 router. You can configure a virtual router.
      • OS VLAN is the VLAN for transmitting tagged L2 traffic of the 802.1Q standard You can configure a VLAN.
      • OS VXLAN is a VXLAN for tunneling. You can configure a VXLAN.
      • OS flat is the flat network for transmitting untagged L2 traffic You can configure a flat network.
   3. Select the UNI tab and drag CPE device UNIs to the graphical design tool. If you are using a network service template, you must replace the abstract UNIs in the topology with real UNIs. Abstract UNIs can be designated by two components, UNI and WAN. The WAN component refers to UNIs that connect to the WAN.

      You can configure a UNI.

4. Connect the network service components added to the topology to each other:
   1. Click the link to which you want to connect a network service component.
   2. Click Add leaf to connect a network service component with the leaf role to the link. If you clicked a P2M service, you can click Add root to connect a network service component with the root role to the link.
   3. Click the network service component that you want to connect to the link. If you clicked a network function or shared network service, select the port to connect the link to in the displayed window.

   The network service component is connected to the link, and a line is displayed between them in the topology. For example, the figure below shows the VLAN to which a virtual network function is connected.

   

5. If you want to assign backup UNIs:

   A backup UNI can be assigned only for UNIs which are connected to at least one link.

   1. Click the UNI for which you want to assign a backup UNI.
   2. Click Reserve.
   3. Click the UNI that you want to use as the backup.

   The UNI is designated as the backup UNI, and a dotted line is displayed between the UNI, the backup UNI, and the link to which the UNI is connected. For example, in the figure below, the WAN is the backup interface for the UNI.

   

6. If you want to remove a network service component from the topology, click the component, then click Delete.

   The network service component is removed from the topology and is no longer displayed in the graphical design tool.

7. If you want to horizontally align the topology, click Arrange.
8. If you do not want to hide the descriptions of the added network service components in the topology, clear the Description check box. This check box is selected by default.
9. In the Name field, enter the name of the network service.
10. Finish creating the network service in one of the following ways:
    • To save the network service, click Save.
    • To save and deploy the network service, click Deploy.

The network service is created and displayed in Network services pane. If you clicked Deploy, the deployment of the network service begins, which may take several minutes. You can interrupt the deployment by clicking Abort deploy.

Editing a network service

To edit a network service:

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

   The network service management page is displayed.

2. In the Network services pane, select the network service that you want to edit.

   The graphical design tool for building the topology is displayed.

3. In the upper part of the graphical design tool, click Edit.
4. If necessary, edit the settings of the network service. For a description of the settings, see the instructions for creating a network service.
5. Finish editing the network service in one of the following ways:
   • If you are editing a network service that is not deployed, do one of the following:
     • To save the network service, click Save.
     • To save and deploy the network service, click Deploy.
   • If you are editing a deployed network service, click Deploy changes to deploy the modified network service.

The network service is modified and updated in Network services pane. If you clicked Deploy or Deploy changes, deployment begins, which may take several minutes. You can interrupt the deployment by clicking Abort deploy.

Deploying a network service

If a virtual network function deployed on a uCPE device is added to the network service topology and there is connectivity between the orchestrator and the uCPE device, this network service is deployed when connectivity is restored.

To deploy a network service:

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

   The network service management page is displayed.

2. In the Network services pane, select the network service that you want to deploy.

   The graphical design tool for building the topology is displayed.

3. In the upper part of the graphical design tool, click Edit.
4. Click Deploy.

This starts the deployment of the network service, which may take several minutes. You can interrupt the deployment by clicking Abort deploy.

Checking the consistency of a network service

The consistency check allows verifying that the components are added to the network service topology actually exist.

To check the consistency of a network service:

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

   The network service management page is displayed.

2. In the Network services pane, click the settings icon → Check consistency next to the network service whose consistency you want to check.
3. In the confirmation window, click Confirm.

This begins the consistency check of the network service.

Redeploying a network service

Redeploying a network service may result in short-term interruptions or temporary inoperability. When planning redeployment activities, we recommend taking into account your organization's circumstances to minimize the disruptions.

To redeploy a network service:

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

   The network service management page is displayed.

2. In the Network services pane, click the settings icon → Redeploy next to the network service that you want to redeploy.
3. In the confirmation window, click Confirm.

This starts the redeployment of the network service, which may take several minutes. You can interrupt the deployment by clicking Abort deploy.

Disabling or enabling auto-healing for a network service

The Zabbix server monitors network service components and sends a REST API request to the orchestrator whenever a problem is detected. If the auto-healing functionality is enabled for the network service, the orchestrator initiates auto-healing for components with problems. By default, this functionality is enabled.

To disable or enable auto-healing for a network service:

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

   The network service management page is displayed.

2. In the Network services pane, click the settings icon → Disable Auto-Healing or Enable Auto-Healing next to the network service for which you want to disable or enable auto-healing.

Auto-healing is disabled or enabled for the network service.

You can perform auto-healing of virtual network functions or their VDUs even if auto-healing is disabled for the network service.

Viewing the network service log

To view the log of a network service:

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

   The network service management page is displayed.

2. In the Network services pane, click the settings icon → Open log next to the network service whose log you want to view.

The page with the network service log is displayed.

Deleting a network service

Deleted network services cannot be restored.

To delete a network service:

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

   The network service management page is displayed.

2. In the Network services pane, click the settings icon → Delete next to the network service that you want to delete.
3. In the confirmation window, click Delete.

The network service is deleted and is no longer displayed in the Network services pane.

Scenario: Deploying a virtual network function

You can deploy a virtual network function for a tenant in a network service. The lifecycle of virtual network functions is managed by an orchestrator. To deploy virtual network functions, you need the OpenStack cloud platform.

For example, you can deploy a virtual network function at the central office of your organization to protect user traffic that is transmitted between CPE devices.

Virtual network function deployment involves the following steps:

1. Preparing a VNF package

   Prepare the VNF package that you want to deploy, and then upload the VNF package to the orchestrator web interface. If necessary, you can enable protection of VNF and PNF packages against substitution before uploading the VNF package to the orchestrator web interface.

2. Ensuring network connectivity between the orchestrator and the OpenStack cloud platform

   Ensure network connectivity between the virtual machine or physical server where the orchestrator is deployed and the OpenStack cloud platform.

3. Assigning the virtual network function to a tenant

   Use one of the following methods to assign the virtual network function to the tenant for which you want to deploy it:

   • If you want to deploy a virtual network function using a network service template:
     1. Add the virtual network function to the topology when creating or editing a network service template.
     2. If necessary, configure the topology of the network service template and the virtual network function. For a description of what you can do with virtual network functions, see the Managing virtual network functions section.
     3. Assign the network service template to a tenant.
   • If you want to deploy a virtual network function without a network service template, assign the virtual network function to the tenant.
4. Logging in to the tenant self-service portal

   Log in to the tenant self-service portal

5. Deploying the virtual network function

   Do the following:

   1. Add the virtual network function to the topology when creating or editing a network service in one of the following ways:
      • If you want to deploy a virtual network function using a network service template, add the network service template to the topology.
      • If you want to deploy a virtual network function without a network service template, add the virtual network function to the topology.
   2. If necessary, configure the topology of the network service and the virtual network function. For a description of what you can do with virtual network functions, see the Managing virtual network functions section.
   3. Deploy the virtual network function using one of the following methods:
      • If you added the virtual network function to the topology while creating the network service, deploy the network service.
      • If you added the virtual network function to the topology while editing a network service, deploy the modified network service.

The virtual network function is deployed.

Scenario: Deploying a physical network function

You can deploy a physical network function for a tenant in a network service. As physical network functions, you can use dedicated hardware as well as virtual entities created using third-party virtualization environments. The orchestrator does not manage the lifecycle of physical network functions.

For example, you can deploy a physical network function at the central office of your organization to protect user traffic that is transmitted between CPE devices.

Physical network function deployment involves the following steps:

1. Preparing the PNF package

   Prepare the PNF package that you want to deploy, and then upload the PNF package to the orchestrator web interface. If necessary, you can enable protection of VNF and PNF packages against substitution before uploading the PNF package to the orchestrator web interface.

2. Ensuring network connectivity between the orchestrator and the physical network function

   Ensure network connectivity between the virtual machine or physical server on which the orchestrator is deployed and the dedicated hardware or virtual entity on which you want to deploy the physical network function.

3. Assigning the physical network function to a tenant

   Use one of the following methods to assign the physical network function to the tenant for which you want to deploy it:

   • If you want to deploy a physical network function using a network service template:
     1. Add the physical network function to the topology when creating or editing a network service template.
     2. If necessary, configure the topology of the network service template and the physical network function. For a description of what you can do with physical network functions, see the Managing physical network functions section.
     3. Assign the network service template to a tenant.
   • If you want to deploy a physical network function without a network service template, assign the physical network function to the tenant.
4. Logging in to the tenant self-service portal

   Log in to the tenant self-service portal

5. Deploying a physical network function

   Do the following:

   1. Add the physical network function to the topology when creating or editing a network service in one of the following ways:
      • If you want to deploy a physical network function using a network service template, add the network service template to the topology.
      • If you want to deploy a physical network function without a network service template, add the physical network function to the topology.
   2. If necessary, configure the topology of the network service and the physical network function. For a description of what you can do with physical network functions, see the Managing physical network functions section.
   3. Deploy the physical network function using one of the following methods:
      • If you added the physical network function to the topology while creating the network service, deploy the network service.
      • If you added the physical network function to the topology while editing a network service, deploy the modified network service.

The physical network function is deployed.

Managing VNF and PNF packages

A VNF or PNF package is a ZIP archive in which you must place the following components to deploy a network function and manage its lifecycle:

• The VNF/PNF descriptor, a file with parameters of the network function.
• The /image directory, which contains virtual machine images in the QCOW format for deploying the virtual network function. This directory is not included in the PNF package.
• The /scripts directory, which contains scripts for deploying and managing the network function.
• logo.png, the icon of the network function. This component is optional.
• description-file.pdf, technical documentation or specification of the network function. This component is optional.

You must upload the VNF or PNF package to the orchestrator web interface to add a virtual or physical network function to the topology when managing a network service template or network service.

Configuring the VNF descriptor

Expand all | Collapse all

Specify the settings of the virtual network function in a VNF descriptor in YAML or XML format, then add the VNF descriptor to the root directory of the VNF package. A VNF descriptor has the following structure:

VNF descriptor example

external_connections

The external_connections section has the following structure:

Example of this section

internal_connections

The internal_connections section has the following structure:

Example of this section

virtual_links

The virtual_links section has the following structure:

Example of this section

images

The images section has the following structure:

Example of this section

configurations

The configurations section has the following structure:

Example of this section

flavours

The flavours section has the following structure:

The affinity and anti-affinity sections have the following structure:

The management section has the following structure:

The vdus section has the following structure:

Example of this section

scaling

The scaling section has the following structure:

Example of this section

user_configurations

The user_configurations section has the following structure:

Example of this section

backups

The backups section has the following structure:

Example of this section

Configuring the PNF descriptor

Expand all | Collapse all

Specify the settings of the physical network function in a PNF descriptor in YAML or XML format, then add the PNF descriptor to the root directory of the PNF package. A PNF descriptor has the following structure:

PNF descriptor example

external_connections

The external_connections section has the following structure:

Example of this section

internal_connections

The internal_connections section has the following structure:

Example of this section

configurations

The configurations section has the following structure:

Example of this section

flavours

The flavours section has the following structure:

The management section has the following structure:

The vdus section has the following structure:

Example of this section

scaling

The scaling section has the following structure:

Example of this section

user_configurations

The user_configurations section has the following structure:

Example of this section

backups

The backups section has the following structure:

Example of this section

Protection of VNF and PNF packages against substitution and modification

Some VNF and PNF package files are placed in the local directory of the Docker container of the orchestrator, and you can protect them against substitution and modification. When VNF and PNF packages are protected, the orchestrator automatically computes their SHA256 hash when they are uploaded to the orchestrator web interface. When accessing files in the local directory of the Docker container, the orchestrator compares their current SHA256 hash with the previously saved hash. If the SHA256 hashes do not match, the orchestrator prevents users from performing actions with the network function, such as adding it to the topology of a network service.

To protect of VNF and PNF packages against substitution and modification:

1. In the lower part of the menu, click the settings icon → Storage security.
2. This opens a window, in that window, select the Calculate hash sum SHA256 for VNF/PNF files on storage check box. This check box is cleared by default.

VNF and PNF packages are protected against substitution and modification.

Uploading a VNF or PNF package to the orchestrator web interface

To upload a VNF or PNF package to the orchestrator web interface:

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

   The network service management page is displayed.

2. In the upper part of the page, click + VNF or + PNF.
3. This opens a window; in that window, select the VNF or PNF package.
4. If you want to check the integrity of the VNF or PNF package, enter its SHA256 hash in the Hash sum SHA256 field. Maximum length: 64 characters.
5. Click Save.

The VNF or PNF package is uploaded to the orchestrator web interface. The VNF or PNF is displayed in the Catalog pane. If you entered a SHA256 hash of a VNF or PNF package, the orchestrator compares the hash you entered with the actual SHA256 hash. If the SHA256 hashes do not match, the VNF or PNF package is not uploaded.

Specifying a brief description of a shared network service

You can specify a brief description of the shared network service.

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 graphical design tool, click the shared network service for which you want to specify a brief description.

   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 . By default, the Settings tab is selected, which displays a brief description of the shared network service.

3. In the Description field, enter a brief description of the shared network service.
4. In the upper part of the settings area, click Save to save shared network service settings.

Managing virtual network functions

To manage a virtual network function, do one of the following:

• On the administrator portal, go to the Catalog section, and in the Catalog pane, click the virtual network function.
• When creating or editing a network service template in the topology, click the virtual network function.
• When creating or editing a network service in the topology, click the virtual network function.

Virtual network function settings are displayed on the following tabs:

• Flavours contains flavours of the virtual network function.
• Connection points contains external connection points of the virtual network function.
• VNF settings contains basic settings of the virtual network function.
• Placement contains placement settings of the virtual network function. You can place a virtual network function in a data center or on a uCPE device. This tab is displayed if you clicked the virtual network function when creating or editing a network service.

The following tabs are displayed if you clicked the virtual network function in the topology of a deployed network service:

• VDU management is a table of VDUs that are part of the virtual network function. Information about VDUs is displayed in the following columns of the table:
  • Name is the name of the VDU.
  • Instance name is the ID of the VDU instance.
  • Mgmt IP is the IP address that the management subnet has assigned to the VDU.
  • vCPU is the number of virtual CPU cores assigned to the VDU.
  • RAM is the amount of RAM assigned to the VDU.
  • Disk is the amount of disk space assigned to the VDU.
• Monitoring contains monitoring results of the virtual network function.
• Problems contains problems that occurred during the operation of the virtual network function. In case of any problems, a red exclamation mark is displayed next to the tab.

Additionally, the tabs that you specified in the user_configurations section of the VNF descriptor may be displayed.

Selecting the flavour of a virtual network function

You can specify flavours in the flavours section of the VNF descriptor.

To select a virtual network function flavour:

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. Click the virtual network function for which you want to select a deployment option.

   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 . By default, the Flavours tab is selected, which displays flavours.

3. Select a flavour for the virtual network function.
4. In the upper part of the settings area, click Save to save virtual network function settings.

Configuring external connection points of a virtual network function

You can specify external connection points of a virtual network function in the external_connections section of the VNF descriptor.

To configure external connection points of the virtual network function:

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. Click the virtual network function for which you want to configure external connection points.

   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 . By default, the Flavours tab is selected, which displays flavours.

3. Select the Connection points tab.

   This displays the external connection points of the virtual network function.

4. In the Type drop-down list, select how you want to assign an IPv4 prefix to the external connection point:
   • DHCP reservation to use DHCP to assign an IPv4 prefix to the external mount point. If you select this option, do the following:
     1. In the IP field, enter the IPv4 address that DHCP assigns to the external connection point.
     2. In the Mask field, enter the subnet mask that DHCP assigns to the external connection point.
   • AUTO to automatically assign an IPv4 prefix to the external connection point. Default value.
5. In the Description field, enter a brief description of the external connection point.
6. If you want to designate the connection point as the trunk port, select the Trunk check box. This check box is cleared by default.
7. In the upper part of the settings area, click Save to save virtual network function settings.

Basic settings of a virtual network function

To edit basic settings of the virtual network function:

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. Click the virtual network function for which you want to configure basic settings.

   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 . By default, the Flavours tab is selected, which displays flavours.

3. Select the VNF settings tab.

   Basic settings of the virtual network function are displayed.

4. In the Name field, enter the name of the virtual network function.
5. In the Description field, enter a brief description of the virtual network function.
6. In the Order field, enter the sequence number for deploying the virtual network function on the OpenStack cloud platform. When you deploy a network service, the virtual network function with the lowest number is the first to be deployed. If none of the virtual network functions added to the network service topology have a sequence number specified, all virtual network functions are deployed simultaneously.
7. In the upper part of the settings area, click Save to save virtual network function settings.

Hosting the virtual network function in a data center and on a uCPE device

To place a virtual network function in a data center or on a uCPE device.

1. Navigate to the topology by starting to create or edit a network service.
2. Click the virtual network function that you want to place in a data center or on a uCPE device.

   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 . By default, the Flavours tab is selected, which displays flavours.

3. Select the Placement tab.

   Placement settings of the virtual network function are displayed.

4. In the Select placement type list, select one of the following values:
   • Data center to place the virtual network function in the specified data center. If you select this option, do the following:
     1. In the Data center field, enter the name of the created data center. As you type the name, you are prompted to select a data center from a drop-down list.
     2. In the VIM field, enter the name of the deployed VIM for the VNF. As you type the name, you are prompted to select a VIM from a drop-down list.
   • uCPE to place the VNF on the specified uCPE device. If you select this option, in the uCPE field, enter the name of the uCPE device. As you type the name, you are prompted to select an uCPE from a drop-down list.
5. In the upper part of the settings area, click Save to save virtual network function settings.

Stopping or starting a virtual network function or a VDU that is part of it

You can stop a virtual network function or a VDU that is part of it to free up the computational resources of the OpenStack cloud platform.

When you start a virtual network function or VDU, it begins consuming computational resources again. This restarts the processes running on the virtual network function or VDU.

To stop or start a virtual network function or a VDU that is part of it:

1. On the self-service portal, go to the Catalog menu section.

   The network service management page is displayed.

2. In the Network services pane, click the deployed network service to whose topology the virtual network function has been added.

   The topology is displayed.

3. Click the virtual network function.

   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 . By default, the Flavours tab is selected, which displays flavours.

4. If you want to stop or start the virtual network function, in the upper part of the settings area, click the Management → Power → Stop VNF or Start VNF.
5. If you want to stop or start a VDU that is part of the virtual network function:
   1. Select the VDU management tab.

      A table of VDUs is displayed.

   2. Click Management → Power → Stop VDU or Start VDU next to the VDU that you want to stop or start.
6. In the confirmation window, click Apply.

The virtual network function or its VDU is stopped or started.

Pausing or unpausing a virtual network function or a VDU that is part of it

You can pause a virtual network function or a VDU that is part of it to pause processes running on it. However, the virtual network function or VDU continues to consume the computational resources of the OpenStack cloud platform. When you unpause a virtual network function or VDU, processes running on it are resumed.

To pause or unpause a virtual network function or a VDU that is part of it:

1. On the self-service portal, go to the Catalog menu section.

   The network service management page is displayed.

2. In the Network services pane, click the deployed network service to whose topology the virtual network function has been added.

   The topology is displayed.

3. Click the virtual network function.

   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 . By default, the Flavours tab is selected, which displays flavours.

4. Pause or unpause the virtual network function or a VDU that is part of it:
   • If you want to pause or unpause a virtual network function, in the upper part of the settings area, click Management → Pause VNF → Power or Unpause VNF.
   • If you want to pause or unpause a VDU that is part of the virtual network function:
     1. Select the VDU management tab.

        A table of VDUs is displayed.

     2. Click Management → Power → Pause VDU or Unpause VDU.
5. In the confirmation window, click Apply.

The virtual network function or its VDU is paused or unpaused.

Suspending or unsuspending a virtual network function or a VDU that is part of it

You can suspend a virtual network function or a VDU that is part of it to free up the computational resources of the OpenStack cloud platform. This saves the state of the virtual network function or VDU to the disk of the OpenStack virtual platform. When you unsuspend the virtual network function or VDU, it begins consuming computational resources again. Processes running on a virtual network function or VDU are resumed from the point at which its state was saved.

To suspend or unsuspend a virtual network function or its VDU:

1. On the self-service portal, go to the Catalog menu section.

   The network service management page is displayed.

2. In the Network services pane, click the deployed network service to whose topology the virtual network function has been added.

   The topology is displayed.

3. Click the virtual network function.

   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 . By default, the Flavours tab is selected, which displays flavours.

4. Suspend or unsuspend a virtual network function or its VDU:
   • If you want to suspend or unsuspend a virtual network function, in the upper part of the settings area, click Management → Suspend VNF → Power or Resume suspended VNF.
   • If you want to suspend or unsuspend a VDU that is part of the virtual network function:
     1. Select the VDU management tab.

        A table of VDUs is displayed.

     2. Click Management → Power → Suspend VDU or Resume suspended VDU next to the VDU that you want to suspend or unsuspend.
5. In the confirmation window, click Apply.

The virtual network function or its VDU is suspended or unsuspended.

Soft rebooting a virtual network function or a VDU that is part of it

When a virtual network function is soft rebooted, all active VDUs in it are restarted. To soft reboot a virtual network function, at least one VDU in it must not be suspended.

To perform a soft reboot of a virtual network function or a VDU that is part of it:

1. On the self-service portal, go to the Catalog menu section.

   The network service management page is displayed.

2. In the Network services pane, click the deployed network service to whose topology the virtual network function has been added.

   The topology is displayed.

3. Click the virtual network function.

   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 . By default, the Flavours tab is selected, which displays flavours.

4. Perform a soft reboot of a virtual network function or its VDU:
   • If you want to perform a soft reboot of the virtual network function, in the upper part of the settings area, click Management → Power → Soft reboot VNF.
   • If you want to soft reboot a VDU that is part of the virtual network function:
     1. Select the VDU management tab.

        A table of VDUs is displayed.

     2. Click Management → Power → Soft reboot VDU next to the VDU that you want to soft reboot.
5. In the confirmation window, click Apply.

The virtual network function or its VDU is soft rebooted.

Hard rebooting of a virtual network function or a VDU that is part of it

A hard reboot imitates turning power on and off again. We recommend that performing a hard reboot only if soft reboot is not successful.

To perform a hard reboot of a virtual network function or a VDU that is part of it:

1. On the self-service portal, go to the Catalog menu section.

   The network service management page is displayed.

2. In the Network services pane, click the deployed network service to whose topology the virtual network function has been added.

   The topology is displayed.

3. Click the virtual network function.

   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 . By default, the Flavours tab is selected, which displays flavours.

4. To perform a hard reboot of a virtual network function or its VDU:
   • If you want to perform a hard reboot of the virtual network function, in the upper part of the settings area, click Management → Power → Hard reboot VNF.
   • If you want to hard reboot a VDU that is part of the virtual network function:
     1. Select the VDU management tab.

        A table of VDUs is displayed.

     2. Click Management → Power → Hard reboot VDU next to the VDU that you want to hard reboot.
5. In the confirmation window, click Apply.

A hard reboot of the VNF or its VDU is performed.

Redeploying a virtual network function or a VDU that is part of it

Redeployment of a virtual network function or a VDU that is part of it may result in short-term interruptions or temporary loss of function. When planning and coordinating redeployment activities, we recommend taking into account your organization's circumstances to minimize the disruptions.

To redeploy a virtual network function or a VDU that is part of it:

1. On the self-service portal, go to the Catalog menu section.

   The network service management page is displayed.

2. In the Network services pane, click the deployed network service to whose topology the virtual network function has been added.

   The topology is displayed.

3. Click the virtual network function.

   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 . By default, the Flavours tab is selected, which displays flavours.

4. To redeploy a virtual network function or its VDU:
   • If you want to redeploy the virtual network function, in the upper part of the configuration area, click Management → Redeploy VNF.
   • If you want to redeploy a VDU that is part of the virtual network function:
     1. Select the VDU management tab.

        A table of VDUs is displayed.

     2. Click Management → Healing VDU next to the VDU that you want to redeploy.
5. In the confirmation window, click Confirm.

Redeployment of the virtual network function or its VDU begins, which may take several minutes. You can interrupt the deployment by clicking Abort deploy.

Auto-healing a virtual network function or a VDU that is part of it

You can auto-heal a virtual network function or a VDU that is part of it, even if you have disabled auto-healing of the network service to whose topology this virtual network function has been added.

To auto-heal a virtual network function or a VDU that is part of it:

1. On the self-service portal, go to the Catalog menu section.

   The network service management page is displayed.

2. In the Network services pane, click the deployed network service to whose topology the virtual network function has been added.

   The topology is displayed.

3. Click the virtual network function.

   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 . By default, the Flavours tab is selected, which displays flavours.

4. Perform auto-healing of the virtual network function or its VDU.
   • If you want to auto-heal the virtual network function, in the upper part of the settings area, click Management → Healing VNF.
   • If you want to auto-heal a VDU that is part of the virtual network function:
     1. Select the VDU management tab.

        A table of VDUs is displayed.

     2. Click Management → Healing VNF next to the VDU that you want to auto-heal.
5. In the confirmation window, click Apply.

Auto-healing of the virtual network function or a VDU that is part of it begins.

Managing VDU snapshots

To display the table of VDU snapshots, click the virtual network function in the topology of the deployed network service, select the VDU management tab, and click Management → Snapshot next to the VDU.

Information about VDU snapshots is displayed in the following columns of the table:

• Name is the name of the VDU snapshot.
• Created at is the date and time when the VDU snapshot was created.
• Size is the size of the VDU snapshot.
• Description is a brief description of the VDU snapshot.
• Management contains actions that can be performed on the VDU snapshot.

Creating a VDU snapshot

We do not recommend storing snapshots for a long time because their existence reduces the performance of the VDU.

To take a VDU snapshot:

1. On the self-service portal, go to the Catalog menu section.

   The network service management page is displayed.

2. In the Network services pane, click the deployed network service to whose topology the virtual network function has been added.

   The topology is displayed.

3. Click the virtual network function that includes the VDU.

   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 . By default, the Flavours tab is selected, which displays flavours.

4. Select the VDU management tab.

   A table of VDUs is displayed.

5. Click Power → Snapshot next to the VDU for which you want to create a snapshot.

   This opens a window with the table of VDU snapshots.

6. In the Name field, enter a name for the VDU snapshot.
7. In the Description field, enter a brief description of the VDU snapshot.
8. Click Create.

A snapshot of the VDU is created and displayed in the table.

Restoring VDU settings using a snapshot

To restoring VDU settings using a snapshot:

1. On the self-service portal, go to the Catalog menu section.

   The network service management page is displayed.

2. In the Network services pane, click the deployed network service to whose topology the virtual network function has been added.

   The topology is displayed.

3. Click the virtual network function that includes the VDU.

   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 . By default, the Flavours tab is selected, which displays flavours.

4. Select the VDU management tab.

   A table of VDUs is displayed.

5. Click Power → Snapshot next to the VDU whose settings you want to restore using the snapshot.

   This opens a window with the table of VDU snapshots.

6. Click Management → Revert next to the snapshot which you want to use to restore the VDU settings.
7. In the confirmation window, click Revert.

The VDU settings are restored in accordance with the snapshot.

Editing a VDU snapshot

To edit a VDU snapshot:

1. On the self-service portal, go to the Catalog menu section.

   The network service management page is displayed.

2. In the Network services pane, click the deployed network service to whose topology the virtual network function has been added.

   The topology is displayed.

3. Click the virtual network function that includes the VDU.

   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 . By default, the Flavours tab is selected, which displays flavours.

4. Select the VDU management tab.

   A table of VDUs is displayed.

5. Click Power → Snapshot next to the VDU whose snapshot you want to edit.

   This opens a window with the table of VDU snapshots.

6. Click Management → Edit next to the VDU snapshot that you want to edit.
7. This opens a window; in that window, if necessary, edit the name and/or description of the VDU snapshot.
8. Click Save.

The VDU snapshot is modified and updated in the table.

Deleting a VDU snapshot

Deleted VDU snapshots cannot be restored.

To delete a VDU snapshot:

1. On the self-service portal, go to the Catalog menu section.

   The network service management page is displayed.

2. In the Network services pane, click the deployed network service to whose topology the virtual network function has been added.

   The topology is displayed.

3. Click the virtual network function that includes the VDU.

   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 . By default, the Flavours tab is selected, which displays flavours.

4. Select the VDU management tab.

   A table of VDUs is displayed.

5. Click Power → Snapshot next to the VDU whose snapshot you want to delete.

   This opens a window with the table of VDU snapshots.

6. Click Management → Delete next to the VDU snapshot that you want to delete.
7. In the confirmation window, click Delete.

The VDU snapshot is deleted and is no longer displayed in the table.

Managing physical network functions

To manage a physical network function, do one of the following:

• On the administrator portal, go to the Catalog section, and in the Catalog pane, click the physical network function.
• When creating or editing a network service template in the topology, click the physical network function.
• When creating or editing a network service in the topology, click the physical network function.

Physical network function settings are displayed on the following tabs:

• Flavours contains flavours of the physical network function.
• VNF settings contains basic settings of the physical network function.

The following tabs are displayed if you clicked the physical network function in the topology of a deployed network service:

• Monitoring contains monitoring results of the physical network function.
• Problems contains problems that occurred during the operation of the physical network function. In case of any problems, a red exclamation mark is displayed next to the tab.

Additionally, the tabs that you specified in the user_configurations section of the PNF descriptor may be displayed.

Selecting the flavour of a physical network function

You can specify flavours in the flavours section of the PNF descriptor.

To select a physical network function flavour:

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. Click the physical network function for which you want to select a deployment option.

   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 . By default, the Flavours tab is selected, which displays flavours.

3. Select a flavour for the physical network function.
4. In the upper part of the settings area, click Save to save physical network function settings.

Basic settings of a physical network function

To edit basic settings of the physical network function:

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. Click the physical network function for which you want to configure basic settings.

   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 . By default, the Flavours tab is selected, which displays flavours.

3. Select the PNF settings tab.

   Basic settings of the physical network function are displayed.

4. In the Name field, enter the name of the physical network function.
5. In the Description field, enter a brief description of the physical network function.
6. In the Order field, enter the sequence number for deploying the physical network function on the OpenStack cloud platform. When you deploy a network service, the physical network function with the lowest number is the first to be deployed. If none of the physical network functions added to the topology have a sequence number specified, all physical network functions are deployed simultaneously.
7. In the upper part of the settings area, click Save to save physical network function settings.

Configuring a P2P service

To configure a P2P service:

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. Click the P2P 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 P2P service.
4. If necessary, in the Description field, enter a brief description of the P2P service.
5. In the upper part of the settings area, click Save to save P2P service settings.

Configuring a P2M service

To configure a P2M service:

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. 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 P2M service.
4. If necessary, in the Description field, enter a brief description of the P2M service.
5. In the Connection points field, enter the maximum number of P2M 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 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.
7. 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.
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 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.

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. Default value: 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 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.
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 value is Disable.
    2. In the CIDR field, enter the IPv4 prefix of the OpenStack subnet that assigns 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 of IP addresses from which the OpenStack subnet assigns IP addresses to virtual network functions: To do so, under Pools, click + Pooland enter the starting and ending values of the IP address range.

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

    5. Specify the DNS server that the OpenStack subnet assigns to virtual network functions. To do so, under DNS, click + DNS and 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 or delete a DNS server. To delete a DNS server, click Delete next to it.

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

Configuring an M2M service

To configure an M2M service:

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. Click the M2M 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 M2M service.
4. If necessary, in the Description field, enter a brief description of the M2M service.
5. In the Connection points field, enter the maximum number of M2M 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 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.
7. 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.

8. 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. Default value: 100.
9. 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.
10. 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 value is Disable.
    2. In the CIDR field, enter the IPv4 prefix of the OpenStack subnet that assigns 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 of IP addresses from which the OpenStack subnet assigns IP addresses to virtual network functions: To do so, under Pools, click + Pooland enter the starting and ending values of the IP address range.

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

    5. Specify the DNS server that the OpenStack subnet assigns to virtual network functions. To do so, under DNS, click + DNS and 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 or delete a DNS server. To delete a DNS server, click Delete next to it.

11. If you want to use an M2M service to create a shared network service, select the Share network service check box. This check box is cleared by default.
12. In the upper part of the settings area, click Save to save M2M service settings.

Configuring a shared network (OS 2 SHARED)

To configure a shared network 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. Click the shared network 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 shared network.
4. If necessary, in the Description field, enter a brief description of the shared network.
5. In the upper part of the settings area, click Save to save shared network settings.

Configuring a virtual router (OS vRouter)

To configure a virtual router:

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. Click the virtual router 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 virtual router.
4. If necessary, in the Description field, enter a brief description of the virtual router.
5. If you want to set the 'up' value for the operating state of the virtual router, select the Administrative state check box. This check box is cleared by default.
6. In the upper part of the settings area, click Save to save virtual router settings.

Configuring a VLAN

To configure a VLAN:

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. Click the VLAN 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 VLAN.
4. If necessary, in the Description field, enter a brief description of the VLAN.
5. 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 value is Disable.
   2. In the CIDR field, enter the IPv4 prefix of the OpenStack subnet that assigns 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 of IP addresses from which the OpenStack subnet assigns IP addresses to virtual network functions: To do so, under Pools, click + Pooland enter the starting and ending values of the IP address range.

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

   5. Specify the DNS server that the OpenStack subnet assigns to virtual network functions. To do so, under DNS, click + DNS and 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 or delete a DNS server. To delete a DNS server, click Delete next to it.

6. If you want to use the VLAN to create a shared network service, select the Share network check box. This check box is cleared by default.
7. If you want to assign a VLAN tag to virtual network functions, in the Segmentation ID field, enter the VLAN tag.
8. In the upper part of the settings area, click Save to save VLAN settings.

Configuring a VXLAN

To configure a VXLAN:

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. Click the VXLAN 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 VXLAN.
4. If necessary, in the Description field, enter a brief description of the VXLAN.
5. 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 value is Disable.
   2. In the CIDR field, enter the IPv4 prefix of the OpenStack subnet that assigns 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 of IP addresses from which the OpenStack subnet assigns IP addresses to virtual network functions: To do so, under Pools, click + Pooland enter the starting and ending values of the IP address range.

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

   5. Specify the DNS server that the OpenStack subnet assigns to virtual network functions. To do so, under DNS, click + DNS and 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 or delete a DNS server. To delete a DNS server, click Delete next to it.

6. If you want to use the VXLAN to create a shared network service, select the Share network check box. This check box is cleared by default.
7. If you want to assign a VXLAN tag to virtual network functions, in the Segmentation ID field, enter the VXLAN tag.
8. In the upper part of the settings area, click Save to save VXLAN settings.

Configuring a flat network

To configure a flat network:

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. Click the flat network 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 flat network.
4. If necessary, in the Description field, enter a brief description of the flat network.
5. 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 value is Disable.
   2. In the CIDR field, enter the IPv4 prefix of the OpenStack subnet that assigns 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 of IP addresses from which the OpenStack subnet assigns IP addresses to virtual network functions: To do so, under Pools, click + Pooland enter the starting and ending values of the IP address range.

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

   5. Specify the DNS server that the OpenStack subnet assigns to virtual network functions. To do so, under DNS, click + DNS and 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 or delete a DNS server. To delete a DNS server, click Delete next to it.

6. If you want to use the flat network to create a shared network service, select the Share network check box. This check box is cleared by default.
7. In the upper part of the settings area, click Save to save flat network settings.

Configuring a UNI

To configure a UNI:

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. Click the UNI 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 UNI.
4. If necessary, in the Description field, enter a brief description of the UNI.
5. In the upper part of the settings area, click Save to save UNI settings.