Install Partner Gateway
This section discusses the steps to install and deploy VeloCloud Gateway as a Partner Gateway. It also covers how to configure the VRF/VLAN and BGP on the Partner Gateway.
This topic contains the following sections:
- Installation Overview
- Minimum Hypervisor Hardware Requirements
- Gateway Installation Procedures
- Post-Installation Tasks
- Upgrade Gateway
- Activate Replacement Partner Gateway
- Custom Configurations
- SNMP Integration
- Custom Firewall Rules
- Configure TACACS+ Authentication for Partner Gateways
- Partner Gateway Upgrade and Migration
Installation Overview
This section provides an overview of Partner Gateway installation.
About Partner Gateways
- One interface faces the private or public WAN network and manages VCMP encapsulated traffic from remote Edges, alongside standard IPsec traffic from Non SD-WAN Destinations.
- Another interface faces the data center and provides access to resources or networks on the PE router connected to the Partner Gateway. The PE router typically provides access to shared managed services for branches or to a private (MPLS/IP-VPN) core network that separates individual customers.
Partner Gateway provides the following distributions:
| Provided | Description | Example |
|---|---|---|
| ESXi | Gateway OVA package. | velocloud-vcg-X.X.X-GA.ova |
| KVM | Gateway qcow2 disk image. | velocloud-vcg-X.X.X-GA.qcow2 |
Minimum Hypervisor Hardware Requirements
The Gateway runs on a standard hypervisor (KVM or VMware ESXi).
Minimum Server Requirements
- CPU: Achieving maximum performance requires an Intel Xeon processor (10 cores minimum to run a single 8-core gateway VM) with a minimum clock speed of 2.0 GHz.
- ESXi vmxnet3 network scheduling functions must have 2 cores reserved per Gateway virtual machine (VM), regardless of the number of cores assigned to the Gateway.
- Example: Assume there is a 24-core server running ESXi with vmxnet3. Deploy 2 (8-core) Gateways. i.e., 2 gateways multiplied by 8 cores requires 16 cores reserved for the Gateway application and leaves 8 free cores. Using this formula, to support these two Gateways running at peak performance, the ESXi/vmxnet3 system requires an additional 4 cores (two cores per deployed Gateway). That means running two Gateways on a 24-core system consumes 20 cores.
Note: SR-IOV offloads network scheduling to the physical NIC (pNIC) to improve performance. However, the hypervisor must still perform other scheduling functions, like CPU, memory, and NUMA allocation management. The hypervisor always requires two free cores to manage system operations and background tasks efficiently.
- Example: Assume there is a 24-core server running ESXi with vmxnet3. Deploy 2 (8-core) Gateways. i.e., 2 gateways multiplied by 8 cores requires 16 cores reserved for the Gateway application and leaves 8 free cores. Using this formula, to support these two Gateways running at peak performance, the ESXi/vmxnet3 system requires an additional 4 cores (two cores per deployed Gateway). That means running two Gateways on a 24-core system consumes 20 cores.
- ESXi vmxnet3 network scheduling functions must have 2 cores reserved per Gateway virtual machine (VM), regardless of the number of cores assigned to the Gateway.
- The CPU must support and activate the following instruction sets: AES-NI, SSSE3, SSE4, RDTSC, RDSEED, RDRAND, AVX/AVX2/AVX512.
- A minimum of 4GB of free RAM must be available to the server system, in addition to the memory assigned to the PGW VMs. Each Gateway VM requires 16GB of RAM, which increases to 32GB for an active certificate-based authentication.
- Minimum of 150GB magnetic or SSD-based, persistent disk volume (One Gateway VM requires 64GB or 96GB Disk Volume, if certificate-based authentication is activated).
- Minimum required IOPS: 200.
- Deployment requires at least one 10GbE network interface port, though the Gateway partner hand-off interface functions best with two ports. The physical NIC cards supporting SR-IOV are Intel 82599/82599ES and Intel X710/XL710 chipsets. (See the Enable SR-IOV.)
Note: SR-IOV does not support NIC bonding. For redundant uplinks, use ESXi vSwitch.
- VeloCloud Gateway is a data-plane intensive workload that requires dedicated CPU cycles to ensure optimal performance and reliability. Meeting these defined settings ensures that the Gateway VM is not oversubscribing the underlying hardware and causing actions that can destabilize the Gateway service (e.g. NUMA boundary crossing, memory, and/or vCPU oversubscription).
- Ensure that the SD-WAN Partner Gateway VM and the resources used to support it, such as network interfaces, memory, and physical CPUs, fit within a single NUMA node.
-
Note: Configure the host BIOS settings as follows:
- Hyper-threading- Turned off
- Power Savings- Turned off
- CPU Turbo- Enabled
- AES-NI- Enabled
- NUMA Node Interleaving- Turned off
- Use ESXi host version: ESXi-6.7.0-14320388-standard or above
- Upgrade VM compatibility should be set before starting the Gateway SD-WAN Gateway instance
| NIC Chipset | Hardware | Specification |
|---|---|---|
| Intel 82599/82599ES | HP DL380G9 | http://www.hp.com/hpinfo/newsroom/press_kits/2014/ComputeEra/HP_ProLiantDL380_DataSheet.pdf |
| Intel X710/XL710 | Dell PowerEdge R640 | https://www.dell.com/en-us/work/shop/povw/poweredge-r640
|
| Intel X710/XL710 | Supermicro SYS-6018U-TRTP+ | https://www.supermicro.com/en/products/system/1U/6018/SYS-6018U-TRTP_.cfm
|
| Intel E810-CQDA2 | Dell PowerEdge R640 | https://www.dell.com/en-us/work/shop/povw/poweredge-r640
|
| Hardware Manufacturer | Firmware Version | Host Driver for Ubuntu 20.04.6 | Host Driver for Ubuntu 22.04.2 | Host Driver for ESXi 7.0U3 | Host Driver for ESXi 8.0U1a |
|---|---|---|---|---|---|
| Dual Port Intel Corporation Ethernet Controller XL710 for 40GbE QSFP+ | 7.10 | 2.20.12 | 2.20.12 | 1.11.2.5 and 1.11.3.5 | 1.11.2.5 and 1.11.3.5 |
| Dual Port Intel Corporation Ethernet Controller X710 for 10GbE SFP+ | 7.10 | 2.20.12 | 2.20.12 | 1.11.2.5 and 1.11.3.5 | 1.11.2.5 and 1.11.3.5 |
| Quad Port Intel Corporation Ethernet Controller X710 for 10GbE SFP+ | 7.10 | 2.20.12 | 2.20.12 | 1.11.2.5 and 1.11.3.5 | 1.11.2.5 and 1.11.3.5 |
| Dell rNDC X710/350 card | nvm 7.10 and FW 19.0.12 | 2.20.12 | 2.20.12 | 1.11.2.5 and 1.11.3.5 | 1.11.2.5 and 1.11.3.5 |
| Dual Port Intel Corporation Ethernet Controller E810-CQDA2 for 100GbE QSFP | 4.20 | ICE 1.11.14 | ICE 1.11.14 | Not supported yet | Not supported yet |
| Hypervisor | Supported Versions |
|---|---|
| VMware |
|
| KVM |
|
Gateway Virtual Machine (VM) Specification
- If using ESXi:
- Set the Latency Sensitivity to 'High'.
- Procedure to adjust Latency Sensitivity:
- Browse to the virtual machine in the vSphere Client.
- To find a virtual machine, select a data center, folder, cluster, resource pool, or host.
- Select the VMs tab.
- Right-click the virtual machine, and then select Edit Settings.
- Select VM Options, and then select Advanced.
- Select High from the Latency Sensitivity drop-down menu.
- Select OK.
- Browse to the virtual machine in the vSphere Client.
- Set the CPU reservation to 100%.
- Set the CPU shares to high.
- Set the CPU Limit to Unlimited.
- 8 vCPUs (The system supports 4 vCPUs but yields lower performance levels.)
Important: Map all the vCPU cores to the same socket, with the Cores per Socket parameter set to either 8 (8 vCPUs) or 4 (4 vCPUs).Note: To achieve maximum performance, deactivate hyper-threading.
- Procedure to allocate CPU resources:
- Select Virtual Machines in the Arista Host Client inventory.
- Right-click a virtual machine from the list, and then select Edit settings from the pop-up menu.
- On the Virtual Hardware tab, expand CPU, and then allocate CPU capacity for the virtual machine.
Table 5. Virtual Hardware - Options and Descriptions Option Description Reservation Guaranteed CPU allocation for this virtual machine. Limit Upper limit for this virtual machine’s CPU allocation. Select Unlimited to specify no upper limit. Shares CPU shares for this virtual machine in relation to the parent’s total. Sibling virtual machines share resources according to their relative share values bounded by the reservation and limit. Select Low, Normal, or High, which specify share values respectively in a 1:2:4 ratio. Select Custom to give each virtual machine a specific number of shares, which expresses a proportional weight.
- Procedure to adjust Latency Sensitivity:
- To activate CPU affinity, perform the following steps:
- In the vSphere Web Client, go to the VM Settings tab.
- Choose the Options tab, and then select .
- Add entries for numa.nodeAffinity=0, 1, ..., where 0 and 1 are the processor socket numbers.
- vNIC must be of type 'vmxnet3' (or SR-IOV, see SR-IOV section for support details).
- Minimum of any one of the following vNICs:
- The First vNIC is the public (outside) interface, which must be an untagged interface.
- The Second vNIC is optional and acts as the private (inside) interface that can support VLAN tagging dot1q and Q-in-Q. This interface typically faces the PE router or L3 switch.
- Optional vNIC (if a separate management/OAM interface is required).
- Memory reservation is set to ‘maximum.’
- 16GB of memory (32GB RAM when enabling certificate-based authentication).
- 64 GB of virtual disk (96GB disk when enabling certificate- based authentication).
Note: Arista uses the above defined settings to obtain scale and performance numbers. Settings deviating from the specified requirements remain untested and often yield unpredictable performance and scale results.
- Set the Latency Sensitivity to 'High'.
- If using KVM:
- vNIC must be of 'Linux Bridge' type. (SR-IOV is required for high performance, see SR-IOV section for support details).
- 8 vCPUs (The system supports 4 vCPUs but yields lower performance levels).
Important: Map all the vCPU cores to the same socket, with the Cores per Socket parameter set to either 8 (8 vCPUs) or 4 (4 vCPUs).Note: To achieve maximum performance, deactivate hyper-threading.
- 16GB of memory (32GB RAM when enabling certificate- based authentication)
- Minimum of any one of the following vNICs:
- The First vNIC is the public (outside) interface, which must be an untagged interface.
- The Second vNIC is optional and acts as the private (inside) interface that can support VLAN tagging dot1q and Q-in-Q. This interface typically faces the PE router or L3 switch.
- Optional vNIC (if a separate management/OAM interface is required).
- 64 GB of virtual disk (96GB disk when enabling certificate- based authentication).
Firewall/NAT Requirements
- The firewall must allow outbound traffic from the Gateway to TCP port 443 (for communication with Orchestrator).
- The firewall must allow inbound traffic from the Internet to UDP/2426 (VCMP), UDP/4500, and UDP/500. The firewall must allow IP/50 (ESP) whenever the deployment excludes NAT.
- The NAT device translates these ports to an externally reachable IP address. The configuration supports both the 1:1 NAT and port translations.
Use of DPDK on Gateways
To improve packet throughput performance, Gateways take advantage of Data Plane Development Kit (DPDK) technology. Intel’s DPDK provides data-plane libraries and drivers that offload TCP packet processing from the OS kernel to user-space processes, thereby increasing packet throughput. For additional details, see https://www.dpdk.org/.
VeloCloud-hosted Gateways and Partner Gateways use DPDK on data-plane interfaces while reserving standard kernel processing for management-plane traffic. On a typical VeloCloud-hosted Gateway, eth0 handles management-plane traffic without DPDK, while eth1, eth2, and eth3 manage data-plane traffic via DPDK.
Gateway Installation Procedures
In general, installing the Gateway involves the following steps:
Pre-Installation Considerations
| Gateway |
|
| Hypervisor | Address/Cluster name |
| Storage | Root volume datastore (>40GB recommended) |
| CPU Allocation | CPU Allocation for KVM/ESXi. |
| Installation Selections | DPDK - This is optional and the system enables it by default for higher throughput. To deactivate DPDK, contact https://www.arista.com/en/support. |
| OAM Network |
|
| ETH0 – Internet Facing Network |
|
| Handoff (ETH1)- Network |
|
| Console access |
|
| NTP |
|
Gateway Section
| Gateway |
|
Create a Gateway and Get the Activation Key
Enable Partner Gateway Mode
Networking

