Thanks so much, y'all are great.
I do already have the unique RD's on all pe's.
I do not have the max paths...i tested that yesterday and it didn't seem to
work, I think it's because I only used the "maximum-paths 2" without those
other iebgp things.... looks good now.
"maximum-paths ibgp 2" - didn't work
"maximum-paths ibgp unequal-cost 2" - worked
(this is a different pe, but similar in its use, in other words it's not one
of those core dual pe's i mentioned)
me3600(config)#router bgp 65000
me3600(config-router)#address-family ipv4 vrf one
me3600(config-router-af)#maximum-paths ibgp unequal-cost 2
me3600(config-router-af)#do sh ip ro vrf one 0.0.0.0
Routing Table: one
Routing entry for 0.0.0.0/0, supernet
Known via "bgp 65000", distance 200, metric 1, candidate default path,
type internal
Last update from 10.101.0.1 00:00:01 ago
Routing Descriptor Blocks:
* 10.101.0.2 (default), from 10.101.0.2, 00:00:01 ago
Route metric is 1, traffic share count is 1
AS Hops 0
MPLS label: 16220
MPLS Flags: MPLS Required
10.101.0.1 (default), from 10.101.0.1, 00:00:01 ago
Route metric is 1, traffic share count is 1
AS Hops 0
MPLS label: 16238
MPLS Flags: MPLS Required
me3600(config-router-af)#
-----Original Message-----
From: Tim Durack [mailto:[email protected]]
Sent: Thursday, April 19, 2012 8:58 AM
To: Aaron
Cc: [email protected]
Subject: Re: [c-nsp] L3VPN works, but not default route
You will need a unique RD per PE, to allow multiple VPN routes to be
"discriminated." You also need to enable maximum-paths for the bgp vrf
context:
PE1:
vrf definition <vrf>
rd <rd1>
route-target both <RT>
end
PE2:
vrf definition <vrf>
rd <rd2>
route-target both <RT>
end
router bgp <AS>
address-family ipv4 vrf <vrf>
maximum-paths eibgp 2 import 2
exit-address-family
address-family ipv6 vrf <vrf>
maximum-paths eibgp 2 import 2
exit-address-family
end
Tim:>
On Thu, Apr 19, 2012 at 9:39 AM, Aaron <[email protected]> wrote:
> As a continuation of this thread/task, I now have the default route
> from my dual core ce-pe hubs, thanks to you all :) ...and now shown
> below is some output from one of my other pe's further out into the
> edge of my network...it seems that it is rcv'ing the dual default
> routes from the dual ce/pe core hubs, but now I'm wanting to allow
> BOTH default routes into the rib to allow for the typical cef src/dst
> hashing for load balancing between both pe next hops 10.101.0.1 and
> 10.101.0.2. Let me know what you think please on how to accomplish this.
>
> Aaron
>
> test-me3600#sh bgp vpnv4 u rd 10.101.0.1:1 0.0.0.0 BGP routing table
> entry for 10.101.0.1:1:0.0.0.0/0, version 9620
> Paths: (1 available, best #1, no table)
> Not advertised to any peer
> Local
> 10.101.0.1 (metric 4) from 10.101.0.1 (10.101.0.1)
> Origin incomplete, metric 1, localpref 100, valid, internal, best
> Extended Community: RT:100:1 OSPF RT:0.0.0.0:5:1
> OSPF ROUTER ID:1.1.191.17:0
> mpls labels in/out nolabel/16238
>
> test-me3600#sh bgp vpnv4 u rd 10.101.0.2:1 0.0.0.0 BGP routing table
> entry for 10.101.0.2:1:0.0.0.0/0, version 11522
> Paths: (1 available, best #1, no table)
> Not advertised to any peer
> Local
> 10.101.0.2 (metric 3) from 10.101.0.2 (10.101.0.2)
> Origin incomplete, metric 1, localpref 100, valid, internal, best
> Extended Community: RT:100:1 OSPF RT:0.0.0.0:5:1
> OSPF ROUTER ID:1.1.191.21:0
> mpls labels in/out nolabel/16220
>
>
> test-me3600#sh ip ro vrf one 0.0.0.0
>
> Routing Table: one
> Routing entry for 0.0.0.0/0, supernet
> Known via "bgp 64512", distance 200, metric 1, candidate default
> path, type internal
> Last update from 10.101.0.2 16:33:17 ago
> Routing Descriptor Blocks:
> * 10.101.0.2 (default), from 10.101.0.2, 16:33:17 ago
> Route metric is 1, traffic share count is 1
> AS Hops 0
> MPLS label: 16220
> MPLS Flags: MPLS Required
>
>
> test-me3600#sh run | sec router bgp
> router bgp 64512
> bgp router-id 10.101.12.253
> bgp log-neighbor-changes
> no bgp default ipv4-unicast
> neighbor 10.101.0.1 remote-as 64512
> neighbor 10.101.0.1 update-source Loopback0
> neighbor 10.101.0.2 remote-as 64512
> neighbor 10.101.0.2 update-source Loopback0
> neighbor 10.101.0.4 remote-as 64512
> neighbor 10.101.0.4 update-source Loopback0
> neighbor 10.101.8.2 remote-as 64512
> neighbor 10.101.8.2 update-source Loopback0
> !
> address-family ipv4
> exit-address-family
> !
> address-family vpnv4
> neighbor 10.101.0.1 activate
> neighbor 10.101.0.1 send-community extended
> neighbor 10.101.0.2 activate
> neighbor 10.101.0.2 send-community extended
> neighbor 10.101.0.4 activate
> neighbor 10.101.0.4 send-community extended
> neighbor 10.101.8.2 activate
> neighbor 10.101.8.2 send-community extended
> exit-address-family
> !
> address-family ipv4 vrf one
> redistribute connected
> exit-address-family
> test-me3600#
>
>
>
> _______________________________________________
> cisco-nsp mailing list [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
--
Tim:>
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
