ona plus user guide - ontuneontune.us/wp-content/uploads/2016/11/onaplus_manual.pdfstarting ona plus...

2016© TeemStone LLC. All Rights Reserved

ONA Plus User Guide Nov. 2016

The Content provided on this document is copyrighted by TeemStone LLC and is protected from copying, reproduction,

modification, distribution, display, performance or transmittal for any purpose under international copyright laws. The

trademarks, trade names, service marks, product packaging, designs and corporate logos and emblems displayed on this document

belong exclusively to TeemStone LLC are protected from reproduction,

It is not allowed to copy, reproduce, modify, distribute, display, and transmit this document without written permission of

TeemStone LLC.


HOW TO INSTALL ONA Plus

* Computer Requirements

1. OS : Windows 2003 or later; Windows 7 or later recommended.

2. CPU : 2GHz, 2 core or more recommended.

3. Memory : 2GB or more free memory.

4. Storage :

400MB per 10GB of nmon logs if filesystem trend is excluded;

Or 700 MB per 10GB of nmon logs if filesystem trend is included.

Or 2 GB per 10GB of nmon logs if process trend is included.

Or 2 GB per 10GB of nmon logs if disk and network are included.

Please note these are estimated storage sizes, and actual usage may vary.

* ONA Plus Components upon download/delivery

1. ONAP.exe : Parser that analyzes nmon logs and stores the data in the database.

2. ONAPService.exe : Service program running ONAP.exe in background.

3. ONAPSetting.exe : For users’ convenience, utility program for ONAP configuration, TAG and table management.

4. I_want_to_use_this.exe : ONAP and database configuration program in an installation stage.

5. mariadb-10.1.11-win32 : To help database installation, included database in installation package.

6. ONAP-ex : User program.


* Installation Steps

1. Execute ONAplus_setup.exe.

2. Choose “I accept …”.


3. Choose a location to install. The drive must have enough space to save data.

4. Complete setup process with below option to run a configuration program.


5. After installation, “I_want_to_use_this.exe” is executed through “Launch the program” checked at last stage of

installation.

A “User Account Control” warning dialog may appear on occasion due to unknown publisher. Please ignore the warning

and continue.

If checked, the ONAP-ex(viewer) may be

used from a remote PC

ONAP.exe(Parser) will delete nmon log file after processing. If not checked, ONAP.exe(Parser) will move completed log file to “Complete” folder. This configuration is saved in “LogFiles” section of ‘Config\ONAP.ini’ as “CompleteLogDeletion”. For example, [LogFiles] CompleteLogDeletion=0 User may modify this manually, and a change will be automatically applied.

ONAP.exe(Parser) will save filesystem trend data. This configuration is saved in “FilesystemTrend” section of ‘Config\ONAP.ini’ as “use”. For example, [FilesystemTrend] Use=1 User may modify this manually, and a change will be automatically applied.

ONAP.exe(Parser) will save “process” or “disk and network” trend data. This configuration is saved in “ProcessTrend” or “DiskTrend” section of ‘Config\ONAP.ini’ as “use”. For example, [ProcessTrend] or [DiskTrend] Use=1 User may modify this manually, and a change will be automatically applied.

ONAP.exe(Parser) will be executed in the

background as a windows service with service

name “onap service”.


* Refer to below used in database configuration.

Create onap as the database, and onapuser as database user

MariaDB [none]> create database onap; /* onap database creation */

MariaDB [none]> grant all on *.* to 'onapuser'@'localhost' identified by 'onappassword'; /* add user and privileges */

MariaDB [none]> flush privileges; /* apply change */

* onapuser must have all privileges for copy operation.

* Refer to Configuration of ONA Plus

- ONAP.ini is included in “Config” folder as a configuration file template, and may be modified to suit your database.

[Database]

Address=localhost

Port=18891

Type=mariadb

Database=onap

User=onapuser

Password=onappassword

/* the User and password entry will disappear once ONAP is executed. */


STARTING ONA Plus

1. Copy nmon files to NMONLogs folder of ONAP.

1) After installation, ONAP(Parser service process) is running in background, and looking in “NMONLogs” folder.

2) ONAP reads the log file and processes if nmon log file is copied to “NMONLogs” folder.

3) After ONAP’s work, the nmon log file is deleted or moved to “Complete” folder depending on the option in

ONAP.ini as below;

[LogFiles] CompleteLogDeletion=0 /* move to Complete folder in case of 0, and delete in case of 1 */


2. To analyze the result from nmon log files, execute ONAP-ex.exe as user program.

Dialog box below appears:

- Database Type: Choose database type for use as ONA Plus repository.

