RE: OT: MPLS VPNV4 routes not making it to EIGRP top

Unfortunately there is no really good explanation for it other than that the
process gets hung, and clearing the table basically restarts the process. You
"shouldn't" need to clear the table to get the redistribution to work, but
just like most of these features it's amazing that the code even works to
begin with ;)

Brian McGahan, CCIE #8593 (R&S/SP/Security)
bmcgahan_at_INE.com<mailto:bmcgahan_at_INE.com>

Internetwork Expert, Inc.
http://www.INE.com

From: ospf cloud [mailto:ospfcloud_at_gmail.com]
Sent: Wednesday, April 04, 2012 2:30 PM
To: Brian McGahan
Subject: Re: OT: MPLS VPNV4 routes not making it to EIGRP top

That fixed it Brian!!!! I want to be like you when I grow up man.....I
remember you mentioned this within your video; I tried cleared ip route *,
cleared ip bgp *, and reloaded to no avail. clearing the vrf routing table
fixed it. Guess I need to signpost that command in my vrf head!

#########################################
R02#show run | b router eigrp
router eigrp 65000
 !
 address-family ipv4 vrf vrf01 autonomous-system 65534
  redistribute bgp 65000
  network 10.1.2.2 0.0.0.0
 exit-address-family
!
router isis 1
 net 49.0001.0000.0000.0002.00
 is-type level-2-only
 metric-style wide
 passive-interface Loopback0
!
router bgp 65000
 no synchronization
 bgp router-id 2.2.2.2
 bgp log-neighbor-changes
 neighbor 3.3.3.3 remote-as 65000
 neighbor 3.3.3.3 update-source Loopback0
 no auto-summary
 !
 address-family vpnv4
  neighbor 3.3.3.3 activate
  neighbor 3.3.3.3 send-community extended
  neighbor 3.3.3.3 next-hop-self
 exit-address-family
 !
 address-family ipv4 vrf vrf01
  no synchronization
  redistribute eigrp 65534
  neighbor 10.1.2.1 remote-as 65534
  neighbor 10.1.2.1 shutdown
  neighbor 10.1.2.1 activate
  neighbor 10.1.2.1 as-override
 exit-address-family
 !
 address-family ipv6 vrf vrf01
  no synchronization
 exit-address-family
!
!
!
no ip http server
no ip http secure-server
!
!

