As a general rule, the LAG configured on the fabric must match the LAG configuration on the peer device at the other end of the Ethernet link. Be aware of the following considerations:
A LAG consists of multiple physical ports of the same speed. A LAG consisting of all 1-GB links is valid, but you cannot create a LAG with a mixture of speeds.
Link properties between the fabric and the peer Ethernet device must be identical at both ends of the LAG. For example:
Link speed – Auto-negotiation on the peer Ethernet device can cause link speed to change.
Full duplex mode – Oracle Virtual Networking LAGs support only full-duplex communication.
These settings must be identical on both ends of the LAG. They cannot be changed for the LAG in runtime, so verify that they are identical before creating the LAG and populating it with ports.
A LAG's ports must all reside on the same fabric slot. For example, you cannot create a LAG from ports on slot 5 and slot 6.
LAG port changes are not reverted. As a result, if a port in the LAG goes down, traffic flows are remapped based on the hashing algorithm (see Port Assignment in the LAG). When the port comes back up, traffic does not revert back to the port that was originally supporting the traffic. Only new traffic flows can be mapped onto this port.