1z0-821 Practice Exam Questions with Answers Oracle Solaris 11 System Administration Certification

A: ZFS also allows you to use UFS files as virtual devices in your storage pool. This feature is aimed primarily at testing and enabling simple experimentation, not for production use. The reason is that any use of files relies on the underlying file system for consistency. If you create a ZFS pool backed by files on a UFS file system, then you are implicitly relying on UFS to guarantee correctness and synchronous semantics.

However, files can be quite useful when you are first trying out ZFS or experimenting with more complicated layouts when not enough physical devices are present. All files must be specified as complete paths and must be at least 64 Mbytes in size.

B, E: You can construct logical devices for ZFS using volumes presented by software-based volume managers, such as Solaris Volume Manager (SVM) or Veritas Volume Manager (VxVM). However, these configurations are not recommended. While ZFS functions properly on such devices, less-than-optimal performance might be the result.

Use the pkg revert command to restore files to their as-delivered condition.

The process of subnetting involves the separation of the network and subnet portion of an address from the host identifier. This is performed by a bitwise AND operation between the IP address and the (sub)network prefix. The result yields the network address or prefix, and the remainder is the host identifier.

The routing prefix of an address is written in a form identical to that of the address itself. This is called the network mask, or netmask, of the address. For example, a specification of the most-significant 18 bits of an IPv4 address, 11111111.11111111.11000000.00000000, is written as 255.255.192.0.

How to Set Up Email Notification of SMF Transition Events

This procedure causes the system to generate an email notification each time one of the services or a selected service has a change in state. You can choose to use either SMTP or SNMP. Normally, you would only select SNMP if you already have SNMP configured for some other reason.

By default, SNMP traps are sent on maintenance transitions. If you use SNMP for monitoring, you can configure additional traps for other state transitions.

1. Become an administrator or assume a role that includes the Service Management rights profile.'

2. Set notification parameters.

Example 1:

The following command creates a notification that sends email when transactions go into the maintenance state.

# /usr/sbin/svccfg setnotify -g maintenance mailto:sysadmins@example.com

Example 2:

The following command creates a notification that sends email when the switch service goes into the online state.

# /usr/sbin/svccfg -s svc:/system/name-service/switch:default setnotify to-online \ mailto:sysadmins@example.com

Note: 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.

Changes made to an existing service in the repository typically do not take effect for that service until the next time the service instance is refreshed.

pkgchk checks the accuracy of installed files or, by using the -l option, displays information about package files. pkgchk checks the integrity of directory structures and files. Discrepancies are written to standard error along with a detailed explanation of the problem.

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

* Adding or updating individual packages – To add individual software packages, use the pkg install command. Any dependent packages are also updated at the same time.

* install package updates that deliver fixes– A pkg update operation might include bug fixes, so the operation is similar to applying a specific patch or patches in previous Oracle Solaris releases.

Note: The IPS interfaces first check for updates for currently installed packages before retrieving them via the network. By default, interfaces check repository catalogs in the following locations:

* The default installation repository at pkg.oracle.com/solaris/release.

* The support repository in My Oracle Support. This repository is restricted to users with Oracle Solaris 11 Express support contracts, and it contains packages with the latest bug fixes. For this reason, a support contract must be purchased for production deployments.

Etherstubs are pseudo ethernet NICs which are managed by the system administrator. You can create VNICs over etherstubs instead of over physical links. VNICs over an etherstub become independent of the physical NICs in the system. With etherstubs, you can construct a private virtual network that is isolated both from the other virtual networks in the system and from the external network. For example, you want to create a network environment whose access is limited only to your company developers than to the network at large. Etherstubs can be used to create such an environment.

Note: Oracle Solaris 11 introduces a new and powerful network stack architecture which includes:

* Networking virtualization with virtual network interface cards (VNICs) and virtual switching (etherstubs)

* Tight integration with zones

* Network resource management - efficient and easy to manage integrated quality of service (QoS) to enforce bandwidth limit on VNICs and traffic flows

