4786996
|
To 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 |
4693161
|
In cluster and scale cluster deployments, the snapshot comparison feature may time out when comparing MAC addresses. |
5.0.0 |
4689932
|
Node 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 |
4687241
|
The activity log in the UI might display multiple entries with “unknown” or “anonymous” usernames. |
5.0.0 |
4683830
|
The 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 |
4668341
|
When 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 |
4667571
|
NetQ might return inconsistent results when queries use the regular expression wildcard. |
5.0.0 |
4637749
|
When the master node is down, the netq show status command might report an incorrect status. |
5.0.0 |
4573427
|
The link health view utilization chart might display incorrect values for the top 5 links when multiple links share the same value. |
5.0.0 |
4527529
|
When there is a high volume of concurrent API requests to NetQ, some requests may fail. |
4.15.0-5.0.0 |
Download all 5.1 release notes as .xls