Release Notes SevOne NMS 8.0.0

General

• Internal Kafka Client (for SDP): sarama 1.45.0
• NMS Kafka Server : 3.9.1 (version must be < 4.x)

Upstream package used for Kafka, provided by RedHat: OpenJDK v21.0.7

4.18.0-553.60.1.el8_10.x86_64

NOTE: The kernel will automatically get installed as part of the upgrade and will be loaded after the reboot of the appliance.

8.3.23

NOTE: To consume PHP 8, please contact Expert Labs if assistance is needed.

• signature-tools-2.0.3-build.1.tgz
• signature-tools-2.0.3-build.1.tgz.sha256.txt

• TAR / CHECKSUM Upgrade:
  • v8.0.0-build20250711-142539-90635362.tar.gz
  • v8.0.0-build20250711-142539-90635362.tar.gz.sha256.txt
• TAR / CHECKSUM Downgrade
  • v8.0.0-to-v7.2.0-build20250711-142539-90635362.tar.gz
  • v8.0.0-to-v7.2.0-build20250711-142539-90635362.tar.gz.sha256.txt
• ISO / CHECKSUM
  • nms-8.0.0-20250711-142539-90635362.iso.iso
  • nms-8.0.0-20250711-142539-90635362.iso.sha256.txt
• AWS OVA - nms-8.0.0-20250711-142539-90635362-ami.ova
• OVA - nms-8.0.0-20250711-142539-90635362.ova
• QCOW2
  • nms-8.0.0-20250711-142539-90635362.qcow2
  • nms-8.0.0-20250711-142539-90635362.qcow2.sha256.txt
• VHD
  • nms-8.0.0-20250711-142539-90635362.vhd.gz
  • nms-8.0.0-20250711-142539-90635362.vhd.gz.gz.sha256.txt

• Intel-VT or AMD-V CPU extensions
• ESXi 5.0 and later (VM version 8) - minimum requirement
• Tested with vSphere Client version 7.0 (ESXi 7.0 and later; VM version 8)

Use a specific name when connecting to mail servers or set the system to autodetect the FQDN of the system sending the mail and use that as the host name.

Run the following query on the Cluster Master.

mysql (config)> UPDATE net.settings SET value = '<enter your.custom.hostname>' WHERE setting = 'mail_client_hostname';
 

By default the setting will be localhost.localdomain to match existing behavior. If the setting is set to an empty value, the OS hostname will be used instead.

mysql (config)> UPDATE net.settings SET value = '' WHERE setting = 'mail_client_hostname';
 

systemctl enable samplicator
systemctl start samplicator
 

SDP: Support for SASL / OAUTHBEARER authentication added. Please refer to FAQ How to set up Kafka using SASL OAUTHBEARER authentication? for details.

NOTE: The steps in this FAQ apply only when you are running SDP on Microsoft Azure and authenticating with an OAUTHBEARER token.

REST API: The following endpoints added for Support > MustGather.

• DELETE / GET /api/v3/support/mustgather
• POST /api/v3/support/mustgather/create
• PATCH /api/v3/support/mustgather/{requestId}/cancel
• GET /api/v3/support/mustgather/{requestId}/result
• GET /api/v3/support/mustgather/{requestId}/status

REST API: Endpoint POST /api/v3/auth/client/token added to fetch tokens for the following static clients.

• aruba-collector
• aws-collector
• azure-collector
• core-nms
• gcp-collector
• gnmi-collector
• sdn-plugin
• sdwan-client
• selfmon
• velocloud-client
• wifi-collector

Platform: For certificates that are expiring, the following rules are followed.

• MySQL, Kafka, and Otel certificates are checked regularly. An alert is sent to the admin if the certificate is expiring in 30 days.
• MySQL and Kafka certificated are regenerated if expiring in 1 day.
• Otel certificate is regenerated with every upgrade.

Flows: To prevent unintended flow matches, user must avoid configuring overlapping App Profiles. The more fields defined, the higher the precedence. The hierarchy is as follows: IP + PORT > IP only > PORT only

By aligning the configuration's hierarchy, accurate and predictable flow classification can be ensured.

• CVE-2018-22699
• CVE-2019-20916
• CVE-2022-37967
• CVE-2023-22102
• CVE-2023-43804
• CVE-2023-50782

