[j-nsp] advertising direct routes in a vrf

[Harshit Kumar]

This is basically to facilitate ARP on multi-access interfaces (fe/ge).
 after popping vrf-label at PE. Depending on what kind of core interface
 you have, you can possibly use vrf-table-label instead.

http://www.juniper.net/techpubs/software/junos/junos72/swconfig72-vpns/h
tml/vpnl3-config25.html#1072807

Harshit


> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net 
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of 
> Ezequiel Carson
> Sent: Tuesday, May 24, 2005 11:28 AM
> To: Juniper list
> Subject: [j-nsp] advertising direct routes in a vrf
> 
> Hi List,
> 
> 	Im configuring a l3vpn and i found that i have to add 
> static routes
> /32s in order to  be able to ping from one CE to anothe CE.
> 
> 	Example.
> 
> 	
> 	ge-1/0/0.1505
> 	vlan-id 1505;
> 		family inet {
>     			address 10.14.120.1/24;
> 	}
> 
> 	The only way that another CE can reach my hsot 10.14.120.10 or
> 10.14.120.4 is adding static routes in the routing-instance
> configuration.
> show configuration routing-instances IFX-MGMT
> instance-type vrf;
> interface ge-1/0/0.1505;
> route-distinguisher 1111:999000005;
> vrf-targ\et target:1111:999000005;
> routing-options {
>     static {
>         route 10.14.120.4/32 next-hop 10.14.120.4;
>         route 10.14.120.10/32 next-hop 10.14.120.10;
>     }
> }
> 
> 
> Is there any problem with my configuration?
> 
> thanks
> Ezequiel
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>