1z0-821 Oracle Solaris 11 System Administration Questions and Answers

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.

The following options are supported:

C

Connects to the zone console. Connects to the zone console.

Note:

After you install a zone, you must log in to the zone to complete its application environment. You might log in to the zone to perform administrative tasks as well. Unless the -C option is used to connect to the zone console, logging in to a zone using zlogin starts a new task. A task cannot span two zones

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.

An image is a location where packages can be installed.

An image can be one of three types:

* Full images are capable of providing a complete system.

* Partial images are linked to a full image (the parent image), but do not provide a complete system on their own.

* User images contain only relocatable packages.

You might need to replace a disk in the root pool for the following reasons:

The root pool is too small and you want to replace it with a larger disk

The root pool disk is failing. In a non-redundant pool, if the disk is failing so that the system won't boot, you'll need to boot from an alternate media, such as a CD or the network, before you replace the root pool disk.

In a mirrored root pool configuration, you might be able to attempt a disk replacement without having to boot from alternate media. You can replace a failed disk by using the zpool replace command.

Some hardware requires that you offline and unconfigure a disk before attempting the zpool replace operation to replace a failed disk.

For example:

# zpool offline rpool c1t0d0s0

# cfgadm -c unconfigure c1::dsk/c1t0d0

# cfgadm -c configure c1::dsk/c1t0d0

# zpool replace rpool c1t0d0s0

# zpool online rpool c1t0d0s0

# zpool status rpool

SPARC# installboot -F zfs /usr/platform/`uname -i`/lib/fs/zfs/bootblk /dev/rdsk/c1t0d0s0

x86# installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c1t9d0s0

When you install this Oracle Solaris release on a system for the first time, Oracle Solaris automatically provides generic link names for all the system's physical network devices. This name assignment uses the net# naming convention, where the # is the instance number. This instance number increments for each device, for example, net0, net1, net2, and so on.

Note:

Network configuration in Oracle Solaris 11 includes

* Generic datalink name assignment – Generic names are automatically assigned to datalinks using the net0, net1, netN naming convention, depending on the total number of network devices that are on the system

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.

ZFS quotas can be set and displayed by using the zfs set and zfs get commands.

We can remove the quota restriction by setting to quota to none.

How to Recreate a ZFS Root Pool and Restore Root Pool Snapshots

In this scenario, assume the following conditions:

* ZFS root pool cannot be recovered

* ZFS root pool snapshots are stored on a remote system and are shared over NFS

* The system is booted from an equivalent Solaris release to the root pool version so that the Solaris release and the pool version match. Otherwise, you will need to add the -o version=version-number property option and value when you recreate the root pool in step 4 below.

All steps below are performed on the local system.

1.

Boot from CD/DVD or the network.

On a SPARC based system, select one of the following boot methods:

ok boot net -s

ok boot cdrom -s

If you don't use -s option, you'll need to exit the installation program.

2.

Mount the remote snapshot dataset.

For example:

# mount -F nfs remote-system:/rpool/snaps /mnt

3.

Recreate the root pool.

For example:

# zpool create -f -o failmode=continue -R /a -m legacy -o cachefile=/etc/zfs/zpool.cache rpool c1t0d0s0

4.

Restore the root pool snapshots.

This step might take some time. For example:

# cat /mnt/rpool.0311 | zfs receive -Fdu rpool

Using the -u option means that the restored archive is not mounted when the zfs receive operation completes.

5.

Set the bootfs property on the root pool BE.

For example:

# zpool set bootfs=rpool/ROOT/osolBE rpool

6.

Install the boot blocks on the new disk.

On a SPARC based system:

# installboot -F zfs /usr/platform/`uname -i`/lib/fs/zfs/bootblk /dev/rdsk/c1t0d0s0

A subnetwork, or subnet, is a logically visible subdivision of an IP network. The practice of dividing a network into two or more networks is called subnetting.

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 Create an iSCSI LUN

