Tools You Can Use: Planning and Memory
While many of us know and regularly use the AIX tools IBM provides, as time goes by, these tools get enhanced and new ones added. So let’s examine some of the newer or updated tools and flags, specifically related to:
- System Planning Tool (SPT)
- Active Memory Expansion (AME), and
- Network Install Manager (NIM) commands
SPT is great for designing a system, especially when it comes to mapping cards to I/O drawers and so on. It has been repeatedly upgraded and additional functions have been added. The current version (22.214.171.124) can be used to design and document systems. For the most part, I export a .sysplan file from the hardware management console (HMC) before and after any changes. This provides great documentation and makes it easy to rebuild the server from scratch should it become necessary.
Although a .sysplan file can be used to deploy LPARs or as input to econfig, I primarily use it to document the system. SPT keeps track all of the resources assigned to the LPARs as well as providing diagrams and slot mappings. In a disaster situation or even for day-to-day purposes, the system plan is one of the better tools to document what’s needed to rapidly recreate the system.
A POWER7 technology, AME allows an administrator to define an LPAR with less physical memory than it actually needs to run. It relies on memory compression, which kicks in only when it’s necessary to use memory beyond that defined as the base.
For example, if an LPAR needs around 6GB at peak but only 3GB most of the time, it could be defined with 3GB and an AME expansion factor of 2. This lets the LPAR use up to 6GB with compression starting after the first 3GB are in use. Its implementation requires the POWER7 server is licensed for AME and that the HMC and AIX are at specific minimum levels. However, it can be useful in dynamic environments, especially when the system is short on memory but has a few spare CPU cycles. I use it regularly on my dev/test systems to run more LPARs on the server.
AME is transparent to applications, which makes it easy to implement. Adding AME to an LPAR requires completing a few fields in the profile definition in the HMC, and then the LPAR needs to be reactivated. One way to avoid this is to always define AME to all LPARs while setting the expansion factor to 1.0. This effectively disables AME while allowing the expansion factor to be increased dynamically without needing to reactivate the LPAR.
AME isn’t designed for LPARs that are short on both memory and CPU as compression will use some CPU. Also, AME only uses the smaller memory page sizes, so some of the larger page sizes aren’t available. And, in a Live Partition Mobility (LPM) environment, both servers must have AME enabled.
The amepat command can be used for planning and monitoring AME once it’s running in active mode. The command runs on POWER4 through POWER7 servers and AIX 7 or AIX 6.1 TL04 and higher. amepat provides statistics and recommendations on how to use AME to reduce the required physical memory for the LPAR and how much additional CPU it would need for compression and decompression activities.
While many administrators are aware of AME, not everyone is aware that several commands have been updated to report AME statistics. These include the following:
- svmon –G –O summary=ame,pgsz=on,unit=MB
- lparstat –i
- lparstat –c
- vmstat –c
- topas (new AME section)
Lastly, topas_nmon will record AME information in the .nmon file, which can then be post-processed.
AME should be in everyone’s toolbox in a POWER7 environment. It won’t be used everywhere, but it can save significant amounts of memory in dev/test and non-database environments.
comments powered by