1z0-580 Questions and Answers

*WAN boot

SPARC clients of AI installation over the network must support WAN boot.

To boot over the network, AI requires WAN boot support for SPARC clients. You can check whether your client Open Boot PROM (OBP) supports WAN boot by checking whether network-boot-arguments is a valid variable that can be set in the eeprom.

If the variable network-boot-arguments is displayed, or if the command returns the output network-boot-arguments: data not available, the OBP supports WAN boot and the client can be installed over the network.

*The following command shows how to check the client OBP for WAN boot support.

# eeprom | grep network-boot-arguments

network-boot-arguments: data not available

In this example, the output network-boot-arguments: data not available indicates that the client OBP supports WAN boot.

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.

How to Install Oracle Solaris From the Live Media If Your System Boots in Console Mode

For this procedure, two networked systems are required: the system on which the Live Media was booted (target system) and a remote system from which the installation will be performed. Both systems must have network access. The two systems are not required to be on the same subnet. However, the target system must be reachable from the remote system. Also, the remote system must be running an OS that supports a graphical desktop.

Note:

*If your system's graphics card is not supported by the Live Media or your system does not have a graphics card, the system boots in console mode when you insert the Live Media. In this case, you cannot perform a GUI installation.

Your two alternatives are as follows:

• Use the text installer image instead of the Live Media ISO image.

You can run the text installer on the local console without network access.

• Perform a remote installation

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

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

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.