03-04-2014 11:24 PM - edited 03-04-2019 10:30 PM
Hello
I have a question which may sound silly...But if i want to ping any ip say i want to ping 1.1.1.1....so can i ping it with Multtiple MTU sizes???
like when i hit the command
Rx# ping 1.1.1.1
Then can i make each ping go with a different a Different MTU size if i want ??? by any command or something??
I want the output to be something like this....
Means each ping Goes with a different Byte Size or MTU size....
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=64 time=2ms TTL=64
Reply from 192.168.1.1: bytes=100 time=2ms TTL=64
Reply from 192.168.1.1: bytes=150 time=7ms TTL=64
Its just an example i took but it clears the concept i think
can this be done??
Thank you
Solved! Go to Solution.
03-04-2014 11:56 PM
Hi,
altough it is a duplicate post I'll reiterate my first answer: extended ping !
here's an example
R1(config)#do ping
Protocol [ip]:
Target IP address: 10.0.0.2
Repeat count [5]: 1
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]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]: y
Sweep min size [36]: 80
Sweep max size [18024]: 90
Sweep interval [1]: 5
Type escape sequence to abort.
Sending 3, [80..90]-byte ICMP Echos to 10.0.0.2, timeout is 2 seconds:
!!!
Success rate is 100 percent (3/3), round-trip min/avg/max = 24/33/44 ms
R1(config)#
*Mar 1 00:03:05.671: IP: tableid=0, s=10.0.0.1 (local), d=10.0.0.2 (FastEthernet0/0), routed via FIB
*Mar 1 00:03:05.675: IP: s=10.0.0.1 (local), d=10.0.0.2 (FastEthernet0/0), len 80, sending
*Mar 1 00:03:05.675: ICMP type=8, code=0
*Mar 1 00:03:05.715: IP: tableid=0, s=10.0.0.2 (FastEthernet0/0), d=10.0.0.1 (FastEthernet0/0), routed via RIB
*Mar 1 00:03:05.715: IP: s=10.0.0.2 (FastEthernet0/0), d=10.0.0.1 (FastEthernet0/0), len 80, rcvd 3
*Mar 1 00:03:05.715: ICMP type=0, code=0
*Mar 1 00:03:05.719: IP: tableid=0, s=10.0.0.1 (local), d=10.0.0.2 (FastEthernet0/0), routed via FIB
*Mar 1 00:03:05.719: IP: s=10.0.0.1 (local), d=10.0.0.2 (FastEthernet0/0), len 85, sending
*Mar 1 00:03:05.723: ICMP type=8, code=0
*Mar 1 00:03:05.747: IP: tableid=0, s=10.0.0.2 (FastEthernet0/0), d=10.0.0.1 (FastEthernet0/0), routed via RIB
*Mar 1 00:03:05.751: IP: s=10.0.0.2 (FastEthernet0/0), d=10.0.0.1 (FastEthernet0/0), len 85, rcvd 3
*Mar 1 00:03:05.751: ICMP type=0, code=0
*Mar 1 00:03:05.751: IP: tableid=0, s=10.0.0.1 (local), d=10.0.0.2 (FastEthernet0/0), routed via FIB
*Mar 1 00:03:05.755: IP: s=10.0.0.1 (local), d=10.0.0.2 (FastEthernet0/0), len 90, sending
*Mar 1 00:03:05.755: ICMP type=8, code=0
*Mar 1 00:03:05.775: IP: tableid=0, s=10.0.0.2 (FastEthernet0/0), d=10.0.0.1 (FastEthernet0/0), routed via RIB
*Mar 1 00:03:05.775: IP: s=10.0.0.2 (FastEthernet0/0), d=10.0.0.1 (FastEthernet0/0), len 90, rcvd 3
*Mar 1 00:03:05.775: ICMP type=0, code=0
Regards
Alain
Don't forget to rate helpful posts.
03-04-2014 11:56 PM
Hi,
altough it is a duplicate post I'll reiterate my first answer: extended ping !
here's an example
R1(config)#do ping
Protocol [ip]:
Target IP address: 10.0.0.2
Repeat count [5]: 1
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]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]: y
Sweep min size [36]: 80
Sweep max size [18024]: 90
Sweep interval [1]: 5
Type escape sequence to abort.
Sending 3, [80..90]-byte ICMP Echos to 10.0.0.2, timeout is 2 seconds:
!!!
Success rate is 100 percent (3/3), round-trip min/avg/max = 24/33/44 ms
R1(config)#
*Mar 1 00:03:05.671: IP: tableid=0, s=10.0.0.1 (local), d=10.0.0.2 (FastEthernet0/0), routed via FIB
*Mar 1 00:03:05.675: IP: s=10.0.0.1 (local), d=10.0.0.2 (FastEthernet0/0), len 80, sending
*Mar 1 00:03:05.675: ICMP type=8, code=0
*Mar 1 00:03:05.715: IP: tableid=0, s=10.0.0.2 (FastEthernet0/0), d=10.0.0.1 (FastEthernet0/0), routed via RIB
*Mar 1 00:03:05.715: IP: s=10.0.0.2 (FastEthernet0/0), d=10.0.0.1 (FastEthernet0/0), len 80, rcvd 3
*Mar 1 00:03:05.715: ICMP type=0, code=0
*Mar 1 00:03:05.719: IP: tableid=0, s=10.0.0.1 (local), d=10.0.0.2 (FastEthernet0/0), routed via FIB
*Mar 1 00:03:05.719: IP: s=10.0.0.1 (local), d=10.0.0.2 (FastEthernet0/0), len 85, sending
*Mar 1 00:03:05.723: ICMP type=8, code=0
*Mar 1 00:03:05.747: IP: tableid=0, s=10.0.0.2 (FastEthernet0/0), d=10.0.0.1 (FastEthernet0/0), routed via RIB
*Mar 1 00:03:05.751: IP: s=10.0.0.2 (FastEthernet0/0), d=10.0.0.1 (FastEthernet0/0), len 85, rcvd 3
*Mar 1 00:03:05.751: ICMP type=0, code=0
*Mar 1 00:03:05.751: IP: tableid=0, s=10.0.0.1 (local), d=10.0.0.2 (FastEthernet0/0), routed via FIB
*Mar 1 00:03:05.755: IP: s=10.0.0.1 (local), d=10.0.0.2 (FastEthernet0/0), len 90, sending
*Mar 1 00:03:05.755: ICMP type=8, code=0
*Mar 1 00:03:05.775: IP: tableid=0, s=10.0.0.2 (FastEthernet0/0), d=10.0.0.1 (FastEthernet0/0), routed via RIB
*Mar 1 00:03:05.775: IP: s=10.0.0.2 (FastEthernet0/0), d=10.0.0.1 (FastEthernet0/0), len 90, rcvd 3
*Mar 1 00:03:05.775: ICMP type=0, code=0
Regards
Alain
Don't forget to rate helpful posts.
03-05-2014 12:23 AM
Excellent!!! Thats what i wanted to know! Thank u and sorry for the duplicate Post But thank u so much sir!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide