P00101_-_HP_Mgmt_Proc_Lite_Profile

Version 2.1.1 17
Figure 4 represents a possible implementation of the HP Management Processor Lite profile. In this
example, the system has 2 Management Processors – MP1 is enabled (active) and MP2 is disabled
(inactive). MP1 and MP2 belong to the collection MPCollection1 and because both MP1 and MP2 are
reporting statuses of ‘OK’ and their respective HP_MemberOfCollection.Included properties have values
of TRUE, the overall group operational status is also OK. Because MPCollection1 is instantiated, the
GroupOperationalStatus is participating in overall system status. FW1 and FW2 are the HP_MPFirmware
instantiations representing the MP1 and MP2 firmware respectively.
For simplicity, not all properties are shown.
Figure 4 – Management Processor Lite Profile: Example Object Diagram
Figure 5 represents a possible implementation of the HP Management Processor Lite profile. In this
example, the system has 1 Management Processor – MP1. MP1 belongs to the collection MPCollection1.
Because MPCollection1 is instantiated and HP_MemberOfCollection.Included property has a value of
TRUE, the GroupOperationalStatus is participating in overall system status. The on-board network
interface is in use in this example and is reporting that it is currently disconnected from the network.
However, in this example the provider does not wish for the NIC status to participate in overall MP status
(and as a result, overall system status) and therefore has not populated the
HP_ManagementProcessor.OperationalStatus[1] property. The overall resulting MP status reported in
HP_ManagementProcessor.OperationalStatus[0] is therefore OK and this status is forwarded to
participate in overall system status via the HP_MPCollection.GroupOperationalStatus[0] property.