- Address: Address of ONAP database. ONAP-ex may run remotely.

- Port: Database connection port.

- Database Name: Database name for ONAP.

- Username: Database user name for ONAP.

- Password: Password for database user.

- Save password: Database encrypted user password will be saved if checked.

- Choose last period from now.

- Start Date: Start date for analysis.

- End Date: End date for analysis.

- All hosts: ONAP-ex will show all hosts if checked; if unchecked, only specified hosts you list in the memo box

below will show. (the memo box recognizes each input entry as a pattern – e.g. if you enter “test”, every

hostname containing “test” will be shown)

- Normal window mode: Enlarge ONAP-ex window if not checked

- Skip all filesystem list: ONAP-ex will not show all filesystems of all hosts in the Filesystem section if checked.

Loading time will be reduced if checked.


USING ONA Plus

ONA plus starts with the window below:

1. Report (requires installed and running MS-Office)

Choosing “Report” activates the following dialogue box:

- For all servers: create an excel document consisting of a summary sheet of all servers; plus one sheet per server.

- For selected servers: create an excel document consisting of a summary sheet; plus one sheet per selected

server from the lower left server list.

- Summary for all servers, and each server for selected servers: create an excel document consisting of a summary

sheet of all servers; plus one sheet per server from the lower left server list.

- Summary only for all servers: creates an excel document consisting of a summary sheet of all servers.

1. Report

2. Band Ratio

3. Server list

4. Right Side Panel

- Summary View

- Direct View

- ChartList Detailed

- Filesystem

5. CPU Pool (IBM Virtualization)


- Summary only for selected servers: create an excel document consisting of a summary sheet of selected servers

in the lower left server list.

* Example Report excel document

- Summary sheet:

Below fields are shown:

Hostname / CPU-AVG / CPU-MAX / BandRatio List / MEM-AVG / MEM-MAX / SWAP-AVG / SWAP-MAX / Disk-AVG / Disk-

MAX / Network-AVG / Network-MAX / Operating System / Patch Level / MachineType(Model) / Serial / CPU Count /

Clock Speed(MHz) / Memory Size(MB) / Good Memory Size(MB) / PagingSpace Size(MB) / IP Address / Sub Netmask /

Gateway / Lpar Number&Name / Lpar Type / Lpar Mode / Hardware / Kernel / Logging Program Name / Logging

Command / Logging Program Version / Logging User


- Individual server sheet

Each sheet includes the individual server’s data including the filesystem, and all statistics of each log file.


2. Band Ratio

The Band Ratio is the average value above the Band Ratio Indicator, such as 50%, 60%, …, and 95%. It is a very useful

supplemental indicator used in conjunction the average value and maximum value to determine how busy a server is.

1) For example, a 60 % Band Ratio means how many occurrences of CPU usage above 60% of the total data count. Please refer to the Band Ratio White Paper for more detail. 2) The vertical axis value displays on the left of the data label; and the horizontal axis value displays on the right. 3) Users may switch the left / right value positions with a left mouse click.

- The yellow encircled point box (kvqjufs) means that for server kvqjufs, (CPU usage chart below from Chartlist Detailed view) CPU usage above 95%

occurred 9.5 times out of 100; and CPU usage above 70% occurred 26.4 times out of 100.

- The green encircled point box (vbqec2) means that for server vbqec2, (CPU usage chart below from Chartlist Detailed view) CPU usage above 95%

occurred 2.9 times of 100; and CPU usage above 70% occurred 100 times out of 100.

- The red encircled point box (MJDPECQ2) means that for server MJDPECQ2, (CPU usage chart below from Chartlist Detailed view) CPU usage above

95% occurred 85.4 times of 100; and CPU usage above 70% occurred 100 times of 100.


3. Server list

Left clicking on any item in the server list activate the following dialogue box:

- Update Performance data by selected item: display detailed performance information of the selected server.

- Find: activate the find edit box, and search for the server item based on your input as a pattern.

- Use PhysicalCPU as CPU% if virtualized: If a server is IBM CPU virtualization, CPU usage is changed to PC*100/VP instead of typical CPU

usage, and the color became different as below.

(PC : Processor Consumed or Physical CPU Consumed / VP : Virtual Processor or Online Virtual CPU)

- Copy all items to clipboard: copy entire contents list to the clipboard. User may paste this to an excel worksheet or notepad.

- Copy selected items to clipboard: Copy contents of selected servers to the clipboard.

- Show Band Ratio caption for selected list: Band Ratio Point Chart will display caption for selected items.

Average

value of

User+Sys

Average of

User

Average of

Sys

Maximum

value of

User+Sys

Average of

Wait (Gray

color region)

Band Ratio of 70%,

