You are setting up a local IPS package repository on your Oracle Solaris11 server: solaris.example.com.
You want to point the existing local IPS publisher to the new local IPS repository located in
/repo.
These are the stops that you have followed:
1. Download and rsync the contents of the Oracle Solaris11 repository ISO image to the
/repo directory.
2. Configure the repository server service properties. The svcprop command display, the IPS related properties:
pkg/inst_root astring/repo pkg/readonly Boolean true
The 1s command displays the contents of the /repo directory:
#ls/repo
Pkg5.repository publisher
The svcs publisher command shows the svc: /application/pkg/server: default service is online.
The pkg publisher command shows the svc: /application/pkg/server: default service is online.
The pkg publisher command still displays: PUBLISHERTYPESTATUSURI
solarisoriginonlinehttp://pkg.oracle.com/solaris/release/
Which steps needs to be performed to set the local IPS publisher to the local IPS repository/repo?

Correct Answer:C
Set the Publisher Origin To the File Repository URI
To enable client systems to get packages from your local file repository, you need to reset the origin for the solaris publisher. Execute the following command on each client:
Example:
# pkg set-publisher -G '*' -M '*' -g /net/host1/export/repoSolaris11/ solaris

You have a user that needs to use the cron tool to schedule some repetitive tasks. When the user enters the crontab –e command in a terminal window, the following error appears:
crontab: you are not authorized to use cron. Sorry
In order to troubleshoot this issue, in what directory would you start your invest

Correct Answer:A
crontab: you are not authorized to use cron. Sorry.
This message means that either the user is not listed in the cron.allow file (if the file exists), or the user is listed in the cron.deny file.
You can control access to the crontab command by using two files in the /etc/cron.d directory: cron.deny and cron.allow. These files permit only specified users to perform crontab command tasks such as creating, editing, displaying, or removing their own crontab files.
The cron.deny and cron.allow files consist of a list of user names, one user name per line.

You are attempting to troubleshoot an event that should have made an entry into the messages log. This event happened about two weeks ago. Which file should you look at
first?

Correct Answer:A
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

Identify the Automated Installer’s (AI) equivalent to jumpStart’s finish scripts and sysidcfg files.

Correct Answer:B
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.

You notice that the /var/.dm/messages file has become very large. Typically, this is managed by a crontab entry. Which entry should be in the root's crontab file?

Correct Answer:B
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

You need to set up an Oracle Solaris 11 host as an iSCSI target so that the host's disk can be accessed over a storage network. The disk device is c3t4d0.
Which six options describe the steps that need to be taken on this host to enable an iSCSI target?

Correct Answer:BCDFHI
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