Interfaces that are on the IP layer (Layer 3) are configured by using the ipadm command.

Recommended best practice is to create a separate ZFS file system for your local package repository. Using a separate ZFS file system enables you to take advantage of the following benefits:

Achieve better performance.

Set separate file system characteristics.

Directly snapshot and recover specified file systems.

If one system hosts more than one IPS repository, make each repository a separate ZFS file system so that you can rollback and recover each repository separately.

B: The disk intended for the root pool must have an SMI label. Otherwise, the installation will fail.

D: The default target location for the installation is the first disk found on each client that meets the size requirement. If the size of a disk is greater than or equal to the recommended size, the installer selects that disk as the installation target. If the size of the disk is less than the recommended size, the installer checks the next disk. If no disk is found that meets the size requirement, the automated installation fails for that client.

Note:

* If you do not specify a target location on a client for installing the Oracle Solaris OS, AI selects a default target.

Incorrect:

not A: < swap >   and   < dump >   – Optional. You can use AI to configure swap and dump during the automated install.

Not C: A mirrored dataset for the root pool is not required.

You can display information about snapshots, boot environments, and datasets that were created by the beadm command by using the beadm list subcommand. The beadm list command output also displays boot environments that are created by the pkg command.

Viewing Boot Environment Specifications

The values for the Active column are as follows:

R   – Active on reboot.

N   – Active now.

NR   – Active now and active on reboot.

“-”   – Inactive.

“!”   – Unbootable boot environments in a non-global zone are represented by an exclamation point.

The following example displays full information for the   BE5   boot environment.

C: When you assign a network to a global zone, you must define the mode of the network, either Shared IP or Exclusive IP:

In Shared IP mode, the network interface is used by more than one zone. You define the network interface when you you assign the global zone to the network.

In Exclusive IP mode, the network interface is dedicated to the zone. An exclusive network must be declared for the global zone when you assign network to the global zone. Then you configure the IP configuration for the non-global zone.

Not B: There is no command dladm disable to disable a network interface.

Not D: There is no command netconfig disable to disable a network interface.

A:

* If your system has more than one OS installed on the system or more than one root boot environment in a ZFS root pool, you can boot from these boot environments for both SPARC and x86 platforms.

* GRUB, the open source boot loader, is the default boot loader in the Solaris OS.

C: With GRUB based booting, the kernel is loaded by specifying its file name, and the drive, and the partition where the kernel resides. GRUB based booting replaces the Solaris Device Configuration Assistant and simplifies the booting process with a GRUB menu.

Incorrect:

Not E:

* In this implementation of GRUB, the multiboot module is no longer used.

Running a Custom Script During First Boot

To perform any additional installation or configuration that cannot be done in the AI manifest or in a system configuration profile, you can create a script that is executed at first boot by a run-once SMF service.

Create the first-boot script.

Create the manifest for an SMF service that runs once at first boot and executes the script.

Create an IPS package that contains the service manifest and the script.

Add the package to an IPS package repository.

Install that package during the AI installation by specifying that package in the AI manifest.

The service runs and executes the script at first reboot after the AI installation.

Incorrect:

not A: IPS relies on network-accessible or locally available software repositories as a delivery

mechanism, which is similar to how other operating systems (notably Oracle Linux) supply

software updates.

not D: can be done with the pkg command.

Note:

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

Safe system upgrades with ZFS boot environments

Network package repositories of software

Efficient downloads and automatic dependency checking

Support for disconnected data center environments

Extensive package publishing tools

The following table lists different tasks for planning the network configuration.

* (A) Identify the hardware requirements of your planned network topology.

Determine the types of equipment that you need for your network site.

*(C) Determine the type of IP addresses to use and obtain registered IP addresses.

Select whether you are deploying a purely IPv4 network, an IPv6 network, or a network that uses both types of IP addresses. Obtain unique IP addresses to communicate to public networks in the Internet.

* (D) Determine a naming scheme to identify the hosts in the network as well as the name service to use.

Create a list of names to assign to the systems on the network and decide whether to use NIS, LDAP, DNS, or the network databases in the local   /etc   directory.

* If necessary, establish administrative subdivisions and design a strategy for subnets.

Decide if your site requires that you divide your network into subnets to service administrative subdivisions

* Determine where to place routers in the network design.

If your network is large enough to require routers, create a network topology that supports them.

* Decide whether to create virtual networks in the overall network configuration scheme.

You might need to create virtual networks within a system to reduce the hardware footprint of your network.