That's what i am looking for Harry. Now it is loadbalancing as expected. Thank you very much.
Regards. -----Original Message----- From: Harry Reynolds [mailto:[EMAIL PROTECTED] Sent: 09 Ocak 2007 Salı 17:45 To: Sinan İlkiz; Juniper Maillist Subject: RE: [j-nsp] VPN loadbalancing using different route distinguishers Hello, You may want to check out the 6.3 feature for LB between PEs. This feature requires configuration of a multi-path statement at the routing-instance hierarchy. According to my info, including vpn-unequal-cost results in compare up to igp metric, while omitting this option compares up to RID. HTHs http://www.juniper.net/techpubs/software/junos/junos62/rn-sw-62/rn-new-f eatures.html#rn-new-features "VPN load balancing between PE routing platforms that have different route distinguishers-Allows the forwarding next hops of both the active route and alternative paths to be used for load-balancing purposes. To configure, include the multi-path statement at the [edit routing-instances name routing-options] and [edit routing-instances name routing-options rib name] hierarchy levels. [VPNs, Command Reference: Protocols] " > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Sinan Ilkiz > Sent: Monday, January 08, 2007 11:11 PM > To: Juniper Maillist > Subject: [j-nsp] VPN loadbalancing using different route > distinguishers > > Hi all, > > I have a question regarding load balancing. I have three PEs, namely > PE1, PE2 and PE3. They all have CPEs connected to them for the same > VPN. MPLS and VPN operation is working fine. I am trying to achive > loadbalancing by using different route distinguishers. I have a static > route "1.1.1.1/32" in this VPN on both PE1 and PE2. PE1 and PE2 have > different route distinguishers to make these routes distinct. > > In PE3's BGP configuration both PE1 and PE2 are in the same group > which has multipath enabled. When i examine the output of "show bgp > neighbor ..." i see multipath option for both PEs. In addition to > this, i have load-balance per packet policy under routing options -> > forwarding options. > > Unfortunately only one of the routes is getting installed. > The output of show route table VPN 1.1.1.1/32 extensive yields > "Inactive reason: Router ID". I can not figure out what is missing or > if multipath is an applicable approach to this issue. > > Regards. > > sinani@<PE3>> show route table VPN 1.1.1.1 extensive > > VPN.inet.0: 18 destinations, 46 routes (18 active, 0 holddown, 0 > hidden) > 1.1.1.1/32 (6 entries, 1 announced) > TSI: > KRT in-kernel 1.1.1.1/32 -> {indirect(262746)} > *BGP Preference: 170/-101 > Route Distinguisher: <rd of PE1> > Next-hop reference count: 21 > Source: <loopback of PE1> > Next hop: via ds-0/0/5:1.0 weight 0x1, selected > Label-switched-path <LSP to PE1> > Label operation: Push 100416, Push 751217(top) > Protocol next hop: <loopback of PE1> > Push 100416 > Indirect next hop: 8f020cc 262746 > State: <Secondary Active Int Ext> > Local AS: <MyASN> Peer AS: <MyASN> > Age: 11:51:42 Metric2: 50 > Task: BGP_15924....+2613 > Announcement bits (1): 0-KRT > AS path: I () > Communities: <vrf target of VPN> > VPN Label: 100416 > Localpref: 100 > Router ID: <loopback of PE1> > Primary Routing Table bgp.l3vpn.0 > BGP Preference: 170/-101 > Route Distinguisher: <rd of PE2> > Next-hop reference count: 20 > Source: <loopback of PE2> > Next hop: via ds-0/0/4:1.0 weight 0x1, selected > Label-switched-path <LSP to PE2> > Label operation: Push 484805 > Protocol next hop: <loopback of PE2> > Push 484805 > Indirect next hop: 8fe78c4 262526 > State: <Secondary NotBest Int Ext> > Inactive reason: Router ID > Local AS: <MyASN> Peer AS: <MyASN> > Age: 11:51:42 Metric2: 50 > Task: BGP_15924....+1034 > AS path: I () > Communities: <vrf target of VPN> > VPN Label: 484805 > Localpref: 100 > Router ID: <loopback of PE2> > Primary Routing Table bgp.l3vpn.0 > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