80%, 90% and 95% In order, 95%, 90%,

80% and 70%

Average of

Memory usage

Average of

Filecache usage

Maximum of

Memory usage

Average of

Swap usage

Maximum of

Swap usage


- OS parameters

Choose servers using shift or control key to select several servers, and mouse right-click.

* It also shows “change history” during selected time period when ONAPex.exe is executed.


4. Right side panel

4-1. Summary View: Display basic statistical results for CPU, Memory, Swap.

Displays the count of servers with average values in the specified range for each item (CPU, Memory and Swap),

The data label (14.3 / 19.9 / 103) of the example to the left means that the count of servers having

average CPU of 0%~10% is 103; and average value of CPU of these servers is 14.3%; and maximum

value among these is 19.9%.

If user clicks on a bar or line, the server list window will display for viewing.


4-2. Direct View

- The bottom chart displays the performance data for CPU, Memory, or Disk for the entire period.

- The CPU, Memory, and Disk charts above it display performance data for the time range selected via mouse click

from the bottom chart.

- The time duration list

provides several

predefined values,

including “Specify a

period”.

Current hostname selected.

This server will be selected in

the server list when you

double-click this label.

Time of selected range for above CPU,

Memory, and Disk charts.

This label, and a Virtual Box below it, follows

mouse movement on this bottom chart.

User may select a time

duration for the selected

range by clicking on this label.

User may choose from

CPU, Memory, or Disk

performance items for

the bottom chart

Clicking this label will show

a predicting trend line chart

User may lock this time

selection even if another

server is selected.


- The following dialogue box activates when you click the “Predicting Trendline“ label. The Predicting Trend line

chart utilizes a general predictive algorithm, aided by standard deviation for representing CPU fluctuations.

- Predicting trend line will disappear when you click again on this label.

* Predicting the future trend via the general predicting trend line is usually not useful as CPU fluctuations cause it to hit

100% early. However, it becomes practical and quite useful if combined with standard deviation.

- Every viewer-provided chart has a popup menu as below:

1) Copy chart image to clipboard: save chart image to clipboard; user may paste to any document.

2) Copy chart data to clipboard: copy chart raw data to clipboard; user may paste to any document, such as

excel.

3) Chart time label configuration: allows user to configure how time labels of charts are shown.

* Rotate time labels option is useful to identify time, but will take up more space.

Predicting trend line Standard deviation

for CPU fluctuation


* Chart time label configuration

1) Rotate bottom chart time labels: Adjusts orientation of time labels

in bottom chart.

2) Rotate other charts time labels: Adjusts orientation of time labels in

other charts.

3) Date format: Defines how to show date format.

4) Time format: Defines how to show time format.

5) Show time labels of lower chart(s) only: Refer to below.

1) Rotate bottom chart time labels.

vs

2) Rotate other charts time labels.

vs

5) Show time labels of lower chart(s) only.

- Upper charts do not show time labels.


4-3. Chart List Detailed

- The Detailed Chart list shows several performance data for a time range selected on the bottom chart.

- When a chart series is clicked, the clicked series and corresponding axis will become thicker, with a

corresponding information window as below.

* This Information window has buttons for Close; Copy to clipboard; and Show/Hide legend is similar to

“Show/Hide Legend” label.

Legends appear when you click this label

as below. Toggle to show/hide.

Close, Copy to clipboard

and Show/Hide legend

Corresponding axis

becomes thicker

Chart Filtering: Default is “on”. Since it

becomes very slow when a chart has a lot

of lines and data, chart lines having only

low values(ignorable) will be unchecked

and not be shown in the chart.

PID or Command Chart shows process

chart. This is a toggle switch.

Disk/Network button shows each disk

and network performance data.

Expert mode: switches this view to

“Expert mode” letting user arrange all

views.


- There is an additional popup menu item for “Chart List Detailed” as shown below:

- This window shows every performance value of “Chart List Detailed” based on time table.

- The table highlights the corresponding row when some point on the chart is clicked.

When clicked here,


* Process Trend Chart (PID / Command Chart)

- There are two buttons under the “Hostname” label.

1. PID Chart: Process chart shows a trend line with Each PID as Each Chart Line.

2. Command Chart: Process chart shows a trend line with Each Command as Each Chart Line.

(if there are several processes with the same command, they are merged into the same command entry.)

3. Disk/Network Chart: The right side shows three of disk charts and one network chart.

*Note: Including the process and disk/network trend will require increased data storage;

For example, in our test case of 6500 nmon files totalling 30GB: basic performance data was 1.2 GB; filesystem trend

data was 2.1GB; process trend data was 6GB; and disk and network trend data was 6GB.*

