SNMP trap monitoring is performed simultaneously with the above phases. SNMP trap monitoring establishes communication to the SNMP trap service and is not a factor in performance characteristics unless a significant number of SNMP traps are generated into the network.

Factors influencing performance characteristics of the monitor service

Number of registered HP BladeSystem c-Class enclosures

The connection, data collection, and monitoring phases are processed on a per enclosure basis. Adding more enclosures to a monitor service increases system and network utilization.

Number of components in an enclosure

The duration of the data collection phase is related to the number of components in an enclosure (for example, number of server blades, storage blades, and interconnect switches). The number of components is not a significant factor in capacity planning.

Rate of configuration changes and error events to enclosures

Any configuration change with an enclosure will trigger the data recollection phase. If a failing component continually changes between healthy and degraded states, every state change triggers the data recollection phase and causes additional load for the monitor service while the information updates.

Connection recovery

The monitor service uses heartbeat monitoring to recover the connection if it is disrupted for 60 seconds or longer. If no heartbeat is detected for a connection, the current connection disconnects and a new connection starts. If there is a network infrastructure issue that causes instability between the monitor service and the HP Onboard Administrator, the monitor service will be busy re-establishing connection to the OA until it succeeds.

Best practices based on these factors

Move the monitor service to non-Operations Manager servers

If the Operations Manager server is highly utilized, you may not want the monitor service to share that same resource. You can move the monitor service to a managed node to free up resource sharing from the Operations Manager server. Identify an under-utilized managed node in a good network infrastructure for both the Operations Manager and HP Onboard Administrator. After the monitor service is configured on the managed node, the management pack automatically discovers the monitor service, and the Operations Manager console displays enclosure information after the next Operations Manager agent discovery cycle.

To install the monitor service on a managed node:

1.Bring the installation kit on the managed node and install it with the custom setup.

2.Select the monitor service and the monitor manager.

3.Use the monitor manager to register enclosures.

The login information of enclosures cannot be copied from one monitor service node to another node because the login information is securely encrypted and protected.

Capacity planning guidelines and best practices 41

Page 41
Image 41
HP OneView for Microsoft System Center manual Best practices based on these factors