Configuring a VIM deployed on location

To configure a VIM deployed on location:

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

   This opens the resource management page. By default, the Network resources tab is selected, which displays the table of SD-WAN and SDN controllers.

2. In the Resources pane, select the previously created domain and data center to which the location belongs.
3. Select the Compute resources tab.

   A table of VIMs is displayed.

4. In the upper part of the page, click + VIM.
5. This opens a window; in that window, in the Name field, enter the name of the VIM.
6. In the IP field, enter the IP address or domain name for connecting the orchestrator to the VIM.
7. In the Port field, enter the port number for connecting the orchestrator to the VIM identification service. The default setting is 5,000.
8. In the Protocol drop-down list, select the protocol for connecting the orchestrator to the VIM:
   • http (default)
   • https
9. In the Login and Password fields, enter the user name and password of an account with administrator privileges to authenticate the orchestrator in the OpenStack cloud platform. If authentication is successful, the orchestrator gains access to managing the virtual infrastructure that is available to the administrator.
10. To specify advanced OpenStack cloud platform authentication settings for the orchestrator, follow these steps:
    1. In the Administrator project field, enter the name of the administrator project for orchestrator authentication in this project.
    2. In the Domain field, enter the OpenStack domain name for orchestrator authentication in this domain.
11. In the Behind NAT drop-down list, select whether the VIM is behind NAT:
    • Enabled to indicate that the VIM is behind NAT and network address translation happens when it interacts with the SD-WAN instance.
    • Disabled to indicate that the VIM is not behind NAT. This is the default.
12. Specify the overcommitment ratios for physical resources:
    1. In the CPU overcommitment field, enter the CPU core overcommitment ratio. The default setting is 1.
    2. In the RAM overcommitment field, enter the RAM overcommitment ratio. The default setting is 1.
    3. In the Disk overcommitment field, enter the disk space overcommitment ratio. The default setting is 1.

    Overcommitment ratios let you provision virtual machines with more virtual resources than physically present. This is possible because, as a rule, virtual machines do not simultaneously use all available physical resources to the maximum. For example, if you specify a disk space overcommitment factor of 3, the available virtual disk space can be three times as large as the disk space physically available on the host.

    When configuring overcommitment, you must consider how the capabilities of your hardware relate to the requirements of the virtual machines. If you specify a high overcommitment ratio for physical resources and virtual machines happen to use them up, this may lead to the network lagging and/or parts of network becoming completely unavailable.

13. In the Parallelism field, enter the maximum number of simultaneous operations between the orchestrator and the VIM. The default setting is 1. This setting lets you reduce the overall processing time for operations, but creates an additional load on the virtual infrastructure.

    We recommend not changing the default value unless the overall operation processing speed is critical for you.

14. In the SDN cluster drop-down list, select the SDN cluster to which OpenStack is connected, or None if OpenStack is not connected to an SDN cluster.
15. In the Maximum number of VLANs field, enter the maximum number of VLANs that the VIM may use. This setting lets the orchestrator keep track of the number of segments available for use. Range of values: 0 to 4,094.
16. If the VIM supports SR-IOV, enter the physnet name in the SR-IOV physical network field. The orchestrator uses the SR-IOV physical network name to connect virtual machines with the SR-IOV interface type.
17. If you are using a network with the VLAN segmentation type for management, in the VLAN physical network field, enter the VLAN tag.
18. If you selected an SDN cluster in the SDN cluster drop-down list, configure the connection to that cluster:
    1. If you want to map the logical networks of the SD-WAN instance to a physical network, enter the physnet name in the OpenStack physical network field.
    2. In the Interface group drop-down list, select the port group through which all OpenStack nodes are connected to the SDN cluster.
    3. In the Control group drop-down list, select the port group through which the OpenStack control nodes are connected to the SDN cluster.
    4. If necessary, in the Compute group drop-down list, select the port group through which OpenStack compute nodes are connected to the SDN cluster.
19. If you selected None in the SDN cluster drop-down list, configure your network:
    1. If you want to map the flat networks of the SD-WAN instance to a physical network, enter the physnet name in the Flat physical network field.
    2. If you want to map the VXLAN of the SD-WAN instance to a physical network, enter the physnet name in the VXLAN physical network field.
    3. In the Control network segmentation drop-down list, select the type of segmentation for isolating and securing control plane traffic in the SD-WAN structure:

       The control part of the network that controls the transmission of traffic packets through CPE devices. Performs functions such as network discovery, route calculation, traffic prioritisation, and security policy enforcement. The control plane allows centrally managing the network by providing a full-scale view of all performed operations. Consists of an orchestrator and an SD-WAN controller.

       • VLAN
       • VXLAN
    4. In the Control segment ID field, enter the segment ID of the management network. The range of values depends on the value selected in the Control network segmentation drop-down list:
       • If you selected VLAN, the range of values is 0 to 4,095.
       • If you selected VXLAN, the range of values is 0 to 16,000,000.
    5. In the Port security drop-down list, select whether you want to enable the Port security function:
       • Enabled
       • Disabled
    6. In the Permit CIDR field, enter the IPv4 prefix of the allowed subnet for the management network.
20. Click Create.

The VIM is created and displayed in the table on the Compute resources tab.