Configuring a VIM deployed on a uCPE device

To configure a VIM deployed on a uCPE device, you must specify the settings of the VIM in a uCPE template. When you specify VIM settings in a uCPE template, such settings are propagated to all devices that are using the template.

To configure a VIM deployed on a uCPE device:

1. In the menu, go to the SD-WAN → CPE templates section.

   A table of CPE templates is displayed.

2. Click the uCPE template in which you want to configure a VIM.

   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 Information tab is selected, which displays general information about the CPE template.

3. Select the VIM tab.

   The VIM settings are displayed.

4. In the Port field, enter the port number for connecting the orchestrator to the VIM identification service. The default setting is 5,000.
5. In the Protocol drop-down list, select the protocol for connecting the orchestrator to the VIM:
   • http (default)
   • https
6. 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.
7. 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.
8. If you are using a network with the VLAN segmentation type for management, in the VLAN physical network field, enter the VLAN tag.
9. 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. Default value.
10. 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.

11. 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.
12. In the upper part of the settings area, click Save to save CPE template settings.