- There are 4 kinds of process charts, namely CPU; RSS(RESText+RESData); CharIO(Character IO); and ThreadCount.

- There are 4 kinds of Disk/Network charts, namely Disk Busy%; ReadWrite; Xfer/s; and Network ReadWrite.

* Popup menu appears, letting user change the chart item when chart title is mouse right-clicked.

Process and Disk/Network chart

region

Scroll bar :

Each panel can

be scrolled

separately.

PID or Command Chart, Disk/Network Chart

Mouse right-click at chart title


- Line chart

- Stacked chart

- Adjust to 100%

nmon collects Process CPU based on the concept that 100% is 1core. For convenience, “Adjust to 100%” divides CPU value by CPU Count as shown below:


* Note: Since nmon collects process performance data only when the process consumes CPU, process performance data

is not continuous. The Viewer shows process trend chart based on the following:

If process data does not exist for a certain time period, it is treated as a case of 0% CPU utilization and zero CharIO

(Character IO) activity. However, for RSS and Threads Count, the Viewer will show the previous last value of each item.

No change in RSS or Threads Count is treated as zero CPU consumed, as a change in RSS or thread count consumes CPU

resource. Likewise, zero CPU consumption can mean that there was no Character IO(CharIO).

Therefore, the Viewer handles absence of data with the above idea, instead of displaying discontinuity in the chart.

- Extraction: Creates cron window with the same performance item. This cron window is not fixed as existing charts, and

user can resize and move.

- Sync selection: Other charts of same category such as process command; process pid; disk or network, will be applied

by this chart when sync selection is turned on and user does something.

Applying activities are things such as sort, check/uncheck, order changes, and highlight/unhightlight.


- Expert mode

User may choose items showing in expert mode view throughout below.

In expert mode, a few buttons appear on the right top side as below.

- Return back: Quit expert mode and return back to ChartList Detailed.

- Bring server list: Server list window appears.

- Config Views: Above expert mode view selection window is shown to let user change views. Of course, user may

change each chart item by mouse right-click on the title as below;

- Hide Bottom Chart: The bottom chart letting user change time period to analyze will be hidden.(or appear)

- Hide guide lines: Hides every guide line and label on charts.

- Chart Filtering: Default is “on”. Since it becomes very slow when a chart has a lot of lines and data, chart lines having

only low values(ignorable) will be unchecked and not be shown in the chart.

Mouse right-click at chart title


4-4. Filesystem

The popup menu below appears when you left click on the particular file system.

- Show selected item only: filesystem chart below will display only selected filesystem list.

- Show selected item: filesystem chart below will add selected filesystem to display list.

- Hide selected item: filesystem chart below will hide selected filesystem.

- Show every item: filesystem chart below will show every filesystem.

- Hide every item: filesystem chart below will hide every filesystem.

- Copy to clipboard: copy list contents to the clipboard; user may paste to excel worksheet or an edit program

such as notepad.

Filesystem information

of the selected server

Filesystem information for

all servers.

This is available when “skip

all filesystem list” option is

unchecked at ONAP-ex

initial configuration.

This filesystem information

list for all servers will

disappear when you click

this label.


5. CPU Pool (IBM Virtualization)

- The window below appears when you select “CPU Pool (IBM Virtualization)” label.

- ONAplus presents CPU Pool information automatically based on machine type(model), serial and pool ID.

- The above table will show maximum pc usage and value if pool idle item is available from nmon.

PC in Pool : % of Processor(Physical CPU) consumed based on Pool

Own PC : % of Processor(Physical CPU) consumed based on each partition.

This value can be different from “PC in Pool” because the nmon period of each server may not be the same.

VP : Virtual Processor(CPU). This means the CPU count of the pool in the row representing the CPU pool.

EC : Entitled Capacity. This means the total entitled capacity of the pool in the row representing the CPU pool.

MAX pc usage in pool based on

Pool Idle if provided by nmon

MAX pc value based on Pool

Idle if provided by nmon


Band Ratio and Band Average

A supplemental indicator of performance saturation

* Back ground

In General, IT professionals use the average value and maximum value of a performance item (e.g. CPU usage

percentage) over a specific period to measure or plan for server capacity.

However, servers are not busy for that entire period, only when they are executing specific tasks. The average value will

also include any idle time. For this reason, the average value may not be a sufficient measure of how busy a server is. It

would be greatly advantageous to have a supplemental indicator to increase confidence in what we can infer from the

average values of performance.

Consider the typical CPU behavior below of a server for one day.

The average value of 34.16%, the 96.77% maximum value, and the chart taken together, are sufficient for IT

professionals to understand how busy this server was.

