1z0-822 Sample Questions Answers

* /etc/default/mpathd

Contains default values used by the in.mpathd daemon.

* By default, in.mpathd limits failure and repair detection to IP interfaces that are configured as

part of a named IPMP group. Setting TRACK_INTERFACES_ONLY_WITH_GROUPS to no enables failure and repair detection on all IP interfaces, even if they are not part of a named IPMP group. IP interfaces that are tracked but not part of a named IPMP group are considered to be part of the “anonymous” IPMP group. In addition to having no name, this IPMP group is

special in that its IP interfaces are not equivalent and thus cannot take over for one another in

the event of an IP interface failure. That is, the anonymous IPMP group can only be used for

failure and repair detection, and provides no high-availability or load-spreading

From the poolcfg –c info command output we see that FSS (Fair Share Scheduler) is used.

From the prctl command output we see that zone z1 has been configured with a zone.cpu-shares value of 40.

* The pool_default has a value of 100 CPU shares.

* prstat

- report active process statistics

Option –Z

-Z

Report information about processes and zones. In this mode, prstat displays separate reports about processes and zones at the same time.

An interface that has been created cannot become a member of an aggregation.

AD: Manifests from the standard directory trees /lib/svc/manifest and /var/svc/manifest are processed during system boot and anytime an administrator or program runs:

$ svcadm restart manifest-import

C: svccfg

apply subcommand

If the argument is a service profile or manifest, apply the configuration to the admin layer of the SMF repository. Services, instances, property groups, and properties will be created as necessary.

E: import [-V] [file | directory]

svccfg import on a file in a system-managed filesystem location (subdirectories of /lib/svc/manifest and /var/svc/manifest) invokes: svcadm restart manifest-import.

Placing your manifests in a system-managed location and invoking svcadm restart manifest-import to import them is the recommended practice.

svccfg import on files in other locations imports their properties as administrative customization into the admin layer. It is equivalent to:

svccfg apply [file | directory]

Incorrect:

not B: Manifests are processed in two different phases during boot.

The service svc:/system/early-manifest-import:default, a pseudo service, is responsible for the first manifest processing. This service processes only manifests from the /lib/svc/manifest directory tree before svc.startd(1M) initializes any services thus enabling services delivered in /lib/svc/manifest to always start with their most updated definition. Since this is a pseudo service, svcadm(1M) commands are ignored though svcs(1) can be used to observe status and get log file information.

The svc:/system/manifest-import:default service handles the second manifest processing and imports manifest files from both /lib/svc/manifest and /var/svc/manifest directory trees, in that respective order.

Example 1: Creating a New Shell

The following example creates a new shell in the canada pro-

ject, displaying the task id:

example$ id -p

uid=565(gh) gid=10(staff) projid=10(default)

example$ newtask -v -p canada

38

To c reate a file system with deduplication:

root@solaris:~# zfs create -o dedup=on

Note: If you have a storage pool named 'tank' and you want to use dedup, just type this:

zfs set dedup=on tank

A:

Note:

Use dladm show-phys to obtain information about the system's datalinks in relation to the physical NICs with which they are associated. Used without any options, the command displays information similar to the following:

# dladm show-phys

LINK MEDIA STATE SPEED DUPLEX DEVICE

net0 Ethernet up 100Mb full e1000g0

net1 Ethernet down 0Mb -- nge0

net2 Ethernet up 100Mb full bge0

net3 Infiniband -- 0Mb -- ibd0

* Your link aggregation configuration is bound by the following requirements:

/You must use the dladm command to configure aggregations.

/ (not B) An interface that has been created cannot become a member of an aggregation.

/All interfaces in the aggregation must run at the same speed and in full-duplex mode.

/ (not E) You must set the value for MAC addresses to “true” in the EEPROM parameter local-mac-address? For instructions, refer to How to Ensure That the MAC Address of an Interface Is Unique.

C: a user must be assigned to a default project, the processes that the user launches can be associated with any of the projects of which that user is a member.

D: How to Create a New Task

1.Log in as a member of the destination project, booksite in this example.

2.Create a new task in the booksite project by using the newtask command with the -v (verbose) option to obtain the system task ID.

machine% newtask -v -p booksite

16

The execution of newtask creates a new task in the specified project, and places the user's default shell in this task.

3.View the current project membership of the invoking process.

machine% id -p

uid=100(mark) gid=1(other) projid=4113(booksite)

The process is now a member of the new project.

Note:

* Projects are collections of tasks, which are collections of processes.

* Projects and tasks are used to label workloads and separate them from one another.

Incorrect:

