Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

C6K Platform: Trying to send giants on a VLAN (reported by MSFC)

Hi

We have the following log entries:

....(start)....

Jun 30 01:35:43: %MSFC2-3-TOOBIG: attempt to send giant packet on Vlan605 (1574

bytes from 70A87D2)

-Traceback= 30259844 301C99D4 302C6218 302B8CA8 302B9A54 302B83F0 302B85EC 302B8

778 301F49F4 301F49E0

Jun 30 01:36:42: %MSFC2-3-TOOBIG: attempt to send giant packet on Vlan605 (1574

bytes from 70A87D2)

-Traceback= 30259844 301C99D4 302C6218 302B8CA8 302B9A54 302B83F0 302B85EC 302B8

778 301F49F4 301F49E0

.......(end)....

Unfortunately I wasn't able to find anything out on the Cisco documentation (e.g. CCO).

It seems that there's no (serious) impact to a network connectivity for a specific host, but the bad thing is the log is filled up with a lot of these messages.

And furthermore I don't have any indication who is the source/sender of this entries (probably the switch itself, because it's an log entry on the MFSC and not on the switch) and that's not a really good feeling.

Does anybody knows anything about this or is it probably a bug?

Thanks a lot for any input.

Raffael

3 REPLIES
Cisco Employee

Re: C6K Platform: Trying to send giants on a VLAN (reported by M

Can you paste the output of sh ver and sh interface VLAN605

Community Member

Re: C6K Platform: Trying to send giants on a VLAN (reported by M

Here it is:

sh ver

Cisco Internetwork Operating System Software

IOS (tm) MSFC2 Software (C6MSFC2-IS-M), Version 12.1(2)E, EARLY DEPLOYMENT RELEA

SE SOFTWARE (fc1)

Copyright (c) 1986-2000 by cisco Systems, Inc.

Compiled Mon 19-Jun-00 22:17 by linda

Image text-base: 0x30008930, data-base: 0x30D14000

ROM: System Bootstrap, Version 12.1(3r)E2, RELEASE SOFTWARE (fc1)

BOOTFLASH: MSFC2 Software (C6MSFC2-BOOT-M), Version 12.1(2)E, EARLY DEPLOYMENT R

ELEASE SOFTWARE (fc1)

agic-tg-ak109109 uptime is 15 weeks, 4 days, 9 hours, 35 minutes

System returned to ROM by power-on at 21:48:12 MET Fri Mar 14 2003

System restarted at 21:49:40 MET Fri Mar 14 2003

Running default software

cisco Cat6k-MSFC2 (R7000) processor with 114688K/16384K bytes of memory.

Processor board ID SAD04350B7L

R7000 CPU at 300Mhz, Implementation 39, Rev 2.1, 256KB L2, 1024KB L3 Cache

Last reset from power-on

Bridging software.

X.25 software, Version 3.0.0.

37 Virtual Ethernet/IEEE 802.3 interface(s)

509K bytes of non-volatile configuration memory.

16384K bytes of Flash internal SIMM (Sector size 512K).

Configuration register is 0x102

The interface statistics show a huge number of input AND output drops which increment with an entry in the log (refer output on previous message). Interesting is the following: the number of input drops remains the same (for a while) whereas the output number increases (that's why I asked the question who's the source of the giant frames, the switch/MSFC?):

sh int vlan 605

Vlan605 is up, line protocol is up

Hardware is Cat6k RP Virtual Ethernet, address is 0002.fdb1.57c2 (bia 0002.fdb

1.57c2)

Description: *** ??????? ***

Internet address is 172.21.28.1/24

MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,

reliability 255/255, txload 1/255, rxload 1/255

Encapsulation ARPA, loopback not set

ARP type: ARPA, ARP Timeout 04:00:00

Last input 00:00:01, output never, output hang never

Last clearing of "show interface" counters never

Queueing strategy: fifo

Output queue 0/40, 24903 drops; input queue 0/75, 10959485 drops

5 minute input rate 0 bits/sec, 1 packets/sec

5 minute output rate 0 bits/sec, 0 packets/sec

10343544 packets input, 685496198 bytes, 5421 no buffer

Received 15817649 broadcasts, 0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

4003833 packets output, 287560480 bytes, 0 underruns

0 output errors, 1 interface resets

0 output buffer failures, 0 output buffers swapped out

.......(end)...............

Thank you

Raffael

Cisco Employee

Re: C6K Platform: Trying to send giants on a VLAN (reported by M

I've decoded the tracebacks that you were getting, and it looks like you are running into two internal bugs in the version of code you are running. (CSCdr48765 and CSCdr67614). You will not be able to see this bugs as they were found internally. 12.1(8b)E14 should be a good code. Make sure you read release notes and bug tool kit for known issues

88
Views
0
Helpful
3
Replies
CreatePlease to create content