Reset Search
 

 

Article

Some of the IPv6 entries are not removed from L3 hardware table

« Go Back

Information

 
TitleSome of the IPv6 entries are not removed from L3 hardware table
Symptoms
The following errors are logged:
 
<Warn:Kern.IPv4Mc.Warning> Slot-4: IPv4 multicast entry not added.  Hardware L3 Table full. (Logged at most once per hour.)
<Warn:Kern.IPv4Adj.Warning> Slot-8: Error finding adjacency when deleting hash collision.
<Warn:Kern.IPv4Adj.Warning> Slot-5: Error finding adjacency when deleting hash collision.
<Warn:Kern.IPv4Adj.Warning> Slot-6: Error finding adjacency when deleting hash collision.
<Warn:Kern.IPv4Adj.Warning> Slot-3: Error finding adjacency when deleting hash collision.
<Warn:Kern.IPv4Adj.Warning> Slot-5: Error finding adjacency when deleting hash collision.
<Warn:Kern.IPv4Adj.Warning> Slot-1: vrId    0 adj 0x00000002 Error finding adjacency when deleting hash collision.
<Warn:Kern.IPv4Adj.Warning> Slot-8: vrId    0 adj 0x865A1298 Error finding adjacency when deleting hash collision.
<Warn:Kern.IPv4Adj.Warning> Slot-5: vrId    0 adj 0x00000002 Error finding adjacency when deleting hash collision.
<Warn:Kern.IPv4Adj.Warning> Slot-6: vrId -2076482664 adj 0x00723E06 Error finding adjacency when deleting hash collision.

 
Environment
EXOS 16.1.x
BlackDiamond 8810
Cause
When an IPv6 entry fails to be deleted from from the l3_entry_2 hardware table, a hashing collision occurs, resulting in the above errors being logged for the affected slot.
This is related to CR xos0061200.
Resolution
Upgrade to a firmware version that fixes this CR.
  • 16.2.x (is not fixed in 16.2.1)
  • 22.1.x
Additional notes
Workaround:
  • Call into GTAC and have an engineer enter debug mode and clear the l3_entry_2 table
  • Reboot the affected slot

How to contact Extreme Networks Global Technical Assistance Center (GTAC)

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255