AD: Manifests from the standard directory trees /lib/svc/manifest and /var/svc/manifest are processed during system boot and anytime an administrator or program runs:

$ svcadm restart manifest-import

C: svccfg

apply subcommand

If the argument is a service profile or manifest, apply the configuration to the admin layer of the SMF repository. Services, instances, property groups, and properties will be created as necessary.

E: import [-V] [file | directory]

svccfg import on a file in a system-managed filesystem location (subdirectories of /lib/svc/manifest and /var/svc/manifest) invokes: svcadm restart manifest-import.

Placing your manifests in a system-managed location and invoking svcadm restart manifest-import to import them is the recommended practice.

svccfg import on files in other locations imports their properties as administrative customization into the admin layer. It is equivalent to:

svccfg apply [file | directory]

Incorrect:

not B: Manifests are processed in two different phases during boot.

The service svc:/system/early-manifest-import:default, a pseudo service, is responsible for the first manifest processing. This service processes only manifests from the /lib/svc/manifest directory tree before svc.startd(1M) initializes any services thus enabling services delivered in /lib/svc/manifest to always start with their most updated definition. Since this is a pseudo service, svcadm(1M) commands are ignored though svcs(1) can be used to observe status and get log file information.

The svc:/system/manifest-import:default service handles the second manifest processing and imports manifest files from both /lib/svc/manifest and /var/svc/manifest directory trees, in that respective order.

A: The audit_remote plugin is loaded by auditd if the plugin is configured as an active via auditconfig. Use the auditconfig -setplugin option to change all the plugin related configuration parameters

B: The solaris-audit service port assigned by IANA is 16162.

Incorrect:

Not D: audit_remote authenticates itself to the remote audit service by way of GSS-API (libgss(3LIB)). Default gss credentials are used as provided by the gss implementation mechanism, such as Kerberos.

Note: audit_remote

- send Solaris audit logs to a remote server

A: The pkd.depotd service is managed by SMF under the service identifier svc:/application/pkg/server.

D:

* Example:

Configure pkg.depotd to provide remote access. pkg.depotd provides an HTTP interface to a pkg repo. Here we are going to make the repo server listen on port 10000, and use the repo dir we created as its default.

# svcadm disable pkg/server

# svccfg -s pkg/server setprop pkg/inst_root = /data/myrepo

# svccfg -s pkg/server setprop pkg/port = 10000

# svcadm refresh pkg/server

# svcadm enable pkg/server

* pkg.depotd is the depot server for the image packaging system. It provides network access to the data contained within a package repository. Clients that do not support direct access to a repository through the file system, or for which network access is the only available or preferred method of transport, typically use the package depot.

B: Link aggregations provide high availability and higher throughput by aggregating multiple interfaces at the MAC layer. IP Multipathing (IPMP) provides features such as higher availability at the IP layer. Both IPMP and Link Aggregation are based on the grouping of network interfaces, and some of their features overlap, such as higher availability. These technologies are however implemented at different layers of the stack, and have different strengths and weaknesses.

E: Internet Protocol Network Multipathing (IPMP) provides fault-tolerance and load balancing across multiple network interface cards. By using IPMP, you can configure one or more interfaces into an IP multipathing group. After configuring IPMP, the system automatically monitors the interfaces in the IPMP group for failure. If an interface in the group fails or is removed for maintenance, IPMP automatically migrates, or fails over, the failed interface's IP addresses

Incorrect:

Not A: The same (non-null) character string IPMP group name identifies all interfaces in the group. You can place interfaces from NICs of different speeds within the same IPMP group, as long as the NICs are of the same type.

Not C:If LACP (Link Aggregation Control Protocol) cannot aggregate all the ports that are compatible (for example, the remote system might have more restrictive hardware limitations), then all the ports that cannot be actively included in the channel are put in hot standby state and are used only if one of the channeled ports fails.

Not D: MP is built into Oracle Solaris and does not require any special hardware. Any interface that is supported by Oracle Solaris can be used with IPMP. However, IPMP does impose the following requirements on your network configuration and topology:

/All interfaces in an IPMP group must have unique MAC addresses.

/ All interfaces in an IPMP group must be of the same media type.

/ All interfaces in an IPMP group must be on the same IP link

http://illumos.org/msg/SMF-8000-MY

Use one of the following methods to restart the depot server process:

B: Use svcadm(1M) to restart the application/pkg/server instance.

C: Send a SIGUSR1 signal to the depot server process using kill(1). This executes a “graceful restart” that leaves the process intact but reloads all configuration, package, and search data:

# kill -USR1 pid

Note:

* The pkd.depotd service is managed by SMF under the service identifier svc:/application/pkg/server.

An interface that has been created cannot become a member of an aggregation.