However, without the chart, it’s difficult to ascertain how busy this server was by knowing just the average value and

the maximum value. Unfortunately in practice, you don’t have the luxury to look at the charts unless something triggers

your suspicion. More likely, you have a table listing servers’ average and max values as below, which is useful as you

are also interested and need to compare the server of interest to other servers simultaneously as a group. (in the table

below, server3 is the one charted above)

Hostname CPU AVG% CPU MAX%

server1 35.30% 50.90%

server2 12.80% 72.01%

server3 34.16% 96.77%

server4 47.72% 88.92%

0102030405060708090

100

20

15

-05

-31

17

:01

:10

-07

20

15

-05

-31

17

:38

:11

-07

20

15

-05

-31

18

:15

:11

-07

20

15

-05

-31

18

:52

:10

-07

20

15

-05

-31

19

:29

:10

-07

20

15

-05

-31

20

:06

:11

-07

20

15

-05

-31

20

:43

:11

-07

20

15

-05

-31

21

:20

:11

-07

20

15

-05

-31

21

:57

:10

-07

20

15

-05

-31

22

:34

:11

-07

20

15

-05

-31

23

:11

:11

-07

20

15

-05

-31

23

:48

:11

-07

20

15

-06

-01

00

:25

:12

-07

20

15

-06

-01

01

:02

:11

-07

20

15

-06

-01

01

:39

:11

-07

20

15

-06

-01

02

:16

:11

-07

20

15

-06

-01

02

:53

:12

-07

20

15

-06

-01

03

:30

:12

-07

20

15

-06

-01

04

:07

:11

-07

20

15

-06

-01

04

:44

:11

-07

20

15

-06

-01

05

:21

:12

-07

20

15

-06

-01

05

:58

:12

-07

20

15

-06

-01

06

:35

:12

-07

20

15

-06

-01

07

:12

:11

-07

20

15

-06

-01

07

:49

:12

-07

20

15

-06

-01

08

:26

:12

-07

20

15

-06

-01

09

:03

:12

-07

20

15

-06

-01

09

:40

:13

-07

20

15

-06

-01

10

:17

:12

-07

20

15

-06

-01

10

:54

:12

-07

20

15

-06

-01

11

:31

:12

-07

20

15

-06

-01

12

:08

:13

-07

20

15

-06

-01

12

:45

:13

-07

20

15

-06

-01

13

:22

:12

-07

20

15

-06

-01

13

:59

:12

-07

20

15

-06

-01

14

:36

:13

-07

20

15

-06

-01

15

:13

:13

-07

20

15

-06

-01

15

:50

:13

-07

20

15

-06

-01

16

:27

:13

-07

CPU% (User+System)


In the table above, you conclude with some confidence that server1 and server2 are fine, since they have low average

and max values. However, a high average value with high maximum value for server 3 should trigger suspicions, or

require deeper analysis.

For example, the chart below shows server1- rather low average value and maximum value.

The average value of server1 is quite similar to server3’s average value, but the maximum value for server1 is 50.90%. In

this case, even without the line trend chart available, you probably have nothing to be concerned about. So, low average

and maximum values are clearly not a concern, but a low average value with high maximum value such as server3 ‘s

should warrant additional investigation or concern. This becomes unmanageable when dealing with a substantial

number of servers, either for lack of data, or lack of time.

Enter the band ratio or band average - how does it help in this situation?

0

10

20

30

40

50

60

70

80

90

100

20

15

-05

-31

… 2

01

5-0

5-3

1…

20

15

-05

-31

… 2

01

5-0

5-3

1…

20

15

-05

-31

… 2

01

5-0

5-3

1…

20

15

-05

-31

… 2

01

5-0

5-3

1…

20

15

-05

-31

… 2

01

5-0

5-3

1…

20

15

-05

-31

… 2

01

5-0

5-3

1…

20

15

-06

-01

… 2

01

5-0

6-0

1…

20

15

-06

-01

… 2

01

5-0

6-0

1…

20

15

-06

-01

… 2

01

5-0

6-0

1…

20

15

-06

-01

… 2

01

5-0

6-0

1…

20

15

-06

-01

… 2

01

5-0

6-0

1…

20

15

-06

-01

… 2

01

5-0

6-0

1…

20

15

-06

-01

… 2

01

5-0

6-0

1…

20

15

-06

-01

… 2

01

5-0

6-0

1…

20

15

-06

-01

… 2

01

5-0

6-0

1…

20

15

-06

-01

… 2

01

5-0

6-0

1…

20

15

-06

-01

… 2

01

5-0

6-0

1…

20

15

-06

-01

… 2

01

5-0

6-0

1…

20

15