B: By carrying SCSI commands over IP networks, the iSCSI protocol enables you to access block devices from across the network as if they were connected to the local system. COMSTAR provides an easier way to manage these iSCSI target devices.

D: Common Multiprotocol SCSI TARget, or COMSTAR, a software framework that enables you to convert any Oracle Solaris 11 host into a SCSI target device that can be accessed over a storage network by initiator hosts.

E: One IP port can handle multiple iSCSI target devices.

From the content of the /etc/shadow file we get:

* username: jack

* encrypted password: $5$9JFrt54$7JdwmO.F11Zt/ jFeeOhDmnw93LG7Gwd3Nd/cwCcNWFFg

* Last password change (lastchanged): Days since Jan 1, 1970 that password was last changed: 0

* Minimum: The minimum number of days required between password changes i.e. the number of days left before the user is allowed to change his/her password: 15

Maximum: The maximum number of days the password is valid (after that user is forced to change his/her password): 30 Warn : The number of days before password is to expire that user is warned that his/her password must be changed: 3

* Inactive : The number of days after password expires that account is disabled

* Expire : days since Jan 1, 1970 that account is disabled i.e. an absolute date specifying when the login may no longer be used

The /var/adm/messages is the file to which all the messages printed on the console are logged to by the Operating System. This helps to track back check the console messages to troubleshoot any issues on the system.

Syslog daemon also writes to this /var/adm/messages file.

The /var/adm/messages file monitored and managed by newsyslog and its configuration file is /usr/lib/newsyslog.

This script runs as the roots cron job everyday, checks the /var/adm/messages file and copies/moves it to /var/adm/messages.0, 1, 2, 3, 4, 5, 6, 7. In other words, it does the Log Rotation for the /var/adm/messages.

In an event the /var file system is running out of space, these files needs to checked and can be removed (not the actual /var/adm/messages itself) to free up space on the file system.

However, care has to be taken, if you decide to empty the /var/adm/messages itself for any reason. This process is called Truncation.

SOLARIS SYSTEM ADMIN TIPS, /var/adm/messages

Oracle Solaris 11 introduces user environment and command-line argument changes that include the following:

* Shell changes - The default shell, /bin/sh, is now linked to ksh93. The default user shell is the Bourne-again (bash) shell.

* The legacy Bourne shell is available as /usr/sunos/bin/sh.

* The legacy ksh88 is available as /usr/sunos/bin/ksh from the shell/ksh88 package.

* Korn shell compatibility information is available in /usr/share/doc/ksh/COMPATIBILITY.

B: Setting the default route on Solaris is easy. If you are trying to just set the route temporarily you can use the route command:

Route add default

Example:

Route add default 192.168.1.1

Note: Route command manipulates the kernel routing tables. Routing is the process of forwarding a packet from one computer to another. It is based on the IP address in the IP packet header and netmask.

F: If you want the route to be persisted when you reboot the system, you will need to set the route in the /etc/defaultrouter file.

/etc/defaultrouter

Example:

Echo 192.168.1.1 > /etc/defaultrouter

Comparing sysidcfg File Keywords to System Configuration Profile Directives

The following table compares sysidcfg file keywords with example AI system configuration profile specifications. 

sysidcfg File Keyword

System Configuration Profile Directives

Etc.

A: You can configure Common Multiprotocol SCSI TARget, or COMSTAR, a software framework that enables you to convert any Oracle Solaris 11 host into a SCSI target device that can be accessed over a storage network by initiator hosts.

This means you can make storage devices on a system available to Linux, Mac OS, or Windows client systems as if they were local storage devices. Supported storage protocols are iSCSI, FC, iSER, and SRP.

B: iSCSI targets cannot be configured as dump devices.

The file command determines the file type file tests each argument in an attempt to classify it. There are three sets of tests, performed in this order: filesystem tests, magic tests, and language tests. The first test that succeeds causes the file type to be printed.

http://docs.oracle.com/cd/E23823_01/html/819-5461/ghzvz.html

