Release Notes SevOne SDN Collector 7.0.0 Monitoring Solution

Edit online

Below please find the Release Notes for SevOne SDN Collector 7.0.0 Monitoring Solution. 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.

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. Please use the latest version of your preferred (supported) browser.

Browser

Vendor	Family
Google	Chrome
Mozilla	Firefox

Important: Please use the latest browser version for Chrome and Firefox.

Compatibility Matrix

Edit online

SDN Version	SevOne NMS / NMS REST API		Widget Version	SOA Version	SevOne Data Insight	Collector Cisco ACI
	NMS	REST API
7.0.0	7.0.0 (T & S)	2.1.47	7.0.0	>= 7.0.0	7.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 7.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

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.

New Feature(s)

Edit online

SDN Plugin added. Improved performance and resource utilization.
SDN is packaged with SevOne NMS as a SDN plugin.

Important: When SevOne NMS is upgraded, SDN Plugin is upgraded automatically.

Resolved Issues

Edit online

Key	Release Notes
S1NPM-77589	Platform: Bytes BW now uses values from field bytesRate. BW Utilization is in between 0 - 100%. Formula used to compute the bandwidth calculation is: `Bandwidth = (BytesRate / (125 * 1000)) * 100 / operSpeed`
S1NPM-100893	Platform: The formula for calculating policy CAM Usage indicator has been updated to match the formula used by Cisco APIC policy_CAM = polUsageCum - polUsageBase.
S1NPM-100975	Platform: Alert policy trigger condition has been updated to use a non-zero value.
S1NPM-100990	Platform: SDN plugin added to SevOne NMS terraform.
S1NPM-101019	Platform: ACI VLAN Count is now updated to reflect the new calculation as it works for APIC version 6.
S1NPM-110395	Platform: Addressed CVE-2023-5363 and CVE-2023-45288.

6 issues

Known Issues

Edit online

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

Key	Known Issues
S1NPM-113805	Platform: The upgrade process from NMS version 6.8.x to NMS version 7.0.x is unable to migrate the SDN solution to plugin mode and results in a loss of functionality and data. Workaround: To resolve this issue, perform the following steps: Using ssh, login to SevOne NMS appliance as root. `$ ssh root@<SevOne NMS appliance IP address>` To create path: `$ mkdir /tmp/clean_migration` `$ cd /tmp/clean_migration` Download the following (latest) files 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 IBM SevOne Support for the latest files. In this case, you must download sevone_solutions_sdn_cleanMigration.tar.gz file and place it in /tmp/clean_migration directory. To retrieve the container id. `$ podman ps` Example: As shown in the output above, the container id is identified as 00bfd5a708e4. To copy the binary file in the sevone_solutions_sdn_cleanMigration.tar.gz to /tmp folder. `$ sudo podman cp sevone_solutions_sdn_cleanMigration.tar.gz <container_id>:/tmp` Example: `$ sudo podman cp sevone_solutions_sdn_cleanMigration.tar.gz 00bfd5a708e4:/tmp` To execute the commands in the SDN container. `$ podman exec -it <container_id> /bin/sh` Change directory to access /tmp folder. `$ cd /tmp/` Extract the binary file from .tar file. `$ tar -xvf sevone_solutions_sdn_cleanMigration.tar.gz` Execute the revert command. `$ ./cleanMigration revert` After executing the previous commands, please restart the container using the following command. `$ podman restart <container_id>` Note: Wait for at least 15 minutes after restarting the container to allow for the changes to take effect.
S1NPM-115679	Platform: If you are on SevOne NMS version 7.0.x and above, changes made to default.yaml file do not automatically reflect in site.yaml file when the configuration settings are modified; this is an expected behavior. Workaround: To apply the modifications made to default.yaml file, changes must be made manually to site.yaml file.
S1NPM-116155	Platform: After a fresh installation of SevOne NMS 7.0.0, the SDN FaultStreamingAgent fails to show the expected indicator values. The log confirms with the log message, Run agent start agent=FaultStreamingAgent, that the agent starts but does not complete. i.e., log does not have message, Run agent done. Additionally, the FaultInstallerAgent's SelfMon device is missing from Object Manager.

Platform: The upgrade process from NMS version 6.8.x to NMS version 7.0.x is unable to migrate the SDN solution to plugin mode and results in a loss of functionality and data.
Workaround:

To resolve this issue, perform the following steps:

Using ssh, login to SevOne NMS appliance as root.
```
$ ssh root@<SevOne NMS appliance IP address>
```

To create path:

$ mkdir /tmp/clean_migration

$ cd /tmp/clean_migration

Download the following (latest) files 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 IBM SevOne Support for the latest files.
In this case, you must download sevone_solutions_sdn_cleanMigration.tar.gz file and place it in /tmp/clean_migration directory.
To retrieve the container id.
```
$ podman ps
```
Example: As shown in the output above, the container id is identified as 00bfd5a708e4.

To copy the binary file in the sevone_solutions_sdn_cleanMigration.tar.gz to /tmp folder.

$ sudo podman cp sevone_solutions_sdn_cleanMigration.tar.gz <container_id>:/tmp

Example:

$ sudo podman cp sevone_solutions_sdn_cleanMigration.tar.gz  00bfd5a708e4:/tmp

To execute the commands in the SDN container.
```
$ podman exec -it <container_id> /bin/sh
```
Change directory to access /tmp folder.
```
$ cd /tmp/
```

Extract the binary file from .tar file.

$ tar -xvf sevone_solutions_sdn_cleanMigration.tar.gz

Execute the revert command.
```
$ ./cleanMigration revert
```
After executing the previous commands, please restart the container using the following command.
```
$ podman restart <container_id>
```
Note: Wait for at least 15 minutes after restarting the container to allow for the changes to take effect.

S1NPM-115679

Platform: If you are on SevOne NMS version 7.0.x and above, changes made to default.yaml file do not automatically reflect in site.yaml file when the configuration settings are modified; this is an expected behavior.

Workaround: To apply the modifications made to default.yaml file, changes must be made manually to site.yaml file.

S1NPM-116155 Platform: After a fresh installation of SevOne NMS 7.0.0, the SDN FaultStreamingAgent fails to show the expected indicator values. The log confirms with the log message, Run agent start agent=FaultStreamingAgent, that the agent starts but does not complete. i.e., log does not have message, Run agent done. Additionally, the FaultInstallerAgent's SelfMon device is missing from Object Manager.

3 issues