vios

Since you can only have one IVM in the JS22, you cannot use SEA failover as you can in a traditional VIOS installation.

This took a long time, as I had several disks (100 ) assigned to my VIOS, and four paths to the SAN, all of which had to be scanned.

The VIOS on both systems must be capable of providing virtual access to all storage resources that the mobile partition is using.

All the disks that are visible on the AIX client partition have to be virtual disks (exported from VIOS using virtual SCSI).

With each of the GUIs, you can query the VIOS that holds the VM library to see what ISO images are available.

These steps were to check the general health of the VIOS.

I noticed several disks were identified as having AIX installed on them, but they did not belong to my VIOS rootvg!

Rather than mix two vendors' MPIO code on the same VIOS, it may be simpler to manage if each storage type has its own VIOS.

The SAN disks that are exported to the AIX client partition must be available to both the VIOS partitions on both the CECs.

Once both my VIOS were activated and I'd verified the virtual adapter mappings and health checks, I started an AIX LPAR.

I also captured the location codes for the VIOS rootvg disks, which proved to be an important step, as shown later.

Therefore, logical memory has to be backed by both the physical memory in the pool and by the paging devices on the paging VIOS.

Using the topas command on the source VIOS, you may observe some network traffic on the SEA (ent6) as a result of the memory copy.

However, many customers run two VIOS partitions to provide redundancy and fail-over to the AIX client partition.

The VIOS partition profile is also updated to reflect the removal of these virtual devices.

The supported devices differ between AIX and POWERVM VIOS, as well.

A switch of the paging VIOS partition can be initiated through the HMC command line using the chhwres command with the -so option.

The data LUNs had already been assigned to the VIOS and mapped and configured on the client LPAR.

The IVM automatically created a VIOS paging device for each LPAR as part of the migration to shared memory.

If possible, the paging VIOS redundancy configuration for the migrated partition will be preserved on the target system.

I also ensure that we update the VIOS and LPAR partition profile (on the HMC) with these newly created virtual adapters.

AIXPCM supports all devices that the AIX operating system and VIOS POWERVM firmware support, including selected third-party devices.

NPIV with a VIOS, utilizes virtual FC devices to present disk (and tape) natively to the client LPARs.

I activated one of the VIOS and waited while it started to boot.

The VIOS on both systems must have a shared Ethernet adapter configured to bridge to the same Ethernet network used by the mobile partition.

If the shared memory partition has been configured to use redundant paging VIOS partitions, a common paging space device will be assigned.

If 'no_reserve' is not set, then VIOS on the original CEC should be shut down before the switch over is done.

However, after an initial spurt, sales of the Vios have been weak.

You can confirm the existence of this device with the lsdev command on the VIOS.

The paging VIOS partitions that you define here will be used as defaults when you later create the shared memory partitions.

Two LUNs from SAN storage are mapped to the two fibre channel adapters on the VIOS partition.

The VIOS itself can be installed on either the internal disk or SAN disk.

Ensure VLAN configuration is done appropriately for VIOS partitions on both the CECs.

No reconfiguration (apart from the boot list) was required, even for the VIOS.

If you prefer the VIOS shell prompt, there are very few commands to learn, and they're easy to remember.

We then enter the OEM VIOS environment to run the pcmpath utility and obtain the LUN ids associated with each hdisk.

Figure 3 illustrates a switchover of an AIX environment using a single VIOS partition.

After a failover, no automatic switch back will occur when the original paging VIOS partition comes up again.

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

If you want to create a non-redundant partition, set the Secondary Paging VIOS field to none.

On each VIOS an SEA has been configured. Confirm this by viewing the device configuration on both VIOS.

Verify that the same SAN disk can be seen by both VIOS.

If you do need to restore a VIOS from mksysb, it's a good idea to create a new SPOT on your NIM master for each VIOS.

Run this command on the source VIOS during the migration.

Verify the virtual device configuration and status on each VIOS.

Likewise, the VIOS used to serve DS8300 storage to client LPARs, will also remain.

One of the most important is that all network connectivity from the LPAR must be virtualized, meaning it must communicate using a VIOS.

Verify the partition profile data for each AIX LPAR and VIOS is correct on the HMC.

Document the current virtual device mappings on each VIOS.

Repeat the same verification procedures for the second VIOS.

With my pool defined, I observed its settings from the IVM and the VIOS.

If a VIOS fails, the service address moves to the boot adapter served by the redundant VIOS.

Run the pcmpath command (from oem_setup_env) and verify that all paths are operating normally on both VIOS.

Again, it was very important to document the location codes of my VIOS rootvg disks prior to restoring the VIOS mksysb.

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

I specified 12GB for the pool and chose rootvg as the location for the VIOS paging devices.

To swap to another ISO image, unload the media on the VIOS using unloadopt or via the GUI.

Mobility activity is logged on the LPAR and the source and target VIOS.

Starting with HMC v7, the HMC reserves the first ten virtual adapter slots on each VIOS for internal HMC use.

I exited SMS and let the VIOS boot as normal.

I noticed that the boot list on each VIOS had changed.

Before starting my LPARs, I first performed several health checks on each VIOS.

Then a chhwres command is executed to switch the active paging VIOS partition.

From the output above, you can confirm that the SEA, ent6, on both VIOS, is configured using the first LHE port, ent0.

I find the VIOS command line much faster and easier.

Prior to starting the migration, we deployed two new VIOS (hvio11 and 12), specifically for use with NetApp.

You can load ISO images on the VIOS command line, or via the GUI.

Select the SAN disk assigned to the VIOS, which in my environment is the DS8100 disks.

On CEC2, ensure the VIOS partition is up and running.

When adding a common paging space device using the chhwres command, you only need to specify one paging VIOS partition.

AMS paging devices view from the VIOS.

Afterwards, you can see in the lshwres command output that the active paging VIOS partition has changed to lpar_2_solchio06.

Using the lspv command, check that both VIOS have the same PVID associated with the SAN storage (hdisk1, 2, and 3), as shown in Figure 3.

Perform a health check on each VIOS.

This is why it was important to collect the location codes for my VIOS rootvg disks prior to the upgrade.

Two virtual SCSI server adapters (vhost0 and vhost1) are created on the VIOS lpar.

WWPNs for all FC adapters on all VIOS involved in the migration.

Review the logs with the errpt (AIX) and errlog (VIOS) commands.

And finally we remove the hdisk from the ODM on the VIOS.

To log in, use the VIOS padmin userid and password.

You can check your VIOS level by logging in as padmin and running ioslevel.

Toyota, for example, had initially expressed interest in adapting its popular Vios and Yaris models rather than developing a new small car.

Configured on the blade were a VIOS (IVM) and two AIX 6. 1 LPARs.

Listing 2 shows how to display and switch the active paging VIOS partition.

This is accomplished by installing a VIOS mksysb image using NIM.

However, you have the option to change the paging VIOS configuration in the migration wizard.

If you have a VM Library you can view its contents by logging into the VIOS as padmin and using the lsrep command.