The diagram above is a representation of the Gateway in a 2-ARM deployment. In this example, assume eth0 is the interface facing the public network (Internet) and eth1 is the interface facing the internal network (handoff or VRF interface).
The Internet-facing network requires only a basic network configuration.
| ETH0 – Internet Facing Network |
|
Configuration of the handoff interface requires both the selection of a handoff type and the specific settings for the Management VRF.
| ETH1 – HANDOFF Network |
|
Console Access
| Console access |
|
To access the Gateway, create a console password or an SSH public key.
Cloud-Init Creation
Below are the templates for both meta_data and user_data files. Omitting the network-config file triggers the default DHCP configuration.
Fill the templates with the information in the worksheet. All #_VARIABLE_# must be replaced, and check any #ACTION#
instance-id: #_Hostname_# local-hostname: #_Hostname_#
version: 2
ethernets:
eth0:
addresses:
- null
gateway4: null
nameservers:
addresses:
- null
- null
search: []
routes:
- to: 0.0.0.0/0
via: null
metric: 1
eth1:
addresses:
- null
gateway4: 192.168.152.1
nameservers:
addresses:
- null
- null
search: []
routes:
- to: 0.0.0.0/0
via: null
metric: 13
hostname: null
password: null
chpasswd:
expire: false
ssh_pwauth: true
ssh_authorized_keys:
- null
velocloud:
vcg:
vco: null
activation_code: null
vco_ignore_cert_errors: false
The default username for the password configured in the user-data file is 'vcadmin'. Use this default username to login to the Gateway for the first time.
sed s/[”“]/'"'/g /tmp/user-data > /tmp/user-data_new
Create ISO File
vcg01-cidata.iso:
genisoimage -output vcg01-cidata.iso -volid cidata -joliet -rock user-data meta-data network-config
mkisofs -output vcg01-cidata.iso -volid cidata -joliet -rock {user-data,meta-data,network-config}
Use this ISO file #CLOUD_INIT_ISO_FILE# with both OVA and ESXi installations.
Install Gateway
Users can install Gateway on Arista and KVM.
- SR-IOV
- Linux Bridge
- OpenVSwitch Bridge
Activate SR-IOV on ESXi
- Intel 82599/82599ES
- Intel X710/XL710
Install Gateway on ESXi
To install the Gateway OVA on ESXi:
Activate SR-IOV on KVM
- Intel 82599/82599ES
- Intel X710/XL710
Validating SR-IOV (Optional)
Executing the following command confirms the SR-IOV status on the host machine:
lspci | grep -i Ethernet
The following command confirms the presence of Virtual Functions:
01:10.0 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function(rev 01)
Install Gateway on KVM
KVM provides multiple ways to provide networking to virtual machines. Configuring the VM requires prior provisioning of the libvirt networking. There are multiple ways to configure networking in KVM. For a full configuration of options on how to configure Networks on libvirt, see the following link:
https://libvirt.org/formatnetwork.html
- SR-IOV (This mode enables the Gateway to deliver the maximum throughput specified by Arista.)
- OpenVSwitch Bridge
Using SR-IOV mode requires activating SR-IOV on KVM. See Activate SR-IOV on KVM.
- Deactivate GRO (Generic Receive Offload) on physical interfaces (to avoid unnecessary re-fragmentation in the Gateway).
ethtool –K <interface> gro off tx off
- Deactivate CPU C-states (power states affect real-time performance). Typically, perform this step as part of kernel boot options by appending processor.max_cstate=1 or deactivate in the BIOS.
- Production deployments require pinning vCPUs to the instance. Production standards prohibit the over-subscription of cores.
Configure Persistent Interface Names on KVM
Starting with release 6.1, when a Gateway VM on KVM has two or more network interfaces, the kernel may not assign the names eth0 and eth1 to the same interfaces after every reboot.
Persistent Interface Names
| Interface | Default Name | Role-Based Name | ethN Offset Name |
|---|---|---|---|
| Internet-facing (VCMP) | eth0 | vcmp0 | eth2 |
| Handoff | eth1 | handoff0 | eth3 |
- Role-Based Name describes the function of each interface and never overlaps with the names the kernel assigns.
- ethN Offset Name keeps the ethN format. Start the numbering at N, where N is the total number of network interfaces of the VM. The kernel only assigns eth0 through eth(N-1), so names from ethN onwards are always available.
For a VM with three interfaces, including an OAM interface, use vcmp0, handoff0, and oam0, or the ethN offset names eth3, eth4, and eth5. Users can also choose other names as long as each name is unique, not in the eth0-eth(N-1) range, and no longer than 15 characters.
- Adding a network interface to the VM later increases N, potentially causing an ethN offset name to fall within the range the kernel assigns. Choosing ethN offset names requires accounting for any planned interface additions or renaming the interfaces after adding a new one.
- The persistent names apply only inside the Gateway VM. Commands running on the KVM host, such as the Virtual Function settings in Install Gateway on KVM, continue to use the host interface names.
The examples in the following sections use role-based names. When using ethN offset names, replace vcmp0 and handoff0 with the corresponding ethN offset names (for example, eth2 and eth3).
Configure Interface Names for a New Gateway
Configure Interface Names for an Existing Gateway
Verify Interface Names
Gateway Upgrades
Expand the Gateway Disk on KVM
Describes how to expand the virtual disk of an existing Gateway on KVM from 64 GB to 96 GB.
- Schedule a maintenance window. The Gateway is offline while the VM is shut down.
- When expanding more than one Gateway, expand one Gateway at a time. Verify that each Gateway is connected to the Orchestrator before starting the next one.
- Make sure the KVM host has enough free space for a backup copy of the QCOW file and for the larger disk.
- Ensure access to the KVM host and root access to the Gateway.
The Gateway VM requires a 96 GB virtual disk when certificate-based authentication is enabled. Use this procedure for a Gateway that was installed with a 64 GB disk. The examples use the VM name test_vcg and the QCOW file /tmp/VeloCloudGateway/vcg-root from Install Gateway on KVM.
Post-Installation Tasks
A successful installation enables immediate login access to the VM.
Configure Handoff Interface in Data Plane

