06-19-2007 06:46 PM - edited 03-05-2019 04:50 PM
Hi all.
We have serius problem.
it auto reboots itself randomly, and at this moment we haven't find the cause.
this is crashinfo file...
Using sup-bootflash:crashinfo_20070619-121155.
Writing crashinfo to bootflash:crashinfo_20070619-1211550 Error:3
Jun 18 13:59:43: %MCAST-SP-6-L2_HASH_BUCKET_COLLISION: Failure installing (G,C)->index: (0100.5e67.db0c,189)->0x830 Protocol :0 Error:3
Jun 18 14:07:52: %MCAST-SP-6-L2_HASH_BUCKET_COLLISION: Failure installing (G,C)->index: (0100.5e1c.6489,189)->0x830 Protocol :0 Error:3
Jun 18 14:08:13: %MCAST-SP-6-L2_HASH_BUCKET_COLLISION: Failure installing (G,C)->index: (0100.5e48.7fdf,189)->0x830 Protocol :0 Error:3
...
...
...
Jun 19 20:13:43: %MCAST-SP-6-L2_HASH_BUCKET_COLLISION: Failure installing (G,C)->index: (0100.5e58.9d37,189)->0x830 Protocol :0 Error:3
Jun 19 20:33:03: %MCAST-SP-6-L2_HASH_BUCKET_COLLISION: Failure installing (G,C)->index: (0100.5e72.ba5f,189)->0x830 Protocol :0 Error:3
thanks
06-19-2007 07:18 PM
hi, can you provide software versions, I will check if there is any software bugs on this.
otherwise I recommend to open a cisco TAC case for the device.
1. %MCAST-6-L2_HASH_BUCKET_COLLISION: Failure installing (G,C)->index: ([enet],[dec])->[hex] Protocol :[dec] Error:[dec]
This message indicates that a L2 entry could not be installed in the hardware because there is not enough space in the hash bucket. Multicast packets will be flooded on the incoming VLAN because the Layer 2 entry installation failed.
Recommended Action: No action is required.
Related documents- No specific documents apply to this error message.
2. %MCAST-6-L2_HASH_BUCKET_COLLISION: Failure installing (G,C)->index: ([enet],[dec])->[hex] Protocol :[dec] Error:[dec]
This message indicates that a Layer 2 entry could not be installed in the hardware because there is not enough space in the hash bucket. Multicast packets will be flooded on the incoming VLAN because the Layer 2 entry installation failed.
Recommended Action: No action is required. Note In later 12.1 E releases, the SYSTEM_CONTROLLER facility name replaces the MISTRAL facility name. For example, MISTRAL-3-ERROR becomes SYSTEM_CONTROLLER-3-ERROR. Both messages indicate the same system condition. Note An "SP" between the facility and the severity level (for example, MISTRAL-SP-3-ERROR) indicates that the condition is coming from the Mistral ASIC on the supervisor engine. If nothing appears between the facility and the severity level (for example, MISTRAL-3-ERROR), the condition is coming from the Mistral ASIC on the MSFC.
HTH, rate if this helps
Jorge
06-19-2007 08:20 PM
version 12.2(18)SXD7b
ios: s72033-ps-mz.122-18.SXD7b.bin
thanks.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide