Re: MPLS issue

Mateen,

Run the below command on each CPE edge router to see if you are
advertising the proper networks.

Show ip bgp neighbors 192.168.101.1 advertised-routes

If you are advertising all the propers routes, then I would check my LDP
neighbors and the most common mistake for scenarios like this is that the
MPLS backbone LDP LSR9s are not using /32 loopback addresses for their ldp
router-id9s.

Next: Check that your route-targets are import/export correctly.

Let us know how it goes

Best Regards,
Joe Sanchez

On 8/8/14, 3:44 PM, "Mateen Taj" <taj.mateen_at_gmail.com> wrote:

>Dear Expert,
>
>Please help me out to know on below configuration , I'm able to reach WAN
>interface from both side but not able to reach LAN, is there anything
>missing in my config
>
>Many Thank
>Mateen
>
>Router1#
>no ipv6 cef
>ip source-route
>ip cef
>!
>!
>!
>interface Embedded-Service-Engine0/0
> no ip address
> shutdown
>!
>interface GigabitEthernet0/0
> description $ETH-LAN$$ETH-SW-LAUNCH$$INTF-INFO-GE 0/0$
> ip address 172.16.31.2 255.255.255.0
> duplex auto
> speed auto
>!
>interface GigabitEthernet0/1
> description Link-Etisalat
> ip address 192.168.101.150 255.255.255.252
> duplex auto
> speed auto
>!
>router bgp 65455
> bgp log-neighbor-changes
> network 10.10.0.0
> network 10.10.200.0
> network 10.10.201.0
> network 10.10.215.0
> network 172.16.31.0
> network 192.168.101.148 mask 255.255.255.252
> neighbor 192.168.101.1 remote-as 64517
>!
>ip forward-protocol nd
>!
>ip http server
>ip http authentication local
>ip http secure-server
>ip http timeout-policy idle 60 life 86400 requests 10000
>!
>ip route 10.10.0.0 255.255.0.0 172.16.31.1
>ip route 172.16.101.0 255.255.255.0 192.168.101.149
>ip route 172.16.102.0 255.255.255.0 192.168.101.149
>ip route 192.168.168.0 255.255.255.0 192.168.101.149
>!
>!
>!
>!
>control-plane
>!
>!
>banner exec ^C
>% Password expiration warning.
>-----------------------------------------------------------------------
>C
>-----------------------------------------------------------------------
>^C
>
>
>User Access Verification
>Password:
>Password:
>Router2#
>Current configuration : 1952 bytes
>!
>version 12.4
>service timestamps debug datetime msec
>service timestamps log datetime msec
>!
>!
>interface FastEthernet0/0
> description LAN
> ip address 172.31.0.3 255.255.255.0
> duplex auto
> speed auto
>!
>interface FastEthernet0/1
> description WAN-Link to Etisalat
> ip address 192.168.30.102 255.255.255.252
> duplex auto
> speed auto
>!
>router bgp 65450
> no synchronization
> bgp log-neighbor-changes
> network 172.16.101.0 mask 255.255.255.0
> network 172.16.102.0 mask 255.255.255.0
> network 172.31.0.0 mask 255.255.255.0
> network 192.168.30.100 mask 255.255.255.252
> network 192.168.168.0
> neighbor 192.168.30.101 remote-as 64517
> no auto-summary
>!
>ip forward-protocol nd
>ip route 10.10.200.0 255.255.255.0 192.168.30.101
>ip route 10.10.201.0 255.255.255.0 192.168.30.101
>ip route 10.10.215.0 255.255.255.0 192.168.30.101
>ip route 132.142.0.0 255.255.0.0 192.168.30.101
>ip route 133.120.0.0 255.255.0.0 192.168.30.101
>ip route 134.120.0.0 255.255.0.0 192.168.30.101
>ip route 135.120.0.0 255.255.0.0 192.168.30.101
>ip route 136.120.0.0 255.255.0.0 192.168.30.101
>ip route 136.146.0.0 255.255.0.0 192.168.30.101
>ip route 138.148.0.0 255.255.0.0 192.168.30.101
>ip route 172.16.101.0 255.255.255.0 172.31.0.1
>ip route 172.16.102.0 255.255.255.0 172.31.0.1
>ip route 172.16.102.0 255.255.255.0 192.168.168.13
>ip route 172.16.102.0 255.255.255.0 192.168.168.155
>ip route 192.168.168.0 255.255.255.0 172.31.0.1
>!
>!
>ip http server
>ip http timeout-policy idle 600 life 86400 requests 10000
>!
>!
>!
>control-plane
>!
>!
>
>!
>scheduler allocate 20000 1000
>!
>end
>
>
>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 Sat Aug 09 2014 - 12:55:17 ART