Port Errors on fiber connected ports 1

[bubarooni1]

Hi,

I have 2 switches connected via fiber converters that connect two bldgs.

Switch 1 is a 2924xl. Switch 2 is a 3548xl. Port 11 on Switch 1 is connected to Switch 2 on Port 1. Everyone is the bldg that Switch 2 is located in is having a terrible time connecting to servers in the bldg where Switch 1 is located. I just can't figure it out...

the only programming I have on either switches ports are the connecting ports:

switch 1

interface FastEthernet0/11
duplex full
speed 100

switch 2

interface FastEthernet0/1
duplex full
speed 100

I have a laptop connected via the console port on switch 2 and get errors on it that says:
FastEthernet0/1 is experiencing errors
The stat light blinks amber and green for that port when that occurs.

Is there something wrong with those simple config statements on the ports? Where else should I be looking to troubleshoot this if it is not the port configs?

Thanks In Advance!

 

[jeter]

Have you tested the connection right on the media converter?

Plug your laptop into the ethernet of the media coverter and see what happens!!!

Depending on what you find will point you in the right direction!!!


SPC NVARNG
Tek-TIP Member 19,650

 

[robertjo24]

What is the optical distance on the fiber?
Do the fiber converters support the distance you are running? Some fiber converters will only operate under a certain distance.
Are you certain the fiber is good?

I had the same issue with fiber converters between two switches throwing errors. We found a pr0oly done splice on a overstressed ariel cable. Every time the wind would blow more than a just a bit, we would get errors.

If none of this fixes the issue...
Tray running the switch ports on AUTO / AUTO

 

[bubarooni1]

i'll try the straight internet connection as soon as i get back to that site today.

the fiber is about 500 foot long. i believe it's all good. the link between the two bldgs is new and had been up and running fine for about five months. about a month ago i started having problems with speed and i had a switch go bad (mem post failures), switch 2, and replaced with another.

here is output from Switch 2, since a reset last night. i hope that it will indicate something wrong to someone:

<code>
FastEthernet0/1 is up, line protocol is up
Hardware is Fast Ethernet, address is 0005.32ec.83c1 (bia 0005.32ec.83c1)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 245/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Auto-duplex (Full), Auto Speed (100), 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:01, output 00:00:30, 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 7000 bits/sec, 7 packets/sec
5 minute output rate 49000 bits/sec, 6 packets/sec
2223860 packets input, 214089094 bytes
Received 117002 broadcasts, 0 runts, 0 giants, 0 throttles
80507 input errors, 78952 CRC, 1555 frame, 0 overrun, 0 ignored
0 watchdog, 24618 multicast
0 input packets with dribble condition detected
4002021 packets output, 1463513781 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 output buffer failures, 0 output buffers swapped out
</code>

 

[bubarooni1]

and here is the other end at Switch 1(port 19 on that switch instead of port 11 as i indicated originally). it seems fine to me and that the problem has got to be something over in the bldg where Switch 2 is located.

<code>
FastEthernet0/19 is up, line protocol is up
Hardware is Fast Ethernet, address is 0002.b978.3353 (bia 0002.b978.3353)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Auto-duplex (Full), Auto Speed (100), 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:02, output 00:00:00, 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 6000 bits/sec, 7 packets/sec
5 minute output rate 8000 bits/sec, 9 packets/sec
4008890 packets input, 1464296260 bytes
Received 29962 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 2 ignored
0 watchdog, 1336 multicast
0 input packets with dribble condition detected
2320726 packets output, 216773702 bytes, 0 underruns
0 output errors, 0 collisions, 3 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
</code>

 

[burtsbees]

FA0/1 has a buttload of input errors and CRC errors,whereas the other does not. Its reliability went to 245...post a sh run fa0/1 of switch 2 and a sh run int fa0/19 of switch 1.

Burt

 

[bubarooni1]

SWITCH 1
WB2900XL1#show run int fa0/19
Building configuration...

Current configuration:
!
interface FastEthernet0/19
end

SWITCH 2
wbldg7_3548xl#show run int fa0/1
Building configuration...

Current configuration:
!
interface FastEthernet0/1
end

 

[bubarooni1]

hmmmmmm....

i just connected a laptop directly to the media converter and have the same problem.

 

[burtsbees]

Seems you have narrowed it down to the media converter. That makes sense.

Burt

 

[vipergg]

Were you getting errors when it was hardcoded to 100/full ?
If you have tried both settings then I would probably look at replacing the converter , those errors are from copper connection to the switch . I assume the patch has been replaced already. Are you seeing heavy ping loss when pinging across that link ???? Did you change the port settings to auto before reloading the switch ?

 

[jeter]

It wouldn't be the first time I have seen the media converter go bad...

Then again which media converter, the host or the remote end?????


SPC NVARNG
Tek-TIP Member 19,650

 

[bubarooni1]

OK, so here's what happened:

I called the manufacturer, Transition Networks.
They ran me thru a bunch of troubleshooting and finally the guy asked me, 'how far between the two bldgs.' 'about 400 feet' i replied. He said 'that's your problem, your units are only rated for 60 meters.'

I quizzed my contractor over it, they gave me the 'we didn't know'. Anyway they agreed to take back the old units and I overnighted new units in from Newegg, rated at 2 kilometers, and everything works great now.

While I have your guys attention and interest, the new bldg started out with about 25 ip addressable ('puters, print servers, switches, etc.)units on the network. That has now grown to about 75 units.

The new converters i got are 10/100 mb's. they had some that were 10/100/1000 mbs, but they were more than double the price so i passed. all the application servers the people in the new bldg access are across the fiber link to the old bldg.

I know it's completely dependent on the switch speeds connected to the converters and the apps being accessed across it, but is the 100 mb link between the 2 bldgs maybe getting close to being full? Would there be certain output on the sh int commands that indicate that?

Thanks for all your Help!!!

 

[vipergg]

I doubt it takes a lot of traffic to fill a 100 meg full duplex pipe. Just look at the interfaces that attach the 2 sites for few days at the load on them and you should be able to get a pretty good idea how much load you will have on them .

 

[vipergg]

Just look at the load parameter on the interface which will show x/255 , 255/255 is fully loaded . Also how many bps. It will look like this. If either is getting near 100 meg then you should worry but I doubt it will with only 75 users.

5 minute input rate 7000 bits/sec, 8 packets/sec
5 minute output rate 3000 bits/sec, 4 packets/sec