Campus Fabric and IP Multicast Considerations

In a Campus Fabric domain, forwarding decisions always occur in the CB, even for incoming traffic on a PE port.

In the upstream direction (from a PE to a CB), the packets are tagged with an E-tag to identify the ingress PE or SPX port. In the downstream direction (from a CB to a PE), the packets are tagged with an E-tag to identify the egress PE ports. E-channel identifiers (E-CIDs) contained in the E-tag header are used to identify a single PE port or a set of PE ports.

Multicast E-CID and IEEE 802.1BR

The point-to-multipoint E-channels used for remote replication are identified by an E-CID with a value in the range of 0x1000 to 0x3FFF (values less than this are reserved for E-CIDs associated with point-to-point E-channels).

General Campus Fabric Multicast Considerations

Unless otherwise stated, Layer 2 and Layer 3 multicast features supported on a standalone ICX 7650, ICX 7750, or ICX 7850 are supported by the CB in a Campus Fabric domain, and the Layer 2 and Layer 3 scaling capacity are the same.

Note: An IP address cannot be configured on a PE port. Consequently, IPv4 and IPv6 multicast routing configuration is not supported on an IP interface for any PE unit.
Note: For details on Campus Fabric configuration for multicast, refer to the RUCKUS FastIron IP Multicast Configuration Guide.

In this section:

  1. Considerations for Multicast Forwarding on PE Units
Parent topic: Campus Fabric Considerations for Layer 2, Layer 3, Multicast, Security, and QoS