4181296
| NetQ might become unresponsive when someone with a non-admin (user) role attempts to create or clone workbenches, add cards to a workbench, create validations, or run a flow analysis. | 4.11.0-4.12.0 | |
4161342
| When NetQ runs a scheduled topology validation, the UI might display the message “No data available” in the medium-sized results card. To view the results from the validation, expand the card to its largest size. | 4.12.0 | |
4160704
| In large-scale environments, NetQ might take up to a minute to display the results of the BGP validation in the UI and the netq check bgp command using the CLI. | 4.12.0 | |
4157785
| When you add a new switch to the NetQ inventory, the NetQ UI might not display interface statistics or interface validation data for the new switch for up to one hour
To work around this issue, adjust the poll period to 60 seconds on the new switch with the netq config add agent command service-key ports poll-period 60 command. When interface data is displayed in the NetQ UI, change it back to the default value of 3600 with the netq config add agent command service-key ports poll-period 3600 command
| 4.12.0 | |
4155900
| When a fan’s sensor state is “high”, NetQ correctly displays the count information on the sensor health card. When the card is expanded to the detailed view, fans with a “high” sensor state will not be included among the fans with problematic states. | 4.12.0 | |
4134341
| If you continuously toggle the option to send all notifications to a default channel, NetQ might ignore the request. To work around this issue, refresh the page or create a new channel and set it as the default channel. | 4.12.0 | |
4131550
| When you run a topology validation, the full-screen topology validation view might not display the latest results. To work around this issue, refresh the page. | 4.12.0 | |
3985598
| When you configure multiple threshold-crossing events for the same TCA event ID on the same device, NetQ will only display one TCA event for each hostname per TCA event ID, even if both thresholds are crossed or status events are triggered. | 4.11.0-4.12.0 | |
3800434
| When you upgrade NetQ from a version prior to 4.9.0, What Just Happened data that was collected before the upgrade is no longer present. | 4.9.0-4.12.0 | |
3772274
| After you upgrade NetQ, data from snapshots taken prior to the NetQ upgrade will contain unreliable data and should not be compared to any snapshots taken after the upgrade. In cluster deployments, snapshots from prior NetQ versions will not be visible in the UI. | 4.9.0-4.12.0 | |
3771279
| When an interface speed is changed in the network, NetQ might not reflect the new speed until up to an hour after the change. | 4.11.0-4.12.0 | |
3769936
| When there is a NetQ interface validation failure for admin state mismatch, the validation failure might clear unexpectedly while one side of the link is still administratively down. | 4.9.0-4.12.0 | |
3752422
| When you run a NetQ trace and specify MAC addresses for the source and destination, NetQ displays the message “No valid path to destination” and does not display trace data. | 4.9.0-4.12.0 | |
3613811
| LCM operations using in-band management are unsupported on switches that use eth0 connected to an out-of-band network. To work around this issue, configure NetQ to use out-of-band management in the mgmt VRF on Cumulus Linux switches when interface eth0 is in use. | 4.8.0-4.12.0 | |
Download all 4.12 release notes as .xls