Not A: The task collects a group of processes into a manageable entity that represents a workload component.

Not E: If no default project is found, the user's login, or request to start a process, is denied.

DE: Link aggregations provide high availability and higher throughput by aggregating multiple interfaces at the MAC layer. IP Multipathing (IPMP) provides features such as higher availability at the IP layer. Both IPMP and Link Aggregation are based on the grouping of network interfaces, and some of their features overlap, such as higher availability. These technologies are however implemented at different layers of the stack, and have different strengths and weaknesses.

E: The IP network multipathing or IPMP is a facility provided by Solaris to provide fault-tolerance and load spreading for network interface cards (NICs). With IPMP, two or more NICs are dedicated for each network to which the host connects.

The IPMP load spreading feature increases the machine's bandwidth by spreading the outbound load between all the cards in the same IPMP group.

Service Dependency. This element identifies a group of FMRIs upon which the service is in some sense dependent.

ATTRIBUTE: Grouping:

Possible values:

'require_all',

'require_any',

'exclude_all',

‘optional_all'

Note:

* Example 1:

name='network'

grouping='require_all'

restart_on='none'

type='service'>

* In this example, let's choose the svc:/system/zones:default service instance. We can use the -l option and the service name to get more information, as shown in Listing 3.

# svcs -l svc:/system/zones:default

fmri svc:/system/zones:default

name Zones autoboot and graceful shutdown

enabled true

state online

next_state none

state_time June 14, 2012 08:30:31 PM NZST

logfile /var/svc/log/system-zones:default.log

restarter svc:/system/svc/restarter:default

manifest /etc/svc/profile/generic.xml

manifest /lib/svc/manifest/system/zones.xml

manifest /lib/svc/manifest/system/zonestat.xml

dependency require_all/none svc:/milestone/multi-user-server (online)

dependency optional_all/none svc:/system/pools:default (disabled)

dependency optional_all/none svc:/system/pools/dynamic:default (disabled)

dependency optional_all/none svc:/system/zones-monitoring (online)

* How to Reconfigure a Zone to Use a VNIC

1. Become an administrator.

2. Create the VNIC.

(C) 3. Change the zone's IP type from shared to exclusive.

4.Change the zone's interface to use a VNIC.

5. Verify and commit the changes you have implemented and then exit the zone.

(D) 6. Reboot the zone.

7. Log in to the zone.

8. Configure the VNIC with a valid IP address.

* Example. Reconfiguring a Zone Configuration to Use a VNIC

In this example, zone2 already exists as a shared zone. The zone also uses the primary interface of the system rather than a virtual link. You need to modify zone2 to use vnic2. To use vnic2, zone2's IP type must first be changed to exclusive. Note that some of the output is truncated to focus on the relevant information that relates to virtual networks.

global# dladm create-vnic -l net0 vnic2

global# zonecfg -z zone2

(C) zonecfg:zone1> set ip-type=exclusive

zonecfg:zone1> remove net physical=net0

zonecfg:zone1> add net

zonecfg:zone1:net> set physical=vnic2

zonecfg:zone1:net> end

zonecfg:zone1> verify

zonecfg:zone1> commit

zonecfg:zone1> exit

(D) global# zoneadm -z zone2 reboot

global# zlogin zone2

zone2# ipadm create-ip vnic2

zone2# ipadm create-addr -a 192.168.3.85/24 vnic2

ipadm: vnic2/v4

zone2# exit

global# vi /etc/hosts

#

1 localhost

127.0.0.1 localhost

192.168.3.70 loghost #For net0

192.168.3.80 zone1 #using vnic1

192.168.3.85 zone2 #using vnic2

A:

* nscfg

- import, export name service configurations

* subcommand import

import [-fvq] FMRI

If none of the SMF repository properties for the specified FMRI are currently populated, import the legacy configuration files associated with the specified FMRI into the SMF repository.

* Example: Importing DNS Client Configuration

The following command imports the DNS client configuration, stored in resolv.conf, into the SMF repository.

# nscfg import svc:/network/dns/client:default

* svcadm– manipulate service instances

D: netcfg

- create and modify network configuration profiles

The netcfg utility manipulates system network configuration profiles. netcfg can be invoked interactively, with an individual subcommand, or by specifying a command file that contains a series of subcommands.

/ netcfg location properties include:

/ nameservices: enum value list: files | dns | nis | ldap

Specifies the name services that should be configured, such as DNS, NIS, and LDAP.

Incorrect:

Not B: netcfg has no subcommand import.

Note:

