Ports on my switch are not working

daniel espinal · ‎01-30-2013

Hi folks,

I have a "C3560 Software (C3560-IPBASEK9-M), Version 12.2(50)SE3" Some of the ports are not working.

here is a show ip in brief of ports 22, 23 and 24, I left out all the other because I think they are irrelevant. I left in vlans and port channels.

Interface IP-Address OK? Method Status Protocol

Vlan1 10.0.1.2 YES NVRAM up up

Vlan10 10.0.10.1 YES NVRAM up up

Vlan20 10.0.20.1 YES NVRAM up up

Vlan30 10.0.30.1 YES NVRAM up up

Vlan40 10.0.40.1 YES NVRAM up up

GigabitEthernet0/22 unassigned YES unset up up

GigabitEthernet0/23 unassigned YES unset down down

GigabitEthernet0/24 unassigned YES unset down down

Port-channel1 unassigned YES unset up up

Port-channel2 unassigned YES unset up up

Port-channel3 unassigned YES unset down down

As you can see port 22 is up and up but 23 and 24 are down and down.

here is a show run of those ports

interface GigabitEthernet0/22

description Port Ready for IP Phone or PC

switchport access vlan 10

switchport trunk allowed vlan 20

switchport mode access

switchport voice vlan 20

mls qos trust device cisco-phone

spanning-tree portfast

spanning-tree bpduguard enable

!

interface GigabitEthernet0/23

description Port Ready for IP Phone or PC

switchport access vlan 10

switchport trunk encapsulation dot1q

switchport trunk allowed vlan 20

switchport mode access

switchport voice vlan 20

mls qos trust device cisco-phone

spanning-tree portfast

spanning-tree bpduguard enable

!

interface GigabitEthernet0/24

description Port Ready for IP Phone or PC

switchport access vlan 10

switchport trunk allowed vlan 20

switchport mode access

switchport voice vlan 20

mls qos trust device cisco-phone

spanning-tree portfast

spanning-tree bpduguard enable

here are the spanning tree commands being used:

spanning-tree mode rapid-pvst

spanning-tree etherchannel guard misconfig

spanning-tree extend system-id

spanning-tree vlan 1,10,20,30,40 priority 8192

I Issued a no shutdown command on both ports and still nothing showed up. I had a printer plugged into port 23. One day last week it just stopped working. The only way I could get the printer back up is to plug the printer into another switch since I had no spare ports on this switch that worked.

Any ideas as to why this port stopped workig all of a sudden? and is the show ip int brief the right command to check port statuses on switches?

kcnajaf · ‎01-30-2013

Hi Daniel,

This could be a cable or speed/duplex problem as well. Could you try connecting a laptop to same port using a different cable and see if the lights comes up.

Also it may worth setting speed and duplex manually based on what is the device speed and duplex connected to that port.

Regards

Najaf

Please rate when applicable or helpful !!!

Leo Laohoo · ‎01-30-2013

So the problem ports are 23 and 24?

If so, please post the output to the command "sh interface Gi0/23" and "sh interface Gi0/24".

Next, run a TDR on each port.

daniel espinal · ‎02-01-2013

Wow I've never even heard of this feature. I love these forums.

As for the switch it just randomly started working. I only have access to it certain days of the week so I don't know what could have changed from the last time I was onsite. I did grab the show int for the mentioned ports. I was using a validator and the validator detected voltage on port 24. I had to unplug it and plug it back in. I think maybe the POE controller chip (if there is one) is going bad. We have been having a ton of electrical issues. One being when I plug my laptop into a socket I can feel the current on the lid of my laptop. That tells me there are grounding problems at the electrical pannel. I just don't know how that would effect the network. Could backfeeding voltage cause POE issues?

here are the show ints

show interfaces gigabitEthernet 0/23

GigabitEthernet0/23 is down, line protocol is down (notconnect)

Hardware is Gigabit Ethernet, address is 0026.5111.6717 (bia 0026.5111.6717)

Description: Port Ready for IP Phone or PC

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

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

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Auto-duplex, Auto-speed, media type is 10/100/1000BaseTX

input flow-control is off, output flow-control is unsupported

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

Last input never, output 12w1d, output hang never

Last clearing of "show interface" counters never

Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/0 (size/max)

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

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

2805175 packets input, 371365165 bytes, 0 no buffer

Received 188519 broadcasts (151047 multicasts)

0 runts, 0 giants, 0 throttles

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

0 watchdog, 151047 multicast, 0 pause input

0 input packets with dribble condition detected

17981568 packets output, 7883010823 bytes, 0 underruns

0 output errors, 0 collisions, 1 interface resets

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier, 0 PAUSE output

0 output buffer failures, 0 output buffers swapped out

GigabitEthernet0/24 is down, line protocol is down (notconnect)

Hardware is Gigabit Ethernet, address is 0026.5111.6718 (bia 0026.5111.6718)

Description: Port Ready for IP Phone or PC

MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,

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

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Auto-duplex, Auto-speed, media type is 10/100/1000BaseTX

input flow-control is off, output flow-control is unsupported

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

Last input never, output never, output hang never

Last clearing of "show interface" counters never

Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/0 (size/max)

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

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

0 packets input, 0 bytes, 0 no buffer

Received 0 broadcasts (0 multicasts)

0 runts, 0 giants, 0 throttles

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

0 watchdog, 0 multicast, 0 pause input

0 input packets with dribble condition detected

0 packets output, 0 bytes, 0 underruns

0 output errors, 0 collisions, 1 interface resets

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier, 0 PAUSE output

0 output buffer failures, 0 output buffers swapped out

Leo Laohoo · ‎02-02-2013

Could backfeeding voltage cause POE issues?

Please post the output to the command "sh post".

Your output doesn't really contain much. Is there anything connected to Gi0/23? It looks like the last time the port was "used" was around 12 weeks ago.

daniel espinal · ‎02-02-2013

That's weird. there was a printer on port 23 less than 2 weeks ago. Like I said the switch seems to be working now. If an issue pops up I'll definitely run through the check list.

I really apreciate all the help.

tobyarnett · ‎02-02-2013

There could be an issue with the POE. You could try to connect a laptop to the port on outlet power to bypass the POE on the switch. This would help you test.

You can also use the command "show power inline" this will help you validate that sufficient power is being applied to the ports you need. I take it you have already done a show log but if not do that. You may need to increase your logging level depending on your current settings.

Other things to check are cable length make sure your not exceeding your 100 meters.

Toby

Sent from Cisco Technical Support Android App

-Toby

Please don't forget to rate any helpful post.

_____________________________________
There are no great limits to growth because there are no limits of human intelligence, imagination, and wonder.
- Ronald Reagan