[j-nsp] VRF load balancing between pair of j-MX480 PEs and pair of c-7609 PEs

Sorilla, Edmar (NSN - AE/Dubai) edmar.sorilla at nsn.com
Tue Feb 16 05:26:47 EST 2010


Hi Sergio,

We already found the issue. The problem lies on the Layer 3 link between MX routers.
Because it is a 10G gig link and the link to P is only 1G. The PE routers prefer this link
to forward the traffic instead of the link to P router. 

We modified the OSPF cost of this 10G link to 25 so the MX routers will forward the traffic to P immediately 
and everything worked fine with BGP multipath enable.

Thanks for your help. I really appreciated it.

Br,
Edmar


-----Original Message-----
From: ext Sergio D. [mailto:sdanelli at gmail.com]
Sent: Tue 2/16/2010 9:46 AM
To: Sorilla, Edmar (NSN - AE/Dubai)
Subject: Re: VRF load balancing between pair of j-MX480 PEs and pair of c-7609 PEs
 
Hmm I don't see an issue here.
You don't have "mpls label mode all-vrfs protocol bgp-vpnv4 per-vrf"
configured on the 7600, do you?
And what labels do you have allocated for the connected routes, are they
aggregate labels?
"sh mpls forwarding-table | in Huawei_Iu-U"
And do both Ciscos share the connected network that you have problems with
in that vrf between them?


On Mon, Feb 15, 2010 at 11:22 PM, Sorilla, Edmar (NSN - AE/Dubai) <
edmar.sorilla at nsn.com> wrote:

>  Hi Sergio,
>
> Here are the configurations and outputs:
>
> Br,
> Edmar
>
>
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> MX480-1
>
> admin at AUH-INJ-OR-MOBMX480-01> ...atement Huawei_Iu_U_import
> term 1 {
>     from {
>         protocol bgp;
>         community [ Iu_C_3220 Iu_U_3210 ];
>     }
>     then accept;
> }
> term 2 {
>     then reject;
> }
> admin at AUH-INJ-OR-MOBMX480-01> ...ons policy-statement Huawei_Iu_U_export
> term 1 {
>     from protocol [ static direct ];
>     then {
>         metric 0;
>         community add Iu_U_3210;
>         accept;
>     }
> }
> term 2 {
>     then reject;
> }
>
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> MX480-2
>
> admin at AUH-INJ-OR-MOBMX480-02> ...atement Huawei_Iu_U_import
> term 1 {
>     from {
>         protocol bgp;
>         community [ Iu_C_3220 Iu_U_3210 ];
>     }
>     then accept;
> }
> term 2 {
>     then reject;
> }
> admin at AUH-INJ-OR-MOBMX480-02> ...ons policy-statement Huawei_Iu_U_export
> term 1 {
>     from protocol [ static direct ];
>     then {
>         metric 0;
>         community add Iu_U_3210;
>         accept;
>     }
> }
> term 2 {
>     then reject;
> }
>
> ------------------------------------------------------------------------------------------------------------------------------------
>
> impor01>show ip bgp vpnv4 vrf Huawei_Iu-U 10.164.128.33
> BGP routing table entry for 15802:3220:10.164.128.32/28, version 6182903
> Paths: (2 available, best #1, table Huawei_Iu-U)
> Multipath: eiBGP
>   Not advertised to any peer
>   Local, imported path from 15802:3201:10.164.128.32/28
>     10.44.105.3 (metric 30) from 10.19.56.141 (10.19.56.141)
>       Origin IGP, metric 0, localpref 100, valid, internal, multipath, best
>       Extended Community: RT:15802:3210
>       Originator: 10.44.105.3, Cluster list: 10.19.56.141
>       mpls labels in/out nolabel/20
>   Local, imported path from 15802:13201:10.164.128.32/28
>     10.44.105.4 (metric 31) from 10.19.56.141 (10.19.56.141)
>       Origin IGP, metric 0, localpref 100, valid, internal, multipath
>       Extended Community: RT:15802:3210
>       Originator: 10.44.105.4, Cluster list: 10.19.56.141
>       mpls labels in/out nolabel/43
>
> --------------------------------------------------------------------------------------------------------------------------------
> impor01>show mpls forwarding-table 10.44.105.3
> Local  Outgoing      Prefix            Bytes Label   Outgoing   Next Hop
> Label  Label or VC   or Tunnel Id      Switched      interface
> 50     298           10.44.105.3/32    300           Gi5/2
> 10.19.120.109
> impor01>show mpls forwarding-table 10.44.105.4
> Local  Outgoing      Prefix            Bytes Label   Outgoing   Next Hop
> Label  Label or VC   or Tunnel Id      Switched      interface
> 87     302           10.44.105.4/32    915848        Gi5/2
> 10.19.120.109
>
> --------------------------------------------------------------------------------------------------------------------------------
>
> impor02>show ip bgp vpnv4 vrf Huawei_Iu-U 10.164.128.33
> BGP routing table entry for 15802:13220:10.164.128.32/28, version 3390318
> Paths: (2 available, best #2, table Huawei_Iu-U)
> Multipath: eiBGP
>   Not advertised to any peer
>   Local, imported path from 15802:3201:10.164.128.32/28
>     10.44.105.3 (metric 31) from 10.19.56.141 (10.19.56.141)
>       Origin IGP, metric 0, localpref 100, valid, internal, multipath
>       Extended Community: RT:15802:3210
>       Originator: 10.44.105.3, Cluster list: 10.19.56.141
>       mpls labels in/out nolabel/20
>   Local, imported path from 15802:13201:10.164.128.32/28
>     10.44.105.4 (metric 30) from 10.19.56.141 (10.19.56.141)
>       Origin IGP, metric 0, localpref 100, valid, internal, multipath, best
>       Extended Community: RT:15802:3210
>       Originator: 10.44.105.4, Cluster list: 10.19.56.141
>       mpls labels in/out nolabel/43
>
>
> --------------------------------------------------------------------------------------------------------------------------------
>
> impor02>show mpls forwarding-table 10.44.105.3
> Local  Outgoing      Prefix            Bytes Label   Outgoing   Next Hop
> Label  Label or VC   or Tunnel Id      Switched      interface
> 141    160           10.44.105.3/32    0             Gi5/2
> 10.19.121.9
>
> impor02>show mpls forwarding-table 10.44.105.4
> Local  Outgoing      Prefix            Bytes Label   Outgoing   Next Hop
> Label  Label or VC   or Tunnel Id      Switched      interface
> 93     292           10.44.105.4/32    370           Gi5/2
> 10.19.121.9
>
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
>
>  ------------------------------
> *From:* ext Sergio D. [mailto:sdanelli at gmail.com]
> *Sent:* Tuesday, February 16, 2010 7:45 AM
> *To:* Sorilla, Edmar (NSN - AE/Dubai)
> *Cc:* juniper-nsp at puck.nether.net
> *Subject:* RE:VRF load balancing between pair of j-MX480 PEs and pair of
> c-7609 PEs
>
> Edmar,
> Can you provide us with the policy configuration from the Junipers?
>
> vrf-import Huawei_Iu_U_import;
> vrf-export Huawei_Iu_U_export;
>
> Those two specifically.
>
>  a "show ip bgp v v Huawei_Iu-U x.x.x.x" From the Cisco routers where
> x.x.x.x is the source IP of where the traffic is coming from to the Cisco
> destinations? , a "sh mpls forwarding-table 10.44.105.3" and ""sh mpls
> forwarding-table 10.44.105.4"  When the problem is happening of course.
>
> --
> Sergio
>



-- 
Sergio Danelli
JNCIE #170



More information about the juniper-nsp mailing list