Practice Free 1z0-580 Oracle Solaris 11 Installation and Configuration Essentials Exam Questions Answers With Explanation

Use the pkg revert command to restore files to their as-delivered condition.

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]

NotE:

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

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 disableto disable a network interface.

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

How to Use DTracein a Non-global Zone

• Use the zonecfg limitpriv property to add the dtrace_proc and dtrace_user privileges.

global# zonecfg -z my-zone

zonecfg:my-zone> set limitpriv="default,dtrace_proc,dtrace_user"

zonecfg:my-zone> exit

Note –

Depending on your requirements, you can add either privilege, or both privileges.

• Boot the zone.

• global# zoneadm -z my-zone boot

Log in to the zone.

global# zlogin my-zone

• Run the DTrace program.

my-zone# dtrace -l

Note:

*Oracle Solaris DTrace is a comprehensive, advanced tracing tool for troubleshooting systemic problems in real time.

*DTrace helps you understand a software system by enabling you to dynamically modify the operating system kernel and user processes to record additional data that you specify at locations of interest, called probes.

B:This example shows how to create a DLMP aggregation. The aggregation has three underlying datalinks.

# dladm create-aggr -m haonly -l net0 -l net1 -l net2 aggr0

# dladm show-link

LINK CLASS MTU STATE BRIDGE OVER

net0 phys 1500 up -- ----

net1 phys 1500 up -- ----

net2 phys 1500 up -- ----

aggr0 aggr 1500 up -- net0, net1, net2

# dladm show-aggr

LINK MODE POLICY ADDRPOLICY LACPACTIVITY LACPTIMER

aggr0 haonly --

E:Check the status of the aggregation you just created.

# dladm show-aggr

The aggregation's state should be UP.

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.

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.

B(not C):A zone is a virtualized operating system environment that is created within a single instance of the Oracle Solaris operating system. Oracle Solaris Zones are a partitioning technology that provides an isolated, secure environment for applications.

Note:

*When you create a zone, you produce an application execution environment in which processes are isolated from the rest of the system. This isolation prevents a process that is running in one zone from monitoring or affecting processes that are running in other zones. Even a process running with root credentials cannot view or affect activity in other zones. A zone also provides an abstract layer that separates applications from the physical attributes of the machine on which the zone is deployed. Examples of these attributes include physical device paths and network interface names. The default non-global zone brand in the Oracle Solaris 11.1 release is the solariszone.

By default, all systems have a global zone. The global zone has a global view of the Oracle Solaris environment that is similar to the superuser (root) model. All other zones are referred to as non-global zones. A non-global zone is analogous to an unprivileged user in the superuser model. Processes in non-global zones can control only the processes and files within that zone. Typically, system administration work is mainly performed in the global zone. In rare cases where a system administrator needs to be isolated, privileged applications can be used in a non-global zone. In general, though, resource management activities take place in the global zone.

auto_reboot – Optional. Omitting the auto_reboot attribute is equivalent to setting the value of the attribute to false. By default, AI does not automatically reboot the client after installation. To request automatic reboot of the client after successful installation, specify auto_reboot="true".

Note:

*Example 1 Set the auto_reboot Attribute

$ aimanifest set /auto_install/ai_instance@auto_reboot false

Note:

* second line in exhibit (minor typo):

boot-device = disk net

*The line starting with net is:

/pci@780/pci@0/pci@1/network@0

*Booting a system using the none milestone can be very useful for debugging startup problems. There is no equivalent run level to the none milestone.

*If problems with starting services occur, sometimes a system will hang during the boot. This procedure shows how to troubleshoot this problem.

2.Boot without starting any services.

This command instructs the svc.startd daemon to temporarily disable all services and start sulogin on the console.

ok boot -m milestone=none

2.Log in to the system as root.

3.Enable all services.

# svcadm milestone all

4.Determine where the boot process is hanging.

When the boot process hangs, determine which services are not running by running svcs -a. Look for error messages in the log files in /var/svc/log.

• After fixing the problems, verify that all services have started.

Verify that all needed services are online.

# svcs -x

Verify that the console-login service dependencies are satisfied.

This command verifies that the login process on the console will run.

# svcs -l system/console-login:default

6.Continue the normal booting process.

Storage

ZFS is the root file system on Oracle Solaris 11 offering a superior experience in terms of

manageability, scalability and data integrity. ZFS presents a pooled storage model that

completely eliminates the concept of volumes and the associated problems of partitions,

provisioning, wasted bandwidth and stranded storage. Thousands of file systems can draw

from a common storage pool, each one consuming only as much space as it actually needs. All

operations are copy-on-write transactions ensuring that the on-disk state is always valid.

Incorrect:

Not A:Network Auto-Magic(NWAM)is a project to simplify and automate network configuration on Solaris. Network Auto-Magic generally refers to Network Profiles, which allow users to specify various network configurations to be created depending on the current network conditions. The Service Discovery project, which incorporates Multicast DNS into Solaris, also fell under the Network Auto-Magic umbrella.

Not B:Pre-Flight Checker tool which can be used to check whether apps will work without modification on Solaris 11

Not C:Network Auto-Magic is a project to simplify and automate network configuration on Solaris. Network Auto-Magic generally refers to Network Profiles, which allow users to specify various network configurations to be created depending on the current network conditions. The Service Discovery project, which incorporates Multicast DNS into Solaris, also fell under the Network Auto-Magic umbrella.

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

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.

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

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:

NotE:

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

Note:

Not A:

* Jumpstart Profiles and Rules would have to be converted to be used in Automated Installer.

Use the js2ai utility with the -r option to convert both JumpStart rules and their associated profiles to AI criteria and manifests.

*Both Solaris Custom JumpStart and Oracle Solaris Automated Installer (AI) provide hands-free installation of multiple systems on a network. Clients are booted over the network, and once the client is booted, the installer takes over.