A snapshot is a read-only point-in-time copy of a file system. The copy-on-write design

of ZFS makes them essentially “free” - They are space efficient and instantaneous, providing an invaluable part of backup strategies and synchronizing data between systems.

Incorrect:

Incorrect:

Not A: A ZFS vdev (aka "virtual device") is either:

a single disk, or

two or more disks that are mirrored, or

a group of disks that are organized using RAID-Z.

There are also special kinds of vdevs like hot-spares, ZIL or cache devices, etc.

Not D:

Clones are writeable snapshots, ideal for storing many private

copies of shared data for operations such as data migration, test

and development, or backup.

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 with the 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 boot environments

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.

Note:

* virtual local area networks (VLANs), link aggregations, and IP tunnels can be assigned administratively-chosen names and then configured by referring to those names.

* VNICs are pseudo interfaces that you create on top of datalinks. A VNIC has an automatically generated MAC address. Depending on the network interface in use, you can explicitly assign to a VNIC a MAC address other than the default address, as described in the dladm(1M) man page. You can create as many VNICs over a datalink as you require.

* Etherstubs are pseudo ethernet NICs which are managed by the system administrator. You can create VNICs over etherstubs instead of over physical links. VNICs over an etherstub become independent of the physical NICs in the system. With etherstubs, you can construct a private virtual network that is isolated both from the other virtual networks in the system and from the external network. For example, you want to create a network environment whose access is limited only to your company developers than to the network at large. Etherstubs can be used to create such an environment.

* The basic link aggregation topology involves a single aggregation that contains a set of physical interfaces. You might use the basic link aggregation in the following situations:

For systems that run an application with distributed heavy traffic, you can dedicate an aggregation to that application's traffic.

For sites with limited IP address space that nevertheless require large amounts of bandwidth, you need only one IP address for a large aggregation of interfaces.

For sites that need to hide the existence of internal interfaces, the IP address of the aggregation hides its interfaces from external applications.

B: Example: Creating a Policy Around a Mission-Critical Port

The command below creates a policy around inbound HTTPS traffic on an HTTPS server so that HTTPS obtains dedicated NIC hardware and kernel TCP/IP resources. The name specified, https-1, can be used later to modify or delete the policy.

# flowadm add-flow -l bge0 -a transport=TCP,local_port=443 https-1

# flowadm show-flow -l bge0

FLOW LINK IP ADDR PROTO PORT RPORT DSFLD

https1 bge0 -- tcp 443 -- --

C:

Note:

* Flow Restrictions Per Zone

Within a zone, no two flows can have the same name. After adding a flow with the link specified, the link will not be required for display, modification, or deletion of the flow.

Incorrect:

Not A: Flow Properties

The following flow properties are supported. Note that the ability to set a given property to a given value depends on the driver and hardware.

maxbw

Sets the full duplex bandwidth for the flow. The bandwidth is specified as an integer with one of the scale suffixes(K, M, or G for Kbps, Mbps, and Gbps). If no units are specified, the input value will be read as Mbps. The default is no bandwidth limit.

priority

Sets the relative priority for the flow. The value can be given as one of the tokens high, medium, or low. The default is medium.

Not D: The following types of combinations of attributes are supported:

local_ip[/prefixlen]=address

remote_ip[/prefixlen]=address

transport={tcp|udp|sctp|icmp|icmpv6}

transport={tcp|udp|sctp},local_port=port

transport={tcp|udp|sctp},remote_port=port

dsfield=val[:dsfield_mask]

On a given link, the combinations above are mutually exclusive. An attempt to create flows of different combinations will fail.

Note: Flow Attributes

The flow operand that identify a flow in a flowadm command is a comma-separated list of one or more keyword, value pairs from the list below.

local_ip [ / prefix_len ]

remote_ip [ / prefix_len ]

transport ={ tcp | udp | sctp | icmp | icmpv6 }

local_port

Identifies a service specified by the local port.

remote_port

Identifies a service specified by the remote port.

dsfield [ : dsfield_mask ]

Not E:

* flowstat

- report flow statistics

* The flowstat command reports run time statistics about user defined flows. flowadm show-flow provides the flow name information for this command.

* flowstat [-r | -t] [-i interval] [-l link] [flow]

This form of the command iteratively examines all flows and reports statistics. The output is sorted in descending order of flow utilization. If no flow is specified, the system displays statistics for all flows.

-r

Display receive-side statistics only. Includes bytes and packets received, drops, and so forth.

-t

Display transmit-side statistics only. Includes bytes and packets sent, drops, and so forth.

-i interval

Specify an interval in seconds at which statistics are refreshed. The default interval is one second.

-l link | flow]

Display statistics for all flows on the specified link or statistics for the specified flow.

No DHCP or Proxy DHCP Offers Were Received

If a DHCP server is not responding to an x86 client's request, you see the following messages:

Intel(R) Boot Agent PXE Base Code (PXE-2.1 build 0.86)

Copyright(C) 1997-2007, Intel Corporation

CLIENT MAC ADDR 00 14 4F 29 04 12 GUID FF2000008 FFFF FFFF FFFF 7BDA264F1400

DHCP......... No DHCP or ProxyDHCP offers were received

PXE-MOF: Exiting Intel Boot Agent

The timeout message indicates that the client is sending a DHCP request and not getting a response. This issue is probably due to an error in the DHCP configuration. Check to see if your client is configured correctly in the DHCP server.

A: project.cpu-shares

Number of CPU shares granted to this project for use with the fair share scheduler

B: project.cpu-cap

Absolute limit on the amount of CPU resources that can be consumed by a project. A value of 100 means 100% of one CPU as the project.cpu-cap setting. A value of 125 is 125%, because 100% corresponds to one full CPU on the system when using CPU caps.

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

As per exhibit these are the two files in the netboot directory.

Note:

*Missing argument is:

file=wanbootCGI-URL

Specifies the URL of the wanboot-cgi program on the web server

* During the installation, WAN boot refers to the contents of the /etc/netboot hierarchy on the web server for instructions about how to perform the installation. This directory contains the configuration information, private key, digital certificate, and certificate authority required for a WAN boot installation. During the installation, the wanboot-cgi program converts this information into the WAN boot file system. The wanboot-cgi program then transmits the WAN boot file system to the client.

E:

* Many configuration tasks around name services have moved into the SMF in Solaris 11.

* The Service Management Facility (SMF), first introduced in Oracle Solaris 10, is a feature of the operating system for managing system and application services, and it replaces the legacy init scripting start-up mechanism common to prior releases of Oracle Solaris and other UNIX operating systems. SMF improves the availability of a system by ensuring that essential system and application services run continuously even in the event of any hardware or software failures. SMF is one of the components of the wider Oracle Solaris Predictive Self Healing capability.

Note:

* In Oracle Solaris 11, certain aspects of system configuration have changed, including the migration of several system, network, and naming services configuration to SMF.

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.

The beadm list command syntax is:

Syntax: beadm list [-a | [-ds] [-H] [BeName]

The command lists information about the existing boot environment. To view information for a specific boot environment, replace BeName with a boot environment name. If a specific boot environment is not specified, the command lists information about all boot environments. The default is to list boot environments without additional information.

-a – Lists all available information about the boot environment. This information includes subordinate datasets and snapshots.

-d – Lists information about all subordinate datasets that belong to the boot environment.

-s – Lists information about the snapshots of the boot environment.

-H – Prevents listing header information. Each field in the output is separated by a semicolon.