Release Notes SD-WAN 8.0.0 Collector

Edit online

Below please find the Release Notes for SD-WAN 8.0.0 collector (Release Date: July 24, 2025). Please contact your Technical Account Manager (if applicable) or Systems Engineering Team or Support Team to discuss and plan the installation. Thank you for being a customer.

Note: Terminology usage...

In SD-WAN guides if there is,

  • [any reference to master] OR
  • [[if a CLI command (for NMS or Kubernetes or Redis) contains master] AND/OR
  • [its output contains master]], it means leader or control plane.

And, if there is any reference to slave or worker, it means follower or agent.

Browser Requirements

Edit online

Minimum Resolution:1200x768 Browsers:

  • Modern, standards-compliant browser
  • JavaScript enabled
  • Pop-up blocker disabled for hostname/IP

The following browsers are supported in the current versions of SevOne.

Browser

Vendor Family
Google Chrome
Mozilla Firefox
Important: Please use the latest browser version for Chrome and Firefox.

Resources & Requirements

Edit online
Contains the following topics.
Resource Requirement
SevOne NMS Please refer to Compatibility Matrix below for SevOne NMS versions supported.
Helm 3.15.3
Kubernetes 1.28.10+k3s1 (for upgrades)

1.28.10+k3s1 (for new provisioning)

