Release Notes SevOne SDN Collector 8.0.0 Monitoring Solution

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

Resources & Requirements

SevOne SDN Collector is packaged with SevOne NMS as SDN plugin.
Note: The Signature Tool details for SevOne SDN Collector are the same as those for SevOne NMS resources. Please refer to Third-Party Packages / Resources Required in Release Notes SevOne NMS 8.0.0.
All SDN Widgets, that is SD-DC (Software Designed Data Center) widgets are available from SevOne Data Insight.
Note: The Signature Tool details for SDN Widgets are the same as those for SevOne Data Insight resources. Please refer to Third-Party Packages / Resources Required in Release Notes SevOne Data Insight 8.0.0.

Compatibility Matrix

Note:
  • T – Tested & S – Supported
SevOne NMS REST API Service-Oriented Architecture (SOA) SevOne Data Insight Collector Cisco ACI
8.0.0 (T & S) 2.1.47 >= 8.0.0 8.0 (T & S)

APIC- 6.0 (T & S)

APIC - 5.x (T & S)

ACI MSO - v3.x (T & S)

SevOne Data Insight

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

Collector Cisco ACI

  • APIC 5.x

  • ACI Multi-Site Orchestrator (MSO) v3.x

  • An administrator-level account in the APIC and MSM. This is necessary in order for the SDN ACI Collector to communicate with the APIC REST API.

  • User name and password for the administrator-level account.

  • IP address of the APIC / MSM.

Any Linux Docker environment (running Linux containers) that can reach the target SevOne NMS and system(s) that can be polled by the network is acceptable.
SevOne NMS failover scenarios can be handled only when the collector is deployed on SevOne NMS appliance.

Recommendation

If the SEVONE_API_PASSWORD changes, the collection will be stopped unless the settings.env and multi_site_config.json files are updated with the new password. The new configure option in the launch script provides the user with a command line interface to do the same.

Important: While using the SDN Collector 8.0.0 Monitoring Solution,
  • Do not rename devices or objects created by the Solution. This can potentially break data collection. Please use alternative name fields if a custom name is required.
  • Do not enable automatic DNS name resolution in SevOne NMS cluster. If enabled, it allows NMS to rename the devices based on the DNS record and break the data collection.

Useful Guides

From IBM's Documentation Portal (https://www.ibm.com/docs/en/sevone-npm) , please refer to SDN / SevOne Data Insight guides for this release for details.

Note: TCAM Utilization Summary

Formula: TCAM Utilization (%) = ( (polUsageCum − polUsageBase) / polUsageCapCum ) × 100

What it means: TCAM (Ternary Content Addressable Memory) tracks how much policy space is being used on a leaf switch. It helps ensure the switch does not run out of space for policies.

Where the numbers come from:
  • polUsageCum: Current number of policies used
  • polUsageBase: Baseline policy count
  • polUsageCapCum: Max policy capacity

Resolved Issues

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.
Key Resolved Issues
S1NPM-113801 Platform: In certificate-based authentication, the destination peer must have the appropriate certificate to resume data collection when a device is moved from a source peer.
S1NPM-114402 Platform: After upgrading SevOne NMS 7.0.0 to SevOne NMS 7.1.x and above, the FaultStreamingAgent is now operating as expected, this is confirmed by the presence of both Run agent start agent=FaultStreamingAgent and Run agent done in the logs. The indicator values are now correctly displayed in SevOne NMS. This issue has been resolved.
S1NPM-114838 Addressed CVE-2025-22868.
S1NPM-115498 Platform: The logrotate configuration now adheres to the following behavior.
  • Log files are truncated, not deleted, after rotation.
  • A compressed version of the rotated log is created.
  • A maximum of 5 rotated files are retained (rotate 5).
  • No rotation occurs if the log file is empty (notifempty).
  • If the log file is missing, no error is raised (missingok).
  • Logs are rotated when they exceed the specified size or maxsize thresholds.
  • Rotated files that are older than the defined maxage are automatically deleted.
