1z0-820 Upgrade to Oracle Solaris 11 System Administrator Questions and Answers

Create a ZFS file system named iscsi/target.

Create a zpool named iscsi with disk device c3t4d0

Create zfs volume named iscsi/target.

Use the stmfadm command to create a LUN using /dev/zvol/rdsk/iscsi/target.

Use the stmfadm command to create a LUN using iscsi/target.

Use the stmfadm command to make the LUN viewable.

Use the stmfadm command to make the volume viewable.

issue the pkgrepo refresh -s command to refresh the repository.

Restart the svc:/application/pkg/server:default service.

issue the pkg set-publisher command to set the new repository location.

issue the pkgrepo rebuild command to rebuild the repository.

issue the pkgrepo set command to set the new repository location-

You can perform a text or LiveCD installation locally or over the network.

The text Installer does not install the GNOME desktop. The GNOME desktop package must he added after you have installed the operating system.

The LiveCD Installation cannot be used to install multiple instances of Oracle Solaris.

The LiveCD installer cannot be used if you need to preserve a specific Solaris Volume Table of Contents (VTOC) slice in your current operating system.

The LiveCD Installer is for x86 platforms only.

The GUI installer cannot be used to upgrade your operating system from Solaris 10.

If you are installing Oracle Solaris 11 on an x86-based system that will have more than one operating system installed in it, you cannot partition your disk during the installation process.

Perform an rsync on the ISO image to copy the files from the ISO image to the /export/IPS file system.

chmod 700 on/export/IPS

Use the svccfg command to set the pkg/inst_root property to export/IPS.

Use the svccfg command to set the pkg.inst_root property to /export/IPS.

Use the svccfg command to set the pkg/readonly property to the application/pkg/server service to true.

Use the svccfg command to set the pkg/readonly property for the application/pkg/server service false.

Refresh the application/pkg/server service with the svcadm refresh command.

The solans-1 boot environment is not bootable.

The solaris-1 boot environment is incomplete.

The solaris-1 boot environment was created automatically when the non-global zone was created.

The solaris-1 boot environment was created in the non-global zone using the beadm create command

The solans-1 boot environment is associated with a non-active global zone boot environment.

You must set up DHCP. The DHCP server and Al install server can be the same machine or two different machines.

You can create only one manifest per install service. If you need more than one manifest, create multiple install services.

The minimum requirement to operate as an Al install server is 1 GB of memory.

If two client machines have different architectures and need to be installed with the same version of the Oracle Solaris 11 OS( then create two Al manifests and a single install service.

Load the install/installadm package on the Al server.

zoneadm -z slO-zone install -a /net/backup_server/slO-system.flar -u

zonecfg -z slO-zone install -a /net/backup_server/s10-system.flar -u

zoneadm -z s10-zone clone -s /net/backup_server/slO-system flar

zonecfg -a s10-zone create -t SUNWsolanslO \

< /net/backup_server/s10-system.flar

zonecfg-zs10-zoneinstall-f/net/backup_server/slO-system.flar

The zone.cfg file is a text file in a zonecfg export format.

The zone.cfg file is an Al manifest that specifies how the zone is to be installed.

The zone.cfg file is an XML file in a form suitable for use as a command file for the zonecfg command.

The zone.cfg file is an SC profile with keywords that are specific for configuring a zone as part of the installation process.

ft is an XML configuration file from the /etc/zone directory. It will be used as a profile for the zone. It specifies the zonename. zonepath, and other zonecfg parameters

if the Al client does not match any cnteria to use a custom manifest or script, the default manifest is used.

if the A! client does not match any criteria to use a custom manifest or script, the automated installation aborts.

Any manifest or script in a service can be designated to be the default for that service.

Only the default.xml file is used as the default Al client manifest.

if a client system does not use any SC profile, then an interactive tool opens on that client at first boot after that client installation to complete the

configuration of that client.

If a client system does not use any SC profile, then the install server will use the default SC profile.

pkg info|grep gzip

pkg list SUNWgzip

pkg contents gzip

pkg search gzip

Create a local IPS repository on the AI Install server and start the repository server service, the publisher origin to the repository file.

Set up a IP address on the AI install server.

The DHCP server must be enabled on the install server and must provide the DHCP service for the clients.

DHCP must be available on the network for the Install server and the clients, but the install server does not need to be the DHCP server.

Download the AI boot image. The image must be the same version as the Oracle Solaris OS that you plan to install on the client.

Download the text install image into the IPS repository.

Install the AI installation tools.

On the server:

set the pkg/inst_root and pkg/readonly properties for the svc:/application/pkg/server:default service and enabled the service

On the server:

set the sharefs property on the ZFS file system containing the IPS repository.

On the client:

reset the origin for the solaris publisher.

On the client:

set the pkg/inst_root and pkg/readonly properties for the svc:/application/server:default service enable the service.

On the client:

start the pkg.depotd process.

pktool genkey keystone=file outkey=/mykey keytype=aes keylen=256

genkey pktool keystore=file outkey=/mykey keytype=aes keylen=256

zfs create -o encryption=aes-256-ccm -o keysource=raw,file://mykey pooll/encrypt

zfs create -o encryption=aes-256-ccm -o keysource=raw,file:///mykey pooM/encrypt

zfs create -o encryption=aes-256-ccm -o keysource=raw,file:///mykey source=local pooll/encrypt

If a location is explicitly enabled, it remains active until explicitly changed.

Wireless security keys can be configured by using the nwammgr command.

NWAM stores profile information in /etc/ipadm/ipadm.conf and /etc/dladm/datalink.conf.

Multiple locations may be automatically activated in systems with multiple network interface cards.

Interface NCU Properties "float" and are automatically attached to the highest priority Link NCU Property.

If the DefaultFixed NCP is enabled, persistent configuration, stored in /etc/ipadm.conf and /etc/dladm/datalink.conf is used.

zfs destroy pooh /prod_data

zfs create pool1/prod_data c4t1d0 zfs create pool1/dev_data c4t1d0

zfssplitpool1/prod_data

zfs mount -F zfs pool1/dev_data c4t1d0

zpool split pooll pool2 zpool import pool2 zfs set mountpoint=/dev_data pool2/prod_data

zpool split pool1/prod_data -n pool2/dev_data

zpool import -o mountpoint=/dev_data pool2/dev_data

3 e zfs split pool1/prod_data -n pool2/dev_data zfs set mountpoint=/dev_data pool2/dev_data

IP address of the Al server

passwords for user accounts

target disk slice for installation

NWAM active network configuration profile (NCP)

IP address of the IPS (Image Packaging System) repository

SI_MANIFEST_SCRIPT, which defines the URL of the manifest script