Reset Search
 

 

Article

I/O slot reboot with I/O memory depletion

« Go Back

Information

 
TitleI/O slot reboot with I/O memory depletion
Symptoms
I/O slot reboot with I/O memory depletion
Environment
  • Black Diamond 8806
  • EXOS 15.3.1.4 Patch 1-36
Cause
The command:
debug hal show sys-health-check
Shows low memory on IO modules.
In the log we see:
<Erro:Kern.Card.Error> Slot-6: async queue is growing (900000) type is 704536, customType is 24
<Erro:Kern.Card.Error> Slot-6: async queue is growing (800000) type is 245785, customType is 25



Custom type 24 and 25 are FDB delete / add.
This is an indication of Excessive MAC movements.
Resolution
Check for MAC movements by enabling MAC tracking:

conf fdb mac-tracking ports all
show log counters FDB.MACTracking


If the counters show high MAC movement.
Briefly add the FDB.MACTracking.MACMove event to the logs.
configure log filter "DefaultFilter" add events "FDB.MACTracking.MACMove"

This command needs to be removed afterwards, otherwise your log will filled with only MAC move messages.
If there are still MAC moves, the above will show the actual MAC and ports that are involved.

<Noti:FDB.MACTracking.MACMove> MSM-A: The MAC address <MAC ADDRESS> on VLAN "<VLAN NAME>" has moved from port 5:24 to port 2:24
<Noti:FDB.MACTracking.MACMove> MSM-A: The MAC address <MAC ADDRESS> on VLAN "<VLAN NAME>" has moved from port 5:24 to port 2:5


Find the reason for this mac-movement from the connected client and correct this.
Possible causes for this are:
  1. Device with a similar MAC address on different ports. (i.e port sharing on the device but not on the switch)
  2. Different devices with duplicate MAC addresses. As you can configure MAC addresses manually on virtual hosts it is also possible that we have such a situation.

 
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

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

Characters Remaining: 255