| 4977619 |
NetQ 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:- 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 - 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}') - 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 ‘,’ -) - 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)"
- 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 |
|
| 4867933 |
Threshold-crossing events created before version 5.1.0 may not display event values correctly after you upgrade NetQ. |
5.1.0 |
|
| 4854041 |
When 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 |
|
| 4839716 |
You 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 |
|
| 4794266 |
Power sensor (PSU) events might show inconsistent sensor names. Additionally, NetQ might not generate PSU events reliably. |
5.1.0 |
|
| 4784336 |
The NetQ for NVLink deployment option is not supported in air-gapped environments. |
5.0.0-5.1.0 |
|
| 4687477 |
When you run a validation against a group of devices with specific labels, NetQ ignores any pre-configured filters. |
5.0.0-5.1.0 |
|
| 4681581 |
The 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 |
|
| 4399074 |
When 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 |
|
| 4100882 |
When 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 |
|
Download all 5.1 release notes as .xls