NVIDIA NetQ 5.1 Release Notes

Download 5.1 Release Notes xls    Download all 5.1 release notes as .xls

5.1.0 Release Notes

Open Issues in 5.1.0

Issue IDDescriptionAffectsFixed
4977619NetQ might fail to load in high-availability (HA) scale deployments when ECMP is enabled. To work around this issue, disable ECMP ingestion by updating the Kafka connector configuration:
  1. Create a backup of the current configuration:
    kubectl get kafkaconnector cassandra-sink-group-1 -n netq-infra -o yaml > /tmp/cassandra-sink-group-1.backup.yaml
  2. Capture the current Kafka connector values:
    OLD_KCQL=$(kubectl get kafkaconnector cassandra-sink-group-1 -n netq-infra -o jsonpath='{.spec.config.connect.cassandra.kcql}')
    OLD_TOPICS=$(kubectl get kafkaconnector cassandra-sink-group-1 -n netq-infra -o jsonpath='{.spec.config.topics}')
  3. Remove ECMP-related entries from KCQL and topics:
    NEW_KCQL=$(echo “$OLD_KCQL” | tr ‘;’ ‘\n’ | grep -v -E ‘INTO ecmp_info SELECT|INTO ecmp_info_aggregate SELECT|INTO ecmp_info_group_aggregate SELECT’ | paste -sd ‘;’ -)
    NEW_TOPICS=$(echo “$OLD_TOPICS” | tr ‘,’ ‘\n’ | grep -v -E ‘^netq_obj_ecmp_info$|^netq_obj_ecmp_info_aggregate$|^netq_obj_ecmp_info_group_aggregate$’ | paste -sd ‘,’ -)
  4. Verify the changes before applying them:
    echo “=== KCQL ECMP entries remaining (should only show ecmp_hash + arEcmpInfo) ==="
    echo “$NEW_KCQL” | tr ‘;’ ‘\n’ | grep -i ecmpecho “=== TOPICS ECMP entries remaining (should only show netq_obj_ecmp_hash) ==="
    echo “$NEW_TOPICS” | tr ‘,’ ‘\n’ | grep -i ecmp
    echo “Old KCQL: $(echo “$OLD_KCQL” | tr ‘;’ ‘\n’ | wc -l) / New: $(echo “$NEW_KCQL” | tr ‘;’ ‘\n’ | wc -l) (-3)"
    echo “Old TOPICS: $(echo “$OLD_TOPICS” | tr ‘,’ ‘\n’ | wc -l) / New: $(echo “$NEW_TOPICS” | tr ‘,’ ‘\n’ | wc -l) (-3)"
  5. Apply the updated configuration:
    kubectl patch kafkaconnector cassandra-sink-group-1 -n netq-infra –type=merge -p “$(jq -n –arg k “$NEW_KCQL” –arg t “$NEW_TOPICS” ‘{spec:{config:{“connect.cassandra.kcql”:$k,“topics”:$t}}}')"
To revert the changes, restore the backup with kubectl apply -f /tmp/cassandra-sink-group-1.backup.yaml
5.1.0
4977342The NetQ UI might not display a complete list of interfaces. To work around this issue, restart the NetQ agent or upgrade to the latest NetQ version.5.1.0
4964170When you create a partition, the operation might fail with a BAD_PARAM error. To work around this issue, retry the operation until it is successful.5.1.0
4897897The NetQ NVLink API might fail to return a 400 error response when unsupported parameters are included in the API request.5.1.0
4894672NVOS upgrades on switches might fail if the image filename contains spaces or special characters.5.1.0
4890084The NetQ CLI might not delete threshold-crossing alerts configured for ACL resources. To work around this issue, use the UI to delete the alerts.5.1.0
4876932The NMX controller service might intermittently fail to switch to an alternate out-of-band (OOB) port when the primary registration port becomes unavailable. As a result, partition management operations might not function correctly on the secondary OOB port if the registered management port goes down.5.1.0
4867933Threshold-crossing events created before version 5.1.0 may not display event values correctly after you upgrade NetQ.5.1.0
4854041When you upgrade a NetQ for NVLink and Ethernet deployment using the data backup and restoration workflow, NetQ does not preserve NVLink data.5.1.0
4839716You cannot perform lifecycle management operations immediately after backing up an HA scale cluster deployment. To work around this issue, wait several hours before initiating LCM operations.5.1.0
4838526NMX controller and telemetry services might display a DOWN status if the primary out-of-band (OOB) management port is unavailable.5.1.0
4830357When you try to filter images in the NetQ UI based on image type, NetQ might ignore the filter.5.1.0
4794266Power sensor (PSU) events might show inconsistent sensor names. Additionally, NetQ might not generate PSU events reliably.5.1.0
4784336The NetQ for NVLink deployment option is not supported in air-gapped environments.5.0.0-5.1.0
4780773The NetQ for NVLink Swagger UI might incorrectly display 500 status placeholder text in example responses.5.0.0-5.1.0
4687477When you run a validation against a group of devices with specific labels, NetQ ignores any pre-configured filters.5.0.0-5.1.0
4681581The netq bootstrap reset purge-db command might take up to 60 minutes to complete on Base Command Manager scale deployments.5.0.0-5.1.0
4399074When connecting a switch to NMX-T or NMX-C through the service registration workflow, use either the IP address or the hostname. Using both creates duplicate registrations, and the operation does not fail as expected.5.0.0-5.1.0
4100882When you attempt to export a file that is larger than 200MB, your browser might crash or otherwise prevent you from exporting the file. To work around this issue, use filters in the UI to decrease the size of the dataset that you intend to export.4.12.0-4.15.1, 5.0.0-5.1.0

Fixed Issues in 5.1.0

Issue IDDescriptionAffects
4786996To use lifecycle management in NMC or BCM environments, you must edit the master node IP address in the configuration manager to match the cluster’s head node IP address. Use the kubectl edit cm -n netq-eth netq-master-node-ip command to edit the configuration. In the configuration file, change the data/master_node field to the cluster’s head node IP address.5.0.0
4693161In cluster and scale cluster deployments, the snapshot comparison feature may time out when comparing MAC addresses.5.0.0
4689932Node reservation for NetQ is not supported in shared multi-node clusters. To work around this issue, deploy NetQ in a dedicated single-node or three-node cluster first, and then scale the deployment by adding nodes for other applications.5.0.0
4687241The activity log in the UI might display multiple entries with “unknown” or “anonymous” usernames.5.0.0
4683830The Cable Validation Tool might fail to load in the NetQ UI. To work around this issue, log out of NetQ and then log back in.5.0.0
4668341When you a create an LDAP server configuration, the NetQ UI incorrectly allows you to modify the default server ports. Only the standard ports (389 for insecure and 636 for secure) are permitted.5.0.0
4667571NetQ might return inconsistent results when queries use the regular expression wildcard.5.0.0
4637749When the master node is down, the netq show status command might report an incorrect status.5.0.0
4573427The link health view utilization chart might display incorrect values for the top 5 links when multiple links share the same value.5.0.0
4527529When there is a high volume of concurrent API requests to NetQ, some requests may fail.4.15.0-5.0.0