08-30-2011 12:56 AM - edited 03-07-2019 01:58 AM
hi all,
these are the logs in my distribution switch which caused to reboot the switch..can someone just share what would be the root cause for this problem.
Aug 22 07:41:10 UTC: %SEC-6-IPACCESSLOGRP: list 169 denied igmp 10.254.171.9 (Vlan508 0021.6a7e.137c) -> 224.0.0.22, 1 packet
Aug 22 07:41:16 UTC: %SEC-6-IPACCESSLOGRP: list 169 denied igmp 10.254.63.57 (Vlan508 0021.6a49.d3c7) -> 224.0.0.22, 1 packet
Aug 22 07:41:22 UTC: %SEC-6-IPACCESSLOGRP: list 169 denied igmp 10.254.0.252 (Vlan508 0024.d75a.eeb2) -> 224.0.0.22, 1 packet
Aug 22 07:41:26 UTC: %SEC-6-IPACCESSLOGRP: list 169 denied igmp 10.254.135.195 (Vlan508 0021.6aaa.f946) -> 224.0.0.22, 1 packet
Aug 22 07:41:29 UTC: %SEC-6-IPACCESSLOGRP: list 169 denied igmp 10.254.27.81 (Vlan508 0024.d723.9e7e) -> 224.0.0.22, 1 packet
Aug 22 07:41:40 UTC: %SEC-6-IPACCESSLOGRP: list 169 denied igmp 10.254.172.20 (Vlan508 0021.6aa4.f451) -> 224.0.0.22, 1 packet
Aug 22 07:41:48 UTC: %SEC-6-IPACCESSLOGRP: list 169 denied igmp 10.254.102.26 (Vlan508 0024.d723.8da4) -> 224.0.0.22, 1 packet
Aug 22 07:41:53 UTC: %SEC-6-IPACCESSLOGRL: access-list logging rate-limited or missed 25 packets
VKS
08-30-2011 01:56 AM
It's quite werid that the ACL deny will cause the switch reload.
Any log indicate the msg cause the switch reload?
probably you can find any clue from show tech e.g. crashfile, crash process, reload reason
08-30-2011 01:19 PM
I would agree with Dazhi that it would be really strange that the ACL logging would have caused the switch to reload. We would need to check for either a crashinfo or looking at the complete logs from the syslog (if configured) would help identifying the root cause. If there is nothing in the logs except these messages & switch didn't crash, let us know. We can look for a known bug.
Regards,
Amit
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