05-18-2015 06:14 PM - edited 03-05-2019 01:29 AM
Hi guys, need help, I type the logging history and this error show up.
What does this mean?
Syslog History Table:1 maximum table entries,
saving level warnings or higher
30190 messages ignored, 0 dropped, 0 recursion drops
1776 table entries flushed
SNMP notifications not enabled
entry number 1777 : IP_VFR-3-COALESCE_ERROR
Unable to coalesce fragments arriving through GigabitEthernet0/1.50 - datagram 4012 bytes is too big. UDP packet 192.168.50.20:53 -> 50.62.117.1:2173 has ident: 1068 flags:0x40000000 and 3 fragments
timestamp: 567816242
I have a 5 sub-interfaces on my router. The IP address 192.168.50.20 (VLAN 50) is my Domain Controller. Does this error has an effect on my network. Please help.
Thank you in advance.
05-24-2015 12:08 PM
Hi there,
It may be a bug: CSCsr59225.
Symptom:
Fragmented packets may trigger the following tracebacks on IOS routers:
Jul 26 00:24:00.484: %SYS-2-GETBUF: Bad getbuffer, bytes= 35040 -Process= "
", ipl= 2, -Traceback= 0x80845F4C 0x8030D5D4 0x810227F0 0x81023440 0x81023DA4 0x8005E51C 0x80054C2C 0x8011B1DC 0x8011CF54 0x8036A0C4 0x800C0BD0 0x800C0BD0 0x8036A184 0x8036D2C8 0x8036CD84 0x80375E5C
router#
Jul 26 00:24:00.484: %IP_VFR-3-SYSTEM_ERROR: FastEthernet4: IP VFR System failure - Unable to coalesce fragments
Conditions:
The router is configured with "ip virtual-reassembly" and receives large fragmented segments.
Workaround:
Use the following command to configure the size of the huge buffer large enough such that these large packets can be coalesced:
buffers huge size
The size should be set such that it is larger than the number of bytes reported in the SYS-2-GETBUF message.
Please note that this workaround may have an impact on memory usage.
Please see if your IOS is one of the affected IOS.
06-09-2015 06:22 PM
Thanks Sergiu Daniluk
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