The following steps are completed on the system that is providing the storage device.

Example: target# zpool create sanpool mirror c2t3d0 c2t4d0

(C)2. Create a ZFS volume to be used as a SCSI LUN.

(D)3. Create a LUN for the ZFS volume.

Example:

target# stmfadm create-lu /dev/zvol/rdsk/sanpool/vol1

Logical unit created: 600144F0B5418B0000004DDAC7C10001

4. Confirm that the LUN has been created.

Example

target# stmfadm list-lu

LU Name: 600144F0B5418B0000004DDAC7C10001

(F) 5. Add the LUN view.

This command makes the LUN accessible to all systems.

target# stmfadm add-view 600144F0B5418B0000004DDAC7C10001

How to Create the iSCSI Target

This procedure assumes that you are logged in to the local system will contains the iSCSI target.

Note: The stmfadm command manages SCSI LUNs. Rather than setting a special iSCSI property on the ZFS volume, create the volume and use stmfadm to create the LUN.

(H) 1. Enable the iSCSI target service.

target# svcadm enable -r svc:/network/iscsi/target:default

(I) 2. Create the iSCSI target.

target# itadm create-target

* The whoami utility displays your effective user ID as a name.

Here this would be root.

* who am i

The command who shows who is logged on.

Here this would be:

user1 console Dec 30 20:20

* The id utility displays the user and group names and numeric IDs, of the calling process, to the standard output. If the real and effective IDs are different, both are displayed, otherwise only the real ID is displayed.

Here this would be:

uid=0(root) gid=0(root)

Note:

Each UNIX proces has 3 UIDs associated to it. Superuser privilege is UID=0.

Real UID

--------

This is the UID of the user/process that created THIS process. It can be changed only if the running process has EUID=0.

Effective UID

-------------

This UID is used to evaluate privileges of the process to perform a particular action. EUID can be change either to RUID, or SUID if EUID!=0. If EUID=0, it can be changed to anything.

Saved UID

---------

If the binary image file, that was launched has a Set-UID bit on, SUID will be the UID of the owner of the file. Otherwise, SUID will be the RUID.

The fingerprints are used to guard against man in the middle attacks. Since ssh logins usually work over the internet (an insecure connection), someone could hijack your connection. When you try to log into yourmachine.com, he could get "in the middle" and return your challenge as if he was yourmachine.com. That way, he could get hold of your login password.

To make this attack harder, ssh stores the fingerprint of the server's public key on the first connection attempt. You will see a prompt like:

The authenticity of host 'eisen (137.43.366.64)' can't be established.

RSA key fingerprint is cf:55:30:31:7f:f0:c4:a0:9a:02:1d:1c:41:cf:63:cf.

Are you sure you want to continue connecting (yes/no)

When you enter yes, ssh will add the fingerprint to your known_hosts file. you will see

Code:

Warning: Permanently added 'eisen, 137.43.366.64' (RSA) to the list of known hosts.

The next time you login, ssh will check whether the host key has changed. A changing host key usually indicates a man in the middle attack, and ssh refuses to connect.

Only the loopback addresses are configured. No IP address is configured.

There are two ways to configure the network configuration: automatic or manual.

In the exhibit we see that DHCP has been used used. This indicates an automatic network configuration.

 In this Solaris release, you can use the zpool split command to split a mirrored storage pool, which detaches a disk or disks in the original mirrored pool to create another identical pool.

After the split operation, import the new pool.

The user file-creation mode mask (umask) is use to determine the file permission for newly created files. It can be used to control the default file permission for new files. It is a four-digit octal number.

You can setup umask in /etc/bashrc or /etc/profile file for all users. By default most Unix distro set it to 0022 (022) or 0002 (002).

1. The default umask 002 used for normal user. With this mask default directory permissions are 775 and default file permissions are 664.

