Note:

*Immutable Zones provide read-only file system profiles for solaris non-global zones.

*A zone with a read-only zone root is called an Immutable Zone. A solaris Immutable Zone preserves the zone's configuration by implementing read-only root file systems for non-global zones. This zone extends the zones secure runtime boundary by adding additional restrictions to the runtime environment. Unless performed as specific maintenance operations, modifications to system binaries or system configurations are blocked.

*vnic-link

A virtual network interface created on a link or an etherstub. It is a pseudo device that can be treated as if it were an network interface card on a machine.

*vlan-link

A VLAN datalink.

*bridge

A bridge instance, identified by an administratively-chosen name. The name may use any alphanumeric characters or the underscore, _, but must start and end with an alphabetic character. A bridge name can be at most 31 characters. The name default is reserved, as are all names starting with SUNW.

Note:

*dladm– administer data links

*The dladm command is used to administer data-links. A data-link is represented in the system as a STREAMS DLPI (v2) interface which can be plumbed under protocol stacks such as TCP/IP. Each data-link relies on either a single network device or an aggregation of devices to send packets to or receive packets from a network.

Each dladm subcommand operates on one of the following objects:

link

A datalink, identified by a name. In general, the name can use any alphanumeric characters (or the underscore, _), but must start with an alphabetic character and end with a number. A datalink name can be at most 31 characters, and the ending number must be between 0 and 4294967294 (inclusive). The ending number must not begin with a zero. Datalink names between 3 and 8 characters are recommended.

Some subcommands operate only on certain types or classes of datalinks. For those cases, the following object names are used:

phys-link

A physical datalink.

vlan-link

A VLAN datalink.

aggr-link

An aggregation datalink (or a key; see NOTES).

ether-link

A physical Ethernet datalink.

wifi-link

A WiFi datalink.

vnic-link

A virtual network interface created on a link or an etherstub. It is a pseudo device that can be treated as if it were an network interface card on a machine.

iptun-link

An IP tunnel link.

dev

A network device, identified by concatenation of a driver name and an instance number.

etherstub

An Ethernet stub can be used instead of a physical NIC to create VNICs. VNICs created on an etherstub will appear to be connected through a virtual switch, allowing complete virtual networks to be built without physical hardware.

bridge

A bridge instance, identified by an administratively-chosen name. The name may use any alphanumeric characters or the underscore, _, but must start and end with an alphabetic character. A bridge name can be at most 31 characters. The name default is reserved, as are all names starting with SUNW.

Note that appending a zero (0) to a bridge name produces a valid link name, used for observability.

secobj

A secure object, identified by an administratively-chosen name. The name can use any alphanumeric characters, as well as underscore (_), period (.), and hyphen (-). A secure object name can be at most 32 characters.

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.

You can use the beadm utility to create and manage snapshots and clones of your boot environments.

Note:The following distinctions relevant to boot environment administration:

A snapshot is a read-only image of a dataset or boot environment at a given point in time. A snapshot is not bootable.

A boot environment is a bootable Oracle Solaris environment, consisting of a root dataset and, optionally, other datasets mounted underneath it. Exactly one boot environment can be active at a time.

A clone of a boot environment is created by copying another boot environment. A clone is bootable.

B:

*With Oracle Solaris 11, the configuration of the system is specified as a set of configuration parameters provided in a file called the System Configuration Profile, which is in the form of an SMF profile.

*Oracle Solaris 11 uses SMF for configuration. SMF uses a database to centralize the configuration information, it uses the SMF framework to carry out configuration tasks, and it uses SMF properties as an API. SMF is also well integrated with Oracle Solaris Zones technology.

*Oracle Solaris 11 uses the Service Management Facility (SMF) to centralize configuration information. The new sysconfig command replaces the older sys-unconfig command and provides a method based upon SMF for unconfiguring an Oracle Solaris 11 instance and reconfiguring it.

D:To use AI to install client systems over the network, you must set up DHCP and set up an AI service on an AI server.

An AI service is associated with a SPARC or x86 AI install image and one or more sets of installation instructions. 

Note:

Using the Oracle Solaris Automated Installer (AI) you can create and manage services to install the Oracle Solaris 11 operating system over the network in a hands-off manner.

Three significant steps are performed by various services during the installation process:

Assigning a network identity for the system being installed

Contacting the automated installation service to download over the network a small boot image and a description of how to provision a system

Provisioning the system over the network, including software and system configuration

Each of the steps can be performed by various services residing on the same physical or virtual system, or the services can be on separate systems. In this article, the following services reside on the same system:

DHCP service

Automated Installer service

Image Packaging System (IPS) repository service

A:ZFS is the default root file system.

UFS is a supported legacy file system, but it is not supported as a bootable root file system.

E:

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:

*Starting with the Solaris 10 10/08 release for a SPARC based system, you can boot a ZFS root file system in a ZFS pool. For ZFS root pools, you can list the available boot environments withthe boot command with the -L option. You can then choose a boot environment and use the OBP boot command with the -Z option to boot that boot environment.

*Starting with the Solaris 10 1/06 release for x86 based systems, a GRUB boot menu provides the interface for booting between different boot environments.

Note:

*The name originally stood for "Zettabyte File System"but today does not stand for anything.

Incorrect:

Not C: Mirroring is not enabled by default.

Not D:Alternate bootenvironments

If you want to create a backup of an existing boot environment, for example, prior to modifying the original boot environment, you can use the beadm command to create and mount a new boot environment that is a clone of your active boot environment. This clone is listed as an alternate boot environment in the GRUB menu for x86 systems or in the boot menu for SPARC systems.

Version5.1.37-0.1/4 is installed(see note 1 below) and this version can be updated (see note 2 below).

Note:

* 1The “i” in the I column indicates that these packages are installed in this image.

2An “f” in the F column indicates the package is frozen. If a package is frozen, you can only install or update to packages that match the frozen version.

*The pkg list command tells you whether a package is installed in the current image and whether an update is available. With no options or operands, this command lists all packages that are installed in the current image. To narrow your results, provide one or more package names. You can use wildcards in the package names. Package variants for an architecture or zone type that does not match this image are not listed.