HP rp7440 nPartition Administrator's Guide, Second Edition - Page 41

Table 1-5 Complex Profile Group Details (continued) Complex Profile Group Description and Contents The Partition Configuration Data contains configuration details specific to each nPartition in the complex. Each nPartition has its own Partition Configuration Data entry, which may be modified by administrators. The service processor (MP or GSP) has a copy of the Partition Configuration Data for every nPartition. Each cell has a copy of the Partition Configuration Data entry for the nPartition to which it is assigned. Partition Configuration Data includes this data for each nPartition: • HP 9000 server components (unused on HP Integrity servers) - These components apply only on HP 9000 servers, but are present on HP Integrity servers for compatibility: Primary Boot Path, HA Alternate Boot Path, Alternate Boot Path, Console Path, Keyboard Path, Boot Timer, Known Good Memory Requirement, Autostart and Restart Flags, and CPU Flags (e.g. Data Prefetch setting). • Cell use-on-next-boot values - Specifies whether the cell is to be an active or inactive member of the nPartition to which it is assigned. • Core Cell Choices - Up to four cells preferred to be the core cell. • Partition Number - The partition number; not user-configurable. • Profile Architecture - Specifies whether the current Partition Configuration Data applies to the HP 9000 server architecture or HP Integrity server architecture; not user-configurable. • nPartition Name - The nPartition name, used in various displays. • Cell Failure Usage - Specifies how each cell in the nPartition is handled when a processor or memory component fails self-tests. Only activating the cell to integrate it into the nPartition is supported (the ri failure usage option, as specified by the parcreate and parmodify commands). • IP Address - If set, should be consistent with the IP address assigned to the nPartition when HP-UX is booted. Not actually used for network configuration, but for information only. Remote and Local Management of nPartitions You can remotely manage cell-based servers using either the Enhanced nPartition Commands or Partition Manager Version 2.0. The Enhanced nPartition Commands and Partition Manager Version 2.0 also can run on an nPartition and manage that nPartition and the complex to which it belongs. The ability to remotely manage a server based on the HP sx1000 chipset or HP sx2000 chipset is enabled by two technologies: the Web-Based Enterprise Management infrastructure (WBEM) and the Intelligent Platform Management Interface (IPMI). A brief overview of these technologies is provided first, then explanations of how to use the tools to locally and remotely manage cell-based servers are provided. Intelligent Platform Management Interface (IPMI) The nPartition management tools perform their functions by sending requests to the service processor. These requests are either to get information about the server or to affect changes to the server. On the first generation of cell-based servers (the HP 9000 Superdome SD16000, SD32000, and SD64000 models; rp7405/rp7410; and rp8400 servers) a proprietary interface to the service processor was implemented. This interface relied on system firmware to convey information between HP-UX and the service processor. This in turn required that the nPartition management tools run on an nPartition in the complex being managed. The service processor in all sx1000-based or sx2000-based servers supports the Intelligent Platform Management Interface (IPMI) as a replacement for the proprietary interface mentioned above. IPMI is an industry-standard interface for managing hardware. IPMI also supports value-added capabilities, such as HP's nPartition and complex management features. Remote and Local Management of nPartitions 41