Specifications

Clarifications and Known Behaviors
ExtremeWare 7.3.1b3 Release Notes 69
Cross module trunking is not supported on WDMi modules (PD2-176314520).
Master Slot Must Be Active for CMT
The slot with the master load-sharing port must be populated and active when you configure a
cross-module load-sharing group. If the master slot is unavailable at configuration, cross-module
load-sharing traffic is not forwarded (PD2-175825901, PD2-175854401).
MSM-3 Log Might Be Out of Chronological Order
Log events are stored independently on the master and slave MSM-3. Thus, a failover might cause the
log to appear out of chronological order, or missing information. Concatenating the logs provides all log
information (PD2-172852704).
Source Addresses Might Age Out of FDB
If a MAC source address is exclusively sourced on a slave CMT slot, such as with a port-based
algorithm, the FDB entry might be aged out. To avoid this, use address-based load sharing on the
neighbor switch (PD2-170942776).
Do Not Use Static FDB Entries with CMT
Do not use static FDB entries with cross-module trunking. If the CMT master fails, static FDB entries are
not transferred to the group members (PD2-170942732, PD2-170942701).
Saving Health Check Configuration After Failure Causes Console Crash
If an MSM fails a system health check with packet memory errors and is taken offline, the slave
becomes the master, but you cannot save the configuration. To avoid this, clear the diagnostics, upload
the configuration, and reboot the switch before saving (PD2-171914501).
Diagnostics on MSM-3 with Hitless Failover Causes Failover and Spurious Message
Running diagnostics on the master MSM-3 with hitless failover enabled causes the MSM-3 to fail over
to the slave and log a hardware failure message. You can safely ignore this message (PD2-168317013).
Do Not Configure a Port-Based Backplane Algorithm When CMT is Enabled
Do not configure a port-based backplane policy when CMT is enabled. It might cause all egress ports on
a given slot to be skipped. To work around this problem, configure an address-based backplane policy.
In a similar manner, if a port-based algorithm is selected for the trunk, some egress ports might be
skipped. To change the load share policy of a trunk, disable sharing for the port and enable sharing
with an address-based policy, then reboot the switch (PD2-165883601).
Cross-Module Trunking and ACLs
Flooding on a CMT trunk cannot initially be blocked by ACLs. After the remote end responds with a
PDU, the destination address is learned via source address learning. Once the address is learned,
packets are blocked in hardware by an ACL (PD2-153404501, PD2-115139620, PD2-130299801,
PD2-130299807).