Hello Muhammad,Greetings!

mali786 · ‎05-24-2015

Dears,

I am looking for some help to understand the following logs on my 6509-E chassis.

1: 05/24/15 10:29:16 2/5/-1: MAJ, GOLD, DIAG_SYS_LIMIT (sp_last_busy_percent, tx_rate, rx_rate, sp_netint_thr) NOT HIT
2: 05/24/15 10:29:16 2/5/-1: MAJ, GOLD, diag_hit_sys_limit[2/1]: sp_netint_thr[1]
3: 05/24/15 10:29:16 2/5/-1: MAJ, GOLD, diag_hit_sys_limit[2/1]: SP[10%], Tx_rate[46017], Rx_rate[14248]
4: 05/24/15 10:29:16 2/5/-1: MAJ, GOLD, DIAG_SYS_LIMIT HIT
5: 05/24/15 10:27:19 2/5/-1: MAJ, GOLD, DIAG_SYS_LIMIT (sp_last_busy_percent, tx_rate, rx_rate, sp_netint_thr) NOT HIT
6: 05/24/15 10:27:15 2/5/-1: MAJ, GOLD, loopback_internal_port[2/6]:diag_hit_sys_limit!test skipped.

7: 05/24/15 10:27:15 2/5/-1: MAJ, GOLD, loopback_internal_port[2/10]:diag_hit_sys_limit!test skipped.

8: 05/24/15 10:27:15 2/5/-1: MAJ, GOLD, diag_hit_sys_limit[4/1]: sp_netint_thr[0]
9: 05/24/15 10:27:15 2/5/-1: MAJ, GOLD, diag_hit_sys_limit[4/1]: SP[11%], Tx_rate[104829], Rx_rate[46593]
10: 05/24/15 10:27:15 2/5/-1: MAJ, GOLD, DIAG_SYS_LIMIT HIT
11: 05/24/15 10:25:39 2/5/-1: MAJ, GOLD, DIAG_SYS_LIMIT (sp_last_busy_percent, tx_rate, rx_rate, sp_netint_thr) NOT HIT
12: 05/24/15 10:25:36 2/5/-1: MAJ, GOLD, diag_hit_sys_limit[3/1]: sp_netint_thr[0]
13: 05/24/15 10:25:36 2/5/-1: MAJ, GOLD, diag_hit_sys_limit[3/1]: SP[5%], Tx_rate[115212], Rx_rate[42402]
14: 05/24/15 10:25:36 2/5/-1: MAJ, GOLD, DIAG_SYS_LIMIT HIT
15: 05/24/15 10:25:18 2/5/-1: MAJ, GOLD, DIAG_SYS_LIMIT (sp_last_busy_percent, tx_rate, rx_rate, sp_netint_thr) NOT HIT
16: 05/24/15 10:25:18 2/5/-1: MAJ, GOLD,
test_sp_rp_inband_ping[5]: diag_hit_sp_sys_limit. SP-RP Ping Test skipped. Reason(s): High Inband Rate (Tx/Rx = 111976/39400).
17: 05/24/15 10:25:15 2/5/-1: MAJ, GOLD, diag_hit_sys_limit[4/1]: sp_netint_thr[0]
18: 05/24/15 10:25:15 2/5/-1: MAJ, GOLD, diag_hit_sys_limit[4/1]: SP[10%], Tx_rate[111976], Rx_rate[39400]
19: 05/24/15 10:25:15 2/5/-1: MAJ, GOLD, DIAG_SYS_LIMIT HIT
20: 05/24/15 10:24:40 2/5/-1: MAJ, GOLD, DIAG_SYS_LIMIT (sp_last_busy_percent, tx_rate, rx_rate, sp_netint_thr) NOT HIT
21: 05/24/15 10:24:36 2/5/-1: MAJ, GOLD, loopback_internal_port[2/6]:diag_hit_sys_limit!test skipped.

