6509: Invalid packet (too large) - discarded

Unanswered Question
Jul 1st, 2009
User Badges:


Maybe this is not a good question. So I discarded it.


#show logging | in too large

Jun 9 22:36:20: Invalid packet (too large) length=34304

Jun 12 16:19:19: Invalid packet (too large) length=34304

Jun 12 16:21:05: Invalid packet (too large) length=34304

Jun 14 16:40:49: Invalid packet (too large) length=33808

Jun 19 03:05:07: Invalid packet (too large) length=33152

Jun 19 04:18:12: Invalid packet (too large) length=33152

Jun 19 07:29:49: Invalid packet (too large) length=33152

Jun 21 09:45:14: Invalid packet (too large) length=34304

Jun 21 11:27:39: Invalid packet (too large) length=34304

Jun 21 12:06:05: Invalid packet (too large) length=34304

Jun 21 14:36:46: Invalid packet (too large) length=34304

Jun 27 12:49:41: Invalid packet (too large) length=33792

Jun 29 09:04:57: Invalid packet (too large) length=33792

Jun 29 09:13:40: Invalid packet (too large) length=33792

Jun 30 01:26:07: Invalid packet (too large) length=34304

Jun 30 01:51:32: Invalid packet (too large) length=34304

Jun 30 02:28:54: Invalid packet (too large) length=34304

Jun 30 02:35:09: Invalid packet (too large) length=34304

Jun 30 03:04:37: Invalid packet (too large) length=34304



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
ldardon Tue, 07/07/2009 - 19:03
User Badges:

This message is being issued by the L2 Trace code. If no one is doing an l2trace command on this switch, then the message is most likely from the L2 trace server process, which is listening for IP packets on UDP port 2228. If the UDP packet format is not exactly as the L2 trace code expects, then you might see an error message like this one.

Actions

This Discussion