Release Notes SD-WAN 6.8.0 Collector

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

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

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

# Identify redis master pod, if below command returns role:master then its master 
$ kubectl exec -it solutions-sdwan-viptela-redis-node-0 -- redis-cli info | grep role
Defaulted container "redis" out of: redis, sentinel
role:master

$ kubectl exec -it solutions-sdwan-viptela-redis-node-1 -- redis-cli info | grep role
Defaulted container "redis" out of: redis, sentinel
role:slave

$ kubectl exec -it solutions-sdwan-viptela-redis-node-2 -- redis-cli info | grep role
Defaulted container "redis" out of: redis, sentinel
role:slave

# Run below command in redis master pod
# Get last run stat for InstallerAgent
$ kubectl exec -it solutions-sdwan-viptela-redis-node-0 -- redis-cli hget "agentStat:lastRun" InstallerAgent
Defaulted container "redis" out of: redis, sentinel
"1718630725161"

# Use above timestamp and set value for DeviceDescriptionAgent
$ kubectl exec -it solutions-sdwan-viptela-redis-node-0 -- redis-cli hset agentStat:lastRun DeviceDescriptionAgent 1718630725161
Defaulted container "redis" out of: redis, sentinel
(integer) 0

# Check if it is updated
$ kubectl exec -it solutions-sdwan-viptela-redis-node-0 -- redis-cli hgetall "agentStat:lastRun"
Defaulted container "redis" out of: redis, sentinel
 1) "MigrationAgent"
 2) "1718630708228"
 3) "InstallerAgent"
 4) "1718630725161"
 5) "DeviceHealthAgent"
 6) "1718283934477"
 7) "InterfaceStatAgent"
 8) "1718283935780"
 9) "TunnelStatAgent"
10) "1718283938045"
11) "DeviceDescriptionAgent"
12) "1718630725161"

# Run PolicyParserAgent
$ sevone-cli solutions run_agent --deployment_name solutions-sdwan-viptela  --agent_name PolicyParserAgent  --log_level info

# Run NextHopTableAgent
$ sevone-cli solutions run_agent --deployment_name solutions-sdwan-viptela  --agent_name NextHopTableAgent  --log_level info 

$ sudo yum clean metadata

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 SevOne NMS > Administration > Flow Configuration > Flow Interface Manager.

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

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