Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1120
Views
0
Helpful
5
Replies

Cisco 6500 interface card issues

almazmazitov
Level 1
Level 1

‎09-04-2013 01:48 AM - edited ‎03-07-2019 03:17 PM

Good day,

In our campus enviroment we have Cisco 6506 VSS Sup 2T as a core switch.

Each of our Cisco 6506 switches contain:

1) 6904-40G with 4xFourX adapter

2) empty

3) 6848-sfp

4) empty

5) Sup 2T

6) empty

Sometimes we had a problem: on all an odd or an even interfaces, interface state become "notconnect" in the interface card 6848-sfp.

On the other side there is access switches 2960, we see the blocking issues it is UDLD err-disable.

Sh/noSH didn't help.

We made some test to check connectivity, made a blocked interface in the 6500 as L3 interface and from the other side put 2960 blocked interface to the access mode and create an SVI on the 2960, to ping and check L3 connectivity between them. There was not any replies from each of side. But interfaces counters increments while we pinging. The only way to return interfaces to the normal state is reload an interface card.

Somebody faced with this problem? Any ideas about a cause?

Best regards,

Almaz

Labels:
0 Helpful
5 Replies 5

Partha Dasgupta
Cisco Employee
Cisco Employee

‎09-04-2013 04:01 AM

Hi,

Do we see any error logs in 6500 ? Please provide the same

Also provide the output of

- show diagnostic result mod 3 detail

-  show log from the module using

     -remote login mod 3

           -show log

Regards

Partha

0 Helpful

almazmazitov
Level 1
Level 1
In response to Partha Dasgupta

‎09-04-2013 04:36 AM

Thx for you reply,

Outputs is attached.

Best regards,

15366839-outputs(when blocked).txt.zip
0 Helpful

almazmazitov
Level 1
Level 1
In response to almazmazitov

‎09-04-2013 12:19 PM

          Could anybody describe the cause of the problem below? 

      

