1z0-580 Exam Dumps - Oracle Solaris Questions and Answers

E:

* Many configuration tasks around name services have moved into the SMF in Solaris 11.

*The Service Management Facility (SMF), first introduced in Oracle Solaris 10, is a feature of the operating system for managing system and application services, and it replaces the legacy init scripting start-up mechanism common to prior releases of Oracle Solaris and other UNIX operating systems. SMF improves the availability of a system by ensuring that essential system and application services run continuously even in the event of any hardware or software failures. SMF is one of the components of the wider Oracle Solaris Predictive Self Healing capability.

Note:

*In Oracle Solaris 11, certain aspects of system configuration have changed, including the migration of several system, network, and naming services configuration to SMF.

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

Note:

Not A:

* Jumpstart Profiles and Rules would have to be converted to be used in Automated Installer.

Use the js2ai utility with the -r option to convert both JumpStart rules and their associated profiles to AI criteria and manifests.

*Both Solaris Custom JumpStart and Oracle Solaris Automated Installer (AI) provide hands-free installation of multiple systems on a network. Clients are booted over the network, and once the client is booted, the installer takes over.

pkgrecv

- Image Packaging System content retrieval utility

Options include:

-c cache_dir

The path to a directory that will be used to cache downloaded content. If this directory is not supplied, the client automatically selects a cache directory. In the case where a download is interrupted, and a cache directory was automatically chosen, use this option to resume the download. See the “Environment Variables” section below for details about how to set the location used for temporary data storage.

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.

*vnic-link

A virtual network interface created on a link or an etherstub. It is a pseudo device that can be treated as if it were an network interface card on a machine.

*vlan-link

A VLAN datalink.

*bridge

A bridge instance, identified by an administratively-chosen name. The name may use any alphanumeric characters or the underscore, _, but must start and end with an alphabetic character. A bridge name can be at most 31 characters. The name default is reserved, as are all names starting with SUNW.

Note:

*dladm– administer data links

*The dladm command is used to administer data-links. A data-link is represented in the system as a STREAMS DLPI (v2) interface which can be plumbed under protocol stacks such as TCP/IP. Each data-link relies on either a single network device or an aggregation of devices to send packets to or receive packets from a network.

Each dladm subcommand operates on one of the following objects:

link

A datalink, identified by a name. In general, the name can use any alphanumeric characters (or the underscore, _), but must start with an alphabetic character and end with a number. A datalink name can be at most 31 characters, and the ending number must be between 0 and 4294967294 (inclusive). The ending number must not begin with a zero. Datalink names between 3 and 8 characters are recommended.

Some subcommands operate only on certain types or classes of datalinks. For those cases, the following object names are used:

phys-link

A physical datalink.

vlan-link

A VLAN datalink.

aggr-link

An aggregation datalink (or a key; see NOTES).

ether-link

A physical Ethernet datalink.

wifi-link

A WiFi datalink.

vnic-link

A virtual network interface created on a link or an etherstub. It is a pseudo device that can be treated as if it were an network interface card on a machine.

iptun-link

An IP tunnel link.

dev

A network device, identified by concatenation of a driver name and an instance number.

etherstub

An Ethernet stub can be used instead of a physical NIC to create VNICs. VNICs created on an etherstub will appear to be connected through a virtual switch, allowing complete virtual networks to be built without physical hardware.

bridge

A bridge instance, identified by an administratively-chosen name. The name may use any alphanumeric characters or the underscore, _, but must start and end with an alphabetic character. A bridge name can be at most 31 characters. The name default is reserved, as are all names starting with SUNW.

Note that appending a zero (0) to a bridge name produces a valid link name, used for observability.

secobj

A secure object, identified by an administratively-chosen name. The name can use any alphanumeric characters, as well as underscore (_), period (.), and hyphen (-). A secure object name can be at most 32 characters.

auto_reboot – Optional. Omitting the auto_reboot attribute is equivalent to setting the value of the attribute to false. By default, AI does not automatically reboot the client after installation. To request automatic reboot of the client after successful installation, specify auto_reboot="true".

Note:

*Example 1 Set the auto_reboot Attribute

$ aimanifest set /auto_install/ai_instance@auto_reboot false

A:

*Oracle Solaris 11 adds transparent data encryption functionality to ZFS. All data and file system metadata (such as ownership, access control lists, quota information, and so on) are encrypted when stored persistently in the ZFS pool.

*A very simple example of using ZFS encryption is as follows:

#zfs create -o encryption=on rpool/export/project

Enter passphrase for 'rpool/export/project':

Enter again:

#zfs create rpool/export/project/A

#zfs create rpool/export/project/A/design

#zfs create rpool/export/project/B

D:compression=onreduces storate footprint

E:If you want to allow the filesystem to be managed inside the zone, use the zfs zoned=on option when creating or modifying the filesystem.

As per exhibit these are the two files in the netboot directory.

Note:

*Missing argument is:

file=wanbootCGI-URL

Specifies the URL of the wanboot-cgi program on the web server

*During the installation, WAN boot refers to the contents of the /etc/netboot hierarchy on the web server for instructions about how to perform the installation. This directory contains the configuration information, private key, digital certificate, and certificate authority required for a WAN boot installation. During the installation, the wanboot-cgi program converts this information into the WAN boot file system. The wanboot-cgi program then transmits the WAN boot file system to the client.