Configure vBond & Generate Certificate
Once vBond VM has been setup and started, it will come up with factory-default configuration. Now some more basic and initial configuration still to be done manually so that devices can be authenticated and verified and can easily join the overlay network.
Once initial configuration is done, a full configuration templates can be created on vManage and then attaching these templates to vBond orchestrator.
Create Initial Configuration for the vBond Orchestrator from CLI Section
Login to the Viptela device via SSH with user admin, using the default password, admin. | Enter configuration mode:
Configure the hostname:
Configure the system IP address:
The vManage NMS uses this vBond system IP address to identify the device and can download the full configuration to the vBond.
Configure the public IP address of the vBond orchestrator which will allow all Viptela devices in the overlay network to reach the vBond orchestrator:
Configure a time limit to confirm that a software upgrade is successful: Time limit is between 1 to 60 mints.
Change the password for the user “admin” whereas The default password is “admin”.
Configure an interface in VPN 0, over which an Internet or other WAN transport network can be connected and must be public IP address.
Commit the configuration:
Once overlay network is UP, create the vBond configuration template in vManage that contain the initial configuration. Use the following vManage Feature template.
- Use System feature template for hostname, system IP address, and vBond functionality configuration
- Use AAA feature template to configure a password for the “admin” user.
- Use VPN Interface Ethernet feature template to configure the interface in VPN 0
In addition, to the above initial configuration, some general system configuration is also required.
- Organization name, on the vManage Administration
- Time zone, NTP servers, and device physical location, from the configuration templates.
- Login banner from Banner feature configuration template.
- Logging parameters from Logging feature configuration template.
- AAA, and RADIUS and TACACS+ servers from AAA feature configuration template.
- SNMP from SNMP feature configuration template
Sample Initial CLI Configuration
Add the vBond Orchestrator and Generate Certificate
Following steps needs to be performed in order to add a vBond orchestrator to the network, automatically generate the CSR for vBond, and install the signed certificate on vBond:
- In vManage NMS | select the Configuration | Devices screen.
- In the Controllers tab | click Add Controller | select vBond.
In the Add vBond dialog box provide the following information
- vBond management IP address | username and password to access the vBond orchestrator.
- Select the Generate CSR checkbox to automatically allow the certificate-generation process | Click Add.
vManage NMS will generates the CSR, retrieves the generated certificate for vBond, and automatically installs it on the vBond orchestrator and this vBond will be added to vManage . To verify that the certificate is installed on a vBond orchestrator follow below screen shots: