MSI MD-3000 Technical Information download pdf (Page 264)

256

 Index

Array Perf: smi-s

Controller Perf: calculated by Profiler. Aggregate the performance values for all

the luns that belong to specific controller.

LUN Perf: smi-s

Disk Perf: API. Currently using the Crystal (10.10) version API. In order to

ascertain disk performance from an array, the controller firmware minimum

version must also be Crystal release (7.10). The 10.10 version of the API was

built against jdk 1.4, which matches with the jdk used in the Profiler agent at the

time of the 4.8 release. The 10.15 (Crystal maintenance) and 10.30 (Emerald)

release was compiled against jdk 1.5, and is the reason it is not used.

Volume Group Perf: calculated by Profiler. Aggregate the performance values

for all the luns that belong to specific raid group.

Q: Why is disk performance not showing up?

A: The controller firmware must be version 7.10 or greater. We use the API to

gather the data, and there is a dependency on the controller firmware to be

greater than 7.10. A trap is sent to Profiler if the minimum version is not met.

You might hear the controller versions referred to by name, which are:

6.60 - Chromium (no disk perf avail, only in this list to show firmware name)

7.10 - Crystal

7.15 - Crystal maintenance

7.30 - Emerald (which is the xbb2)

7.36 - Crystal/Emerald 4Q08 Maintenance

7.50 - Aurora (2009)

7.60 - Allegheny (2009)

8.10 - Flint (2009)

Q: Is any configuration required to get disk performance to show up?

A: No configuration required on the agent nor from Profiler gui. The disk

performance uses LSI’s API (symsdk.jar) in conjunction with the smi-s provider to

ascertain the disk performance. The API requires the IP addresses of the

controllers. The IP addresses are obtained from the smi-s provider; therefore,

you must have the smi-s settings configured correctly.

1 2 ... 259 260 261 262 263 264 265 266 267 268 269 ... 284 285

No comments

MSI MD-3000 Technical Information Page 264