1z0-580 Oracle Solaris 11 Installation and Configuration Essentials Questions and Answers

Note:

* second line in exhibit (minor typo):

boot-device = disk net

*The line starting with net is:

/pci@780/pci@0/pci@1/network@0

The Stop rights profile is the simplest way to create a restricted shell. The authorizations and rights profiles that are assigned in the policy.conf file are not consulted. In the default configuration, the role or user is not assigned the Basic Solaris User rights profile, the Console User rights profile, or the solaris.device.cdrw authorization.

Example:

Assign the Desktop Applets rights profile and the Stop rights profile to the user.

# usermod -P "Desktop Applets,Stop" username

This user does not have the Basic Solaris User rights profile or the Console User rights profile. Therefore, no commands other than the commands in the Desktop Applets rights profile can be run by this user.

Note:

*The usermod utility modifies a user's login definition on the system. It changes the definition of the specified login and makes the appropriate login-related system file and file system changes.

*Synopsis

usermod [-u uid [-o]] [-g group] [-G group [, group...]]

[-d dir [-m]] [-s shell] [-c comment] [-l new_name]

[-f inactive] [-e expire]

[-A authorization [, authorization]]

[-P profile [, profile]] [-R role [, role]]

[-K key=value] login

*-P profile

One or more comma-separated rightsprofiles defined in prof_attr.

*prof_attr

- profile description database

If an error occurs when booting the new BE, activate and boot to the previous BE.

Example:

# beadm activate solaris

# init 6

B(not C):A zone is a virtualized operating system environment that is created within a single instance of the Oracle Solaris operating system. Oracle Solaris Zones are a partitioning technology that provides an isolated, secure environment for applications.

Note:

*When you create a zone, you produce an application execution environment in which processes are isolated from the rest of the system. This isolation prevents a process that is running in one zone from monitoring or affecting processes that are running in other zones. Even a process running with root credentials cannot view or affect activity in other zones. A zone also provides an abstract layer that separates applications from the physical attributes of the machine on which the zone is deployed. Examples of these attributes include physical device paths and network interface names. The default non-global zone brand in the Oracle Solaris 11.1 release is the solariszone.

By default, all systems have a global zone. The global zone has a global view of the Oracle Solaris environment that is similar to the superuser (root) model. All other zones are referred to as non-global zones. A non-global zone is analogous to an unprivileged user in the superuser model. Processes in non-global zones can control only the processes and files within that zone. Typically, system administration work is mainly performed in the global zone. In rare cases where a system administrator needs to be isolated, privileged applications can be used in a non-global zone. In general, though, resource management activities take place in the global zone.

Note:

*A user can only assume roles that are assigned to the user's login account.

*After you have set up roles with default Solaris rights profiles, and assigned the roles to users, the roles can be used. A role can be assumed on the command line. In the Solaris Management Console, a role can also be used for administering the system locally and over the network.

*How to Assume a Role in a Terminal Window

The role must already be assigned to you. The name service must be updated with that information.

• In a terminal window, determine which roles you can assume.
• % roles

Comma-separated list of role names is displayed

• Use the su command to assume a role.
• % su -rolename
• Password:

$

The su - rolename command changes the shell to a profile shell for the role. A profile shell recognizes security attributes (authorizations, privileges, and set ID bits).

• Verify that you are now in a role.
• $ /usr/ucb/whoami

rolename

You can now perform role tasks in this terminal window.

TFTP Error or System Hangs After GATEWAY Message

The DHCP server provides an IP address and a location of the initial boot program as part of the DHCP response.

If the boot program does not exist, then the AI client boot cannot proceed. The following message is displayed:

Intel(R) Boot Agent PXE Base Code (PXE-2.1 build 0.86)

Copyright(C) 1997-2007, Intel Corporation

CLIENT MAC ADDR 00 14 4F 29 04 12 GUID FF2000008 FFFF FFFF FFFF 7BDA264F1400

CLIENT IP: 10.6.68.29 MASK: 255.255.255.0 DHCP IP: 10.6.68.49

GATEWAY: 10.6.68.1

TFTP.

PXE-T02: Access Violation

PXE-E3C: TFTP Error - Access violation

PXE-MOF: Exiting Intel Boot Agent

How to Enable the STMF Service

COMSTAR uses SMF to store its current, persistent configuration, such as logical unit mapping, host group definitions, and target group definitions. When the service is enabled during boot or when using the svcadm command, it clears any stale configuration data inside the kernel framework, and then reloads the configuration from the SMF repository into the driver.

The COMSTAR target mode framework runs as the stmf service. By default, the service is disabled. You must enable the service to use COMSTAR functionality. You can identify the service with the svcs command. If you have not rebooted the server since installing the group/feature/storage-server package, the service might not be enabled correctly.

Note:

*You can set up and configure a COMSTAR Internet SCSI (iSCSI) target and make it available over the network. The iSCSI features can work over a normal Internet connection (such as Ethernet) using the standard iSCSI protocol. The iSCSI protocol also provides naming and discovery services, authentication services using CHAP and RADIUS, and centralized management through iSNS.