Veritas InfoScale™ 7.4.1 Virtualization Guide - AIX
- Section I. Overview
- Storage Foundation and High Availability Solutions in AIX PowerVM virtual environments
- Section II. Implementation
- Setting up Storage Foundation and High Availability Solutions in AIX PowerVM virtual environments
- Supported configurations for Virtual I/O servers (VIOS) on AIX
- Installing and configuring Storage Foundation and High Availability (SFHA) Solutions in the logical partition (LPAR)
- Installing and configuring Cluster Server for logical partition and application availability
- Supported configurations for Virtual I/O servers (VIOS) on AIX
- Setting up Storage Foundation and High Availability Solutions in AIX PowerVM virtual environments
- Section III. Use cases for AIX PowerVM virtual environments
- Application to spindle visibility
- Simplified storage management in VIOS
- Configuring Dynamic Multi-Pathing (DMP) on Virtual I/O server
- Configuring Dynamic Multi-Pathing (DMP) pseudo devices as virtual SCSI devices
- Extended attributes in VIO client for a virtual SCSI disk
- Virtual machine (logical partition) availability
- Simplified management and high availability for IBM Workload Partitions
- Implementing Storage Foundation support for WPARs
- How Cluster Server (VCS) works with Workload Patitions (WPARs)
- Configuring VCS in WPARs
- High availability and live migration
- Limitations and unsupported LPAR features
- Multi-tier business service support
- Server consolidation
- About IBM Virtual Ethernet
- Using Storage Foundation in the logical partition (LPAR) with virtual SCSI devices
- How DMP handles I/O for vSCSI devices
- Physical to virtual migration (P2V)
- Section IV. Reference
About configuring failovers
An application can be failed over from an LPAR to a WPAR running on a different LPAR. You can configure VCS to fail over from a physical system to a virtual system and vice versa. A physical to virtual failover gives an N + N architecture in an N + 1 environment. For example, several physical servers with applications can fail over to containers on another physical server. On AIX, a container is a WPAR.
In this configuration, you have two LPARs. One node runs AIX 7.1 (sysA) and another node that runs AIX 6.1 (sysB). The node that runs AIX 6.1 has WPARs configured.
In the main.cf
configuration file, define the container name, type of container, and whether it is enabled or not. The following is an example of the ContainerInfo lines in the main.cf
file:
ContainerInfo@sysA = {Name = W1, Type = WPAR, Enabled = 2}
ContainerInfo@sysB = {Name = W1, Type = WPAR, Enabled = 1}
On sysA, you set the value of Enabled to 2 to ignore WPARs so that the application runs on the physical system. When an application running on sysA fails over to sysB, the application runs inside the WPAR after the failover because Enabled is set to 1 on sysB. The application can likewise fail over to sysA from sysB.
IMF must be disabled on the node where Enabled is set to 2 (sysA in this example). To disable IMF, set the mode to 0.
On a Workload Partition (WPAR) where the WPAR is ignored to run the application on the physical system, you can disable the IMF for the WPARs.
To disable IMF monitoring
- Set the Mode key of IMF attribute to 0:
# hares -override <wpar_res> IMF # hares -local <wpar_res> IMF # hares -modify <wpar_res> IMF Mode 0 MonitorFreq 5 RegisterRetryLimit 3 \ -sys sysA