Important: If the installed Kubernetes version in your setup is not supported by SD-WAN collector you are provisioning, you will get an error message. Kubernetes must be upgraded prior to upgrading SD-WAN collector.
Kernel 4.18.0-553.56.1.el8_10.x86_64
Ports Required Please refer to SevOne NMS Port Number Requirements Guide > section Solutions Deployment.
VMware vSphere Client >=6.5
Signature Tools
Note: The latest files can be downloaded from IBM Passport Advantage (https://www.ibm.com/software/passportadvantage/pao_download_software.html) via Passport Advantage Online. However, if you are on a legacy / flexible SevOne contract and do not have access to IBM Passport Advantage but have an active Support contract, please contact SevOne Support Team for the file.

Once you have downloaded the package, unpack the fix / install / upgrade packs to obtain the required files.

  • signature-tools-v2.0.3-build.1.tgz
  • signature-tools-v2.0.3-build.1.tgz.sha256.txt
Other
Note: The latest files can be downloaded from IBM Passport Advantage (https://www.ibm.com/software/passportadvantage/pao_download_software.html) via Passport Advantage Online. However, if you are on a legacy / flexible SevOne contract and do not have access to IBM Passport Advantage but have an active Support contract, please contact SevOne Support Team for the files.

Once you have downloaded the package, unpack the fix / install / upgrade packs to obtain the required files.

Aruba EdgeConnect, Cisco SD-WAN, Fortinet, Palo Alto Prisma and VeloCloud are packaged with SevOne NMS as SD-WAN plugins.
Note: The File Type details for the SD-WAN plugins are the same as those for SevOne NMS resources. Please refer to the Third-Party Packages / Resources Required section in Release Notes SevOne NMS 8.0.0.
SD-WAN Widgets

  • sdwan-widgets-v8.0.0-build.4.tar.gz

  • sdwan-widgets-v8.0.0-build.4.tar.gz.sha256.txt

Summary for complex table
File Type Versa Viptela
TAR sevone_solutions_sdwan_versa-v8.0.0-build.38.tgz sevone_solutions_sdwan_viptela-v8.0.0-build.70.tgz
CHECKSUM sevone_solutions_sdwan_versa-v8.0.0-build.38.tgz.sha256.txt sevone_solutions_sdwan_viptela-v8.0.0-build.70.tgz.sha256.txt
OVA sevone_solutions_sdwan_versa-v8.0.0-build.38.ova sevone_solutions_sdwan_viptela-v8.0.0-build.70.ova
QCOW2 sevone_solutions_sdwan_versa-v8.0.0-build.38.qcow2 sevone_solutions_sdwan_viptela-v8.0.0-build.70.qcow2
ISO sevone_solutions_sdwan_versa-v8.0.0-build.38.iso sevone_solutions_sdwan_viptela-v8.0.0-build.70.iso
VHD sevone_solutions_sdwan_versa-v8.0.0-build.38.vhd.gz-part-1 sevone_solutions_sdwan_viptela-v8.0.0-build.70.vhd.gz-part-1

Facts & Limitations

Edit online

The following notes are some facts and limitations that you must be aware of.

Note: Controllers Aruba EdgeConnect, Cisco SD-WAN, Fortinet Plugin, Prisma (Palo Alto), and VeloCloud come integrated with SevOne NMS.
Important: Viptela Collector: vManage rate limits

The vManage overall rate limit is 450 requests per second. Currently, it has an API route related to device statistics which has a much lower rate limit of 43 requests per minute (or 0.72 requests per second). These rate limits are used as default rates in the Viptela collector configuration.

For the Viptela collector, each Agent has a vManage session.

Please refer to https://developer.cisco.com/docs/sdwan/#!browsing-returned-results-sorting-results-filtering-results-and-rate-limits/understanding-pagination for details.

Important: Viptela Collector: vManage data (Case change for names)

Collector handles the case change scenario for vManage data. Migration script removes the device / object group rules and adds new case-insensitive rules in the next run of deviceDescription / objectDescription agent.

Limitations:
  • Collector handles the case change only and not a complete name change.
  • In case of device name changes, collector does not change the actual device name in SevOne NMS. However, it keeps pushing data in the existing device.
  • In case of site / tenant name changes, collector does not update the device / object group name in SevOne NMS. However, it holds all the devices / objects available in the group.
  • In case of interface name changes, collector does not update the interface, interface queue, or tunnel name. However, it keeps pushing data for that object.
  • Collector does not support a scenario in which the device / interface name is same with a case difference in vManage. For example, device names, abc and ABC are not allowed.
Important: Viptela / Versa Collector

When upgrading the collector from a newly deployed SD-WAN 2.9 or SD-WAN 2.10 OVA to SD-WAN 8.0.0, please perform the steps mentioned in SD-WAN Viptela Collector Troubleshooting Guide or SD-WAN Versa Collector Troubleshooting Guide > section Upgrade Collector.

Important: Versa Collector

Tunnel data is coming from two different sources (sdwanB2BSlamLog and monStatsLog). Hence, the data gap might be visible in SevOne NMS.

Compatibility Matrix

Edit online
Platform / Component Versions supported (T – Tested & S – Supported)
SevOne NMS

8.0.0 (T & S)

7.2.0 (T & S)

7.1.0 (T & S)
REST API 2.1.47
Widget Version 8.0.0
SevOne Data Insight 8.0 (T & S)

CONTROLLERS

Edit online
Controller Versions supported (T – Tested & S – Supported)
Aruba EdgeConnect
  • 9.5.3 (T & S)
  • 9.4.1 (S)
Cisco SD-WAN
  • 20.16.1 (S)
  • 20.3.5 (S)
  • 20.12.4.1 (S)
Fortinet
  • v7.6.2 FortiManager (T & S)
  • v7.4.5 FortiManager (T & S)
  • v7.4.2 FortiManager (T & S)
  • v7.4.1 FortiManager (S)
Prisma (Palo Alto)
  • 6.5.1-b5 (T & S)
VeloCloud
  • VMware SASE 6.4.0.0 (T & S)
  • VMware SASE 5.4.0.1 (T & S)
  • VMware SASE 5.4.0.0 (S)
Controller Type Versions supported (T – Tested & S – Supported)
Versa n/a
  • 22.1.4 (T & S)
  • 22.1.2 (S)
  • 21.1.4 (T & S)
  • 21.2.3 (S)
Viptela vManage
  • 20.16.1 (S)
  • 20.13.1 (S)
  • 20.12.4.1 (S)
  • 20.11.1.1 (T & S)
  • 20.9.4 (S)
  • 20.9.1 (S)
  • 20.6.4 (T & S)
  • 20.6.2.1 (S)
  • 20.5.1.2 (S)
  • 20.5.1 (S)
  • 20.4.1.1 (S)
  • 20.3.6 (S)
  • 20.3.5 (T & S)
  • 20.3.4.1 (S)
  • 20.3.4 (S)
  • 20.3.3.1 (S)
  • 20.3.1 (S)
  • 20.1.1 (S)
  • 19.2.2 (S)
vEdge
  • 20.9.1 (T & S)
  • 20.6.1. -2 (T & S)
cEdge
  • 17.9.1 (T & S)
  • 17.6.02 (T & S)
  • 16.9.2 (S)
Note: Other requirements
Minimum resource needed on NMS for Versa and Viptela controllers:
  • CPU: 4 or more
  • RAM: 8GB or more
  • HDD: 20GB or more
Note: For additional details on hardware requirements such as, CPUs, RAM, flow limits, number of rack units, etc., for various hardware components, please contact your SevOne Technical Account Manager.
Note: SevOne Data Insight
  • Please refer to Release Notes SevOne Data Insight for details.

SevOne NMS

  • An administrator-level account in SevOne NMS.
  • User name and password for the administrator-level account.
  • IP address of the PAS.
  • 20k (vPAS_20K) appliance (minimum requirement).

New Features / Enhancements

Edit online
  • Vendor, Prisma Palo Alto, has been added to IBM SevOne’s SD-WAN solution.
  • Versa Collector: New indicators pdu_loss_ratio, fwd_loss, and rev_loss have been added to the Tunnel Object from sdwanB2BSlamLog.

Resolved Issues

Edit online
Component/s Key Release Notes
SDWAN Fortinet S1NPM-109504 Fortinet Collector: During a fresh installation or upgrade, the SD-WAN plugin on Fortinet devices now automatically activates the HTTP plugin. As a result, HTTP objects are created, and data collection functions as expected.
SDWAN Solution S1NPM-112216 Platform: With multiple users in SevOne Data Insight, the post-check task completes as intended.
SDWAN VeloCloud S1NPM-112223 VeloCloud Collector: During a fresh installation or upgrade, the SD-WAN plugin on VeloCloud devices now automatically activates the HTTP plugin. As a result, HTTP objects are created, and data collection functions as expected. This issue has now been resolved.
SDWAN VeloCloud S1NPM-114443 VeloCloud Collector: After upgrading to SevOne NMS 7.2.0 from 7.1.0, all relevant attributes, including Coordinates, Model, and Serial Number are displaying as expected in SevOne NMS 7.2.0.
SDWAN Fortinet Fortinet Collector: After upgrading to SevOne NMS 7.2.0 from 7.1.0, all relevant attributes, including Coordinates, Model, and Serial Number are displaying as expected in SevOne NMS 7.2.0.
SDWAN Solution S1NPM-114600 Flow Augmentor: Source template contains the missing field id, 48, and sampling rate.
SDWAN VeloCloud S1NPM-115128 VeloCloud Collector: During the installation or upgrade of the collector, the HTTP Poller for the orchestrator device works as expected.
SDWAN Solution S1NPM-115437 Flow Augmentor: Source template passes all the fields and templates after Flow Augmentation.
SDWAN Viptela S1NPM-115470 Platform: In certain scenarios, FlowInterfaceManager displays ifIndex instead of interfaceName / objectName. This is acceptable and details can viewed in Support Ticket DT436910. Duplicate object mapping has also been addressed with this release.
SDWAN VeloCloud S1NPM-116862 When upgrading SevOne Data Insight version 7.2.x to 8.0.x, adding the VeloCloud datasource now allows the VeloCloud SDWAN Site Summary reports and their corresponding widgets to load as expected.

9 issues

CVEs

Edit online
Important: It is strongly recommended to run the external security scans such as Nessus, Snyk, or similar on the latest available patch for this release to verify whether the vulnerability has been addressed. If upgrading the production environment is not currently possible, these scans can still be performed in a lab or test environment.
CVEs CVEs (continued) CVEs (continued)

CVE-2020-26555

CVE-2021-46909

CVE-2021-46939

CVE-2021-46972

CVE-2021-46984

CVE-2021-47018

CVE-2021-47069

CVE-2021-47073

CVE-2021-47097

CVE-2021-47101

CVE-2021-47236

CVE-2021-47257

CVE-2021-47257

CVE-2021-47284

CVE-2021-47287

CVE-2021-47289

CVE-2021-47304

CVE-2021-47310

CVE-2021-47311

CVE-2021-47321

CVE-2021-47338

CVE-2021-47352

CVE-2021-47353

CVE-2021-47356

CVE-2021-47373

CVE-2021-47383

CVE-2021-47384

CVE-2021-47385

CVE-2021-47386

CVE-2021-47393

CVE-2021-47408

CVE-2021-47412

CVE-2021-47432

CVE-2021-47441

CVE-2021-47455

CVE-2021-47456

CVE-2021-47461

CVE-2021-47466

CVE-2021-47468

CVE-2021-47491

CVE-2021-47495

CVE-2021-47497

CVE-2021-47527

CVE-2021-47548

CVE-2021-47560

CVE-2021-47579

CVE-2021-47582

CVE-2021-47609

CVE-2021-47624

CVE-2022-48619

CVE-2022-48632

CVE-2022-48743

CVE-2022-48747

CVE-2022-48754

CVE-2022-48757

CVE-2022-48760

CVE-2022-48804

CVE-2022-48836

CVE-2022-48866

CVE-2023-5090

CVE-2023-28746

CVE-2023-45286

CVE-2023-52451

CVE-2023-52463

CVE-2023-52464

CVE-2023-52469

CVE-2023-52470

CVE-2023-52471

CVE-2023-52476

CVE-2023-52478

CVE-2023-52486

CVE-2023-52522

CVE-2023-52530

CVE-2023-52560

CVE-2023-52605

CVE-2023-52615

CVE-2023-52619

CVE-2023-52622

CVE-2023-52623

CVE-2023-52626

CVE-2023-52648

CVE-2023-52653

CVE-2023-52658

CVE-2023-52662

CVE-2023-52667

CVE-2023-52669

CVE-2023-52675

CVE-2023-52679

CVE-2023-52683

CVE-2023-52686

CVE-2023-52700

CVE-2023-52703

CVE-2023-52707

CVE-2023-52730

CVE-2023-52756

CVE-2023-52762

CVE-2023-52764

CVE-2023-52775

CVE-2023-52777

CVE-2023-52781

CVE-2023-52784

CVE-2023-52791

CVE-2023-52796

CVE-2023-52798

CVE-2023-52800

CVE-2023-52803

CVE-2023-52809

CVE-2023-52811

CVE-2023-52813

CVE-2023-52817

CVE-2023-52832

CVE-2023-52834

CVE-2023-52835

CVE-2023-52840

CVE-2023-52845

CVE-2023-52847

CVE-2023-52864

CVE-2023-52877

CVE-2023-52878

CVE-2023-52881

CVE-2023-6040

CVE-2024-2201

CVE-2024-10379

CVE-2024-10980

CVE-2024-21823

CVE-2024-23848

CVE-2024-24786

CVE-2024-26583

CVE-2024-26584

CVE-2024-26585

CVE-2024-26586

CVE-2024-26595

CVE-2024-26600

CVE-2024-26614

CVE-2024-26638

CVE-2024-26640

CVE-2024-26645

CVE-2024-26649

CVE-2024-26656

CVE-2024-26660

CVE-2024-26665

CVE-2024-26669

CVE-2024-26675

CVE-2024-26686

CVE-2024-26698

CVE-2024-26704

CVE-2024-26717

CVE-2024-26720

CVE-2024-26733

CVE-2024-26735

CVE-2024-26740

CVE-2024-26759

CVE-2024-26769

CVE-2024-26772

CVE-2024-26773

CVE-2024-26801

CVE-2024-26802

CVE-2024-26804

CVE-2024-26810

CVE-2024-26826

CVE-2024-26837

CVE-2024-26840

CVE-2024-26843

CVE-2024-26846

CVE-2024-26852

CVE-2024-26853

CVE-2024-26855

CVE-2024-26859

CVE-2024-26870

CVE-2024-26878

CVE-2024-26880

CVE-2024-26894

CVE-2024-26906

CVE-2024-26907

CVE-2024-26908

CVE-2024-26921

CVE-2024-26923

CVE-2024-26925

CVE-2024-26939

CVE-2024-26940

CVE-2024-26958

CVE-2024-26960

CVE-2024-26961

CVE-2024-26974

CVE-2024-26982

CVE-2024-27010

CVE-2024-27011

CVE-2024-27013

CVE-2024-27019

CVE-2024-27020

CVE-2024-27025

CVE-2024-27042

CVE-2024-27065

CVE-2024-27388

CVE-2024-27395

CVE-2024-27397

CVE-2024-27410

CVE-2024-27434

CVE-2024-31076

CVE-2024-33621

CVE-2024-35789

CVE-2024-35790

CVE-2024-35801

CVE-2024-35807

CVE-2024-35809

CVE-2024-35810

CVE-2024-35814

CVE-2024-35823

CVE-2024-35824

CVE-2024-35835

CVE-2024-35838

CVE-2024-35845

CVE-2024-35847

CVE-2024-35852

CVE-2024-35853

CVE-2024-35854

CVE-2024-35855

CVE-2024-35876

CVE-2024-35877

CVE-2024-35884

CVE-2024-35888

CVE-2024-35890

CVE-2024-35893

CVE-2024-35896

CVE-2024-35897

CVE-2024-35899

CVE-2024-35900

CVE-2024-35910

CVE-2024-35912

CVE-2024-35924

CVE-2024-35925

CVE-2024-35930

CVE-2024-35937

CVE-2024-35938

CVE-2024-35944

CVE-2024-35946

CVE-2024-35947

CVE-2024-35952

CVE-2024-35958

CVE-2024-35959

CVE-2024-35960

CVE-2024-35962

CVE-2024-35989

CVE-2024-36000

CVE-2024-36004

CVE-2024-36005

CVE-2024-36006

CVE-2024-36007

CVE-2024-36010

CVE-2024-36016

CVE-2024-36017

CVE-2024-36020

CVE-2024-36025

CVE-2024-36270

CVE-2024-36286

CVE-2024-36489

CVE-2024-36883

CVE-2024-36886

CVE-2024-36889

CVE-2024-36896

CVE-2024-36901

CVE-2024-36902

CVE-2024-36904

CVE-2024-36905

CVE-2024-36917

CVE-2024-36919

CVE-2024-36920

CVE-2024-36921

CVE-2024-36922

CVE-2024-36924

CVE-2024-36927

CVE-2024-36929

CVE-2024-36933

CVE-2024-36939

CVE-2024-36940

CVE-2024-36941

CVE-2024-36945

CVE-2024-36950

CVE-2024-36952

CVE-2024-36953

CVE-2024-36954

CVE-2024-36960

CVE-2024-36971

CVE-2024-36978

CVE-2024-36979

CVE-2024-37356

CVE-2024-38538

CVE-2024-38555

CVE-2024-38558

CVE-2024-38559

CVE-2024-38570

CVE-2024-38573

CVE-2024-38575

CVE-2024-38579

CVE-2024-38581

CVE-2024-38596

CVE-2024-38598

CVE-2024-38615

CVE-2024-38619

CVE-2024-38627

CVE-2024-39276

CVE-2024-39471

CVE-2024-39472

CVE-2024-39476

CVE-2024-39487

CVE-2024-39499

CVE-2024-39501

CVE-2024-39502

CVE-2024-39506

CVE-2024-40901

CVE-2024-40904

CVE-2024-40911

CVE-2024-40912

CVE-2024-40927

CVE-2024-40929

CVE-2024-40931

CVE-2024-40941

CVE-2024-40954

CVE-2024-40958

CVE-2024-40959

CVE-2024-40960

CVE-2024-40972

CVE-2024-40974

CVE-2024-40977

CVE-2024-40978

CVE-2024-40988

CVE-2024-40989

CVE-2024-40995

CVE-2024-40997

CVE-2024-40998

CVE-2024-41005

CVE-2024-41007

CVE-2024-41008

CVE-2024-41012

CVE-2024-41013

CVE-2024-41014

CVE-2024-41023

CVE-2024-41035

CVE-2024-41038

CVE-2024-41039

CVE-2024-41040

CVE-2024-41041

CVE-2024-41044

CVE-2024-41055

CVE-2024-41056

CVE-2024-41060

CVE-2024-41064

CVE-2024-41065

CVE-2024-41071

CVE-2024-41076

CVE-2024-41090

CVE-2024-41091

CVE-2024-41097

CVE-2024-42084

CVE-2024-42090

CVE-2024-42094

CVE-2024-42096

CVE-2024-42114

CVE-2024-42124

CVE-2024-42131

CVE-2024-42152

CVE-2024-42154

CVE-2024-42225

CVE-2024-42226

CVE-2024-42228

CVE-2024-42237

CVE-2024-42238

CVE-2024-42240

CVE-2024-42246

CVE-2024-42265

CVE-2024-42322

CVE-2024-43830

CVE-2024-43871

CVE-2024-45338

CVE-2024-45339

CVE-2025-7531

CVE-2025-8056

CVE-2025-22868

Known Issues

Edit online
Warning: FYI
  • The default interval for the updation of the augmenter cache is 24 hours. If a policy is changed or added on vManage, it is necessary to update the cache forcefully to augment the flows correctly. Please run the PolicyParserAgent to update the cache forcefully.
    Note: Applicable to Viptela Collector only.
    • 
kubectl exec <COLLECTOR_POD_ID> -- ./collector-viptela -run PolicyParserAgent
    • To find the <COLLECTOR_POD_ID>, execute the following command. 
      
kubectl get pods
  • Data gaps might be seen on the graphs in SevOne NMS for indicators of the objects of type SD-WAN Device Health as they are being polled at different timestamps. For example, SevOne NMS shows the data for the following indicators related to SD-WAN Device Health object.
    • memory_utilization
    • disk_utilization
    • cpu_utilization

    When querying data for these indicators from vManage, if the data is missing for any of the indicators, then the data gap might be visible in SevOne NMS.

  • If you are using SevOne NMS version < 5.7.2.23 (without the NMS-75375 hotfix), you may experience an impact on the performance of the collector. At a same time, collectors will not support tunnels > 10k.
  • Widgets
    • When the alternate name is enabled in SevOne Data Insight, Network Topology Widget 2.8.x / 2.9 does not show any tunnels for SD-WAN 2.6 collectors.

Summary for complex table
Component/s Key Known Issues
SDWAN Cisco Catalyst S1NPM-77627 Viptela / Versa Collectors: When installing / upgrading the collector via GUI, you can proceed to the Upgrade SOA stage in the following scenarios:
  • Without selecting or updating the configuration file (in the Config stage).
  • Even if there are errors in the configuration file (in the Config stage).
SDWAN Solution, SDWAN Versa, SDWAN Cisco Catalyst S1NPM-100519 Platform: Depending on the scale of the environment, jaeger may quickly consume its allotted memory and in turn, restart. The maximum allotted memory can be adjusted when Jaeger is enabled.
SDWAN Solution, SDWAN Versa S1NPM-100816 Versa Collector: Tunnel objects will be pinned to their respective object groups either after 24 hours or according to the discovery schedule in SevOne NMS.
SDWAN Viptela S1NPM-101063 Viptela Collector: When updating the Installer Agent, the BFD_SESSIONS cache key gets updated based on received BFDSession data. The TunnelStatAgent parses the BFD Session data and updates the availability and transition indicators accordingly.

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.
SDWAN Cisco Catalyst S1NPM-109664 Viptela Collector: When the NEXT_HOP_IP field is not present in a flow, the following fields will be set to Unknown.
  • 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)
SDWAN Solution S1NPM-110248 Platform: In a multi-node, multi-vDirector setup, the Collector and Augmenter Evidence Framework is currently unable to collect evidence information or generate the .tar.gz file. However, the must-gather functionality continues to work as expected.
SDWAN Cisco Catalyst S1NPM-110676 Viptela Collector: Upgrading the collector from version 6.7.5 or above to Red Hat Enterprise Linux (RHEL) versions 6.8 or above fails with the error No package matching 'convert2rhel' found because the yum metadata still refers to the previously installed CentOS package.

Workaround: Run the following command and repeat the upgrade process. For more details, please refer to SD-WAN Viptela Collector Upgrade Process Guide.


sudo yum clean metadata
SDWAN Solution S1NPM-112181

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.
SDWAN VeloCloud S1NPM-112408 VeloCloud Collector: When upgrading VeloCloud from 7.0.0 or above to version 7.1.0, the VeloCloudSDWAN-DI-OOTB-Reports.tar file is still present in the /config/collectors/sdwan/velocloud/spk directory. This is an expected behavior.
SDWAN Viptela S1NPM-112547 / S1NPM-112715

Viptela Collector: After successful upgrade from version 7.1.0 to 7.1.x, the Viptela Summary Report in GUI displays a SevOne Data Insight migration error as shown below.

Workaround: Please click on Try to load anyway to proceed with loading the report without any conflicts.
SDWAN Viptela S1NPM-112731 Viptela Collector: When installing / upgrading the collector, running the command below to import the OOTB reports during post-check, may trigger an error. This is an expected behavior. 

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.
SDWAN Solution S1NPM-113717
Platform: The MetadataAgent fails to complete metadata updates for devices/objects because its runtime exceeds the default 1hour timeout limit. As a result, the metadata is not accurately reflected in the device/object with the following error. 
2024-06-24T16:49:37Z ERR agent run canceled error="context deadline exceeded" agent=MetadataAgent
Workaround:
  1. Locate and change the timeout for MetadataAgent from 1h to greater than or equal to 2h (but, less than 12h) in the config file, /opt/SevOne/chartconfs/<config-file>, as shown below. 
    
collectorConfig:

agent:

override:

MetadataAgent:

timeout: 2h
  2. Run the below command in the collector to apply the changes. 
    sevone-cli solutions reload
  3. Manually execute the below command in separate screen session, if needed , or wait for its next automatic cycle and then check the logs. 
    sevone-cli solutions run_agent --deployment_name solutions-sdwan-viptela --agent_name MetadataAgent --log_level info > met...
SDWAN Cisco Catalyst S1NPM-114791

Viptela Collector: Upgrading the collector from version 7.1.x to 7.2.x via the Graphical User Interface (GUI) may fail at the Deploy step with Helm error.

Workaround: Please refrain from using Graphical User Interface (GUI) process; perform the upgrade using the Command Line Interface (CLI).

Do not use the steps below until the Graphical User Interface (GUI) issue has been resolved.
SDWAN Cisco Catalyst S1NPM-116885

Versa / Viptela Collector: When installing the collector version 8.0 or when upgrading the collector from version 7.2 to 8.0, using the Graphical User Interface (GUI), the process fails at the Run Upgrade SOA step with the error Upgrade SOA: Failed.

Workaround: Please refrain from using Graphical User Interface (GUI) process; perform the upgrade using the Command Line Interface (CLI).

Please refer to SD-WAN Versa Collector Upgrade Process Guide or SD-WAN Viptela Collector Upgrade Process Guide for more details.
SDWAN Cisco Catalyst S1NPM-116965

Versa / Viptela Collector: When upgrading the Collector from version 7.1 to later version via SSU, the GUI workflow completes successfully without any errors and displays a success message. However, upon verification, the helm list command still show the previous Collector version.

Workaround: Please perform the upgrade using the Command Line Interface (CLI) instead of the Graphical User Interface (GUI)
SDWAN Cisco Catalyst S1NPM-117472

Device and object metadata may appear incomplete in SevOne NMS, with the Viptela / Versa Metadata Agent reporting the following message: 2024-06-24T16:49:37Z ERR agent run canceled error="context deadline exceeded"
SDWAN VeloCloud S1NPM-119203 In SevOne NMS 8.0 and later, when using the SD-WAN VeloCloud, if the startTime field in the device advance health response is null, the Advance Health Agent stops with an error as shown below, and does not continue processing the remaining devices. As a result, SD-WAN objects might not display for all devices. 
panic: runtime error: invalid memory address or nil pointer dereference

17 issues