S1NPM-115679 Platform: In SevOne NMS versions 7.0.x, 7.1.x, and 7.2.x changes made to default.yaml are now applied to site.yaml automatically. By migrating configuration to advance-site.yaml, now ensures automatic update of changes without manual intervention. This issue has been resolved.

5 issues

Known Issues

This section lists issues that SevOne is aware of in SevOne SDN Collector 8.0.0 Monitoring Solution. Most of these issues were discovered during quality assurance testing and are published here to provide you with information that may be relevant when you plan your update. This list does not include feature requests or low impact issues that do not affect functionality. If you have questions, comments, or concerns, please contact us.

  • ACI Switch Capacity widget has a few pre-set max values. For example, rather than using the APIC API max values, VRF's max value is 800 (400 for NorthStar model) and EPG's max value is 3960.
Key Known Issues

S1NPM-116660

Platform: Alerts are currently generated even when the associated device is not found in the SevOne NMS database. This behavior can result in unnecessary alert noise, particularly when a device has been intentionally removed or has not yet completed provisioning.

S1NPM-116910

Platform: Device type name fails to update following an upgrade.

S1NPM-116925

Platform: After adding SDN device to SevOne NMS version 8.0 and configuring the data source in SevOne Data Insight, the ACI SDN Capacity widget in SevOne Data Insight displays incorrect data, showing 0% values for Hypervisor, Virtual Machines, and Virtualization.

S1NPM-116981

Platform: After adding an SDN device to SevOne NMS version 8.0.0 and configuring the data source in SevOne Data Insight, the Cisco ACI Fabric report does not display any data when the Mapping or Topology tab is selected.

S1NPM-116998

Platform: After adding an SDN device to SevOne NMS version 8.0.0 and configuring the data source in SevOne Data Insight, the Create Report page in SevOne Data Insight does not display data when the SDN Mapping widget and SDN Logical Topology widget are added.

S1NPM-117039

Platform: In a fresh installation of SevOne NMS version 7.2.0, the Device Type Membership tab does not display device-related details for both the SC CISCO ACI HYPERVISOR and SC CISCO ACI VM device types. Furthermore, after upgrading SevOne NMS from version 7.2.0 to 8.0.0, the Device Type Membership tab does not display device-related details for the SC CISCO ACI VM device type.

S1NPM-117040

Platform: After upgrading SevOne NMS from version 7.2 to 8.0.0, some devices are not displayed on the Device Types page.

S1NPM-117089

Platform: After adding SDN device to SevOne NMS version 8.0 and configuring the data source in SevOne Data Insight, the Cisco ACI Fabric Virtualization OOTB report does not display data in Data Insight.

S1NPM-117098

Platform: After adding an SDN device to SevOne NMS version 8.0 and configuring the data source in SevOne Data Insight, data such as Ingress, Egress, and other traffic metrics are not displayed in some ACI traffic related widgets within the SDN OOTB reports.

S1NPM-117131

Platform: The message currently displayed under the Comparison Operation section of the trigger condition for the SDN policy siteN::SDN::SelfmonAvailability incorrectly shows a percentage. However, it should reflect the elapsed time, in seconds, since the most recent data point.

Example, the correct message should read as 7200 seconds since newest data point.

S1NPM-117654

The SDN Collector generates warning messages for non-SDN devices that are not present in the SDN cache. This issue affects logging only and does not impact device discovery, data collection, or device updates.This is not an expected behavior.

S1NPM-119243

Platform: WebSocket subscription failures prevent the Fault Streaming Agent from receiving Cisco ACI fault data

The Fault Streaming Agent is unable to establish WebSocket subscriptions with the APIC (Cisco ACI controller), which prevents the agent from receiving fault information.

S1NPM-121365

A defect in the Cisco ACI SDN collector may cause runtime panics during hypervisor and VM topology discovery when APIC returns malformed or unexpected tDn/pathDn values. Although the APIC APIs return successful 200 OK responses, the collector may crash while processing the topology data. This is not an expected behavior.

13 issues