[c-nsp] CRC errors on fastethernet interface

Aaron dudepron at gmail.com
Thu Nov 22 10:36:57 EST 2012


The FE on the 7200 is a FE, not 10/100 switchable, hence no speed.

Have you tried a different port on both sides? That would narrow down
where the issue is since you tried swapping the cable.
Is the cable passing near power cable or over power cables at not 90degs?



On Thu, Nov 22, 2012 at 1:33 AM, Joe Mays <mays at win.net> wrote:
> Have a 7206 connected to a Catalyst 2900XL switch port.
>
> The 2900XL is getting CRC errors on the port at the rate of about one
> every one or two seconds. I've tried replacing the cable, no effect.
>
> core-sw1.noc#show int fastethernet0/1
> FastEthernet0/1 is up, line protocol is up
>   Hardware is Fast Ethernet, address is 0002.7d2f.bc41 (bia
> 0002.7d2f.bc41)
>   Description: 802.1q trunk to core-gw1.noc.win.net port FastEthernet0/0
>   MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
>      reliability 255/255, txload 51/255, rxload 37/255
>   Encapsulation ARPA, loopback not set
>   Keepalive not set
>   Full-duplex, 100Mb/s, 100BaseTX/FX
>   ARP type: ARPA, ARP Timeout 04:00:00
>   Last input never, output 00:00:00, output hang never
>   Last clearing of "show interface" counters 00:05:49
>   Queueing strategy: fifo
>   Output queue 0/40, 0 drops; input queue 0/75, 0 drops
>   30 second input rate 14547000 bits/sec, 2327 packets/sec
>   30 second output rate 20099000 bits/sec, 3507 packets/sec
>      862330 packets input, 682108246 bytes
>      Received 398 broadcasts, 0 runts, 0 giants, 0 throttles
>      63 input errors, 63 CRC, 0 frame, 64 overrun, 64 ignored
>      0 watchdog, 257 multicast
>      0 input packets with dribble condition detected
>      1262698 packets output, 899402766 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 output buffer failures, 0 output buffers swapped out
>
> Since changing the cable made no difference, it's either a port problem
> on the 7206 or 2900XL, or a config problem. Here are the configs for the
> interfaces on each end.
>
> (Since the 7206 does not specify 100mbps, I had thought maybe it was
> occasionally trying to renegotiate the speed, which might screw up the
> switch end, which is hardwired 100-full, while the 7206 is set to
> full-duplex, the speed command to force 100mbps speed does not seem to
> exist on the 7206.)
>
> Cisco 7206 --
>
> interface FastEthernet0/0
>  description Win.net NOC gateway LAN, 911 Heyburn Bldg (via
> core-sw1.noc.win.net)
>  ip address nnn.nnn.nnn.nnn 255.255.255.192
>  ip access-group block-out-to-dot30 out
>  no ip proxy-arp
>  ip route-cache same-interface
>  ip route-cache flow
>  ip ospf message-digest-key 1 md5 7 xxxxxxxxxxxxxxxxxxxxxxx
>  ip ospf cost 2
>  ip ospf priority 200
>  no ip mroute-cache
>  load-interval 60
>  duplex full
>  no keepalive
>  no cdp enable
>  standby 1 ip 216.24.30.65
>  standby 1 timers 5 15
>  standby 1 priority 105
>  standby 1 preempt delay minimum 60
>  standby 1 authentication dfwmhsrp
>  standby 1 track Serial6/0
>  crypto map KYtoINvpn
>  service-policy output queue-on-dscp
>
> 2900XL
>
> interface FastEthernet0/1
>  description 802.1q trunk to core-gw1.noc.win.net port FastEthernet0/0
>  load-interval 30
>  duplex full
>  speed 100
>  switchport trunk encapsulation dot1q
>  switchport mode trunk
>  no cdp enable
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/


More information about the cisco-nsp mailing list