Prerequisites
Network Management Architectureπ
Each system requires a management subnet that can support 5 system IP addresses as well as 3 IP addresses per managed switch. The breakdown is as follows:
| IP address Allocations for Management | Component | Allocation |
|---|---|---|
| Verity System components | vNetC LAN side, SDLC, ACS, Backend Services, Monitoring | 5 Static Addresses |
| Managed Switches | Verity Switch Controller | 1 Dynamic Address per switch |
| Managed Switches | Switch in ZTP Process | 1 Dynamic Address per switch |
| Managed Switches | Switch post ZTP Process | 1 Static Address per switch |
- vNetC
- Resolvable, fully qualified domain name
- Static IP address, gateway, DNS servers
- Valid Verity license
- SDLC
- IP addressing per table above. This must be routable to the vNetC!
- Controllers (within SDLC)
- IP Addressing per table above. The diagram above shows that the controllers are bridged to NIC 2 of the SDLC. The IP must be on the same VLAN/subnet as the SDLC!
-
Monitoring
- IP addressing per table above. This must be routable to the vNetC!
-
Routable or switched network between Verity components and managed switching devices (All TCP ports). For more information see the section titled Security.
- If using a router or firewall between Verity and the switches, the following ports must be allowed to pass.
- Port 8080 for gNMI
- Port 80 - HTTP (not needed if using TLS option for file downloads)
- Port 443 - HTTPS
- Port 22 - SSH
- Port 161 - SNMP
- Port 6343 - sFlow
- If using a router or firewall between Verity and the switches, the following ports must be allowed to pass.
Hypervisor Configuration (Required)π
VMwareπ
The VMware installation procedure is documented for VMware ESXi 7.0.3. VMware systems require this additional network configuration:
- ESXi
- Compute resources meeting Verity requirements based on the number of switches being managed. Use the VM Resource Calculator in Downloads to compute CPU and memory needs.
-
- The vNetC and SDLC should be on the same virtual switch in ESXi or at minimum they must be routable.
- Your system requires Promiscuous mode to be set to Accept.
- Your system requires MAC address changes to be set to Accept.
- Your system requires Forged transmits to be set to Accept.
These settings are needed because the SDLC bridges its Device Controller containers onto the management network, and each container sends and receives traffic with its own MAC address rather than the MAC address that ESXi assigned to the VM's virtual NIC. When these settings are set to Reject, ESXi drops that traffic.
Apply the settings only to the port group used by the Verity VMs, not to the entire virtual switch, and keep that port group dedicated to the management network. Promiscuous mode lets every VM on the port group receive all traffic on it, so do not attach unrelated VMs to that port group.
KVM and Proxmoxπ
KVM and Proxmox systems require this additional network configuration:
- KVM
- Compute resources meeting Verity requirements based on the number of switches being managed. Use the VM Resource Calculator in Downloads to compute CPU and memory needs.
- Virtual Switch
- The vNetC, SDLC and Monitoring should be on the same bridge or at minimum they must be routable.
Required Filesπ
Obtain the following files:
VMware Required Filesπ
| Description | Filename Example | File Type | Notes |
|---|---|---|---|
| vNetC VM Image | vNetC-x_x_x_x.ova | VMware OVA | Resources including vCPU and memory should be adjusted based on the VM Resource Calculator (see Downloads). Networking will need to be altered to the correct virtual switch names used in the server |
| vNetC βcoreβ Upgrade | core-x_x_x_x- full.tar | tarball | vNetC needs to be updated via GUI SD-Admin immediately after configuration and boot |
| SDLC VM Image | SDLC-x_x_x_x.ova | VMware OVA | Resources including vCPU and memory should be adjusted based on the VM Resource Calculator (see Downloads). Networking will need to be altered to the correct virtual switch names used in the server |
| SDLC Binary Firmware Upgrade | firmware-x_x_x_x.tar | tarball | SDLC should be upgraded via web page immediately after configuration and boot |
| Monitoring VM Image | monitoring_x.x.x.ova | VMware OVA | Resources including vCPU and memory should be adjusted based on the VM Resource Calculator (see Downloads). Networking will need to be altered to the correct virtual switch names used in the server |
| Monitoring Software Upgrade | monitoring_x.x.x.tar | tarball | Monitoring needs to be updated via GUI SD-Admin immediately after configuration and boot |
| License | license.cms or sitexxxxx.tar | License file | Is uploaded using GUI |
| Firmware Upgrade Package | firmware-x_x_x_x.tar | Binary | SDLC should be upgraded via web page immediately after configuration and boot |
KVM & Proxmox Required Filesπ
| Description | Filename Example | File Type | Notes |
|---|---|---|---|
| vNetC VM Image | vNetC-x_x_x_x.qcow2 | KVM qcow | Resources including vCPU and memory should be adjusted based on the VM Resource Calculator (see Downloads). Networking will need to be altered to the correct bridge names used in the server |
| vNetC βcoreβ Upgrade | core-x_x_x_x- full.tar | Tarball | vNetC needs to be updated via UI SD-Admin immediately after configuration and boot |
| SDLC VM Image | SDLC-x_x_x_x.qcow2 | KVM qcow | Resources including vCPU and memory should be adjusted based on the VM Resource Calculator (see Downloads). Networking will need to be altered to the correct virtual switch names used in the server |
| Firmware Upgrade Package | firmware-x_x_x_x.tar | Tarball | SDLC should be upgraded via system upgrader immediately after configuration and boot |
| Monitoring VM Image | monitoring_x.x.x.qcow2 | KVM qcow | Resources including vCPU and memory should be adjusted based on the VM Resource Calculator (see Downloads). Networking will need to be altered to the correct bridge names used in the server |
| Monitoring Upgrade Package | monitoring_x.x.x.tar | Tarball | Monitoring should be updated via UI AS-Admin immediately after configuration and boot |
| License | license.cms or sitexxxxx.tar | License file | Uploaded using UI |
| XML Parameters | vnetc.xml, SDLC.xml and monitoring.xml | xml | Default files are provided and are edited during the installation process. There are 4 available vNetC xml files covering the use cases of single or multiple NICs along with High Availability options |
