Server Hardware > About server hardware |  | next

# About server hardware

A server hardware resource represents an instance of server being managed or monitored by HPE OneView.

For a managed server hardware resource, the configuration can be applied by assigning a server profile to it.

Servers also are associated with a server hardware type. A server hardware type captures the details of the relevant physical configuration for server hardware and defines which settings are available to server profiles that are to be assigned to that type of server hardware.

There are different ways servers can be added into HPE OneView.

Managed | HPE OneView manages the server enabling you to apply configurations, assign server profiles, monitor operation status, collect statistics, and alert users to specific conditions. Server blades that are in a managed enclosure will automatically be added as managed. Managed servers require an HPE OneView Advanced or an HPE OneView Advanced w/o iLO license.
Monitored | HPE OneView monitors the hardware for inventory and hardware status only. The server can be managed outside of HPE OneView. Server blades that are in a monitored enclosure will be added as monitored. Monitored servers use a free license called HPE OneView Standard.

#### More information

Server hardware management features
Server hardware monitoring features
About unsupported server hardware
License types

### Connectivity and synchronization with the appliance

The appliance uses the iLO or Onboard Administrator to monitor the overall health status of the server, including connectivity. If the appliance loses connectivity with server hardware, an alert is displayed until connectivity is restored. The appliance attempts to resolve connectivity issues and clear the alert automatically, but if it cannot, you have to resolve the issue and manually refresh the server hardware to synchronize it with the appliance.

The appliance also monitors server hardware to remain synchronized with changes to hardware and configuration settings. However, some changes to devices made outside of the control of the appliance (from iLO or the OA, for example) might cause them to lose synchronization with the appliance. You might have to manually refresh devices that lose synchronization with the appliance.

You can manually refresh the management configuration and status between the appliance and server hardware from the Server Hardware screen.

#### More information

Resolve connectivity issues between the appliance and server hardware

### About monitored server hardware

You can add rack servers or server blades in order to inventory and monitor the hardware. This is useful when you have servers that have already been deployed.

Monitoring allows you to monitor power, cooling, hardware health, and utilization. You can power on and off the server, iLO remote console, and review inventory. You will also get email notification, SNMP trap forwarding, and optional 1 year 9x5 support.

The monitoring feature is available for all G6 and later ProLiant servers with iLO 2, iLO 3, or iLO 4. If a server is being monitored by HPE OneView, you can still manage the enclosures, server profiles, and Virtual Connect infrastructure through VCM or VCEM. You cannot manage server profiles for monitored server hardware in HPE OneView.

A benefit of monitoring server hardware is that the basic functionality of inventory and monitoring can be done with a free license called HPE OneView Standard.

OneView can configure the servers’ iLO to send their sysLogs to a remote destination. See the HPE OneView REST API Reference documentation of the PATCH operation on /rest/serverhardware for additional details about how to perform an sysLog operation.

To add a server blade for monitoring, see Add a c7000 enclosure to monitor the hardware.

## About unsupported server hardware

The appliance cannot manage unsupported server hardware. However, you can place unsupported server hardware in enclosures or racks. Adding unsupported server hardware to the appliance enables you to account for the physical space it occupies in an enclosure or rack for planning and inventory purposes.

The appliance displays basic information about unsupported server hardware that it obtains from the iLO or the OA.

When the appliance detects unsupported server hardware, it places the hardware in the `Unsupported` state. You can perform a remove action on unsupported server hardware to remove it from the appliance.

| NOTE: Unsupported DL servers can only be added via an intelligent iPDU.

## How the iLO is changed as a result of HPE OneView management

When server hardware is being managed by the appliance, the following configuration changes are made to the iLO on the server:

- A management account (_HPOneViewadmin) is created and can be viewed on the iLO Overview and User Administration screens.

- SNMP is enabled and the appliance is added as an SNMP trap destination.

  | NOTE: Health monitoring is not enabled on ProLiant G6 or ProLiant G7 iLO 3 server hardware until the management agents are installed on the OS and the SNMP service is configured with the same SNMP read community string shown on the Settings screen.

- NTP is enabled and the appliance becomes the server hardware’s NTP time source.

- An appliance certificate is installed to enable single sign-on operations.

- iLO firmware is updated to the minimum versions listed in the HPE OneView Support Matrix for managed servers.

- The iLO time zone is set to `Atlantic/Reykjavik` as recommended by the iLO documentation.

  The time zone setting determines how the iLO adjusts UTC time to obtain the local time and how it adjusts for daylight savings time (summer time). For the entries in the iLO event log and IML to display the correct local time, you must specify the time zone in which the server is located.

  If you want iLO to use the time provided by the SNTP server, without adjustment, configure the iLO to use a time zone that does not apply an adjustment to UTC time. In addition, that time zone must not apply a daylight saving time (summer time) adjustment.

  There are several time zones that fit this requirement. One example is the `Atlantic/Reykjavik` time zone. This time zone is neither east nor west of the prime meridian and time does not change in the spring or fall.

#### More information

Enabling health monitoring for legacy servers
Settings: Appliance Networking
Server Hardware

prev | up | next
Adding a server | home | Server Hardware states

Copyright © 2013, 2016 Hewlett Packard Enterprise Development LP