Specifications

Alcatel-Lucent Page 29
OmniSwitch 6850 Series
the same VLAN. However, SSM forwarding between different VLANs (routing) is supported. In
addition, the current implementation of IGMPv3 and SSM only forwards packets to a list of included
sources for a given multicast destination. Exclude list forwarding is not supported, as it is not a
requirement for SSM, and specifically Protocol Independent Multicast–Source Specific Multicast
(PIM-SSM).
IP Multicast Switching and Routing (IPMSR) IP multicast routing can be used for IP Multicast Switching and Routing (IPMSR). IP multicast routing
is a way of controlling multicast traffic across networks. The IP multicast router discovers which
networks want to receive multicast traffic by sending out Internet Group Management Protocol
(IGMP) queries and receiving IGMP reports from attached networks. The IGMP reports signal that
users want to join a multicast group. The IPv6 multicast router discovers multicast listeners by sending
out Multicast Listener Discovery (MLD) Protocol queries and receiving MLD reports from attached
networks. The MLD reports signal that users want to join a IPv6 multicast group.
If there is more than one IP multicast router in the network, the router with the lowest IP address is
elected as the querier router, which is responsible for querying the sub-network for group members.
The IP multicast routing package provides the following two separate protocols:
• Protocol Independent Multicast — Sparse Mode (PIM-SM) and Dense Mode (PIM-DM)
• Distance Vector Multicast Routing Protocol (DVMRP)
The multicast routing protocols build and maintain a multicast routing database. The multicast routing
protocols forward multicast traffic to networks that have requested group membership to a specific
multicast group. IPMS uses decisions made by the routing protocols and forwards multicast traffic to
ports that request group membership.
Multicast Address Boundaries Multicast boundaries confine scoped multicast addresses to a particular domain. Confining scoped
addresses helps to ensure that multicast traffic passed within a multicast domain does not conflict with
multicast users outside the domain.
Multicast Boundary Specifications:
RFCs Supported:
2365—Administratively Scoped IP Multicast
2932—IPv4 Multicast Routing MIB
Maximum Multicast Flows per switch: 400 (with hardware routing; see note below)
Valid Scoped Address Range: 239.0.0.0 to 239.255.255.255
Note. If software routing is used, the number of total flows supported is variable, depending on the
number of flows and the number of routes per flow.
Multicast Routing The OmniSwitch 6850 Series supports multicast routing and includes configuration options for
multicast address boundaries, the Distance Vector Multicast Routing Protocol (DVMRP), and
Protocol-Independent Multicast (PIM).
Multicast traffic consists of a data stream that originates from a single source and is sent to hosts that
have subscribed to that stream. Live video broadcasts; video conferencing, corporate communications,
distance learning, and distribution of software, stock quotes, and news services are examples of
multicast traffic.
Multicast traffic is distinguished from unicast traffic and broadcast traffic.
Multicast boundaries confine scoped multicast addresses to a particular domain. Confining scoped
addresses helps to ensure that multicast traffic passed within a multicast domain does not conflict with
multicast users outside the domain.
Distance Vector Multicast Routing Protocol (DVMRP) is a dense-mode multicast routing protocol
designed to assist routers in propagating IP multicast traffic through a network. DVMRP works by
building per-source broadcast trees based on routing exchanges, then dynamically creating per-source,
group multicast delivery trees by pruning the source’s truncated broadcast tree.
D
D
i
i
a
a
g
g
n
n
o
o
s
s
i
i
n
n
g
g
S
S
w
w
i
i
t
t
c
c
h
h
P
P
r
r
o
o
b
b
l
l
e
e
m
m
s
s
Several tools are available for diagnosing problems that may occur with the switch. These tools include:
• Port Mirroring
• Port Monitoring
• Remote Monitoring (RMON) probes
• Switch Health Monitoring
• SFlow
• Monitoring Memory tools
• Switch Logging
Port mirroring copies all incoming and outgoing traffic from a single mirrored Ethernet port to a second mirroring Ethernet port, where it can be monitored with
a Remote Network Monitoring (RMON) probe or network analysis device without disrupting traffic flow on the mirrored port. Switch Health monitoring
software checks previously configured threshold levels for the switch’s consumable resources, and notifies the Network Monitoring Station (NMS) if those
limits are violated.
Port Mirroring Ethernet ports supporting port mirroring include 10BaseT/100BaseTX/1000BaseT (RJ-45),
1000BaseSX/LX/LH, and 10GBaseS/L (LC) connectors. When port mirroring is enabled, the active
“mirrored” port transmits and receives network traffic normally, and the “mirroring” port receives a
copy of all transmit and receive traffic to the active port. You can connect an RMON probe or network
analysis device to the mirroring port to see an exact duplication of traffic on the mirrored port without
disrupting network traffic to and from the mirrored port.
Port mirroring runs in the Chassis Management software and is supported for Ethernet (10 Mbps), Fast