I have used pinging myself to discover a faulty 7206 card that was either
ds3 or oc3.
Brian "Sonic" Whalen
Success = Preparation + Opportunity
On Mon, 7 May 2001, Brian Dennis wrote:
> You should be able to ping yourself on a LAN interface without any addition
> configuration (see below). As far as a WAN environment goes there is not
too
> many reasons to ping yourself and it's a bad troubleshooting technique
> (pinging yourself that is). If you can ping the other side of the WAN link
> then it should be okay. You don't need to ping yourself after you ping the
> other side.
>
> In a WAN environment you send the echo request down the link and the other
> side bounces it back. You then answer it by sending an echo reply down the
> link and the other side bounces it back to you again. This is why pinging
> yourself on a WAN link takes twice as long as pinging the other side (see
> below).
>
> Brian
>
>
> ********* Ethernet *********
>
> R2#sho ip int brie e0/0
> Interface IP-Address OK? Method Status
> Protocol
> Ethernet0/0 172.17.1.22 YES manual up
> up
> R2#ping 172.17.1.22
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 172.17.1.22, timeout is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip min/avg/max = 1/3/4 ms
> R2#
>
>
>
> ******** Point to Point Serial ***********
>
> R1#sho ip int brie s1
> Interface IP-Address OK? Method Status
> Protocol
> Serial1 161.61.62.1 YES NVRAM up up
> R1#ping 161.61.62.2
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 161.61.62.2, timeout is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip min/avg/max = 32/33/36 ms
> R1#ping 161.61.62.1
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 161.61.62.1, timeout is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip min/avg/max = 60/61/64 ms
> R1#
>
> > -----Original Message-----
> > From: Chuck Larrieu [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, May 07, 2001 4:49 PM
> > To: Brian Dennis; [EMAIL PROTECTED]
> > Subject: RE: cannot ping myself [7:3498]
> >
> >
> > Guys, my own experiments indicate that you can't ping yourself on an
> > ethernet interface either.
> >
> > But an extended ping sourcing from another interface works fine.
> >
> > Something else that is bothering me - why do you need to ping yourself?
> > There are plenty of tools that tell you if an interface is up,
> > and if it is
> > an ip interface.
> >
> > Sh int
> > Sh ip int
> > Sh ip int brief
> >
> > I generally think of ping as a test of routing, not a test of interfaces
> > being up. Is there another reason I'm missing?
> >
> > Chuck
> >
> >
> >
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of
> > Brian Dennis
> > Sent: Monday, May 07, 2001 4:34 PM
> > To: [EMAIL PROTECTED]
> > Subject: RE: cannot ping myself [7:3498]
> >
> > You don't have a frame-relay map statement to yourself. If you
> > want to ping
> > yourself you need to add a map statement (i.e. frame-relay map ip
> > 10.10.10.1
> > 16).
> >
> > Brian
> >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> > > [EMAIL PROTECTED]
> > > Sent: Monday, May 07, 2001 3:49 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: cannot ping myself [7:3498]
> > >
> > >
> > > #sh run
> > > ...
> > > !
> > > interface Serial1
> > > description Enlace al San Alfonso (BellSouth)
> > > ip address 10.10.10.1 255.255.255.0
> > > no ip directed-broadcast
> > > encapsulation frame-relay IETF
> > > no fair-queue
> > > frame-relay interface-dlci 16
> > > frame-relay lmi-type ansi
> > > !
> > > ...
> > > #ping 10.10.10.1
> > >
> > >
> > > Type escape sequence to abort.
> > > Sending 5, 100-byte ICMP Echos to 10.10.10.1, timeout is 2 seconds:
> > > .....
> > > Success rate is 0 percent (0/5)
> > >
> > > (pinging 10.10.10.1 from other box works, but by the own router
doesn't)
> > >
> > > What can be happening?
> > >
> > > Thanks,
> > > HoraPe
> > > ---
> > > Horacio J. Peqa
> > > [EMAIL PROTECTED]
> > > [EMAIL PROTECTED]
> > > [EMAIL PROTECTED]
> > > [EMAIL PROTECTED]
> > > FAQ, list archives, and subscription info:
> > > http://www.groupstudy.com/list/cisco.html
> > > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> > FAQ, list archives, and subscription info:
> > http://www.groupstudy.com/list/cisco.html
> > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=3514&t=3498
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