22: 05/24/15 10:24:36 2/5/-1: MAJ, GOLD, diag_hit_sys_limit[4/1]: sp_netint_thr[0]
23: 05/24/15 10:24:36 2/5/-1: MAJ, GOLD, diag_hit_sys_limit[4/1]: SP[12%], Tx_rate[107539], Rx_rate[44938]
24: 05/24/15 10:24:36 2/5/-1: MAJ, GOLD, DIAG_SYS_LIMIT HIT
25: 05/24/15 10:23:39 2/5/-1: MAJ, GOLD, DIAG_SYS_LIMIT (sp_last_busy_percent, tx_rate, rx_rate, sp_netint_thr) NOT HIT
26: 05/24/15 10:23:36 2/5/-1: MAJ, GOLD, loopback_internal_port[2/6]:diag_hit_sys_limit!test skipped.

27: 05/24/15 10:23:36 2/5/-1: MAJ, GOLD, loopback_internal_port[2/10]:diag_hit_sys_limit!test skipped.

28: 05/24/15 10:23:36 2/5/-1: MAJ, GOLD, diag_hit_sys_limit[2/10]: sp_netint_thr[0]
29: 05/24/15 10:23:36 2/5/-1: MAJ, GOLD, diag_hit_sys_limit[2/10]: SP[10%], Tx_rate[107027], Rx_rate[41098]
30: 05/24/15 10:23:36 2/5/-1: MAJ, GOLD, DIAG_SYS_LIMIT HIT
31: 05/24/15 10:22:39 2/5/-1: MAJ, GOLD, DIAG_SYS_LIMIT (sp_last_busy_percent, tx_rate, rx_rate, sp_netint_thr) NOT HIT
32: 05/24/15 10:22:36 2/5/-1: MAJ, GOLD, diag_hit_sys_limit[1/1]: sp_netint_thr[0]
33: 05/24/15 10:22:36 2/5/-1: MAJ, GOLD, diag_hit_sys_limit[1/1]: SP[11%], Tx_rate[127521], Rx_rate[42656]

Please let me know if someone have any idea about it.

Regards,

Charles Hill · ‎05-24-2015

Hello,

GOLD = General Online Diagnostics

Take a look at the following posting.

https://supportforums.cisco.com/discussion/11020836/cisco-6500-system-log

Q&A for General Online Diagnostics

http://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/generic-online-diagnostics-gold/prod_qas0900aecd804c224e.html

White paper for GOLD on the 6500 switch

http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-6500-series-switches/prod_white_paper0900aecd801e659f.html

Hope this helps,

Please rate helpful posts.

Thanks.

Rafatur Rahman · ‎05-24-2015

Hello Muhammad,

Greetings!

The messages you're seeing do not indicate a test failure, they're merely
informational messages stating that the test got skipped due to high inband
port or CPU utilization. If this utilization is above a certain threshold
the test packets can become vulnerable to delays and/or drops and possibly
cause false failures (i.e. the test would fail although there is nothing is
wrong with the data path).

The switch is expected to run into transient conditions like CPU spikes,
excessive packet interrupts in SW etc. As a result, we skip the test to
avoid false failures. This is by design. Unless the test is running into
consecutive failures exceeding the threshold (10 in this case), there is no
problem.

The above messages are informational and do not mean that the module is
faulty. The "MAJ" word in the log message is a bit misleading, as it would
make a person believe there is some sort of major error on the line
card.This is not the case here, as the developers are working on changing
this cosmetic issue in later codes.

To summarize this case, there's actually no problem with the hardware or the
switch. The logs are just informational and are part of the periodic health
check.

If you check the "show diagnostics result module all" you should not see any
failed test.

You could set your diagnostics to "complete" so that complete diagnostics is run
on the modules after a reboot of the switch or reseat of the module (so more
of those tests listed are actually run).

The command to do so is "diagnostic
bootup level complete"

HTH.

Regards,

6509 System Logging