From: Ramya S (ramya_1975@hotmail.com)
Date: Sat Jun 16 2007 - 04:18:09 ART
Hello Tarun,
Thank you for the reply.
The method you suggested seems to be the best way. I think many big sp's use
what you suggested . If the vpn customers are using private addresses then we
can use vrf aware nat. Should we use nat at the local pe router or at the
remote internet pe router? Which would be a better way to accomplish?
Thanks,
Ramya Sen
> Date: Sat, 16 Jun 2007 04:19:27 +0530> From: pahujat@gmail.com> To:
ramya_1975@hotmail.com> Subject: Re: Internet access for MPLS VPN customers>
CC: ccielab@groupstudy.com> > Ramya,> The most common way to provide Internet
access to VPN> customers that I have seen is by providing them with a default
route. The> VPN provider implements an Internet Vrf where it receives all the
routes> from the Internet. This vrf also contains a default route generated by
the> internet gateway. Customer Vrfs import this default default and export
their> network routes to the Internet vrf for network reachability.> > CCO
mentions about some other ways of providing Internet connectivity to>
customers, the following examples talks about using global routing table to>
provide Internet connectivity.> >
http://www.cisco.com/warp/public/105/internet_access_mpls_vpn.html> > HTH,>
Tarun Pahuja> CCIE#7707(R&S,Security,SP,Voice,Storage),CCSI> >
This archive was generated by hypermail 2.1.4 : Sun Jul 01 2007 - 17:24:49 ART