* Each workstation has a nsswitch.conf file in its /etc directory. Each line of that file identifies a particular type of network information, such as host, password, and group, followed by one or more sources, such as NIS+ tables, NIS maps, the DNS hosts table, or local /etc, where the client is to look for that information.

* The Solaris platform provides the following naming services.

/ DNS, the Domain Name System

/ /etc files, the original UNIX naming system

/ NIS, the Network Information Service

/ NIS+, the Network Information Service Plus

/ LDAP, the Lightweight Directory Access Protocol

A: Oracle Solaris Image Types include:

x86 or SPARC ISO Image for Automated Installations – The Oracle Solaris release includes the automated installer tool. The automated installer (AI) is used to automate the installation of the Oracle Solaris OS on one or more SPARC and x86 systems over a network.

D:

* You can also create custom scripts to modify your installation image. Then, you can add checkpoints to the manifest file to run these custom scripts.

* You can use the options provided in the distro_const command to stop and restart the build process at various stages in the image-generation process, in order to check and debug the image that is being built. This process of stopping and restarting during the build process is called checkpointing. Checkpointing is optional. Default checkpoints are specified in each manifest file.

Incorrect:

Not B: Only for x86, not for SPARC-

Oracle Solaris x86 LiveCD – You can create an x86 ISO image that is comparable to the LiveCD image that's distributed as an Oracle Solaris release. You can also modify the content of this ISO image by adding or removing packages. You can revise the default settings for the resulting booted environment to create a custom ISO image or USB image.

Note: The distribution constructor creates images based on settings specified in XML files, called manifest files. The manifest files contain specifications for the contents and parameters for the ISO images that you create using the distribution constructor. The distribution-constructor package provides sample manifests that can be used to create a custom x86 Live Media ISO, an x86 or SPARC Automated Install ISO image, or an x86 or SPARC text installation ISO image.

The elements in each manifest file provide preset, default values that will create the type of ISO image you need. You can manually edit these preset elements in a manifest file to customize the resulting image. In addition, you can create custom scripts to further modify your image. Then, reference the new scripts in the manifest file.

The audit service makes the following possible:

Monitoring security-relevant events that take place on the host

Recording the events in a network-wide audit trail

Detecting misuse or unauthorized activity

Reviewing patterns of access and the access histories of individuals and objects

Discovering attempts to bypass the protection mechanisms

Discovering extended use of privilege that occurs when a user changes identity

Incorrect:

Not A: auditing does not prevent attempts to bypass the protection mechanisms, it just discovers them.

Not on compression setting:

compression=on | off | lzjb | gzip | gzip-N

Controls the compression algorithm used for this dataset. The

"lzjb" compression algorithm is optimized for performance while

providing decent data compression. Setting compression to "on" uses

the "lzjb" compression algorithm.

Incorrect:

Not A, Not E: Should not use commas like this.

Not B, Not D: There is no property algorithm named to this command. To specify the use of the lzjb compression command we must use compression=lzjb.

The zfs get command supports the -H and -o options, which are designed for scripting. You can use the -H option to omit header information and to replace white space with the Tab character. Uniform white space allows for easily parseable data. You can use the -o option to customize the output in the following ways:

* The literal name can be used with a comma-separated list of properties as defined in the Introducing ZFS Properties section.

* A comma-separated list of literal fields, name, value, property, and source, to be output followed by a space and an argument, which is a comma-separated list of properties.

The following example shows how to retrieve a single value by using the -H and -o options of zfs get:

# zfs get -H -o value compression tank/home

on

Rights profiles – The user_attr, prof_attr, and exec_attr databases are now read-only. These local files databases are assembled from fragments that are located in /etc/user_attr.d, /etc/security/prof_attr.d, and /etc/security/exec_attr.d.

The fragment files are not merged into a single version of the file, but left as fragments. This change enables packages to deliver complete or partial RBAC profiles. Entries that are added to the local files repository with the useradd and profiles commands are added to the local-entries file in the fragment directory.

The beadm utility enables you to create a new boot environment based on an existing snapshot.

Note:

* You can manage the boot environments on your system either by using the beadm command or by using the Package Manager.

* A boot environment is a bootable instance of the Oracle Solaris operating system image plus any other application software packages installed into that image. System administrators can maintain multiple boot environments on their systems, and each boot environment can have different software versions installed.

Link-Based Failure Detection

Link-based failure detection is always enabled, provided that the interface supports this type of failure detection.

To determine whether a third-party interface supports link-based failure detection, use the ipmpstat -i command. If the output for a given interface includes an unknown status for its LINK column, then that interface does not support link-based failure detection. Refer to the manufacturer's documentation for more specific information about the device.

The following list provides a brief description of each default checkpoint in the order the checkpoints are executed in most manifests.

