System Administration

This section describes system administration bugs in the Oracle Solaris 11 Express release.

System Hangs During iSCSI Boot After Installation on an iSCSI Device (6974162)

After you install the Oracle Solaris 11 Express release on an iSCSI device for iSCSI boot, the system might hang. You might be unable to log in to the system.

Workaround: Before the reboot, follow these steps to manually disable the svc:/network/physical:nwam service and then enable the svc:/network/physical:default service.

In this release, the default.xml Automated Installer manifest resides in the /var/ai/<port_number>/AI_data/default.xml directory and contains the following section:

<service name="network/physical" version="1" type="service">
<instance name="nwam" enabled="true"/>
<instance name="default" enabled="false"/>
</service>

To obtain the port number in the /var/ai/<port_number>/AI_data/default.xml directory, type the following command:

# installadm list -n <install_service>

To disable the NWAM service and to enable the default service, make the following changes to the default.xml AI manifest:

• Change the line <instance name="nwam" enabled="true"/> as follows:

  <instance name="nwam" enabled="false"/>

• Change the line <instance name="default" enabled="false"/> as follows:

  <instance name="default" enabled="true"/>

If you do not have the permission to configure the manifest on the installation server, you can use the following workaround on the client system. Use this workaround before the initial reboot after you install the current release on the iSCSI device.

1. Mount the iSCSI boot device.

   # beadm mount solaris /a

2. Modify the /a/etc/svc/profile/sc_profile.xml file by deleting the following lines:

   <service name="network/physical" version="1" type="service">
   <instance name="nwam" enabled="true"/>
   <instance name="default" enabled="false"/>
   </service>

3. Unmount the iSCSI device.

   # beadm unmount solaris

4. Reboot the system.

Default dumpadm Configuration Is Not Set to Capture Crash Dumps (5003)

The dumpadm configuration in this release is not configured to save crash dumps on reboot after panic.

Workaround: Use the dumpadm -y command to enable crash dumps at boot time.

# dumpadm -y