Use the chmod command to change permissions for a file or directory. You must be the owner of a file or directory, or have root access, to change its permissions.

Here we do not know if brian owns db_data.

Note:

Permission

7 full

6 read and write

5 read and execute

4 read only

3 write and execute

2 write only

1 execute only

0 none

0 --- no permission

1 --x execute

2 -w- write

3 -wx write and execute

4 r-- read

5 r-x read and execute

6 rw- read and write

7 rwx read, write and execut

Solaris: Solaris Advanced User's Guide

If you want to create a backup of an existing boot environment, for example, prior to modifying the original boot environment, you can use the beadm command to create and mount a new boot environment that is a clone of your active boot environment. This clone is listed as an alternate boot environment in the GRUB menu for x86 systems or in the boot menu for SPARC systems.

When you clone a boot environment by using the beadm create command, all supported zones in that boot environment are copied into the new boot environment.

How to Create a Boot Environment

1. Become the root role.

2. Create the boot environment.

# beadm create BeName

BeName is a variable for the name of the new boot environment. This new boot environment is inactive.

3. (Optional) Use the beadm mount command to mount the new boot environment.

# beadm mount BeName mount-point

Note: If the directory for the mount point does not exist, the beadm utility creates the directory, then mounts the boot environment on that directory.

If the boot environment is already mounted, the beadm mount command fails and does not remount the boot environment at the newly specified location.

4. (Optional) Activate the boot environment.

# beadm activate BeName

BeName is a variable for the name of the boot environment to be activated.

On reboot, the newly active boot environment is displayed as the default selection in the x86 GRUB menu or the SPARC boot menu.

Solaris 11 Express makes it pretty easy to set up a local copy of the repository.

A common reason folks need access to a local repository is because their system is not connected to the Internet.

Tthe pkg set-publisher command can be used to for example add a publisher or to enable or disable a publisher.

Note: Example Adding a Publisher

Use the -g option to specify the publisher origin URI.

# pkg set-publisher -g http://pkg.example.com/release example.com

Example Specifying the Preferred Publisher

Use the -P option to specify a publisher as the preferred publisher. The specified publisher moves to the top of the search order. You can specify the -P option when you add a publisher or you can modify an existing publisher.

# pkg set-publisher -P example.com

Example Enabling or Disabling a Publisher

Use the -d option to disable a publisher. The preferred publisher cannot be disabled. A disabled publisher is not used in package operations such as list and install. You can modify the properties of a disabled publishers.

Use the -e option to enable a publisher.

# pkg set-publisher -d example2.com

http://www.oracle.com/technetwork/server-storage/solaris11/overview/solaris-matrix-1549264.html

B: The mount point Error. The following message appears during the boot process or in response toan explicit mount request and indicates a non-existent mount point.

Mount: mount-point /DS9 does not exist.

To solve the mount point error condition, check that the mount point exists on the client. Check the spelling of the mount point on the command line or in the /etc/vfstab file (B) on the client, or comment outthe entry and reboot the system.

Note: The /etc/vfstab file lists all the file systems to be automatically mounted at system boot time, with the exception of the /etc/mnttab and /var/run file systems.

E: showmount

This command displays all clients that have remotely mounted file systems that are shared from an NFS server, or only the file systems that are mounted by clients, or the shared file systems with the client access information. The command syntax is:

showmount [ -ade ] [ hostname ]

where -a prints a list of all the remote mounts (each entry includes the client name and the directory), -d prints a list of the directories that are remotely mounted by clients, -e prints a list of the files shared (or exported), and hostname selects the NFS server to gather the information from. If hostname is not specified the local host is queried.

F: * mountd Daemon

This daemon handles file-system mount requests from remote systems and provides access control. The mountd daemon checks /etc/dfs/sharetab to determine which file systems are available for remote mounting and which systems are allowed to do the remote mounting.

* Commands for Troubleshooting NFS Problems

These commands can be useful when troubleshooting NFS problems.

rpcinfo Command

This command generates information about the RPC service that is running on a system.

