Solaris 11 update 1 :: Host Driver System Limitations and Restrictions on Oracle Fabric Interconnect

Asset ID:	1-79-1574296.1
Update Date:	2017-07-11
Keywords:

Solution Type Predictive Self-Healing Sure

Solution 1574296.1 : Solaris 11 update 1 :: Host Driver System Limitations and Restrictions on Oracle Fabric Interconnect

Applies to:

Oracle Fabric Interconnect F1-15 - Version All Versions and later
Oracle Fabric Interconnect F1-4 - Version All Versions and later
Information in this document applies to any platform.

Purpose

This section documents system limitations and restrictions for this version of the Solaris host driver version 5.1.1-SL.

Details

System Limitations and Restrictions

This section documents system limitations and restrictions for this version of the Solaris host driver.

A vNIC or vHBA on a Solaris Host Cannot be deleted if It is Part of an LDOM or Solaris Zone

Currently, a vNIC or vHBA cannot be deleted from a Solaris host if that vNIC or vHBA is part of a Solaris Logical Domain (LDOM) or zone, the vNIC or VHBA cannot just be deleted from the host. Instead, to delete a vNIC or vHBA that is in an online zone or LDOM, must first disassociate the vNIC or vHBA from the zone/LDOM, then delete the vNIC or vHBA.

Names for vNICs and vHBAs Cannot Be the Same on a Solaris Host

Release 5.1.1-SL host drivers do not support creation of a vNIC and vHBA with the same name. Be aware that when creating a vNIC or vHBA, the two names must be different.

Limitation on the Length of Virtual Resource Names Under Solaris

With Solaris operating systems, the names of virtual resources are restricted to the following lengths:

• vNICs: 10 characters

• vHBAs: 15 characters

• server profiles: 31 characters

Consideration for Naming vNICs and vHBAs under Solaris

With Solaris operating systems, vNICs and vHBAs can be named with the standard Oracle notation of:

• <vnic-name>.<server-profile>

• <vhba-name>.<server-profile>

However, Oracle strongly recommends that using a numeral at the end of a vNIC and vHBA name so that the vNIC and vHBA receive correctly enumerated instance numbers. There are no special numerals in the vNIC or vHBA name string (for example, 0 is not reserved). Threrefore, can use any number of numerals in the vNIC and vHBA strings, as long as the entire name string complies with the name length limitation documented in release notes.

Some examples of acceptable vNIC and vHBA names:

• vnic0.profile1, vnic01.profile1, vnic001.profile1

• vhba1.profile1, vhba123.profile1, vhba987.profile1

• oracle2.profile1, webapps9.profile1, backups3.profile

Attachments

This solution has no attachment