-06

-01

… 2

01

5-0

6-0

1…

20

15

-06

-01

…

CPU% (User + System)


* Band Ratio

Let’s take server3 as our example.

If we use the 90 percentile as an important performance threshold,

Band Ratio is : [Occurrence count of value is 90% or more] * 100 / [total data count]

13 occurrence * 100 / 1440

Band Ratio (90 percentile) = 0.90%

If we use the 80 percentile as a threshold

88 occurrence * 100 / 1440


If we use 70 percentile as a threshold

0102030405060708090

100

20

15

-05

-31

17

:01

:10

-07

20

15

-05

-31

17

:38

:11

-07

20

15

-05

-31

18

:15

:11

-07

20

15

-05

-31

18

:52

:10

-07

20

15

-05

-31

19

:29

:10

-07

20

15

-05

-31

20

:06

:11

-07

20

15

-05

-31

20

:43

:11

-07

20

15

-05

-31

21

:20

:11

-07

20

15

-05

-31

21

:57

:10

-07

20

15

-05

-31

22

:34

:11

-07

20

15

-05

-31

23

:11

:11

-07

20

15

-05

-31

23

:48

:11

-07

20

15

-06

-01

00

:25

:12

-07

20

15

-06

-01

01

:02

:11

-07

20

15

-06

-01

01

:39

:11

-07

20

15

-06

-01

02

:16

:11

-07

20

15

-06

-01

02

:53

:12

-07

20

15

-06

-01

03

:30

:12

-07

20

15

-06

-01

04

:07

:11

-07

20

15

-06

-01

04

:44

:11

-07

20

15

-06

-01

05

:21

:12

-07

20

15

-06

-01

05

:58

:12

-07

20

15

-06

-01

06

:35

:12

-07

20

15

-06

-01

07

:12

:11

-07

20

15

-06

-01

07

:49

:12

-07

20

15

-06

-01

08

:26

:12

-07

20

15

-06

-01

09

:03

:12

-07

20

15

-06

-01

09

:40

:13

-07

20

15

-06

-01

10

:17

:12

-07

20

15

-06

-01

10

:54

:12

-07

20

15

-06

-01

11

:31

:12

-07

20

15

-06

-01

12

:08

:13

-07

20

15

-06

-01

12

:45

:13

-07

20

15

-06

-01

13

:22

:12

-07

20

15

-06

-01

13

:59

:12

-07

20

15

-06

-01

14

:36

:13

-07

20

15

-06

-01

15

:13

:13

-07

20

15

-06

-01

15

:50

:13

-07

20

15

-06

-01

16

:27

:13

-07

CPU% (User+System)

0102030405060708090

100

20

15

-05

-31

17

:01

:10

-07

20

15

-05

-31

17

:38

:11

-07

20

15

-05

-31

18

:15

:11

-07

20

15

-05

-31

18

:52

:10

-07

20

15

-05

-31

19

:29

:10

-07

20

15

-05

-31

20

:06

:11

-07

20

15

-05

-31

20

:43

:11

-07

20

15

-05

-31

21

:20

:11

-07

20

15

-05

-31

21

:57

:10

-07

20

15

-05

-31

22

:34

:11

-07

20

15

-05

-31

23

:11

:11

-07

20

15

-05

-31

23

:48

:11

-07

20

15

-06

-01

00

:25

:12

-07

20

15

-06

-01

01

:02

:11

-07

20

15

-06

-01

01

:39

:11

-07

20

15

-06

-01

02

:16

:11

-07

20

15

-06

-01

02

:53

:12

-07

20

15

-06

-01

03

:30

:12

-07

20

15

-06

-01

04

:07

:11

-07

20

15

-06

-01

04

:44

:11

-07

20

15

-06

-01

05

:21

:12

-07

20

15

-06

-01

05

:58

:12

-07

20

15

-06

-01

06

:35

:12

-07

20

15

-06

-01

07

:12

:11

-07

20

15

-06

-01

07

:49

:12

-07

20

15

-06

-01

08

:26

:12

-07

20

15

-06

-01

09

:03

:12

-07

20

15

-06

-01

09

:40

:13

-07

20

15

-06

-01

10

:17

:12

-07

20

15

-06

-01

10

:54

:12

-07

20

15

-06

-01

11

:31

:12

-07

20

15

-06

-01

12

:08

:13

-07

20

15

-06

-01

12

:45

:13

-07

20

15

-06

-01

13

:22

:12

-07

20

15

-06

-01

13

:59

:12

-07

20

15

-06

-01

14

:36

:13

-07

20

15

-06

-01

15

:13

:13

-07

20

15

-06

-01

15

:50

:13

