Re: Unable to Configure MPLS VPN in the below Scenario

Hi,

I havent gone through the full configuration. You must configure MPLS (label
switching) on the links between PE and P routers.

eg:
PE1(config)#ip cef
PE1(config)#mpls ip
PE1(config)#mpls label protocol ldp

#enable mpls ip for the interfaces in the provider core

PE1(config)#int e0/2 # interface connecting to P router
PE1(config-if)#mpls ip

Do the same on the P router as well.

Regards

On Tue, Apr 7, 2009 at 1:28 PM, Akber Ali Mirza <akberali.cisco_at_gmail.com>wrote:

> Hi Experts,
>
> Could you please give your Valuable posts on my below MPLS VPN query.
>
> Highly appreciate your efforts.
>
> Thanks and Regards,
> Akber Mirza.
>
> On Mon, Apr 6, 2009 at 6:34 PM, Akber Ali Mirza <akberali.cisco_at_gmail.com
> >wrote:
>
> > Hi GS,
> >
> > I have tried configuring MPLS VPN with the following details, with out
> any
> > success!
> >
> > can any one tell me What should be configured on the P Router.
> > Can any one go through the config and commment if i missed out any basic.
> >
> > R4- P-Router
> > R3/R5/R6 - PE Router
> > R1/R2/R7/R8 - CE router.
> > Does MPLS works on 7200 Router with IOS in GNS3 LAB -----
> > c7200-jk9s-mz.124-23.bin ( Including P/PE/CE routers)
> >
> > Attached diagram will give you more details on IP and AS numbers .
> >
> > R7 ( CE -Customer A)
> > |
> > |
> > R6( PE Router)
> > |
> > |
> > R3( PE Router)--------------R4(P Router)-----------------R5( PE
> > Router)--------------------------R8( CE CustomerB)
> > | |
> > | |
> > R1 ( CE CustomerB) R2 ( CE -CustomerA)
> >
> >
> >
> > I have tried the below config -
> >
> >
> > R3:
> >
> > ip vrf CustB
> > description Customer B
> > rd 1:1
> > route-target export 1:1
> > route-target import 1:1
> > R5:
> >
> > ip vrf CustA
> > description Customer A
> > rd 2:1
> > route-target export 2:1
> > route-target import 2:1
> > !
> > ip vrf CustB
> > description Customer B
> > rd 1:1
> > route-target export 1:1
> > route-target import 1:1
> > R6:
> >
> > ip vrf CustA
> > description Customer A
> > rd 2:1
> > route-target export 2:1
> > route-target import 2:1
> >
> > R3:
> >
> > interface Serial1/0
> > ip vrf forwarding CustB
> > ip address 192.168.13.1 255.255.255.252
> > R5:
> >
> > interface Serial1/0
> > ip vrf forwarding CustA
> > ip address 192.168.25.1 255.255.255.252
> >
> > interface Serial1/2
> > ip vrf forwarding CustB
> > ip address 192.168.58.1 255.255.255.252
> > R6:
> >
> > interface Serial1/2
> > ip vrf forwarding CustA
> > ip address 192.168.67.1 255.255.255.252
> >
> >
> >
> > R1:
> >
> > router bgp 1
> > bgp router-id 150.1.1.1
> > redistribute connected
> > neighbor 192.168.13.1 remote-as 101
> > no auto-summary
> > R2:
> >
> > router bgp 2
> > bgp router-id 150.1.2.2
> > redistribute connected
> > neighbor 192.168.25.1 remote-as 101
> > no auto-summary
> > R7:
> >
> > router bgp 7
> > bgp router-id 150.1.7.7
> > redistribute connected
> > neighbor 192.168.67.1 remote-as 101
> > no auto-summary
> > R8:
> >
> > router bgp 8
> > bgp router-id 150.1.8.8
> > redistribute connected
> > neighbor 192.168.58.1 remote-as 101
> > no auto-summary
> >
> >
> >
> > R3:
> >
> > router bgp 101
> > bgp router-id 150.1.3.3
> > no bgp default ipv4-unicast
> > neighbor 192.168.13.2 remote-as 1
> > !
> > address-family ipv4 vrf CustB
> > neighbor 192.168.13.2 remote-as 1
> > neighbor 192.168.13.2 activate
> > exit-address-family
> > R5:
> >
> > router bgp 101
> > bgp router-id 150.1.5.5
> > no bgp default ipv4-unicast
> > neighbor 192.168.25.2 remote-as 2
> > neighbor 192.168.58.2 remote-as 8
> > !
> > address-family ipv4 vrf CustA
> > neighbor 192.168.25.2 remote-as 2
> > neighbor 192.168.25.2 activate
> > exit-address-family
> > !
> > address-family ipv4 vrf CustB
> > neighbor 192.168.58.2 remote-as 8
> > neighbor 192.168.58.2 activate
> > exit-address-family
> > R6:
> >
> > router bgp 101
> > bgp router-id 150.1.6.6
> > no bgp default ipv4-unicast
> > neighbor 192.168.67.2 remote-as 7
> > !
> > address-family ipv4 vrf CustA
> > neighbor 192.168.67.2 remote-as 7
> > neighbor 192.168.67.2 activate
> > exit-address-family
> >
> > R3:
> >
> > router bgp 101
> > neighbor 150.1.5.5 remote-as 101
> > neighbor 150.1.5.5 update-source lo0
> > neighbor 150.1.6.6 remote-as 101
> > neighbor 150.1.6.6 update-source lo0
> > !
> > address-family vpnv4
> > neighbor 150.1.5.5 activate
> > neighbor 150.1.5.5 send-community extended
> > neighbor 150.1.6.6 activate
> > neighbor 150.1.6.6 send-community extended
> > exit-address-family
> > R5:
> >
> > router bgp 101
> > neighbor 150.1.3.3 remote-as 101
> > neighbor 150.1.3.3 update-source lo0
> > neighbor 150.1.6.6 remote-as 101
> > neighbor 150.1.6.6 update-source lo0
> > !
> > address-family vpnv4
> > neighbor 150.1.3.3 activate
> > neighbor 150.1.3.3 send-community extended
> > neighbor 150.1.6.6 activate
> > neighbor 150.1.6.6 send-community extended
> > exit-address-family
> > R6:
> >
> > router bgp 101
> > neighbor 150.1.3.3 remote-as 101
> > neighbor 150.1.3.3 update-source lo0
> > neighbor 150.1.5.5 remote-as 101
> > neighbor 150.1.5.5 update-source lo0
> > !
> > address-family vpnv4
> > neighbor 150.1.3.3 activate
> > neighbor 150.1.3.3 send-community extended
> > neighbor 150.1.5.5 activate
> > neighbor 150.1.5.5 send-community extended
> > exit-address-family
> >
> >
> >
> > Sincerely would Appreciate your efforts and comments on this Task.
> >
> > Warm Regards,
> > Akber Mirza.
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Tue Apr 07 2009 - 14:09:13 ART