The Internet Control Message Protocol (ICMP) is one of the core protocols of the Internet Protocol Suite.

ICMP differs from transport protocols such as TCP and UDP in that it is not typically used to exchange data between systems, nor is it regularly employed by end-user network applications (with the exception of some diagnostic tools like ping and traceroute).

The /etc/passwd contains one entry per line for each user (or user account) of the system. All fields are separated by a colon (:) symbol. Total seven fields as follows.

1. Username: It is used when user logs in. It should be between 1 and 32 characters in length.

2. Password: An x character indicates that encrypted password is stored in /etc/shadow file.

3. User ID (UID): Each user must be assigned a user ID (UID). UID 0 (zero) is reserved for root and UIDs 1-99 are reserved for other predefined accounts. Further UID 100-999 are reserved by system for administrative and system accounts/groups.

4. Group ID (GID): The primary group ID (stored in /etc/group file)

5. User ID Info: The comment field. It allow you to add extra information about the users such as user's full name, phone number etc. This field use by finger command.

6. Home directory: The absolute path to the directory the user will be in when they log in. If this directory does not exists then users directory becomes /

7. Command/shell: The absolute path of a command or shell (/bin/bash). Typically, this is a shell. Please note that it does not have to be a shell.

The ipadm delete-addr subcommand removes addresses from interfaces.

To remove an address from the IPMP group, type the following command:

# ipadm delete-addr addrobj

The addrobj uses the naming convention inder-interface/user-string.

A: How to Log In to the Zone Console Use the zlogin command with the -C option and the name of the zone, for example, my-zone.

global# zlogin -C my-zone

C: To disconnect from a non-global zone, use one of the following methods.

* To exit the zone non-virtual console:

zonename# exit

* To disconnect from a zone virtual console, use the tilde (~) character and a period:

zonename# ~.

How to Monitor All Failed Login Attempts

This procedure captures in a syslog file all failed login attempts.

Assume the Primary Administrator role, or become superuser.

1. Assume the Primary Administrator role, or become superuser.

2. (C) Set up the /etc/default/login file with the desired values for SYSLOG and SYSLOG_FAILED_LOGINS

3. (A) Create a file with the correct permissions to hold the logging information.

Create the authlog file in the /var/adm directory.

4. (B) Edit the syslog.conf file to log failed password attempts.

This example shows how to display the default root crontab file.

$ suPassword:

# crontab -l

#ident "@(#)root 1.19 98/07/06 SMI" /* SVr4.0 1.1.3.1 */

#

# The root crontab should be used to perform accounting data collection.

#

#

10 3 * * * /usr/sbin/logadm

15 3 * * 0 /usr/lib/fs/nfs/nfsfind

30 3 * * * [ -x /usr/lib/gss/gsscred_clean ] && /usr/lib/gss/gsscred_clean

#10 3 * * * /usr/lib/krb5/kprop_script ___slave_kdcs___

A: You will see two files starting with id_rsa. id_rsa is the private key and id_rsa.pub is public key.

E: The .ssh/known_hosts file

In order to use public-key secure connection with other hosts (ssh, scp, sftp) there is a special directory, ~/.ssh/, where passphrases and public keys are stored. Normally you wouldn't need to know the gory details, but from time to time a host will change its public key and then you have difficulty using ssh or scp with that host, and have to edit a file named known_hosts.

If you try to ssh to another computer, but get an error message that warns about a changed or incorrect public key, then it is probably just a case of that host changing its public key. (It is possible, though usually not the case, that malicious hacking is involved.) Unless you actually suspect hacker involvement, you can edit the file ~/.ssh/known_hosts using your usual text editor (vi, emacs, nedit, or pico) and delete any line with the name of that host.

Then when you try to ssh that host again, it will be like the first time ever; ssh will ask you if you want to accept a new public key, you type the whole word yes, and everything will proceed normally from there.

Here is what a typical ~/.ssh/known_hosts file might contain. Note that newton is represented on two different lines:

newton 1024 35 153438062610297067329638677441205712613292203533062535600064224677647442245028855505387934431717435134842994423656065076260604296084868001730665553662299156116414854701274715680961503198280525759778667306417179500370189017139564144825610347509023078143132936185076849630461827976942220442313116255293297021841

ucsub 1024 37 132170811640421742212085598383135714069016332111955003414250071326834884018721183646445780180633494496866895830879394309011412231102757022090299732775466435482517698989962531081214859205054227533597152962802400251809883548442498002326460312850336779152617243800769119880843882425555806081435017335194477605333

simpson 1024 41 84089692059249458440345362273528263453600205470157624776507876697481412839375294315107162983484390901602702661279164375297211645960275026726690836525966507273615949171966757621717137045892868050436884725563247792566023489318554721885765548457461907512536847079297627580626353420887972219277539015703446529603

newton, 128.138.249.8 ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEA0d7Aoure0toNJ+YMYi61QP2ka8m5x5ZQlT7obP8CK3eropfqsMPPY6uiyIh9vpiFX2r1LHcbx139+vG6HOtVvuS8+IfMDtawm3WQvRuOopz3vVy5GtMwtaOgehsXoT930Ryev1bH5myPtWKlipITsOd2sX9k3tvjrmme4KCGGss=

An “f” in the F column indicates the package is frozen. If a package is frozen, you can only install or update to packages that match the frozen version. 

Note: The “i” in the I column indicates that these packages are installed in this image.

Adding and Updating Oracle Solaris 11 Software Packages, Showing Package Install State Information

A: Zones can use Oracle Solaris 11 products and features such as the following:

Oracle Solaris ZFS encryption

Network virtualization and QoS

CIFS and NFS

C: Non-global zones cannot modify the system clock by default, but each zone can have a separate time zone setting.

F (not E): The Oracle Solaris Zones partitioning technology is used to virtualize operating system services and provide an isolated and secure environment for running applications. A zone is a virtualized operating system environment created within a single instance of the Oracle Solaris operating system.

The $HOME/.profile file is an initialization file that is executed after the /etc/profile when logging in to the Bourne or Korn shell. The file contains user preferences for variable settings. If the ENV variable is set to .kshrc, the .kshrc file executes every time a new shell begins execution. The $HOME/.profile is copied from the /etc/skel/local.profile file by the Administration Tool when creating a new account.

Note: /etc/skel/local.profile

Per-system configuration file for

sh/ksh/ksh93/bash login sessions,

installed for new users

D: zoneadm halt command halts the specified zones. halt bypasses running the shutdown scripts inside the zone. It also removes run time resources of the zone.

E: Use: zlogin zone shutdown

to cleanly shutdown the zone by running the shutdown scripts.

Use this procedure to cleanly shut down a zone.

1. Become superuser, or assume the Primary Administrator role.

2. Log in to the zone to be shut down, for example, my-zone, and specify shutdown as the name of the utility and init 0 as the state global# zlogin my-zone shutdown -y -g0 -i 0

B: The /etc/default/syslogd file contains the following default parameter settings. See FILES.

LOG_FROM_REMOTE

Specifies whether remote messages are logged. LOG_FROM_REMOTE=NO is equivalent to the -t command-line option. The default value for LOG_FROM_REMOTE is YES.

A: terminal

The js2ai tool does not perform any translation. Make sure the terminal type speciied in the sysidcfg ile is supported in Oracle Solaris 11.

D: system_locale

The js2ai tool does not perform any translation. Make sure the locale specified in the sysidcfg ile is supported in Oracle Solaris 11.

Here we should use SIGTERM to terminate the process.

Note:

When no signal is included in the kill command-line syntax, the default signal that is used is –15 (SIGKILL). Using the –9 signal (SIGTERM) with the kill command ensures that the process terminates promptly. However, the –9 signal should not be used to kill certain processes, such as a database process, or an LDAP server process. The result is that data might be lost.

Tip - When using the kill command to stop a process, first try using the command by itself, without including a signal option. Wait a few minutes to see if the process terminates before using the kill command with the -9 signal.

