Routing
Highlighted
Routing

Separating multicast traffic and unicast traffic?

[ Edited ]
‎08-17-2014 02:07 AM

Hi.

 

I have a topo like this

 

Source-------------->RP1-------ge0<unicast>------------------------------RP2------------>Receiver

                                 -----------------------<ge1 unicast/mulicast>-----

 

Between RP1 and RP2  I run BGP and MSDP. On ge-1 I enable PIM and bgp family-inet-unicast, bgp family-inet-multicast. ALl thing seems to be ok. 

 

But I want to separate unicast traffic and mulitcast traffic on RP2.  In my lab, I only see the interface ge-0/0/1 is used for multicast and unicast. From RP2, if BGP selects route to source via interface ge-0/0/1, receiver can receive multicast traffic, but it cannot, if BGP select via ge-0.

 

Is there any solution ?

 Please see my topo from attachment

 

 

 

 

Attachments

14 REPLIES 14
Highlighted
Routing

Re: Separating multicast traffic and unicast traffic?

‎08-17-2014 01:02 PM
protocols pim rib-group ...

make the rib-group include inet.2

I don't remember if it's import or export, you can play around
Highlighted
Routing

Re: Separating multicast traffic and unicast traffic?

‎08-17-2014 08:42 PM

Thanks for your reply, but what do you mean when using the command protocols pim rib-group ... 

 

As I understand, it will help us to check RPF by using inet.2 instead of inet.0 Here is my configuration at RP2

root@SRSX240-01# show routing-options
interface-routes {
rib-group inet CONNECTED;
}
static {
rib-group STATIC-ROUTE;
route 1.1.1.6/32 next-hop [ 10.60.1.22 10.60.1.30 ];
}
rib-groups {
MCAST.INET2 {
import-rib inet.2;
}
CONNECTED {
import-rib [ inet.0 inet.2 ];
import-policy RPF-CHECK;
}
BGP-ROUTE {
import-rib [ inet.0 inet.2 ];
import-policy RPF-CHECK-BGP;
}
STATIC-ROUTE {
import-rib [ inet.0 inet.2 ];
import-policy STATIC-ROUTE;
}
}
router-id 1.1.1.4;
autonomous-system 120;

show protocols pim
rib-group inet MCAST.INET2;

 

Routing

Re: Separating multicast traffic and unicast traffic?

‎08-18-2014 01:20 AM
BGP family inet multicast installs routes in inet.2 and you need to instruct PIM to do the RPF in that table. You define PIM rib group with keyword import(-rib) in its definition try with export instead on the RIB group definition.
Highlighted
Routing

Re: Separating multicast traffic and unicast traffic?

‎08-18-2014 01:41 AM

Hi.

 

inet.2 table is empty, if you don't use it to check RPF. So, inet.2 is only used to check RPF, not for multicast streaming, it's right ?

I want to control unicast traffic will flow one path, and mulciast traffic will flow other. Do you have suggestion?

Highlighted
Routing

Re: Separating multicast traffic and unicast traffic?

‎08-18-2014 02:18 AM

As I understand, inet.2 is only used to checked RPF (maybe route in inet.2 is different inet.0), but  multicast treaming still flows as unicast routing ?

Highlighted
Routing

Re: Separating multicast traffic and unicast traffic?

‎08-18-2014 02:22 AM

hello,

If I understand Your issue correctly, You use BGP routes for RPF, have ECMP for these BGP routes' nexthops but run PIM only on 1 link.

In that case You need to manipulate BGP nexthop so it resolves only via PIM link.

There is a number of ways to do it in JUNOS, take Your pick:

1/ resolution-rib policy

2/ change BGP nexthop in import or export BGP policy

3/ static /32 towards BGP nexthop overriding IGP route towards BGP nexthop

I am sure other posters will come with even more suggestions.

HTH

Thanks
Alex

 

_____________________________________________________________________

Please ask Your Juniper account team about Juniper Professional Services offerings.
Juniper PS can design, test & build the network/part of the network as per Your requirements

