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
Tracing Low Memory event
Trace events have also been added to trace memory pressure situations. It helps to identify pressure on page cache or pinned memory heap.
While performing read/write operations on page cache, 'lowmem' thresholds is calculated. If the number of client free pages goes below this threshold, VxFS starts its own pager. The trace entries provide details about free client pages and whether the low memory condition is detected.
In this example, the trace hook identifier for VxFS memory pressure situations is 0E5. For tracing memory pressure:
# trace -a -j 0E5 & # trcon # cat script.sh (file on VxFS file system) # trcoff # trcstop # trcrpt > trace.out
Sample output with entries for low page cache:
0E1 0.000619916 VxFS lowpgcache: numclientframes AA96, trigger_limit CC880, lowmem detected 0000
VxFS checks the available pinned heap and calculates the limitalloc, limitsuff, and limitfree thresholds. If pinnable memory goes below the 'limitalloc' threshold, pinned memory allocation for new inodes and buffers is allowed in certain scenarios only. The 'limitsuff' threshold is limit to decide whether in-sufficient pinned memory situation has reached. If 'limitfree' threshold is hit then VxFS starts freeing allocations which are not in use currently. Basically there are pools or caches for various types of data structures. Whenever VxFS needs any of these data structures, memory from theses pools or caches are taken instead of asking the operating system every time. When VxFS is done with the data structure, the memory is returned back to pool or cache as the case may be. If memory pressure is noticed and this threshold is hit then VxFS looks at these pools, caches and see whether any memory can be given back to system. The trace entries provide details about these thresholds and pinnable memory left.
The trace entries provide details about these thresholds and pinnable memory left.
Sample output with entries for low pinned heap:
0E1 0.926113776 0.118139 VxFS lowpinnedheap: limitalloc = 17B8E, limitsuff = 14C1C, limitfree = 11CAA, pinnable_left = 71E55