07-14-2008 08:58 AM - edited 03-06-2019 12:10 AM
Dear Netpro community,
I am puzzled by the high number of ignore counter showing on vlan 1.
Base on the output of debug ip error, here is the captured output:
9w1d: datagramsize=342, IP 51203: s=137.55.136.151 (Vlan1), d=255.255.255.255, t
otlen 328, fragment 0, fo 0, dispose udp.noport
9w1d: datagramsize=524, IP 15838: s=137.55.136.245 (Vlan1), d=255.255.255.255, t
otlen 510, fragment 0, fo 0, dispose udp.noport
9w1d: datagramsize=62, IP 0: s=137.55.136.3 (Vlan1), d=224.0.0.2, totlen 48, fra
gment 0, fo 0, dispose ip.notgateway
9w1d: datagramsize=60, IP 0: s=137.55.136.3 (Vlan1), d=224.0.0.2, totlen 44, fra
gment 0, fo 0, dispose ip.notgateway
9w1d: datagramsize=62, IP 0: s=137.55.136.2 (Vlan1), d=224.0.0.2, totlen 48, fra
gment 0, fo 0, dispose ip.notgateway
9w1d: datagramsize=342, IP 51204: s=137.55.136.151 (Vlan1), d=255.255.255.255, t
otlen 328, fragment 0, fo 0, dispose udp.noport
9w1d: datagramsize=518, IP 51639: s=137.55.136.24 (Vlan1), d=137.55.255.255, tot
len 504, fragment 0, fo 0, dispose udp.noport
9w1d: datagramsize=62, IP 0: s=137.55.136.3 (Vlan1), d=224.0.0.2, totlen 48, fra
gment 0, fo 0, dispose ip.notgateway
9w1d: datagramsize=62, IP 0: s=137.55.136.2 (Vlan1), d=224.0.0.2, totlen 48, fra
gment 0, fo 0, dispose ip.notgateway
9w1d: datagramsize=62, IP 0: s=137.55.136.3 (Vlan1), d=224.0.0.2, totlen 48, fra
gment 0, fo 0, dispose ip.notgateway
9w1d: datagramsize=272, IP 17624: s=137.55.136.245 (Vlan1), d=137.55.137.255, to
tlen 258, fragment 0, fo 0, dispose udp.noport
9w1d: datagramsize=92, IP 36118: s=192.168.1.201 (Vlan1), d=192.168.1.255, totle
n 78, fragment 0, fo 0, dispose ip.notgateway
Jul 15 00:50:07 SG: %SYS-5-SCHEDULED_RELOAD_CANCELLED: Scheduled reload cancell
ed at 00:50:07 SG Tue Jul 15 2008
my questions would be:
1) Is the ignore counter caused by the above conditions?
2) if yes, what would be the cause? Is it due to the buffers?
3) How do i interpret the messages?
Small buffers, 104 bytes (total 36, permanent 25, peak 115 @ 7w0d):
35 in free list (20 min, 60 max allowed)
70236535 hits, 3310 misses, 5706 trims, 5717 created
0 failures (0 no memory)
Middle buffers, 600 bytes (total 18, permanent 15, peak 39 @ 7w0d):
17 in free list (10 min, 30 max allowed)
4070336 hits, 330 misses, 139 trims, 142 created
10 failures (0 no memory)
Big buffers, 1524 bytes (total 6, permanent 5, peak 22 @ 6w4d):
6 in free list (5 min, 10 max allowed)
625577 hits, 1733 misses, 1275 trims, 1276 created
1316 failures (0 no memory)
VeryBig buffers, 4520 bytes (total 10, permanent 0, peak 16 @ 3d00h):
10 in free list (0 min, 10 max allowed)
132496 hits, 581 misses, 74 trims, 84 created
573 failures (0 no memory)
Large buffers, 5024 bytes (total 1, permanent 0, peak 6 @ 6w5d):
1 in free list (0 min, 5 max allowed)
263 hits, 310 misses, 619 trims, 620 created
310 failures (0 no memory)
Huge buffers, 18024 bytes (total 1, permanent 0, peak 3 @ 6w5d):
1 in free list (0 min, 2 max allowed)
103 hits, 207 misses, 612 trims, 613 created
207 failures (0 no memory)
Any pointer is greatly appreciated. Thanks.
Beno
07-14-2008 12:41 PM
Hello Benson,
at a first glance I don't think the two outputs are related.
About the debug ip error output:
d=255.255.255.255 is the broadcast address these are UDP destined to a port not open on the device
d=224.0.0.2 is the all routers in the subnet
the only line to take care is the following
9w1d: datagramsize=92, IP 36118: s=192.168.1.201 (Vlan1), d=192.168.1.255, totle
n 78, fragment 0, fo 0, dispose ip.notgateway
I suppose your vlan1 is in net =137.55.136.0/23 for the the line:
9w1d: datagramsize=272, IP 17624: s=137.55.136.245 (Vlan1), d=137.55.137.255, to
tlen 258, fragment 0, fo 0, dispose udp.noport
Hope to help
Giuseppe
07-17-2008 07:17 AM
Dear Giuseppe,
Thanks for the information.
9w1d: datagramsize=92, IP 36118: s=192.168.1.201 (Vlan1), d=192.168.1.255, totle
n 78, fragment 0, fo 0, dispose ip.notgateway
For this line, it could be due to a static IP input on the end stations.
However, I am particularly intrigue by the message:
9w1d: datagramsize=272, IP 17624: s=137.55.136.245 (Vlan1), d=137.55.137.255, to
tlen 258, fragment 0, fo 0, dispose udp.noport
what is the meaning of dispose udp.noport? Is this causing the increment in ignore counter?
07-17-2008 07:24 AM
I think it means that 137.55.137.255 is a directed broadcast to a subnet your router is part of, so your router should process the packet itself. However, the packet was addressed to a UDP port that the router does not have any application running. So it discards it. It's a pity the debug doesn't tell you the port number, but maybe debug ip udp would.
Kevin Dorrell
Luxembourg
07-17-2008 07:55 PM
Kevin,
Thanks for the reply. Can I assume that the ignore counter is partly caused by when there is a udp.noport? I need to know more, because, I have vlan1 on other switches, however, I do not see a high number of ignore statistics, only this one has.
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