-07

20

15

-06

-01

16

:27

:13

-07

CPU% (User+System)


269 occurrence * 100 / 1440


We find for server3, that:

90% threshold band ratio is 0.90%;

80% threshold band ratio is 6.11%;

70% threshold band ratio is 18.68%.

What can we derive from this data? It depends to some extent on your management and understanding of your servers

and resources. In general, for this particular band ratio data, you’re able to determine with some confidence that

server3 is fine for the immediate future capacity-wise. However, with a 70 percentile threshold band ratio at around

18%, it’s indication to either plan a capacity increase in the near future for this server, or flag it for closer scrutiny going

forward.

In Summary, the surest way to analyze state of your servers is to analyze the raw performance data directly, and not rely

on statistically-drawn information. If available and practical, trend line charts are a great help to visualize and

understand the raw data of individual servers.

In the larger picture, the band ratio is especially valuable when IT professionals must analyze the performance of many

servers, and has limited time or resources to analyze each server individually.

First, the band ratio taken with the average and max values weed out servers that are not in any danger with much

greater confidence. Secondly, the band ratio highlight servers that will require future capacity upgrades, or closer

scrutiny and monitoring. In addition, the band ratio average distribution shown graphically (as bar graphs) can provide

an immediate warning of potential danger.

The true benefit is that you get all these without having to analyze each server’s raw data individually.

The band ratio is one of the unique features of onTune nmon Analyzer plus, an indispensable analysis and capacity

management tool for nmon users. ONA + provides a wide, at-a-glance, summary views of your servers most meaningful

0102030405060708090

100

20

15

-05

-31

17

:01

:10

-07

20

15

-05

-31

17

:38

:11

-07

20

15

-05

-31

18

:15

:11

-07

20

15

-05

-31

18

:52

:10

-07

20

15

-05

-31

19

:29

:10

-07

20

15

-05

-31

20

:06

:11

-07

20

15

-05

-31

20

:43

:11

-07

20

15

-05

-31

21

:20

:11

-07

20

15

-05

-31

21

:57

:10

-07

20

15

-05

-31

22

:34

:11

-07

20

15

-05

-31

23

:11

:11

-07

20

15

-05

-31

23

:48

:11

-07

20

15

-06

-01

00

:25

:12

-07

20

15

-06

-01

01

:02

:11

-07

20

15

-06

-01

01

:39

:11

-07

20

15

-06

-01

02

:16

:11

-07

20

15

-06

-01

02

:53

:12

-07

20

15

-06

-01

03

:30

:12

-07

20

15

-06

-01

04

:07

:11

-07

20

15

-06

-01

04

:44

:11

-07

20

15

-06

-01

05

:21

:12

-07

20

15

-06

-01

05

:58

:12

-07

20

15

-06

-01

06

:35

:12

-07

20

15

-06

-01

07

:12

:11

-07

20

15

-06

-01

07

:49

:12

-07

20

15

-06

-01

08

:26

:12

-07

20

15

-06

-01

09

:03

:12

-07

20

15

-06

-01

09

:40

:13

-07

20

15

-06

-01

10

:17

:12

-07

20

15

-06

-01

10

:54

:12

-07

20

15

-06

-01

11

:31

:12

-07

20

15

-06

-01

12

:08

:13

-07

20

15

-06

-01

12

:45

:13

-07

20

15

-06

-01

13

:22

:12

-07

20

15

-06

-01

13

:59

:12

-07

20

15

-06

-01

14

:36

:13

-07

20

15

-06

-01

15

:13

:13

-07

20

15

-06

-01

15

:50

:13

-07

20

15

-06

-01

16

:27

:13

-07

CPU% (User+System)


performance data, organized to give you immediate insight to the state of your servers. At the same time, ONA +

provides detailed charts of the performance data of each server for in-depth analysis.

* Conclusion

1. Average value and maximum value are items showing value exact.

2. Even though these stand for exact value, average and maximum values are not enough to express how busy this

server is because working time and idle time are separated and it is more important to determine whether this server is

busy or not considering working time only.

3. Band ratio will be very useful indicator supplement this weakness of using average value and maximum value only.

Hostname CPU AVG% CPU MAX% Band Ratio by 70% Band Ratio by 80% Band Ratio by 90%

server1 35.30% 50.90% 0.00% 0.00% 0.00%

server2 12.80% 72.01% 0.03% 0.00% 0.00%

server3 34.16% 96.77% 18.68% 6.11% 0.90%

server4 47.72% 88.92% 1.12% 0.83% 0.01%

In addition, it will be very helpful if a user-defined band ratio (such as 95%) is added to above table, next to

predefined band ratio of 70%, 80%, and 90%.


