NMON "switches"

[David_Tsatsi]

Hi guys DirkBleyenberg, Jim.Tokarz, SurendranathKS, dupda03, limro02

 

I am attempting to get NMON running on and AIX environment OS and then export data to import it to CA DM and this was the question asked: "Please provide what switches you require for the nmon command with regards to the CA tool. Please advise as to what the CA tool recommends"

 

Please advise.

 

Regards

David

[Mohindra.Singh]

Hi David,

I could not track down the exact switches required for the Nmon configuration. As per previous interactions, I would recommend configuring Nmon to collect 30 minute metric data. See below for list of metrics that the DA collects.

 

I've included a list of the preq's and defects to look out for.

 

IBM NMON data collection

Data Manager can collect and store performance metrics generated by IBM NMON for LPAR AIX environments.  When you create your data source, you should provide the NMON file just as it is generated by the NMON tool. That is, the “AAA” section should appear at the beginning of the file and every timestamp (the “ZZZZ” section) must be followed by its corresponding data.

Note: A defect in multiple versions of topas_nmon included in AIX 5.3 and AIX 6.1 inserts incorrect (future) dates into the topas_nmon recording file. Data Manager halts the load process when it encounters these incorrect dates. To correct the problem, you should obtain and apply the IBM Program Temporary Fix (PTF) for your version of AIX. If you already loaded data with the incorrect dates with an earlier version of Data Manager, contact CA technical support for assistance.

For more information about setting up a data source, see NMON data source details.

Version support

Data Manager supports the following versions of IBM NMON:

Product	Version
NMON	13b 12e 11e 11d
TOPAS-NMON for AIX	6.x 5.3 5.2

LS_Server metrics

Data Manager can collect the following metrics:

Data Manager Metric	Description	Unit	Source
GBL_LS_ENTITLEMENT	The entitlement for the logical system in the unit in which it was collected.	Native Unit	GBL_LS_ENTITLEMENT
GBL_LS_LOGICAL_CPU	Number of logical CPUs the logical system can use.	Number of cores	Number of logical CPUs the logical system can use
GBL_LS_MEM_MB_USAGE	Megabytes of physical memory consumed by the logical system.	Megabytes	real_free_mb
GBL_LS_MEM_UTIL	Percentage of entitled memory utilized by the logical system.	Percent	real_free_perc
GBL_LS_PHYS_CPU_USED	Number of physical CPUs used.	Percent	GBL_LS_PHYS_CPU_USED
GBL_LS_PHYS_CPU_UTIL	Percent of physical CPUs used.	Percent	GBL_LS_PHYS_CPU_UTIL
GBL_LS_POOL_CPU	Pool CPU idle time for the logical system	Percent	GBL_LS_POOL_CPU
GBL_LS_POOL_CPU_IDLE	Pool CPU idle time for the VM.	Percent	GBL_LS_POOL_CPU_IDLE
GBL_LS_POOL_CPU_UTIL	Percentage of Pool CPU utilized by the logical system.	Percent	GBL_LS_POOL_CPU_UTIL
GBL_LS_VIRT_CPU	Number of virtual CPUs in the logical system.	Number	GBL_LS_VIRT_CPU
GBL_LS_WEIGHT	Weight (Share) assigned to the logical system.	Number	GBL_LS_WEIGHT

hth,

Mohindra Singh

[Legacy User]

David,

  Look at the samples directory for the NMON file.  The switches that are set are documented inside the file in the first 5 lines of the file.

The command line used to run NMON is documented inside each NMON output file.

 

NMON dedicated file has this:

AAA,command,/usr/nmon/nmon_aix53 -m /monitor/nmon -fT -s 60 -c 1438 -A

 

NMON shared example file has this:

AAA,command,/usr/local/sysadmin/perftools/nmon/nmon53 -F /usr/local/sysadmin/perfdata/nmon/nmon.server01.073107.nmon -s300 -c288 -t

 

 

 

David