User`s guide

Chapter 13 Link Aggregation Groups (LAGs) 227
When a LAG contains multiple ports, traffic is mapped to the appropriate port based
on a hashing algorithm that considers the following parameters of the packets
originating from the vNICs in a LAG:
■ Source and destination MAC address and (if applicable)
■ IPv4 source and destination addresses and (if applicable)
■ TCP and UDP source and destination ports (if applicable)
Ports that are assigned to a LAG remain part of the LAG regardless of their state. If
a port is in the up/up state, and transitions to the up/down state, the port does not
leave the LAG. Instead, it remains a member of the LAG but does not support traffic
until it transitions back to the up/up state. When the port returns to the up/up state,
it can resume operation in the LAG. However, only new traffic flows may be
assigned to this port. Existing traffic flows are not remapped onto the port when it
comes back up.
Ports membership in a LAG is statically assigned by you. Ports are not dynamically
added or deleted based on LAG changes on the peer Ethernet switch. As a result,
any time you make a LAG change on the peer device at the end of the Gigabit
Ethernet link, you must make the corresponding change to the LAG on the Oracle
Fabric Interconnect.
LAG Considerations
As a general rule, the LAG configured on the Oracle Fabric Interconnect must match
the LAG configuration on the peer device at the other end of the Ethernet link.
Specifically, you should be aware of the following considerations:
■ A LAG consists of multiple physical ports of the same speed on the 10-Port GE
module. A LAG consisting of all 1 GB links is valid, but a LAG with a mixture of
1 Gbps and 100 Mbps cannot be created.
■ Link properties between the Oracle Fabric Interconnect and the peer Ethernet
device must be identical at both ends of the LAG. Some examples:
■ Link speed. Be aware that auto-negotiation on the peer Ethernet device can
cause link speed to change.
■ Full duplex mode. OVN LAGs support only full-duplex communication.
■ MTU size on the link.
■ These settings must be identical on both ends of the LAG. They cannot be
changed for the LAG in runtime, so be sure that they are identical before creating
the LAG and populating it with ports.
■ A LAG’s ports must all reside on the same Oracle Fabric Interconnect slot. For
example, you cannot create a LAG from ports on slot 5 and slot 6.