What would cause the ports to go bad in these types of switches? I'm currently having problems with ports going bad in switches that are not even 2yrs old. They were purchased directly from cisco, and we let smartnet relapse so right now we don't have anything. Can some point me in the right direction on why this is happening
It is really hard to tell. It could be that you received a series of switches with hardware issues. You should never let your SmartNet expires. Talk to your Cisco sales guy. You maybe able to trade them in for newer switches for a small price.
2960 LAN Lite switches have Limited Lifetime Hardware Warranty even without Smartnet. You are entitled to receive a replacement product in 10 days.
Duration of Hardware Warranty:
As long as the original End User continues to own or use the Product. In the event of discontinuance of product manufacture, Cisco warranty support is limited to five (5) years from the announcement of discontinuance.
Check the data sheet and Cisco Warranty Finder
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2013.09.15 00:00:56 =~=~=~=~=~=~=~=~=~=~=~=
Cisco IOS Software, C2960 Software (C2960-LANLITEK9-M), Version 12.2(50)SE5, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Tue 28-Sep-10 13:44 by prod_rel_team
Image text-base: 0x00003000, data-base: 0x01200000
ROM: Bootstrap program is C2960 boot loader
BOOTLDR: C2960 Boot Loader (C2960-HBOOT-M) Version 12.2(53r)SEY3, RELEASE SOFTWARE (fc1)
SuiteD-3 uptime is 1 day, 13 hours, 8 minutes
System returned to ROM by power-on
System restarted at 03:45:43 EDT Fri Sep 13 2013
System image file is "flash:/c2960-lanlitek9-mz.122-50.SE5/c2960-lanlitek9-mz.122-50.SE5.bin"
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
--More-- compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
If you require further assistance please contact us by sending email to
cisco WS-C2960-24LC-S (PowerPC405) processor (revision K0) with 65536K bytes of memory.
Processor board ID FCQ1625Y4SR
Last reset from power-on
1 Virtual Ethernet interface
24 FastEthernet interfaces
2 Gigabit Ethernet interfaces
The password-recovery mechanism is enabled.
64K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address : 64:D8:14:BC:D6:00
Motherboard assembly number : 73-12783-05
Power supply part number : 341-0267-02
--More-- Motherboard serial number : FCQ162503WR
Power supply serial number : DCA1620J243
Model revision number : K0
Motherboard revision number : A0
Model number : WS-C2960-24LC-S
System serial number : FCQ1625Y4SR
Top Assembly Part Number : 800-33171-02
Top Assembly Revision Number : A0
Version ID : V06
CLEI Code Number : COMBX00BRD
Hardware Board Revision Number : 0x02
Switch Ports Model SW Version SW Image
------ ----- ----- ---------- ----------
* 1 26 WS-C2960-24LC-S 12.2(50)SE5 C2960-LANLITEK9-M
Configuration register is 0xF
SuiteD-3#sh interface status err
SuiteD-3#sh interface status err
Stored system POST messages:
POST: CPU MIC register Tests : Begin
POST: CPU MIC register Tests : End, Status Passed
POST: PortASIC Memory Tests : Begin
POST: PortASIC Memory Tests : End, Status Passed
POST: CPU MIC interface Loopback Tests : Begin
POST: CPU MIC interface Loopback Tests : End, Status Passed
POST: PortASIC RingLoopback Tests : Begin
POST: PortASIC RingLoopback Tests : End, Status Passed
POST: Inline Power Controller Tests : Begin
POST: Inline Power Controller Tests : End, Status Passed
POST: PortASIC CAM Subsystem Tests : Begin
POST: PortASIC CAM Subsystem Tests : End, Status Passed
--More-- POST: PortASIC Port Loopback Tests : Begin
POST: PortASIC Port Loopback Tests : End, Status Passed
I agree with Leo that this output does not show any ports on this switch as being bad. I think we need more clarification from the original poster about the ports that he is calling bad. I am wondering if he is having ports going into error disabled and is considering them as bad. If it is not this then what is it?
Thanks for noticing. I have been very busy with work, which is a good thing, but it has impacted my participation in the forum.
Well for some of you that think I'm an idiot and don't know why I've posted this. I have rebooted the system, changed ethernet cables, and tested the port again. Port didn't come up. So to eliminate the end user I plugged directly into that same port to test if it was the end user. Port still did not respond. Showing down down. Also looked at the interface, it was not administratively shut nor was it in err disable mode. That’s common sense because if the port were in error disable then the port would show orange. I'm receiving no link light and no action on the switch under that port.
So again, what could cause ports on a switch to go bad other then hardware? For being in the IT field for 7yrs you always cancel out the obvious before reaching out for any help. The Internet is your friend until you can't find what your looking for.
Well for some of you that think I'm an idiot and don't know why I've posted this
I don't think like that. I've seen a few make worst post but I don't result in someone that "low".
I'm receiving no link light and no action on the switch under that port.
Ok, what happens if you plug to a known working port? Try this. Stupid as it may sound, I've seen something like this in the past 6 months.
Plug into another port and it comes up. Tried this as well before asking this question. So sense I have explained to you that I've tested the port every way possible, and plugged the cable into another port and it works.
What would officailly make ports go bad on a switch? Other then bad hardware. Switch is not POE, did not have a power surge, and the only thing thats connected to the port is a POSI device.
What would officailly make ports go bad on a switch?
Like I said, I've seen this once before. 6 months ago.
Post the output to the command "sh interface