If you are assigning a static IP address, use the following syntax:

# ipadm create-addr -T static -a address addrobj

where addrobj uses the naming format interface/user-defined-string, such as e1000g0/v4globalz.

Note:

create-addr [-t] -T static [-d] -a {local | remote}=addr[/prefixlen], ... addrobj

Creates a static IPv4 or IPv6 address on the interface specified in addrobj. If the interface on which the address is created is not plumbed, this subcommand will implicitly plumb the interface. The created static address will be identified by addrobj.

By default, a configured address will be marked up, so that it can be used as a source or destination of or for outbound and inbound packets.

JumpStart: Use the setup_install_server(1M) command.

AI: Use the installadm create-service command.

A: dir followed by a single letter.

C: dir followed by any characters ending with a.

D: dir followed by any characters, then character b, then one single character.

only dirabc matches

https://docs.oracle.com/cd/E23824_01/html/E21798/glitd.html#scrolltoc

http://docs.oracle.com/cd/E23824_01/html/E21798/glitd.html#aizoneconf

Audit Significant Events in Addition to Login/Logout (see step 2 below)

Use this procedure to audit administrative commands, attempts to invade the system, and other significant events as specified by your site security policy.

For all users and roles, add the AUE_PFEXEC audit event to their preselection mask.

# usermod -K audit_flags=lo, ps:no username

# rolemod -K audit_flags=lo, ps:no rolename

# auditconfig -setpolicy +argv

3- Record the environment in which audited commands are executed.

# auditconfig -setpolicy +arge

Note: [-t] -setpolicy [+|-]policy_flag[, policy_flag ...]

Set the kernel audit policy. A policy policy_flag is literal strings that denotes an audit policy. A prefix of + adds the policies specified to the current audit policies. A prefix of - removes the policies specified from the current audit policies. No policies can be set from a local zone unless the perzone policy is first set from the global zone.

ZFS Deduplication Property

Solaris Express Community Edition, build 129: In this Solaris release, you can use the deduplication property to remove redundant data from your ZFS file systems. If a file system has the dedup property enabled, duplicate data blocks are removed synchronously. The result is that only unique data is stored and common components are shared between files.

You can enable this property as follows:

# zfs set dedup=on tank/home

A: ZFS can automatically share file systems by setting the sharenfs property. Using this property, you do not have to modify the /etc/dfs/dfstab file when a new file system is shared. The sharenfs property is a comma-separated list of options to pass to the share command. The value on is an alias for the default share options, which provides read/write permissions to anyone. The value off indicates that the file system is not managed by ZFS and can be shared through traditional means, such as the /etc/dfs/dfstab file. All file systems whose sharenfs property is not off are shared during boot.

This procedure captures in a syslog file all failed login attempts.

1. Set up the /etc/default/login file with the desired values for SYSLOG and SYSLOG_FAILED_LOGINS

Edit the /etc/default/login file to change the entry. Make sure that SYSLOG=YES is uncommented.

2. Create a file with the correct permissions to hold the logging information.

Create the authlog file in the /var/adm directory.

3. Edit the syslog.conf file to log failed password attempts.

Send the failures to the authlog file.

Unlike DOS, which uses the file extension to determine if a file is executable or not, UNIX relies on file permissions.

The value assigned by umask is subtracted from the default.

User's file creation mask. umask sets an environment variable which automatically sets file permissions on newly created files. i.e. it will set the shell process's file creation mask to mode.

umask 000 would grant full permissions.

Note: 777 full permissions

UFS quotas enable system administrators to control the size of file systems. Quotas limit the amount of disk space and the number of inodes, which roughly corresponds to the number of files, that individual users can acquire. For this reason, quotas are especially useful on the file systems where user home directories reside. As a rule, the public and /tmp file systems usually do not benefit significantly by establishing quotas.

Note: The cp command copies files and directories.

