InfoScale™ 9.0 Virtualization Guide - AIX
- Section I. Overview
- Storage Foundation and High Availability Solutions in AIX PowerVM virtual environments
- Overview of the InfoScale Virtualization Guide
- About the AIX PowerVM virtualization technology
- About InfoScale products support for the AIX PowerVM environment
- About IBM LPARs with N_Port ID Virtualization (NPIV)
- About Veritas Extension for Oracle Disk Manager
- Virtualization use cases addressed by InfoScale
- 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
- Dynamic Multi-Pathing in the logical partition (LPAR)
- Dynamic Multi-Pathing in the Virtual I/O server (VIOS)
- InfoScale products in the logical partition (LPAR)
- Storage Foundation Cluster File System High Availability in the logical partition (LPAR)
- Dynamic Multi-Pathing in the Virtual I/O server (VIOS) and logical partition (LPAR)
- Dynamic Multi-Pathing in the Virtual I/O server (VIOS) and InfoScale products in the logical partition (LPAR)
- Cluster Server in the logical partition (LPAR)
- Cluster Server in the management LPAR
- Cluster Server in a cluster across logical partitions (LPARs) and physical machines
- Support for N_Port ID Virtualization (NPIV) in IBM Virtual I/O Server (VIOS) environments
- About setting up logical partitions (LPARs) with InfoScale products
- Configuring IBM PowerVM LPAR guest for disaster recovery
- Installing and configuring Storage Foundation and High Availability (SFHA) Solutions in the logical partition (LPAR)
- Installing and configuring storage solutions in the Virtual I/O server (VIOS)
- Installing and configuring Cluster Server for logical partition and application availability
- Enabling Veritas Extension for ODM file access from WPAR with VxFS
- 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
- About simplified management
- About Dynamic Multi-Pathing in a Virtual I/O server
- About the Volume Manager (VxVM) component in a Virtual I/O server
- 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 IO client adapter settings for Dynamic Multi-Pathing (DMP) in dual-VIOS configurations
- Using DMP to provide multi-pathing for the root volume group (rootvg)
- Boot device management on NPIV presented devices
- Virtual machine (logical partition) availability
- Simplified management and high availability for IBM Workload Partitions
- About IBM Workload Partitions
- About using IBM Workload Partitions (WPARs) with InfoScale products
- Implementing InfoScale support for WPARs
- How Cluster Server (VCS) works with Workload Patitions (WPARs)
- Configuring VCS in WPARs
- Configuring AIX WPARs for disaster recovery using VCS
- High availability and live migration
- About Live Partition Mobility (LPM)
- About the partition migration process and simplified management
- About Storage Foundation and High Availability (SFHA) Solutions support for Live Partition Mobility
- Providing high availability with live migration in a Cluster Server environment
- Providing logical partition (LPAR) failover with live migration
- Limitations and unsupported LPAR features
- Multi-tier business service support
- Server consolidation
- About IBM LPARs with virtual SCSI devices
- Using Storage Foundation in the logical partition (LPAR) with virtual SCSI devices
- Using Storage Foundation with virtual SCSI devices
- Setting up DMP for vSCSI devices in the logical partition (LPAR)
- About disabling DMP for vSCSI devices in the logical partition (LPAR)
- Preparing to install or upgrade Storage Foundation with DMP disabled for vSCSI devices in the logical partition (LPAR)
- Disabling DMP multi-pathing for vSCSI devices in the logical partition (LPAR) after installation or upgrade
- Adding and removing DMP support for vSCSI devices for an array
- How DMP handles I/O for vSCSI devices
- Using VCS with virtual SCSI devices
- About server consolidation
- About IBM Virtual Ethernet
- Physical to virtual migration (P2V)
- Section IV. Reference
Recommendations for improved resiliency of InfoScale clusters in virtualized environments
Arctera recommends that you configure the following settings to improve the resiliency of InfoScale cluster configurations in virtualized environments:
Peerinact: Set the default LLT tunable parameter peerinact to 32 seconds instead of 16 seconds. Doing so helps improve the stability of the cluster in virtualized environments, where multiple external factors as described further in this list, can affect the stability of the cluster.
Provisioning ratio: The CPU and memory provisioning ratio affects the stability of the InfoScale cluster. To ensure maximum stability, set the ratio to the lowest value possible. For critical solutions that require maximum resiliency, the ratio must be set to 1:1.
CPU load on host operating systems: Although the provisioning ratio is low, the CPU load on the host operating systems still plays a part in cluster stability. If the load on the host operating system is very high, it can affect how vCPUs on the guest VMs are scheduled, because vCPUs are processes from the perspective of the host servers.
CPU requirement of the actual workload on guests: When the total CPU requirement for workloads exceeds the available physical CPU capacity, it causes node evictions due to heartbeat timeouts.
External events: External events like live migration of the guest VMs, virtualized disk backups, and so on, are known to add CPU load on the host servers. To reduce this additional load on the CPU, watch the stun duration in your environment caused by these events, and increase the peerinact value, if required. Increase the peerinact value only in these conditions and not in any other circumstances.
Hypervisor: Always follow the best practices for the hypervisor.