Comparing Trunk and DLMP Aggregation
This section presents a general comparison of the two types of link aggregation.
Table 2-1 Feature Comparison of Trunk and DLMP Aggregation
|
|
|
|
Link-based failure detection
|
Supported
|
Supported
|
|
LACP
|
Supported
|
Not supported
|
|
Use of standby interfaces
|
Not supported
|
Not supported1
|
|
Span multiple switches
|
Not supported unless using vendor proprietary solution
|
Supported
|
|
Switch configuration
|
Required
|
Not required
|
|
Policies for load balancing
|
Supported
|
Not applicable
|
|
Load spreading across all of the aggregation's ports
|
Supported
|
Limited2
|
|
User-defined flows for resource management
|
Supported
|
Supported
|
|
Link protection
|
Supported
|
Supported
|
|
Back-to-back configuration
|
Supported
|
Not supported3
|
|
1 Each DLMP client is associated with exactly one DLMP port. The
remaining ports act as available ports for the DLMP clients, but you cannot configure these
available ports.
2 The aggregation spreads its VNICs across all ports. However,
individual VNICs cannot spread the load on multiple ports.
3 DLMP aggregations must always use an intermediary switch to send
packets to other destination systems. However, no switch configuration is required for DLMP.