transfer-ips-install – At this checkpoint, the distribution constructor contacts the IPS publishers and adds to the image the packages that are listed in the software_data element of the manifest.

set-ips-attributes – At this checkpoint, the constructor sets the publisher to be used by the installed system. The values set by this checkpoint are not relevant if you are building an automated installation image.

pre-pkg-img-mod – At this checkpoint, the constructor imports into the image the SMF service files that were specified in the configuration element of the manifest. Also, the constructor modifies some files to optimize the image.

To make IPMP groups persists across reboots you would have to do some work:

To configure an IPMP group that persists across system reboots, you would edit the hostname configuration file of the IPMP interface to add data addresses.

Note: The same (non-null) character string IPMP group name identifies all interfaces in the group. You can place interfaces from NICs of different speeds within the same IPMP group, as long as the NICs are of the same type. For example, you can configure the interfaces of 100-megabit Ethernet NICs and the interfaces of one gigabit Ethernet NICs in the same group. As another example, suppose you have two 100-megabit Ethernet NICs. You can configure one of the interfaces down to 10 megabits and still place the two interfaces into the same IPMP group.

Incorrect:

Not A: You cannot place two interfaces of different media types into an IPMP group. For example, you cannot place an ATM interface in the same group as an Ethernet interface.

Not B: An IP multipathing group, or IPMP group, consists of one or more physical interfaces on the same system that are configured with the same IPMP group name. All interfaces in the IPMP group must be connected to the same IP link.

dumpadm - configure operating system crash dump

SYNOPSIS

/usr/sbin/dumpadm [-nuy] [-c content-type] [-d dump-device]

[-m mink | minm | min%] [-s savecore-dir]

[-r root-dir] [-z on | off]

The options include:

A: -d dump-device

Modify the dump configuration to use the specified dump device.

B: -s savecore-dir

Modify the dump configuration to use the specified directory to

save files written by savecore.

D: -m mink | minm | min%

Create a minfree file in the current savecore directory indicating

that savecore should maintain at least the specified amount of free

space in the file system where the savecore directory is located.

E: -z on | off

Modify the dump configuration to control the operation of savecore on reboot. The options are on, to enable saving core files in a compressed format, and off, to automatically uncompress the crash dump file. The default is on, because crash dump files can be very large and require less file system space if saved in a compressed format.

A: The pkd.depotd service is managed by SMF under the service identifier svc:/application/pkg/server.

D:

* Example:

Configure pkg.depotd to provide remote access. pkg.depotd provides an HTTP interface to a pkg repo. Here we are going to make the repo server listen on port 10000, and use the repo dir we created as its default.

# svcadm disable pkg/server

# svccfg -s pkg/server setprop pkg/inst_root = /data/myrepo

# svccfg -s pkg/server setprop pkg/port = 10000

# svcadm refresh pkg/server

# svcadm enable pkg/server

* pkg.depotd is the depot server for the image packaging system. It provides network access to the data contained within a package repository. Clients that do not support direct access to a repository through the file system, or for which network access is the only available or preferred method of transport, typically use the package depot.

* Set the default scheduler for the system to be the FSS.

# dispadmin -d FSS

* Scheduling Class on a System with Zones Installed

Non-global zones use the default scheduling class for the system. If the system is updated with a new default scheduling class setting, non-global zones obtain the new setting when booted or rebooted.

The preferred way to use FSS in this case is to set FSS to be the system default scheduling class with the dispadmin command.

Must be in the same network range (see * below).

Different speeds are fine (see ** below).

* An IP multipathing group, or IPMP group, consists of one or more physical interfaces on the same system that are configured with the same IPMP group name. All interfaces in the IPMP group must be connected to the same IP link (A, not B, not C, Not D).

** The same (non-null) character string IPMP group name identifies all interfaces in the group. You can place interfaces from NICs of different speeds within the same IPMP group, as long as the NICs are of the same type. For example, you can configure the interfaces of 100-megabit Ethernet NICs and the interfaces of one gigabit Ethernet NICs in the same group. As another example, suppose you have two 100-megabit Ethernet NICs. You can configure one of the interfaces down to 10 megabits and still place the two interfaces into the same IPMP group.

svccfg

subcommand: revert [snapshot]

Reverts the administrative customizations of the currently selected instance and its service to those recorded in the named snapshot. If no argument is given, use the currently selected snapshot and deselect it on success.

Incorrect:

Not A: Rollback to as-delivered system: svccfg delcust

svccfg

subcommand: delcust [-M] [pattern]

