Multicast Policies; Implementation Information; Ipv4 Multicast Policies - Dell Force10 C150 Configuration Manual

Ftos configuration guide ftos 8.4.2.7 e-series terascale, c-series, s-series (s50/s25)

Hide thumbs Also See for Force10 C150:

Manual (57 pages)

Manual (66 pages)

Quick start manual (33 pages)

Table of Contents

Because protocol control traffic in FTOS is redirected using the MAC address, and multicast control

traffic and multicast data traffic might map to the same MAC address, FTOS might forward data traffic

with certain MAC addresses to the CPU in addition to control traffic.

As the upper five bits of an IP Multicast address are dropped in the translation, 32 different multicast

group IDs all map to the same Ethernet address. For example, 224.0.0.5 is a well known IP address for

OSPF that maps to the multicast MAC address 01:00:5e:00:00:05. However, 225.0.0.5, 226.0.0.5, etc.,

map to the same multicast MAC address. The Layer 2 FIB alone cannot differentiate multicast control

traffic multicast data traffic with the same address, so if you use IP address 225.0.0.5 for data traffic,

both the multicast data and OSPF control traffic match the same entry and are forwarded to the CPU.

Therefore, do not use well-known protocol multicast addresses for data transmission, such as the ones

Protocol Ethernet Address

The FTOS implementation of MTRACE is in accordance with IETF draft draft-fenner-traceroute-ipm.

Multicast is not supported on secondary IP addresses.

Egress L3 ACL is not applied to multicast data traffic if multicast routing is enabled.