16:36:1010.240.0.128Critical10.240.0.12816714: MSK: Bad refcount in datagram_done, ptr=F88A38C, count=0SYS-SW1_DFC1-2-BADSHARE
16:36:1010.240.0.128Debug10.240.0.12816723: -Traceback= 8F5DDD4z 90AD9B8z 94155F8z 942326Cz 9423974z 9423AC4z 9415DA8z 94AFF28z 93CFE3Cz 93CFE3Cz 94AFFD8z 94B78B4z 94B4F2Cz
16:36:1010.240.0.128Critical10.240.0.12816722: MSK: Bad refcount in datagram_done, ptr=FB5AF5C, count=0SYS-SW1_DFC1-2-BADSHARE
16:36:1010.240.0.128Debug10.240.0.12816721: -Traceback= 8F5DDD4z 90AD9B8z 94155F8z 942326Cz 9423974z 9423AC4z 9415DA8z 94AFF28z 93CFE3Cz 93CFE3Cz 94AFFD8z 94B78B4z 94B4F2Cz
16:36:1010.240.0.128Critical10.240.0.12816724: MSK: Bad refcount in datagram_done, ptr=FBA7CCC, count=0SYS-SW1_DFC1-2-BADSHARE
16:36:1010.240.0.128Critical10.240.0.12816718: MSK: Bad refcount in datagram_done, ptr=FB81DDC, count=0SYS-SW1_DFC1-2-BADSHARE
16:36:1010.240.0.128Critical10.240.0.12816716: MSK: Bad refcount in datagram_done, ptr=FB3EFF0, count=0SYS-SW1_DFC1-2-BADSHARE
16:36:1010.240.0.128Debug10.240.0.12816715: -Traceback= 8F5DDD4z 90AD9B8z 94155F8z 942326Cz 9423974z 9423AC4z 9415DA8z 94AFF28z 93CFE3Cz 93CFE3Cz 94AFFD8z 94B6C08z 94B4F2Cz
16:36:0910.240.0.128Error10.240.0.12816712: MSK: Received an IPC message from unknown slot 35XDR-3-RX_UNKNOWN_PEER
16:36:0910.240.0.128Error10.240.0.12816711: -Traceback= 46CC708z 4CB0CB8z 5E5F42Cz 5E5F470z 5E5F7E8z 5E5FE20z 5E60418z 5E60B9Cz 4C965ECz 4C96A74z 4C9A738z 4C9AB24z 4C863D8z 4C9490Cz 804EDD4z 804AAACz
16:36:0910.240.0.128Error10.240.0.12816713: -Traceback= 46CC708z 4CB0CB8z 5E5F42Cz 5E5F470z 5E5F7E8z 5E5FE20z 5E60418z 5E60B9Cz 4C965ECz 4C96A74z 4C9A738z 4C9AB24z 4C863D8z 4C9490Cz 804EDD4z 804AAACz
16:36:0910.240.0.128Error10.240.0.12816710: MSK: Received an IPC message from unknown slot 35XDR-3-RX_UNKNOWN_PEER
16:36:0810.240.0.128Error10.240.0.12816709: -Traceback= 46CC708z 4CB0CB8z 5E5F42Cz 5E5F470z 5E5F7E8z 5E5FE20z 5E60418z 5E60B9Cz 4C965ECz 4C96A74z 4C9A738z 4C9AB24z 4C863D8z 4C9490Cz 804EDD4z 804AAACz
16:36:0810.240.0.128Error10.240.0.12816704: MSK: Received an IPC message from unknown slot 35XDR-3-RX_UNKNOWN_PEER
16:36:0810.240.0.128Error10.240.0.12816707: -Traceback= 46CC708z 4CB0CB8z 5E5F42Cz 5E5F470z 5E5F7E8z 5E5FE20z 5E60418z 5E60B9Cz 4C965ECz 4C96A74z 4C9A738z 4C9AB24z 4C863D8z 4C9490Cz 804EDD4z 804AAACz
16:36:0810.240.0.128Error10.240.0.12816708: MSK: Received an IPC message from unknown slot 35XDR-3-RX_UNKNOWN_PEER
16:36:0810.240.0.128Error10.240.0.12816706: MSK: Received an IPC message from unknown slot 35XDR-3-RX_UNKNOWN_PEER
16:36:0810.240.0.128Error10.240.0.12816705: -Traceback= 46CC708z 4CB0CB8z 5E5F42Cz 5E5F470z 5E5F7E8z 5E5FE20z 5E60418z 5E60B9Cz 4C965ECz 4C96A74z 4C9A738z 4C9AB24z 4C863D8z 4C9490Cz 804EDD4z 804AAACz
16:36:0810.240.0.128Error10.240.0.12816703: -Traceback= 46CC708z 4CB0CB8z 5E5F42Cz 5E5F470z 5E5F7E8z 5E5FE20z 5E60418z 5E60B9Cz 4C965ECz 4C96A74z 4C9A738z 4C9AB24z 4C863D8z 4C9490Cz 804EDD4z 804AAACz
16:36:0810.240.0.128Error10.240.0.12816701: -Traceback= 46CC708z 4CB0CB8z 5E5F42Cz 5E5F470z 5E5F7E8z 5E5FE20z 5E60418z 5E60B9Cz 4C965ECz 4C96A74z 4C9A738z 4C9AB24z 4C863D8z 4C9490Cz 804EDD4z 804AAACz
16:36:0810.240.0.128Error10.240.0.12816699: -Traceback= 46CC708z 4CB0CB8z 5E5F42Cz 5E5F470z 5E5F7E8z 5E5FE20z 5E60418z 5E60B9Cz 4C965ECz 4C96A74z 4C9A738z 4C9AB24z 4C863D8z 4C9490Cz 804EDD4z 804AAACz
16:36:0810.240.0.128Error10.240.0.12816702: MSK: Received an IPC message from unknown slot 35XDR-3-RX_UNKNOWN_PEER
16:36:0810.240.0.128Error10.240.0.12816698: MSK: Received an IPC message from unknown slot 35XDR-3-RX_UNKNOWN_PEER
16:36:0810.240.0.128Error10.240.0.12816700: MSK: Received an IPC message from unknown slot 35XDR-3-RX_UNKNOWN_PEER
16:36:0810.240.0.128Error10.240.0.12816697: -Traceback= 46CC708z 4CB0CB8z 5E5F42Cz 5E5F470z 5E5F7E8z 5E5FE20z 5E60418z 5E60B9Cz 4C965ECz 4C96A74z 4C9A738z 4C9AB24z 4C863D8z 4C9490Cz 804EDD4z 804AAACz
16:36:0810.240.0.128Error10.240.0.12816695: -Traceback= 46CC708z 4CB0CB8z 5E5F42Cz 5E5F470z 5E5F7E8z 5E5FE20z 5E60418z 5E60B9Cz 4C965ECz 4C96A74z 4C9A738z 4C9AB24z 4C863D8z 4C9490Cz 804EDD4z 804AAACz
16:36:0810.240.0.128Error10.240.0.12816696: MSK: Received an IPC message from unknown slot 35XDR-3-RX_UNKNOWN_PEER
16:36:0810.240.0.128Error10.240.0.12816694: MSK: Received an IPC message from unknown slot 35XDR-3-RX_UNKNOWN_PEER
16:36:0710.240.0.128Error10.240.0.12816689: -Traceback= 46CC708z 4CB0CB8z 5E5F42Cz 5E5F470z 5E5F7E8z 5E5FE20z 5E60418z 5E60B9Cz 4C965ECz 4C96A74z 4C9A738z 4C9AB24z 4C863D8z 4C9490Cz 804EDD4z 804AAACz
16:36:0710.240.0.128Error10.240.0.12816693: -Traceback= 46CC708z 4CB0CB8z 5E5F42Cz 5E5F470z 5E5F7E8z 5E5FE20z 5E60418z 5E60B9Cz 4C965ECz 4C96A74z 4C9A738z 4C9AB24z 4C863D8z 4C9490Cz 804EDD4z 804AAACz
16:36:0710.240.0.128Error10.240.0.12816688: MSK: Received an IPC message from unknown slot 35XDR-3-RX_UNKNOWN_PEER
16:36:0710.240.0.128Error10.240.0.12816690: MSK: Received an IPC message from unknown slot 35XDR-3-RX_UNKNOWN_PEER
16:36:0710.240.0.128Error10.240.0.12816687: -Traceback= 46CC708z 4CB0CB8z 5E5F42Cz 5E5F470z 5E5F7E8z 5E5FE20z 5E60418z 5E60B9Cz 4C965ECz 4C96A74z 4C9A738z 4C9AB24z 4C863D8z 4C9490Cz 804EDD4z 804AAACz
16:36:0710.240.0.128Error10.240.0.12816686: MSK: Received an IPC message from unknown slot 35XDR-3-RX_UNKNOWN_PEER
16:36:0710.240.0.128Error10.240.0.12816683: -Traceback= 46CC708z 4CB0CB8z 5E5F42Cz 5E5F470z 5E5F7E8z 5E5FE20z 5E60418z 5E60B9Cz 4C965ECz 4C96A74z 4C9A738z 4C9AB24z 4C863D8z 4C9490Cz 804EDD4z 804AAACz
16:36:0710.240.0.128Error10.240.0.12816684: MSK: Received an IPC message from unknown slot 35XDR-3-RX_UNKNOWN_PEER
16:36:0710.240.0.128Error10.240.0.12816685: -Traceback= 46CC708z 4CB0CB8z 5E5F42Cz 5E5F470z 5E5F7E8z 5E5FE20z 5E60418z 5E60B9Cz 4C965ECz 4C96A74z 4C9A738z 4C9AB24z 4C863D8z 4C9490Cz 804EDD4z 804AAACz
16:36:0710.240.0.128Error10.240.0.12816680: .MSK: Te2/1/20: Link downVSLP-SW2_STBY-3-VSLP_LMP_FAIL_REASON
16:36:0610.240.0.128Informational10.240.0.12816679: MSK: Message not sent to slot 33/0 (33) because of IPC error timeout. Disabling linecard. (Expected during linecard OIR or system reloads)XDR-6-XDRIPCNOTIFY
16:36:0410.240.0.128Informational10.240.0.12816675: MSK: DualActive: DUAL ACTIVE CAPAILITY LOSTHA_EM-6-LOG
16:36:0410.240.0.128Error10.240.0.12816672: -Traceback= 5873DECz 5874D8Cz 5870940z 5872B38z 8E6F9A8z 5877788z 5BDB1E4z 5BDBD04z 5BDAF08z 5C17B10z 5C17C60z 5C1C124z 5C0E504z 5C1F4D4z 5C22210z 501E280z
16:36:0410.240.0.128Error10.240.0.12816673: MSK: Failed to send cstate message to standby for GigabitEthernet2/3/18, rc=6NETWORK_RF_API-3-FAILSENDMSGTOSTDBY
16:36:0410.240.0.128Error10.240.0.12816674: -Traceback= 64FD060z 64FE8A0z 4805314z 4802644z 501E280z 5017B34z
16:36:0410.240.0.128Error10.240.0.12816671: MSK: Checkpointing message transmission failure (queue flush)CHKPT-3-TRANSMIT_FAILED
16:33:5410.240.0.128Informational10.240.0.12816652: MSK: list shahidy_in denied udp 192.168.103.251(138) -> 192.168.103.255(138), 1 packetSEC-6-IPACCESSLOGP
0 Helpful

Partha Dasgupta
Cisco Employee
Cisco Employee
In response to almazmazitov

‎09-04-2013 10:36 PM

Hi,

As per the logs provided it looks there was some VSS issue since we are seeing the logs for blocked interface from both switch 1 and  switch 2  ie not specific to module on 1 switch. I would like to know the following

1. What is the version of IOS running in 6500?

2. Where are the above error message collected from ? Is it from 6500 or 2960 ? I believe these error messages appeared during the time issue happened?

3. Please provide the output of show diagnostic result mod 5 detail ( Active superisor Switch 1 ) ?

Regards

Partha

0 Helpful

almazmazitov
Level 1
Level 1
In response to Partha Dasgupta

‎09-06-2013 02:20 AM

Hi,

1) 15.0(1)SY4

2) From the 6500, Yes, you are right.

3) attached

Best regards,

15366999-diag.txt.zip
0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents
Review Cisco Networking products for a $25 gift card