ISR4221这日志是什么报错

[kingisme]

Apr 8 05:55:23: %UTIL-6-RANDOM: A pseudo-random number was generated twice in succession
Apr 8 07:32:10: %UTIL-6-RANDOM: A pseudo-random number was generated twice in succession
Apr 8 07:42:11: %UTIL-6-RANDOM: A pseudo-random number was generated twice in succession
Apr 8 08:54:35: %UTIL-6-RANDOM: A pseudo-random number was generated twice in succession
Apr 8 08:55:41: %UTIL-6-RANDOM: A pseudo-random number was generated twice in succession
Apr 8 09:16:00: %UTIL-6-RANDOM: A pseudo-random number was generated twice in succession
Apr 8 09:56:18: %UTIL-6-RANDOM: A pseudo-random number was generated twice in succession
Apr 8 17:12:12: %UTIL-6-RANDOM: A pseudo-random number was generated twice in succession
Apr 8 17:47:38: %UTIL-6-RANDOM: A pseudo-random number was generated twice in succession
Apr 8 18:06:31: %UTIL-6-RANDOM: A pseudo-random number was generated twice in succession
Apr 8 19:18:00: %UTIL-6-RANDOM: A pseudo-random number was generated twice in succession
Apr 8 20:00:02: %UTIL-6-RANDOM: A pseudo-random number was generated twice in succession
Apr 8 20:06:23: %UTIL-6-RANDOM: A pseudo-random number was generated twice in succession
Apr 8 20:21:51: %UTIL-6-RANDOM: A pseudo-random number was generated twice in succession
Apr 8 23:07:40: %UTIL-6-RANDOM: A pseudo-random number was generated twice in succession
Apr 8 23:56:13: %UTIL-6-RANDOM: A pseudo-random number was generated twice in succession

[Rps-Cheers]

来参考一下如下bug：
%UTIL-6-RANDOM: A pseudo-random number was generated twice in succession
CSCve32330
Description
Symptom:
May 5 21:26:10.188: %UTIL-6-RANDOM: A pseudo-random number was generated twice in succession
*May 5 21:43:08.348: %UTIL-6-RANDOM: A pseudo-random number was generated twice in succession
*May 5 21:47:46.161: %UTIL-6-RANDOM: A pseudo-random number was generated twice in succession
Above messages are seen once occasionally.
Conditions:
When CDP is enabled.
Issue is not seen when CDP not enabled.
Workaround:
There's no workaround at this time.
Messages can be safely ignored as they do not have any functional impact.
Further Problem Description:
Issue seen in 16.6 onwards after the introduction of crimson_db_cdp_receive_notify().
Customer Visible
Notifications

Save Bug
Open Support Case
Was the description about this Bug Helpful?(18)
Details
Last Modified:
Apr 5,2019
Status:
Fixed
Severity:
2 Severe
Product: (15)
Cisco IOS
Cisco 4221 Integrated Services Router
Cisco 4331 Integrated Services Router
Cisco 4321 Integrated Services Router
Cisco 4431 Integrated Services Router
Cisco ASR 1002-X Router
Cisco ASR 1001-X Router
Cisco Cloud Services Router 1000V
Cisco 4451-X Integrated Services Router
Cisco 4351 Integrated Services Router
Cisco ASR 1000 Series Route Processor (RP2)
Cisco ASR 1002-HX Router
Cisco cBR-8 Converged Broadband Router
Cisco ASR 1001-HX Router
Cisco ASR 1000 Series Route Processor (RP3)
Known Affected Releases: (3)
16.6.1
16.8.1
Fuji-16.8.1
Known Fixed Releases: (11)
Everest-16.6.3
16.8.1
16.7.2
16.6.3
Fuji-16.8.1
Fuji-16.7.2
16.8(0.142)
16.7(1.53)
16.6(2.45)

[18653465190]

跟着学习了解一下。

[Walter.wu]

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCve32330/?rfs=iqvred
以上为BUG链接，可以进去看到BUG信息。
简而言之，找代理商要版本，让他们升级或者你自己找时间窗口升级。

[Rockyw]

Here's the explanation by cisco:
RANDOM-6
Error Message %RANDOM-6-RANDOM: A pseudo-random number was generated twice in succession
Explanation: A pseudo-random number generator produced the same number twice in succession.
Recommended Action: Under normal circumstances, a pseudo-random number generator will occasionally produce the same number twice in succession, which is not a problem. However, if this message occurs frequently, the system should be manually reloaded. If the message is persistent across reloads, copy the error message exactly as it appears, and report it to your Cisco technical support representative.

From what can be told about that is, probably nothing to worry about but better make a case with Cisco and have it investigated.
上述信息来源：https://learningnetwork.cisco.com/thread/95730