01-27-2018 11:59 PM - edited 03-05-2019 09:50 AM
On a 892FSP router running Version 15.7(3)M1 I get a new type of messages in my log. The router is connected to the internet, with at inbound ACL on the interface, and it runs DMVPN.
I do get all the normal scanning attempts from the internet but also this new entry "Packet is neither ipv4 nor ipv6"
What is this all about? I have google´d it but did not find anything from cisco.
Jan 28 07:52:17.786: %SEC-6-IPACCESSLOGP: list outside_in denied udp 167.114.46.166(5062) -> xxx.xxx.xxx.xxx(5060), 1 packet
Jan 28 07:52:21.014: %SEC-6-IPACCESSLOGP: list outside_in denied tcp 101.99.6.176(27059) -> xxx.xxx.xxx.xxx(445), 1 packet
Jan 28 07:52:44.138: %SEC-6-IPACCESSLOGDP: list outside_in denied icmp 206.117.25.90 -> xxx.xxx.xxx.xxx (8/0), 1 packet
Jan 28 07:52:54.086: Packet is neither ipv4 nor ipv6
Solved! Go to Solution.
01-28-2018 12:29 AM
Hello,
I have tried to access the IP addresses in your log.
This one is especially interesting:
206.117.25.90
03-14-2018 10:50 AM
This is now documented under bug ID - CSCvi42835.
01-28-2018 12:29 AM
Hello,
I have tried to access the IP addresses in your log.
This one is especially interesting:
206.117.25.90
01-28-2018 03:23 PM - edited 01-28-2018 03:23 PM
We too are seeing this with version 157-3.M1.bin but how can we filter these from eating up our syslog and spewing to the terminal? We are seeing them every 10 seconds.
03-04-2018 07:56 PM
Did you figure out what was causing this? I'm seeing this same message after upgrading some 2921's to 15.5(3)M7.
-Brian
03-05-2018 03:14 AM - edited 03-05-2018 03:17 AM
It's most likely a software issue. I was able to keep it from filling the logs by installing a logging discriminator that matches a regular expression filter like so:
logging discriminator PACKET mnemonics drops _Packet is neither ipv4 nor ipv6
logging buffered discriminator PACKET 4096
03-06-2018 02:17 AM
I have also got this issue on C897VA-K9 with 15.5(3)M7. The issue was not present on 15.5(3)M6a
Mar 6 11:13:13: Packet is neither ipv4 nor ipv6
Could somebody open a TAC case for this? I haven't seen any bug id related to the issue. This particular device is not curently covered with the service contract.
03-12-2018 03:06 PM
In my case, I was able to eliminate this log from appearing after disabling CDP on my DMVPN tunnel interface.
03-12-2018 11:37 PM
Disabling CDP on DMVPN interface resolved the issue!
03-14-2018 10:50 AM
This is now documented under bug ID - CSCvi42835.
03-29-2018 04:31 AM - edited 03-29-2018 04:33 AM
In my case, I see such messages even if the CDP is disabled globally. I also do not have a DMVPN.
Cisco 3925e - 15.5(3)M7.
05-27-2018 12:17 AM
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