[c-nsp] Megapath frame relay question

[Vinny_Abello at Dell.com]

This may also be relevant and helpful in this situation:

http://blog.ine.com/2009/12/03/ping-thyself-yet-again-pppofr/

-Vinny

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Scott Granados
Sent: Thursday, February 23, 2012 5:02 PM
To: Bill
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Megapath frame relay question

Ok, few points.

FIrst, yes, Megapath is going to assign you a 172.16 address to your wan interface.  This is a pretty standard Covad / Megapath thing.

Next, when I've done this is memory served I had to use a dialer interface for the actual interface and bind that to a sub interface using a dialer pool

You should see something like a standard interface when you show the dialer that includes the IP assigned.
Then you set your default route with ip route 0.0.0.0 0.0.0.0 interface dialer1
and it should work, at least as well as Megapath circuits ever work which is definitely not that well.  If you google Cisco PPP over FR you should find the example I used as the first or second listing with a great config example.

GOod luck


On Feb 23, 2012, at 1:09 PM, Bill wrote:

> Dear Cisco gurus,
> 
> I have the following simple config for a frame-relay T1 on Megapath's 
> network:
> 
> interface FastEthernet0/0
> ip address x.x.x.x x.x.x.x !!!!!!!!!!!!(publicly addressable /29)
> duplex auto
> speed auto
> !
> interface Serial0/0
> no ip address
> encapsulation frame-relay IETF
> no fair-queue
> frame-relay interface-dlci 16 ppp Virtual-Template1 !!!!!!!!!(I've seen 
> examples where this line is entered on a sub-interface - not sure if this 
> matters)
> frame-relay lmi-type ansi
> !
> interface Virtual-Template1
> ip address negotiated
> ppp chap hostname username at bz8
> ppp chap password 0 password
> ppp ipcp dns request
> ppp ipcp route default
> ppp ipcp address accept
> !
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> The issue I have is, there's no connectivity from the router itself. 
> Anything behind the router - using the LAN IP block - works fine.  For 
> example, within the Cisco CLI, if I issue the ping command by itself, I get 
> no reply.  If I issue the ping command & specify that the source address is 
> the IP on the FastE interface, then I get replies.
> 
> This seems to me like an issue with the way Megapath provisions these 
> circuits but I'm trying to see if there's a simple way to workaround the 
> issue.  Such as making ALL traffic from the router appear to originate from 
> the IP on the FastE interface.
> 
> Thanks in advance for your help/replies.
> 
> Bill 
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/


_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/