cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
903
Views
0
Helpful
5
Replies

C1000 Connectivity Issue

bcramer04
Level 1
Level 1

I have a Cisco C1000 that is passing traffic fine but it drops the connection to manage the switch and it stops pinging for a while. When it isn't pinging I can still get to the Cisco 3560CX switch behind it. The C1000 is on VLAN 1 with 172.31.244.2 and the C3560CX is on IP Address 172.31.244.3. The gigabit link is not going down on the C1000. 

C1000:

interface Vlan1
ip address 172.31.244.2 255.255.255.0
!
ip default-gateway 172.31.244.1

interface GigabitEthernet1/0/16
description HXXX
switchport mode access
spanning-tree bpdufilter enable

3560CX:

interface Vlan1
ip address 172.31.244.3 255.255.255.0
!
ip default-gateway 172.31.244.1

interface GigabitEthernet1/0/13
description MXXXX
switchport mode access
spanning-tree bpdufilter enable

 

5 Replies 5

Hi

 If you ping both switch one stop responding and the other not, even though the 3560 is behind the 1000 ?

 When the ping fails did you check the logs?  or CPU?

 Switch is able to use data plance and control plane and sometimes  problem on the control plance does not cause problem on the data place.

 I would like to see the CPU usage when ping is failing.

Hello,

Yes, the only switch that stops pinging is the C1000 which is the main switch. The 3560 is on Gigabit port 1/0/15 of the C1000. 

show logging doesn't show anything currently except 4 of these entries:

May 15 17:47:52.171: %SYS-5-CONFIG_I: Configured from console by vty

I don't understand the date in the log above. When I do show clock it shows the correct time. 

XXX1_C1000# show clock
10:52:33.306 PDT Mon May 15 2023
XXX1_C1000#

I'm not onsite so I don't know that I could pull up the CPU usage when this is happening. 

 Check the CPU when you notice that the ping is failing. Of course you , you need to have console connection while doing this

show proc cpu

If cpu hits 100% or closer, the device can stop responding ping.  that could be one explanation.

 

Would that show up in show proc cpu history? I don't see anything above 20%. 

If the problem of stop responding is due CPU spike then yes, the command would show it. But if not, then might be something else. 

 You can try upgrade the device just in case. 

Review Cisco Networking for a $25 gift card