In this practice, you configure the AI server to automatically install an Oracle Solaris 11 desktop client on the network using the AI default settings.

Oracle Solaris 11 provides DTrace for dynamically tracing systemic problems in real time. It is designed to quickly identify the root cause of system performance problems. This demonstration illustrates the use of DTrace to examine slow throughput of an application on a system.

This demonstration offers an example of the required Oracle Solaris 11 OS configuration for Oracle RAC Database install. An assumption is made that the Grid Infrastructure and the Clusterware is pre-configured with two nodes. The OS configuration and the Oracle Universal Installer (OUI) steps are shown to include all the required steps before the actual database install. The demonstration includes step-by-step walkthroughs of each task associated with the RAC Database install.

In this practice you work with the  CLI commands to perform common software update tasks such as adding, removing, and searching for packages.

You also learn how to perform a “dry run” on package installations. This allows you to see the changes that will occur on the system when a package is installed, without actually installing the package.

The Oracle Solaris 11 Network Administration training provides you with the knowledge and skills necessary to configure and administer a reliable, scalable, highly available, and secure network, both physical and virtual, using the Oracle Solaris 11.1 OS. The course is primarily built around a hands-on approach to configure and administer virtual networks, failover options, network services, network resources, and network security. The demonstrations hosted here give you an insight into some of the key practices that are part of a larger, unified, scenario-based lab exercise in this training.

The Configuring Server Message Block (SMB) for Cross-platform Resource Sharing demonstration illustrates the sharing of files between Oracle Solaris and Windows systems.

Network Resource Management is a constant challenge for any IT-enabled industry. Oracle Solaris 11 helps in network provisioning, establishing service-level agreements, billing clients, and diagnoses security problems by setting datalink properties pertaining to network resources. By managing network resources, network administrators can achieve quality of service (QoS) more easily and dynamically. Network administrators can set network bandwidth priorities and regulate network resources to critical applications by setting datalink properties pertaining to these network resources.

Oracle Solaris 11.2 introduces the Unified Archives feature that enables creating a single archive for redeployment either as clones within a cloud envrionment or for system backup and disaster recovery purposes. You can quickly capture a complete bare-metal system, virtual environments, or a combination of both. This demonstration illustrates the use of Unified Archives to deploy a system via Automated Installer.

Oracle Solaris 11.2 supports two types of authentication material for Internet Key Exchange (IKE), preshared keys and public key certificates. A preshared key is a string of hex or ASCII characters that only two IKE systems know. The keys are called preshared because both endpoints must know the value of the key before the IKE exchange. This key must be part of the IKE configuration on both systems. The preshared key is used in the generation of the IKE payloads, which make up the packets that implement the IKE protocol. The system that processes these IKE payloads uses the same key to authenticate the payloads that it receives.
The preshared key is not exchanged between the IKE endpoints by using the IKE protocol. Typically, the key is shared with the peer system over a different medium, such as a phone call. The preshared key on the peers that use this authentication method must be identical. The keys are stored in a file on each system.

Network virtualization in Oracle Solaris 11.1 is an OS provisioned mechanism that decouples the virtual network from the underlying physical network. A virtual network, also called an internal network, is therefore a pseudo network that only uses the physical network as an IP backplane. Although a pseudo network, the virtual network offers the same capabilities as that of a physical network and much more, such as hardware independence and scaling. Being an OS supported technique; virtual networks are programmatically created and configured. This scenario-based demonstration illustrates how to use the basic building blocks of network virtualization (such as VNICs, virtual switches, etherstubs, and routing functionality) to consolidate a distributed computing environment. This demonstration is divided into two parts.

Network virtualization in Oracle Solaris 11.1 is an OS provisioned mechanism that decouples the virtual network from the underlying physical network. A virtual network, also called an internal network, is therefore a pseudo network that only uses the physical network as an IP backplane. Although a pseudo network, the virtual network offers the same capabilities as that of a physical network and much more, such as hardware independence and scaling. Being an OS supported technique; virtual networks are programmatically created and configured. This scenario-based demonstration illustrates how to use the basic building blocks of network virtualization (such as VNICs, virtual switches, etherstubs, and routing functionality) to consolidate a distributed computing environment. This demonstration is the concluding part of Configuring a Virtual Network in Oracle Solaris 11.1 demonstration.

The Oracle Solaris Elastic Virtual Switch (EVS) feature enables you to manage virtual switches that are spread across multiple physical machines hosting several virtual machines (VMs). This demonstration illustrates the use of EVS to provide connectivity between the virtual machines connected to it from anywhere in the network.

In this practice, you explore the physical-to-virtual (P2V) process for migrating an Oracle Solaris 10 global zone to an Oracle Solaris 11 environment. To do this, first you should assess the source Solaris 10 global zone to ensure it is Solaris 10 9/10 OS or higher. Then, you perform three key tasks:
•    Prepare the source global zone for migration
•    Prepare the target global zone for migration
•    Migrate from the Oracle Solaris 10 global zone

This demonstration provides an example of the physical-to-virtual (P2V) method for migrating workloads from a physical machine to a virtual machine using Oracle Solaris Zones technology. During this demonstration, workloads running in the Oracle Solaris 10 physical environment are migrated to an Oracle Solaris 11 zone. The demonstration includes step-by-step walkthroughs of each task associated with the P2V migration.

In this practice, you explore Oracle Solaris 11 network virtualization by configuring VNICs and an etherstub to work within two pre-configured Oracle Solaris zones, and then configure that virtual network for public access.

In this practice, you work with CLI commands to create an iSCSI target on your server. To achieve this goal you will first create an iSCSI Logical Unit Number (LUN) and then create the iSCSI target itself.

Oracle Solaris 11.2 supports two types of authentication material for Internet Key Exchange (IKE), preshared keys and public key certificates. A preshared key is a string of hex or ASCII characters that only two IKE systems know. The keys are called preshared because both endpoints must know the value of the key before the IKE exchange. This key must be part of the IKE configuration on both systems. The preshared key is used in the generation of the IKE payloads, which make up the packets that implement the IKE protocol. The system that processes these IKE payloads uses the same key to authenticate the payloads that it receives.
The preshared key is not exchanged between the IKE endpoints by using the IKE protocol. Typically, the key is shared with the peer system over a different medium, such as a phone call. The preshared key on the peers that use this authentication method must be identical. The keys are stored in a file on each system.

In this practice, you create an encrypted ZFS file system using a raw key that you create.

Protecting the network traffic from security threats, such as packet sniffing, man-in-the-middle attack, packet forgery, is one of the prime concerns in today’s world. The network traffic is secured at IP layer by using IPSec protocol, which provides encryption and authentication. IPSec uses ESP protocol for strong integrity, data authentication, and confidentiality. These protocols use AES algorithm for encryption and SHA1 algorithm for authentication.
In this demonstration, you learn how to secure the traffic between two hosts by configuring the ESP protocol with authentication and encryption protection. Then, you use SHA1 with a 160-bit key for authentication protection and AES with a 256-bit key for encryption.