• December 16, 2019, 09:10:46 AM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: ERS 5530-24TFD: strange logs  (Read 3447 times)

0 Members and 1 Guest are viewing this topic.

Offline FjRe

  • Rookie
  • **
  • Posts: 14
ERS 5530-24TFD: strange logs
« on: July 03, 2012, 03:44:57 PM »
Hi all,

One customer has a 5th units stack of 1 ERS5530-24TFD(Base unit) and 4 ERS5520-48T(FW:5.0.0.4; SW:5.1.3.024).
When connecting the console to the base unit - periodically appear the following logs:
soc_draco_l3_hash: invalid hash_sel 6
soc_draco_l3_hash: invalid hash_sel 7
soc_draco_l3_hash: invalid hash_sel 6
soc_draco_l3_hash: invalid hash_sel 6
soc_draco_l3_hash: invalid hash_sel 6
soc_draco_l3_hash: invalid hash_sel 6
soc_draco_l3_hash: invalid hash_sel 6
soc_draco_l3_hash: invalid hash_sel 6
soc_draco_l3_hash: invalid hash_sel 7....
 and so one

Anyone faced with a similar, and that this could mean?

Thanks in advance.
« Last Edit: July 03, 2012, 03:54:33 PM by FjRe »


Offline Flintstone

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 961
Re: ERS 5530-24TFD: strange logs
« Reply #1 on: July 04, 2012, 04:11:32 AM »
Hi FjRe,

I believe this is an error from the Broadcom part of the code?

I believe the problem you are seeing could be a 'hash' collision?

In order to forward data at line rate at layer 3 the IP addresses are 'hashed' using an algorithm to point at a location in a memory table to forward data quickly.  If there are lots of data with similar IP addresses being forwarded at the the same time there is a possibility of a 'hash' collision.  What is normally seen in this scenario is that some layer 3 traffic will be forwarded by the CPU instead of the hardware, so you might see high CPU as a symptom of the issue?

CheerZ

Offline FjRe

  • Rookie
  • **
  • Posts: 14
Re: ERS 5530-24TFD: strange logs
« Reply #2 on: August 02, 2012, 01:58:05 PM »
Hi Flinstone,

Thanks for the explanation.

Unfortunately, I no longer had the capacity to deal with this problem. This unit was replaced, then the problem is not reproduced.