Gary- the following was posted back on the 1st of July. It may help you in proving where the failure is.
Brad Dodds posted: "you can use extended ping testing to try to uncover if it is in fact a Telco line problem from : http://www.cisco.com/warp/public/784/packet/oct01/p53-cover.html Extended Ping Testing The ping command is generally used to make sure that two devices that are remote from one another can attain basic Layer 3 connectivity. The ping command also has an "extended commands" section that allows you to enter the 2-byte data pattern, in hexadecimal format, that is repeated in the payload of the ping packet. Three useful ping data patterns that expose line problems include the following: 0x0000 - Line-code mismatches 0xFFFF - Repeater power problems 0x4040 - Timing problems The 0x4040 extended ping pattern also enables you to detect jitter and wander. T1 phase variations greater than or equal to 10Hz are considered jitter, and variations less than 10Hz are considered wander. example: RouterHostname#ping Protocol [ip]: Target IP address: XXX.XXX.XXX.XXX Repeat count [5]: 50 Datagram size [100]: Timeout in seconds [2]: Extended commands [n]: y Source address: Type of service [0]: Set DF bit in IP header? [no]: Validate reply data? [no]: y Data pattern [0xABCD]: 0x4040 Loose, Strict, Record, Timestamp, Verbose[none]: Sweep range of sizes [n]: Type escape sequence to abort. Sending 50, 100-byte ICMP Echoes to XXX.XXX.XXX.XXX, timeout is 2 seconds: Packet has data pattern 0x4040 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Success rate is 100 percent (50/50), round-trip min/avg/max = 8/9/24 ms" HTHs, Mark -----Original Message----- From: Gary Crouch [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 28, 2002 12:02 PM To: [EMAIL PROTECTED] Subject: CRC frame errors and carrier transitions [7:52225] our WAN connections dies about once a month and we always get lots of frame error and carrier transitions Pac Bell does not have a clue to why this is happening the have blamed our Equpment Cisco 3640 with Adtran TSU LS or timing errors but general have no clue. is there any way to clean this connection up and stop the monthly outages Thanks MCI-Frame#sh int s0/1 Serial0/1 is up, line protocol is up Hardware is QUICC Serial Description: backport to DI Internet address is x.x.x.x/30 MTU 1500 bytes, BW 2048 Kbit, DLY 20000 usec, reliability 255/255, txload 2/255, rxload 7/255 Encapsulation HDLC, loopback not set Keepalive set (10 sec) Last input 00:00:00, output 00:00:00, output hang never Last clearing of "show interface" counters 17:02:48 Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 10 Queueing strategy: weighted fair Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/22/256 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) Available Bandwidth 1536 kilobits/sec 5 minute input rate 59000 bits/sec, 13 packets/sec 5 minute output rate 17000 bits/sec, 14 packets/sec 350855 packets input, 175929333 bytes, 0 no buffer Received 7602 broadcasts, 0 runts, 0 giants, 0 throttles 37509 input errors, 2081 CRC, 35414 frame, 0 overrun, 0 ignored, 8 abort 292361 packets output, 39591690 bytes, 0 underruns 0 output errors, 0 collisions, 5 interface resets 0 output buffer failures, 0 output buffers swapped out 168 carrier transitions DCD=up DSR=up DTR=up RTS=up CTS=up Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=52230&t=52225 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
