IOS-XR 5.1.3 SP2 - %OS-RT_CHECK-3-INCONSISTENCY_DETECTED : ipv4-unicast detected inconsistency with

Question

I'm curious if anyone else has seen this message logged after an up/down grade to 5.1.3 w/ SP2
%OS-RT_CHECK-3-INCONSISTENCY_DETECTED : ipv4-unicast detected inconsistency with 1 entries for scan-id N
We were told by TAC this is a cosmetic issue only and not to worry.  However, the engineer inside me wants to know what the router is upset about and how to suppress the log message.  I'd also like to ask Cisco to create a cosmetic bug fix for 5.1.3 to resolve the log message if it is indeed truly cosmetic only in nature.
Thanks!
-ben

Answer 1

hi Ben, the ddts is fixed in 52x forward. There is no smu planned for prior releases.
you can schedule a periodic selective clear of the log buffer via:
RP/0/RSP0/CPU0:A9K-BNG#clear log events delete [option] [field]
the logging correlator, here is a little write up on that (copy/paste from my kb)
XR nag Killer
The short version  (i.e. here's the code to make it happen!)
!! enter config mode... 
conf t
!! this removes the correlator so you can edit it...
no logging correlator apply rule kill-annoyances all-of-router
!!! define the rule
logging correlator rule kill-annoyances type nonstateful
  timeout 600000
!!! this is the "root cause" one... make sure you pick something that happens frequently
rootcause PLATFORM ENVMON FAN_FAIL
!!! these are all the NON root cause events. this is what gets squashed along with the root cause.
!!! add things here that you want squashed.
  nonrootcause
  alarm PLATFORM ENVMON FAN_CLEAR
  alarm PLATFORM ENVMON FANTRAY_FAIL
  alarm PLATFORM ENVMON ENV_CONDITION
  alarm PLATFORM ENVMON FANTRAY_CLEAR
!!! timeouts are currently maxed at ten minutes... (smu anyone?)
  timeout-rootcause 600000
!!! this re-applies the correlator
 logging correlator apply rule kill-annoyances all-of-router
!!! now commit the thing
commit
!!! done...
On a somewhat related note, if anyone is not already familiar with the
 "logging correlator" function -- it can be used to greatly reduce the
 amount of "noise" generated by all these various little things that are
 broken (like single fan tray systems!)
 An example config that I have on my box is as follows:
 logging correlator rule fan type nonstateful
  timeout 600000
  rootcause PLATFORM ENVMON FAN_FAIL
  nonrootcause
  alarm PLATFORM ENVMON FAN_CLEAR
  alarm PLATFORM ENVMON FANTRAY_FAIL
  alarm PLATFORM ENVMON ENV_CONDITION
  alarm PLATFORM ENVMON FANTRAY_CLEAR
  timeout-rootcause 600000
logging correlator apply rule fan
  all-of-router
>>
Which essentially says the following:
>>
1) a message of format "PLATFORM-ENVMON-FAN_FAIL" is a 'root cause' event.
the timeout for root cause events is set to 600000ms (ten minutes), so
no matter how many of these events I see, I will only actually throw a
syslog every ten minutes.
2) underneath this 'root cause' event are a number of 'nonrootcause'
events.  If I see any of these events within the timeout specified (again,
ten minutes) of a 'root cause' I will also suppress these messages -- the
theory here is that I already know the root cause and don't want to clutter
myself up with all the side effects.    In reality we're just hacking the
correlator to get rid of messages, but hey -- it works.  ;-)
>>
3) this particular "correlator rule" is applied to the whole router (you
*can* do all sorts of funky stuff with where you apply it if you want).
4) in real environments the idea is to have lots of different correlators
for different events... but what I do is basically maintain a great big
list of known syslog messages that I don't want to have splattering my
screen, and the correlator gobbles them all up for me.
>>
Limitations:
>>
5) UPDATE: you can now set timeouts up to 7200000 seconds (LONG time...)
>>
6) the only really annoying part is that you have to unapply the rule
before you can edit it... so the process is "unapply rule, commit, change
rule, apply rule, commit" instead of just "change rule".  But hey, it's
better than nothing.
>>
7) if you want to see the messages that got suppressed/correlated, use the
"show logging correlator buffer all-in-buffer" command -- and sit back and
be amazed at how much console bandwidth you've saved.  ;-)
>>
Hope people find this helpful...
config example courtesy of LJ Wobker.
xander