system vbond—Configure the IP address and other information related to the vBond orchestrator.
vManage Feature Template
For vEdge routers acting as vBond controllers only:
Configuration ► Templates ► System
system vbond (dns-name | ip-address) [local] [port number] [ztp-server]
In Releases 16.3 and later, the following command hierarchy is also available:
system vbond [dns-name | host-name | ip-address] [local] [port number] [ztp-server]
- Configure Device To Be only a vBond Orchestrator
- vbond-only (Deprecated starting with Release 16.1)
Configure a hardware vEdge router or a software vEdge Cloud router to act only as a vBond orchestrator. Starting with Release 16.1, you must include this option to configure a vBond orchestrator. Starting with Release 16.1, a vBond orchestrator and a vEdge router cannot coexist in the same virtual machine or on the same hardware router, so do not configure any edge router functionality on a vBond orchestrator.
- DNS Name of the vBond Orchestrator
DNS name that points to one vBond orchestrator or to a number of vBond orchestrators. The addresses can resolve to vBond orchestrators configured with IPv4 addresses, with IPv6 addresses, or with both IPv4 and IPv6 adresses.
- IP Address of the vBond Orchestrator
IPv4 or IPv6 address of the vBond orchestrator, in decimal four-part dotted notation. You can configure one address, and it must be a public IP address.
- Local vBond System
(On vBond orchestrator only. Designate the local vEdge router to be a vBond orchestrator in the Viptela overlay network domain.
Starting in Release 16.3, if you configure the local option, you can omit the DNS name, hostname, or IP address of the vBond orchestrator as long as one of the interfaces in VPN 0 has a routable public IP address.
- Local Zero-Touch-Provisioning Server
Designate the local vEdge router to be the zero-touch-provisioning (ZTP) server in the overlay network domain. Such a vBond orchestrator acts as an enterprise ZTP server, and provides the vEdge routers in your domain with the IP address of your enterprise vBond orchestrator and with the enterprise root CA chain. You must load two files onto your enterprise ZTP server: the vEdge authorized serial number file that you received from Viptela and your enterprise root CA chain, which must be signed by Symantec. You must also configure your enterprise DNS server with an A record that redirects the URL ztp.viptela.com to your enterprise ZTP server. The recommended URL for this enterprise server is ztp. your-company-name.com.
A vEdge router acting as an enterprise ZTP server should be dedicated to that function. It cannot be used as a regular vBond orchestrator in the overlay network domain. Also, it is recommended that you not use it in an edge router capacity.
- Multiple vBond Orchestrators
If you want to configure addresses of multiple vBond orchestrators, but are not using a DNS name resolution server, you can configure the hostname of an orchestrator. Then, in VPN 0, use the host command to configure the IP addresses of the vBond orchestrators. For example, if you configure system vbond vbond1, you could configure vpn 0 host vbond1 10.0.12.26 2001::10.0.12.26 to configure two vBond orchestrator addresses, one an IPv4 address and the second an IPv6 address.
- Port Number to Connect to vBond Orchestrator
- port number
Port number to use to connect to the vBond orchestrator.
If you omit this option, the local system first tries port 12346 on the vBond orchestrator. If this port is not available, the system then tries port 12366 and then port 12388, rotating through these three port numbers until one is available.
If you do not want to rotate through these three port numbers, configure the port number to use to connect to the vBond orchestrator.
Range: 1 through 65535
- Remove a vBond Orchestrator from the Configuration
- no system vbond
Remove the vBond configuration from the device. If you have configured an IP address for the vBond orchestrator, to change the address, you must delete the address and then configure the new address. Doing this causes all of the devices existing connections to the Viptela devices in the network to go down; they come back up after you commit the configuration with the new IP address. To avoid this problem, it is highly recommended that you always use a DNS name for your vBond orchestrators, and then make changes to the DNS devices instead of on the vEdge routers and vSmart controllers directly.
Configure the DNS name of a vBond orchestrator on a vEdge router:
system vbond vbond.east.acme.com !
Designate the local vEdge router to be a vBond orchestrator in its Viptela overlay network domain:
system vbond 10.0.4.12 local !
Designate the local vEdge router to be an enterprise ZTP server:
system vbond 22.214.171.124 local ztp-server !
Command introduced in Viptela Software Release 14.1.
In Release 14.3, add ztp-server option.
In Releae 16.1, deprecate vbond-only option.