Go to main content
Oracle® Solaris 11.3 Release Notes

Exit Print View

Updated: July 2017
 
 

Hardware Issues

This section describes the hardware issues in the Oracle Solaris 11.3 release.

iSCSI Driver Might Give Up Prematurely When Trying to Reconnect to a Target (21216881)

When the connection to a target address is temporarily disrupted, the default iSCSI maximum connection retry of 180 seconds (3 minutes) might be insufficient for the initiators that are using an iSCSI boot device. The following error message is displayed:

NOTICE: iscsi connection(19) unable to connect to target iqn.1986-03.com.sun:02:hostname, target address 192.168.001.160 

Workaround: Increase iSCSI maximum connection retry to at least 1080 seconds (18 minutes) on initiators that are using the iSCSI boot device.

SPARC: suriadm lookup-uri Command Fails to Return All URI Information for a Device in the DMP Mode (21532185)

The suriadm lookup-uri command might fail to return all uniform resource identifier (URI) information for a Aura2.1 Flash Accelerator in the distributed memory parallel (DMP) mode. The following error message is displayed:

$ suriadm lookup-uri c10t5002361000099204d0
Failed to look up "file" URI for device: "/dev/dsk/c10t5002361000099204d0": Failed to look up file name associated with lofi device: unable 
to get mapping information: Invalid argument lu:luname.naa.5002361000099204
lu:initiator.naa.500605b0064c7100,target.naa.5002361000099204,luname.naa.5002361000099204
Failed to look up "nfs" URI for device: "/dev/dsk/c10t5002361000099204d0": Failed to look up file name associated with lofi device: unable
to get mapping information: Invalid argument
  

Workaround: Run the following command to enable MPxIO mode:

$ stmsboot -e

After you change the host into MPxIO mode, the suriadm lookup-uri command shows all the information.

SPARC: OPL System Displays Error Message (19562754)

Oracle public library (OPL) systems (M3000, M4000, M5000, M8000) might report the following message from the ntp daemon:

Aug 26 02:22:19 mysystem.us.example.com ntpd[956]: [ID 702911 daemon.notice] frequency error 7054 PPM exceeds tolerance 500 PPM
Aug 26 02:31:04 mysystem.us.example.com ntpd[956]: [ID 702911 daemon.notice] frequency error 7021 PPM exceeds tolerance 500 PPM
Aug 26 02:33:16 mysystem.us.example.com ntpd[956]: [ID 702911 daemon.notice] frequency error 2139 PPM exceeds tolerance 500 PPM
Aug 26 02:42:03 mysystem.us.example.com ntpd[956]: [ID 702911 daemon.notice] frequency error 7037 PPM exceeds tolerance 500 PPM  

Workaround: Verify that the time is correct on your system. If not correct, reset it as appropriate.