02-28-2011 01:11 PM - edited 03-06-2019 03:48 PM
Hello All,
I have a very simple and a weird issue. I have a 2960 which I am using as a unmanageable switch. So a month back I assigned port # 5 on the switch to one of the windows server. Everything was working fine until all of sudden it stopped working. The peculiar thing is that I plugged in to the port# 6 on the same switch and it worked without any issue until after a while, it also failed again.
Now if I use the #7 on the same switch it works but it will not work on port#5.While I was troubleshooting I did shut and no shut, that fixed the issue on the port #6. But when I try to do the same on port#5, I am even unable to ping to the default gateway. One more thing I also did a default command on the port#5 and it seems like it is still not working . Finally the physical connection seems to be fine as well
Issue : I cant ping the default gateway from port 5#
Please see below the running config
version 12.2
no service pad
service timestamps debug uptime
service timestamps log uptime
service password-encryption
!
hostname XXXXXXX
!
enable secret 5 $1$4.Qt$4fzaWc/R3WvAHYJSyYb3p/
enable password 7 0210505C0F1E1D62657D28
!
no aaa new-model
system mtu routing 1500
ip subnet-zero
!
!
!
!
no file verify auto
spanning-tree mode pvst
spanning-tree extend system-id
!
vlan internal allocation policy ascending
!
interface GigabitEthernet0/1
description ***XXXXXX***
!
interface GigabitEthernet0/2
description ****XXXXXXXXX***
!
interface GigabitEthernet0/3
description ****XXXXXXXXXXX***
!
interface GigabitEthernet0/4
description ***XXXXXXXXX***
!
interface GigabitEthernet0/5
!
interface GigabitEthernet0/6
description ***XXXXXXXXX***
!
interface GigabitEthernet0/7
shutdown
!
interface GigabitEthernet0/8
shutdown
!
interface Vlan1
no ip address
no ip route-cache
!
ip http server
!
control-plane
!
!
line con 0
password XXXXXXXXXXXXXXXXXXXXXXXX
login
line vty 0 4
password XXXXXXXXXXXXXXXXXXXXX
login
line vty 5 15
password XXXXXXXXXXXXXXXXX
login
!
end
Thanks in advance
Soofi
02-28-2011 01:33 PM
Everything was working fine until all of sudden it stopped working. The peculiar thing is that I plugged in to the port# 6 on the same switch and it worked without any issue until after a while, it also failed again.
The config you've posted is not enough. Can you post the following commands:
1. sh logs;
2. sh version;
3. sh interface status error
I am suspecting the port may have gone into error-disable.
03-01-2011 08:11 AM
sh version
Cisco IOS Software, C2960 Software (C2960-LANBASE-M), Version 12.2(35)SE5, RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2007 by Cisco Systems, Inc.
Compiled Thu 19-Jul-07 20:06 by nachen
Image text-base: 0x00003000, data-base: 0x00D40000
ROM: Bootstrap program is C2960 boot loader
BOOTLDR: C2960 Boot Loader (C2960-HBOOT-M) Version 12.2(35r)SE2, RELEASE SOFTWARE (fc1)
RICHFORTR uptime is 1 year, 13 weeks, 6 days, 1 hour, 18 minutes
System returned to ROM by power-on
System image file is "flash:c2960-lanbase-mz.122-35.SE5/c2960-lanbase-mz.122-35.SE5.bin"
cisco WS-C2960G-8TC-L (PowerPC405) processor (revision A0) with 61440K/4088K bytes of memory.
Processor board ID FOC1212U4MB
Last reset from power-on
1 Virtual Ethernet interface
8 Gigabit Ethernet interfaces
The password-recovery mechanism is enabled.
64K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address : 00:21:1B:43:81:80
Motherboard assembly number : 73-10613-08
Power supply part number : 341-0208-01
Motherboard serial number : FOC12123DXJ
Power supply serial number : LIT12090BZC
Model revision number : A0
Motherboard revision number : B0
Model number : WS-C2960G-8TC-L
System serial number : FOC1212U4MB
Top Assembly Part Number : 800-28133-01
Top Assembly Revision Number : D0
Version ID : V01
CLEI Code Number : COM7S00ARA
Hardware Board Revision Number : 0x01
Switch Ports Model SW Version SW Image
------ ----- ----- ---------- ----------
* 1 8 WS-C2960G-8TC-L 12.2(35)SE5 C2960-LANBASE-M
Configuration register is 0xF
-------------------------------------------------------------------------------------------------------- ----------------------------
sh log
Syslog logging: enabled (0 messages dropped, 1 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)
Console logging: level debugging, 490 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 490 messages logged, xml disabled,
filtering disabled
Exception Logging: size (4096 bytes)
Count and timestamp logging messages: disabled
File logging: disabled
Trap logging: level informational, 493 message lines logged
Log Buffer (4096 bytes):
LINK-5-CHANGED: Interface GigabitEthernet0/5, changed state to administratively down
1y13w: %SYS-5-CONFIG_I: Configured from console by console
1y13w: %LINK-5-CHANGED: Interface GigabitEthernet0/6, changed state to administratively down
1y13w: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/6, changed state to down
1y13w: %LINK-3-UPDOWN: Interface GigabitEthernet0/7, changed state to down
1y13w: %LINK-3-UPDOWN: Interface GigabitEthernet0/7, changed state to up
1y13w: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/7, changed state to up
1y13w: %SYS-5-CONFIG_I: Configured from console by console
1y13w: %LINK-5-CHANGED: Interface GigabitEthernet0/7, changed state to administratively down
1y13w: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/7, changed state to down
1y13w: %SYS-5-CONFIG_I: Configured from console by console
1y13w: %CLEAR-5-COUNTERS: Clear counter on interface GigabitEthernet0/5 by console
1y13w: %LINK-3-UPDOWN: Interface GigabitEthernet0/5, changed state to down
1y13w: %LINK-3-UPDOWN: Interface GigabitEthernet0/5, changed state to up
1y13w: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/5, changed state to up
1y13w: %SYS-5-CONFIG_I: Configured from console by console
1y13w: %SYS-5-CONFIG_I: Configured from console by console
1y13w: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/5, changed state to down
1y13w: %LINK-3-UPDOWN: Interface GigabitEthernet0/5, changed state to down
1y13w: %SYS-5-CONFIG_I: Configured from console by console
1y13w: %LINK-3-UPDOWN: Interface GigabitEthernet0/5, changed state to up
1y13w: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/5, changed state to up
1y13w: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/5, changed state to down
1y13w: %LINK-3-UPDOWN: Interface GigabitEthernet0/5, changed state to down
1y13w: %LINK-3-UPDOWN: Interface GigabitEthernet0/5, changed state to up
1y13w: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/5, changed state to up
1y13w: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/5, changed state to down
1y13w: %LINK-3-UPDOWN: Interface GigabitEthernet0/5, changed state to down
1y13w: %LINK-3-UPDOWN: Interface GigabitEthernet0/5, changed state to up
1y13w: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/5, changed state to up
1y13w: %SYS-5-CONFIG_I: Configured from console by console
1y13w: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/5, changed state to down
1y13w: %LINK-3-UPDOWN: Interface GigabitEthernet0/5, changed state to down
1y13w: %LINK-3-UPDOWN: Interface GigabitEthernet0/5, changed state to up
1y13w: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/5, changed state to up
1y13w: %SYS-5-CONFIG_I: Configured from console by console
1y13w: %LINK-5-CHANGED: Interface GigabitEthernet0/5, changed state to administratively down
1y13w: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/5, changed state to down
1y13w: %SYS-5-CONFIG_I: Configured from console by console
1y13w: %LINK-3-UPDOWN: Interface GigabitEthernet0/5, changed state to down
1y13w: %LINK-3-UPDOWN: Interface GigabitEthernet0/5, changed state to up
1y13w: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/5, changed state to up
1y13w: %SYS-5-CONFIG_I: Configured from console by console
1y13w: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/5, changed state to down
1y13w: %LINK-3-UPDOWN: Interface GigabitEthernet0/5, changed state to down
1y13w: %LINK-3-UPDOWN: Interface GigabitEthernet0/5, changed state to up
1y13w: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/5, changed state to up
1y13w: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/5, changed state to down
1y13w: %LINK-3-UPDOWN: Interface GigabitEthernet0/5, changed state to down
1y13w: %LINK-3-UPDOWN: Interface GigabitEthernet0/5, changed state to up
1y13w: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/5, changed state to up
--------------------------------------------------------------------------------------------------------------------------------------------------
The sh interface status error is not a valid command
Thanks for the help
Soofi
02-28-2011 01:55 PM
please also post the results of 'sh errdisable recovery'
03-01-2011 08:26 AM
'sh errdisable recovery' didnt work it said invalid command. So I tried " sh interface status err-disabled " and it came out blank.
03-01-2011 09:15 AM
Well you can start by checking the status of the ports you mentioned by running sh int gigabitethernet "portumber"
You can also try enabling error recovery by running, please also make sure your in "conf t" before running the commands
errdisable recovery interval 300
errdisable recovery cause all
then run the sh erdisable recovery and you should see a result such as:
ErrDisable Reason Timer Status
----------------- --------------
udld Enabled
bpduguard Enabled
security-violatio Enabled
channel-misconfig Enabled
pagp-flap Enabled
dtp-flap Enabled
link-flap Enabled
l2ptguard Enabled
psecure-violation Enabled
gbic-invalid Enabled
dhcp-rate-limit Enabled
mac-limit Enabled
unicast-flood Enabled
arp-inspection Enabled
Timer interval: 300 seconds
Interfaces that will be enabled at the next timeout:
Interface Errdisable reason Time left(sec)
--------- --------------------- --------------
Fa2/4 bpduguard 273
Also sounds like it might be a possible link flap issue.
also might want to check your link speed settings on the nicin your server,...
Hope this helps...
03-01-2011 12:03 PM
Thanks for input.
I tried the steps you have suggested, please see below for the output. Also, as stated earlier the port in question is not connected to a windows server. But it is been conencted to a linksys home router 4 port + 1 port ( WAN ) .
Also, The other test I did was manually assigned a static IP to a laptop and tried pining the gateway. It still didnt work, So I am speculating that the issue is with the 2960 swicth and not on the other side.
GigabitEthernet0/5 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 0021.1b43.8185 (bia 0021.1b43.8185)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s, 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 00:00:00, output hang never
Last clearing of "show interface" counters 3d18h
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
353144 packets input, 22783502 bytes, 0 no buffer
Received 353144 broadcasts (0 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 8924 multicast, 0 pause input
0 input packets with dribble condition detected
219853 packets output, 16094422 bytes, 0 underruns
----------------------------------------------------------------------------
RICHFORTR#sh errdisable recovery
ErrDisable Reason Timer Status
----------------- --------------
udld Disabled
bpduguard Disabled
security-violatio Disabled
channel-misconfig Disabled
vmps Disabled
pagp-flap Disabled
dtp-flap Disabled
link-flap Disabled
psecure-violation Disabled
sfp-config-mismat Disabled
gbic-invalid Disabled
dhcp-rate-limit Disabled
unicast-flood Disabled
storm-control Disabled
arp-inspection Disabled
loopback Disabled
Timer interval: 300 seconds
Interfaces that will be enabled at the next timeout:
--------------------------------------------------------------------------------------
sh errdisable detect
ErrDisable Reason Detection status
----------------- ----------------
udld Enabled
bpduguard Enabled
security-violatio Enabled
channel-misconfig Enabled
psecure-violation Enabled
unicast-flood Enabled
vmps Enabled
loopback Enabled
unicast-flood Enabled
pagp-flap Enabled
dtp-flap Enabled
link-flap Enabled
sfp-config-mismat Enabled
gbic-invalid Enabled
dhcp-rate-limit Enabled
storm-control Enabled
arp-inspection Enabled
community-limit Enabled
invalid-policy Enabled
----------------------------------------------------------------
RICHFORTR#sh errdisable flap-values
ErrDisable Reason Flaps Time (sec)
----------------- ------ ----------
pagp-flap 3 30
dtp-flap 3 30
link-flap 5 10
Thanks,
Soofi
03-01-2011 12:47 PM
If you look at your "sh logs" interface 5 is flapping like no tomorrow. Have you checked the cable? Unfortunately, I would like to recommend you enable the TDR feature of the 2960. It's unfortunate because you are running a fairly old IOS and using the TDR will bring the line down .... but then again, the link is already flapping, so why not?
The combo commands are the following:
test cable tdr interface gi 0/5
wait for approximately 7-10 seconds and follow up with the final command of:
sh cable tdr interface gi0/5
03-01-2011 12:56 PM
Thanks Leo, for the response here is the output from the command. And yes the link was down and came back up.
sh cable tdr interface gi0/5
TDR test last run on: June 06 22:48:36
Interface Speed Local pair Pair length Remote pair Pair status
--------- ----- ---------- ------------------ ----------- --------------------
Gi0/5 100M Pair A N/A Pair A Normal
Pair B N/A Pair B Normal
Pair C 20 +/- 2 meters Pair C Short
Pair D 20 +/- 2 meters Pair D Short
03-01-2011 01:13 PM
Gi0/5 100M Pair A N/A Pair A Normal
Pair B N/A Pair B Normal
Pair C 20 +/- 2 meters Pair C Short
Pair D 20 +/- 2 meters Pair D Short
You may have just solved your issue. The cable could be faulty. Is this a single cable from the switch to the NIC? Replace it. It's terminated incorrectly in all four pairs.
03-01-2011 01:37 PM
Nope! That didnt fixed the issue . Even after replacing the cable the issue continues and I did ran same command here is the output
Interface Speed Local pair Pair length Remote pair Pair status
--------- ----- ---------- ------------------ ----------- --------------------
Gi0/5 100M Pair A N/A Pair B Normal
Pair B N/A Pair A Normal
Pair C 28 +/- 2 meters Pair D Short
Pair D 20 +/- 2 meters Pair C Short
Is this a single cable from the switch to the NIC?
No, it is connecting to a ( 5port ) linksys home router.
03-01-2011 01:52 PM
I did ran same command here is the output
Did you ran both commands or just the "show" command?
No, it is connecting to a ( 5port ) linksys home router.
So it's SWITCH < --- cable --- > Router? Is this it?03-01-2011 02:01 PM
Did you ran both commands or just the "show" command?
No, I ran both the commands.
So it's SWITCH < --- cable --- > Router? Is this it?
Yes
Also, I think the output from sh log posted on the previous thread was heading us into wrong direction. The reason I say that is because once I cleared the log buffer. and ran sh log, ( please see below the output )
sh log
Syslog logging: enabled (0 messages dropped, 1 messages rate-limited, 0 flushes,
0 overruns, xml disabled, filtering disabled)
Console logging: level debugging, 502 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 502 messages logged, xml disabled,
filtering disabled
Exception Logging: size (4096 bytes)
Count and timestamp logging messages: disabled
File logging: disabled
Trap logging: level informational, 505 message lines logged
Log Buffer (4096 bytes):
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide