Defining A Multicast Bandwidth Map - Juniper JUNOSE 11.0.X MULTICAST ROUTING Configuration Manual

JUNOSe 11.0.x Multicast Routing Configuration Guide

Defining a Multicast Bandwidth Map

Multicast interface-level admission control, port-level admission control, and QoS
adjustment all use a single multicast bandwidth map. The multicast bandwidth map
is a route map that uses the set admission-bandwidth, set qos-bandwidth, set
admission-bandwidth adaptive, or set qos-bandwidth adaptive commands. The
adaptive commands configure an auto-sense mechanism for measuring the multicast
bandwidth.
NOTE: Even though you can include any of the above commands several times in a
route map entry, only the last admission-bandwidth command or qos-bandwidth
command in the bandwidth map is used. In other words, if you included the set
qos-bandwidth command first and then the set qos-bandwidth adaptive command,
the bandwidth map would use the set qos-bandwidth adaptive command.
Interface- and port-level admission control is performed when an OIF on the interface
or port is added to the mroute for a given (S,G) multicast data stream and the multicast
bandwidth map contains a set admission-bandwidth or set admission-bandwidth
adaptive action for that (S,G).
QoS adjustment is performed on the joining interface when an OIF is added to the
mroute for a given (S,G) data stream and the multicast bandwidth map contains a
set qos-bandwidth or set qos-bandwidth adaptive action for that (S,G).
NOTE: You can create a single route map with the set admission-bandwidth
command, the set qos-bandwidth command, or both. However, creating an entry
with only one of these set commands enables only that specific function for the
matched address (that is, only multicast traffic admission control or only QoS
adjustment). The same is true for the adaptive commands.
154
Defining a Multicast Bandwidth Map
Permanent mroutes are removed if a topology change occurs that affects the
mroute.
Permanent mroutes may be removed due to certain protocol actions (for example,
PIM sparse mode switching from shared to shortest path tree).
Outgoing interface lists of permanent mroutes may change due to protocol
actions.
Example
host1(config)#ipv6 multicast-routing permanent-mroute routesv61
Use the no version to prevent any new mroutes from becoming permanent. To
remove existing permanent mroutes, use the clear ipv6 mroute command.
See ipv6 multicast-routing permanent-mroute