port blinking orange.

Unanswered Question
Sep 24th, 2007

Hi all,

We have 2950S all ports blinking green so that they all are working fine but one port f0/34 blinking orange but still accessing & working fine.

Actually my disbelief is when port seems orange colour indicate coming up and when orange to green then it ready to access but while orange only the port able to access and working fine.

Experts anybody can see and explain.



I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
ankbhasi Mon, 09/24/2007 - 21:59

Hi Naidu,

Can you post the output of "sh interface fa0/34" , "sh run int fa0/34" and "sh spanning-tree interface fa0/34"?



ilnaiduccna Mon, 09/24/2007 - 22:11

Hi Ankur,

Great your early reply.

Fallowing is the output for your desired things.

Switch#sh int f0/44

FastEthernet0/44 is up, line protocol is up (connected)

Hardware is Fast Ethernet, address is 001c.0f15.da2c (bia 001c.0f15.da2c Description: ** MBPN Connectivity **

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/100BaseTX

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

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

Last input 00:00:01, output 00:00:05, 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/40 (size/max)

5 minute input rate 1000 bits/sec, 1 packets/sec

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

15602792 packets input, 1091346211 bytes, 0 no buffer

Received 15432142 broadcasts (0 multicast)

0 runts, 0 giants, 0 throttles

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

0 watchdog, 15344336 multicast, 0 pause input

0 input packets with dribble condition detected

892117 packets output, 97075223 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

Switch#sh spanning-tree interface f0/44

Vlan Role Sts Cost Prio.Nbr Type

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

VLAN0015 Altn BLK 19 128.44 P2p



lgijssel Mon, 09/24/2007 - 22:24

The behaviour that you report is mostly due to incorrect duplex settings on the interface.

A high amount of errors causes the port to reinitialize.

Please verify speed/duplex setting.



ilnaiduccna Mon, 09/24/2007 - 22:32

Hi Leo,

As you told I would like to verify speed & duplex settings.

From where we can able to see these things and which two ports should tally both settings like F0/34 dupled full & speed 100 mbps it should tally with which port.



Kevin Dorrell Mon, 09/24/2007 - 22:56

Did I miss something here? The listing is for F0/44, but the original problem was for F0/34. And I cannot see the errors and collisions that Leo was talking about. Is there some parallel thread going on about this problem?

[P.S. Edit] Sorry Leo, my apologies if that last paragraph sounded arogant. Looking at the structure of the thread I realise now that you posted before the show int was available. I am sorry I got confused.

In answer to the last posting on this thread, the settings on each port are independent of each other. Each port should set up according to the host that is connected on that port.

Kevin Dorrell


ilnaiduccna Mon, 09/24/2007 - 23:07

Hi Kevin,

I am sorry for my disregard that actually problem with f0/44 port it self not with f0/34.

You are saying that some parallel thread going on this problem what is that can u tell briefly.



Kevin Dorrell Mon, 09/24/2007 - 23:12

Well, I don't see any problem in the show int.

When you power on the switch and it does its self-test, do all the LEDs come up green?

Kevin Dorrell


ankbhasi Tue, 09/25/2007 - 01:01

Hi Naidu,

Can you update to which switch is this port connected as I believe this port is in blocking state and is the reason it is in amber state.



ilnaiduccna Tue, 09/25/2007 - 01:19

Hi Ankur,

Good diverse.

The port is f0/44 connected one core-telco node and it was not blocked cos still it was able to access & working fine.




This Discussion