Release Notes SD-WAN 7.0.0 Collector

1.27.1 (for upgrades)
1.27.1 (for new provisioning)

• signature-tools- -build.<latest>.tgz
• signature-tools- -build.<latest>.tgz .sha256.txt

• signature-tools-v2.0.3-build.1.tgz
• signature-tools-v2.0.3-build.1.tgz .sha256.txt

VeloCloud: The following object has been added along with its associated indicators.

Object: QoE - After

Indicators:

1. scoreAfterVoice
2. scoreAfterVideo
3. scoreAfterTrans

VeloCloud: The following object has been added along with its associated indicators.

Object: QoE - {Link Name}. The field Link Name dynamically appears based on the values returned from API calls to individual devices.

Indicators:

1. scoreBeforeVoice
2. scoreBeforeVideo
3. scoreBeforeTrans

Viptela Collector: A new variable prechecks.dnc.enabled has been added to enable/disable DNC-related prechecks. The default value is true.

• If set to true, all prechecks related to DNC will be executed.
• If set to false, the following prechecks will be skipped.
  • Validate DNC IPs are part of the cluster
  • Check reachability to DNC
  • Check reachability to DNC IP address

Versa Collector: Flow augmentor now creates a separate log folder for each version.

To review the augmentor logs, log into the node IP (via SSH) where the augmentor pod is running, and then navigate to the directory /var/log/sdwan-versa/<deployment_name>/<build_version>/FlowAugmentor/

$ ./deploy.sh <widget-tar-file-name> --force --delete-old-widgets

Versa Collector: The following metadata fields have been added to store the source and destination access circuits for tunnels.

• SDWAN_TUNNEL.SRC_TRANSPORT
• SDWAN_TUNNEL.DST_TRANSPORT

Viptela Collector: A new variable prechecks.dnc.enabled has been added to enable/disable DNC-related prechecks. The default value is true.

• If set to true, all prechecks related to DNC will be executed.
• If set to false, the following prechecks will be skipped.
  • Validate DNC IPs are part of the cluster
  • Check reachability to DNC
  • Check reachability to DNC IP address

Workaround: Please try to deploy the collector after ~ 10 minutes, as Kubernetes requires some time to clean up stale ports.

• Without selecting or updating the configuration file (in the Config stage).
• Even if there are errors in the configuration file (in the Config stage).

Versa Collector: When upgrading the SD-WAN Versa Collector from version 2.15 or later to 7.0.0, you may encounter the following error.

msg": "Timeout when waiting...

To resolve this issue, perform the following steps:

1. Login to master node, applicable for both single and multi-node scenarios.
2. $ sevone-cli playbook reset
3. $ sudo reboot
4. $ sevone-cli cluster up
5. $ sevone-cli playbook postcheck

• Wan Path Source (4323)
• Wan Path Source Alternate Name (4354)
• Wan Path Destination (4323)
• Wan Path Destination Alternate Name (4355)
• Tunnel (4353)
• Tunnel Alternate Name (4356)

Interface statistics are not generated for the sub-interfaces; an expected behavior from Cisco. sdwan::device-interface objects for interfaces are created to provide interface statistics datapoints.

Since the mapping is performed for interface objects available in SevOne NMS, the ifIndex is not renamed to interface name for the sub-interfaces in Flow Interface Manager.

Error: Type Error: "None Type" object is not subscriptable.

Workaround: By following these steps, you should be able to retrieve the requester's user datasource, update the post-checks, and complete the post-check process without any errors

The task Execute script to load the OOTB report has now completed successfully.

$ /usr/local/sbin/SevOne-validate-image \
-i $(ls -Art /opt/SevOne/upgrade/sevone_solutions_sdwan_versa-*.tgz | tail -n 1) \
-s $(ls -Art /opt/SevOne/upgrade/sevone_solutions_sdwan_versa-*.tgz.sha256.txt | tail -n 1) \
--installer solutions  --installer-opts '--no_screen'
 

Error:

