vio.

For instance, it is advisable, for the sake of redundancy and availability, to have at least two VIO Servers per managed frame.

VIO SCSI disks configured in the global partition can be exported to a WPAR for use as a data disk or as the rootvg for the WPAR.

VIO technology can help you use resources more effectively, cut down on hardware costs, and consolidate servers in new and powerful ways.

The resources that you assign to each VIO server should be as close to identical as possible and designed to maximize availability.

This VIO server runs a special version of the AIX operating system, with an additional software package called IOS.

The second virtual Ethernet adapter on each of the VIO Servers must be configured as a non-trunk adapter.

mkvdev: This command manages the virtual devices that you create and serve up to the VIO client LPARs.

Therefore, it is recommended to use at least two VIO Servers to host storage and network resources to the LPARs.

For the VIO Server, you must allocate at least one storage controller and one Ethernet card.

In creating the VIO Servers, you assign disks to the server by assigning a storage controller to that server.

Do not mix a slower speed Ethernet adapter on one VIO server with a faster speed one on another.

You can back up the VIO Server to a file, a tape device, CD, or DVD drive.

You define virtual Ethernet and disk devices on the VIO Server and then make them available to the other LPARs on the system.

With the use of VIO LPARs, you could host 15 LPARs with a much smaller number of Ethernet and disk controllers.

When configuring the profiles of the VIO Servers on the HMC, create two virtual Ethernet adapters on each server.

You also learned how to improve recoverability by using NIM on an LPAR to house recovery images for your LPARs, VIO Servers, and HMCs.

Set different trunk priority numbers between the two VIO servers.

Building two VIO servers into the same System p hardware can provide redundancy in case one component fails.

These profiles will contain your VIO servers' configurations with virtual devices.

Make sure each client adapter on the LPAR points to a different VIO Server.

They permit physical adapters to be shared by one or more VIO client partitions.

VIO technologies consist of servers, software, and various commands.

The screen shot of the second virtual Ethernet adapter for the VIO Servers should look the same.

When VIO servers are created, they are assigned both physical Ethernet adapters and virtual Ethernet adapters.

In the HMC, make copies of the current VIO servers' profiles, and call them $SERVER. vio.

Note: You created the VIO client LPAR as a blank slate so that you can define this easily.

The third area you need to plan is to have redundant VIO servers on the same physical pSeries or System P server.

Mapping disks to both VIO servers and creating network control channels gives VIO client LPARs two legs to stand on.

Then, the VIO client LPARs are told the virtual Ethernet adapters and VLAN numbers they should access through an SEA mapping.

If you need to make this SEA available from the VIO Server, use the mktcpip command to set an IP address on it.

Just make sure the Virtual LAN ID field has the same value as the trunk adapters in the VIO Server configurations (see Figure 5).

cfgdev: This command is the equivalent of the cfgmgr command and detects new physical and logical devices added to the VIO server.

Shut down your VIO servers, and activate them from these profiles, or dynamically add the same resources to the LPARs.

Benefits: This method is an extremely elegant way to manage VIO disk resources and simplifies the process of mapping disks.

And, an errant rmlv command can completely knock a VIO client LPAR off of the wire.

It also makes it possible to perform IOS upgrades on the VIO servers dynamically without affecting the VIO client LPARs.

The SAS tape adapter is owned by the VIO server partition, similar to NPIV.

Insufficient resources in the VIO server can bottleneck the whole system.

Make sure you make the virtual disk devices of the LPAR the same size on each of the VIO Servers.

When you need to build an LPAR or install AIX software quickly, making an ISO image available to the VIO client takes seconds.

You should also set up a third virtual Ethernet adapter on each VIO Server using the Virtual LAN ID of the trunk adapter.

Figure 3 depicts two sets of computing environments, illustrating Solaris zones and AIX VIO.

Again, you will rarely have to become root on a VIO server.

In this method, disks are assigned to the VIO servers and mapped directly to the VIO client LPARs.

After installing the VIO Server operating system, run the following command on both VIO Servers (see Listing 2).

APAR IZ01331 describes the scenarios of using VIO with PowerHA clusters and the challenges faced in detecting network failures.

VIOs Virtual tape drive support for client LPARs is another new offering that allows client LPARs access to SAS tape resources.

Drawbacks: Resource contention can occur if you have too many VIO client LPARs going through the same physical Ethernet adapter.

Using the HMC, create two virtual SCSI adapters on each LPAR that use the VIO to access the SAN.

Including the interface name will not work in a VIO environment.

Then, you map those LVs to VIO client LPARs for use, seeing them as individual disks.

A specialized superuser, padmin, is used for most aspects of setting up VIO servers.

It is assumed that there is more than one disk attached to the disk controller allocated to the VIO Server (see Listing 4).

Both VIO Servers must be running Fix Pack 7.

The VIO client LPARs are told which virtual Ethernet adapters they should use for their communication.

Log in to the VIO servers with the padmin user ID and run cfgdev to detect any new disks.

When the VIO server is up, log in with the padmin user ID and set its password.

Unless you have a small managed system or do not plan on utilizing the VIO Server extensively, this is too small.

Benefits: As long as you have a physical entX device available, you can make a new connection for your VIO client LPARs.

The Trunk priority for VIO Server 1 in Figure 1 is set to 1, making it the primary adapter.

Assign the SAN disks in the VIO Server to the LPARs using the mkvdev command.

Upgrading your VIO servers to version 2. 1.

The VIO client LPARs will go to the other VIO server for their disk and network resources.

In the HMC, open the VIO servers' virtual-enabled profiles using the Edit menu.

Open the VIO partition's profile on the HMC (see Figure 22).

In the HMC, open the VIO client LPARs' virtual-enabled profiles using the Edit menu.

Application data storage redundancy using two VIO Servers