The SD-WAN Gateway creates a management VRF to send periodic ARP refreshes to the default gateway IP address to determine the next-hop MAC address. Arista recommends setting up a dedicated VRF on the PE router for this purpose. The PE router can also use the same management VRF to send an IP SLA probe to the SD-WAN Gateway to check for SD-WAN Gateway status (SD-WAN Gateway has a stateful ICMP responder that responds to ping only when its service is up). The Management VRF operates without requiring BGP peering. One of the customer VRFs can function as a Management VRF in the absence of a dedicated management setup, though this practice remains non-recommended.
Remove Blocked Subnets
2015-12-18T12:49:55.639 ERR [NET] proto_ip_recv_handler:494 Dropping packet destined for 10.10.150.254, which is a blocked subnet. 2015-12-18T12:52:27.764 ERR [NET] proto_ip_recv_handler:494 Dropping packet destined for 10.10.150.254, which is a blocked subnet. [message repeated 48 times] 2015-12-18T12:52:27.764 ERR [NET] proto_ip_recv_handler:494 Dropping packet destined for 10.10.150.10, which is a blocked subnet.
[
{
"network_addr": "10.0.0.0",
"subnet_mask": "255.0.0.0"
},
{
"network_addr": "172.16.0.0",
"subnet_mask": "255.255.0.0"
}
]
Upgrade Gateway
This section discusses how to upgrade a Gateway installation.
Authenticate Software Update Package Via Digital Signature
The software installer in the Orchestrator version 4.3.0 and higher now has the ability to authenticate the software update package using a digital signature.
Prior to upgrading to a newer version of the software, make sure the public key exists to verify the package. The known public key location to verify signature has the following format, /var/lib/velocloud/software_update/keys/software.key. Alternatively, the key can be provided on the command line using --pubkey- parameter.
-----BEGIN PUBLIC KEY----- MHYwEAYHKoZIzj0CAQYFK4EEACIDYgAEbjZ08w3RNJvuOICBp8fysU/3opLejsrP pArA1IyKeUzU0U31MU4kPcLdggojobNfs3i1kvyvGvprEmfGYWzc3dXUyT9Tv73C lVgYPLNd/nOxJsXomROKogfvJdYFuy4/ -----END PUBLIC KEY----
If the key is missing or the signature cannot be verified, The Edge notifies the Operator that the package is untrusted with an option to proceed or not proceed.
To skip verification, use --untrusted parameter.
If running in batch mode or not on the terminal, the installation aborts unless you specify the "--untrusted" option on the command line.
By default, the installer runs in interactive mode and may issue prompts. For automated scripts, use --batch parameter to suppress prompts.
Upgrade Procedures
- Download the Gateway update package.
- Upload the image to the Gateway system using, for example, the
scpcommand). Copy the image to the following location on the system: /var/lib/velocloud/software_update/vcg_update.tar - Connect to the Gateway console and run:
sudo /opt/vc/bin/vcg_software_update
Activate Replacement Partner Gateway
This section discusses activating a replacement Partner Gateway.
Overview
Gateway activation keys do not have the same default 30 day lifetime as Edges. In fact, a Gateway activation key has an infinite lifespan. If an on-premises Gateway fails and you want to replace it with a new Gateway using the same name and IP address, you can use the same activation key used for the original Gateway.
As a result, for most Gateway issues, creating a new VM provides the quickest method of recovery and register it with the Orchestrator using the failed Gateway activation key. This saves you a lot of time as Orchestrator pushes the existing configuration to this new instance. Most Partners prefer this approach over configuring a new Gateway from scratch.
Prerequisites
Before you can use this Gateway replacement method, you must adjust the System Property gateway.activation.validate.deviceID and set the value to false. To do this you or another Operator with a Superuser role must go to and search for gateway.activation and inspect gateway.activation.validate.deviceID. If the Value is already false, then you are ready for the next steps. If the Value is true, then a Gateway reactivation does not work, and you need to modify this System Property by selecting it.


