[j-nsp] no inet.2 for multicast RPF etc. by default?

Bill Nickless nickless at mcs.anl.gov
Tue Apr 15 11:19:08 EDT 2003

At 09:58 AM 4/15/2003 +0300, Pekka Savola wrote:
>It seems to me that Juniper does not use inet.2 at all by default.
>That is, even if I configure routes for inet.2 or use MBGP to distribute
>multicast routes when unicast/multicast topology is not congruent, Juniper
>only uses inet.0 by default.
>This seems *odd*.  The desired behaviour should be to always look for
>inet.2 first, and if it fails, look at inet.0 (or so I've been believing).
>Otherwise, being transit using MBGP (for example) would likely break RPF
>quite badly.
>Am I missing something?

I disagree that the "desired behavior" should be the default.

You can configure your "desired behaviour" by an appropriate rib-group, 
applied to the various mujlticast routing protocols.  For example:

rib-groups {
     mcast-rib {
         export-rib inet.2;
         import-rib [ inet.2 inet.0 ];
protocols {
     msdp {
         rib-group mcast-rib;
     pim {
         rib-group inet mcast-rib;

Bill Nickless    http://www.mcs.anl.gov/people/nickless      +1 630 252 7390
PGP:0E 0F 16 80 C5 B1 69 52 E1 44 1A A5 0E 1B 74 F7     nickless at mcs.anl.gov

More information about the juniper-nsp mailing list