HP Device Monitor (v 1.2) for Microsoft System Center User Guide Abstract This guide provides information on using the HP Device Monitor version 1.2 to monitor hardware components in an HP OneView for Microsoft System Center environment (formerly HP Insight Control for Microsoft System Center), with the exception of HP OneView appliances which are monitored by the HP OneView Configuration Dashboard.
© Copyright 2008–2014 Hewlett–Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Warranty The information contained herein is subject to change without notice.
Contents 1 Overview..................................................................................................5 Introduction..............................................................................................................................5 Product operation.....................................................................................................................5 Supported DMS configurations.........................................................................................
Windows SNMP Trap Service is required for DMS but is disabled on servers using SCOM 2012 for network monitoring.......................................................................................................27 Suggested action..........................................................................................................27 SCOM does not discover devices.........................................................................................27 SCOM does not alert managed devices.............
1 Overview This guide is intended for system administrators who use the HP Device Monitor and other HP applications and tools to manage hardware components in a Microsoft System Center environment. NOTE: The HP Device Monitor is not used to monitor HP OneView appliances; they are monitored by the HP OneView Management Pack. For more detailed information, see the HP OneView Management Pack User Guide.
Supported DMS configurations SCOM version DMS location 2012 SP1 Local to SCOM server or Remote DMS 2012 2007 Up to 505 Maximum number of VC domains2 per DMS Up to 505 Maximum numbers of servers per DMS3 Minimum recommended memory Minimum recommended CPU cores per server4 250 Agentless 8-12 GB 4 8-12 GB 4 8-12 GB 4 250 VMware 250 Linux Local to SCOM server or Remote DMS Up to 505 Local to SCOM server or Remote DMS Up to 305 Up to 505 250 Agentless 250 VMware 250 Linux Up to 305 100 A
2 Using the HP Device Monitor Console The DMC provides the capability to connect to one or more DMS instances to configure devices for management inside of the System Center Operations Manager. The DMC enables you to configure the required credentials and configuration information for each managed device. The DMC window includes the following panes: • Device Monitor Connections Displays the current DMS connections. The pane also displays the status of each monitor connection. See Table 1 (page 8).
Table 1 Device Monitor Connection status Icon Status Description Connected to DMS The selected Device Monitor Connection is connected to the DMS. Disconnected from DMS The selected Device Monitor Connection is disconnected from the DMS. HP Device Monitor Service connection A problem has caused the connection to be lost. When the problem error has been solved, the connection can be reestablished.
Removing a DMS connection Removing a connection disconnects it from the DMS and deletes the connection from the Device Monitor Connections pane. To reestablish the connection, it must be added again. 1. Open the DMC. 2. Select the monitor connection to remove. 3. In the Device Monitor Connections pane, click the Remove Connection icon. The connection is removed. TIP: You can also remove a connection by right-clicking it and selecting Remove.
NOTE: • This option is not available when connected to DMS version 1.0. Add Virtual Connect Domain Adds virtual connect domain. Adding a virtual connect domain 1. Open the DMC. NOTE: 2. You must use an administrator account to run DMC. Select the monitor connection to which you are adding the device. The current devices on the connection are displayed in the Discovered Devices pane. 3. In the Actions pane, click Add Virtual Connect Domain.
4. Enter the device IP Address or DNS Name. IMPORTANT: If a Linux or VMware ESX server is added that has the same host name as an existing server device, the server will be added but the existing Linux or VMware ESX server will no longer be displayed in the SCOM console. To avoid this situation, do not assign the same host name to multiple devices. 5. Enter the Community String. The community string must have read access to the SNMP agent of the target system. 6. Click OK.
4. 5. Enter the device IP Address or DNS Name of the server's iLO Management Engine. Enter the Community String. The community string must have read access to the SNMP agent of the target iLO Management Engine. 6. Click OK. If the information is valid, the device is added to the Discovered Devices pane. Adding an Onboard Administrator 1. 2. Open the DMC. Select the monitor connection to which you are adding the device. The current devices on the connection are displayed in the Discovered Devices pane.
5. Click Remove. The devices are deleted from the Discovered Devices pane. TIP: You can also delete a single device by right-clicking it and selecting Delete. Updating device configuration If necessary, you can update the credentials used to access a monitored device. TIP: • The Onboard Administrator credentials must be updated in the DMC if the credentials are changed on the managed enclosure's Onboard Administrator.
4. 5. Enter the appropriate credentials: • If you are updating a Linux, VMware, or Agentless server, enter the Community String. • If you are updating an Onboard Administrator, enter the credentials. • If you are updating a Virtual Connect Domain, enter the credentials. Click OK.
3 Using Windows PowerShell with HP Device Monitor Many of the DMC tasks can also be performed using Windows PowerShell, the Microsoft command console, and scripting language. PowerShell enables you to create scripts that can automate many of the device monitor tasks. When the DMS is installed, the PowerShell cmdlets in this chapter are available to add and remove managed devices. If the modules are not available, the following command can be used to load the correct PowerShell snap-in: Add-PSSnapin HP.
Parameters • Address IP address or hostname • CommunityString SNMP community string Example (interactive) PS C:\> Remove-ProLiantServer Supply values for the following parameters: Address: 192.168.21.1 CommunityString: public PS C:\> Example (single command) PS C:\> Remove-ProLiantServer -address 192.168.21.1 Add-OnboardAdministrator Add-OnboardAdministrator adds the specified Onboard Administrator to the DMS. A username and password must be specified. This cmdlet throws an exception if unsuccessful.
Parameters • Address IP address Example (interactive) PS C:\> Remove-OnboardAdministrator Supply values for the following parameters: Address: 192.168.0.100 PS C:\> Example (single command) PS C:\> Remove-OnboardAdministrator -address 192.168.0.100 Add-VirtualConnectManager Add-VirtualConnectManager adds the specified Virtual Connect Domain to the DMS. A username and password must be specified. This cmdlet throws an exception if unsuccessful.
Address: 192.168.0.101 PS C:\> Example (single command) PS C:\> Remove-VirtualConnectManager -address 192.168.0.101 Sample PowerShell Scripts The following examples illustrate how PowerShell scripts can be created to add multiple devices to the DMS. Adding multiple ProLiant servers This sample script uses a CSV file to add two servers to the DMS. Sample CSV file (servers.csv) Address,CommunityString 192.168.21.37,public 192.168.21.41,public Sample script $items = Import-CSV ".\servers.
Adding multiple Virtual Connect Manager This sample script uses a CSV (comma separated values) file to add three Virtual Connect Domains to the DMS. Sample CSV file (vcdomains.csv) Address,Username,Password 192.168.12.34,vs,password1 192.168.12.35,Administrator,password2 192.168.12.36,vs,password1 Sample script $items = Import-CSV ".\vcdomains.csv" foreach ($item in $items) { "Adding " + $item.Address + " ..." Add-VirtualConnectManager -Address $item.Address -Username $item.Username -Password $item.
4 More about the HP Device Monitor This chapter provides supplemental information about the operation of the HP Device Monitor. HP Device Monitor architecture The DMS provides a communication link between non-Windows devices that are managed from within Microsoft System Center Operations Manager (SCOM). The Device Monitor Service is built on HP Common Services, which provides the underlying monitoring of the managed devices.
Figure 3 Multiple instances of the HP Device Monitor Service Network port usage Table 2 (page 21) lists the ports used by HP Device Monitor. Table 2 Port number/Type Used by Comments 5317/TCP HP Device Monitor Service (DMS) and This port is the Microsoft .NET Remoting HP Device Monitor Console (DMC) interface between the DMC and the DMS. The DMC can be run locally or remotely. This port is registered with http://www.iana.org/.
5 Device monitor performance and scalability guidelines The DMS acts as a proxy to communicate between the HP Management Packs on the SCOM Server and the non-Windows monitored devices (BladeSystem Onboard Administrator, Virtual Connect Domains, and supported Linux, VMware, and Agentless servers). The DMS requires system and network resources that are shared with an Operations Manager server or other applications on the system where it is configured.
change triggers the data re-collection phase and causes additional load to the DMS while the information updates. • Connection recovery The DMS 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.
• ◦ Windows Server 2008 R2 SP1 or Windows Server 2008 x86/x64 SP2 ◦ Windows Server 2012 or Windows Server 2012 R2 Maximum supported managed entities per instance of DMS: ◦ 50 BladeSystem enclosures ◦ 50 HP Virtual Connect Domains ◦ 250 ProLiant servers (per server type) NOTE: HP Device Monitor Service can be installed on multiple systems in the managed environment on either a virtual or physical server.
6 HP Device Monitor Service NT events Table 3 (page 25) lists the NT events that may be reported when a device connection fails. The events are entered in the HP Device Monitor log file. The event source is the HP Device Monitor Core. These events can be caused by the following conditions: • Communication with the device has been lost. • Device failover has occurred. • Device information is not yet available because the HP Device Monitor Service is starting.
7 Troubleshooting the HP Device Monitor Introduction The following information is designed to help resolve some common operating issues that might occur when using the HP Device Monitor. Device monitor management issues This section provides troubleshooting information for device monitor management issues with the HP Device Monitor and SCOM. Same device added to more than one device monitor connection (DMS) It is possible to add the same device to more than one device monitor connection.
Windows SNMP Trap Service is required for DMS but is disabled on servers using SCOM 2012 for network monitoring The DMS requires the SNMP Trap Service to process SNMP traps. However, when a computer is used as a management server or gateway server for network monitoring using SCOM 2012, the SNMP Trap Service is disabled. Consequently, the DMS cannot process SNMP trap events on that computer.
NOTE: If the snmpd.conf file is changed, you must restart the following services: • snmpd • hp-snmp-agents On Linux/VMware servers, test SNMP traps can be generated from the same SNMP Settings screen. Click Send Test Alert to send a test trap. If the management pack is functioning properly, a test SNMP trap posts in the HP Device Monitor Log (in the NT Event log), and an alert is generated on the SCOM console. To view and update the SNMP Settings of an Agentless server: 1.
A Linux or VMware ESX server is not displayed in the SCOM console after the device is updated This may occur if an invalid community string is entered when a Linux or VMware ESX server is updated. An event 310 is entered in the HP Device Monitor Event log, and the alert can be viewed by selecting the HP Systems→Active Alerts view in the SCOM console. To correct this situation, enter a valid community string and then update the server again.
Operating System field in the DMC indicates “unknown” If the value of the server Operating System field in the DMS has changed to “unknown” it may indicate that the associated management service has stopped. • For VMware and Linux servers: Check the status of the Insight Management Agents service for that server. If the Insight Management Agent service has stopped, restart the service. • For Agentless servers: Check the status of the Agentless Monitoring Service (AMS) for the server.
Postgres service fails to start after OS reboot After an OS boot of the system running the HP Device Monitor, if the Postgresql service fails to start due to the pg_ctl this data directory appears to be running a pre-existing postmaster event log error, reboot the OS again. The additional reboot should allow the Postgresql service to start up correctly the second time.
8 Support and other resources Information to collect before contacting HP Be sure to have the following information available before you contact HP: • Software product name • Hardware product model number • Operating system type and version • Applicable error message • Third-party hardware or software • Technical support registration number (if applicable) How to contact HP Use the following methods to contact HP technical support: • See the Contact HP worldwide website: http://www.hp.
Warranty information HP will replace defective delivery media for a period of 90 days from the date of purchase. This warranty applies to all Insight Management products. HP authorized resellers For the name of the nearest HP authorized reseller, see the following sources: • In the United States, see the HP U.S. service locator website: http://www.hp.com/service_locator • In other locations, see the Contact HP worldwide website: http://www.hp.
User input Indicates commands and text that you type exactly as shown. Replaceable The name of a placeholder that you replace with an actual value. [] In command syntax statements, these characters enclose optional content. {} In command syntax statements, these characters enclose required content. | The character that separates items in a linear list of choices. ... Indicates that the preceding element can be repeated one or more times.
Index A O adding devices to DMS, 9 Agentless server, 11 Linux or VMware ESX server, 10 Onboard Administrator, 12 adding DMS connection, 8 Agentless server adding to DMS, 11 audience assumptions, 5 Onboard Administrator adding to DMS, 12 operation overview, 5 overview, 5 C connection status, 8 contacting HP, 32 D deleting devices from DMS, 12 device configuration updating, 13 device monitor architecture, 20 performance and scalability guidelines, 22 troubleshooting, 26 device monitor connection status,
