Release Notes SD-WAN 7.1.0 Collector

1.28.10+k3s1 (for new provisioning)

• 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: Advanced Health

Indicators:

• Over Capacity Drops
• Tunnel Count

Versa Collector: The following indicators have been added to Interface object from IntfUtilLog when the InterfaceStatStreamingAgent is enabled.

Object: Interface object

Indicators:

• up_capacity_percentage
• down_capacity_percentage

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

If BFD Session data is not found for a specific object, the following occurs:

• Not found bfd session for key warning string is logged in the collector logs.
• The ApprouteStatStatistic response displays a down state for the specific objectName.
• Empty values appear for availability and transition indicators on NMS.
• Gaps may appear on the NMS graph for these indicators, which is expected behavior.

Versa Collector: When upgrading the SD-WAN Versa Collector from version 2.15 or later to 7.0.0 or above, 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

Fortinet Collector: During a fresh installation or upgrade, the SDWAN plugin will not automatically activate the HTTP plugin in the Fortinet device. As a result, HTTP objects will not be created, and data collection will not occur on the Fortinet device. This is an expected behavior.

However, manually enabling the SDWAN plugin activates the HTTP plugin and creates an HTTP object. Data collection begins after the next automatic or manual rediscovery of the Fortinet device, allowing the device to effectively monitor the network and connectivity issues.

• 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)

Platform: 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.

VeloCloud Collector: During a fresh installation or upgrade, the SDWAN plugin will not automatically activate the HTTP plugin in the VeloCloud device. As a result, HTTP objects will not be created, and data collection will not occur on the VeloCloud device. This is an expected behavior.

However, manually enabling the SDWAN plugin activates the HTTP plugin and creates an HTTP object. Data collection begins after the next automatic or manual rediscovery of the VeloCloud device, allowing the device to effectively monitor the network and connectivity issues.

/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": []}
 

Workaround: Run the commands as shown below and proceed with the upgrade process.

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.

S1NPM-112547 / S1NPM-112715

Workaround: Please click on Try to load anyway to proceed with loading the report without any conflicts.

/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.

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

sevone-cli playbook postcheck

Error:

TASK [reports : Check script response] *************************************************
****************************************************************************************
fatal: [sevonek8s]: FAILED! => {"changed": false, "msg": "AUTHENTICATING CLIENT...\nFETCHING ALL DATASOURCES...\nSELECTED DATASOURCE: 'SevOne' WITH ADDRESS: 
'10.49.12.97'\nUPLOADING REPORTS...\nRESULTS\n----------\nSUCCESS: Indicator Summary Calendar View     \nSUCCESS: SDWAN Device Health Object Summary

Workaround: The OOTB reports are still imported, and the installation or upgrade during post-check will continue as expected without any conflicts. Please refer to Versa Collector - Deployment guides for details.

sevone-cli playbook postcheck

Error:

TASK [reports : Check script response] *************************************************
****************************************************************************************
fatal: [sevonek8s]: FAILED! => {"changed": false, "msg": "AUTHENTICATING CLIENT...\nFETCHING ALL DATASOURCES...\nSELECTED DATASOURCE: 'SevOne' WITH ADDRESS: 
'10.49.12.97'\nUPLOADING REPORTS...\nRESULTS\n----------\nSUCCESS: Indicator Summary Calendar View     \nSUCCESS: SDWAN Device Health Object Summary

Workaround: The OOTB reports are still imported, and the installation or upgrade during post-check will continue as expected without any conflicts. Please refer to Viptela Collector - Deployment guides for details.