u need to cont ur telco they are dropping ur traffic
is there too much load on line?
-----Original Message-----
From: Eric Mwambaji [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 19, 2001 11:23 PM
To: Farhan Ahmed
Subject: RE: Latency on ATM interface - Any ideas [7:12978]
ping
Protocol [ip]:
Target IP address: pingy 50192.168.1.1
Repeat count [5]: 50
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface:
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]: y
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
verbose
Loose, Strict, Record, Timestamp, Verbose[V]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 50, 100-byte ICMP Echos to 192.168.1.1,
timeout is 2 seconds:
Reply to request 0 (708 ms)
Reply to request 1 (68 ms)
Reply to request 2 (48 ms)
Reply to request 3 (56 ms)
Reply to request 4 (48 ms)
Reply to request 5 (76 ms)
Reply to request 6 (44 ms)
Reply to request 7 (48 ms)
Reply to request 8 (56 ms)
Reply to request 9 (48 ms)
Reply to request 10 (44 ms)
Reply to request 11 (48 ms)
Reply to request 12 (44 ms)
Reply to request 13 (48 ms)
Reply to request 14 (48 ms)
Reply to request 15 (44 ms)
Reply to request 16 (48 ms)
Reply to request 17 (44 ms)
Reply to request 18 (48 ms)
Reply to request 19 (44 ms)
Reply to request 20 (48 ms)
Reply to request 21 (48 ms)
Reply to request 22 (44 ms)
Reply to request 23 (48 ms)
Reply to request 24 (44 ms)
Reply to request 25 (48 ms)
Reply to request 26 (48 ms)
Reply to request 27 (44 ms)
Reply to request 28 (48 ms)
Reply to request 29 (44 ms)
Reply to request 30 (48 ms)
Reply to request 31 (44 ms)
Reply to request 32 (48 ms)
Reply to request 33 (76 ms)
Reply to request 0 (708 ms)
Reply to request 34 (48 ms)
Reply to request 35 (48 ms)
Reply to request 36 (44 ms)
Reply to request 37 (48 ms)
Reply to request 38 (68 ms)
Reply to request 39 (44 ms)
Reply to request 40 (48 ms)
Reply to request 41 (48 ms)
Reply to request 42 (68 ms)
Reply to request 43 (44 ms)
Reply to request 44 (48 ms)
Reply to request 45 (44 ms)
Reply to request 46 (48 ms)
Reply to request 47 (68 ms)
Reply to request 48 (48 ms)
Reply to request 49 (44 ms)
Success rate is 100 percent (50/50), round-trip
min/avg/max = 44/62/708 ms
ping
Protocol [ip]:
Target IP address: pingverbosey
50192.168.1.1
Repeat count [5]: 50
Datagram size [100]: 1500
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface:
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]: y
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Verbose
Loose, Strict, Record, Timestamp, Verbose[V]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 50, 1500-byte ICMP Echos to 192.168.1.1,
timeout is 2 seconds:
Reply to request 0 (708 ms)
Reply to request 1 (704 ms)
Reply to request 2 (716 ms)
Reply to request 3 (704 ms)
Reply to request 4 (704 ms)
Reply to request 5 (708 ms)
Reply to request 6 (704 ms)
Reply to request 7 (708 ms)
Reply to request 8 (704 ms)
Reply to request 9 (708 ms)
Reply to request 10 (740 ms)
Reply to request 11 (704 ms)
Reply to request 12 (708 ms)
Reply to request 13 (704 ms)
Reply to request 14 (704 ms)
Reply to request 15 (708 ms)
Reply to request 16 (704 ms)
Reply to request 17 (708 ms)
Reply to request 18 (1184 ms)
Reply to request 19 (1184 ms)
Reply to request 20 (704 ms)
Reply to request 21 (704 ms)
Reply to request 22 (708 ms)
Reply to request 23 (704 ms)
Reply to request 24 (708 ms)
Reply to request 25 (704 ms)
Reply to request 26 (708 ms)
Reply to request 27 (740 ms)
Reply to request 28 (704 ms)
Reply to request 29 (704 ms)
Reply to request 30 (708 ms)
Reply to request 31 (704 ms)
Reply to request 32 (708 ms)
Reply to request 33 (704 ms)
Reply to request 34 (708 ms)
Reply to request 35 (704 ms)
Reply to request 36 (704 ms)
Reply to request 37 (708 ms)
Reply to request 38 (704 ms)
Reply to request 39 (708 ms)
Reply to request 40 (724 ms)
Reply to request 41 (704 ms)
Reply to request 42 (704 ms)
Reply to request 43 (708 ms)
Reply to request 44 (704 ms)
Reply to request 45 (708 ms)
Reply to request 46 (704 ms)
Reply to request 47 (708 ms)
Reply to request 48 (704 ms)
Reply to request 49 (704 ms)
Success rate is 100 percent (50/50), round-trip
min/avg/max = 704/726/1184 ms
sho at i atm int atm3/0.1
Interface ATM3/0:
AAL enabled: AAL5 , Maximum VCs: 1024, Current VCCs:
18
Maximum Transmit Channels: 64
Max. Datagram Size: 4496
PLIM Type: DS3 - 45000Kbps, Framing is C-bit ADM,
DS3 lbo: short, TX clocking: LINE
Cell-payload scrambling: OFF
13830 input, 9729 output, 2129 IN fast, 1312 OUT fast,
0 out dropCBR : 500 VBR-NRT : 128
Avail bw = 44372
Config. is ACTIVE
TOKYO#sho atm traffic
16049 Input packets
11101 Output packets
0 Broadcast packets
0 Packets received on non-existent VC
0 Packets attempted to send on non-existent VC
0 OAM cells received
F5 InEndloop: 0, F5 InSegloop: 0, F5 InAIS: 0, F5
InRDI: 0
F4 InEndloop: 0, F4 InSegloop: 0, F4 InAIS: 0, F4
InRDI: 0
0 OAM cells sent
F5 OutEndloop: 0, F5 OutSegloop: 0, F5 OutRDI: 0
F4 OutEndloop: 0, F4 OutSegloop: 0, F4 OutRDI: 0
0 OAM cell drops
TOKYO#sho int atm3/0.1
ATM3/0.1 is up, line protocol is up
Hardware is RS8234 ATM DS3
Internet address is 192.168.1.2/30
MTU 4470 bytes, BW 45000 Kbit, DLY 190 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ATM
13219 packets input, 2183359 bytes
8976 packets output,1058652 bytes
0 OAM cells input, 0 OAM cells output
AAL5 CRC errors : 0
AAL5 SAR Timeouts : 0
AAL5 Oversized SDUs : 0
AAL5 length violation : 31
AAL5 CPI Error : 28
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=13006&t=12978
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
