SD-WAN Viptela Collector Prerequisites & Common Questions

Edit online

About

Edit online

This document provides a list of questions that SevOne requires the user to respond to prior to a fresh install or an upgrade. For details on compatibility, please refer to Release Notes SD-WAN Collector > Resources & Requirements > section Compatibility Matrix.

Network Requirements

Edit online
  • Port exposed on Collector Server
    Inbound Port Description
    9995 Flow Augmentor input
  • Collector Outbound Connections
    Address Outbound Port Description
    vManage server 443 Viptela vManage API
    NMS server 443 NMS API
    NMS DNC server 9996 Flow Augmentor output
  • Ports required for K3s
    Address Outbound Port Description
    K3s supervisor & Kubernetes API Server 6443 The K3s server needs port 6443 to be accessible by all nodes
    Flannel VXLAN backend 8472 The nodes need to be able to reach other nodes over UDP port 8472 when using the Flannel VXLAN backend. However, if you do not use Flannel and provide your own custom CNI, then the ports needed by Flannel are not needed by K3s
    Kubelet Metrics 10250 All nodes must be accessible to each other on port 10250

for Fresh Installs only

Edit online
  Prerequisites for Viptela Fresh Installs Only Response
1 Please provide the output of Viptela sizing script to confirm the license capacity of SevOne NMS. <enter results here>
2 Have you verified the checksum of the installer file?

NOTE: If you do not know how to verify the checksum, please refer to SD-WAN Viptela Collector Upgrade Process Guide > section Upgrade Viptela Collector using Graphical User Interface > Step 5. If you are still not able to verify the checksum, please contact IBM SevOne Support.

 Yes / No
3 Please provide the following information.
  • NMS appliance IP address (NOTE: NMS cluster or appliance must be running.)
  • Username for an administrator-level account
  • Is password for NMS ready to share during the installation/upgrade session? (NOTE: Please ensure the graphical user interface (GUI) for API access and ssh passwords are available prior to the session.)
  • IP address of SevOne DNC where the flows need to be sent.
  • Port number for DNC where the flows are being sent. (NOTE: The default port number is 9996.)
  • IP address:
  • Username:
  • Yes / No:
  • DNC IP address:
  • DNC port:
4 Please provide the following information related to vManage.
  • IP address of targeted vManage
  • Username for vManage (vManage credentials with admin-level read privileges)
  • Is password for vManage ready to share during the session? (NOTE: Please ensure all passwords are available prior to the session.)
  • API port number of targeted vManage (NOTE: The default port number is 8443)
  • Protocol of targeted vManage (NOTE: The default protocol is https)
  • IP address:
  • Username:
  • Yes / No:
  • API port:
  • http / https:
5 Please provide the collector node IP address(es). <enter IP address(es)>
6 Does ICMP connectivity exist between the collector and the nameserver? Yes / No
7 Have you performed the health check on your SevOne NMS cluster to ensure that all critical services are up and running with no potential issues? If Yes, please share the results in the Response column.

NOTE: Execute SevOne-act check checkout --full-cluster command to perform the health check. If you do not have access to shell prompt, please contact IBM SevOne Support.

 <enter results here>
8 Have you checked the reachability of vManage from the collector PAS?

If Yes, please share the result of curl command in the Response column.

NOTE: Please check the reachability by running the following command:
curl -u <vmanage_user>:<vmanage_password>--url "https://<vmanage_ip>:<vmanage_port>/dataservice/device" -k
If you do not have access to shell prompt, please contact IBM SevOne Support.

 <enter output of curl command>
9 Please provide the Managed Service Provider (MSP) name for the configured vManage.

NOTE: MSP name is used to create a device group containing all devices which are created by the collector.

 <enter details here>
10 Please provide the Tenant / Enterprise Name available in vManage for the collection of data.

NOTE: To check the Tenant Name on vManage, go to Administration > Settings > Organization Name.

 <enter details here>
11 Do you want to distribute devices created by the collector among all or some peers of the NMS cluster?

NOTE: If you want to distribute devices to some peers only then, please provide the IP addresses / peer names of those selected peers in the Response column.

 <All / Some>
<If Some, please enter IP addresses / peer names of selected peers>
12 Do you want to monitor flow? Please circle one option in the Response column. Yes / No
13 Do you want to enable custom site grouping? Please circle one option in the Response column.

NOTE: Once enabled, you can create a custom site grouping using the device metadata. If the two devices have the same name (matching of name is case-insensitive), collector will create the site with the name from the REST API response.

 Yes / No
14 Do you want to prevent suffixing the device names (created by collector) with the tenant name? Please circle one option in the Response column. If yes, please ensure that all device hostnames are unique across all tenants.

NOTE: This setting cannot be changed in subsequent upgrades.

 Yes / No
15 Is NTP synchronization enabled on the PAS, collector/augmentor, and vManage? Please circle one option in the Response column. Yes / No
16 Please highlight any detail that must be addressed during the fresh installation session. <enter details>

for Upgrades only

Edit online
  Prerequisites for Viptela Upgrades Only Response
1 Please provide the output of Viptela sizing script to confirm the license capacity of SevOne NMS. <enter results here>
2 Please provide NPM version being installed. <enter version here>
3 Have you verified the checksum of the installer file?

NOTE: If you do not know how to verify the checksum, please refer to SD-WAN Viptela Collector Upgrade Process Guide > section Upgrade Viptela Collector using Graphical User Interface > Step 5. If you are still not able to verify the checksum, please contact IBM SevOne Support.

 Yes / No
4 Please provide the following information.
  • NMS appliance IP address (NOTE: NMS cluster or appliance must be running.)
  • IP address of SevOne DNC where the flows need to be sent.
  • Port number for DNC where the flows are being sent. (NOTE: The default port number is 9996)
  • IP address:
  • DNC IP address:
  • DNC port:
5 Please provide the collector node IP address(es). <enter IP address(es)>
6 Does ICMP connectivity exist between the collector and the nameserver? Yes / No
7 Have you performed the health check on your SevOne NMS cluster to ensure that all critical services are up and running with no potential issues? If Yes, please share the results in the Response column.

NOTE: Execute SevOne-act check checkout --full-cluster command to perform the health check.
If you do not have access to shell prompt, please contact IBM SevOne Support.

 <enter results here>
8 Is there any port available for GUI Installer and API?
NOTE:
  • The default port number for GUI Installer is 3000.
  • The default port number for API is 3001.
 <Yes / No>
<If Yes, please provide the port number for GUI Installer and API>
9 Please highlight any detail that must be addressed during the upgrade session. <enter details>