Re: Static Routes with interface or not

For your first question I believe the answer has something to do with
this when you have the (optional) interface included in the static vrf
route:

You are bypassing the route recursion process by
telling the router all the info it needs to find its destination and
create the CEF adjacency (next-hop IP + interface).

I didn't understand what you meant by "I should
 also say that 155.1.76.7 is not reachable but Gig 0/0 is up/up"
Isn't the 155.1.76.7 the next hop over the Gi0/0?

-Rich

On Thu, May 5, 2011 at 10:16 PM, Andrew LaPorte <andy_at_cloud9.net> wrote:
> Steve,
>
> Thanks for your response. Your reference did help a bit but I still have a
> confusion. My problem has to do with when should a static route be
> advertised into BGP.
>
> I have a specific problem here. I found this while doing an INE MPLS lab.
> My basic configuration is as follows:
>
> ip vrf VPN_A
> rd 100:1
> route-target both 100:1
>
> router bgp 100
> no bgp default ipv4-unicast
> neighbor 150.1.4.4 remote-as 100
> neighbor 150.1.4.4 update-source loopback 0
> address-family vpnv4 unicast
> neighbor 150.1.4.4 activate
> neighbor 150.1.4.4 send-community extended
> address-family ipv4 vrf VPN_A
> redistribute connected
> redistribute static
>
> ip route vrf VPN_A 192.168.7.0 255.255.255.0 Gig 0/0.1 155.1.76.7
>
> As you can see I'm redistributing static and connect. Now on 12.4.(24)T the
> route no being advertised to my BGP peers:
>
> Rack1R6#show bgp vpnv4 unicast all 192.168.7.0
> BGP routing table entry for 100:1:192.168.7.0/24, version 3
> Paths: (1 available, no best path)
> Not advertised to any peer
> Local
> 155.1.76.7 (inaccessible) from 0.0.0.0 (150.1.6.6)
> Origin incomplete, metric 0, localpref 100, weight 32768, valid,
> sourced
> Extended Community: RT:100:1
>
> But on 12.4.(24)T5 the route is being advertised to my BGP peers:
>
> Rack1R6#show bgp vpnv4 unicast all 192.168.7.0
> BGP routing table entry for 100:1:192.168.7.0/24, version 10
> Paths: (1 available, best #1, table VPN_A)
> Flag: 0x820
> Advertised to update-groups:
> 1
> Local
> 0.0.0.0 from 0.0.0.0 (150.1.6.6)
> Origin incomplete, metric 0, localpref 100, weight 32768, valid,
> sourced, best
> Extended Community: RT:100:1
> mpls labels in/out 22/nolabel
>
>
> As you can see 12.4.(24)T is acting different then 12.4.(24)T5. I should
> also say that 155.1.76.7 is not reachable but Gig 0/0 is up/up.
>
> So now I'm left with the question which IOS is correctly handling the issue.
>
>
> #1) What defines if a static route should be advertised out into BGP?
> Which IOS is doing the correct job.
> #2) Where do I find this type of information on the DocCD?
>
> Andy

Blogs and organic groups at http://www.ccie.net
Received on Sat May 07 2011 - 18:42:25 ART