1z0-822 Oracle Solaris 11 Advanced System Administration Questions and Answers

zpool detach pool device

Detaches device from a mirror. The operation is refused if there

are no other valid replicas of the data.

Network drivers that support link-based failure detection monitor the interface's link state and notify the networking subsystem when that link state changes.

Incorrect:

Not B: GLDv2 is a multi-threaded, clonable, loadable kernel module that provides support to device drivers for local area networks. Local area network (LAN) device drivers in the Solaris OS are STREAMS-based drivers that use the Data Link Provider Interface (DLPI) to communicate with network protocol stacks.

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

You cannot disable link-based failure detection if this method is supported by the NIC driver.

Note:

* To write a network driver for the Oracle Solaris OS, use the Solaris Generic LAN Driver (GLD) framework.

/ For new Ethernet drivers, use the GLDv3 framework.

/ To maintain older Ethernet, Token Ring, or FDDI drivers, use the GLDv2 framework.

* To ensure continuous availability of the network to send or receive traffic, IPMP performs failure detection on the IPMP group's underlying IP interfaces. Failed interfaces remain unusable until they are repaired. Remaining active interfaces continue to function while any existing standby interfaces are deployed as needed.

The in.mpathd daemon handles the following types of failure detection:

/ Probe-based failure detection, of two types:

No test addresses are configured (transitive probing).

Test addresses are configured.

/ Link-based failure detection, if supported by the NIC driver

C: You can use the scheduling-class property in zonecfg to set the scheduling class for the zone.

D: When you explicitly set the cpu-shares property, the fair share scheduler (FSS) will be used as the scheduling class for that zone. However, the preferred way to use FSS in this case is to set FSS to be the system default scheduling class with the dispadmin command. That way, all zones will benefit from getting a fair share of the system CPU resources. If cpu-shares is not set for a zone, the zone will use the system default scheduling class.

E: You can set the scheduling class for a zone through the resource pools facility. If the zone is associated with a pool that has its pool.scheduler property set to a valid scheduling class, then processes running in the zone run in that scheduling class by default.

Disabled in the MODE column means that all probe-based failure detection is disabled.

You must enable transitive probing to use this failure detection method that does not require test addresses.

Note:

* ipmpstat

- display IPMP subsystem status

The ipmpstat command concisely displays information about the IPMP subsystem.

The -t option identifies the probe targets that are associated with each IP interface in an IPMP group.

* Target mode displays IPMP probe target information. The following output fields are supported:

/ INTERFACE

The IP interface name associated with the information.

/ MODE

The probe target discovery mode:

routes

Probe targets found by means of the routing table.

multicast

Probe targets found by means of multicast ICMP probes.

disabled

All probe-based failure detection is disabled.

transitive

Failure detection is by means of transitive probing, where the health of the IP interface is determined by probing other active interfaces in the group.

/ TESTADDR

The source address used in outgoing probes. Active interfaces that are being used for data traffic, as well as interfaces that have been explicitly configured with NOFAILOVER test addresses, will have the hostname (or IP address) that is used for sending and receiving the ICMP probes. All other interfaces in the group will display the name of the interface from which the probes are sent. Note that if an active IP interface is configured with both IPv4 and IPv6 test addresses, probe target information will be displayed separately for each test address.

/ TARGETS

A space-separated list of probe target hostnames (or IP addresses) for ICMP probes, or target interfaces for transitive probes. The IP targets will be listed in firing order, and, if no probe targets could be found, this field will be empty.

The capped-memory resource sets limits for physical, swap, and locked memory. Each limit is optional, but at least one must be set.

Note:

* (not A, not B, not D) The privs key contains a comma-separated list of privilege numbers that will be effective when the command or action is run.

* euid and uid contain a single user name or a numeric user ID. Commands designated with euid run with the effective UID indicated, which is similar to setting the setuid bit on an executable file. Commands designated with uid run with both the real and effective UIDs. Setting uid may be more appropriate than setting the euid on privileged shell scripts.

* egid and gid contain a single group name or a numeric group ID. Commands designated with egid run with the effective GID indicated, which is similar to setting the setgid bit on a file. Commands designated with gid run with both the real and effective GIDs. Setting gid may be more appropriate than setting guid on privileged shell scripts.

* /etc/security/exec_attr is a local database that specifies the execution attributes associated with profiles.

