Oracle 1z0-580 Oracle Solaris 11 Installation and Configuration Essentials Exam Practice Test

Note:

*The services started by svc.startd are referred to as milestones. The milestone concept replaces the traditional run levels that were used in previous versions of Solaris. A milestone is a special type of service that represents a group of services. A milestone is made up of several SMF services. For example, the services that instituted run levels S, 2, and 3 in previous version of Solaris are now represented by milestone services named:

milestone/single-user (equivalent to run level S)

milestone/multi-user (equivalent to run level 2)

milestone/multi-user-server (equivalent to run level 3)

*Shut down the system.

# shutdown -iinit-state -ggrace-period -y

-iinit-state

Brings the system to an init state that is different from the default of S. The choices are 0, 1, 2, 5, and 6.

Run levels 0 and 5 are states reserved for shutting the system down. Run level 6 reboots the system. Run level 2 is available as a multiuser operating state.

Use the zpool split command to split a mirrored storage pool, which detaches a disk or disks in the original mirrored pool to create another identical pool.

TheJumpStart Migration Utility (js2ai)is used to convert Oracle Solaris 10 JumpStart rules and profiles to a format that is compatible with AI manifest entries.

Note:

*There are no upgrade methods or tools available to transition from Oracle Solaris 10 to Oracle Solaris 11. You cannot use an installer to upgrade from Oracle Solaris 10 to Oracle Solaris 11. You must perform a fresh installation of Oracle Solaris 11.

A: project.cpu-shares

Number of CPU shares granted to this project for use with the fair share scheduler

B:project.cpu-cap

Absolute limit on the amount of CPU resources that can be consumed by a project. A value of 100 means 100% of one CPU as the project.cpu-cap setting. A value of 125 is 125%, because 100% corresponds to one full CPU on the system when using CPU caps.

Note:

*virtual local area networks (VLANs), link aggregations, and IP tunnels can be assigned administratively-chosen names and then configured by referring to those names.

*VNICs are pseudo interfaces that you create on top of datalinks. A VNIC has an automatically generated MAC address. Depending on the network interface in use, you can explicitly assign to a VNIC a MAC address other than the default address, as described in the dladm(1M) man page. You can create as many VNICs over a datalink as you require.

*Etherstubs are pseudo ethernet NICs which are managed by the system administrator. You can create VNICs over etherstubs instead of over physical links. VNICs over an etherstub becomeindependent of the physical NICs in the system. With etherstubs, you can construct a private virtual network that is isolated both from the other virtual networks in the system and from the external network. For example, you want to create a network environment whose access is limited only to your company developers than to the network at large. Etherstubs can be used to create such an environment.

*The basic link aggregation topology involves a single aggregation that contains a set of physical interfaces. You might use the basic link aggregation in the following situations:

For systems that run an application with distributed heavy traffic, you can dedicate an aggregation to that application's traffic.

For sites with limited IP address space that nevertheless require large amounts of bandwidth, you need only one IP address for a large aggregation of interfaces.

For sites that need to hide the existence of internal interfaces, the IP address of the aggregation hides its interfaces from external applications.

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

Example:

# beadm activate solaris

# init 6

To display information about software packages, refer to the following examples. No special privileges are required to display information about packages.

List the packages that are currently installed on your system:

$ pkg list -H entire

Determine whether a specific package is installed in the current image and whether an update is available.

$ pkg list amp

pkg list: no packages matching 'amp' installed

Creating a ZFS Storage Pool with Cache Devices

You can create a storage pool with cache devices to cache storage pool data. For example:

# zpool create tank mirror c2t0d0 c2t1d0 c2t3d0 cache c2t5d0 c2t8d0

Note:

*Creating a Basic Storage Pool

The following command creates a new pool named tank that consists of the disks c1t0d0 and c1t1d0:

#zpool status tank

pool: tank

state: ONLINE

scrub: none requested

config:

NAME STATE READ WRITE CKSUM

tank ONLINE 0 0 0

mirror-0 ONLINE 0 0 0

c2t0d0 ONLINE 0 0 0

c2t1d0 ONLINE 0 0 0

c2t3d0 ONLINE 0 0 0

cache

c2t5d0 ONLINE 0 0 0

c2t8d0 ONLINE 0 0 0

errors: No known data errors

# zpool create tank c1t0d0 c1t1d0

These whole disks are found in the /dev/dsk directory and are labelled appropriately by ZFS to contain a single, large slice. Data is dynamically striped across both disks.

*Creating a Mirrored Storage Pool

To create a mirrored pool, use the mirror keyword, followed by any number of storage devices that will comprise the mirror. Multiple mirrors can be specified by repeating the mirror keyword on the command line. The following command creates a pool with two, two-way mirrors:

# zpool create tank mirror c1d0 c2d0 mirror c3d0 c4d0

There are no upgrade methods or tools available to transition from Oracle Solaris 10 to Oracle Solaris 11. You cannot use an installer to upgrade from Oracle Solaris 10 to Oracle Solaris 11.

Oracle Solaris 11 Transition Tools and Features

/JumpStart Migration Utility (js2ai)

Used to convert Oracle Solaris 10 JumpStart rules and profiles to a format that is compatible with AI manifest entries.

/ZFS shadow migration feature

Used to migrate data from an existing file system to a new file system.

/Oracle Solaris 11 support for Oracle Solaris 10 zones

Used to migrate your Oracle Solaris 10 application environments to an Oracle Solaris 11 system.

/NFS file sharing and pool migration

Used to access shared files from an Oracle Solaris 10 system on an Oracle Solaris 11 system.

Used to import a ZFS storage pool from an Oracle Solaris 10 system into an Oracle Solaris 11 system.

*Booting a system using the none milestone can be very useful for debugging startup problems. There is no equivalent run level to the none milestone.

*If problems with starting services occur, sometimes a system will hang during the boot. This procedure shows how to troubleshoot this problem.

2.Boot without starting any services.

This command instructs the svc.startd daemon to temporarily disable all services and start sulogin on the console.

ok boot -m milestone=none

2.Log in to the system as root.

3.Enable all services.

# svcadm milestone all

4.Determine where the boot process is hanging.

When the boot process hangs, determine which services are not running by running svcs -a. Look for error messages in the log files in /var/svc/log.

• After fixing the problems, verify that all services have started.

Verify that all needed services are online.

# svcs -x

Verify that the console-login service dependencies are satisfied.

This command verifies that the login process on the console will run.

# svcs -l system/console-login:default

6.Continue the normal booting process.

A:dedicated-cpu Resource

The dedicated-cpu resource specifies that a subset of the system's processors should be dedicated to a non-global zone while it is running. When the zone boots, the system will dynamically create a temporary pool for use while the zone is running.

C:s the global administrator in the global zone, you can import raw and block devices into a non-global zone. After the devices are imported, the zone administrator has access to the disk. The zone administrator can then create a new file system on the disk and perform one of the following actions:

Mount the file system manually

Place the file system in /etc/vfstab so that it will be mounted on zone boot

D, E:Booting a zone places the zone in the running state. A zone can be booted from the ready state or from the installed state. A zone in the installed state that is booted transparently transitions through the ready state to the running state. Zone login is allowed for zones in the running state.

Incorrect:

Not F: Sys_time not related to booting a zone.