
Design Guide – DOC. 7977C DigitalMedia NVX Series System •13
Network Multicast Functionality
NVX networks rely on multicast functionality exclusively to send and receive video, even in
the simplest case of a single encoder endpoint and single decoder endpoint. Internet Group
Management Protocol (IGMP) multicast in the Ethernet context replaces a fixed switching
architecture in AV distribution. The challenge is to ensure that such traffic is capable of any
permutation of one encoder to many decoders, and vice-versa without adversely affecting
or being affected by other network devices.
Segregation of NVX traffic by using a VLAN or MPLS is generally the first step in enabling
multicast. A VLAN or MPLS ensures that NVX traffic stays on the NVX network and does not
route out to other network segments to interfere with their operation, nor allow traffic from
other network segments to interfere with NVX operation. Within that segment, however, all
ports can still be flooded by IGMP traffic regardless of if that traffic was intended to be sent
or received by a network device at any given point in time. This will result in interference with
the network operation and can even be a means of implementing a denial-of-service attack
on a network if done maliciously.
To ensure that only traffic between intended multicast senders and multicast receivers
appears at a given port, a switch feature called IGMP snooping must be enabled. Snooping
refers to the ability of the switch to limit multicast traffic only to ports between intended
senders and receivers. The NVX supports both versions of IGMP snooping, IGMPv2 and
IGMPv3.
In order for the switch to understand where route limiting will be specifically implemented in
the network for multicast traffic, a network switch that assesses and maps the network for
multicast nodes in the NVX network called an IGMP querier must be enabled. Normally, a
single switch is selected by address to act as the IGMP querier, but the switch with the
lowest numerical IP address on the network will typically be the default when multiple
switches are configured as queriers. The default leave time for the querier (typically around
125s) is normally sufficient for an NVX network unless there are other specific requirements
that a network designer must account for.
Further assisting the discovery and optimization of multicast network traffic routing is a
feature called Protocol Independent Multicast (PIM). There are different modes of PIM such
as Sparse Mode (PIM-SM), Dense Mode (PIM-DM) and Source-Specific (PIM-SSM), but
NVX networks should be configured to use PIM-SM. PIM-SM assists in finding the shortest
trees per path from any given multicast source to multicast receivers on a network and is
more scalable than PIM-DM or PIM-SSM. PIM-SM also prevents edge-switch link saturation
as well as network loops in the routing of multicast traffic.
Enabling network QoS is also useful in prioritizing NVX traffic over other ancillary traffic such
as control traffic. Although there are multiple mechanisms that enable QoS, the most
essential part of this is to enable the highest priority possible on IGMP multicast traffic. For
example, enabling 802.1q VLAN tagging support in the switch, and then enabling and
assigning an 802.1p priority (for example, 5, 6, or 7) to NVX addresses, ports or IGMP
protocol traffic, will prioritize NVX traffic over other traffic at both the source and destination.
Other traffic such as HTTP for web services, or SSH for console access, would be assigned
lower priority numbers (for example, 0 to 4) based on their respective addresses, ports, or
protocols. Other protocols exist for QoS (depending on the switch vendor) but are
configured in a similar way to the 802.1p and 802.1q example. It is critical to ensure that all
traffic types are affirmatively accounted for in QoS setup to ensure successful QoS
operation.