[c-nsp] FE experienceing errors and CRCs
r.sahney
r.sahney at gmail.com
Thu Apr 28 12:21:56 EDT 2005
Hi ,
In case of multivendor integration as I have seen , seeting the
speed does make a lot of difference, just to share a bit, try
connecting Avaya Gear with Nortel Boxes with 100 Mbps FD explicity and
you will see drops and crc, change it to auto and its resolved.
Since yours is Cisco Gear this should not be the case, but
usually the first place to start troubleshooting will be changing the
cable and setting both to 100 Mbps FD.
Hope this helps...
Regards
Raja
On 4/28/05, Michael K. Smith <mksmith at noanet.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> You might also want to set the keepalive on your cat-3524 port. It's
> set to 10 (default) on your other port. I think the "keepalive"
> command will set it to 10. You might also want to set "speed 100" on
> both ends, but I don't think that will give you CRC's. I would still
> look at the physical infrastructure. Maybe your second cable is also
> bad. Maybe it's almost too long, or it's receiving interference from
> something else, etc.
>
> Mike
> - --
> Michael K. Smith mksmith at noanet.net
> Senior Network and Systems Engineer NoaNet
> (206) 963-3679 http://www.noanet.net
>
> On Apr 27, 2005, at 9:26 AM, Kim Onnel wrote:
>
> > Hi,
> >
> >
> > I have an interface that generates CRCs and Errors,
> >
> > Cat-3524#sh ver
> > Cisco Internetwork Operating System Software
> > IOS (tm) C3500XL Software (C3500XL-C3H2S-M), Version 12.0(5.3)WC(1),
> > MAINTENANCE
> > INTERIM SOFTWARE
> > Copyright (c) 1986-2001 by cisco Systems, Inc.
> > Compiled Mon 30-Apr-01 07:51 by devgoyal
> > Image text-base: 0x00003000, data-base: 0x003331F4
> >
> > ROM: Bootstrap program is C3500XL boot loader
> >
> > Cat-3524 uptime is 24 weeks, 10 hours, 40 minutes
> > System returned to ROM by power-on
> > System image file is "flash:c3500XL-c3h2s-mz.120-5.3.WC.1.bin"
> >
> >
> >
> > at-3524#sh int FastEthernet 0/2
> > FastEthernet0/2 is up, line protocol is up
> > Hardware is Fast Ethernet, address is 0006.288e.b602 (bia
> > 0006.288e.b602)
> > Description: new MCE
> > MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
> > reliability 255/255, txload 9/255, rxload 19/255
> > Encapsulation ARPA, loopback not set
> > Keepalive not set
> > Full-duplex, Auto Speed (100), 100BaseTX/FX
> > ARP type: ARPA, ARP Timeout 04:00:00
> > Last input never, output 00:00:01, output hang never
> > Last clearing of "show interface" counters 02:09:56
> > Queueing strategy: fifo
> > Output queue 0/40, 0 drops; input queue 0/75, 0 drops
> > 5 minute input rate 7603000 bits/sec, 1937 packets/sec
> > 5 minute output rate 3723000 bits/sec, 1453 packets/sec
> > 16243259 packets input, 3149513025 bytes
> > Received 11677 broadcasts, 0 runts, 0 giants, 0 throttles
> > 1749 input errors, 1749 CRC, 0 frame, 0 overrun, 0 ignored
> > 0 watchdog, 14 multicast
> > 0 input packets with dribble condition detected
> > 11741374 packets output, 4034232096 bytes, 0 underruns
> > 0 output errors, 0 collisions, 0 interface resets
> > 0 babbles, 0 late collision, 0 deferred
> >
> > and the Errors, CRC increasing.
> >
> > This interface has the following configurations and is connected to an
> > RPM-PR (7200 router)
> >
> > Cat-3524#sh run int FAstEthernet 0/2
> > !
> > interface FastEthernet0/2
> > description new MCE
> > duplex full
> > end
> >
> >
> >
> > The adjacent interface on the RPM has the following configurations :
> >
> > MCE#sh run int FastEthernet 1/1
> >
> > interface FastEthernet1/1
> > ip address x.x.110.3 255.255.255.192 secondary
> > ip address x.1x.140.209 255.255.255.240 secondary
> > ip address x3.2x.255.49 255.255.255.248 secondary
> > ip address 2xx.x2.255.237 255.255.255.252 secondary
> > ip address 1x.1x.200.2 255.255.255.0 secondary
> > ip address x.1x.249.197 255.255.255.252 secondary
> > ip address x.1x.235.193 255.255.255.192 secondary
> > ip address 10.20.10.2 255.255.255.240 secondary
> > ip address 1x.x.1.254 255.255.255.0 secondary
> > ip address x.x0.110.251 255.255.255.192
> > ip access-group block-worms in
> > ip access-group block-worms out
> > rate-limit input access-group rate-limit 100 2048000 5000 5000
> > conform-action t
> > ransmit exceed-action transmit
> > rate-limit input access-group 114 5000000 900000 900000
> > conform-action transmit
> > exceed-action drop
> > rate-limit input access-group 115 512000 64000 96000 conform-action
> > transmit ex
> > ceed-action drop
> > rate-limit output access-group 114 5000000 900000 900000
> > conform-action transmi
> > t exceed-action drop
> > rate-limit output access-group 115 512000 64000 96000 conform-action
> > transmit e
> > xceed-action drop
> > rate-limit output access-group rate-limit 100 2048000 5000 5000
> > conform-action
> > transmit exceed-action transmit
> > load-interval 30
> > full-duplex
> > no cdp enable
> > end
> >
> > MCE#sh int FastEthernet 1/1
> > FastEthernet1/1 is up, line protocol is up
> > Hardware is DEC21140A, address is 0007.ec79.5ace (bia 0007.ec79.5ace)
> > Internet address is x.x.110.251/26
> > MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
> > reliability 255/255, txload 18/255, rxload 8/255
> > Encapsulation ARPA, loopback not set
> > Keepalive set (10 sec)
> > Full-duplex, 100Mb/s, 100BaseTX/FX
> > 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 02:53:17
> > Queueing strategy: fifo
> > Output queue 0/40, 0 drops; input queue 0/75, 0 drops
> > 30 second input rate 3353000 bits/sec, 1406 packets/sec
> > 30 second output rate 7238000 bits/sec, 1875 packets/sec
> > 15874784 packets input, 1083525547 bytes
> > Received 6043 broadcasts, 0 runts, 0 giants, 0 throttles
> > 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
> > 0 watchdog
> > 0 input packets with dribble condition detected
> > 21790301 packets output, 1291808671 bytes, 2357 underruns
> > 2357 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
> >
> > in my humble experience, i should try to
> >
> > 1) have the same duplex on both, which i think i have.
> > 2) change cable, also done
> >
> > Whats my next step ?
> >
> > _______________________________________________
> > 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/
>
> -----BEGIN PGP SIGNATURE-----
> Version: PGP 8.1
>
> iQA/AwUBQnByGZzgx7Y34AxGEQKE0gCfTzydkhAgh+6XdFI1gOZjgFA+KbwAn38m
> 6HBQ7ax2i9hjGWHSHXTTFCxn
> =Ck+I
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> 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