Release Notes SevOne SDN Collector 7.1.0 Monitoring Solution

Edit online

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

Resources & Requirements

Edit online
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.

Signature Tools
  • signature-tools-v2.0.3-build.1.tgz
  • signature-tools-v2.0.3-build.1.tgz .sha256.txt
SDN Widgets
  • cisco-aci-sdi-widgets-v7.1.0-build.7.tar.gz
  • cisco-aci-sdi-widgets-v7.1.0-build.7.tar.gz.sha256.txt

SDN is packaged with SevOne NMS as a SDN plugin.

Compatibility Matrix

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

Resolved Issues

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.
Key Release Notes
S1NPM-110884 Platform: ACI VLAN Count is now updated to reflect the new calculation as it works for APIC version 6.
S1NPM-111257 Addressed CVE-2024-37890 and CWE-400.
S1NPM-116155 Platform: After a fresh installation of SevOne NMS 7.0.0, the FaultStreamingAgentis now operating as expected, this is confirmed by the presence of both Run agent start agent=FaultStreamingAgent and Run agent done in the logs. Also, the FaultInstallerAgent’s SelfMon device has been restored in Object Manager, with all the functionality validated. This confirms that all the expected indicator values are now correctly displayed in SevOne NMS.

3 issues

Known Issues

Edit online

This section lists issues that SevOne is aware of in SevOne SDN Collector 7.1.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-113526 Platform: Upgrading from version 6.0.x to version 7.0.x without prior SDN device configuration in 6.0.x environment may result in the absence of TopN OOTB reports for some users.

Workaround: Please refer to the Troubleshooting section in SevOne SDN Collector Advanced Configuration & Troubleshooting Guide for details.
S1NPM-113805

Platform: When you upgrade from NMS version 6.8.x to version 7.0.x or 7.1.x, the SDN solution is not migrated to plugin mode, which results in loss of functionality and data.

During the upgrade, the system attempts to automatically migrate the SDN solution to plugin mode. In some cases, this migration might not complete, which can result in partial configuration or missing SDN data.

Use the following steps to determine when to run the migration script, how to identify migration failures, and how to confirm that the migration is complete.
When to Run the Migration Script
Run the SDN migration script only under the following conditions.
  1. Wait until the NMS upgrade process is complete and all services are running.
  2. Allow at least 15 minutes after the upgrade for background initialization tasks to finish.
  3. Review the system logs. Run the script only if log messages indicate SDN plugin migration failures.
    Important: Do not run the migration script while services are still starting. Doing so can result in incomplete migration.
How do you identify when migration has failed
Check the SDN logs and SDN plugin container logs for any of the following messages.
  • Error sending HTTP request to enable SDN plugin
  • Unable to marshal settings for device
  • Error preparing SQL statement
  • Error inserting rows in SDN device info table, or finding rows affected
These messages indicate that device records exist in the database, but the SDN plugin toggle did not complete during the upgrade. In this case, you must run the migration script to restore the SDN state.
How do you confirm that the migration is complete
After waiting 15 minutes post-upgrade, verify that the SDN migration is complete.
  1. Confirm that the SDN plugin is collecting data.
  2. Confirm that the SDN plugin is pushing statistics to the devices.
Workaround: To resolve this issue, perform the following steps:
  1. Using ssh, login to SevOne NMS appliance as root. 
    ssh root@<SevOne NMS appliance IP address>
  2. To create path: 
    mkdir /tmp/clean_migration
    cd /tmp/clean_migration
  3. 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.

  4. To retrieve the container id. 
    podman ps

    Example:

    00bfd5a708e4 na.artifactory.swg-devops.com/hyc-sevone-team-docker-staging-docker-local/solutions-central/sdn/plugin:7.1.0-build.12
    As shown in the output above, the container id is identified as 00bfd5a708e4.
  5. 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
  6. To execute the commands in the SDN container. 
    podman exec -it <container_ID> /bin/sh
  7. Change directory to access /tmp folder. 
    cd /tmp/
  8. Extract the binary file from .tar file. 
    tar -xvf sevone_solutions_sdn_cleanMigration.tar.gz
  9. Execute the revert command. 
    ./cleanMigration revert
  10. 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-114402 Platform: After upgrading SevOne NMS 7.0.0 to SevOne NMS 7.1.x and above, 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.
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-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.

5 issues