Known Issues in This Release
Ref # |
Description |
4119214 |
Description: In case of pulling telemetry data from the UFM server (High or low-frequency instances), the loopback/local host IP should be used instead of the hostname or host IP. Example of High-Frequency (Primary) Telemetry Instance:
Example of Low-Frequency (Secondary) Telemetry Instance:
|
Keywords: Localloop IP, Telemetry, Local Host | |
Workaround: N/A | |
Discovered in Release: 6.19.0 | |
4151847 |
Description: Primary Telemetry is not updated properly |
Keywords: Primary Telemetry | |
Workaround: Comment out or remove the line that defines If UFM is already running, restart the telemetry service for the change to take effect by running | |
Discovered in Release: 6.19.0 | |
4157855 |
Description: The High-Frequency (Primary) Telemetry instance is missing the necessary environment variable in UTM (non-legacy) mode, which causes an incorrect sample rate.
|
Keywords: Telemetry | |
Workaround:
| |
Discovered in Release: 6.19.0 | |
4172677 |
Description: UFM Telemetry server experiencing slowdowns in data collection and response to requests |
Keywords: Telemetry, Slowdown, Data Collection | |
Workaround: Implement the following configuration update on both the primary and secondary telemetry:
Then, restart UFM or UFM Telemetry. | |
Discovered in Release: 6.19.0 | |
4161921 |
Description: VL15 counters are returned NA due to invalid parsing of the response. |
Keywords: L15 counters, Management Traffic, ibdiagnet | |
Workaround: N/A | |
Discovered in Release: 6.19.0 |
For a list of known issues from previous releases, please refer to Known Issues History.