Specify the following parameters for your IP address or prefix:
#Cloud overlay serial#
Overlay, using Datagram Transport Layer Security (DTLS) or Transport Layer Security (TLS) tunnels, as long as Cisco vManage allows the device serial numbers.įrom the Cisco SD-WAN Self-Service Portal dashboard, navigate to your overlay network.įrom the drop-down list, click Cisco Hosted Overlays. You do not need to add the IP addresses of devices for them to join the overlay. To request user access, specify a rule type, protocol, port range, and source IP (IP addresses and prefixes) for which Specify the Allowed List of IP Addresses for Managing Controller Accessįor Cisco-hosted overlay networks, you can specify trusted IP addresses, including prefixes, from which you can manage controllerĪccess. To delete an overlay network, contact Cisco SD-WAN Technical Support.
#Cloud overlay install#
The controller password is deleted from the Cisco SD-WAN Self-Service Portal after seven days, so we recommend that you keep a copy of the controller password if you do not change the password.Īfter logging in to Cisco vManage, install the controller certificates on your devices.įor more information on installing controller certificates, see Use Case: Cisco-Hosted Cloud Overlays with Software Version 19.x and Above.įor information on installing web server certificates, see Web Server Certificates. To secure your environment, we recommend that you immediately change the password after logging in. Use this password to access the overlay network after it is created. The organization name provides a unique identity for the overlay.Ī unique controller password appears. The organization name option allows you to choose a specific name for the organization, which is configured on every single The DNS names option allows you to configure a custom name for the host part of the DNS.Įnter the custom DNS name for the Cisco vBond Orchestrator.Įnter the custom DNS name for Cisco vManage.Ĭhoose a frequency for taking snapshots from one of the following:īy default, the network overlay configuration is backed up once a day and ten snapshots are stored.Įnter the custom organization name for your overlay network. In the vEdge Cloud router field, click Enable to provision vEdge Cloud routers for TACACS-based user authentication and authorization.
The subnets are used in the following order: You can provide any of the three subnets. Provide two /24 IP prefixes, one for each region, during the overlay creation process.Įnsure that the provided IP prefix (/24) is unique within your network.Įnter a /24 prefix under each of the primary and the secondary subnet fields, and then enter three inclusive /26 subnets underįor example, IP prefix 10.6.117.0/24 can be divided into the following four /26 subnets: IP addresses in specific prefixes-prefixes that are unique and unused within your overlay. Server, or management access to instances over an overlay network, you may want to deploy the controllers with their private WhileĪdvanced options are not mandatory, if your use case requires them, configure advanced options before provisioning the overlayĪdvanced options cannot be changed once the overlay network is provisioned.įor the primary and the secondary subnets, specify the custom IP prefixes to be used for the controller interface IP addresses.įor use cases, such as connecting to an enterprise TACACS, authentication, authorization, and accounting (AAA), or syslog Providing advanced options allows you to specify custom parameter inputs that may be required for certain use cases. (Optional) To customize subnets, Domain Name System (DNS) names, organization names, or snapshot settings, click Edit in Advanced Options. In the Overlay Status field, choose Production.
We recommend that you choose different primary and secondary locations to achieve geographical redundancy.Ĭhoose the location where you want your monitoring data to be stored.Įnter the email address of the Cisco SD-WAN overlay network owner or administrator.
0 kommentar(er)
