Release Notes SD-WAN 6.7.0 Collector

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

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

• Device groups are no longer created based on the appliance name.
• Collector now updates the Description for devices in SevOne NMS in the following format.
  • VERSA::<device-type>, where device type is a type of appliance (such as a branch or controller).
• Device groups are now created based on the following:
  • Location of devices instead of the appliance names.
  • Metadata field Site-id available under SDWAN_DEVICES.
  • Metadata fields MSP Level and Tenant Level are available under the SDWAN_INFO.

• Metadata field Domain-id is now removed from the SDWAN_DEVICES namespace in case of fresh installation. However, in old setups, field Domain-id will remain as it is.
• Pinned devices are no longer available for old sites. They are now available for new location-based sites.
• If you modify the name of an existing location and then revert it to the original name, both locations will have pinned devices.

• If set to true, the DeviceDescriptionAgent will refrain from updating the IP addresses of SevOne NMS devices.
• If set to false, the DeviceDescriptionAgent will update the IP addresses.

• If set to true, the device flow mapping will use the device IPs provided during the device onboarding process.
• If set to false, the device flow mapping will rely on vDirector IPs.

• 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

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

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