|Skip Navigation Links|
|Exit Print View|
|Oracle Solaris 11 Release Notes Oracle Solaris 11 Information Library|
This section describes configuration issues in the Oracle Solaris 11 release.
When an Oracle Solaris instance is unconfigured, the custom SMF site profiles in the /etc/svc/profile/site directory are deleted.
Workaround: During unconfiguration, place the custom site profiles to be preserved in a subdirectory of the /etc/svc/profile/site directory.
When you create a profile using the following sysconfig command, the System Configuration Tool (SCI) does not show the network configuration screens:
# sysconfig create-profile
This issue occurs only when you are logged into a non-global zone that has been configured for shared IP. The generated profile does not contain any network information because the SCI tool does not see any network in the zone.
Workaround: Choose one of the following workarounds:
Generate profiles outside the zone.
Manually add the missing configuration information into the generated profile.
Run sysconfig create-profile and pass the correct groupings for a non-global zone with shared IP:
# sysconfig create-profile -g location,identity,naming_services,users
For system reconfiguration purposes, the sysconfig configure command has a -c option that can take a directory as a parameter. This directory can contain subdirectories with system configuration profiles in them.
Due to the flattening of the directory structure, if there are any files within the directory tree that have the same name, then one of these files is used to reconfigure the system. As a result, the system would be partially reconfigured using one of the profiles. For example, assume that you have the following directory structure:
directory-name/profiles1/sc_profile.xml directory-name/profiles2/sc_profile.xml directory-name/profiles3/sc_profile.xml
If you execute the sysconfig command with the -c option, the system is partially reconfigured by using only one of the profiles.
# sysconfig configure -c directory-name
Workaround: Ensure that each profile has an unique name regardless of its location in the directory tree. For example:
directory-name/profiles1/sc_profile_a.xml directory-name/profiles2/sc_profile_b.xml directory-name/profiles3/sc_profile_c.xml
A destructive system unconfiguration occurs in a non-global zone in the following two scenarios:
When booting a freshly cloned non-global zone
When running a destructive sysconfig configure or sysconfig unconfigure command inside a non-global zone
When you use the sysconfig unconfigure command with the --destructive option, the system end state is in maintenance mode. This maintenance mode provides a login prompt that allows you to log in as root user without requiring a password.
# sysconfig unconfigure --destructive
Destructive unconfiguration fails for svc:/system/config-user in a non-global zone. In this case, the unconfiguration process fails to completely unconfigure the user and root configuration information. As a result, you cannot log in at the maintenance prompt without a root password. The following error message is displayed:
Unconfiguration failed for svc:/system/config-user:default
You will also see this error message when you boot a freshly cloned non-global zone or when you run the sysconfig configure command with the --destructive option.
# sysconfig configure --destructive
When you use the sysconfig configure command with the --destructive option and a cloned zone, the impact is minimal.
In both scenarios, the final state is a configured and an operational non-global zone. Entries in the /etc/sudoers file might not be removed as expected.
Workaround: Log in as a root user using the password that was set before unconfiguring the non-global zone. You must edit the /etc/sudoers file to remove any entries.
To simplify the process of creating a system configuration profile, the sysconfig(1M) command can be used as follows:
# sysconfig create-profile
sysconfig generates a system configuration profile based on the information provided in the configuration screens. If the initial user account configured in the Users screen exists as a local user account on the system, sysconfig refuses to proceed and displays the following error message:
<login> cannot be used
Workaround: Create a sample system configuration profile with different user name and manually modify the generated profile.