Gary, 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 Brad Dodds WAN Engineer NCS MOREnet ""Gary Crouch"" wrote in message news:[EMAIL PROTECTED]... > reset are up to 783 in less the 5 minuets from 739 > > MCI-Frame#sh in s0/1 > Serial0/1 is up, line protocol is up > Hardware is QUICC Serial > Description: backport to DI > Internet address is 10.152.5.254/30 > MTU 1500 bytes, BW 2048 Kbit, DLY 20000 usec, > reliability 251/255, txload 1/255, rxload 1/255 > Encapsulation HDLC, loopback not set > Keepalive set (10 sec) > Last input 00:00:19, output 00:00:01, output hang never > Last clearing of "show interface" counters never > Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 > Queueing strategy: weighted fair > Output queue: 0/1000/64/0 (size/max total/threshold/drops) > Conversations 0/6/256 (active/max active/max total) > Reserved Conversations 0/0 (allocated/max allocated) > Available Bandwidth 1536 kilobits/sec > 5 minute input rate 0 bits/sec, 0 packets/sec > 5 minute output rate 0 bits/sec, 0 packets/sec > 15753 packets input, 4040974 bytes, 0 no buffer > Received 6872 broadcasts, 0 runts, 0 giants, 0 throttles > 395 input errors, 0 CRC, 395 frame, 0 overrun, 0 ignored, 0 abort > 14887 packets output, 1732578 bytes, 0 underruns > 0 output errors, 0 collisions, 783 interface resets > 0 output buffer failures, 0 output buffers swapped out > 0 carrier transitions > DCD=up DSR=up DTR=up RTS=up CTS=up > > MCI-Frame# Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=47859&t=47668 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
