Release Notes SevOne SDN Collector 8.2.0 Monitoring Solution

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.2.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 Resources & Other Requirements in Release Notes SevOne Data Insight 8.2.0 .

Compatibility Matrix

Edit online

Note:

T & S - Tested & Supported

Table 1. Component Version Compatibility Matrix
SevOne NMS	REST API	Service-Oriented Architecture (SOA)	SevOne Data Insight	Cisco APIC Version
8.2.0(T & S)	2.1.47	>=8.2.0	8.2(T & S)	APIC - 6.0 (T & S) APIC - 5.x (T & S) ACI MSO - v3.x (T & S)

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

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

Edit online

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

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.

Useful Guides

Edit online

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

Known Issues

Edit online

This section lists issues that SevOne is aware of in SevOne SDN Collector 8.2.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.

Table 2. Known Issues in Release 8.2.0
Key	Known Issues
S1NPM-116910	Platform: Device type name fails to update following an upgrade.
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-117089	Platform: After adding SDN device to SevOne NMS version 8.0.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.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-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-118986	SDN log rotation may not trigger as configured, resulting in log files continuing to grow instead of rotating by time or size. This can lead to increased disk usage and less streamlined log management.
S1NPM-120944	Some Cisco ACI Object Types (e.g., Aggregated, Controller, L3 Management, Physical, and Port Channel Interfaces) may be not appear in the Object Manager page. Additionally, several Object Groups (including APIC Interface, Physical Interface, Port Channel, and multiple Site2-APIC1 groups) may appear without any members. This is not an expected behavior.
S1NPM-120945	Cisco ACI Top N reports in the SevOne NMS may display empty results despite valid data being available. This affects multiple categories, including tenant, AP, EPG, BD, PN, HV, VM, and interface metrics and this is not expected behavior.
S1NPM-120977	Device discovery may remain incomplete for some devices up to 48 hours after creating an SDN device. In such cases, associated objects are not created and the Objects column shows New.This issue may be caused by delays in background processing or intermittent communication failures. This is not an expected behavior.
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.

10 issues