Confluence will be unusable 23-July-2024 at 06:00 due to a Crowd upgrade.
...
...
Multi-chip systems using both Tahoe and Bali devices may, depending on the hardware learning configuration,
require consistent frame hashing across the two generations of switches. For example, in a fat tree with
learning enabled in the spine chips, it is important that (a) the hash function be symmetric and (b) all edge
switches use the same hash function. The following table summarizes the configuration requirements that
are necessary in order to achieve consistent hashing between Bali and Tahoe devices.
Table 25: Summary of Hash Configuration Requirements for Tahoe Compatibility"
Bali Requirement | Tahoe Requirement | Motivation |
---|---|---|
TahoeCompatible == 1 UseSMAC == 0, UseDMAC == 0 | - | Select Tahoe Compatibility mode. |
UseType == 0 | IncludeTypeAndSource == 0 | See note above about differences between Bali & Tahoe in their handling of EtherType. |
Page 351:
Name | Bit | Description | Type | Default |
---|---|---|---|---|
FloodGlort (was GlortFlood) | 15: 0 | Defines the glort to use when flooding. | RW | 0x0 |
XcastGlort (was GlortBroadcast) | 31: 16 | Defines the glort used for broadcast and multicast. Note that multicast in this case is defined as MAC addresses that resolve to a destination mask instead of a glort, which is how multicast is implemented in FM2000, but is deprecated in FM4000 | RW | 0x0 |