/etc/security/exec_attr

Locally added entries. Make sure that the shipped header remains intact.

/etc/security/exec_attr.d/*

Entries added by package installation.

Only verbose mode is selected (-v) not checkpoints options.

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

Note:

* 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 your selection of files, packages, and scripts for the image that is being built. This process uses the checkpointing options that are available in the distro_const command.

* distro_const Command Options

/ distro_const build manifest

Builds an image in one step using specified manifest file

/ distro_const build -v

Verbose mode

/ distro_const build -l manifest

Lists all valid checkpoints at which you can pause and resume building an image

/ distro_const build -p checkpoint_name manifest

Pauses building an image at a specified checkpoint

/ distro_const build -r checkpoint_name manifest

Resumes building an image from a specified checkpoint

/ distro_const build -h

Displays help for the command

* After you have set up the manifest file that you plan to use and, if desired, customized the finalizer scripts, you are ready to build an image by running the distro_const command.

You can use the distro_const command to build an image in either of the following:

In one step

Pausing and restarting the build as needed to examine the content of the image and debug the scripts during the build process

The FX scheduler provides a scheduling policy for processes that require user or application control of scheduling priorities. The priorities of processes that run under FX are fixed.

The FX class provides a fixed-priority preemptive scheduling policy. This policy is used by processes that require user or application control of scheduling priorities but are not dynamically adjusted by the system. By default, the FX class has the same priority range as the TS, IA, and FSS classes. The FX class allows user or application control of scheduling priorities through user priority values assigned to processes within the class. These user priority values determine the scheduling priority of a fixed-priority process relative to other processes within its class.

Incorrect:

Not A: The fair share scheduling class enables you to allocate CPU time based on shares instead of the priority scheme of the timesharing (TS) scheduling class.

Not D: The goal of the time-sharing policy is to provide good response time to interactive processes and good throughput to CPU-bound processes. The scheduler switches CPU allocation often enough to provide good response time, but not so often that the system spends too much time on switching. Time slices are typically a few hundred milliseconds.

The time-sharing policy changes priorities dynamically and assigns time slices of different lengths.

* 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

Global Actions on Resource Control Values

Global actions apply to resource control values for every resource control on the system. You can use the rctladm command to perform the following actions:

* Display the global state of active system resource controls

* Set global logging actions

* DiffServ uses the 6-bit Differentiated services Field (DS field) in the IP header for packet classification purposes.

* In the Diffserv model, the marker marks a packet with a value that reflects a forwarding behavior. Marking is the process of placing a value in the packet's header to indicate how to forward the packet to the network. IPQoS contains two marker modules:

/ dscpmk – Marks the DS field in an IP packet header with a numeric value that is called the Differentiated Services codepoint, or DSCP. A Diffserv-aware router can then use the DS codepoint to apply the appropriate forwarding behavior to the packet.

/ dlcosmk – Marks the virtual local area network (VLAN) tag of an Ethernet frame header with a numeric value that is called the user priority. The user priority indicates the class of service (CoS), which defines the appropriate forwarding behavior to be applied to the datagram.

Note:

* Differentiated services or DiffServ is a computer networking architecture that specifies a simple, scalable and coarse-grained mechanism for classifying and managing network traffic and providing quality of service (QoS) on modern IP networks. DiffServ can, for example, be used to provide low-latency to critical network traffic such as voice or streaming media while providing simple best-effort service to non-critical services such as web traffic or file transfers.

* IPQoS, included in Solaris, includes the following modules, which are part of the Differentiated Services (Diffserv) architecture that is defined in RFC 2475:

Classifier

Meter

Marker

IPQoS adds the following enhancements to the Diffserv model:

Flow-accounting module

802.1D datagram marker

re

page reclaims.

The information is given in units per second.

Note:

* vmstat reports virtual memory statistics regarding kernel thread, virtual memory, disk, trap, and CPU activity.

Incorrect:

Not B: sr, pages scanned by clock algorithm

Not C: free

size of the free list (Kbytes)

Not D: fr

kilobytes freed

The ps command prints information about active processes.

Without options, ps prints information about processes asso-

ciated with the controlling terminal. The output contains

only the process ID, terminal identifier, cumulative execu-

tion time, and the command name. Otherwise, the information

that is displayed is controlled by the options.

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.