HP Device Monitor (v 1.1) for Microsoft System Center User Guide Abstract This guide provides information on using the HP Device Monitor version 1.1 to monitor hardware components in an HP Insight Control for Microsoft System Center environment. This information is for system administrators who use the HP Device Monitor and other HP tools to manage hardware components.
© Copyright 2008, 2013 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.........................................................................................
Suggested action..........................................................................................................24 SCOM does not discover devices.........................................................................................24 SCOM does not alert managed devices................................................................................25 The DMC is unable to connect to the DMS following repair of a management pack....................26 The DMC is unable to connect to the DMS........
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. You must be familiar with the configuration and operation of Microsoft Windows and Microsoft Systems Center Operations Manager. Because of the potential risk of data loss, only individuals who are experienced with using this software should implement the procedures described in this guide.
Supported DMS configurations SCOM version 6 DMS location Maximum number of Maximum number of Minimum Recommended OAs/servers supported OAs to servers in mixed Memory per DMS DMS configuration 2012 Local to SCOM server1 35-50 OAs or 2502 servers 50 OAs and 250 servers 4-6 GB 2012 Remote DMS 35-50 OAs or 250 servers 50 OAs and 250 servers1 4-6 GB 2007 Local to SCOM server1 35-50 OAs or 2502 servers 30 OAs and 100 servers 4-6 GB 2007 Remote DMS 35-50 OAs or 250 servers 30 OAs and 100 serv
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 Onboard Administrator Adds the Onboard Administrator for an HP BladeSystem enclosure Adding a Linux or VMware ESX server 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. 3. In the Actions pane, click Add Linux or VMware ESX Server. The Add Linux or VMware ESX Server dialog box is displayed. 4.
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.
6. Click OK. If the information is valid, the device is added to the Discovered Devices pane. Deleting devices from the DMS 1. 2. Open the DMC. Select the monitor connection from which you are removing the device. The current devices on the connection are displayed in the Discovered Devices pane. 3. 4. In the Discovered Devices pane, select one or more devices to delete. In the Actions pane, click Delete Managed Device(s). The Delete Managed Device(s) confirmation window is displayed. 5.
TIP: • The Onboard Administrator credentials must be updated in the DMC if the credentials are changed on the managed enclosure's Onboard Administrator. • The community string must be updated in the DMC if the community string is changed on the managed Linux, VMware, or Agentless server. 1. 2. Open the DMC. Select the monitor connection for the device you are updating. The current devices on the connection are displayed in the Discovered Devices pane. 3. 4. 5.
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 or hostname 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 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.
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 2 Multiple instances of the HP Device Monitor Service Network port usage Table 2 (page 18) lists the ports used by HP Insight Control for System Center. Table 2 18 Port number/Type Used by 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.
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 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 recollection 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 SP2 ◦ Windows Server 2012 OS in supported configuration Maximum supported managed entities per instance of DMS: ◦ 50 BladeSystem enclosures ◦ 250 ProLiant servers NOTE: HP Device Monitor Service can be installed on multiple systems in the managed environment on either a virtual or physical server. If more than 50 enclosures or more than 250 servers are to be managed, multiple instances of DMS should be used.
6 HP Device Monitor Service NT events Table 3 (page 22) 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.
Suggested action Connect the DMC to a locally-installed instance of the DMS. If a local connection to the DMS is not possible, advanced users can perform the following steps on the multihomed system on which the DMS is installed: 1. Use the Windows Service Control Manager to stop the HP Device Monitor Service. 2.
next discovery cycle. The default discovery cycle time is four hours, but this can be changed by the administrator. In addition to registering devices, you must perform the following actions: • On the HP Onboard Administrator web console, verify that a monitor account exists and that the account has managing permission to each managed device. To see the user settings, select User/Authentication→Local Users or Directory Groups, and then select a user or a group.
SNMP trap posts in the HP Device Monitor Log (in the NT Event log), and an alert is generated on the SCOM console. The DMC is unable to connect to the DMS following repair of a management pack When a management pack is being repaired, the device monitor services may stop. If the services stop, the DMC displays an error message indicating that it failed to connect to the DMS.
Events are not being logged in the HP Device Monitor Event log when a non-administrator account is used This is expected behavior when the DMC is used with a non-administrator account. To ensure all events are logged, it is recommended that an administrator account be used when managing devices with the DMC. When a non-administrator account is used, events can be viewed in the device monitor logs generated under %ProgramFiles%\HP SCOM Management Packs\HP Device Monitor Service.
console. After changing a client hostname, perform the following procedure to rediscover the device: 1. Run the DMC. 2. Delete the device with the old hostname. 3. Add the device with the new hostname. The device will again be displayed in the SCOM console. Active Alert view displays only one alert when there are multiple device state changes The event processing rules are designed to consolidate similar events and to not repeat issues.
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.
{} 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. WARNING An alert that calls attention to important information that, if not understood or followed, results in personal injury.
Index A adding devices to DMS, 9 Agentless server, 10 Linux or VMware ESX server, 10 Onboard Administrator, 11 adding DMS connection, 8 Agentless server adding to DMS, 10 audience assumptions, 5 C connection status, 8 contacting HP, 29 D deleting devices from DMS, 12 device configuration updating, 12 device monitor architecture, 17 performance and scalability guidelines, 19 troubleshooting, 23 device monitor connection status, 8 device monitor console opening, 8 using, 7 device monitor overview, 5 disconn
