Release Notes SevOne NMS 7.0.0

• 6.8.x
• 7.0.x

General

• Internal Kafka Client (for SDP): sarama 1.41.0
• NMS Kafka Server : 3.6.0-2.13.2.el8

4.18.0-553.el8_10

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.7-1.el8

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

• signature-tools-<latest version>-build.<###>.tgz
• signature-tools-<latest version>-build.<###>.tgz.sha256.txt

For example,

• signature-tools-2.0.3-build.1.tgz
• signature-tools-2.0.3-build.1.tgz.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)

• SevOne-polld
• SevOne-highpolld
• SevOne-device-scand

• Administration > Flow Configuration
  • Protocols and Services renamed to Apps and Protocols
  • Service Mapping renamed to App Mapping
  • Service Profiles renamed to App Profiles
  • Service Categories renamed to App Categories
• Cluster Manager > Cluster Settings > FlowFalcon
  • Enable Service Enrichment renamed to Enable App Enrichment
• Flow alerts, service alert, renamed to app alert when the aggregated view selected is Top Applications with Protocol.
• FlowFalcon Resolution settings
  • Display Service Profile renamed to Display App Profile
  • Display Service Category renamed to Display App Category
• Webhook Definition Manager > Add/Edit
  • Flow policy variable $flowServiceProfileList renamed to $flowAppProfileList

• Add Peer renamed to Join Cluster - allows peer to join a cluster. Must enter peer name, cluster IP address, IP address of the peer joining the cluster, and token. Token can be copied from Integration tab.
• Remove Peer renamed to Leave Cluster.
• Cluster Manager: Integration tab > Allows user to get and copy the token required when a peer is joining a cluster.

• Cluster Settings tab > subtab Storage
• select a peer > Peer Settings tab > subtab Storage

• /SevOne.info has moved to /config/SevOne.info
• The following files have been removed from /etc/sevone/ (host).
  - gen-nms-secrets.sh
  - import_data_disk.sh
  - nms-collectors.yaml
  - nms-prometheus.yaml
  - nms-secrets-done
  - nms.yaml

• /etc/cron.d/ moved to /config/cron.d/
• /etc/logrotate.sevone.d/ moved to /config/logrotate.sevone.d/

sasl.gssapi.principal: sdp@EXAMPLE.COM
sasl.gssapi.realm: EXAMPLE.COM

• POST /api/v2/devicegroups/rules/apply
• POST /api/v2/devicegroups/{id}/rules/apply
• POST /api/v1/objectgroups/{id}/rules/apply
• POST /api/v2/objectgroups/{id}/rules/apply
• POST /api/v2/devices/{id}/rules/apply

• The NAT deployment scripts do not work; modifications to the peers' NAT setup must be executed manually.
• In SevOne NMS 7.0, peer IP address is checked against the local machine's interfaces. This can be limiting to some customers and flexibility available in SevOne NMS 6.x is required. In SevOne NMS 6.x, peer could be added using an IP address that did not match any of the peer's interface IP addresses as long as the IP address was able to successfully route to the intended machine.

• 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/ 
  

• SSH into your SevOne NMS appliance and log in as support.

  
  $ ssh support@<NMS appliance>
  

• Connect to the NMS container.

  
  $ podman --url=unix:/run/podman_sevone/podman.sock exec -it nms-nms-nms /bin/bash
  

• Once logged into the container, execute the following command and enter your desired PAS / DNC appliance model.

  
  $ SevOne-select -m all appliance <enter your desired PAS / DNC appliance model>
  

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