Replacement Partner Gateway Workflow
- Locate the original activation key by navigating to and selecting the name of the Gateway you are replacing. Select the down arrow beside the name and note the activation key.
Figure 30. Gateway Management 
- Use the activation key to activate the replacement Gateway on your newly spun up
VM: /opt/vc/bin/activate.py-s vco_name_or_ip activation_key.
Custom Configurations
This section discusses custom configurations.
This topic contains the following sections:
NTP Configuration
Edit the /etc/ntpd.conf file to change the NTP configuration.
OAM Interface and Static Routes
OAM - SR-IOV with vmxnet3 or SR-IOV with VIRTIO
In some installations, a configuration provides the capability to mix and match and provide different interface types for the Gateway. This generally happens if you have an OAM without SR-IOV. This custom configuration requires additional steps since this causes the interfaces to become active out of order.
Record the MAC address of each interface.
Arista - After creating the VM, go to Edit Settings and copy the Mac address.

KVM - After defining the VM, run the following command:

Special Consideration When Using 802.1ad Encapsulation
In some instances, the 802.1ad devices do not populate the outer tag EtherType with 0x88A8. It requires a special change for user data to interoperate with these devices.
Assuming a Management VRF has a configuration with the S-Tag, 20, and the C-Tag, 100, edit the vrf_vlan section in / etc/ config/ gatewayd. Also, define resp_mode to 1 and allow the Gateway to relax its check to allow Ethernet frames with the incorrect EtherType of 0x8100 in the outer header.
SNMP Integration
For additional information on SNMP configuration, see https://www.net-snmp.org/docs/man/ documentation. To configure SNMP integration, use the following steps:
Custom Firewall Rules
To modify local firewall rules, edit the following file: /etc/iptables/rules.v4.
drop or accept rules. The Gateway appends its own rules to the table and, because the rules evaluate in order, it may prevent Gateway software from functioning properly.*filter :INPUT ACCEPT [0:0] -A INPUT -p udp -m udp --source 127.0.0.1 --dport 161 -m comment --comment "allow SNMP port" -j ACCEPT :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] COMMIT
netfilter service:
service netfilter-persistent restart service vc_process_monitor restart
Configure TACACS+ Authentication for Partner Gateways
Organizations use the Terminal Access Controller Access-Control System Plus (TACACS+) to authenticate administrators accessing network devices. On a Partner Gateway, TACACS+ authenticates SSH and console logins to the Gateway's Linux shell.
-
The Gateway is installed and activated. See Install Partner Gateway.
-
You have root access to the Gateway, either on the console or over SSH with a local administrator account (for example,
vcadmin). -
The TACACS+ server is reachable from the Gateway over TCP (port 49 by default). There is no source interface setting; the Gateway reaches the server through its routing table. Allow the traffic on any firewall between the Gateway and the server.
-
The TACACS+ server has the shared secret and the users who need access. The server must authorize these users for
service=pppandprotocol=ip, or for the service and protocol you set with--serviceand--protocol. -
Keep a local administrator account. Local accounts do not use the TACACS+ server, so you can still log in if the server is unavailable.
Unlike Edges, TACACS+ for a Partner Gateway is not configured from the Orchestrator. Configure it locally on each Gateway with the configure_tacacs.sh command.
Activate TACACS+
Deactivate TACACS+
sudo /opt/vc/bin/configure_tacacs.sh --disable
/etc/ssh/sshd_config.d/02-tacacs.conf in Step 3, delete it and reload sshd:
sudo rm -f /etc/ssh/sshd_config.d/02-tacacs.conf sudo sh -c 'sshd -t && systemctl reload ssh'
TACACS+ User Access
All TACACS+ users log in to the Gateway as the shared local account vctacacs. The SSH log records each user's TACACS+ username.
The Gateway does not use TACACS+ privilege levels. By default, TACACS+ users cannot run commands with sudo; use a local administrator account for tasks that require root access, or see "Allow TACACS+ users to use sudo". Control who can access the Gateway on the TACACS+ server.
Allow TACACS+ Users to Use Sudo
TACACS+ users can run commands with sudo after setting a password for the vctacacs account. All TACACS+ users share this password, and anyone who knows it can open SSH connections to the Gateway as vctacacs without TACACS+ authentication. Use a strong password and share it only with administrators who need root access.
Partner Gateway Upgrade and Migration
Network Configuration
Netplan stores network configuration files in /etc/netplan instead of the legacy /etc/network directory.
network:
version: 2
ethernets:
eth0:
addresses:
- 192.168.151.253/24
nameservers:
addresses:
- 8.8.8.8
- 8.8.4.4
search: []
routes:
- to: default
via: 192.168.151.1
- to: 192.168.0.0/16
via: 192.168.151.254
metric: 100
eth1:
addresses:
- 192.168.152.251/24
nameservers:
addresses:
- 8.8.8.8
search: []
routes:
- to: default
via: 192.168.152.1
echo 'network: {config: disabled}' > /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
Cloud-init
Example 1: Simple
meta-data:
instance-id: vcg1
local-hostname: vcg1
#cloud-config hostname: vcg1 password: Velocloud123 chpasswd: {expire: False} ssh_pwauth: True
Example 2: New-style network configuration (network-config file)
instance-id: vcg1 local-hostname: vcg1
#cloud-config hostname: vcg1 password: Velocloud123 chpasswd: {expire: False} ssh_pwauth: True ssh_authorized_keys: - ssh-rsa … rsa-key velocloud: vcg: vco: demo.velocloud.net activation_code: F54F-GG4S-XGFI vco_ignore_cert_errors: false runcmd: - 'echo “Welcome to VeloCloud”'
network-config Example 1:
version: 2
ethernets:
eth0:
addresses:
- 192.168.152.55/24
nameservers:
addresses:
- 8.8.8.8
- 8.8.4.4
routes:
- to: default
via: 192.168.152.1
eth1:
addresses:
- 192.168.151.55/24
nameservers:
addresses:
- 8.8.8.8
- 8.8.4.4
routes:
- to: default
via: 192.168.151.1
network-config Example 2:
version: 2
ethernets:
eth0:
addresses: [192.168.82.1/24]
eth1:
addresses: [70.150.1.1/24]
routes:
- { metric: 1, to: 0.0.0.0/0, via: 70.150.1.254 }
eth2:
addresses: [70.155.1.1/24]
routes:
- { metric: 2, to: 0.0.0.0/0, via: 70.155.1.254 }
Net-tools
| Old Net-tool Utilities | New Corresponding Net-tool Utilities |
|---|---|
| arp | ip n (ip neighbor) |
| ifconfig | ip a (ip addr), ip link, ip-s (ip-stats) |
| nameif | ip link, ifrename |
| netstat | ss, ip route (for netstat-r), ip-s link (for netstat-i), ip maddr (for netstat-g) |
| route | ip r (ip route) |
Sample Command Output for Net-tool Utilities
- ip n (ip neighbor):
root@SS-gateway-1:~# ip n 192.168.0.100 dev eth2 lladdr 00:50:56:84:85:d4 REACHABLE 192.168.0.250 dev eth2 lladdr 00:50:56:84:97:66 REACHABLE 13.1.1.2 dev eth0 lladdr 00:50:56:84:e7:fa REACHABLE root@SS-gateway-1:~#
- ip a (ipaddr):
root@SS-gateway-1:~# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 4096 link/ether 00:50:56:84:a0:09 brd ff:ff:ff:ff:ff:ff inet 13.1.1.1/24 brd 13.1.1.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::250:56ff:fe84:a009/64 scope link valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:50:56:84:a6:ab brd ff:ff:ff:ff:ff:ff inet 101.101.101.1/24 brd 101.101.101.255 scope global eth1 valid_lft forever preferred_lft forever inet6 fe80::250:56ff:fe84:a6ab/64 scope link valid_lft forever preferred_lft forever 4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:50:56:84:bc:75 brd ff:ff:ff:ff:ff:ff inet 192.168.0.201/24 brd 192.168.0.255 scope global eth2 valid_lft forever preferred_lft forever inet6 fe80::250:56ff:fe84:bc75/64 scope link valid_lft forever preferred_lft forever 6: gwd1: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 4096 link/none inet 169.254.129.1/32 scope global gwd1 valid_lft forever preferred_lft forever inet6 fe80::27d5:9e46:e7f7:7198/64 scope link stable-privacy valid_lft forever preferred_lft forever root@SS-gateway-1:~#
- ip link:
root@SS-gateway-1:~# ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 4096 link/ether 00:50:56:84:a0:09 brd ff:ff:ff:ff:ff:ff 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether 00:50:56:84:a6:ab brd ff:ff:ff:ff:ff:ff 4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether 00:50:56:84:bc:75 brd ff:ff:ff:ff:ff:ff 6: gwd1: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 4096 link/none root@SS-gateway-1:~#
Upgrade Considerations
Preserving the public IP of a VPN or NAT Gateway necessitates the following specific procedure.
Procedure: (VNP or NAT Gateways with well-known Public IP Addresses)
Gateways Without Well-known Public IPs
Obtaining Gateway Activation Key Via API
Sample response:
{"jsonrpc":"2.0","result":[{"id":1, "activationKey":"69PX-YHY2-N5PZ-G3UW …



























