RE: L3VPN works, except default route

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#

Blogs and organic groups at http://www.ccie.net
Received on Thu Apr 19 2012 - 08:41:16 ART