+++++++++++++++++++++++++++++++++++++++++++++

Accept as Solution = cool !
Accept as Solution+Kudo = You are a Star !
Highlighted
Routing

Re: Separating multicast traffic and unicast traffic?

‎08-18-2014 09:03 PM

Hi.

 

I'm waiting your detail solution 🙂

Highlighted
Routing

Re: Separating multicast traffic and unicast traffic?

‎08-18-2014 09:49 PM

hi.

 

I think your guides only help to make IGP choose the route for unicast is same as multicast. I agree with you, if unicast and multicast are same next-hop, it's ok. But I want they are different. Unciast will flow one path, multicast is other. RPF only help to check multicast packet is valid, but multicast stream still flow as unicast flows. Is right ?

Highlighted
Routing

Re: Separating multicast traffic and unicast traffic?

‎08-19-2014 02:58 AM

Hello,

 


@hoand wrote:

hi.

 

I think your guides only help to make IGP choose the route for unicast is same as multicast.


I forgot to mention, that my suggestions have to be used in conjunction with Ato's suggestion to use inet.2 as multicast RPF table.

In this way You can separate unicast forwarding (which uses inet.0) and multicast RPF (which can use inet.2).

HTH

Thanks
Alex

_____________________________________________________________________

Please ask Your Juniper account team about Juniper Professional Services offerings.
Juniper PS can design, test & build the network/part of the network as per Your requirements

+++++++++++++++++++++++++++++++++++++++++++++

Accept as Solution = cool !
Accept as Solution+Kudo = You are a Star !
Highlighted
Routing

Re: Separating multicast traffic and unicast traffic?

‎08-19-2014 06:57 AM

inet.2 ís only used to check RPF. But, multicast streaming is still flow unicast routing. As you can see from my devices's status

FROM RP2 (nearest receiver)

root@SRSX240-01> show route 172.30.1.0

inet.0: 24 destinations, 25 routes (24 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

172.30.1.0/24 *[BGP/170] 2d 04:58:42, MED 3, localpref 100
AS path: 130 I
to 10.60.1.30 via ge-0/0/1.0
> to 10.60.1.22 via ge-0/0/2.0
[BGP/170] 09:15:50, MED 3, localpref 100
AS path: 130 I
> to 10.60.1.30 via ge-0/0/1.0

inet.2: 8 destinations, 9 routes (8 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

172.30.1.0/24 *[Static/5] 1d 07:13:32
> to 10.60.1.30 via ge-0/0/1.0
[BGP/170] 09:15:50, MED 3, localpref 100
AS path: 130 I
> to 10.60.1.30 via ge-0/0/1.0

you can see,172.30.1.0/24 is source of mulicast. From table inet.0, next-hop is ge-0/0/2 (without enabled PIM), and in inet.2, next-hop is ge-0/0/1 (with enabled PIM).

In this situation, receiver cannot receive multicast streaming.

 

If I change any BGP parameter to make ge-0/0/1 will be choosen for 172.30.1.0 in inet.0, receiver can receive normally.

 

Highlighted
Routing

Re: Separating multicast traffic and unicast traffic?

‎08-19-2014 01:55 PM
Not sure if you already tried pim rib-group with EXPORT rib inet.2? It should work.

http://www.juniper.net/techpubs/en_US/junos13.2/topics/example/routing-protocol-multicast-security-p...
Highlighted
Routing

Re: Separating multicast traffic and unicast traffic?

‎08-22-2014 05:25 AM

It does not work. 🙂 Do you have any solution for this case ? It seems Cisco supports this.

Highlighted
Routing

Re: Separating multicast traffic and unicast traffic?

‎08-22-2014 01:51 PM
I've seen it work fine across Junos releases since at least 7 years ago. If you have configured it correctly as mentioned (export rib) and as documented it may be a bug, please open a jtac case.
Highlighted
Routing

Re: Separating multicast traffic and unicast traffic?

‎08-23-2014 01:58 AM

Thanks for suggestion. I've resolved it. 🙂

Feedback