Multicast Traffic Receipt Without Forwarding; Figure 15: Multicast Oif Mapping - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - MULTICAST ROUTING CONFIGURATION GUIDE 2010-10-07 Configuration Manual

Software for e series broadband services routers multicast routing configuration guide
Table of Contents

Advertisement

Multicast Traffic Receipt Without Forwarding

Copyright © 2010, Juniper Networks, Inc.

Figure 15: Multicast OIF Mapping

One disadvantage to using multicast OIF mapping is that the multicast traffic bypasses
any QoS treatment that is applied to subscriber interfaces. Configuring QoS adjustment
resolves this problem. (See Parameter Definition Attributes for QoS Administrators
Overview for additional information about configuring QoS adjustment.) With QoS
adjustment configured, when a subscriber requests to receive a multicast stream (or,
more appropriately, when an OIF is added to the mroute), the router reduces the unicast
QoS bandwidth applied to the subscriber interface (that is, the join interface) by the
amount of bandwidth for that multicast stream.
In this case, the router is not given the responsibility of forwarding multicast streams.
Instead, the service provider arranges for the router to receive the multicast streams so
the router can detect the flow and perform QoS adjustment. An OIF map is installed that
maps the traffic streams to a loopback interface configured for MLD version passive.
This means that when the traffic is received, a null mroute is installed (that is, an mroute
with an empty OIF list) and the router applies the QoS adjustment to the join interface.
See Figure 16 on page 156.
NOTE: Ensure that PIM-SM (or any other upstream multicast protocol) is
informed of the group (or source-group) interest.
Chapter 5: Configuring IPv6 Multicast
155

Advertisement

Table of Contents
loading

This manual is also suitable for:

Junose 11.3

Table of Contents