You can specify the underlay configuration of a hub device by using the Configure Site feature on the Site Management page.
You can also configure an SD-WAN on-premise spoke site using dual CPE devices. The workflow to configure a site with dual CPE devices is similar to single CPE device. You need atleast one WAN link per CPE to act as a OAM_AND_DATA for redundancy, so that the individual nodes establish connectivity with CSO.
You must provide the serial number and the activation code for the primary and the secondary device.
To configure a site:
The Configure Site Site Name page is displayed.
Table 160: Fields on the Configure Site Page
Field | Description |
|---|---|
Site Type | Displays the site type. |
Management Region | Displays the regional server with which the CPE device communicates based on the information in the device profile. This field cannot be modified. |
Selected Plan | Displays the connection plan that you selected when you created the site. This field cannot be modified. |
Hub Multihoming | Displays whether multihoming was enabled or disabled on the site during the creation of the site. This field cannot be modified. |
Configuration | |
| Connectivity | |
Management Connectivity | |
OAM Traffic Information | Enable Operation, Administration, and Maintenance (OAM) traffic information to specify the OAM VLAN ID, IP prefix for the site management network, and gateway IP address of the default route. |
VLAN ID | Specify the OAM VLAN ID for in-band management of the site. |
IP Prefix | Specify one or more prefixes for the site management network. You can specify IPv4 or IPv6 addresses. Example: 10.0.2.16/24 |
Gateway IP | Specify the IP address of the default route for the management network. You can use an IPv4 or IPv6 address. |
WAN_0, WAN_1, WAN_2, WAN_3 | |
WAN Interface | Displays the interface name configured in the device profile. This field cannot be modified. |
Link Type | Displays the link type (MPLS or Internet) configured in the device profile. This field cannot be modified. |
Address Assignment | Select the method of IP address assignment. Select DHCP to assign IP addresses by using a DHCP sever or Static to assign a static IP address. |
Traffic Type | Select the traffic type. You specify whether you want to use the WAN link to transmit only data traffic or both management traffic and data traffic. You must select the traffic type as OAM_and_DATA when you configure a site with dual CPE devices. You need atleast one WAN link per CPE to act as a OAM_AND_DATA for redundancy. |
Data VLAN ID | VLAN ID associated with the WAN link. |
Local Breakout | Displays whether local breakout was enabled on the WAN link during creation of the site. This field cannot be modified. If the WAN link is selected to be used for only local breakout traffic, then the Overlay Tunnel section is not displayed. |
Autocreate Source NAT Rule | Select this option to enable interface-based source NAT on the WAN link. Note: If this option is enabled for a WAN interface W1 during the site creation workflow, a series of NAT source rules are automatically created. Each automatically created NAT rule is from a zone to the WAN interface, with a translation of type interface. Each pair of [zone - interface] represents a rule-set. For example, the following zone to W1 interface rule-set might be created: Zone1 --> W1: Translation=Interface Zone2 --> W1: Translation=Interface Zone3 --> W1: Translation=Interface To manually override any of these rules, you can create a NAT rule within a particular rule-set. For example, to use a source NAT pool instead of an interface for translation, create a NAT rule within this particular rule-set, that includes the relevant zone and WAN interface as the source and destination. For example: Zone1 --> W1 : Translation=Pool-2 The manually created NAT rule is placed at a higher priority than the corresponding automatically created NAT rule. You can also add other fields (such as addresses, ports, protocols, and so on) as part of the source or destination endpoints. For example: Zone1, Port 56578 --> W1: Translation=Pool-2 |
Overlay Tunnel | |
Tunnel Type | Select the tunnel type—GRE or GRE over IPsec. |
Peer Device | Displays the hub device to which the site is connected. |
Interface Name | Select the name of the interface of the hub device to which the MPLS or Internet link is connected. |
| Devices | |
Assign CPE Devices | |
Device Redundancy | Displays whether device redundancy is enabled or disabled for an SD-WAN on-premise spoke site. |
Primary Device Serial Number | Enter the serial number of the primary CPE device. You can use a unique string of alphanumeric characters. The maximum length is 64 characters. Serial numbers are case-sensitive. |
Primary Device Activation Code | Enter the activation code of the primary device that your service provider supplied for the device. Note: If you do not want to specify an activation code, on the Resources > Device Templates > Template Settings page, disable the ACTIVATION_CODE_ENABLED field and save the changes. |
Secondary Device Serial Number | Enter the serial number of the secondary CPE device. You can use a unique string of alphanumeric characters. The maximum length is 64 characters. Serial numbers are case-sensitive. |
Activation Code | Enter the activation code of the secondary device that your service provider supplied for the device. Note: If you do not want to specify an activation code, on the Resources > Device Templates > Template Settings page, disable the ACTIVATION_CODE_ENABLED field and save the changes. |
Boot Image | (Optional) Select the boot image from the drop-down list. The boot image is the device image that was previously uploaded to the image management system through the “Images” page. The boot image is used to upgrade the device when the CSO starts the ZTP process. If the boot image is not provided, then the device skips the automatic upgrade procedure. See Uploading a Device Image. |