repeat ping

[knseja001]

hi all

i am trying to use this command

router#ping <ip address> repeat 10000 in EIGRP scenario

Router#ping 10.1.1.1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.1.1.1, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/1 ms

Router#ping 10.1.1.1 repeat 10000

^

% Invalid input detected at '^' marker.

both in packet tracer and Gns3 but i get that

what could be the problem

packet tracer i checked with most of the routers then with gns3 i checked with 3600

thank you in advance

[Mark Malone]

some ios may not have the extended part syntax like that

instead just type ping hit return it will start giving you options as well one after another like below example

SWA1#ping
Protocol [ip]:
Target IP address: 1.1.1.1
Repeat count [5]: 100000
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]: y
Sweep min size [36]: 100
Sweep max size [18024]:
Sweep interval [1]:
Type escape sequence to abort.
Sending 1792500000, [100..18024]-byte ICMP Echos to 1.1.1.1, timeout is 2 seconds:

[knseja001]

thank you very much Mark, it worked :)

[harkin252]

Hi am currently doing a CCNA course at my local collage and I am working through some of the labs. At the moment I am stuck on a lab 7.3.2.7 Lab – Testing Network Connectivity with Ping and Traceroute. 

Particularly on this step.

"You can use an extended ping to observe when there is a network issue. Start the ping command to 192.168.3.3 with a repeat a count of 500. "

I have tried the command suggested of 

ping 192.168.3.3 repeat 500

but keep getting the error 

% Invalid input detected at '^' marker.

with the ^ pointing at r in repeat from below. 

I have tried entering the ping command and then entering the IP address sepratly on the next coomand line in the hope the it could allow me to specify how many echo or pings I want to send in this case 500.

But no luck it just does the normal ping command.

Can you guys help me. 

I have uploaded a copy of the PDF for the lab. 

The part I am stuck on is.

Part 2: Use Ping Command for Basic Network Testing

Step 3: Test network connectivity from the LOCAL network using Cisco devices.

d. You can use an extended ping to observe when there is a network issue. Start the ping command to
192.168.3.3 with a repeat a count of 500. Then, disconnect the cable between the REMOTE router and
the S3 switch or shut down the GigabitEthernet 0/1 interface on the REMOTE router.

[Richard Burts]

Is it possible that you are trying this in user mode rather than in privilege mode?

Are you doing this in a simulator (GNS3 or packet tracer or something) or on a physical router?

HTH

Rick

[harkin252]

Hi Rick yeah am using packet tracer. I think I was in privilege mode as  typed enable before ruining the commands.

[Devaa]

Hi @harkin252 

In Packet Tracker, repeat option is not available with ping command. But in real devices and in emulated tools like GNS3 and EVE-NG, you'll see the repeat option. 

SO in PT, you have to use the below method for repeated pings. 

Router#ping 
Protocol [ip]: 
Target IP address: 10.0.0.1
Repeat count [5]: 50
Datagram size [100]: 
Timeout in seconds [2]: 
Extended commands [n]: 
Sweep range of sizes [n]: 
Type escape sequence to abort.
Sending 50, 100-byte ICMP Echos to 10.0.0.1, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent (50/50), round-trip min/avg/max = 0/0/1 ms

Router#

[Joseph W. Doherty]

"But in real devices and in emulated tools like GNS3 and EVE-NG, you'll see the repeat option."

BTW, on pretty old platforms or IOSs, you will NOT find the prompted ping options on a single ping command line either (I remember when the additional single ping command line options started to appear on the newest platforms and IOSs - a nice enhancement, IMO).  But, PT, even when current, often is missing many configuration options (also those it does have may not function as they do on real devices).

Oh, in another recent thread, it seems ping uses different default packet contents whether you use just the single command line versus the prompted variant.  Normally, that shouldn't matter in almost all ping use cases.

[qusay]

I am experiencing an issue with continuous ping not working in Packet Tracer. Despite ensuring that my devices are properly configured and connected, the ping command only runs once instead

[Joseph W. Doherty]

Very possibly just a limitation of PT, as it's a teaching tool not an emulator.

If you desire more more faithful replication of actual Cisco device operation, you might look into CML.