Oracle 1z0-821 Exam Success: Oracle Solaris 11 System Administration Complete Study and Preparation Tips

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

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

Note: # route -p add -host destination-IP gateway-IP -static

where destination-IP and gateway-IP are IPv4 addresses of the host to be used as a target. 

For example, you would type the following to specify the target system 192.168.10.137, which is on the same subnet as the interfaces in IPMP group itops0:

$ route -p add -host 192.168.10.137 192.168.10.137 -static

This new route will be automatically configured every time the system is restarted. If you want to define only a temporary route to a target system for probe-based failure detection, then do not use the -p option.

Oracle Solaris 11 uses Automated Installer (AI) for unattended installations.

Unattended installations are possible by placing the contents of the AI Image media (or ISO image contents from a download) on an AI server.

If you're logged on to the system, you can run prstat -Z to generate a summary of cpu/memory utilization by zone.

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

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

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.

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.