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?
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
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
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
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
This document gives several answers on frequently asked questions for PFRv3 channel state behavior.
Q1: What are all the channel operational states from a BR (border role) perspective and what are the rules/conditions to be in each st...
The need was to reach an host inside a LAN through a VPN connection managed by the LAN gateway (Cisco 1921).
The LAN gateway performs NAT and there was a dedicate nat rule for the host i wanted to reach through VPN.
I couldn't connect to the hos...
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...