On POSIX-compliant platforms, SIGTERM is the signal sent to a process to request its termination. The symbolic constant for SIGTERM is defined in the header file signal.h. Symbolic signal names are used because signal numbers can vary across platforms, however on the vast majority of systems, SIGTERM is signal #15.

SIGTERM is the default signal sent to a process by the kill or killall commands. It causes the termination of a process, but unlike the SIGKILL signal, it can be caught and interpreted (or ignored) by the process. Therefore, SIGTERM is akin to asking a process to terminate nicely, allowing cleanup and closure of files. For this reason, on many Unix systems during shutdown, init issues SIGTERM to all processes that are not essential to powering off, waits a few seconds, and then issues SIGKILL to forcibly terminate any such processes that remain.

As your machine gets started, it will need to know the mapping of some hostnames to IP addresses before DNS can be referenced. This mapping is kept in the /etc/hosts file. In the absence of a name server, any network program on your system consults this file to determine the IP address that corresponds to a host name.

B (not A, not D, Not C): If two client machines need to be installed with the same version of the Oracle Solaris 11 OS but

need to be installed differently in other ways, then create two AI manifests for the AI install service. The different AI manifests can specify different packages to install or a different slice as the install target, for example.

Note: An AI manifest provides installation instructions.

The AI manifest specifies one or more IPS package repositories where the client retrieves the packages needed to complete the installation. The AI manifest also includes the names of additional packages to install and information such as target installation device and partition information.

F: The install server can be either an x86 machine or a SPARC machine.

Check the physical connection.

Single quotes are most strict. They prevent even variable expansion. Double quotes prevent wildcard expansion but allow variable expansion. For example:

#!/bin/sh

echo $SHELL

echo "$SHELL"

echo '$SHELL'

This will print:

/usr/bin/bash

/usr/bin/bash

$SHELL

Example: Encrypting a ZFS File System by Using a Raw Key

In the following example, an aes-256-ccm encryption key is generated by using the pktool command and is written to a file, /cindykey.file.

# pktool genkey keystore=file outkey=/cindykey.file keytype=aes keylen=256

Then, the /cindykey.file is specified when the tank/home/cindy file system is created.

# zfs create -o encryption=aes-256-ccm -o keysource=raw, file:///cindykey.file tank/home/cindys

Use the pkg search command to search for packages whose data matches the specified pattern.

Like the pkg contents command, the pkg search command examines the contents of packages. While the pkg contents command returns the contents, the pkg search command returns the names of packages that match the query.

B: The Network Status notification icon is only displayed on the desktop if you are using NWAM to automatically configure your network.

C: All online (Wireless)

Indicates all manually enabled connections in the enabled network profile are online and that the required number of connections in the enabled profile group (if such a group exists) are online. The required number is the same as those described for the All online (Wired) status.

Note that at least one online connection is wireless.

'ipadm show-addr' displays all the configured addresses on the system.

Example:

# ipadm show-addr

ADDROBJ TYPE STATE ADDR

lo0/v4 static ok 127.0.0.1/8

lo0/v6 static ok ::1/128

The host he is trying to connect to (oracle) is not running the required service (ssh).

A: The beadm utility includes support for creating and administering non-global zone boot environments.

Note: 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.

B: Role-based access control (RBAC) is a security feature for controlling user access to tasks that would normally be restricted to the root role. By applying security attributes to processes and to users, RBAC can divide up superuser capabilities among several administrators.

STMF – Manages transactions, such as context and resources for Small Computer System Interface (SCSI) command execution, and tracking logical unit and port providers. STMF also handles logical unit mappings, allocating memory, recovering failed operations, enumeration, and other necessary functions of an I/O stack.

STMF is controlled by stmfadm, and stmfadm is the majority of the commands you will be using to administer COMSTAR (COmmon Multiprotocl Scsi TARget).

Install the packages you need for COMSTAR with iSCSI and reboot:

# pfexec pkg install storage-server

# pfexec pkg install SUNWiscsit

# shutdown -y -i6 -g0

