Release Notes SevOne NMS 7.1.0

General

• Internal Kafka Client (for SDP): sarama 1.41.0
• NMS Kafka Server : 3.6.0-2.13.2.el8 (version must be < 4.x)

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

4.18.0-553.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.

9.9.0-1.el9

(libvirt-libs)

8.3.11-1.el8

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:
  • v7.1.0-build20241015-153317-3595bbec.tar.gz
  • v7.1.0-build20241015-153317-3595bbec.tar.gz.sha256.txt
• TAR / CHECKSUM Downgrade
  • v7.1.0-to-v7.0.1-build20241015-153317-3595bbec.tar.gz
  • v7.1.0-to-v7.0.1-build20241015-153317-3595bbec.tar.gz.sha256.txt
• ISO / CHECKSUM
  • nms-7.1.0-20241014-140649-1aa56c99.iso
  • nms-7.1.0-20241014-140649-1aa56c99.iso.sha256.txt
• AWS OVA - nms-7.1.0-20241015-153317-3595bbec-ami.ova
• OVA - nms-7.1.0-20241015-153317-3595bbec.ova
• QCOW2
  • nms-7.1.0-20241015-153317-3595bbec.qcow2
  • nms-7.1.0-20241015-153317-3595bbec.qcow2.sha256.txt
• VHD
  • nms-7.1.0-20241015-153317-3595bbec.vhd.gz
  • nms-7.1.0-20241015-153317-3595bbec.vhd.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)

Enable App Enrichment field from Cluster Manager > Cluster Settings tab > FlowFalcon subtab must be enabled to create an app alert.

Enable the required aggregated views to make use of them for the app alert policy.

NOTE: After upgrading to SevOne NMS 7.1, i.e., after removal of NAM functionality, NAM flow data cannot be collected. Historical NAM data and the ability to report on it, is unaffected after the upgrade.

• Observation Domain ID
• Template ID

Policy Browser: Default policies now support the following.

• SevOne Process: mysqld Availability
• SevOne Process: mysqld Instances

NOTE: NBAR data collection has been removed however, NBAR reporting on historical data after the upgrade is still supported.

After upgrading to SevOne NMS 7.1, i.e., after removal of NBAR functionality, user must enable NetFlow export on devices that have the NBAR functionality to continue to collect and report on the applications using NBAR and the Application ID field.

• Cluster Overview tab > added field Unknown Flow Devices to display flow devices that are not mapped with a device in Device Manager.
• Peers tab > added column Unknown Flow Device Count to display the number of flow devices in a peer that are not mapped with a device in Device Manager.

• = (equals to)
• + (plus)
• - (minus)
• @ (at)
• 0x09 (tab)
• 0x0D (carriage return)

• can create mapping of entity with metadata attribute with type Accepted Values.
• can delete mapping of entity with metadata attribute with type Accepted Values.
• can create mapping with Accepted Values attribute for all entities.

• Lambda
• Route 53 Health Checks
• Route 53 Resolvers

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.

  
  sudo podman exec -it nms-nms-nms /bin/bash
  

• 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]"

The reason is simply that the operation bails entirely if keys are failed to be obtained from even a single peer.

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

systemctl enable dex

Failed to enable unit: Unit /run/systemd/generator/dex.service is transient or generated.

• dex is needed if and only if you are using Single Sign-On (SSO). Otherwise, dex should not be running.
• samplicator is an optional service if you want to multiplex flow.

Workaround: Retry the downgrade process.

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

HOME=/

Workaround: Please refer to the note block titled WiFi solution in your environment? for details.