1z0-820 Exam Dumps - Upgrade to Oracle Solaris 11 System Administrator

While creating the non-global zone, make the following entry:

add device

set match=/dev/rdsk/c4t0d0

end

Boot the zone and log in the zone as root. Create the zpool:

zpool create pool2 c4t0d0

In the non-global zone, root can now create ZFS file system in the pool2 zpool

In the global zone, create the zpool:

global# zpool create pool2 c4t1d0

While creating the no-global zone, make the following entry:

add dataset

set name=pool2

end

add fs

set dir=pool1

set special=pool1

set type=zfspool1

end

Boot the zone, log in the zone as root, and create the zfs file system in the pool2 zpool.

In the global zone, create the zpool:

global#zpool create pool2 c4t1d0

While creating the global zone, make the following entry:

add dataset

set name=pool2

end

Boot the zone, log in to the zone as root and create the zfs file systems in the pool2 zpool.

In the global zone, create the zpool and the ZFS file systems that you want to use in the non-global zone:

global#zpool create pool2 c4t1d0

global#zfs create pool2/data

While creating the non-global zone, make the following entry for each ZFS file system that you want to make available in the zone:

add fs

set dir=/data

set special=pool2/data

set type=zfs

end

Create the zpool in the global zone:

global#zpool create pool2 c4t1d0

Boot the non-global zone, log in to the zone as root, and issue this command to delegate ZFS permissions to root:

non-global zone# zfs allow root create , destroy, mount pool2

Log in to the non-global zone create ZFS file systems in the pool2 zpool.

AJ: manifest files

JumpStart: begin script

Al:installadmcreate-client

JumpStart: setup_install_sen/er

Al SMF system configuration profile files JumpStart: profile files

Al: SMF system configuration profile files JumpStart: finish scripts and sysidcfg files

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

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

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

zone cfg - a s10-zone create - t SUNWsolaris10\

zonecfg -z s10-zone install -f /net/backup/backup_server/s10-system.flar

terminal=xterms

name_service=NIS+

timezone=US/Pacific

system_locale=en_US

network_interface=PRIMARY

root_password=rJmv5LUXM10cU

it associates an install image with a named install service.

Client systems use the service name to find the correct install image.

Every Oracle Solaris 11 system uses this service to find its IPS publisher and to locate its IPS repository.

A server can have multiple instances of the install/server service, each associated with one boot image.

This service is not present on a server by default.

This service is present on every Oracle Solaris 11 system, but it is not enabled.

A new install/server service cannot be created without DHCP.

ISO images for use with the Automated Installer (AI) can be created.

Bootable USB images can be created for SPARC and x86 architectures.

A single installation server can be used to create ISO images for SPARC and x86 architectures.

Checkpoints can be used to pause the build, allowing scripts to run that modify the resulting ISO Image.

A single Installation server can be used to create ISO images for Solaris 10 and Solaris11 operating systems.

in the global zone, run this command to change the process scheduler for the global zone dispadmin -d FSS

in the non-global zone, run this command to change the process scheduler for this specific zone: dispadmin -d FSS

Change the zone resource control to:

value: (priv=privileged,limit=20,action=none,default)

Use svccfg to modify the general/scheduler property in the svc:/system/zones:default service:

svccfg -s system/zones:default editprop general/scheduler=FSS

By default, in.mpathd selects the default router as the only test partner.

The default failure detection time is 60 seconds (12 consecutive probes).

Without test partners, in.mpathd cannot detect the failure of a subinterface.

Arbitrary hosts on the subnet are detected by sending an "all hosts" (224.0.0.1) multicast packet

Arbitrary hosts on the subnet are detected by sending an "all routers" (224.0.0.2) multicast packet.

Arbitrary hosts on the subnet are detected by examining the ARP cache (Internet-to-MAC address translation table).