2. The default umask for the root user is 022 result into default directory permissions are 755 and default file permissions are 644.

3. For directories, the base permissions are (rwxrwxrwx) 0777 and for files they are 0666 (rw-rw-rw).

In short,

1. A umask of 022 allows only you to write data, but anyone can read data.

2. A umask of 077 is good for a completely private system. No other user can read or write your data if umask is set to 077.

3. A umask of 002 is good when you share data with other users in the same group. Members of your group can create and modify data files; those outside your group can read data file, but cannot modify it. Set your umask to 007 to completely exclude users who are not group members.

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

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.

No OpenBoot Environment on the Intel Platform. The Intel environment has no OpenBoot PROM or NVRAM. On Intel systems, before the kernel is started, the system is controlled by the basic input/output system (BIOS), the firmware interface on a PC. Therefore, many features provided by OpenBoot are not available on Intel systems.

Note: The Open Boot PROM (OBP) bootloader only exists within SPARC. Before Solaris 10 01/06, the bootloader for Solaris x86 was a Sun customized bootstrap software. After Solaris 10 01/06, it uses GRUB, a well known bootloader that's commonly used in the Linux world.

With GRUB, it's much easier to make the system dual-boot Linux and Solaris. GRUB extends the capabilities of the bootloader that was not available previously such as the ability to boot from a USB DVD drive. Those who have used Linux will be quite familiar with GRUB and its options.

The Internet Protocol (IP) is the principal communications protocol in the Internet protocol suite for relaying datagrams across network boundaries. Its routing function enables internetworking, and essentially establishes the Internet.

FLAGS

Indicates the status of each underlying interface, which can be one or any combination of the following:

(D) d indicates that the interface is down and therefore unusable.

(E) M indicates that the interface is designated by the system to send and receive IPv6 multicast traffic for the IPMP group.

Note:

i indicates that the INACTIVE flag is set for the interface. Therefore, the interface is not used to send or receive data traffic.

s indicates that the interface is configured to be a standby interface.

m indicates that the interface is designated by the system to send and receive IPv4 multicast traffic for the IPMP group.

b indicates that the interface is designated by the system to receive broadcast traffic for the IPMP group.

h indicates that the interface shares a duplicate physical hardware address with another interface and has been taken offline. The h flag indicates that the interface is unusable.

Image Packaging System (IPS) is a new network based package management system included in Oracle Solaris 11. It provides a framework for complete software lifecycle management such as installation, upgrade and removal of software packages. IPS also enables you to create your own software packages, create and manage package repositories, and mirror existing package repositories.

Oracle Solaris software is distributed in IPS packages. IPS packages are stored in IPS package repositories, which are populated by IPS publishers.

E: The following command displays property information about the local repository.

$ pkgrepo get -s /export/repoSolaris11

SECTION PROPERTY VALUE publisher prefix solaris repository description This\ repository\ serves\ a\ copy\ of\ the\ Oracle\ Solaris\ 11\ Build\ 175b\ Package\ Repository.

repository name Oracle\ Solaris\ 11\ Build\ 175b\ Package\ Repository

repository version 4

The value of the publisher prefix specifies that solaris is to be used in the following cases:

When more than one publisher's packages are present and no publisher is specified in the package name in the pkg command

When packages are published to the repository and no publisher is specified.

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# ~.

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

The prctl utility allows the examination and modification of the resource controls associated with an active process, task, or project on the system. It allows access to the basic and privileged limits and the current usage on the specified entity.

How to Change the zone.cpu-shares Value in a Zone Dynamically

This procedure can be used in the global zone or in a non-global zone.

For more information about roles, see Configuring and Using RBAC (Task Map) in System Administration Guide: Security Services.

# prctl -n zone.cpu-shares -r -v value -i zone zonename

idtype is either the zonename or the zoneid. value is the new value.

Note: project.cpu-shares

Number of CPU shares granted to a project for use with the fair share scheduler