Hi Krasimir,
I had only considered vt interfaces for doing filtering/additional look ups
for traffic egressing L3VPNs (prior to the vrf-table-lable being
available). I now have a working NG MVPN (extranet). However, what if I
wanted to have senders/receivers physically terminated on the same
Hi,
vt when used with multicast keyword(in configuration upon binding VT ifl
to VRF) is only used for multicast traffic replication(loopback) to
receivers living in different MVPN instances. The unicast traffic can still
use vrf-table-label, the same vt ifl as multicast, a different vt ifl than
Hi,
The only thing I wasn't sure about was, whether or not the traffic goes
through the fabric in cases where you have different VTs (I'm almost
certain this used to be a problem).
Thanks,
Vladi
On Mon, Dec 17, 2012 at 2:16 PM, Krasimir Avramski kr...@smartcom.bgwrote:
Hi,
vt when used with
Well, juniper does NOT support fabric multicast replication, so inter PFE
multicast robustness depends on:
number of fabrics installed and fabric capacity(legacy/enhanced).
binary + unary multicast replication support - trio only mode (DPC are
not allowed) using network-services enhanced-ip.
Best
Hi all,
I need to deliver multicast data to a receiver in a VRF, which resides on
the same PE as the sender VRF.
The only way I see this could be done is by putting one of the VRFs into a
logical system and presenting the traffic over an lt interface. The problem
is that this type of design does
Hi,
NG-MVPN extranets are supported since junos 9.5:
http://www.juniper.net/techpubs/en_US/junos11.4/topics/topic-map/mcast-mbgp-extranets.html#jd0e120
As I remember in some corner cases(only two extranet VRFs on the same
router - if my memory serves me right) there is NO need for tunnel hw
6 matches
Mail list logo
