Re: MPLS VPN - difficulties in last level trouble shooting

Could you show us the R4 P router? Show mpls forwarding table, ldp
neighbor, mpls interfaces?

Thanks
Rich

On Sun, Apr 26, 2009 at 4:51 AM, Akber Ali Mirza
<akberali.cisco_at_gmail.com> wrote:
> Experts,
>
> *can you plz let me know why i am unable to achive the below PING tasks*
>
> Configured the following command on the PE-P connected interfaces.
> on Routers R4, R4, R5 routers.
> mpls ip
> mpls label protocol ldp
> mpls ldp advertise-labels
>
> *Currently i'm Unbale to ping from below PE routers to CE routers -*
>
> *R3 #ping vrf CustB 172.31.8.1 ( Router8 Lo ip , belongs to CustB VRF)....0%
> success rate*
> R3 #ping vrf CustB 172.31.1.1 ( Router1 Lo ip , belongs to CustB VRF)..100%
> success rate
>
> *R5 #ping vrf CustA 172.31.7.1 ( Router7 Lo ip, belongs to CustA VRF)..0%
> success rate.*
> R5 #ping vrf CustA 172.31.2.1 ( Router2 Lo ip, belongs to CustA VRF)...100%
> success rate
>
> R1 , R8 are belong to VRF CustB CE routers. ( ips are 172.31.1 /172.32.8.1)
> R2, R7 are belongs to VRF CustA CE routers. ( ips are 172.31.2.1 /172.31.7.1
> )
>
> Appreciate your response on this.
>
>
> Thanks ,
> Mirza.
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> On Sun, Apr 26, 2009 at 1:45 PM, Akber Ali Mirza
> <akberali.cisco_at_gmail.com>wrote:
>
>> Sorry missed out PE router R3/R5 output :-
>>
>> R3#sh ip bgp vpnv4 all sum
>> BGP router identifier 150.1.3.3, local AS number 101
>> BGP table version is 10, main routing table version 10
>> 6 network entries using 822 bytes of memory
>> 6 path entries using 408 bytes of memory
>> 5/2 BGP path/bestpath attribute entries using 620 bytes of memory
>> 2 BGP AS-PATH entries using 48 bytes of memory
>> 1 BGP extended community entries using 24 bytes of memory
>> 0 BGP route-map cache entries using 0 bytes of memory
>> 0 BGP filter-list cache entries using 0 bytes of memory
>> BGP using 1922 total bytes of memory
>> BGP activity 10/1 prefixes, 11/2 paths, scan interval 15 secs
>> Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
>> State/PfxRcd
>> 150.1.5.5 4 101 24 23 10 0 0 00:18:27
>> 3
>> 150.1.6.6 4 101 2373 2374 10 0 0 1d15h
>> 0
>> 192.168.13.2 4 1 2370 2370 10 0 0 1d15h
>> 3
>> R3#sh mpls for
>> Local Outgoing Prefix Bytes tag Outgoing Next Hop
>> tag tag or VC or Tunnel Id switched interface
>> 16 Untagged 192.168.67.0/24 0 Se1/1 point2point
>> 17 Untagged 192.168.25.0/24 0 Gi2/0 192.168.34.2
>> 18 Untagged 192.168.58.0/24 0 Gi2/0 192.168.34.2
>> 19 Untagged 150.1.5.5/32 0 Gi2/0 192.168.34.2
>> 20 Untagged 150.1.6.6/32 0 Se1/1 point2point
>> 21 Untagged 192.168.13.0/24[V] <http://192.168.13.0/24%5BV%5D> \
>> 0 Se1/0 point2point
>> 22 Untagged 172.31.1.0/24[V] <http://172.31.1.0/24%5BV%5D>
>> 0 Se1/0 point2point
>> 23 Untagged 150.1.1.1/32[V] <http://150.1.1.1/32%5BV%5D>
>> 0 Se1/0 point2point
>> +++++++++++++++++++++++++++++++++++++++++++++++++++++
>> R5#sh ip bgp vpnv4 all sum
>> BGP router identifier 150.1.5.5, local AS number 101
>> BGP table version is 19, main routing table version 19
>> 12 network entries using 1644 bytes of memory
>> 12 path entries using 816 bytes of memory
>> 8/4 BGP path/bestpath attribute entries using 992 bytes of memory
>> 4 BGP AS-PATH entries using 96 bytes of memory
>> 2 BGP extended community entries using 48 bytes of memory
>> 0 BGP route-map cache entries using 0 bytes of memory
>> 0 BGP filter-list cache entries using 0 bytes of memory
>> BGP using 3596 total bytes of memory
>> BGP activity 17/2 prefixes, 17/2 paths, scan interval 15 secs
>> Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
>> State/PfxRc
>> 150.1.3.3 4 101 26 27 19 0 0 00:21:26
>> 3
>> 150.1.6.6 4 101 2375 2377 19 0 0 1d15h
>> 3
>> 192.168.25.2 4 2 2367 2367 19 0 0 1d15h
>> 3
>> 192.168.58.2 4 8 2363 2362 19 0 0 1d15h
>> 3
>> R5#sh mpls for
>> R5#sh mpls forwarding-table
>> Local Outgoing Prefix Bytes tag Outgoing Next Hop
>> tag tag or VC or Tunnel Id switched interface
>> 16 Untagged 192.168.67.0/24 0 Se1/0 point2point
>> 17 Untagged 192.168.13.0/24 0 Gi2/0 192.168.45.2
>> 18 Untagged 150.1.3.3/32 0 Gi2/0 192.168.45.2
>> 19 Untagged 150.1.6.6/32 0 Se1/0 point2point
>> 20 Untagged 192.168.25.0/24[V] <http://192.168.25.0/24%5BV%5D> \
>> 0 Se1/2 point2point
>> 21 Untagged 172.31.2.0/24[V] <http://172.31.2.0/24%5BV%5D>
>> 0 Se1/2 point2point
>> 22 Untagged 150.1.2.2/32[V] <http://150.1.2.2/32%5BV%5D>
>> 0 Se1/2 point2point
>> 23 Untagged 192.168.58.0/24[V] <http://192.168.58.0/24%5BV%5D> \
>> 0 Se1/1 point2point
>> 24 Untagged 150.1.8.8/32[V] <http://150.1.8.8/32%5BV%5D>
>> 0 Se1/1 point2point
>> 25 Untagged 172.31.8.0/24[V] <http://172.31.8.0/24%5BV%5D>
>> 0 Se1/1 point2point
>>
>> Regards,
>> Mirza.
>>
>> On Sun, Apr 26, 2009 at 1:19 PM, Akber Ali Mirza <akberali.cisco_at_gmail.com
>> > wrote:
>>
>>> Hello Smith,
>>>
>>> I want to achive the below mentioned Tasks , plz check on my config &
>>> below output and see where i am missing config.
>>>
>>> Plz see below the outputs-
>>>
>>> R3#sh ip bgp vpnv4 all sum
>>> BGP router identifier 150.1.3.3, local AS number 101
>>> BGP table version is 10, main routing table version 10
>>> 6 network entries using 822 bytes of memory
>>> 6 path entries using 408 bytes of memory
>>> 5/2 BGP path/bestpath attribute entries using 620 bytes of memory
>>> 2 BGP AS-PATH entries using 48 bytes of memory
>>> 1 BGP extended community entries using 24 bytes of memory
>>> 0 BGP route-map cache entries using 0 bytes of memory
>>> 0 BGP filter-list cache entries using 0 bytes of memory
>>> BGP using 1922 total bytes of memory
>>> BGP activity 10/1 prefixes, 11/2 paths, scan interval 15 secs
>>> Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
>>> State/PfxRcd
>>> 150.1.5.5 4 101 24 23 10 0 0 00:18:27
>>> 3
>>> 150.1.6.6 4 101 2373 2374 10 0 0 1d15h
>>> 0
>>> 192.168.13.2 4 1 2370 2370 10 0 0 1d15h
>>> 3
>>> R3#sh mpls for
>>> Local Outgoing Prefix Bytes tag Outgoing Next Hop
>>> tag tag or VC or Tunnel Id switched interface
>>> 16 Untagged 192.168.67.0/24 0 Se1/1 point2point
>>> 17 Untagged 192.168.25.0/24 0 Gi2/0 192.168.34.2
>>> 18 Untagged 192.168.58.0/24 0 Gi2/0 192.168.34.2
>>> 19 Untagged 150.1.5.5/32 0 Gi2/0 192.168.34.2
>>> 20 Untagged 150.1.6.6/32 0 Se1/1 point2point
>>> 21 Untagged 192.168.13.0/24[V] <http://192.168.13.0/24%5BV%5D> \
>>> 0 Se1/0 point2point
>>> 22 Untagged 172.31.1.0/24[V] <http://172.31.1.0/24%5BV%5D>
>>> 0 Se1/0 point2point
>>> 23 Untagged 150.1.1.1/32[V] <http://150.1.1.1/32%5BV%5D>
>>> 0 Se1/0 point2point
>>> +++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> R5#sh ip bgp vpnv4 all sum
>>> BGP router identifier 150.1.5.5, local AS number 101
>>> BGP table version is 19, main routing table version 19
>>> 12 network entries using 1644 bytes of memory
>>> 12 path entries using 816 bytes of memory
>>> 8/4 BGP path/bestpath attribute entries using 992 bytes of memory
>>> 4 BGP AS-PATH entries using 96 bytes of memory
>>> 2 BGP extended community entries using 48 bytes of memory
>>> 0 BGP route-map cache entries using 0 bytes of memory
>>> 0 BGP filter-list cache entries using 0 bytes of memory
>>> BGP using 3596 total bytes of memory
>>> BGP activity 17/2 prefixes, 17/2 paths, scan interval 15 secs
>>> Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
>>> State/PfxRc
>>> 150.1.3.3 4 101 26 27 19 0 0 00:21:26
>>> 3
>>> 150.1.6.6 4 101 2375 2377 19 0 0 1d15h
>>> 3
>>> 192.168.25.2 4 2 2367 2367 19 0 0 1d15h
>>> 3
>>> 192.168.58.2 4 8 2363 2362 19 0 0 1d15h
>>> 3
>>> R5#sh mpls for
>>> R5#sh mpls forwarding-table
>>> Local Outgoing Prefix Bytes tag Outgoing Next Hop
>>> tag tag or VC or Tunnel Id switched interface
>>> 16 Untagged 192.168.67.0/24 0 Se1/0 point2point
>>> 17 Untagged 192.168.13.0/24 0 Gi2/0 192.168.45.2
>>> 18 Untagged 150.1.3.3/32 0 Gi2/0 192.168.45.2
>>> 19 Untagged 150.1.6.6/32 0 Se1/0 point2point
>>> 20 Untagged 192.168.25.0/24[V] <http://192.168.25.0/24%5BV%5D> \
>>> 0 Se1/2 point2point
>>> 21 Untagged 172.31.2.0/24[V] <http://172.31.2.0/24%5BV%5D>
>>> 0 Se1/2 point2point
>>> 22 Untagged 150.1.2.2/32[V] <http://150.1.2.2/32%5BV%5D>
>>> 0 Se1/2 point2point
>>> 23 Untagged 192.168.58.0/24[V] <http://192.168.58.0/24%5BV%5D> \
>>> 0 Se1/1 point2point
>>> 24 Untagged 150.1.8.8/32[V] <http://150.1.8.8/32%5BV%5D>
>>> 0 Se1/1 point2point
>>> 25 Untagged 172.31.8.0/24[V] <http://172.31.8.0/24%5BV%5D>
>>> 0 Se1/1 point2point
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> >> > Please help me to configure MPLS VPN in GNS3( 7200 router) lab with
>>> the
>>> >> > following Diagram/Configuration/output commands.
>>> >> >
>>> >> >
>>> >> > Currently my E-BGP ( R1&R3 ; R2,R8 &R5 ; R7&R6) & MP-BGP between
>>> R3,R5
>>> >> > &R6 are working fine.
>>> >> >
>>> >> > R1.& R8 belongs to Cust B and R2 & R7 belongs to Cust A.
>>> >> > R3/R5/R6 are PE routers
>>> >> > R4-P router.
>>> >> > R1/R2/R7/R8 are CE routers.
>>> >> >
>>> >> > I have configured MPLS VPN using above scenario & configs , *but
>>> unbale
>>> >> > to achieve the below* -
>>> >> >
>>> >> > 1) ping from R1 to R8 IP (as they are within CustB)
>>> >> > 2) ping R3 to R5 IP's & R3 to R4's IP 192.168.45.2 ( plz chk if any
>>> >> > routing issue between R3-R4-R5 )
>>> >> > 3) ping from R3 to R8 Interface IP.
>>> >> >
>>> >> >
>>> >> > I am finding difficulties to do the last level trouble shooting to
>>> get
>>> >> the
>>> >> > above queries working fine!
>>> >> >
>>> >> > I sincerely appreciate and thankful for all your suggestions &
>>> replies.
>>> >> >
>>> >> > Please let me know if any further information needed for you to
>>> trouble
>>> >> > shoot my issue.
>>> >> >
>>> On Thu, Apr 23, 2009 at 2:48 PM, Shaughn Smith <
>>> Shaughn.Smith_at_mtnbusiness.co.za> wrote:
>>>
>>>> Doesn't look like MPLS is enabled.
>>>>
>>>> Do a sh mpls forwarding-table and check the output, I suspect you don't
>>>> have a label switched path for the VPN traffic to use
>>>>
>>>> -----Original Message-----
>>>> From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of
>>>> Bryan Bartik
>>>> Sent: Wednesday, April 22, 2009 4:09 AM
>>>> To: Akber Ali Mirza
>>>> Cc: CCIE Lab
>>>> Subject: Re: MPLS VPN - difficulties in last level trouble shooting
>>>>
>>>> Is this all your config? Do you have MPLS enabled on the interfaces?
>>>>
>>>> Bryan Bartik
>>>> CCIE #23707, CCNP
>>>> Sr. Support Engineer - IPexpert, Inc.
>>>> URL: http://www.IPexpert.com <http://www.ipexpert.com/>
>>>>
>>>> On Tue, Apr 21, 2009 at 10:10 AM, Akber Ali Mirza
>>>> <akberali.cisco_at_gmail.com>wrote:
>>>>
>>>> > Hi GS,
>>>> >
>>>>
>>>> > Hence pasting my Configuration & Diagram in below -
>>>> >
>>>> > Example
>>>> >
>>>> >
>>>> >
>>>> > *MPLS Configuraion using above diagram*
>>>> > **
>>>> > +++++++++++++++++++++++++++++++++++++++++++++++
>>>> > R1:
>>>> > int se 1/0
>>>> > no shut
>>>> > ip add 192.168.13.2 255.255.255.0
>>>> > int lo 0
>>>> > ip add 150.1.1.1 255.255.255.255
>>>> > int Lo 1
>>>> > ip add 172.31.1.1 255.255.255.0
>>>> > no shut
>>>> > router bgp 1
>>>> > bgp router-id 150.1.1.1
>>>> > no synchr
>>>> > redistribute connected
>>>> > neighbor 192.168.13.1 remote-as 101
>>>> > no auto-summary
>>>> > exit
>>>> > router rip
>>>> > ver 2
>>>> > no auto-sum
>>>> > network 172.31.1.0
>>>> > +++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> > R2:
>>>> > int ser 1/0
>>>> > no shut
>>>> > ip add 192.168.25.2 255.255.255.0
>>>> > int lo 0
>>>> > ip add 150.1.2.2 255.255.255.255
>>>> > int Lo 1
>>>> > ip add 172.31.2.1 255.255.255.0
>>>> > router bgp 2
>>>> > bgp router-id 150.1.2.2
>>>> > no synchr
>>>> > redistribute connected
>>>> > neighbor 192.168.25.1 remote-as 101
>>>> > no auto-summary
>>>> > exit
>>>> > router rip
>>>> > ver 2
>>>> > no auto-sum
>>>> > network 172.31.2.0
>>>> > ++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> > R7:
>>>> > int ser 1/0
>>>> > no shut
>>>> > ip add 192.168.67.2 255.255.255.0
>>>> > int Lo 1
>>>> > ip add 172.31.7.1 255.255.255.0
>>>> > int lo 0
>>>> > ip add 150.1.7.7 255.255.255.255
>>>> > router bgp 7
>>>> > bgp router-id 150.1.7.7
>>>> > no synchr
>>>> > redistribute connected
>>>> > neighbor 192.168.67.1 remote-as 101
>>>> > no auto-summary
>>>> > exit
>>>> > router rip
>>>> > ver 2
>>>> > no auto-sum
>>>> > network 172.31.7.0
>>>> > +++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> > R8:
>>>> > int ser 1/0
>>>> > no shut
>>>> > ip add 192.168.58.2 255.255.255.0
>>>> > int Lo 1
>>>> > ip add 172.31.8.1 255.255.255.0
>>>> > int lo 0
>>>> > ip add 150.1.8.8 255.255.255.255
>>>> > router bgp 8
>>>> > bgp router-id 150.1.8.8
>>>> > no synchro
>>>> > redistribute connected
>>>> > neighbor 192.168.58.1 remote-as 101
>>>> > no auto-summary
>>>> > exit
>>>> > router rip
>>>> > ver 2
>>>> > no auto-sum
>>>> > network 172.31.8.0
>>>> >
>>>> > ++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> > R3:
>>>> > ip vrf CustB
>>>> > description Customer B
>>>> > rd 1:1
>>>> > route-target export 1:1
>>>> > route-target import 1:1
>>>> > interface Serial1/0
>>>> > no shut
>>>> > ip vrf forwarding CustB
>>>> > ip address 192.168.13.1 255.255.255.252
>>>> > int ser 1/1
>>>> > no shut
>>>> > ip add 192.168.36.1 255.255.255.0
>>>> > int gi 2/0
>>>> > no shut
>>>> > ip add 192.168.34.1 255.255.255.0
>>>> > int Lo 0
>>>> > ip add 150.1.3.3 255.255.255.0
>>>> > router bgp 101
>>>> > no synch
>>>> > redistribute connected
>>>> > 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
>>>> > mpls ip
>>>> > mpls label protocol ldp
>>>> > mpls ldp advertise-labels
>>>> > 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
>>>> > ip route 192.168.67.0 255.255.255.0 192.168.36.2
>>>> > ip route 192.168.25.0 255.255.255.0 192.168.34.2
>>>> > ip route 192.168.58.0 255.255.255.0 192.168.34.2
>>>> > ip route 150.1.5.5 255.255.255.255 192.168.34.2
>>>> > ip route 150.1.6.6 255.255.255.255 192.168.36.2
>>>> > +++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> > 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
>>>> > exit
>>>> > interface Serial1/2
>>>> > ip vrf forwarding CustA
>>>> > ip address 192.168.25.1 255.255.255.252
>>>> > no shut
>>>> > interface Serial1/1
>>>> > ip vrf forwarding CustB
>>>> > ip address 192.168.58.1 255.255.255.252
>>>> > no shut
>>>> > int serial 1/0
>>>> > no shut
>>>> > ip add 192.168.56.1 255.255.255.0
>>>> > int gi 2/0
>>>> > no shut
>>>> > ip add 192.168.45.1 255.255.255.0
>>>> > int Lo 0
>>>> > ip add 150.1.5.5 255.255.255.0
>>>> > router bgp 101
>>>> > no synch
>>>> > redistribute connected
>>>> > 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
>>>> > mpls ip
>>>> > mpls label protocol ldp
>>>> > mpls ldp advertise-labels
>>>> > 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
>>>> > ip route 192.168.67.0 255.255.255.0 192.168.56.2
>>>> > ip route 192.168.13.0 255.255.255.0 192.168.45.2
>>>> > ip route 150.1.3.3 255.255.255.255 192.168.45.2
>>>> > ip route 150.1.6.6 255.255.255.255 192.168.56.2
>>>> > +++++++++++++++++++++++++++++++++++++++++++++++++
>>>> > R6
>>>> > ip vrf CustA
>>>> > description Customer A
>>>> > rd 2:1
>>>> > route-target export 2:1
>>>> > route-target import 2:1
>>>> > exit
>>>> > interface Serial1/1
>>>> > ip vrf forwarding CustA
>>>> > ip address 192.168.67.1 255.255.255.252
>>>> > no shut
>>>> > int ser 1/0
>>>> > no shut
>>>> > ip add 192.168.36.2 255.255.255.0
>>>> > int ser 1/2
>>>> > no shut
>>>> > ip add 192.168.56.2 255.255.255.0
>>>> > int Lo 0
>>>> > ip add 150.1.6.6 255.255.255.0
>>>> > 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
>>>> > ip route 192.168.13.0 255.255.255.0 192.168.36.1
>>>> > ip route 192.168.25.0 255.255.255.0 192.168.56.1
>>>> > ip route 192.168.58.0 255.255.255.0 192.168.56.1
>>>> > ip route 150.1.3.3 255.255.255.255 192.168.36.1
>>>> > ip route 150.1.5.5 255.255.255.255 192.168.56.1
>>>> > router bgp 101
>>>> > no sync
>>>> > 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
>>>> > mpls ip
>>>> > mpls label protocol ldp
>>>> > mpls ldp advertise-labels
>>>> > ++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> > R4:
>>>> > int gi 1/0
>>>> > no shut
>>>> > ip add 192.168.34.2 255.255.255.0
>>>> > int gi 2/0
>>>> > no shut
>>>> > ip add 192.168.45.2 255.255.255.0
>>>> > ip route 192.168.34.0 255.255.255.0 192.168.36.1
>>>> > ip route 192.168.45.0 255.255.255.0 192.168.56.1
>>>> > ip route 0.0.0.0 0.0.0.0 192.168.34.1
>>>> > ip route 0.0.0.0 0.0.0.0 192.168.45.1
>>>> > ip route 150.1.5.5 255.255.255.255 192.168.45.1
>>>> > ip route 150.1.3.3 255.255.255.255 192.168.34.1
>>>> > ++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> 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 Sun Apr 26 2009 - 14:38:29 ART