TechLibrary

Navigation

Supported Platforms

You can use the bridge-domain statement's service-id id option to specify the multichassis aggregated Ethernet configuration.

The service-id statement is mandatory for non-single VLAN type bridge domains (none, all or vlan-id-tags:dual).
It is optional for bridge domains with a VID defined.
If no service-id is defined in the latter case, it will be picked up from the RTT's service-id configuration.
The bridge level service-id is required to link related bridge domains across peers, and should be configured with the same value.
The service-id values share the name space across all bridging and routing instances, and across peers. Thus, duplicate values for service-ids are not permitted across these entities.
A change of bridge service-id is considered catastrophic, and the bridge domain is reincarnated.

This procedure allows you to enable or disable the replication feature. This option applies to all instances.

To configure IGMP snooping in active-standby mode:

Use the multichassis-lag-replicate-state statement at the multicast-snooping-options hierarchy level in the master instance.
multicast-snooping-options {...multichassis-lag-replicate-state; # REQUIRED}

The interchassis link, interface icl-intf-name, of the learning domain should be a router facing interface.

Use the interface icl-intf-name statement at the protocols igmp-snooping hierarchy level, as shown in the following example:
protocols {igmp-snooping {interface icl-intf-name {multicast-router-interface;}}}