From: Scott Morris (smorris@ipexpert.com)
Date: Wed Jun 13 2007 - 10:13:55 ART
With a multicast ping, it will send it out all AVAILABLE interfaces... So
if you only want to send out one way, take off the PIM modes on other
interfaces? :)
Otherwise, step through the options.
Doing it all on one line is a fairly recent (well, ok, a few years now)
addition, and it really is just the more "common" things selected, not EVERY
option from stepping through the extended ping options.
HTH,
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713, JNCIE
#153, CISSP, et al.
CCSI/JNCI-M/JNCI-J
VP - Technical Training - IPexpert, Inc.
IPexpert Sr. Technical Instructor
A Cisco Learning Partner - We Accept Learning Credits!
smorris@ipexpert.com
Telephone: +1.810.326.1444
Fax: +1.810.454.0130
http://www.ipexpert.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Bit
Gossip
Sent: Tuesday, June 12, 2007 11:57 PM
To: Douglas M Todd, Jr
Cc: ccielab
Subject: Re: Extended ping in one line
From my testing I noticed that if you do a multicast ping like this:
ping 239.239.239.239 source lo0
the source address of the multicast packets have the address of lo0 as
source address but they are sent out of all interfaces. While in the
extended ping there is also the possibility to specify the egress interface.
So we should conclude that there is no other way of specifying the output
interface than to use the extended ping which is quite time consuming?
Bit
----- Original Message -----
From: "Douglas M Todd, Jr" <dtodd@partners.org>
To: "Bit Gossip" <bit.gossip@chello.nl>
Cc: "ccielab" <ccielab@groupstudy.com>
Sent: Monday, June 11, 2007 10:13 PM
Subject: Re: Extended ping in one line
> Sure See below:
>
> Basics after a ping:
>
> Router#ping ip 172.16.1.1 ?
> data specify data pattern
> df-bit enable do not fragment bit in IP header
> repeat specify repeat count
> size specify datagram size
> source specify source address or name
> timeout specify timeout interval
> validate validate reply data
> <cr>
>
> Used:
>
> Router#ping ip 172.16.1.1 source lo0 repeat 1 timeout 1
>
> Then you Get Pinging:
> !
>
> Save you lots of time
>
> I use a script like:
>
> foreach i {
> 1.1.1.1
> 2.2.2.2
> 3.3.3.3
> 4.4.4.4
> } {ping $address repeat 1}
>
> This saves lots of time especially when you have problems with
> reachability.
>
> DMT
>
> Bit Gossip wrote:
>> Group,
>> for testing multicast the following ping is useful because allow to
>> specify the outgoing interface; but it is very tedious and time
>> consuming because one has to type in every option every time.
>>
>> Rack1R6#ping
>> Protocol [ip]: Target IP address: 239.239.239.239
>> Repeat count [1]: 10
>> Datagram size [100]: Timeout in seconds [2]: Extended commands [n]: y
>> Interface [All]: FastEthernet0/0
>> Time to live [255]: Source address: 192.10.1.6
>> 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]: Type escape sequence to abort.
>> Sending 10, 100-byte ICMP Echos to 239.239.239.239, timeout is 2
>> seconds:
>> Packet sent with a source address of 192.10.1.6 On the other side the
>> following one liner is not equivalent because in
>> this case
>> ping ip 239.239.239.239 source FastEthernet0/0 repeat 10
>> packet are source with the IP address of f0/0 but sent out ALL
>> interfaces
>>
>> Question: is there a way to create a one liner that does all the
>> extended ping does, in particular source address AND egress interface?
>> Maybe TCL?
>>
>> Thanks,
>> Bit.
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
> The information transmitted in this electronic communication is intended
> only for the person or entity to whom it is addressed and may contain
> confidential and/or privileged material. Any review, retransmission,
> dissemination or other use of or taking of any action in reliance upon
> this information by persons or entities other than the intended recipient
> is prohibited. If you received this information in error, please contact
> the Compliance HelpLine at 800-856-1983 and properly dispose of this
> information.
This archive was generated by hypermail 2.1.4 : Sun Jul 01 2007 - 17:24:48 ART