TASK [helm upgrade/install default/solutions-sdwan-versa] ***************************************************************************
fatal: [sevonek8s]: 
FAILED! => {"changed": true, "cmd": "helm upgrade solutions-sdwan-versa local/solutions-sdwan-versa -o json --install --create-namespace --namespace default --timeout=5m --insecure-skip-tls-verify --devel --atomic  -f /tmp/ansible.wLFGEx/solutions-sdwan-versa_custom_guii.yaml  \n", "delta": "0:10:02.543798", "end": "2023-03-27 02:44:03.478942", "msg": 
"non-zero return code", "rc": 1, "start": "2023-03-27 02:34:00.935144", "stderr": "W0327 02:34:02.451394  997524 warnings.go:70] spec.template.spec.containers[0].env[7].name: duplicate name \"MINER_DATA_SOURCE\"\nW0327 02:34:02.712946  997524 warnings.go:70] spec.template.spec.containers[0].env[4].name: 
duplicate name \"SECRETS_API_NAME\"\nW0327 02:39:03.266490  997524 warnings.go:70] spec.template.spec.containers[0].env[7].name: duplicate name \"MINER_DATA_SOURCE\"\nW0327 02:39:03.348819  997524 warnings.go:70] spec.template.spec.containers[0].env[4].name: duplicate name \"SECRETS_API_NAME\"\nError: 
UPGRADE FAILED: an error occurred while rolling back the release. original upgrade error: timed out waiting for the condition: release solutions-sdwan-versa failed: timed out waiting for the condition", "stderr_lines": ["W0327 02:34:02.451394  997524 warnings.go:70] spec.template.spec.containers[0].env[7].name: 
duplicate name \"MINER_DATA_SOURCE\"", "W0327 02:34:02.712946  997524 warnings.go:70] spec.template.spec.containers[0].env[4].name: duplicate name \"SECRETS_API_NAME\"", "W0327 02:39:03.266490  997524 warnings.go:70] spec.template.spec.containers[0].env[7].name: duplicate name \"MINER_DATA_SOURCE\"", "W0327 02:39:03.348819  997524 warnings.go:70] spec.template.spec.containers[0].env[4].name: duplicate name \"SECRETS_API_NAME\"", 
"Error: UPGRADE FAILED: an error occurred while rolling back the release. original upgrade error: timed out waiting for the condition: release solutions-sdwan-versa failed: timed out waiting for the condition"], "stdout": "", "stdout_lines": []}
 

$ ssh sevone@<SD-WAN collector 'control plane' node IP address or hostname>
 

$ sevone-cli cluster down
 

$ sevone-cli cluster up
 

Please refer to SD-WAN Versa Collector Upgrade Process Guide for details.

$ /usr/local/sbin/SevOne-validate-image \
-i $(ls -Art /opt/SevOne/upgrade/sevone_solutions_sdwan_viptela-*.tgz | tail -n 1) \
-s $(ls -Art /opt/SevOne/upgrade/sevone_solutions_sdwan_viptela-*.tgz.sha256.txt | tail -n 1) \
--installer solutions  --installer-opts '--no_screen'

Error:

TASK [helm : helm upgrade/install default/solutions-sdwan-viptela] *****************************************************
fatal: [sevonek8s]: FAILED! =>

{"changed": true, "cmd": "helm upgrade solutions-sdwan-viptela local/solutions-sdwan-viptela -o json --install --create-namespace --namespace default --timeout=5m --insecure-skip-tls-verify --devel --atomic  -f /tmp/ansible.phf6sgc1/solutions-sdwan-viptela_custom_guii.yaml   --set=multiTenant=False\n",
 "delta": "0:05:36.590937", "end": "2024-09-25 11:39:10.474620",
 "msg": "non-zero return code", "rc": 1, "start": "2024-09-25 11:33:33.883683",
 "stderr": "W0925 11:33:47.000633 1465726 warnings.go:70] spec.template.spec.containers[0].env[4].name: duplicate name \"SECRETS_API_NAME\"\nW0925 11:38:48.180808 1465726 warnings.go:70] spec.template.spec.containers[0].env[4].name: duplicate name \"SECRETS_API_NAME\"\nError: UPGRADE FAILED: release solutions-sdwan-viptela failed, and has been rolled back due to atomic being set: context deadline exceeded",
 "stderr_lines": ["W0925 11:33:47.000633 1465726 warnings.go:70] spec.template.spec.containers[0].env[4].name: duplicate name \"SECRETS_API_NAME\"", "W0925 11:38:48.180808 1465726 warnings.go:70]spec.template.spec.containers[0].env[4].name: duplicate name \"SECRETS_API_NAME\"", "Error: UPGRADE FAILED: release solutions-sdwan-viptela failed, and has been rolled back due to atomic being set: context deadline exceeded"],
 "stdout": "", "stdout_lines": []}

Workaround: Rerun the command above and proceed with the upgrade process. Refer to SD-WAN Viptela Collector Upgrade Process Guide.