Discovery of gen8 servers – HP Systems Insight Manager User Manual
Page 48
2.
Discover the Virtual Center first to which the ESXi 5.0 Host is registered.
Make sure Virtual Center credentials are properly entered for the Virtual Center and the node
has the subtype set as “Virtual Center”.
If a node is Virtual Center, provide the Virtual Center credentials:
a.
From the System Page
→Edit System Credentials select all the credential and click
the Edit Credential button. Select Show Advanced Credentials, select the VME tab
and provide the vCenter credentials.
b.
The credentials will be set and will trigger a discovery over the node again, which will
identify the node as a “Virtual Center” node.
3.
If you discover the ESXi host in “Lockdown Enabled” mode, no credentials are required.
Neither Insight managed system setup wizard nor Configure or Repair Agents works in
“Lockdown Enabled” mode.
4.
Migration from “Lockdown Disabled” to “Lockdown Enabled” resets the credentials.
5.
Migration from “Lockdown Enabled” to “Lockdown Disabled” will require a discovery task
with the appropriate credentials.
Discovery of Gen8 servers
Discovery for a Gen8 server must happen through the IP address of the host server’s ILO4 IP
address. If it is a blade server, you can discover the server through the Onboard Administrator IP
address. If the host IP address is used, it will be discovered, but will not include all the HP
Management Instrumentation, as this now all comes from the iLO4. It is the iLO4 which makes all
the proper associations (along with Onboard Administrator if it's a blade). The host is fully off
loaded from the system management tasks.
Discovery for the Gen8 with host-based agents fully installed, properly configured, and agentless
mode disabled, can be discovered through a number of ways. This host IP is the correct place to
find all you would need. Additionally, an Onboard Administrator IP if the host is a blade, is also
allowed here. Since this is using host-based agents, the iLO4 can be viewed as a pass through to
the host, and could be used as well, but is treated as a management processor, not a host NIC.
48
Discovery