RE: token ring problem - URGENT [7:3596]
This only started this weekend just gone. New STP cabling was installed by the client. I replaced the one device yesterday to prove a point, but I really believe the cabling is a problem. Client does not believe me though. This is what I got from the Madge RMON stats on the port.. Name Value Abort errors 525 AC errors 14 Beacon events 0 Beacon packets0 Beacon time 0 Burst errors 0 Claim token events0 Claim token packets 0 Congestion errors 2652 Dropped events0 Frame copied errors 0 Frequency errors 0 Internal errors 0 Line errors 9 Lost frame errors 1868 MAC octets2385536 MAC packets 73924 NAUN changes 1 Ring poll events 5799 Ring purge events 9651 Ring purge packets10561 Soft error reports1250 Token errors 4834 Thanks for all the help Andrew -Original Message- From: Priscilla Oppenheimer [mailto:[EMAIL PROTECTED]] Sent: 08 May 2001 20:09 To: [EMAIL PROTECTED] Subject: Re: token ring problem - URGENT [7:3596] At 10:19 AM 5/8/01, Vincent Chong wrote: >Hi; > >You should use show controller token to determine how many Soft Errors and >types of soft error > >Soft errors: 2 Types: Isolating and Non-isolating soft error. > >Isolating soft error: the NAUN in the soft error report frame is irrelevant. Thanks for a good answer. You meant to say that the NAUN is relevant with isolating errors, though. With isolating errors, the troubleshooter can isolate the fault domain. The fault may be with the reporting station, the nearest active upstream neighbor (NAUN), or cabling, MSAU ports or patch panels between the station and its NAUN. If CRC errors (line errors) are excessive, check for crosstalk, noise, RFI or EMI affecting the cabling between the reporting station and its upstream neighbor. Also check the NIC of the upstream neighbor. 60 CRC errors in four minutes with 2.2 Mbytes of traffic is a lot. But is this a continuous problem or just a one-time thing? When an error occurs, a station sets a two-second timer and waits for any other errors before sending a soft error report. Using a Sniffer, look back two seconds from the soft error report to see if there's any evidence of what caused the problem. It might just be stations inserting or leaving the ring. Priscilla >Types: Line error (CRC error, illegal bit find in Token or frame), Internal >error, Burst Error, ARI/FCI error > >Non-isolating soft error: Cannot be isolated to a station and the stations >NAUN or the cabling between them. > >Types: Lost frame, copy error, receive congested, token error, frequency >error. > >The cyclic redundancy checksum generated by the originating LAN station or >far-end device does not match the checksum calculated from the data >received. On a LAN, this usually indicates noise or transmission problems on >the LAN interface or the LAN bus itself. A high number of CRCs is usually >the result of a station transmitting bad data. > >HTH > >Vincent Chong > > >""Andrew Larkins"" wrote in message >[EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > What causes a CRC error on the token ring port and what is a soft >error > > > > > > JOHANNESBURG#sho int to 0/0 > > TokenRing0/0 is up, line protocol is up > > Hardware is IBM2692, address is 0007.7829.1b43 (bia 0007.7829.1b43) > > Internet address is x.x.x.x > > MTU 8136 bytes, BW 16000 Kbit, DLY 630 usec, > > reliability 255/255, txload 3/255, rxload 1/255 > > Encapsulation SNAP, loopback not set > > Keepalive set (10 sec) > > ARP type: SNAP, ARP Timeout 04:00:00 > > Ring speed: 16 Mbps > > Duplex: half > > Mode: Classic token ring station > > Source bridging enabled, srn 1025 bn 1 trn 1997 (ring group) > > sp
Re: token ring problem - URGENT [7:3596]
At 10:19 AM 5/8/01, Vincent Chong wrote: >Hi; > >You should use show controller token to determine how many Soft Errors and >types of soft error > >Soft errors: 2 Types: Isolating and Non-isolating soft error. > >Isolating soft error: the NAUN in the soft error report frame is irrelevant. Thanks for a good answer. You meant to say that the NAUN is relevant with isolating errors, though. With isolating errors, the troubleshooter can isolate the fault domain. The fault may be with the reporting station, the nearest active upstream neighbor (NAUN), or cabling, MSAU ports or patch panels between the station and its NAUN. If CRC errors (line errors) are excessive, check for crosstalk, noise, RFI or EMI affecting the cabling between the reporting station and its upstream neighbor. Also check the NIC of the upstream neighbor. 60 CRC errors in four minutes with 2.2 Mbytes of traffic is a lot. But is this a continuous problem or just a one-time thing? When an error occurs, a station sets a two-second timer and waits for any other errors before sending a soft error report. Using a Sniffer, look back two seconds from the soft error report to see if there's any evidence of what caused the problem. It might just be stations inserting or leaving the ring. Priscilla >Types: Line error (CRC error, illegal bit find in Token or frame), Internal >error, Burst Error, ARI/FCI error > >Non-isolating soft error: Cannot be isolated to a station and the stations >NAUN or the cabling between them. > >Types: Lost frame, copy error, receive congested, token error, frequency >error. > >The cyclic redundancy checksum generated by the originating LAN station or >far-end device does not match the checksum calculated from the data >received. On a LAN, this usually indicates noise or transmission problems on >the LAN interface or the LAN bus itself. A high number of CRCs is usually >the result of a station transmitting bad data. > >HTH > >Vincent Chong > > >""Andrew Larkins"" wrote in message >[EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > What causes a CRC error on the token ring port and what is a soft >error > > > > > > JOHANNESBURG#sho int to 0/0 > > TokenRing0/0 is up, line protocol is up > > Hardware is IBM2692, address is 0007.7829.1b43 (bia 0007.7829.1b43) > > Internet address is x.x.x.x > > MTU 8136 bytes, BW 16000 Kbit, DLY 630 usec, > > reliability 255/255, txload 3/255, rxload 1/255 > > Encapsulation SNAP, loopback not set > > Keepalive set (10 sec) > > ARP type: SNAP, ARP Timeout 04:00:00 > > Ring speed: 16 Mbps > > Duplex: half > > Mode: Classic token ring station > > Source bridging enabled, srn 1025 bn 1 trn 1997 (ring group) > > spanning explorer enabled > > Group Address: 0x, Functional Address: 0x0880001A > > Ethernet Transit OUI: 0x00 > > Last Ring Status 00:00:08 (0x2000) > > Last input 00:00:00, output 00:00:00, output hang never > > Last clearing of "show interface" counters 00:04:36 > > 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 63000 bits/sec, 53 packets/sec > > 5 minute output rate 193000 bits/sec, 49 packets/sec > > 15161 packets input, 2224430 bytes, 0 no buffer > > Received 1304 broadcasts, 0 runts, 0 giants, 0 throttles > > 60 input errors, 60 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort > > 15150 packets output, 8156480 bytes, 0 underruns > > 0 output errors, 0 collisions, 0 interface resets > > 0 output buffer failures, 0 output buffers swapped out > > 0 transitions > > > > > > Thanks > > > > Andrew > > FAQ, list archives, and subscription info: >http://www.groupstudy.com/list/cisco.html > > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] >FAQ, list archives, and subscription info: >http://www.groupstudy.com/list/cisco.html >Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] Priscilla Oppenheimer http://www.priscilla.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=3652&t=3596 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: token ring problem - URGENT [7:3596]
Hi; You should use show controller token to determine how many Soft Errors and types of soft error Soft errors: 2 Types: Isolating and Non-isolating soft error. Isolating soft error: the NAUN in the soft error report frame is irrelevant. Types: Line error (CRC error, illegal bit find in Token or frame), Internal error, Burst Error, ARI/FCI error Non-isolating soft error: Cannot be isolated to a station and the stations NAUN or the cabling between them. Types: Lost frame, copy error, receive congested, token error, frequency error. The cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of a station transmitting bad data. HTH Vincent Chong ""Andrew Larkins"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > What causes a CRC error on the token ring port and what is a soft error > > > JOHANNESBURG#sho int to 0/0 > TokenRing0/0 is up, line protocol is up > Hardware is IBM2692, address is 0007.7829.1b43 (bia 0007.7829.1b43) > Internet address is x.x.x.x > MTU 8136 bytes, BW 16000 Kbit, DLY 630 usec, > reliability 255/255, txload 3/255, rxload 1/255 > Encapsulation SNAP, loopback not set > Keepalive set (10 sec) > ARP type: SNAP, ARP Timeout 04:00:00 > Ring speed: 16 Mbps > Duplex: half > Mode: Classic token ring station > Source bridging enabled, srn 1025 bn 1 trn 1997 (ring group) > spanning explorer enabled > Group Address: 0x, Functional Address: 0x0880001A > Ethernet Transit OUI: 0x00 > Last Ring Status 00:00:08 (0x2000) > Last input 00:00:00, output 00:00:00, output hang never > Last clearing of "show interface" counters 00:04:36 > 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 63000 bits/sec, 53 packets/sec > 5 minute output rate 193000 bits/sec, 49 packets/sec > 15161 packets input, 2224430 bytes, 0 no buffer > Received 1304 broadcasts, 0 runts, 0 giants, 0 throttles > 60 input errors, 60 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort > 15150 packets output, 8156480 bytes, 0 underruns > 0 output errors, 0 collisions, 0 interface resets > 0 output buffer failures, 0 output buffers swapped out > 0 transitions > > > Thanks > > Andrew > FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=3602&t=3596 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
token ring problem - URGENT [7:3596]
What causes a CRC error on the token ring port and what is a soft error JOHANNESBURG#sho int to 0/0 TokenRing0/0 is up, line protocol is up Hardware is IBM2692, address is 0007.7829.1b43 (bia 0007.7829.1b43) Internet address is x.x.x.x MTU 8136 bytes, BW 16000 Kbit, DLY 630 usec, reliability 255/255, txload 3/255, rxload 1/255 Encapsulation SNAP, loopback not set Keepalive set (10 sec) ARP type: SNAP, ARP Timeout 04:00:00 Ring speed: 16 Mbps Duplex: half Mode: Classic token ring station Source bridging enabled, srn 1025 bn 1 trn 1997 (ring group) spanning explorer enabled Group Address: 0x, Functional Address: 0x0880001A Ethernet Transit OUI: 0x00 Last Ring Status 00:00:08 (0x2000) Last input 00:00:00, output 00:00:00, output hang never Last clearing of "show interface" counters 00:04:36 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 63000 bits/sec, 53 packets/sec 5 minute output rate 193000 bits/sec, 49 packets/sec 15161 packets input, 2224430 bytes, 0 no buffer Received 1304 broadcasts, 0 runts, 0 giants, 0 throttles 60 input errors, 60 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 15150 packets output, 8156480 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out 0 transitions Thanks Andrew Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=3596&t=3596 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
