Oracle Fabric Interconnect F1-15
 
Oracle Fabric Interconnect F1-4
 

PLA-Support>Sun Systems>SAND>Network>SN-SND: Oracle Virtual Networking
 

In this Document

Purpose

Details

Applies to:

Purpose

Some of the caveats to be aware of when using LAG with the Oracle Fabric Interconnect

Details

LAG Considerations
 
As a general rule, the LAG configured on the Fabric Director 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 1-GE or 4-Port 10-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 Fabric Director 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. Fabric Director 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 Fabric Director slot. For example, you cannot create a LAG from ports on slot 5 and slot 6.
• LAG port changes are not revertive. As a result, if a port in the LAG goes down, traffic flows are remapped based on the hashing algorithm. 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.

This solution has no attachment