R02#show ip bgp vpnv4 vrf vrf01 20.20.20.20/32<http://20.20.20.20/32>
BGP routing table entry for 65000:1:20.20.20.20/32<http://20.20.20.20/32>,
version 13
Paths: (1 available, best #1, table vrf01)
  Not advertised to any peer
  Local
    19.19.19.19 (metric 50) from 3.3.3.3 (3.3.3.3)
      Origin incomplete, metric 146944, localpref 100, valid, internal, best
      Extended Community: RT:65000:1 Cost:pre-bestpath:128:146944
        0x8800:32768:0 0x8801:65534:130560 0x8802:65281:16384
        0x8803:65281:1514 0x8806:0:336860180
      Originator: 19.19.19.19, Cluster list: 3.3.3.3
      mpls labels in/out nolabel/19017
R02#show ip eigrp vrf vrf01 top
EIGRP-IPv4 Topology Table for AS(65534)/ID(10.1.2.2) VRF(vrf01)
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
       r - reply Status, s - sia Status

P 10.19.20.0/24<http://10.19.20.0/24>, 1 successors, FD is 18944
        via VPNv4 Sourced (18944/0)
P 10.10.10.10/32<http://10.10.10.10/32>, 1 successors, FD is 156160
        via VPNv4 Sourced (156160/0)
P 10.4.10.0/24<http://10.4.10.0/24>, 1 successors, FD is 28160
        via VPNv4 Sourced (28160/0)
P 20.20.20.20/32<http://20.20.20.20/32>, 1 successors, FD is 146944
        via VPNv4 Sourced (146944/0)
P 10.1.2.0/24<http://10.1.2.0/24>, 1 successors, FD is 28160
        via Connected, FastEthernet0/1
P 1.1.1.1/32<http://1.1.1.1/32>, 1 successors, FD is 156160
        via 10.1.2.1 (156160/128256), FastEthernet0/1

R02#

On Wed, Apr 4, 2012 at 1:37 PM, Brian McGahan
<bmcgahan_at_ine.com<mailto:bmcgahan_at_ine.com>> wrote:
Correct, you don't need to set the metric because it will automatically be
encoded as part of the EIGRP Cost Community. Is your config a variation on
this task? http://goo.gl/1VRWe Someone else just posted about having this
same problem on this task. I just re-verified yesterday that the solution is
working properly, so if your config matches that solutions the problem is not
configuration related.

If you're running this in Dynamips it's possible that it's a Dynamips bug.
What you can also try doing is a "clear ip route vrf vrf01 *" after the VPNv4
BGP to EIGRP redistribution occurs. Sometimes the process gets hung and you
have to kickstart it with that clear command.

What IOS version are you running?

Brian McGahan, CCIE #8593 (R&S/SP/Security)
bmcgahan_at_INE.com<mailto:bmcgahan_at_INE.com>

Internetwork Expert, Inc.
http://www.INE.com

-----Original Message-----
From: nobody_at_groupstudy.com<mailto:nobody_at_groupstudy.com>
[mailto:nobody_at_groupstudy.com<mailto:nobody_at_groupstudy.com>] On Behalf Of ospf
cloud
Sent: Wednesday, April 04, 2012 11:38 AM
To: ccielab_at_groupstudy.com<mailto:ccielab_at_groupstudy.com>
Subject: Re: OT: MPLS VPNV4 routes not making it to EIGRP top

Actually, the two customer facing PEs are running EIGRP with respective CPEs
at customer sites. This worked, but suddenly stopped working. I'm aware that
there is no need to specify metrics because the EIGRP costs get encoded within
vpnv4 routes.

On Wed, Apr 4, 2012 at 11:28 AM, ospf cloud
<ospfcloud_at_gmail.com<mailto:ospfcloud_at_gmail.com>> wrote:

> Gurus,
>
> I'm trying to redistribute vpnv4 routes into a vrf on my PE, the vpnv4
> routes are showing up in the vrf's BGP table, but not making it to
> EIGRP top. I cleared ip route *, cleared ip bgp *, and reloaded to no
> avail, but the routes are still getting stuck. Any ideas?
>
>
> ########################################################
> R02#show ip eigrp vrf vrf01 top
> EIGRP-IPv4 Topology Table for AS(65534)/ID(10.1.2.2) VRF(vrf01)
> Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
> r - reply Status, s - sia Status
>
> P 10.1.2.0/24<http://10.1.2.0/24>, 1 successors, FD is 28160
> via Connected, FastEthernet0/1 P 1.1.1.1/32<http://1.1.1.1/32>, 1
successors, FD
> is 156160
> via 10.1.2.1 (156160/128256), FastEthernet0/1
>
> R02#show ip bgp vpnv4 vrf vrf01
> BGP table version is 13, local router ID is 2.2.2.2 Status codes: s
> suppressed, d damped, h history, * valid, > best, i - internal,
> r RIB-failure, S Stale, m multipath, b backup-path, x
> best-external Origin codes: i - IGP, e - EGP, ? - incomplete
>
> Network Next Hop Metric LocPrf Weight Path
> Route Distinguisher: 65000:1 (default for vrf vrf01)
> *> 1.1.1.1/32<http://1.1.1.1/32> 10.1.2.1 156160
32768 ?
> *> 10.1.2.0/24<http://10.1.2.0/24> 0.0.0.0 0
32768 ?
> *>i10.1.20.0/24 19.19.19.19 5138944
100<tel:5138944%20%20%20%20100> 0 ?
> *>i10.4.10.0/24 4.4.4.4 0 100 0 ?
> *>i10.10.10.10/32 4.4.4.4 156160 100 0 ?
> *>i10.19.20.0/24 19.19.19.19 0 100 0 ?
> *>i20.20.20.20/32 19.19.19.19 146944 100 0 ?
> R02#show ip bgp vpnv4 vrf vrf01 10.19.20.0/24<http://10.19.20.0/24> BGP
routing table entry
> for 65000:1:10.19.20.0/24<http://10.19.20.0/24>, version 12
> Paths: (1 available, best #1, table vrf01)
> Not advertised to any peer
> Local
> 19.19.19.19 (metric 50) from 3.3.3.3 (3.3.3.3)
> Origin incomplete, metric 0, localpref 100, valid, internal, best
> Extended Community: RT:65000:1 Cost:pre-bestpath:128:18944
> 0x8800:32768:0 0x8801:65534:2560 0x8802:65280:16384
> 0x8803:65281:4470
> 0x8806:0:169022483
> Originator: 19.19.19.19, Cluster list: 3.3.3.3
> mpls labels in/out nolabel/19016 R02#show run | b router eigrp
> router eigrp 65000 !
> address-family ipv4 vrf vrf01 autonomous-system 65534
> redistribute bgp 65000
> network 10.1.2.2 0.0.0.0
> exit-address-family
> !
> router bgp 65000
> no synchronization
> bgp router-id 2.2.2.2
> bgp log-neighbor-changes
> neighbor 3.3.3.3 remote-as 65000
> neighbor 3.3.3.3 update-source Loopback0 no auto-summary !
> address-family vpnv4
> neighbor 3.3.3.3 activate
> neighbor 3.3.3.3 send-community extended
> neighbor 3.3.3.3 next-hop-self
> exit-address-family
> !
> address-family ipv4 vrf vrf01
> no synchronization
> redistribute eigrp 65534
> neighbor 10.1.2.1 remote-as 65534
> neighbor 10.1.2.1 shutdown
> neighbor 10.1.2.1 activate
> neighbor 10.1.2.1 as-override
> exit-address-family
> !
> !
> !
> no ip http server
>
> R02#show ip bgp vpnv4 vrf vrf01 20.20.20.20/32<http://20.20.20.20/32> BGP
routing table entry
> for 65000:1:20.20.20.20/32<http://20.20.20.20/32>, version 13
> Paths: (1 available, best #1, table vrf01)
> Not advertised to any peer
> Local
> 19.19.19.19 (metric 50) from 3.3.3.3 (3.3.3.3)
> Origin incomplete, metric 146944, localpref 100, valid,
> internal, best
> Extended Community: RT:65000:1 Cost:pre-bestpath:128:146944
> 0x8800:32768:0 0x8801:65534:130560 0x8802:65281:16384
> 0x8803:65281:1514 0x8806:0:336860180
> Originator: 19.19.19.19, Cluster list: 3.3.3.3
> mpls labels in/out nolabel/19017 R02#

Blogs and organic groups at http://www.ccie.net
Received on Wed Apr 04 2012 - 14:37:32 ART