6500 loses connectivity to 4500

[baselzind]

i have 2 6500 with supervisor WS-SUP720 version  12.2(17r)SX5 and a 4500 with supervisor WS-X4516-10GE version  12.2(31)SGA8 connected to both my 6500 cores. my 4500 have an tengig interface to both my 6500 cores , however every hour it loses connectivity for 30 seconds to 1 minute without seeing any interface down on my cores and without any logs on both 4500 and 6500 and barely 1 crc error. anyone can help please

[Flavio Miranda]

CPU and memory on both side?

[baselzind]

what are the commands for those 2

[Flavio Miranda]

show proc cpu history

[MHM Cisco World]

show spanning tree in both 6500 and 4500

[baselzind]

uplinks are on ten 6/1 on both 6500. The show spanning tree vlan x output on both cores doesn't change during the issue

Spanning tree enabled protocol ieee
Root ID Priority 0
Address x
Cost 3
Port 1665 (Port-channel1)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec

Bridge ID Priority 4096
Address x
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300

Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Gi1/1 Desg FWD 4 128.1 P2p
Gi1/2 Desg FWD 4 128.2 P2p
Gi1/3 Desg FWD 4 128.3 P2p
Gi1/5 Desg FWD 4 128.5 P2p
Gi1/6 Desg FWD 4 128.6 P2p
Gi1/7 Desg FWD 4 128.7 P2p
Gi1/8 Desg FWD 4 128.8 P2p
Gi1/10 Desg FWD 4 128.10 P2p
Gi1/11 Desg FWD 4 128.11 P2p
Gi1/12 Desg FWD 4 128.12 P2p
Gi1/13 Desg FWD 4 128.13 P2p
Te6/1 Altn BLK 2 128.641 P2p
Te6/2 Altn BLK 2 128.642 P2p
Gi9/1 Desg FWD 4 128.1025 P2p
Gi9/2 Desg FWD 4 128.1026 P2p
Gi9/3 Desg FWD 4 128.1027 P2p
Gi9/4 Desg FWD 4 128.1028 P2p
Gi9/5 Desg FWD 4 128.1029 P2p
Gi9/8 Desg FWD 4 128.1032 P2p
Gi9/9 Desg FWD 4 128.1033 P2p
Gi9/10 Desg FWD 4 128.1034 P2p
Po1 Root FWD 3 128.1665 P2p

Spanning tree enabled protocol ieee
Root ID Priority 0
Address x
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec

Bridge ID Priority 0
Address x
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300

Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Gi1/2 Desg FWD 4 128.2 P2p
Gi1/3 Desg FWD 4 128.3 P2p
Gi1/4 Desg FWD 4 128.4 P2p
Gi1/6 Desg FWD 4 128.6 P2p
Gi1/7 Desg FWD 4 128.7 P2p
Gi1/8 Desg FWD 4 128.8 P2p
Gi1/9 Desg FWD 4 128.9 P2p
Gi1/10 Desg FWD 4 128.10 P2p
Gi1/12 Desg FWD 4 128.12 P2p
Gi1/14 Desg FWD 4 128.14 P2p
Te6/1 Desg FWD 2 128.641 P2p
Te6/2 Desg FWD 2 128.642 P2p
Gi7/46 Desg FWD 4 128.814 P2p
Gi9/1 Desg FWD 4 128.1025 P2p
Gi9/2 Desg FWD 4 128.1026 P2p
Gi9/3 Desg FWD 4 128.1027 P2p
Gi9/4 Desg FWD 4 128.1028 P2p
Gi9/5 Desg FWD 4 128.1029 P2p
Gi9/6 Desg FWD 4 128.1030 P2p
Gi9/7 Desg FWD 4 128.1031 P2p
Gi9/8 Desg FWD 4 128.1032 P2p
Po1 Desg FWD 3 128.1665 P2p
Po2 Desg FWD 3 128.1666 P2p

[MHM Cisco World]

Hi
two 6500 running VSS ?

[baselzind]

no they aren't just hsrp

[Leo Laohoo]

---

@baselzind wrote:

without seeing any interface down on my cores

---

Link state logging for the Catalyst 4k and 6k are, by default, disabled.  So when a link goes down/up, it will not show up in the logs.

Post the complete output to the following commands: 

1. Catalyst 4k:  sh interface <PHYSICAL PORT> controll
2. Catalyst 6k:  sh counter interface <PHYSICAL PORT>

[baselzind]

how can i enable linkstate to show in logs?

[Leo Laohoo]

---

@baselzind wrote:

how can i enable linkstate to show in logs?

---

conf t
 interface <PORT>
 logging event link-state
end

[marce1000]

- Check logs on both devices, when that happens, preferably use a syslog server on both, to be able to correlate messaging from both boxes and better determining the source of the problem.

 M.

[baselzind]

problem is that show log on both switches doesn't show any new messages. could a bad fiber cable cause packets drops every now and then?

[marce1000]

- Keep investing in continious log monitoring through syslog server.M.

[baselzind]

before this problem started there was a spanning tree root guard on one of the interfaces that was getting blocked and unblocked repeatedly which i fixed by removing the command. afterward the dysconnectivity started however now after couple of days the problem stopped so I think im good for now.