Note: You can set up and configure a COMSTAR Internet SCSI (iSCSI) target and make it available over the network. The iSCSI features can work over a normal Internet connection (such as Ethernet) using the standard iSCSI protocol. The iSCSI protocol also provides naming and discovery services, authentication services using CHAP and RADIUS, and centralized management through iSNS.

The COMSTAR target mode framework runs as the stmf service. By default, the service is disabled. You must enable the service to use COMSTAR functionality. You can identify the service with the svcs command. If you have not rebooted the server since installing the group/feature/storage-server package, the service might not be enabled correctly.

The zoneadm command is the primary tool used to install and administer non-global zones. Operations using the zoneadm command must be run from the global zone on the target system.

How to Install the solaris10 Branded Zone

A configured solaris10 branded zone is installed by using the zoneadm command with the install subcommand.

Example: global# zoneadm -z s10-zone install -a /net/machine_name/s10-system.flar –u

A: Non-global zones can not utilize DHCP (neither client nor server).

B (not C): By default, non-global zones will be configured with a shared IP functionality. What this means is that IP layer configuration and state is shared between the zone you’re creating and the global zone. This usually implies both zones being on the same IP subnet for each given NIC.

Note: A zone is a virtual operating system abstraction that provides a protected environment in which applications run. The applications are protected from each other to provide software fault isolation. To ease the labor of managing multiple applications and their environments, they co-exist within one operating system instance, and are usually managed as one entity.

The original operating environment, before any zones are created, is also called the "global zone" to distinguish it from non-global zones, The global zone is the operating system instance.

Incorrect answer:

E: Exclusive-IP zones can use IPMP. IPMP is configured the same way in an exclusive-IP zone as it is on a system not using zones.

For shared-IP zones, IPMP can be configured in the global zone.

F: Full IP-level functionality is available in an exclusive-IP zone.

An exclusive-IP zone has its own IP-related state.

An exclusive-IP zone is assigned its own set of data-links using the zonecfg command. The zone is given a data-link name such as xge0, e1000g1, or bge32001, using the physical property of the net resource. The address property of the net resource is not set.

Note that the assigned data-link enables the snoop command to be used.

The dladm command can be used with the show-linkprop subcommand to show the assignment of data-links to running exclusive-IP zones.

By default, Solaris will boot to the pseudo milestone “all” and start all services. This behaviour can be changed at boot time using either “-s” to reach single-user, or the new SMF option “-m milestone=XXX” (see kernel(1M) for a list of the bootable milestones) to select an explicit milestone.

Note: boot -s is the same as: boot -m milestone=single-user

with the difference being that the former is a lot less to type and is what most SysAdmins will be familiar with.

Show address information, either for the given addrobj or all the address objects configured on the specified interface, including the address objects that are only in the persistent configuration.

Example:

# ipadm show-addr

ADDROBJ TYPE STATE ADDR

lo0/v4 static ok 127.0.0.1/8

lo0/v6 static ok ::1/128

The sulog file, /var/adm/sulog, is a log containing all attempts (whether successful or not) of the su command. An entry is added to the sulog file every time the su command is executed. The fields in sulog are: date, time, successful (+) or unsuccessful (-), port, user executing the su command, and user being switched to. In the preceding example, all su attempts were successful, except for the attempt on 2/23 at 20:51, when user pete unsuccessfully attempted to su to user root.

Look for entries where an unauthorized user has used the command inappropriately. The following entry shows a successful (indicated by +) su from user userid to root.

SU 03/31 12:52 + pts/0 -root

A: the pgk list command display a list of packages in the current image, including state and other information. By default, package variants for a different architecture or zone type are excluded.

D: pkginfo displays information about software packages that are installed on the system (with the first synopsis, with -l) or that reside on a particular device or directory (with the second synopsis, with -r).

Without options, pkginfo lists the primary category, package instance, and the names of all completely installed and partially installed packages. It displays one line for each package selected.

With -r, retrieve the data from the repositories of the image's configured publishers. Note that you must specify one or more package patterns in this case.

www.oracle.com would have to be resolved to an IP name by the domain name service.