Operating System agentLPAR2RRD OS agent is a solution for those of you who wish to consolidate memory, paging, SAN (FC), SEA, vSCSI, Eth adapters performance statistics into the tool.
Without that LPAR2RRD only provides CPU physical utilization, memory allocation and Active Memory Sharing graphs.
Summary of memory monitoring in LPAR2RRD without the OS agent.
OS agent Release notes / Download the latest OS agent version / Installation manual
OS agent is not necessary on VMware VMs as the tool gets enough OS details directly from vCenter or ESXi servers.
- IBM i (AS/400) agent (1.0.2)
- OS agent supports Linux generally (x86, x32 ...). It allows to load performance data from any Linux box.
All will be placed under "Linux" item in "SERVER" menu.
- new metric: response times per FCS and vSCSI adapters
- vSCSI adapter statistics (IO, data throughput, response time) can be found under SAN tabs in the GUI
- OS CPU utilization of user/sys/IO wait/idle in %
- Memory utilization of used/pinned/fs cache/free memory in MB (v3.60)
- Paging rate in MB/sec (v3.60)
- Paging space utilization in %
- SAN (fiber channel) throughput in MB/sec
- SAN (fiber channel) throughput in IO/sec
- LAN (ethernet) throughput in MB/sec
- SEA (Shared Ethernet Adapter) throughput in MB/sec (only on VIO servers)
- AME (Active Memory Expansion) allocation
- Paging activity alerting via alerting module (v3.60)
- AIX 5.1+
- Linux on Power
- Linux x86 (v4.84)
- IBM i (v4.90)
- WPAR support
- LPARs not being managed by the HMC (targeted mainly to old POWER4/5 full partition stuff)
Implementationit is impelemented as simple client/server application.
- There is LPAR2RRD daemon listening on the host where LPAR2RRD server is running on port 8162 (IANA official port assigned to LPAR2RRD project).
- Each LPAR has installed simple Perl based agent which is started every minute from the crontab and saves memory and paging statistics into a temporary file.
- The agent contacts the server every 10 minutes and sends statistics data which is imported into RRDTool DB files like usual CPU data in LPAR2RRD.
- As soon as data is stored then you might browse them via LPAR2RRD GUI (LPAR details are enhanced about 4 memory graphs and 4 paging graphs).
- The server process is started automatically from standard LPAR2RRD scripts (load.sh).
- Starting happens only if there is set parameter LPAR2RRD_AGENT_DAEMON=1 in etc/lpar2rrd.cfg. (note that it is switched off in default LPAR2RRD_AGENT_DAEMON=0)
Disadvantage of the solution is an agent deploy to all lpars. On the other hand deploy itself is easy and the agent is very simple.
Agent deployAgent is written in Perl and calls basic OS commands to obtain required statistics like vmstat, lparstat and svmon.
Agent RPMs can be found after LPAr2RRD server installation in /home/lpar2rrd/lpar2rrd/agent:
- AIX and VIOS: lpar2rrd-agent-4.84-0.aix5.1.ppc.rpm
- Linux: lpar2rrd-agent-4.84-0.Linux.noarch.rpm (any Linux X86 or Linux on Power)
- Perl interpreter (AIX usually contains it) and preferably a user account on each LPAR.
- Opened TCP communication between each LPAR and LPAR2RRD server on port 8162.
Connections are initiated from LPARs.
- Additional disk space on LPAR2RRD server (about 40MB per each monitored LPAR)