Free Oracle Solaris 11 Installation and Configuration Essentials 1Z0-580 Exam Questions

The JumpStart 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.

How to Loopback Mount a File That Is Usually Not Visible in a Labeled Zone

This procedure enables a user in a specified labeled zone to view files that are not exported from the global zone by default.

1. Halt the zone whose configuration you want to change.

# zoneadm -z zone-name halt

2. Loopback mount a file or directory.

For example, enable ordinary users to view a file in the /etc directory.

# zonecfg -z zone-name

add filesystem

set special=/etc/filename

set directory=/etc/filename

set type=lofs

add options [ro,nodevices,nosetuid]

end

exit

Note - Certain files are not used by the system, so that loopback mounting them has no effect. For example, the /etc/dfs/dfstab file in a labeled zone is not checked by Trusted Extensions software. For more information, see Sharing Files From a Labeled Zone.

3. Start the zone.

# zoneadm -z zone-name boot

Note:

* In this Solaris release, you create a ZFS file system share and publish the share as follows:

Create the file system share and define the NFS or SMB share properties by using the zfs share command.

* ZFS File Sharing Within a Non-Global Zone

In previous Solaris releases, you could not create and publish NFS or SMB shares in a Oracle Solaris non-global zone. In this Solaris release, you can create and publish NFS shares by using the zfs set share command and the legacy share command with a non-global zone.

* If a ZFS file system is mounted and available in a non-global zone, it can be shared in that zone.

* A file system can be shared in the global zone if it is not mounted in a non-global zone or is not shared to a non-global zone.

* If a ZFS file system's mountpoint property set to legacy, the file system can be shared by using the legacy share command.

A:

* If your system has more than one OS installed on the system or more than one root boot environment in a ZFS root pool, you can boot from these boot environments for both SPARC and x86 platforms.

* GRUB, the open source boot loader, is the default boot loader in the Solaris OS.

C: With GRUB based booting, the kernel is loaded by specifying its file name, and the drive, and the partition where the kernel resides. GRUB based booting replaces the Solaris Device Configuration Assistant and simplifies the booting process with a GRUB menu.

Incorrect:

Not E:

* In this implementation of GRUB, the multiboot module is no longer used.

* 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.

1. 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.

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.

Updating all of the packages on your installed system -- To update all of the packages on your system that have available updates, use the pkg update command, as follows:

# pkg update

Running this command updates packages that you might not otherwise consider updating, for example, kernel components and other low-level system packages.

B: This example shows how to create a DLMP aggregation. The aggregation has three underlying datalinks.

# dladm create-aggr -m haonly -l net0 -l net1 -l net2 aggr0

# dladm show-link

LINK CLASS MTU STATE BRIDGE OVER

net0 phys 1500 up -- ----

net1 phys 1500 up -- ----

net2 phys 1500 up -- ----

aggr0 aggr 1500 up -- net0, net1, net2

# dladm show-aggr

LINK MODE POLICY ADDRPOLICY LACPACTIVITY LACPTIMER

aggr0 haonly --

E: Check the status of the aggregation you just created.

# dladm show-aggr

The aggregation's state should be UP.

Storage

ZFS is the root file system on Oracle Solaris 11 offering a superior experience in terms of manageability, scalability and data integrity. ZFS presents a pooled storage model that completely eliminates the concept of volumes and the associated problems of partitions, provisioning, wasted bandwidth and stranded storage. Thousands of file systems can draw from a common storage pool, each one consuming only as much space as it actually needs. All operations are copy-on-write transactions ensuring that the on-disk state is always valid.

Incorrect:

Not A: Network Auto-Magic (NWAM) is a project to simplify and automate network configuration on Solaris. Network Auto-Magic generally refers to Network Profiles, which allow users to specify various network configurations to be created depending on the current network conditions. The Service Discovery project, which incorporates Multicast DNS into Solaris, also fell under the Network Auto-Magic umbrella.

Not B: Pre-Flight Checker tool which can be used to check whether apps will work without modification on Solaris 11

Not C: Network Auto-Magic is a project to simplify and automate network configuration on Solaris. Network Auto-Magic generally refers to Network Profiles, which allow users to specify various network configurations to be created depending on the current network conditions. The Service Discovery project, which incorporates Multicast DNS into Solaris, also fell under the Network Auto-Magic umbrella.

B:

* With Oracle Solaris 11, the configuration of the system is specified as a set of configuration parameters provided in a file called the System Configuration Profile, which is in the form of an SMF profile.

* Oracle Solaris 11 uses SMF for configuration. SMF uses a database to centralize the configuration information, it uses the SMF framework to carry out configuration tasks, and it uses SMF properties as an API. SMF is also well integrated with Oracle Solaris Zones technology.

* Oracle Solaris 11 uses the Service Management Facility (SMF) to centralize configuration information. The new sysconfig command replaces the older sys-unconfig command and provides a method based upon SMF for unconfiguring an Oracle Solaris 11 instance and reconfiguring it.

D: To use AI to install client systems over the network, you must set up DHCP and set up an AI service on an AI server.

An AI service is associated with a SPARC or x86 AI install image and one or more sets of installation instructions.

Note:

Using the Oracle Solaris Automated Installer (AI) you can create and manage services to install the Oracle Solaris 11 operating system over the network in a hands-off manner.

Three significant steps are performed by various services during the installation process:

Assigning a network identity for the system being installed

Contacting the automated installation service to download over the network a small boot image and a description of how to provision a system

Provisioning the system over the network, including software and system configuration

Each of the steps can be performed by various services residing on the same physical or virtual system, or the services can be on separate systems. In this article, the following services reside on the same system:

DHCP service

Automated Installer service

Image Packaging System (IPS) repository service

* Use the configuration element in the AI manifest for the client system to specify non-global zones.

Use the name attribute of the configuration element to specify the name of the zone.

Use the source attribute to specify the location of the config file for the zone.

The source location can be any http:// or file:// location that the client can access during installation.

* The following sample AI manifest specifies two Non-Global Zones: zone1 and zone2

You should replace the server_ip with the ip address of the NFS server.

<!DOCTYPE auto_install SYSTEM 'file:///usr/share/install/ai.dtd.1'>

<target>

<logical>

<zpool name='rpool' is_root='true'>

<filesystem name='export' mountpoint='/export'/>

<filesystem name='export/home'/>

<be name='solaris'/>

</zpool>

</logical>

</target>

<software type='IPS'>

<source>

<origin name='http://pkg.oracle.com/solaris/release'/>

</source>

<software_data action='install'>

<name>pkg:/entire@latest</name>

<name>pkg:/group/system/solaris-large-server</name>

</software_data>

</software>

<configuration type='zone' name='zone1' source='file:///net/server_ip/export/zone_config/zone1'/>

<configuration type='zone' name='zone2' source='file:///net/server_ip/export/zone_config/zone2'/>