1z0-580 Oracle Solaris 11 Installation and Configuration Essentials Questions and Answers

TFTP Error or System Hangs After GATEWAY Message

The DHCP server provides an IP address and a location of the initial boot program as part of the DHCP response.

If the boot program does not exist, then the AI client boot cannot proceed. The following message is displayed:

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

CLIENT IP: 10.6.68.29 MASK: 255.255.255.0 DHCP IP: 10.6.68.49

GATEWAY: 10.6.68.1

TFTP.

PXE-T02: Access Violation

PXE-E3C: TFTP Error - Access violation

PXE-MOF: Exiting Intel Boot Agent

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

Oracle Cloud Infrastructure

Overview

*Flexible cloud infrastructure supports dynamic resource pooling, elastic scalability, and rapid application deployment

*Includes Oracle Enterprise Manager, a complete cloud lifecycle management solution that allows you to quickly set up, manage, and support enterprise clouds and traditional Oracle IT environments from applications to disk

*Built-in security and high availability

*Application-aware virtualization and management capabilities

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

There are no upgrade methods or tools available to transition from Oracle Solaris 10 to Oracle Solaris 11. You cannot use an installer to upgrade from Oracle Solaris 10 to Oracle Solaris 11.

Oracle Solaris 11 Transition Tools and Features

Note:

*There are no upgrade methods or tools available to transition from Oracle Solaris 10 to Oracle Solaris 11. You cannot use an installer to upgrade from Oracle Solaris 10 to Oracle Solaris 11.

/JumpStart Migration Utility (js2ai)

Used to convert Oracle Solaris 10 JumpStart rules and profiles to a format that is compatible with AI manifest entries.

/ZFS shadow migration feature

Used to migrate data from an existing file system to a new file system.

/Oracle Solaris 11 support for Oracle Solaris 10 zones

Used to migrate your Oracle Solaris 10 application environments to an Oracle Solaris 11 system.

/NFS file sharing and pool migration

Used to access shared files from an Oracle Solaris 10 system on an Oracle Solaris 11 system.

Used to import a ZFS storage pool from an Oracle Solaris 10 system into an Oracle Solaris 11 system.

TheJumpStart Migration Utility (js2ai)is used to convert Oracle Solaris 10 JumpStart rules and profiles to a format that is compatible with AI manifest entries.

Note:

*There are no upgrade methods or tools available to transition from Oracle Solaris 10 to Oracle Solaris 11. You cannot use an installer to upgrade from Oracle Solaris 10 to Oracle Solaris 11. You must perform a fresh installation of Oracle Solaris 11.

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

'stamf' doesn't match any instances

Note:

*Enabling the COMSTAR service

COMSTAR runs as a SMF-managed service and enabling is no different than usual. First of all, check if the service is running:

# svcs \*stmf\*

STATE STIME FMRI

disabled 11:12:50 svc:/system/stmf:default

If the service is disable, enable it:

# svcadm enable svc:/system/stmf:default

After that, check that the service is up and running:

# svcs \*stmf\*

STATE STIME FMRI

online 11:12:50 svc:/system/stmf:default

# stmfadm list-state

Operational Status: online

Config Status : initialized

ALUA Status : disabled

ALUA Node : 0