Managing Network Datalinks in Oracle® Solaris 11.2

Exit Print View

Updated: September 2014
 
 

Requirements for Link Aggregations

    The link aggregation configuration has the following requirements:

  • The datalinks to be configured into an aggregation should not have any IP interface configured over them.

  • You can create link aggregations only from the global zone. You cannot use datalinks to create a link aggregation from a non-global zone even if you do not have any IP interface configured over the datalinks. Link aggregation only combines multiple physical NICs but in a non-global zone all interfaces are virtual. Therefore, you cannot create a link aggregation from the non-global zone.

  • All the datalinks in the aggregation must run at the same speed and in full-duplex mode.

  • For DLMP aggregations, you must have at least one switch to connect the aggregation to the ports in the other systems. You cannot use a back-to-back setup when configuring DLMP aggregations.

  • On SPARC based systems, each datalink must have its own unique MAC address. For information, see How to Ensure That the MAC Address of Each Interface Is Unique in Configuring and Administering Network Components in Oracle Solaris 11.2 .

  • (Trunk aggregation only) Devices must support link state notification as defined in the IEEE 802.3ad Link Aggregation Standard in order for a port to attach to a trunk aggregation or to detach from a trunk aggregation. Devices that do not support link state notification can be aggregated only by using the –f option of the dladm create-aggr command. For such devices, the link state is always reported as UP. For information about the use of the –f option, see How to Create a Link Aggregation.