Multicast Routing And Forwarding And Multicast Domains; Multicast Distribution Trees - Cisco WS-SUP32-GE-3B - Supervisor Engine 32 Software Configuration Manual

Software configuration guide
Hide thumbs Also See for WS-SUP32-GE-3B - Supervisor Engine 32:
Table of Contents

Advertisement

Understanding How MVPN Works
MVPN routes and forwards multicast packets for each individual VPN routing and forwarding (VRF)
instance, as well as transmitting the multicast packets through VPN tunnels across the service provider
backbone.
MVPN is an alternative to IP-in-IP generic route encapsulation (GRE) tunnels. GRE tunnels are not a
readily scalable solution and they are limited in the granularity they provide to customers.

Multicast Routing and Forwarding and Multicast Domains

MVPN adds multicast routing information to the VPN routing and forwarding table. When a
provider-edge (PE) router receives multicast data or control packets from a customer-edge (CE) router,
forwarding is performed according to the information in the multicast VRF (MVRF).
MVRF is also commonly referred to as multicast over VRF-lite.
Note
Each MVRF maintains the routing and forwarding information that is needed for its particular VRF
instance. An MVRF is created and configured in the same way as existing VRFs, except multicast
routing is also enabled on each MVRF.
A multicast domain constitutes the set of hosts that can send multicast traffic to each other within the
MPLS network. For example, the multicast domain for a customer that wanted to send certain types of
multicast traffic to all global employees would consist of all CE routers associated with that enterprise.

Multicast Distribution Trees

The MVPN feature establishes at least one multicast distribution tree (MDT) for each multicast domain.
The MDT provides the information needed to interconnect the same MVRFs that exist on the different
PE routers.
MVPN supports two MDT types:
To create data MDTs, each PE router that is forwarding multicast streams to the backbone periodically
examines the traffic being sent in each default MDT as follows:
1.
Catalyst Supervisor Engine 32 PISA Cisco IOS Software Configuration Guide, Release 12.2ZY
22-2
Default MDT—The default MDT is a permanent channel for PIM control messages and
low-bandwidth streams between all PE routers in a particular multicast domain. All multicast traffic
in the default MDT is replicated to every other PE router in the domain. Each PE router is logically
seen as a PIM neighbor (one hop away) from every other PE router in the domain.
Data MDT—Data MDTs are optional. If enabled, they are dynamically created to provide optimal
paths for high-bandwidth transmissions, such as full-motion video, that do not need to be sent to
every PE router. This allows for on-demand forwarding of high-bandwidth traffic between PE
routers, so as to avoid flooding every PE router with every high-bandwidth stream that might be
created.
Each PE router periodically samples the multicast traffic (approximately every 10 seconds for
software switching, and 90 seconds for hardware switching) to determine whether a multicast stream
has exceeded the configured threshold. (Depending on when the stream is sampled, this means that
in a worst-case scenario, it could take up to 180 seconds before a high-bandwidth stream is
detected.)
Chapter 22
Configuring IPv4 Multicast VPN Support
OL-11439-03

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Catalyst supervisor engine 32 pisa

Table of Contents