ONAP(onTune nmon Analyzer plus) feature by Band Ratio

ONAP provides an eidetic graph as below:

Below Band Ratio is providing 70%, 80%, 90% and 95% together.

At this table, there is additional bar-graph by Band Ratio.

This bar graph is based on below idea.

Above ‘jupiter’ server has below real CPU performance data over one month.

Above chart is provided by ONAP, and below is by EXCEL.

Average is 42.5% and maximum is 100%, 70/80/90%/95% Band Ratio is 26.4%/19.4%/12.7%/9.5%.

We can get below chart if we sort above real data.

0

50

100

CPU

0

50

100

CPU


We can simplify the result by taking 70% and more as meaningful range like this.

Below bar graph expresses this idea.

With this bar graph, ONAP user can draw CPU utilization in the brain and catch the performance utilization status like a

landscape quickly.

70

80

90

100

CPU


Properly analyzing CPU pools in IBM CPU Virtualization with nmon logs

As useful as nmon is, System engineers attempting to analyze CPU pool with nmon logs will have a hard time due to the

following:

1. The Micro-partitions’ nmon logs in same CPU pool that are needed and used for analysis are not time-synchronized.

2. Not all micro-partitions are guaranteed to be active for the time periods under consideration. Some micro-partitions

may be off for certain periods.

3. Depending on the configuration, nmon may not collect the “used pool CPU%” properly.

If you don’t provide for these gotchas; you will misread the current status of the CPU pool. (derived from simple

summation of pc value of micro-partitions.) Not surprisingly, having to deal with these considerations are a big headache

for system administrators/engineers.

To overcome these problems of analyzing CPU pool(IBM CPU Virtualization), ONA plus provides these enhanced features

to work with standard nmon logs:

1. An encompassing time slot (period) is automatically chosen in order to include every nmon log of every member

micro-partition of the CPU pool.

- This time slot is at least larger than the biggest interval of all these micro-partitions.

- To make it convenient, we use the three factors affecting pc value are: “effective duration”, “own pc” and “pc in pool”.

These three are defined as follows:

* Effective duration (of pool): whole period. In case of pool, the period not used by any micro-partitions is not included.

* Own pc: Average pc based on period of each micro-partition. (Finally, normal average is Own pc)

* pc in pool: Average pc based on effective duration.


Example - Encompassing time period/slot is 1 day.

In this case where the total period is 5 days, the 1st micro-partition was active on the first, second, and the last days (3

time slots), and the 2nd micro-partition was active on the second and fourth day (2 time slots).

During uptime, the 1st micro-partition used 4, 2, 6 pc for the corresponding days; and the 2nd micro-partition used

average 4 and 2 pc for the corresponding days.

The ONA plus methodology is illustrated as below:

Own pc pc in pool Effective Duration

1st micro-partition (4+2+6)/3 = 4 Own pc * 3/4 = 3 3 days

2nd micro-partition (4+2)/2 = 3 Own pc * 2/4 = 1.5 2 days

CPU Pool SUM of above = 4.5 4 days (3rd day is excepted)

* Effective duration of pool: whole period. In case of pool, the period not used by any micro-partitions is not included.

* Own pc: Average pc based on period of each micro-partition. (Finally, normal average is Own pc)

* pc in pool: Average pc based on effective duration.

CPU pool

4 pc 6 pc

4 pc

2 pc 2 pc

1st day 2nd day 3rd day 4th day 5th day

1st micro-partition 2nd micro-partition

When the simple summation method is used, the average pc of pool yields: 1st micro-partition average pc 4 + 2nd

micro-partition average pc 3 = 7.

Simple summation average: 7

ONA plus average: 4.5


This methodology for CPU pools is most effectively conveyed in the ONA Plus chart below:

In addition, the ONA Plus view below promotes easier management.

To reiterate, these results are obtained and presented from standard nmon logs only, without additional information or

manual re-work or manipulation.


10 MICHELLE WAY, PINE BROOK, NEW JERSEY, 07058

[email protected] http://www.teemstone.com

http://www.ontune.us

اشكرً

תודה

감사합니다

Thank you

շնորհակալ եմ

謝謝

děkuji

hvala

tak

dank u

kiitos

merci

მადლობთ

danke

mahalo

köszönö

grazie

ありがとう

dziękuję

спасибо

хвала ďakujeme

gracias

tack

ขอบคณุ

teşekkür ederim

cám ơn

mailto:[email protected]

http://www.teemstone.com/

http://www.ontune.us/

ona plus user guide - ontuneontune.us/wp-content/uploads/2016/11/onaplus_manual.pdfstarting ona plus...

Documents