[f-nsp] VRRP-E in combination with Route-Maps

[Joseph Jackson]

?
What type of routes are you getting from your providers? Full? Default route?

________________________________

From: foundry-nsp-bounces at puck.nether.net on behalf of A. Krijgsman - QCC
Sent: Sun 2/26/2006 4:17 AM
To: foundry-nsp at puck.nether.net
Subject: Re: [f-nsp] VRRP-E in combination with Route-Maps



Dear Gunther / All,

That would have been my first guess as well.
However when I try the bgp route to my provider B. (Below are my real
results.)
You will see it takes the longer AS-path trough provider A to the provider
B. IP :-(

Has this anything to do with the backup-priority / track-priority in VRRP-E?
Or is this default iBGP behaviour?

If anyone has a clue? :-)

Kind regards,
Armand

++++++++++++++++++++++++ MY RESULT +++++++++++++++++++++++++++++++++++
SSH at ams-gs-rt2>show ip bgp 217.170.9.139
Number of BGP Routes matching display condition : 2
Status codes: s suppressed, d damped, h history, * valid, > best, i internal
Origin codes: i - IGP, e - EGP, ? - incomplete
    Network            Next Hop        Metric LocPrf Weight Path
*>  217.170.9.0/24     84.233.188.97               100    0      8928 15412
24785 24785 i
*i   217.170.9.0/24     217.170.9.129               100    0      24785 i
       Last update to IP routing table: 2d1h4m16s, 1 path(s) installed:
         Gateway           Port
         84.233.188.97     v1
       Route is advertised to 1 peers:
        195.144.2.2(35829)
++++++++++++++++++++++++ MY RESULT +++++++++++++++++++++++++++++++++++

----- Original Message -----
From: "Gunther Stammwitz" <gstammw at gmx.net>
To: "'A. Krijgsman - QCC'" <a.krijgsman at quality-control-centre.net>;
<foundry-nsp at puck.nether.net>
Sent: Sunday, February 26, 2006 1:01 PM
Subject: AW: [f-nsp] VRRP-E in combination with Route-Maps


> Hello Armand,
>
> I guess you're running BGP as outside/external routing protocol, right?
> Well... That would explain why traffic is flowing the way it is: if both
of
> your providers are supplying you with the same as-path-lengths for most of
> the prefixes - this is mostly happening when both of them are of the same
> tier-class like both are tier1 - your router is always going to prefer the
> the external path over the internal one.
> Example:
> Here we can see that the network 3.0.0.0/8 can be reached in 5 as-hops.
The
> internal path (5.6.7.8) as well as the external one have exactly the same
> lenght and localpref but the external one is being preferred. This is a
> standard mechanism in bgp (ebgp over ibgp).
>
> *>  3.0.0.0/8          1.2.3.4                999    0      12345 3356 701
> 703 80 i
> *i  3.0.0.0/8          5.6.7.8    0           999    0      12345 3356 701
> 703 80 i
>
> I hope this was a help.
> Gunther
>
>
>
>


_______________________________________________
foundry-nsp mailing list
foundry-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20060226/41f4fa2d/attachment.html>