Re: Frame-Relay self ping on PPP

Hi Scott

Thanks for your input

Based on my tests you do not have to create the actual interface multilink
for this to work.
Simply putting "ppp multilink" under the virtual temp does the job.
I believe its more of a case of the properties of the virtual-access
interface that is created when you configure ppp multilink.

R1
interface Serial0/0.12 point-to-point
 snmp trap link-status
 frame-relay interface-dlci 102 ppp Virtual-Template12
interface Virtual-Template12
 ip address 10.1.12.1 255.255.255.0
* ppp multilink*

R2
interface Serial0/0.21 point-to-point
 snmp trap link-status
 frame-relay interface-dlci 201 ppp Virtual-Template21
interface Virtual-Template21
 ip address 10.1.12.2 255.255.255.0
* ppp multilink*

Testing:

R1#ping 10.1.12.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.12.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms

R2#ping 10.1.12.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.12.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms

Regards
Roy

2009/8/24 Scott Morris <swm_at_emanon.com>

> The "interface multilink" actually allows you to ping it. Since the
> interface is there, and is "up" by virtue of having a participating Layer2
> connection in the bundle, it's reachable. It is not dependent on the
> template.
>
> Kind of a strange thing in the "order" that IOS looks at things in
> determining reachability. With PPPoFR, you are pulling your address from
> the virtual template. For many things, IOS treats the template LIKE an
> interface (hence your show commands) although it really cannot move
> traffic. So when it shows up first in the list of "where is this IP so I
> can ping it" nothing actually works.
>
> A multilink interface on the other hand is actually used for moving IP
> traffic and passing it off to the bundle member Layer2 links, so it IS a
> viable interface and thus you can ping it.
>
> Sorry about not noticing Joe had already responded to the initial message.
> :)
>
> HTH,
>
>
>
>
> *Scott Morris*, CCIE*x4* (R&S/ISP-Dial/Security/Service Provider) #4713,
>
> JNCIE-M #153, JNCIS-ER, CISSP, et al.
>
> CCSI #21903, JNCI-M, JNCI-ER
>
> swm_at_emanon.com
>
>
> Knowledge is power.
>
> Power corrupts.
>
> Study hard and be Eeeeviiiil......
>
>
> Roy Waterman wrote:
>
> Hey Joe
> This is great.
> Could you explain why self ping works using mlpppofr as opposed to pppofr?
> Is there some logical reason for it?
> Also, could you also explain the ip numbered lo0 serial solution? Pinging
> your own ip is no problem with this, but pinging the other end of the link
> results in...issues.
>
> In my scenario:
>
> lo0 --- R3 s0/0.34 ---------------s0/0.43 R4 --- lo0
>
> R3
> int s0/0.34 p
> ip unnumbered lo0
> frame int 304
> int lo0
> ip add 10.1.34.3 255.255.255.0
>
> R4
> int s0/0.43 p
> ip unnumbered lo0
> frame int 403
> int lo0
> ip add 10.1.34.4 255.255.255.0
>
> R3 can self ping but cannot ping R4, as 10.1.34.4 points to lo0...
>
> R3#ping 10.1.34.3
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 10.1.34.3, timeout is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
> R3#ping 10.1.34.4
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 10.1.34.4, timeout is 2 seconds:
> .....
> Success rate is 0 percent (0/5)
>
> R3#sh ip ro 10.1.34.4
> Routing entry for 10.1.34.0/24
> Known via "connected", distance 0, metric 0 (connected, via interface)
> Routing Descriptor Blocks:
> * directly connected, via Loopback0
> Route metric is 0, traffic share count is 1
>
>
> Could you show how you managed to get around this?
>
> Cheers man.
>
>
>
> 2009/8/24 Joe Astorino <jastorino_at_ipexpert.com> <jastorino_at_ipexpert.com>
>
> You need either ppp multilink over frame or setup ip unnumbered and point
> it to a loopback
>
>
> ------Original Message------
> From: Sameer Khurana
> Sender: nobody_at_groupstudy.com
> To: CCIE Groupstudy
> ReplyTo: Sameer Khurana
> Subject: Frame-Relay self ping on PPP
> Sent: Aug 23, 2009 10:55 PM
>
> Hi Group,
>
> If there is a P2P serial connections, for example:
>
> R1:
> ===
> S1:
> en fr
> no fram inv
> !
> int S1.1 po
> fram interface-dlci 102 ppp virtual-tem 1
> !
> int virtual-tem 1
> ip add 1.1.1.1 255.255.255.0
>
>
> R2:
> ===
> S1:
> en fr
> no fram inv
> !
> int S1.1 po
> fram interface-dlci 201 ppp virtual-tem 1
> !
> int virtual-tem 1
> ip add 1.1.1.2 255.255.255.0
>
> If we have to do self ping our own serial interfaces then what we need to
> do? Means... R1 should ping its own 1.1.1.1 and R2 should ping 1.1.1.2.
>
> Thanks,
> Sameer
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>
>
> Regards,
>
> Joe Astorino - CCIE #24347 R&S
> Technical Instructor - IPexpert, Inc.
> Cell: +1.586.212.6107
> Fax: +1.810.454.0130
> Mailto: jastorino_at_ipexpert.com
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>
>

-- 
Regards
Roy
Blogs and organic groups at http://www.ccie.net