Configure vManage & Generate Certificate

Configure vManage & Generate Certificate

After you deployed the VM instance, it will come up with factory default setting. But for minimum configuration, you should configure IP address of vBond orchestrator, vManage system IP address, tunnel Interface VPN 0 for exchanging control traffic among vBond, vManage, and vSmart devices.

vManage must be configured with following so that it can participate in overly network.

• Configure a tunnel interface (one interface) in VPN 0. This interface is one over which any WAN transport is connected and all Viptela devices must be able to access this interface. VPN 0 is the tunnel interface that carries all the control traffic among Viptela devices
• Enable OMP protocol if it is not enabled. This protocol is responsible for establishing and maintaining Viptela Control plane.

Configure the vManage NMS with a Device Configuration Template

In order to configure the vManage NMS, a device configuration template must be created

1. Configure the address of the vBond orchestrator:

• Select the Administration section | Settings screen | Click the Edit button to the right of the vBond bar.
• In the vBond DNS/IP Address: Port field, enter the DNS name which points to the vBond orchestrator or the IP address of the vBond orchestrator and the port number to use to connect to it. | Click Save.

2. In vManage NMS, select the Configuration | Templates screen. | In the Device tab, click Create Template | From the Create Template drop-down, select From Feature Template.
3. From the Device Model drop-down, select vManage device and the required feature templates are shown with an asterisk (*), and the remaining templates are shown as optional. The factory-default template for each feature is selected by default
4. In the Template Name field | name for the device template. This field is mandatory. In the Description field | enter a description for the device template. This field is mandatory.
5. In the System feature template | Site ID | System IP Address | Host name | Location | Time zone, and GPS Location.
6. In the AAA feature template | Local tab | click Users | change the password for the user "admin."
7. In the VPN feature template | select VPN 0 | configure the system IP address and the address or host name of a DNS server. If necessary, click the Route tab | add a static route.
8. If you need to add a static route in VPN 512, in a second VPN feature template, select VPN 512, click the Route tab, and add the static route.
9. In the VPN-Interface-Ethernet feature template | configure the interface in VPN 0 to connect to the WAN transport network. In Shutdown | click No enter the Interface Name | Assign the interface either a dynamic or static address. In the Interface Tunnel tab, Tunnel Interface | click On.| assign a color to the Tunnel interface, | select the desired services to allow on the tunnel
10. In a second VPN-Interface-Ethernet feature template, configure management interface in VPN 512. In Shutdown | click No | enter the Interface Name | assign the interface either a dynamic or static Address.
11. In the Security feature template | configure the control plane protocol
12. Optionally, modify the default Archive | Banner | Logging | NTP | SNMP feature templates.
13. Click Create. The new configuration template will be displayed in the Device Template table. The Feature Templates column shows the number of feature templates that are included in the device template, and the Type column shows "Feature" to indicate that the device template was created from a collection of feature templates.
14. In the Device Template table | locate the desired device template | Click the More Actions icon to the right of the row | select Attach Devices.
15. In the Attach Devices box, select the local vManage NMS from the Available Devices list | click the right-pointing arrow to move it to the Selected Devices box | Click Attach.

Sample CLI Configuration