cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1763
Views
0
Helpful
14
Replies

Question: My fastEthernet ports shuts down by themselves

silaswulff
Level 1
Level 1

Hi,

I have a C3524-XL Switch which I'm trying to configure.

Problem is that when i plug clients into the network ports nothing happens, so i try "no shutdown", the port goes up, but then immediatly down again.

Anyone know what the problem may be? The switch have no configuration what so ever other than a custom hostname and enable secret.

Thanks

14 Replies 14

Shashank Singh
Cisco Employee
Cisco Employee

Hi,

Try configuring the following under the interface connecting the PC and see if it helps:

    int fa0/0

switchport

speed auto

duplex auto

switchport mode access

Cheers,

Shashank

Please rate this answer if you found the content useful

Hi

I tried what you suggested, it did not help unfortunately..

Any other sugggestions?

oyama.hall
Level 1
Level 1

Check your port for port-security.

You may be exceeding the maximum number of MAC addresses that are allowed to be associated with the port.

http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.1E/native/configuration/guide/port_sec.html

Cheers!

Hi

I havent tried it yet but i doubt it would help, there is no limitof MAC's seeing as i have not configured it

Should i try anyway?

sdheer
Cisco Employee
Cisco Employee

Hi Silas,

Kindly put in the " show logg " , " show run int fa x/y " and " sh int fa x/y"   commands output here .

Regards,

Swati Dheer

Show Logg:

Log Buffer (4096 bytes):
         
00:00:17: %SYS-5-RESTART: System restarted --
Cisco Internetwork Operating System Software
IOS (tm) C3500XL Software (C3500XL-C3H2S-M), Version 12.0(5.2)XU, MAINTENANCE INTERIM SOFTWARE
Copyright (c) 1986-2000 by cisco Systems, Inc.
Compiled Mon 17-Jul-00 18:29 by ayounes
00:01:31: %SYS-5-CONFIG_I: Configured from console by console
00:02:55: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to up
00:02:55: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to down
00:04:22: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to up
00:04:22: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to down
00:04:40: %SYS-5-CONFIG_I: Configured from console by console

---------------------------------------------------------------------------------------------------

Switch#show run int fa0/1
Building configuration...

Current configuration:
!
interface FastEthernet0/1
end

----------------------------------------------------------------------------------------------------

Switch#sh int fa0/1
FastEthernet0/1 is down, line protocol is down
  Hardware is Fast Ethernet, address is 0004.dd1f.91c1 (bia 0004.dd1f.91c1)
  MTU 1500 bytes, BW 0 Kbit, DLY 100 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive not set
  Auto-duplex , Auto Speed , 100BaseTX/FX
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input never, output 00:14:47, output hang never
  Last clearing of "show interface" counters never
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     1 packets input, 64 bytes
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 0 multicast
     0 input packets with dribble condition detected
     10 packets output, 1532 bytes, 0 underruns
     0 output errors, 0 collisions, 7 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out

Leo Laohoo
Hall of Fame
Hall of Fame

What is the error message presented when the ports shuts themselves?

IF there is no configuration (other than the hostname) then delete the config and reload the switch.

After the reboot can you do the command "sh post"?

There is no error message, when i plug a client in or try the no shutdown comman all i get is

00:03:03: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to up
00:03:03: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to down

and that repeats itself..

I tried restarting and "sh post" all i got back was "passed"

thanks

Hi Silas,

Try to configure the port as follwoing and see if that helps.

conf t

int fa 0/1

switchport mode access

speed 100

duplex full

Try configuring once to " duplex full " and then test with " duplex half"

Regards,

Swati

Please let me know if that helps and rate if you find it useful

Hi Silas,

Once try to connect the PC on another Switch port & then check. May be port is faulty.Otherwise check the client end NIC card or replace the lan cable or reboot the PC once. Try to above things, surely yours problem should be rectified.

Regards

SS

Please let me know if that helps and find it useful.

r-godden
Level 1
Level 1

silaswulff
Level 1
Level 1

Ok

I tried pluging in PC and rebooting switch, now the interface seems to be up..

I also have a router connected to the switch but that port continues to be down.

This issue affects two switches on all ports.

Back in 2007, I was managing a fleet of 2900/3500XL switches.  The client, without consulting the network team, decides to embark on a multi-million dollar desktop refresh.  SO here comes an initial shipment of 2k boxes of brand-new desktops and nearly half decides to fall over upon connecting to the LAN.  When the users are logged in, the ports would "flap":  It would go down/up every second (yes, every second).

Our initial suspect is that the 10/100/1000BaseTx NIC chip is incompatible to Cisco.  Strange?  Here's the reason:  The NIC chip is a newly developed chip.  But the switches are, what we'd like to call "legacy".  So there's a major incompatibility issue between the two, particularly in the area known as "jitter".

A Catalyst 3524-PWR XL switch does not work correctly with some Intel Pro/1000 MT network interface cards (NICs). This is an Intel product defect. There is no workaround. (CSCec00968)

I'm not sure if you are having similar issues with what I had before but one thing we did to test the theory was to connect the affected PCs into a newer switch like a 2940/2950/2955 or later.

Don't worry about the part of the "3524-PWR XL" as this affects the ENTIRE 3500XL range with a specific chipset (batch number).  Doesn't matter if you upgrade the IOS from "XU" to "WC17", you are still stuck.

silaswulff
Level 1
Level 1

Ok its solved

Im not actually sure what was the problem, i turned everything off, wiped config of switches and router, then configured them as people in here have been suggesting.. I reconnected everything and it worked..

Im not sure what the problem was but it is solved now thankfully :-)

Thanks for all you help

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Innovations in Cisco Full Stack Observability - A new webinar from Cisco