Server workflows for HP Matrix Operating Environment

Integrity c-Class blades not using Virtual Connect and rack-mount servers

As noted earlier, Matrix OE is able to automatically gather information regarding (and perform power operations on)

blades using Virtual Connect. OO workflows are needed for Integrity c-Class blades not using Virtual Connect, or

Integrity rack-mount servers.

The blades/servers should use the standard HP Matrix OE – VSE suite for Integrity license:

 Integrity c-Class Blades not using Virtual Connect

o <serverModel>Integrity BLXXXc GX<serverModel>

o <cpuFamily>HPIntegrity</cpuFamily>

 Integrity rackmount

o <serverModel>Integrity rxXXX iX<serverModel>

o <cpuFamily>HPIntegrity</cpuFamily>

The mechanism of XML file annotation enables the specification of additional servers which can be managed with the

existing workflows. Managing additional types of servers (e.g., HP servers with power commands different than the

iLO2 commands in the existing workflow) will involve adding a branch in the existing flow to handle that specific set

of servers. Figure 6 shows the main Get Server Info workflow, and Figure 7 shows the subflow to gather the power

status of a server.

Figure 6: Get Server Info main workflow