INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Jobs

passport 8600 losing its routing capability intermittently

passport 8600 losing its routing capability intermittently

(OP)
This box is running 4.1.4 version and say every two weeks the switch loses its routing feature and you cannot ping anywhere outside each subnet.
the log message says
"2012-09-21 19:59:23 Local1.Info 159.207.200.2 CPU5
[09/21/12 11:58:55] HW INFO rarCheckConsistency: Record size 140 in hash bin 0x00077331 Next threshold 150"


any help!

Regards,

Mo

RE: passport 8600 losing its routing capability intermittently

Error Message "HW INFO rarCheckConsistency: Record size 140 in hash bin 0x00008ad7 Next threshold 150".

It can be explained as follows:- On the Passport, incoming packets are handled as internal data using :
1) hash pointer (queued in hash bin as FIFO; pointing to forwarding record)
2) forwarding record (internal data itself; originally incoming packets)

The logs above mean that the number of hash pointers queued in hash bin has exceeded the threshold (Record size), which could mean that the number of forwarding records awaiting for being forwarded is getting increased by some reason. This is just an indication of data pointer queue. This itself there would no problem and should be ignored except debugging purpose. The Hash table is used to increase the speed of searching the forwarding table of the RaptARU.

CR v4.1.3
In the CR its mentioned " Too many interfaces running routing protocols will cause serious problems like hash-bin inflation, lookup failures and serious scalability issues".

SOLUTION is to use the control-record-optimisation feature. Actually its a flag which should be enabled and then REBOOT for the flag to take effect.

Commands :
config bootconfig flags control-record-optimization true
save boot

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Resources

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close