Delete any administrative customizations for the current selection. If an argument is supplied, it is taken as a glob pattern and only property groups and properties with names that match the argument are deleted.

Not B: There is no command revetsnap

Not C: Run the command /lib/svc/bin/restore_repository, and follow its instructions to restore one of the automatic backup copies of the repository. Upon successful completion, the system or local zone will be rebooted, and the restored repository will take effect.

Not D:

* Syntax:

priocntl -s [-c class] [class-specific options]

[-i idtype] [idlist]

* The priocntl command displays or sets scheduling parameters of the specified process(es). It can also be used to display the current configuration information for the system's process scheduler or execute a command with specified scheduling parameters.

Processes fall into distinct classes with a separate scheduling policy applied to each class. The process classes currently supported are the real-time class, time-sharing class, interactive class, fair-share class, and the fixed priority class.

* priocntl options include:

-c

class

Specifies the class to be set. (The valid class arguments are RT for real-time, TS for time-sharing, IA for inter-active, FSS for fair-share, or FX for fixed-priority.) If the specified class is not already configured, it is automatically configured.

-s

Sets the scheduling parameters associated with a set of processes.

root@solaris:~# zfs snapshot pool1/sales/qrreports@qrreportroot@solaris:~# zfs list -t snapshot -r pool1/sales/qrreportsNAME USED AVAIL REFER MOUNTPOINTpool1/sales/qrreports@qrreport 0 - 31K -root@solaris:~# zfs send -i pool1/sales/qrreports@qrreport pool1/sales/qrreports@mth2qtrreportError: Stream can not be written to a terminal.You must redirect standard output.

Example. Displaying Administratively Customized Properties (here only admin layer is displayed with –l)

The following command uses SMF layers to display administratively customized properties.

example% svcprop -p config -l admin svc:/network/dns/client

(A) config/domain astring admin my.domain.com

(D) config/nameserver net_address admin 10.22.33.44 10.44.33.11

Note:

* config/nameserver refers to the Solaris DNS server.

/ The nameserver keyword specifies DNS servers to query using IP address.

Example:

The /etc/resolv.conf file contains configuration directives for the DNS resolver. The following resolv.conf example shows two name servers and three search suffixes:

domain nj.bigcorporation.com

nameserver 192.168.10.11

nameserver 192.168.20.88

* The svcprop utility prints values of properties in the service configuration repository. Properties are selected by -p options and the operands

Example:

List all configuration changes that have been made in the SMF configuration repository to the name-service/switch service:

# svccfg -s name-service/switch listcust –L

How to Specify a Temporary Resource Cap for a Zone

This procedure is use to allocate the maximum amount of memory that can be consumed by a specified zone. This value lasts only until the next reboot. To set a persistent cap, use the zonecfg command.

1. Become superuser, or assume a role that includes the Process Management profile.

The System Administrator role includes the Process Management profile.

2. Set a maximum memory value of 512 Mbytes for the zone my-zone.

# rcapadm -z testzone -m 512M

Interface mode displays the state of all IP interfaces (IP links) that are tracked by in.mpathd on the system.

Incorrect:

Not A: Address mode displays the state of all IPMP data addresses on the system.

Not B: Group mode displays the state of all IPMP groups on the system.

Not D: Probe mode displays information about the probes being sent by in.mpathd.

Not E: Target mode displays IPMP probe target information.

Refer to step 3 below.

After a typical software installation, there can be a half dozen or more processes that need to be started and stopped during system startup and shutdown. In addition, these processes may depend on each other and may need to be monitored and restarted if they fail. For each process, these are the logical steps that need to be done to incorporate these as services in SMF:

1.Create a service manifest file.

2.Create a methods script file to define the start, stop, and restart methods for the service.

3.Validate and import the service manifest using svccfg(1M).

4.Enable or start the service using svcadm(1M).

5.Verify the service is running using svcs(1).

URL: http://www.oracle.com/technetwork/articles/servers-storage-admin/o11-118-s11-script-zones-524499.html

* AI Server Software Requirements include:

Default router

Ensure that your AI server has a default route set by using the netstat command to show network status. If your AI server does not have a default route set, you can set a static default route by populating the /etc/defaultrouter file with the IP address of a static default route for your server's network.

* For any currently active NCP (fixed or reactive), use the route command with the -p option to persistently add a route:

# route -p add default ip-address

Because this command applies the specified route to the currently active NCP, the default route is removed and potentially replaced, if the active NCP changes.

Incorrect:

Not A, Not B: The svccfg command manipulates data in the service configuration repository. svccfg can be invoked interactively, with an individual subcommand, or by specifying a command file that contains a series of subcommands.