Switchport taking errors when connected to Proxim wireless bridge

Cooky

Golden Member
Apr 2, 2002
1,408
0
76
We have several sites that use Proxim's GigaLink 6451e wireless bridge to connect between their buildings.

For some odd reason, the switchport on our 3750G would take errors, even after we swap out every component between the devices. (fiber, SFP, and even tried a different switch)

We insisted that the problem is w/ the bridge, so Proxim took it back to their repair lab, and determined there's nothing wrong w/ it.

So we're now stuck.
Has anyone had this weird problem before?

Below is the show output from the switch, could someone tell me why we're taking errors?

3750#sh run int g0/51
Building configuration...

Current configuration : 188 bytes
!
interface GigabitEthernet0/51
description Giglink Wireless
switchport trunk encapsulation dot1q
switchport mode trunk
speed nonegotiate
priority-queue out
mls qos trust dscp
end

3750#

3750#sh int g0/51
GigabitEthernet0/51 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 001b.90e3.9fb3 (bia 001b.90e3.9fb3)
Description: Giglink Wireless
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Full-duplex, 1000Mb/s, link type is force-up, media type is 1000BaseSX SFP
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters 22:38:39
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 353000 bits/sec, 140 packets/sec
5 minute output rate 873000 bits/sec, 164 packets/sec
7114047 packets input, 3075807618 bytes, 0 no buffer
Received 434979 broadcasts (0 multicast)
0 runts, 0 giants, 0 throttles
108854 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 42800 multicast, 0 pause input
0 input packets with dribble condition detected
8202823 packets output, 242104950 bytes, 0 underruns
0 output errors, 0 collisions, 0 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
3750#

3750#sh controllers ethernet-controller gi0/51

Transmit GigabitEthernet0/51 Receive
2521107492 Bytes 3299512421 Bytes
12292780 Unicast frames 12546794 Unicast frames
1779939 Multicast frames 69249 Multicast frames
202646 Broadcast frames 585250 Broadcast frames
0 Too old frames 3139945349 Unicast bytes
0 Deferred frames 10021627 Multicast bytes
0 MTU exceeded frames 55154470 Broadcast bytes
0 1 collision frames 0 Alignment errors
0 2 collision frames 204 FCS errors
0 3 collision frames 0 Oversize frames
0 4 collision frames 0 Undersize frames
0 5 collision frames 212 Collision fragments
0 6 collision frames
0 7 collision frames 3452231 Minimum size frames
0 8 collision frames 3126344 65 to 127 byte frames
0 9 collision frames 1751243 128 to 255 byte frames
0 10 collision frames 513947 256 to 511 byte frames
0 11 collision frames 414942 512 to 1023 byte frames
0 12 collision frames 4144144 1024 to 1518 byte frames
0 13 collision frames 0 Overrun frames
0 14 collision frames 0 Pause frames
0 15 collision frames
0 Excessive collisions 205974 Symbol error frames
0 Late collisions 3018 Invalid frames, too large
0 VLAN discard frames 0 Valid frames, too large
0 Excess defer frames 1814 Invalid frames, too small
2184793 64 byte frames 0 Valid frames, too small
5662789 127 byte frames
1766583 255 byte frames 0 Too old frames
594455 511 byte frames 0 Valid oversize frames
205786 1023 byte frames 0 System FCS error frames
3860959 1518 byte frames 0 RxPortFifoFull drop frame
0 Too large frames
0 Good (1 coll) frames
0 Good (>1 coll) frames

 

spidey07

No Lifer
Aug 4, 2000
65,469
5
76
Take out the speed nonegotiate command.

Also there were some bugs in the 3750 code that would incorrectly show errors when there were none. I'd open a case with cisco.

CHeck CSCsg35293 in bug toolkit.
 

Cooky

Golden Member
Apr 2, 2002
1,408
0
76
Thanks for the info - I don't think the bug applies to us though...we're connected to Gig port, and not 10/100.
Also the link wouldn't come up w/o the nonegotiate command.

Just opened an SR w/ TAC, and will see what they say...if we connect a switch to that same port we don't get any errors though so I think it's something about those Proxim bridges but they keep saying there's nothing wrong.

I anticipate both Proxim and Cisco will say the same thing, and we'll be left where we are now.
 

spidey07

No Lifer
Aug 4, 2000
65,469
5
76
Have you tested the fiber and sure it passes 1000 Base-SX for loss, bandwidth? Any chance you have a mix of 50 and 62.5 micron? That will cause similar physical layer problems - patch cables not matching the horizontal core diameter, or not seated well. You'll get link, but it's not clean.

The link not coming up might be flow control mismatch as well.
 

sims

Junior Member
Aug 2, 2013
1
0
0
Hi Corky,
I know that it's been 4 years but can you tell me if you were able to find a solution for this? we are getting the exact same errors that you were seeing when you posted this.
thanks!

Willie
Network Administrator
Sims Metal Management