• CVE-2024-3596
• CVE-2024-6345
• CVE-2024-10963
• CVE-2024-12797
• CVE-2024-26130
• CVE-2024-36039

• CVE-2024-56171
• CVE-2025-22868
• CVE-2025-24928
• CVE-2025-27152
• CVE-2025-30204

Workaround: The following steps must be executed manually post-upgrade.

• You must be in the NMS container. To enter the NMS container, execute the following command.

  
  nms
   

• Execute the following command to identify the log rotations and cron.d files for your adapter.

  
  echo "adapterName,cronDfile,logDir,logRotateFile";\
  find /opt/sevone-xstats/ -type f -name install.config.json | \
  grep -v backup | \
  while read INSTALLCONFIGFILE;do adapterName=$(cat ${INSTALLCONFIGFILE} | \
  jq -r '.adapterName');LOGDIR=$(cat ${INSTALLCONFIGFILE} | jq -r '.logDir');LOGROTATEDIR=$(cat ${INSTALLCONFIGFILE} | \
  jq -r '.components.Logrotate.logrotateDir');LOGROTATEFILE=$(cat ${INSTALLCONFIGFILE} | \
  jq -r '.components.Logrotate.logrotateFile');CRONDIR=$(cat ${INSTALLCONFIGFILE} | \
  jq -r '.components.Cron.cronDir');CRONDFILE=$(cat ${INSTALLCONFIGFILE} | \
  jq -r '.components.Cron.cronFile');echo "${adapterName},${CRONDIR}/$(eval echo \"$CRONDFILE\"),$(eval echo \"$LOGDIR\"),${LOGROTATEDIR}/$(eval echo \"$LOGROTATEFILE\")";done
   

  where the output is,

  
  adapterName,cronDfile,logDir,logRotate
  GenericCSVTransform,/etc/cron.d/xstats-GenericCSVTransform,/var/log/xstats/GenericCSVTransform,/etc/logrotate.sevone.d/adapter-xstats-GenericCSVTransform
  AccedianCSVTransform,/etc/cron.d/xstats-AccedianCSVTransform,/var/log/xstats/AccedianCSVTransform,/etc/logrotate.sevone.d/xstats-AccedianCSVTransform
  AccedianNidXmlTransform,/etc/cron.d/xstats-AccedianNidXmlTransform,/var/log/xstats/AccedianNidXmlTransform,/etc/logrotate.sevone.d/xstats-AccedianNidXmlTransform
   

• Move the following files to the correct folder.

  
  mv /etc/cron.d/<your xStats adapter name> /config/cron.d/<your xStats adapter name>
  
  mv /etc/logrotate.sevone.d/adapter-xstats* /config/logrotate.sevone.d/
  
  mv /etc/logrotate.sevone.d/xstats* /config/logrotate.sevone.d/ 
   

2024-09-23T21:38:49+00:00 SevOne soa: {"error":"rpc error: code = FailedPrecondition desc = problem encountered executing command",\
"fatal":false,"level":"warning","method":"AddNewNodeStage2","module":"clusterOrchestrator",\
"msg":"failed to fix ssh keys, user should manually fix them from the cluster leader","time":"2024-09-23T21:38:49Z"}
 

SevOne-fix-ssh-keys

time=2024-09-23T22:37:30.503Z level=ERROR msg="error getting public keys" error=<nil> failureIds="[PeerId: 2 | Peer State: Active]"
 

Workaround: Run SevOne-fix-ssh-keys manually on the Cluster Master / Cluster Leader after peering.

PHPRC=/config/php.d/php-cli.ini

HOME=/
 

Workaround: From the SevOne NMS command line interface, restart the WiFi collector container.

podman restart  nms-collections-wifi-collector
                

Platform: After upgrading SevOne NMS, the following fields are missing from the cluster leader. However, the fields contain the values in its peer(s).

Actual behavior:

AUDIT_LOGS_RETENTION_PERIOD=
DEL_AUDIT_LOGS=
DEL_OBJECTS=False

Expected behavior:

AUDIT_LOGS_RETENTION_PERIOD=8760
DEL_AUDIT_LOGS=True
DEL_OBJECTS=True

Observed behavior post-upgrade

AUDIT_LOGS_RETENTION_PERIOD=
DEL_AUDIT_LOGS=
 

Expected behavior

AUDIT_LOGS_RETENTION_PERIOD=8760
DEL_AUDIT_LOGS=True