When you initially create a LAG, you must specify at least one of the 10 GbE ports. After the LAG is created, you can add individual ports to the LAG.
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 (if applicable)
IPv4 source and destination addresses (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 can be assigned to this port. Existing traffic flows are not remapped onto the port when it comes back up.
You assign static port membership in a LAG. 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 fabric.