Extracting Resource Allocation Data for Chargeback in a HP Virtual Server Environment for HP Integrity Servers

 va00-cplx_USE4452HL6 is a complex server divided into two nPar workloads.
 va01sv is a noncomplex server with 4 VM guest workloads running on it. It also includes the
VSE-created Other workload.
 va02cm is a noncomplex server with two user-defined fss workloads and the additional VSE-
created Other fss workload.
 legacy01, legacy02, and legacy03 are noncomplex servers with whole OS workloads.
CLI: mxnode and mxquery commands
HP SIM keeps many parameters about systems it has detected in its database. The mxnode command
provides a simple tool to list and obtain basic data about servers. The following example command,
which includes the –ln flag, displays a simple listing of the servers that are managed nodes from a
HP SIM perspective:
CMS # mxnode -ln
va01sv
va03sa
legacy01
va00mp
va00vm00
va00vm03
va00-cplx_USE4452HL6
va00vm01
va02cm
va00vm02
legacy03
legacy02
va00np00
va00np10
CMS #
The next step is to determine which servers on this list are physical HP 9000 and Integrity servers. The
output from the mxnode command output for an individual server includes parameters that can help
with this identification. The mxnode –ld command displays the following detailed data for a
specific server:
CMS # mxnode -ld va01sv
System name: va01sv
Host name: va01sv.zko.hp.com
IP addresses: 16.116.90.85
OS name: HPUX
OS revision: 11.23
OS revision text: HP-UX B.11.23 U
OS vendor: HP
…
Device type: Server
Device subtype: HPVMHost
Device subtype: HPIntegrity
Device subtype: SMI
Device subtype: Storage
Model: ia64 hp server rx4640
…
CMS #
For a physical HP 9000 or Integrity server, the Device type and Device subtype fields have the
following values:
35