On May 20, 2008, at 4:46 PM, Dave Diller wrote:
> Normally, the system uses the vrf-target to import routes from
> bgp.l3vpn.0 to the correct VRF.inet.0. This is working fine for
> unicast routes. I'm trying to do the same now to get routes from
> bgp.l3vpn.2 to VRF.inet.2
>
> Routes are receiv
> Try this:
>
> http://www.juniper.net/techpubs/software/junos/junos85/swconfig85-multicast/id-13041423.html#id-13041423
>
>
I hadn't put that into the VRF's PIM yet, although I had it for inet.2
itself. Added it now on principle. This is a step beyond where I am
though... this will just t
Try this:
http://www.juniper.net/techpubs/software/junos/junos85/swconfig85-multicast/id-13041423.html#id-13041423
On 5/20/08, Dave Diller <[EMAIL PROTECTED]> wrote:
>
> Normally, the system uses the vrf-target to import routes from
> bgp.l3vpn.0 to the correct VRF.inet.0. This is working fin
Do you have a tunnel pic installed?
Dave Diller wrote:
> Normally, the system uses the vrf-target to import routes from
> bgp.l3vpn.0 to the correct VRF.inet.0. This is working fine for
> unicast routes. I'm trying to do the same now to get routes from
> bgp.l3vpn.2 to VRF.inet.2
>
> Rou
On May 20, 2008, at 6:27 PM, Chris Spears wrote:
> Do you have a tunnel pic installed?
>
Yup.
-dd
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Normally, the system uses the vrf-target to import routes from
bgp.l3vpn.0 to the correct VRF.inet.0. This is working fine for
unicast routes. I'm trying to do the same now to get routes from
bgp.l3vpn.2 to VRF.inet.2
Routes are received correctly in bgp.l3vpn.2 from the peer, are
active
6 matches
Mail list logo