Technical Tip: Information about DRBG failed errors

Under some circumstances, DRBG errors may be seen in the console.

System event logs do not show these messages, but console output shows these when the following commands are run:

config global
diagnose debug console time enable
diagnose debug kernel level 8
diagnose debug enable
diagnose debug duration 0
diagnose debug kernel level 8

2025-Feb-20 13:30:58.234 RXDATA: DRBG generate failed
2025-Feb-20 13:30:58.234 RXDATA:
2025-Feb-20 20:59:58.181 RXDATA: DRBG generate failed
2025-Feb-20 20:59:58.181 RXDATA:
2025-Feb-21 06:58:46.840 RXDATA: DRBG generate failed
2025-Feb-21 06:58:46.840 RXDATA:
2025-Feb-21 15:24:58.216 RXDATA: DRBG generate failed
2025-Feb-21 15:24:58.216 RXDATA:
2025-Feb-21 21:33:58.214 RXDATA: DRBG generate failed
2025-Feb-21 21:33:58.215 RXDATA:
2025-Feb-22 18:41:58.224 RXDATA: DRBG generate failed
2025-Feb-22 18:41:58.224 RXDATA:
2025-Feb-23 08:33:58.214 RXDATA: DRBG generate failed
2025-Feb-23 08:33:58.214 RXDATA:
2025-Feb-24 07:44:58.215 RXDATA: DRBG generate failed
2025-Feb-24 07:44:58.216 RXDATA:
2025-Feb-24 16:10:58.226 RXDATA: DRBG generate failed
2025-Feb-24 16:10:58.226 RXDATA:

DRBG generating failed errors are fixed in v7.4.1 firmware and beyond.
This is not an error message, but an 'informational' message.