HP Insight Dynamics 6.0 software without OpenSSH on HP ProLiant and Integrity Servers Running Microsoft® Windows®

4
HP Integrity nPartition configuration
HP Insight Dynamics provides capabilities for managing nPartitions on supported HP Integrity servers.
Read-only access to HP Integrity servers does not require OpenSSH. When OpenSSH is not installed on
HP Integrity nPartition servers running Microsoft® Windows®, all configuration changes must be made
by directly communicating with the management processor in the nPartition server. Follow these steps
to direct the Partition Manager to communicate directly with the management processor and enable
configuration changes without relying upon OpenSSH:
1. Make sure IPMI over LAN is enabled on the management processor for the managed system.
2. Open Partition Manager by clicking on the Partition Manager icon in Virtualization Manager
for an nParition system or nPartition complex.
3. Expand the Tools menu in the right-hand menu of Partition Manager.
4. Click on the Switch Complexes... link.
5. In the “A remote partitionable complex” section, enter the hostname or IP address of the nPartition’s
management processor, and the IPMI password.
6. Perform necessary management operations.
Related whitepapers
The HP Systems Insight Manager whitepaper “Secure Shell (SSH) in HP SIM 5.x” provides a detailed
background and explanation for the benefits of installing OpenSSH when managing systems with HP
Systems Insight Manager. Consult this document for additional details on the features of HP Systems
Insight Manager which will not function on systems without OpenSSH. The document can be found at
the following location:
http://h10018.www1.hp.com/wwsolutions/misc/hpsim-helpfiles/hpsim_5_ssh.pdf
Conclusion
The HP Insight Dynamics product has several features, which depend on OpenSSH being present for
HP ProLiant and Integrity servers running Microsoft® Windows®. For environments where OpenSSH
is not desired, HP Insight Dynamics is supported. This paper described the features which depend
on OpenSSH and require alternate procedures to fully configure, troubleshoot, and manage such
environments where OpenSSH is not present.