HP Insight Remote Support Monitored Devices Configuration Guide Software Version: 7.0.
Legal Notices Warranty The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice. Restricted Rights Legend Confidential computer software.
Contents Contents 3 Preface 18 Document Purpose and Audience 18 Product Overview 18 Related Documents 19 Document Revision History 19 Sign Up to Receive Insight Remote Support Communications 19 HP Support Information 20 We Appreciate Your Feedback! 20 Chapter 1: Understanding Monitored Devices Prerequisites 21 Identify Required Communication Protocols and Software Components 21 Functionality Not Supported in Insight RS 7.0.
Contents Missing IP Address During Discovery 43 Warranty and Contract Discrepancy in Insight Online 44 Chapter 3: Configuring ProLiant Windows Servers Configuring ProLiant Windows Servers Using WMI 45 45 Fulfill Configuration Requirements 45 Install and Configure Communication Software on Servers 46 Install and Configure WMI 46 Install Service Pack for ProLiant 46 Install WMI 46 Install System Management Homepage 47 Disabling User Account Control in Windows 2008 47 Verify Communication
Contents Verify Connectivity by Sending an SNMP Test Trap to the Hosting Device 60 Viewing Test Events in the Insight RS Console 61 Chapter 5: Configuring ProLiant VMware ESX Servers 62 Fulfill Configuration Requirements 62 Install and Configure Communication Software on Servers 62 Configure SNMP Verify Communication Between Monitored Device and Insight RS 62 65 Verify Connectivity by Sending an SNMP Test Trap to the Hosting Device 65 Viewing Test Events in the Insight RS Console 65 Chapter
Contents Install the ELMC Software Package on the Monitored Device 75 Verify SNMP Agent Prerequisites on the Monitored Device 76 Verify WBEM Provider Prerequisites on the Monitored Device 77 Add Protocol Credentials and Start Discovery 77 Create the ELMC Protocol in the Insight RS Console 77 Create an SNMP Protocol Credential in Insight RS 77 Create a WMI Protocol Credential in Insight RS 78 Discover the Device in the Insight RS Console 78 Verify Communication Between Monitored Device and I
Contents Verify System Fault Management is Operational 96 Create WBEM Users 98 Creating Non-Privileged Users with cimauth Creating WBEM Privileged Users with WBEM A.02.09.
Contents Fulfilling Required Permissions and Access 114 Grant Permissions Required to Install ELMC 114 Grant Permissions Required to Run ELMC 115 Grant Cluster Node Access to ELMC Install Directory 115 Archiving and Cleaning the Error Log 116 Verify Serial Number 116 Install the ELMC OpenVMS Software Package on the Monitored Device 117 Configure Dynamic Processor Resilience 118 Add Protocol Credentials and Start Discovery 119 Create the ELMC Protocol in the Insight RS Console Chapter 14:
Contents Configuring the Management Module of the IBM BladeCenter® Chassis Install IBM Device Drivers and Service Processor Firmware Add Protocol Credentials and Start Discovery 130 133 134 Discover the Device in the Insight RS Console 134 Configure Warranty and Contract Information 134 Chapter 16: Configuring Dell PowerEdge Servers 136 Fulfill Configuration Requirements 136 Install and Configure Communication Software on Servers 136 Configure the Windows SNMP Service 136 Install and Configur
Contents Disable Monitoring of a BladeSystem c-Class Enclosure Chapter 18: Configuring P6000 and Enterprise Virtual Arrays Configuring P6000 and Enterprise Virtual Arrays Using Server Based Management 147 148 148 Fulfill Configuration Requirements 148 Install and Configure Communication Software on Arrays 149 Install P6000 Command View 149 Fulfilling P6000 Command View System and Access Requirements 150 Installing HP SIM and P6000 Command View on the Same Server 150 Understanding HP SIM Port
Contents Fulfill Configuration Requirements 163 Install and Configure Communication Software on Storage Systems 163 Install and Configure CMC on the Hosting Device 164 Upgrade LeftHand OS on the P4000 Storage Systems 166 Understand Best Practices 166 Select the Type of Upgrade 167 Increase the Size of the OS Disk on the VSAs 168 Verify Management Group Version 169 Check for Patches 169 Configuring SNMP on the P4000 Storage System Add Protocol Credentials and Start Discovery 169 175 Add
Contents Install WBEM SMI-S Proxy Provider Software Add Protocol Credentials and Start Discovery 186 187 Create an SNMP Protocol Credential in Insight RS 187 Create a WBEM Protocol Credential in Insight RS 187 Discover the Device in the Insight RS Console 187 Chapter 22: Configuring MSA2xxx G1 Modular Smart Arrays 189 Fulfill Configuration Requirements 189 Install and Configure Communication Software on Arrays 189 Configure SNMP on Your MSA2xxx G1 Modular Smart Arrays Add Protocol Credentials
Contents Fulfill Configuration Requirements 201 Install and Configure Communication Software on Storage Systems 201 Configure SNMP on the File Serving Nodes 201 Start or Restart Insight Management Agents 202 Add Protocol Credentials and Start Discovery 203 Create an SNMP Protocol Credential in Insight RS 203 Discover Nodes in Insight Remote Support or HP SIM 203 Configure Warranty and Contract Information 204 Verify Communication Between Monitored Device and Insight RS 204 Send a Test Tra
Contents Configuring Command View TL 3.
Contents Verify Communication Between Monitored Device and Insight RS Send a Test Event Chapter 31: Configuring StoreFabric H-Series Switches 231 231 232 Fulfill Configuration Requirements 232 Install and Configure Communication Software on SAN Switches 232 Configure SNMP Add Protocol Credentials and Start Discovery 232 232 Create an SNMP Protocol Credential in Insight RS 233 Discover the Device in the Insight RS Console 233 Verify Device Details 233 Verify Warranty and Contract Information
Contents Fulfill Configuration Requirements 242 Install and Configure Communication Software on Switches 242 Configure Telnet or SSH 242 Configuring Telnet 242 Configuring SSH Version 2 243 Verifying Telnet/SSH Communication 244 Setup SNMP Traps 244 Saving the Current Configuration 244 Add Protocol Credentials and Start Discovery 244 Discover the Device in the Insight RS Console 245 Verify Warranty and Contract Information 245 Verify Communication Between Monitored Device and Insight
Contents Chapter 35: Configuring Modular Cooling Systems 254 Fulfill Configuration Requirements 254 Install and Configure Communication Software on Modular Cooling Systems 254 Configure SNMP on the Modular Cooling System Add Protocol Credentials and Start Discovery 254 256 Create an SNMP Protocol Credential in Insight RS 256 Discover the Device in the Insight RS Console 256 Verify Communication Between Monitored Device and Insight RS Send a Test Trap Chapter 36: Configuring VMware vCenter Serv
Preface Document Purpose and Audience This document provides the necessary information to configure your monitored devices before discovering the devices with HP Insight Remote Support (RS). This document is for HP Customers and HP Support Personnel who are installing, configuring, and using Insight RS.
Preface Related Documents For additional Insight RS documentation, go to: http://www.hp.com/go/insightremotesupport/docs. l HP Insight Remote Support Release Notes This document provides product details and information about which monitored devices and Hosting Devices are supported for use with the Insight RS solution. l HP Insight Remote Support Quick Installation Guide This document provides a checklist for installing and configuring Insight RS.
Preface When you subscribe, search for Insight Remote Support. HP Support Information HP recommends you consult the Insight RS documentation to resolve issues. The documentation is designed to guide you through a successful installation and configuration. However, if you need further support for Insight RS, help is available through HP's local Response Centers. For contact details, go to: http://www.hp.com/go/rstechsupport. Before contacting support, you can check if your issue has a solution available.
Chapter 1: Understanding Monitored Devices Prerequisites To use Insight Remote Support (RS) you need at least two pieces of hardware: a supported Windows ProLiant server to be used as the Hosting Device and one or more devices to be monitored by Insight RS. Use the table below to identify what protocols and software components are necessary for your monitored devices and then go to the information for your specific devices for complete configuration details.
Chapter 1: Understanding Monitored Devices Prerequisites l Web-Based Enterprise Management (WBEM) l Windows Management Instrumentation (WMI) If you do not configure the required protocols and software for your monitored devices, the devices will not communicate with the Hosting Device and your events and configuration collections will not be sent to HP for support.
Chapter 1: Understanding Monitored Devices Prerequisites Table 1.1 Required Monitored Device Communication Protocols and Components for Insight RS Services Discovery Monitoring Basic Collections RIBCL RIBCL RIBCL SAN Collections Notes HP Servers ProLiant Gen8 HP ProLiant Gen8 servers can be monitored using the embedded management capabilities in the iLO 4 or using a diagnostic agent installed on the operating system.
Chapter 1: Understanding Monitored Devices Prerequisites Table 1.1 Required Monitored Device Communication Protocols and Components for Insight RS Services, continued Linux on ProLiant Discovery Monitoring Basic Collections SNMPv1, SNMPv2 or SNMPv3 SNMPv1, SNMPv2 or SNMPv3 SNMPv1, SNMPv2 or SNMPv3 SAN Collections Notes Must install the HP Service Pack for ProLiant and all providers that ship with it. See "Configuring ProLiant Linux Servers" on page 57.
Chapter 1: Understanding Monitored Devices Prerequisites Table 1.1 Required Monitored Device Communication Protocols and Components for Insight RS Services, continued Windows 2003 on Integrity Discovery Monitoring Basic Collections SAN Collections Notes WMI WMI WMI WMI SNMPv1 SNMPv1 SNMPv1 Must install the Integrity Support Pack and all providers that ship with it. This includes the installation of SNMPv1 and WMI. See "Configuring Integrity Windows 2003 Servers" on page 75.
Chapter 1: Understanding Monitored Devices Prerequisites Table 1.1 Required Monitored Device Communication Protocols and Components for Insight RS Services, continued Discovery Monitoring HP Integrity WSMAN Superdome 2 Onboard Administrator (OA) WSMAN OpenVMS on Integrity WBEM WBEM Basic Collections SAN Collections Notes Discovery uses WSMAN and collections use HTTPS. The OA is monitored using WSMAN, but the Superdome 2 partitions are monitored using WBEM.
Chapter 1: Understanding Monitored Devices Prerequisites Table 1.1 Required Monitored Device Communication Protocols and Components for Insight RS Services, continued Windows on Dell PowerEdge Discovery Monitoring SNMPv1 SNMPv1 Basic Collections SAN Collections HP Insight Remote Support 7.0.9: Monitored Devices Configuration Guide Notes Configuration collections are not supported. See "Configuring Dell PowerEdge Servers" on page 136.
Chapter 1: Understanding Monitored Devices Prerequisites Table 1.1 Required Monitored Device Communication Protocols and Components for Insight RS Services, continued Discovery Monitoring SNMPv1 SNMPv1 Basic Collections SAN Collections Notes HP BladeSystems HP Onboard Administrator for c-class Enclosures HP c-Class BladeSystem Enclosures can be monitored using the embedded management capabilities in the HP Onboard Administrator (OA) or by configuring SNMP in the OA.
Chapter 1: Understanding Monitored Devices Prerequisites Table 1.1 Required Monitored Device Communication Protocols and Components for Insight RS Services, continued Discovery Storage Blades Monitoring Basic Collections SAN Collections (See Notes) Notes Configuration collections are not supported. Storage Blades are monitored through the Storage Agents installed on the partner server blade. The partner server blade is the adjacent server blade connected directly to the storage blade.
Chapter 1: Understanding Monitored Devices Prerequisites Table 1.1 Required Monitored Device Communication Protocols and Components for Insight RS Services, continued HP MSA 2040 HP P2000 G3 MSA HP MSA23xx G2 Discovery Monitoring SNMPv1 SNMPv1 WBEM WBEM SNMPv1 SNMPv1 WBEM WBEM SNMPv1 SNMPv1 WBEM HP MSA2xxx G1 SNMPv1 Basic Collections SAN Collections Notes Both SNMPv1 and WBEM must be installed and configured. WBEM WBEM See "Configuring P2000 G3 Modular Smart Arrays" on page 179.
Chapter 1: Understanding Monitored Devices Prerequisites Table 1.1 Required Monitored Device Communication Protocols and Components for Insight RS Services, continued Discovery Monitoring SNMPv1 SNMPv1 Basic Collections SAN Collections Notes Data Protection HP StoreOnce Backup (D2D) Configuration collections are not supported, except when the HP StoreOnce Backup System is part of a SAN collection.
Chapter 1: Understanding Monitored Devices Prerequisites Table 1.1 Required Monitored Device Communication Protocols and Components for Insight RS Services, continued Discovery Monitoring Basic Collections SAN Collections Notes HP StoreFabric SAN Switches B-Series SAN Switch SNMPv1 or SNMPv2 SNMPv1 or SNMPv2 See "Configuring StoreFabric B-Series Switches" on page 222.
Chapter 1: Understanding Monitored Devices Prerequisites Table 1.1 Required Monitored Device Communication Protocols and Components for Insight RS Services, continued Discovery Monitoring Basic Collections SNMPv1 or WMI SNMPv1 or WMI SNMPv1 or WMI SAN Collections Notes HP Solutions E5000 Messaging Systems These devices should be configured the same as a Windows ProLiant server. WMI HTTP You can choose to use SNMPv1 or WMI, however to gather SAN Collections, you must use WMI.
Chapter 1: Understanding Monitored Devices Prerequisites Functionality Not Supported in Insight RS 7.0.9 The following devices and functionality were supported in 5.x versions of Insight RS, but are not supported in version 7.0.9: Table 1.2 Insight RS 5.x Functionality Not Available in Insight RS 7.0.9 Functionality Details Hosting Device l All Microsoft Windows 2003 operating system versions. Note that this will not be supported on any Insight RS 7.x versions.
Chapter 1: Understanding Monitored Devices Prerequisites Table 1.2 Insight RS 5.x Functionality Not Available in Insight RS 7.0.9, continued Functionality Details Products that will not be supported by any 7.x version l HP Dynamic Smart Cooling l HP SAN Virtualization Services Platform l HP Modular Array l HP Enterprise Modular Array l HP Raid Array l HP Enterprise Storage Array l M-series Switches (McData) HP Insight Remote Support 7.0.
Chapter 2: Configuring ProLiant Gen8 Servers The Insight Remote Support (RS) feature available through the iLO 4 web interface provides intelligent event diagnosis and automatic secure submission of event notifications to HP and your HP Authorized Channel Partner through the Insight RS installation on the Hosting Device.
Chapter 2: Configuring ProLiant Gen8 Servers 1. In a web browser, log on to the Insight RS Console. 2. In the main menu, select Discovery and click the Credentials tab. 3. Select iLO Remote Insight Board Command Language Protocol (RIBCL) from the Select and Configure Protocol drop-down list and click New. 4. Fill in the required fields. Use the Username and Password of the iLO 4 web interface on the ProLiant Gen8 server. 5. Click Add.
Chapter 2: Configuring ProLiant Gen8 Servers Remote Support. You can register Insight Remote Support for a ProLiant Gen8 server in the iLO 4 web interface. Important: When setting up your iLO 4 web interface, it is important to set the time zone. If the time zone is not set, events sent to Insight Remote Support are displayed with a GMT offset. In the iLO 4 web interface, browse to Administration → Network → SNTP Settings to set your time zone.
Chapter 2: Configuring ProLiant Gen8 Servers Test Communication from the ProLiant Gen8 Server to Insight RS To test communication of your monitored devices, complete the following steps: Verify Service Event Monitoring After registering the ProLiant Gen8 server with Insight Remote Support, send a test event to confirm the connection. Note: Sending SNMP test traps from the iLO 4 web interface Administration → Management page is not supported in Insight Remote Support.
Chapter 2: Configuring ProLiant Gen8 Servers The Time Generated column in the Service Event Log shows the date and time based on the configured iLO time zone. 5. Check the Insight RS Console to verify that the test event arrived: a. Log on to the Insight RS Console. b. In the main menu, select Devices. c. Find the Gen8 ProLiant server and click the device name. d. Click the Service Events tab.
Chapter 2: Configuring ProLiant Gen8 Servers Initiating a Data Collection in the iLO 4 Web Interface To initiate a data collection in the iLO 4 web interface, complete the following steps: 1. Log on to the iLO 4 web interface (https://). 2. Navigate to Remote Support → Data Collections. The Data Collections screen displays. 3. Click Send Data Collection. 4. Click OK to confirm the action.
Chapter 2: Configuring ProLiant Gen8 Servers iLO sends the Active Health System report to Insight RS. In the Insight RS Console you can view the results on the Collection Services → Basic Collection Results screen. Sending an Active Health System Report from Insight Remote Support To send an Active Health System report from the Insight RS Console, complete the following steps: 1. Log on to the Insight RS Console. 2. Navigate to Collection Services → Collection Schedules. 3.
Chapter 2: Configuring ProLiant Gen8 Servers 3. In the Expires in drop-down list, select the length of time you will work on the ProLiant Gen8 server. 4. Click Apply. Note: Maintenance Mode ends once the specified time has elapsed. You can end maintenance mode early by selecting the Clear Maintenance Mode check box and clicking Apply. A confirmation message appears.
Chapter 2: Configuring ProLiant Gen8 Servers n RIBCL—The iLO Remote Insight Board Common Language Protocol (RIBCL) credentials for the server are configured in the Insight RS Console and are assigned to the Gen8 server. 2. Log on to the Insight RS Console. 3. Navigate to Devices → Device Summary. 4. Click the serial number in the Device Name column. 5. On the Device tab, expand the Status section and click Discover Device. When the device is rediscovered host name or IP address is displayed.
Chapter 3: Configuring ProLiant Windows Servers Insight Remote Support (RS) must be able to communicate with your ProLiant server before it can be monitored. Insight RS can communicate with ProLiant servers running Windows with either WMI or SNMP. The following information describes how to install and configure the communication protocols and other recommended software components so that it can be monitored by Insight RS. Use these configuration instructions for Windows 2003, Windows 2008, and Windows 2012.
Chapter 3: Configuring ProLiant Windows Servers Table 3.1 ProLiant Windows Server Using WMI Configuration Steps, continued Task Complete? Add the WBEM protocol to the Insight RS Console. Discover the ProLiant Windows server in the Insight RS Console. Send a test event to verify connectivity between your ProLiant Windows server and Insight RS.
Chapter 3: Configuring ProLiant Windows Servers Install System Management Homepage System Management Homepage (SMH) is also part of the SPP. It provides additional reporting capabilities on the monitored device itself. While not mandatory for Insight Remote Support, SMH can be used to work with the WBEM protocol such as sending test events. Disabling User Account Control in Windows 2008 In Windows 2008, WMI fails to connect to the namespace root\WMI if User Account Control (UAC) is enabled.
Chapter 3: Configuring ProLiant Windows Servers Send a WBEM Test Indication to the Hosting Device To verify connectivity from the monitored device to the Hosting Device, send a WBEM test indication to the Hosting Device and then verify the test indication was received in the Insight RS Console. 1. In a web browser, access System Management Homepage (SMH) on the monitored device: https://[ipaddress]:2381. 2. Log on using the administrator user name and password for the monitored device.
Chapter 3: Configuring ProLiant Windows Servers 1. Log on to the Insight RS Console. 2. In the main menu, select Service Events. If your monitored device is properly configured, the event will appear in the Service Events Information pane.
Chapter 3: Configuring ProLiant Windows Servers Table 3.2 ProLiant Windows Server Using SNMP Configuration Steps Task Complete? Check the HP Insight Remote Support Release Notes to make sure your ProLiant Windows server is supported. Install SNMP on the ProLiant Windows server, available from the Service Pack for ProLiant (SPP). Configure SNMP on the ProLiant Windows server. Add the SNMP protocol to the Insight RS Console. Discover the ProLiant Windows server in the Insight RS Console.
Chapter 3: Configuring ProLiant Windows Servers Configure SNMP Your monitored devices must be configured to communicate with the Hosting Device. If you choose to use SNMP the following steps are required to allow the monitored devices to fully communicate with the Hosting Device. Monitored devices that use SNMP notifications must include the following: l All monitored devices must have a working intranet connection, such as through an Ethernet adapter, with TCP/IP installed and running.
Chapter 3: Configuring ProLiant Windows Servers c. In the top menu bar, click Settings. If you changed the data source to SNMP while logged into SMH remotely, you will have to log on again and click the Settings tab. 4. In the SNMP Webagent pane, click the SNMP & Agent Settings link. 5. In the left menu of the Management Agents Configuration screen, click the Security link. HP Insight Remote Support 7.0.
Chapter 3: Configuring ProLiant Windows Servers 6. In the Security Configuration screen click one of the following options in the Selected Hosts section: n Accept SNMP packets from any host. or n Accept SNMP packets from these hosts and specify the IP address for your Hosting Device in the text area. HP Insight Remote Support 7.0.
Chapter 3: Configuring ProLiant Windows Servers 7. In the left menu of the Security Configuration screen, click the Trap link. 8. In the Trap Configuration screen, do one of the following: n Add a Community Name that includes the Hosting Device as a Trap Destination. or n Edit the public Community Name to include the Hosting Device as a Trap Destination. HP Insight Remote Support 7.0.
Chapter 3: Configuring ProLiant Windows Servers Complete the preceding steps for each ProLiant Windows monitored device that uses SNMP to communicate with the Hosting Device.
Chapter 3: Configuring ProLiant Windows Servers arrived. 1. Log on to the Insight RS Console. 2. In the main menu, select Service Events. If your monitored device is properly configured, the event will appear in the Service Events Information pane. HP Insight Remote Support 7.0.
Chapter 4: Configuring ProLiant Linux Servers Fulfill Configuration Requirements To configure your ProLiant Linux servers to be monitored by Insight RS, complete the following steps: Table 4.1 ProLiant Linux Server Configuration Steps Task Complete? Make sure Insight RS supports your ProLiant Linux server by checking the HP Insight Remote Support Release Notes. Install SNMP on the ProLiant Linux server, available from the Service Pack for ProLiant (SPP). Configure SNMP on the ProLiant Linux server.
Chapter 4: Configuring ProLiant Linux Servers installed, must be removed according to the SPP documentation available at: http://www.hp.com/go/spp/documentation/. Note: On your Linux monitored device, the /etc/snmp/snmpd.conf file contains the SNMP configuration information. During the IM Agents installation script, watch for information about this file. When the script prompts you about Configuring SNMP access from remote Management Station(s), be sure to include the Hosting Device IP address.
Chapter 4: Configuring ProLiant Linux Servers The trapsink command is required for events to be sent to Insight Remote Support for analysis. If the trapsink command is not configured, Insight Remote Support will not receive traps. A rocommunity directive allows SNMP GET and GETNEXT access. It is required for discovery and by the analysis rules. The format is: rocommunity , for example rocommunity public.
Chapter 4: Configuring ProLiant Linux Servers a. Scroll down in the SNMP Configuration File to the view systemview included entries. b. Comment out the default entries with a # character. c. Add the following entry: view systemview included .1 80 d. Click Change.
Chapter 4: Configuring ProLiant Linux Servers snmptrap -v 1 -c public [Hosting Device IP Address] .1.3.6.1.4.1.232 [Linux monitored device IP Address] 6 11003 1234 .1.3.6.1.2.1.1.5.0 s test .1.3.6.1.4.1.232.11.2.11.1.0 i 0 .1.3.6.1.4.1.232.11.2.8.1.0 s [provide your own identifier and time stamp] The resulting text with details of the monitored device and Hosting Device should be returned.
Chapter 5: Configuring ProLiant VMware ESX Servers Fulfill Configuration Requirements To configure your ProLiant VMware ESX servers to be monitored by Insight RS, complete the following steps: Table 5.1 ProLiant VMware ESX Server Configuration Steps Task Complete? Make sure Insight RS supports your ProLiant VMware ESX server by checking the HP Insight Remote Support Release Notes. Configure SNMP on the ProLiant VMware ESX server. Add the SNMP protocol credentials to the Insight RS Console.
Chapter 5: Configuring ProLiant VMware ESX Servers SNMP Agents are required for VMware ESX monitored devices. Once you have installed the SNMP Agents on your monitored devices, use SMH to edit the snmpd.conf file to add the Hosting Device IP address and the SNMP community string. This enables SNMP communication from the monitored device to the Hosting Device. You will need to do this for each VMware ESX monitored device. Note: You can also edit the snmpd.conf file in a text editor if you are not using SMH.
Chapter 5: Configuring ProLiant VMware ESX Servers 6. For those Linux installations (for example Red Hat 4 or 5) that support the added security of view statements, add a view systemview included entry. The view systemview included entry allows Insight Remote Support to read the entire .232 MIB tree and gather all of the analysis data when events occur. Make the following change to the default settings: a. Scroll down in the SNMP Configuration File to the view systemview included entries. b.
Chapter 5: Configuring ProLiant VMware ESX Servers c. Add the following entry: view systemview included .1 80 d. Click Change.
Chapter 5: Configuring ProLiant VMware ESX Servers will appear in the Service Events Information pane. HP Insight Remote Support 7.0.
Chapter 6: Configuring ProLiant VMware ESXi Servers Fulfill Configuration Requirements To configure your ProLiant VMware ESXi servers to be monitored by Insight RS, complete the following steps: Table 6.1 ProLiant VMware ESXi Server Configuration Steps Task Complete? Make sure Insight RS supports your ProLiant VMware ESXi server by checking the HP Insight Remote Support Release Notes. Install and configure WBEM providers on the ESXi server.
Chapter 6: Configuring ProLiant VMware ESXi Servers Important: If using the ESXi distribution files distributed by HP, then it is not necessary to download and install the WBEM Providers bundle because the distribution files already have the bundle integrated within. Download HP ESXi 4 distribution from the following link: https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=HPVM06. Download HP ESXi 5 distribution from the following link: https://h20392.www2.hp.
Chapter 6: Configuring ProLiant VMware ESXi Servers 1. In a web browser, log on to the Insight RS Console. 2. In the main menu, select Discovery and click the Credentials tab. 3. From the Select and Configure Protocol drop-down list, select Web-Based Enterprise Management (WBEM). 4. Click New. The New Credential dialog box appears. 5. Enter the Username and Password that WBEM uses on the ProLiant ESXi server. 6. Click Add. Insight RS creates the protocol credential and it appears in the credentials table.
Chapter 7: Configuring ProLiant Citrix Xen Servers Fulfill Configuration Requirements To configure your ProLiant Citrix Xen servers to be monitored by Insight RS, complete the following steps: Table 7.1 ProLiant Citrix Xen Server Configuration Steps Task Complete? Make sure Insight RS supports your ProLiant Citrix Xen server by checking the HP Insight Remote Support Release Notes. Install HP SNMP Agents for Citrix XenServer on the ProLiant Citrix Xen server.
Chapter 7: Configuring ProLiant Citrix Xen Servers http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?swItem=MTX9f349b2b4fc94915ac6cde8b8a. SNMP Agents support HP ProLiant systems running Citrix, which are included in the HP SNMP Agents for Citrix XenServer software package. Note: On your Citrix monitored device, the /etc/snmp/snmpd.conf file contains the current SNMP configuration.
Chapter 7: Configuring ProLiant Citrix Xen Servers address, for example trapsink 1.2.3.4 public, and click Change. The trapsink command is required for events to be sent to Insight Remote Support for analysis. If the trapsink command is not configured, Insight Remote Support will not receive traps. A rocommunity directive allows SNMP GET and GETNEXT access. It is required for discovery and by the analysis rules. The format is: rocommunity , for example rocommunity public.
Chapter 7: Configuring ProLiant Citrix Xen Servers a. Scroll down in the SNMP Configuration File to the view systemview included entries. b. Comment out the default entries with a # character. c. Add the following entry: view systemview included .1 80 d. Click Change.
Chapter 7: Configuring ProLiant Citrix Xen Servers snmptrap -v 1 -c public [Hosting Device IP Address] .1.3.6.1.4.1.232 [Linux monitored device IP Address] 6 11003 1234 .1.3.6.1.2.1.1.5.0 s test .1.3.6.1.4.1.232.11.2.11.1.0 i 0 .1.3.6.1.4.1.232.11.2.8.1.0 s [provide your own identifier and time stamp] The resulting text with details of the monitored device and Hosting Device should be returned.
Chapter 8: Configuring Integrity Windows 2003 Servers Event Log Monitoring Collector (ELMC) is responsible for remote support monitoring on Windows 2003 Integrity monitored devices. SNMP is necessary for Discovery, and WBEM is necessary for configuration collections. Fulfill Configuration Requirements To configure your Integrity Windows 2003 servers to be monitored by Insight RS, complete the following steps: Table 8.
Chapter 8: Configuring Integrity Windows 2003 Servers l TCP-IP configured on the monitored server l Required Permissions and Access: To install, upgrade, or uninstall ELMC, you must be logged on as the Administrator or as a user with administrator privileges. ELMC is required on the Integrity Windows 2003 server so that events can be forwarded to Insight RS. If ELMC is already installed on the Integrity Windows 2003 server, make sure it is version 6.2 or later. If it's older than version 6.
Chapter 8: Configuring Integrity Windows 2003 Servers For SNMP Agents to communicate to the Hosting Device, you must provide the SNMP credentials within the Insight RS Console. These actions must occur within the Insight RS Console on the Hosting Device when you are completing the Insight Remote Support configuration.
Chapter 8: Configuring Integrity Windows 2003 Servers community string or use a nonstandard port, you must create an SNMPv1 protocol credential in the Insight RS Console. To configure SNMPv1 in the Insight RS Console, complete the following steps: 1. In a web browser, log on to the Insight RS Console. 2. In the Main Menu, select Discovery and click the Credentials tab. 3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol Version 1. 4. Click New.
Chapter 8: Configuring Integrity Windows 2003 Servers Verify Communication Between Monitored Device and Insight RS To verify communication between your monitored device and Insight RS, complete the following steps: Verify Connectivity by Sending an SNMP Test Trap Use SNMP Agents to send SNMP Test Traps to verify connectivity. 1. In a web browser, access System Management Homepage (SMH) on the monitored device: https://[ipaddress]:2381. 2.
Chapter 8: Configuring Integrity Windows 2003 Servers 7. In the Management Agents Configuration screen, click Send Test Trap. Sending a WBEM Test Indication to Verify Connectivity Use WBEM Providers to send WBEM Indications to verify connectivity. 1. In a web browser, access System Management Homepage (SMH) on the monitored device: https://[ipaddress]:2381. 2. Log on using the administrator user name and password for the monitored device.
Chapter 8: Configuring Integrity Windows 2003 Servers 5. In the Send Test Indication screen, select an Event ID type and click Send. Viewing Test Events in the Insight RS Console Some monitored device types allow you to send a test event to Insight Remote Support. After you configure your monitored device and send a test event, use the following process to verify the test event arrived. 1. Log on to the Insight RS Console. 2. In the main menu, select Service Events.
Chapter 8: Configuring Integrity Windows 2003 Servers will appear in the Service Events Information pane. HP Insight Remote Support 7.0.
Chapter 9: Configuring Integrity Windows 2008 Servers Fulfill Configuration Requirements To configure your Integrity Windows 2008 servers to be monitored by Insight RS, complete the following steps: Table 9.1 Integrity Windows 2008 Server Configuration Steps Task Complete? Make sure Insight RS supports your Integrity Windows 2008 server by checking the HP Insight Remote Support Release Notes. Install WBEM on the Integrity Windows 2008 server. Add the WBEM protocol to the Insight RS Console.
Chapter 9: Configuring Integrity Windows 2008 Servers For WBEM Providers to communicate to the Hosting Device, you must provide the WBEM credentials within the Insight RS Console when you are completing the Insight Remote Support configuration.
Chapter 9: Configuring Integrity Windows 2008 Servers 5. In the Send Test Indication screen, select an Event ID type and click Send. Viewing Test Events in the Insight RS Console Some monitored device types allow you to send a test event to Insight Remote Support. After you configure your monitored device and send a test event, use the following process to verify the test event arrived. 1. Log on to the Insight RS Console. 2. In the main menu, select Service Events.
Chapter 9: Configuring Integrity Windows 2008 Servers will appear in the Service Events Information pane. HP Insight Remote Support 7.0.
Chapter 10: Configuring Integrity Linux Servers Important: Configuration collections are not supported. Note: nPars are not supported on Linux Integrity servers. Fulfill Configuration Requirements To configure your Integrity Linux servers to be monitored by Insight RS, complete the following steps: Table 10.1 Integrity Linux Server Configuration Steps Task Complete? Make sure Insight RS supports your Integrity Linux server by checking the HP Insight Remote Support Release Notes.
Chapter 10: Configuring Integrity Linux Servers Verify Communication Between Monitored Device and Insight RS To verify communication between your monitored device and Insight RS, complete the following steps: Send a Test Event to the Hosting Device To send a test event from the monitored device to the Hosting Device, from a command line on the monitored device type the following command: touch /tmp/SMX.test Note: This process is not supported for Red Hat Linux 4 or 5.
Chapter 11: Configuring Integrity HP-UX Servers Before attempting to configure Insight Remote Support for your HP-UX monitored device, read the following information. Note: Insight Remote Support version 7.0.9 only supports HP-UX on Integrity servers. Fulfill Configuration Requirements To configure your Integrity HP-UX servers to be monitored by Insight RS, complete the following steps: Table 11.
Chapter 11: Configuring Integrity HP-UX Servers the minimum requirements identified in that section, then you do not need to remove or reinstall those components. Note: You may be familiar with the variety of SFM providers available in the different SFM offerings. Insight Remote Support only requires the providers in the standard SFM package(s) as specified in section "Meeting HP-UX Operating System, Software, and Patch Requirements".
Chapter 11: Configuring Integrity HP-UX Servers Fulfilling Software and Patch Requirements for HP-UX 11i v2 Important: While not required for HP-UX 11i v2 (11.23), HP strongly recommends installing the latest QPKBASE patch bundle. QPKBASE fulfills all system patch requirements and provides a stable supported environment. The following table identifies the minimum required patches (required if QPKBASE is not installed).
Chapter 11: Configuring Integrity HP-UX Servers Table 11.2 Required Software Components for HP-UX 11i v2, continued Required Software Version Required Operating System Patch Requirements BUNDLE 11i patch bundle B.11.23.0409.3 (September, 2004): Note: These six additional patches for HP-UX 11i v2 are not part of the Bundle11i and must be installed in addition to it. l PHKL_36288 - 11.23 Cumulative diag2 driver and vPars enablement (use in place of PHKL_ 32653), requires a reboot l PHKL_34795 - 11.
Chapter 11: Configuring Integrity HP-UX Servers Table 11.2 Required Software Components for HP-UX 11i v2, continued Required Software Version Required How to Download or Access Software: l Available on Application Software Media from December, 2007 onwards l Alternatively, go to the following HP Software Depot location for the latest version: https://h20392.www2.hp.com/portal/swdepot/try.
Chapter 11: Configuring Integrity HP-UX Servers Table 11.2 Required Software Components for HP-UX 11i v2, continued Required Software Version Required How to Download or Access Software: l Available on HWE0712 media l Alternatively, go to the following HP Software Depot location for the latest version: https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=SysFaultMg mt Note: See the System Fault Management Release Notes for more details and additional SFM prerequisites.
Chapter 11: Configuring Integrity HP-UX Servers Table 11.3 Required Software Components for HP-UX 11i v3, continued Required Software Version Required OpenSSL Secure Network Communications Protocol A.00.09.07e.013 or later How to Download or Access Software: l Available on Application Software Media from September 2007 onwards l Alternatively, go to the following HP Software Depot location for the latest version: https://h20392.www2.hp.com/portal/swdepot/try.
Chapter 11: Configuring Integrity HP-UX Servers Table 11.3 Required Software Components for HP-UX 11i v3, continued Required Software Version Required System Management Web is recommended to take full advantage of SFM's EVWEB GUI component which allows viewing of events handled by SFM on the host. If only SysMgmtHomepage version 2.2.6.2 is present on the server, then the following patch must also be applied: For HP-UX 11i v3 (11.
Chapter 11: Configuring Integrity HP-UX Servers 2. To list registered CIM providers and their current status to make sure that they are all enabled, run the following command: # cimprovider –l –s 3. Run the following command to check OnlineDiag is installed and make sure it is version B.11.11.16xx or later. # swlist | grep –i OnlineDiag The output should look similar to the following: 4.
Chapter 11: Configuring Integrity HP-UX Servers a. Check if SFM is used for hardware monitoring: # /opt/sfm/bin/sfmconfig -w –q b. If EMS is enabled for monitoring, switch to SFM using the command: # /opt/sfm/bin/sfmconfig –w –s 7. Run the following command to determine the version of the optional, but recommended, SMH component is at least version A.2.2.6.2: # swlist SysMgmtWeb SysMgmtHomepage The output should look similar to the following: 8.
Chapter 11: Configuring Integrity HP-UX Servers Creating Non-Privileged Users with cimauth It is possible to use a non-privileged account for WBEM communication. Create a user or use an existing non-privileged user. The specified username must represent a valid HP-UX user on the local host. To create a non-privileged account on an HP-UX monitored device, complete the following steps: 1. Create a user, hpirs in this example, and assign the user to the users group: # useradd –g users hpirs 2.
Chapter 11: Configuring Integrity HP-UX Servers enableHttpConnection=false 7. Add read and write authorizations for the user hpirs to each of the namespaces, root/cimv2, root/PG_ InterOp, and root/PG_Internal: # cimauth –a –u hpirs –n root/cimv2 –R –W # cimauth –a –u hpirs –n root/PG_InterOp –R –W # cimauth –a –u hpirs –n root/PG_Internal –R –W # cimauth –a –u hpirs –n root/cimv2/npar –R –W # cimauth –a –u hpirs –n root/cimv2/vpar –R –W 8.
Chapter 11: Configuring Integrity HP-UX Servers 3. Change enableSubscriptionsForNonprivilegedUsers to true: # cimconfig -s enableSubscriptionsForNonprivilegedUsers=true -p 4. Stop the WBEM Services: # cimserver -s 5. Restart the WBEM Services: # cimserver Note: Users configured in the Insight Remote Support configuration file can perform WBEM operations with root privileges. However, these users can still continue to have system privileges as defined in the HP-UX /etc/passwd file.
Chapter 11: Configuring Integrity HP-UX Servers 3. From the Select and Configure Protocol drop-down list, select Web-Based Enterprise Management (WBEM). 4. Click New. The New Credential dialog box appears. 5. Type the Username and Password you have configured on your device. Use the user that was created previously in "Create WBEM Users" on page 98. 6. Click Add. Insight RS creates the protocol credential and it appears in the credentials table.
Chapter 11: Configuring Integrity HP-UX Servers idleConnectionTimeout=0 enableSubscriptionsForNonprivilegedUsers=true socketWriteTimeout=20 shutdownTimeout=30 authorizedUserGroups= enableRemotePrivilegedUserAccess=true enableHttpsConnection=true enableNamespaceAuthorization=true enableHttpConnection=false d. Make sure the fields in red are defined as above. If they are not, change the values and validate them using the following commands: i.
Chapter 11: Configuring Integrity HP-UX Servers above. Discover the Device in the Insight RS Console To discover the device from the Insight RS Console, complete the following steps: 1. In a web browser, log on to the Insight RS Console. 2. In the main menu, select Discovery and click the Sources tab. 3. Expand the IP Addresses section and add the IP address for your device: a. Click New. b. Select the Single Address, Address Range, or Address List option. c.
Chapter 11: Configuring Integrity HP-UX Servers Verify Connectivity by Sending an SNMP Test Trap to the Hosting Device Send a test event from the HP-UX server to verify communication between the HP-UX server and the Hosting Device. Execute one of the following commands on the HP-UX server: # /etc/opt/resmon/lbin/send_test_event disk_em or # /opt/sfm/bin/sfmconfig -t -a For details on SysFaultMgmt, including issuing test events, refer to the HP-UX System Fault Management Administration Guide at: http://www.
Chapter 12: Configuring Integrity Superdome 2 Servers The Superdome 2 system complex has two independent interfaces that report event indications: the HPUX partitions and the Superdome 2 Onboard Administrator (OA). HP-UX System Fault Manager (SFM) monitors the IO devices within the partition domain and generates WBEM indications when it determines an important event has occurred.
Chapter 12: Configuring Integrity Superdome 2 Servers Install and Configure Communication Software on Servers To configure your monitored devices, complete the following sections: Superdome 2 OA Configuration Verification Connect to the Superdome 2 OA using Telnet, SSH or a web browser (HTTPS), and verify the network settings and protocol status of the OA.
Chapter 12: Configuring Integrity Superdome 2 Servers 1. In a web browser, log on to the Insight RS Console. 2. In the Main Menu, select Discovery and click the Credentials tab. 3. Selection the following filters: a. From the Select Type drop-down list, select Server. b. From the Select Sub-Type drop-down list, select HP Integrity HPUX. c. From the Select and Configure Protocol drop-down list, select Web-Based Enterprise Management (WBEM). 4. Click New. The New Credential dialog box appears. 5.
Chapter 12: Configuring Integrity Superdome 2 Servers d. Click Add. 4. Click Start Discovery. Note: If discovery is configured to discover standby OAs, it will populate the Devices screen with minimal information on these devices because although their network interfaces can be active and be reachable, they are not monitoring port 443 used for communication and therefore cannot provide Insight RS with information about themselves.
Chapter 12: Configuring Integrity Superdome 2 Servers the Active OA to the Standby OA. The Insight RS Console will continue to show that it is actively monitoring the previously configured Active OA (even though that OA has failed). Note: An Superdome 2 32s configuration consists of two enclosures joined into a single server complex. Each enclosure has a primary and a standby OA that manages and monitors that enclosure.
Chapter 12: Configuring Integrity Superdome 2 Servers "Configuring Integrity HP-UX Servers" on page 89 describes how to generate test events from each of the HP-UX partitions. Generate a test event and verify the HP-UX SFM test events have been received and processed by Insight RS. HP Insight Remote Support 7.0.
Chapter 13: Configuring OpenVMS Servers Important: Configuration collections for OpenVMS on AlphaServer are not available except when the OpenVMS server is part of a SAN collection. Important: HP only provides limited remote support for customers using HP Alpha servers. As with standard support, HP Insight Remote Support version 7.x will attempt to discover these products as remotely monitored HP products and send information about failure events to HP.
Chapter 13: Configuring OpenVMS Servers Fulfilling Hardware and Software Requirements l l Processor architecture: n Integrity (Itanium) Server n HP AlphaServer Operating system: n OpenVMS Itanium (Integrity) — 8.3-1H1 or higher. Note: Some supported OpenVMS platforms require a minimum version of 8.4. See http://h71000.www7.hp.com/openvms/hw_supportchart.html. Note: HP Sustaining Engineering maintains a schedule of support for the OpenVMS operating system.
Chapter 13: Configuring OpenVMS Servers 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0 ms 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0 ms After verifying that LOCALHOST responds to the ping command, you can use Ctrl-C or Ctrl-Y to stop pinging. l System firmware: The prerequisite system firmware supports the logging of events according to the FRU Table Version 5 Specification, which is required for Insight Remote Support FRU configuration tree processing.
Chapter 13: Configuring OpenVMS Servers See section "Installing the ELMC OpenVMS Software Package on the Monitored Device", for more precautions about one system disk versus multiple system disks. Grant Permissions Required to Run ELMC To execute any ELMC commands, the user needs all of the following OpenVMS privileges.
Chapter 13: Configuring OpenVMS Servers Install Target: A directory on disk C, specified by you during the installation. Result: ELMC installs itself for all nodes. Note: In all cases the installation package also lets you choose only a subset of the nodes that can see the install location.
Chapter 13: Configuring OpenVMS Servers Type the six-character serial number provided on the tag in the power cabinet. Note: This issue also can arise when multiple AlphaServers are ordered, because the factory may assign an identical serial number to each system. In this scenario, Insight RS does not work correctly because it requires that each AlphaServer have a unique number.
Chapter 13: Configuring OpenVMS Servers Note: The ProgramData folder is a hidden folder. To view this folder, set the folder options to show hidden folders. 4. Copy the OpenVMS Itanium ELMC software package (ELMC[version]_OVMSI64.EXE) to the OpenVMS monitored device. Place the .exe file in an empty directory. Make sure that: n There are no other kits in the directory, especially other versions of ELMC kits. n There are no old ELMC or WCCProxy files in the directory left over from previous operations.
Chapter 13: Configuring OpenVMS Servers OpenVMS documentation for Indictment Service to learn how to modify this procedure to meet your needs. 2. Reboot the server for the changes to take effect. When the Indictment Server is started, there will be an INDICT_SERVER process shown in the SHOW SYS output: ES47S3_V8.3>>sho sys OpenVMS V8.3 on node ES47S3 17-NOV-2008 15:29:15.48 Uptime 0 00:13:01 Pid Process Name State Pri I/O CPU Page flts Pages 0000041C INDICT_SERVER HIB 8 6 0 00:00:00.
Chapter 13: Configuring OpenVMS Servers 3. From the Select and Configure Protocol drop-down list, select Event Log Monitoring Collector (ELMC). 4. Click New. The New Credential dialog box appears. Insight RS creates the protocol credential and it appears in the credentials table. HP Insight Remote Support 7.0.
Chapter 14: Configuring Tru64 UNIX Servers Important: Configuration collections are not supported on HP AlphaServer products. Important: HP only provides limited remote support for customers using HP Alpha servers. As with standard support, HP Insight Remote Support version 7.x will attempt to discover these products as remotely monitored HP products and send information about failure events to HP.
Chapter 14: Configuring Tru64 UNIX Servers Note: HP Sustaining Engineering maintains a schedule of support for the Tru64 UNIX operating system. HP does not commit to supporting Insight Remote Support when installed on an operating system version that has exceeded its end-of-support date. l Minimum 20 MB free disk space for installation of all components. l TCP/IP services must be installed and running. l Upgrade to V1.
Chapter 14: Configuring Tru64 UNIX Servers Tru64 UNIX Version 4.0G 1. Stop the binlogd process: # /sbin/init.d/binlog stop 2. If desired, move the original error log to any appropriate name, for example: # mv /var/adm/binary.errlog /var/adm/binary.errlog.2002_06_11 Saved logs can be analyzed at a later time. 3. If you skipped step 2, remove the original error log: # rm /var/adm/binary.errlog 4. Restart the binlogd process: # /sbin/init.d/binlog start Tru64 UNIX Version 5.
Chapter 14: Configuring Tru64 UNIX Servers # mv /var/cluster/members//adm/binary.errlog /var/cluster/members//adm/binary.errlog.2002_06_11 # mv /var/cluster/members//adm/binlog.saved/binary.errlog.saved /var/cluster/members//adm/binlog.saved/binary.errlog.saved.2002_06_11 4. Remove existing error logs, ignoring any No such file or directory errors: # rm /var/adm/binary.errlog # rm /var/cluster/members//adm/binary.errlog # rm /var/cluster/members//adm/binlog.saved/binary.
Chapter 14: Configuring Tru64 UNIX Servers At the SRM console firmware prompt (the prompt when you first power on the server), check the serial number with the following command: show sys_serial_num The serial number shown should match the actual serial number on the model/serial number tag located in the power cabinet. If necessary, change the serial number with the following command: set sys_serial_num Type the six-character serial number provided on the tag in the power cabinet.
Chapter 14: Configuring Tru64 UNIX Servers Add Protocol Credentials and Start Discovery To discover your monitored devices, complete the following steps: Create the ELMC Protocol in the Insight RS Console To configure ELMC in the Insight RS Console, complete the following steps: 1. In a web browser, log on to the Insight RS Console. 2. In the main menu, select Discovery and click the Credentials tab. 3. From the Select and Configure Protocol drop-down list, select Event Log Monitoring Collector (ELMC). 4.
Chapter 15: Configuring IBM Servers Insight Remote Support (RS) must be able to communicate with your IBM server before it can be monitored. Insight RS can communicate with IBM servers running Windows with SNMP. The following information describes how to install and configure the communication protocols and other recommended software components so that it can be monitored by Insight RS.
Chapter 15: Configuring IBM Servers Configure the Windows SNMP Service 1. On the monitored device, open the SNMP Service Properties window and select the Traps tab. 2. In the Community name field, type the SNMP community name and click Add to list. Important: The community name must match the community name as configured in the Insight RS Console. 3. In the trap destinations field, add the Hosting Device to the list: a. To open the SNMP Service Configuration window, click Add. b.
Chapter 15: Configuring IBM Servers 5. Select the Send authentication trap check box. 6. Click the Accept SNMP packets from any host option. 7. Click OK to save the settings. Install and Configure SNMP IBM Director Agent must be installed on the IBM server and the SNMP service must be configured. IBM Director Agent includes an SNMP agent. On a Windows 2008 and 2008 R2 server the solution was tested with IBM Systems Director Common Agent version 6.1.1.
Chapter 15: Configuring IBM Servers 1. To configure the service processor’s trap destination use the Management Processor Assistant task in the IBM Director console. 2. Add the IP address of the Hosting Device as a trap destination. 3. Restart the service processor. Configuring the Management Module of the IBM BladeCenter® Chassis 1. Login into to the BladeCenter Management Module web page. 2. Select Alerts in the MM Control section of the left menu. The Alerts page appears. 3.
Chapter 15: Configuring IBM Servers 4. On the Remote Alert Recipient page: a. From the Status drop-down list, select Enabled. b. In the Name field, type a Remote Alert Recipient name. For example: Remote Alert Recipient 1 c. From the Notification method drop-down list, select SNMPover LAN. d. In the IP address or host name field, type the Hosting Device IP address. e. Optional: In the E-mail address field, type an e-mail address, if you want to be notified about alerts by e-mail 5. Select Save.
Chapter 15: Configuring IBM Servers 8. Save your settings. 9. In the MM Control section of the left menu, select Network Protocol. The Network Protocol page appears. 10. Scroll down to SNMP. HP Insight Remote Support 7.0.
Chapter 15: Configuring IBM Servers 11. From the SNMPv1 agent drop-down list, select Enabled. 12. Configure an SNMPv1 Community: a. In the Community Name field, type a SNMP community name. b. From the Access Type drop-down list, select Get. c. In the Host Name or IP Address field, type the Hosting Device host name or IP address. 13. Click Save. 14. Restart the BladeCenter Management Module: a. In the MM Control section of the left menu, select Restart MM. b. Click Restart.
Chapter 15: Configuring IBM Servers http://www.redbooks.ibm.com/redbooks/pdfs/sg246188.pdf l A combined device driver for all service processors is available for each operating system at: http://www.ibm.com/systems/support/. l No additional driver is needed for servers that have only an ISM processor installed. Upgrade the service processor firmware to the latest version to ensure that all features of the service processors are available.
Chapter 15: Configuring IBM Servers 1. In the Insight RS Console, verify the server appears on the Devices page. Important: For IBM BladeCenter® chassis the Product column is empty by default. 2. Click the Device Name and on the Device tab, type the following information: Note: The HP Account Support team must add the entitlement data for IBM servers in the Insight RS Console.
Chapter 16: Configuring Dell PowerEdge Servers Insight Remote Support (RS) must be able to communicate with your Dell PowerEdge server before it can be monitored. Insight RS can communicate with Dell PowerEdge servers with SNMP. The following information describes how to install and configure the communication protocols and other recommended software components so that it can be monitored by Insight RS.
Chapter 16: Configuring Dell PowerEdge Servers 2. In the Community name field, type the SNMP community name and click Add to list. Important: The community name must match the community name as configured in the Insight RS Console. 3. In the trap destinations field, add the Hosting Device to the list: a. To open the SNMP Service Configuration window, click Add. b. Type the host name or IP address of the Hosting Device. c. Click Add. 4.
Chapter 16: Configuring Dell PowerEdge Servers 5. Select the Send authentication trap check box. 6. Click the Accept SNMP packets from any host option. 7. Click OK to save the settings. Install and Configure SNMP Dell OpenManage Server Administrator must be installed on the Dell PowerEdge server and SNMP service must be configured. On a Windows 2008 and 2008 R2 server the solution was tested with Dell OpenManage Server Administrator version 6.2.0.
Chapter 16: Configuring Dell PowerEdge Servers selecting Manage, and then clicking Device Manager. See also Dell OpenManage Installation and Security User’s Guide. Configuring SNMP Traps in Dell OpenManage Server Administrator 1. Open Dell OpenManage Server Administrator. 2. Click the Alert Management tab. 3. Click the SNMP Traps link. 4. Select the following options: n System n Critical n Temperatures n Voltages n Logs n Memory n Batteries 5. Click Apply Changes.
Chapter 16: Configuring Dell PowerEdge Servers Add Protocol Credentials and Start Discovery To discover your monitored devices, complete the following steps: Discover the Device in the Insight RS Console To discover the device from the Insight RS Console, complete the following steps: 1. In a web browser, log on to the Insight RS Console. 2. In the main menu, select Discovery and click the Sources tab. 3. Expand the IP Addresses section and add the IP address for your device: a. Click New. b.
Chapter 17: Configuring BladeSystem c-Class Enclosures HP BladeSystem c-Class Enclosures can be monitored by Insight Remote Support (RS). Configuring the BladeSystem c-Class Enclosure only enables Insight RS to monitor the enclosure itself. The blades installed in the BladeSystem c-Class Enclosure need to be configured separately to be monitored by Insight RS. See "Identify Required Communication Protocols and Software Components" on page 21 for information about configuring your individual blade types.
Chapter 17: Configuring BladeSystem c-Class Enclosures Fulfill Configuration Requirements To configure your BladeSystem c-Class Enclosures through the OA to be monitored by Insight RS, complete the following steps: Table 17.1 BladeSystem c-Class Enclosure Through the OA Configuration Steps Task Complete? Make sure Insight RS supports your BladeSystem c-Class enclosure by checking the HP Insight Remote Support Release Notes. Register for Remote Support through the Onboard Administrator.
Chapter 17: Configuring BladeSystem c-Class Enclosures 5. Type a host name or IP address. 6. In the Port field, type 7906. 7. Click Register. Verify Communication Between Monitored Device and Insight RS To verify communication between your monitored device and Insight RS, complete the following steps: Sending a Test Event After registering the c-Class enclosure with Insight Remote Support, send a test event to confirm the connection. 1.
Chapter 17: Configuring BladeSystem c-Class Enclosures Insight RS converts the OA service event Time Generated value to the time zone of the browser used to access the Insight RS Console. Note: Test events are automatically closed by HP since no further actions are required.
Chapter 17: Configuring BladeSystem c-Class Enclosures Configuring BladeSystem c-Class Enclosures Using SNMP HP BladeSystem c-Class Enclosures can be monitored by Insight Remote Support (RS). Configuring the BladeSystem c-Class Enclosure only enables Insight RS to monitor the enclosure itself. The blades installed in the BladeSystem c-Class Enclosure need to be configured separately to be monitored by Insight RS.
Chapter 17: Configuring BladeSystem c-Class Enclosures 1. In a web browser, open the HP BladeSystem Onboard Administrator. 2. In the log on screen, type your user name and password and click Sign In. 3. Expand Enclosure Information → Enclosure Settings. 4. Click SNMP Settings. 5. In the System Information pane, select the Enable SNMP check box and complete the following steps: a. Add system location and contact information. b. Set Read and Write community strings. 6. Click Apply. 7.
Chapter 17: Configuring BladeSystem c-Class Enclosures RS Console. To configure SNMPv1 in the Insight RS Console, complete the following steps: 1. In a web browser, log on to the Insight RS Console. 2. In the main menu, select Discovery and click the Credentials tab. 3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol Version 1. 4. Click New. The New Credential dialog box appears. 5. Enter the Community String you have configured on your device. 6. Click Add.
Chapter 18: Configuring P6000 and Enterprise Virtual Arrays The P6000 Command View server can be either a standalone server with the Command View and SMI-S software installed (referred to as Server Based Management - SBM) or it can be built in to the EVA device itself, referred to as Array Based Management ABM.
Chapter 18: Configuring P6000 and Enterprise Virtual Arrays Table 18.1 P6000 and Enterprise Virtual Array Using SBM Configuration Steps Task Complete? Make sure Insight RS supports your P6000 disk array by checking the HP Insight Remote Support Release Notes. Verify HP P6000 Command View is installed and configured on the Storage Management Server. Install ELMC on the Storage Management Server. Add ELMC to the Insight RS Console. Add P6000 Command View to the Insight RS Console.
Chapter 18: Configuring P6000 and Enterprise Virtual Arrays To be supported by Insight Remote Support, the monitored device must have P6000 Command View installed (version 9.4 or later) and be managing at least one array. SMI-S is delivered with the P6000 Command View installation and is required because it serves as the communication path between Insight Remote Support and the array, using CIMOM for WBEM communications.
Chapter 18: Configuring P6000 and Enterprise Virtual Arrays 5989. The subsequent P6000 Command View installation can detect if port 5989 is in use, and can redirect to a different port. To obtain a snapshot of the current port assignments in your environment, in a command window, execute the following command: C:\ netstat –anb >netstat.txt Installing HP SIM For the First Time When installing HP SIM for the first time, the First Time Wizard includes a step to configure WBEM/WMI Mapper Proxy.
Chapter 18: Configuring P6000 and Enterprise Virtual Arrays 3. Save the wbemportlist.xml file. 4. Restart the HP SIM service: right click on the HP Systems Insight Manager service and select restart from the drop-down list.
Chapter 18: Configuring P6000 and Enterprise Virtual Arrays enableHttpConnection=false sslCertificateFilePath=C:\hp\sslshare\cert.pem sslKeyFilePath=C:\hp\sslshare\file.pem httpsPort=5989 To change the WMI Mapper Proxy port in HP SIM: 1. Log in to HP SIM with Administrative privileges. 2. Verify the existing credentials for the Hosting Device are correct: a. Open the All Systems list and select the device serving as the HP SIM CMS from the list. b. Click the Tools & Links tab. c.
Chapter 18: Configuring P6000 and Enterprise Virtual Arrays The following example shows the complete file, with port number 60000 used as the HTTPS port for SMI-S:
Chapter 18: Configuring P6000 and Enterprise Virtual Arrays If one or both of these ports are in use, the installation provides an additional configuration screen on which you can change the port numbers. The SMI-S installer suggests port 60000 if that port is not in use. SMI-S retains port 5988 if it does not conflict with another port number. SMI-S uses these ports when the HP CIM Object Manager (CIMOM) process starts.
Chapter 18: Configuring P6000 and Enterprise Virtual Arrays 1. Open the following file: C:\Program Files\Hewlett-Packard\SMI-S\CXWSCimom\config\cxws.properties 2. Locate the cxws.http.port and cxws.https.port entries and reset the to the following values: cxws.http.port=5988 cxws.https.port=60000 3. Restart the HP CIMOM service. Documentation for P6000 Command View P6000 Command View documentation is available at: http://h18006.www1.hp.com/products/storage/software/cmdvieweva/index.html.
Chapter 18: Configuring P6000 and Enterprise Virtual Arrays Note: The ProgramData folder is a hidden folder. To view this folder, set the folder options to show hidden folders. 4. Copy the appropriate Windows x86/x64 ELMC software package into a temporary directory on the P6000 Command View server. 5. Double-click the installer file to begin the install process. The kit will install and finish with no user prompting. No user configuration input is required to install the ELMC software package.
Chapter 18: Configuring P6000 and Enterprise Virtual Arrays To configure the Discovery settings and discover the EVAs, complete the following steps: 1. In the Insight RS Console, navigate to Discovery → Credentials. 2. Create discovery protocol credentials for each Named Credential created earlier. a. In the Select and Configure Protocol drop-down list, select HP P6000 Command View. b. Click New. c. In the Named Credential drop-down list, select the Named Credential created earlier. d. Click Add. 3.
Chapter 18: Configuring P6000 and Enterprise Virtual Arrays 3. On the General tab, click System Options. 4. On the System Options screen, under the Service heading, click Perform remote service test. 5. On the Perform Remote Service Test screen, click Perform Remote Service Test. 6. Click OK. 7. In the Insight RS Console, navigate to Devices → Service Events to verify that the event was received.
Chapter 18: Configuring P6000 and Enterprise Virtual Arrays Being in this mode has no effect on the functionality of P6000 Command View or event handling within P6000 Command View. This mode is solely for the benefit of external support tools, such as Insight Remote Support. To enable User-Initiated Service Mode, complete the following steps: 1. Open P6000 Command View and select a device in the left menu tree. 2.
Chapter 18: Configuring P6000 and Enterprise Virtual Arrays Important: The ABM Fully Qualified Domain Name must not be the same as the EVA array name. Insight RS has no way to differentiate between two devices that have the same name. Fulfill Configuration Requirements To configure your P6000 and Enterprise Virtual Arrays using ABM to be monitored by Insight RS, complete the following steps: Table 18.
Chapter 18: Configuring P6000 and Enterprise Virtual Arrays 1. In a web browser, log on to the Insight RS Console. 2. In the main menu, select Discovery and click the Credentials tab. 3. From the Select and Configure Protocol drop-down list, select Event Log Monitoring Collector (ELMC). 4. Click New. The New Credential dialog box appears. Insight RS creates the protocol credential and it appears in the credentials table.
Chapter 19: Configuring StoreVirtual P4000 Storage Systems HP Insight Remote Support software delivers secure remote support for your HP servers, storage, network, and SAN environments, which includes the P4000 SAN. Note: HP StoreVirtual Storage is the new name for HP LeftHand Storage and HP P4000 SAN solutions. LeftHand Operating System (LeftHand OS) is the new name for SAN/iQ.
Chapter 19: Configuring StoreVirtual P4000 Storage Systems Install and Configure CMC on the Hosting Device You need to do the complete install of Centralized Management Console (CMC) to install the SNMP MIBs. If you do not modify the SNMP defaults that CMC uses, then SNMP should work with Insight Remote Support without modification. Insight RS supports CMC 9.0 and higher (CMC 11.0 is recommended) CMC 11.0 can be used to manage LeftHand OS 9.5, 10.x, and 11.0 storage nodes.
Chapter 19: Configuring StoreVirtual P4000 Storage Systems Remote Support can co-exist with Service Console without conflict. 2. Use the Find Nodes wizard to discover the storage systems on the network, using either IP addresses or host names, or by using the subnet and gateway mask of the storage network. The found storage systems appear in the available category in the CMC. HP Insight Remote Support 7.0.
Chapter 19: Configuring StoreVirtual P4000 Storage Systems Upgrade LeftHand OS on the P4000 Storage Systems Note: LeftHand Operating System (LeftHand OS) is the new name for SAN/iQ. Use CMC to upgrade to LeftHand OS 9.5 or higher (LeftHand OS 11.0 is recommended) on the P4000 Storage Systems. If your P4000 Storage Systems already has LeftHand OS 9.5 installed, you do not need to perform this procedure. Note: For LeftHand OS 9.5 devices, Patch Set 05 is required for all devices. CMC version 9.
Chapter 19: Configuring StoreVirtual P4000 Storage Systems Figure 19.1 Find the Storage Node Running the VIP l Remote Copy — If you are upgrading management groups with Remote Copy associations, you should upgrade the remote management groups first. If you upgrade the primary group first, Remote Copy may stop working temporarily, until both the primary management group and the remote group have finished upgrading. Upgrade the primary site immediately after upgrading the remote site.
Chapter 19: Configuring StoreVirtual P4000 Storage Systems Figure 19.2 Viewing the CMC Upgrade/Installation Window Increase the Size of the OS Disk on the VSAs Due to changes in the size of the VMware tools that get installed during software upgrades from pre-8.5 versions of LeftHand OS, you must increase the size of the OS disk before upgrading the VSA. Additional space requirements are necessary for future software releases, as well.
Chapter 19: Configuring StoreVirtual P4000 Storage Systems 7. Using the VI Client, power on the VSA. 8. Find the VSA in the CMC and apply the upgrade. Verify Management Group Version l When upgrading from version LeftHand OS 7.x to release 9.5 or higher, the management group version will not move to the new release version until all storage nodes in the management group (and in the remote management group if a Remote Copy relationship exists) are upgraded to release LeftHand OS 9.5 or higher.
Chapter 19: Configuring StoreVirtual P4000 Storage Systems LeftHand OS 9.5 and higher Management Groups configure the Hosting Device SNMP trap host destination once at the Management Group level. Even though you only configure SNMP once at the Management Group level under CMC 10.0 and higher, you need to configure SNMP on the Hosting Device to allow traps from all LeftHand OS nodes.
Chapter 19: Configuring StoreVirtual P4000 Storage Systems 3. Select Alerts in the left menu tree, and verify that alerts are configured with the "trap" option for each storage system. Note: LeftHand OS ships by default with traps set for all alert cases. HP Insight Remote Support 7.0.
Chapter 19: Configuring StoreVirtual P4000 Storage Systems 4. Add the Hosting Device IP address to the P4000 Storage System's SNMP trap send list. The Hosting Device IP address is needed to configure SNMP traps on each storage system. Note that in CMC 9.0 and higher, SNMP traps are configured at the Management Group level, not at the node level. a. Select SNMP in the left menu tree and open the SNMP Traps tab. b. Open the Edit SNMP Traps dialog by browsing to SNMP Trap Tasks → Edit SNMP Traps.
Chapter 19: Configuring StoreVirtual P4000 Storage Systems c. In the Edit SNMP Traps dialog, click Add. d. In the Add IP or Hostname dialog, type the IP address or host name into the IP or Hostname field. Verify that the Trap Version is v1, and click OK. 5. Repeat steps 3 to 4 for each P4000 Storage System. Alternatively, you could also configure one node using steps 3 to 4, then use the CMC copy node configuration option to copy the configuration to all other nodes. 6.
Chapter 19: Configuring StoreVirtual P4000 Storage Systems a. Select Administration in the left menu tree. b. Create a user group with read-only access, if one does not already exist. Browse to Administrative Tasks → New Group. c. Create a new user. First select the group you created in the previous step, then go to Administrative Tasks → New User. Type the User Name, Password, and click Add to add this user to the read-only user group you created. HP Insight Remote Support 7.0.
Chapter 19: Configuring StoreVirtual P4000 Storage Systems Add Protocol Credentials and Start Discovery To discover your monitored devices, complete the following steps: Add P4000 SAN Solution (SAN/iQ) Protocol to the Insight RS Console To add the P4000 SAN Solution (SAN/iQ) protocol, complete the following steps: 1. In a web browser, log on to the Insight RS Console (https://:7906.) 2. Create a Named Credential for every set of Management Group credentials: a.
Chapter 19: Configuring StoreVirtual P4000 Storage Systems i. In the Select and Configure Protocol drop-down list, select P4000 SAN Solution (SAN/iQ). ii. Click New. iii. In the Named Credential drop-down list, select the Named Credential created earlier. iv. Click Add. Discover the P4000 To discover the P4000, complete the following steps: 1. In a web browser, log on to the Insight RS Console (https://:7906.) 2.
Chapter 19: Configuring StoreVirtual P4000 Storage Systems 1. If synchronizing Insight RS with HP SIM, verify that the Device Name appears correctly on the Devices screen. If the devices appears as a Serial Number rather than as an IP address or host name, perform the following tasks: a. Click the Device Name, and on the Device tab, expand the Status section. Click Delete Device. b. On the Credentials tab, verify that the credentials assigned to the device are correct. c.
Chapter 19: Configuring StoreVirtual P4000 Storage Systems Go to Hosting Device configurations to verify that the test event was posted to the Hosting Device logs. The CMC read-only credentials were verified during device discovery when each LeftHand OS device was added to Hosting Device monitored listed. HP Insight Remote Support 7.0.
Chapter 20: Configuring P2000 G3 Modular Smart Arrays Fulfill Configuration Requirements To configure your P2000 G3 Modular Smart Arrays to be monitored by Insight RS, complete the following steps: Table 20.1 P2000 and Modular Smart Array Configuration Steps Task Complete? Make sure Insight RS supports your Modular Smart Array by checking the HP Insight Remote Support Release Notes. Configure SNMP on the MSA. Configure WBEM on the MSA. Add the SNMP protocol to the Insight RS Console.
Chapter 20: Configuring P2000 G3 Modular Smart Arrays Remote Support will not be supported. It is critical to verify SNMP is active. 4. From the menu select Configuration → Services → SNMP Notification. 5. On the Configure SNMP Notification page, modify the SNMP settings to include the Hosting Device as an SNMP Trap Host and select your Notification Level from the drop-down list (the Informational level is recommended). HP Insight Remote Support 7.0.
Chapter 20: Configuring P2000 G3 Modular Smart Arrays 6. Click Apply to commit your changes. 7. Exit the utility and discover your P2000 G3 in the Insight RS Console. About WBEM on the P2000 G3 The SMI-S provider for the P2000 G3 MSA is integrated in the firmware and delivered with the P2000 G3 series disk arrays. It provides a WBEM-based management framework. Insight RS can interact with this embedded provider directly and does not need an intermediate proxy provider.
Chapter 20: Configuring P2000 G3 Modular Smart Arrays 1. In a web browser, log on to the Insight RS Console. 2. In the Main Menu, select Discovery and click the Credentials tab. 3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol Version 1. 4. Click New. The New Credential dialog box appears. 5. Enter the Community String you have configured on your device. 6. Click Add. Insight RS creates the protocol credential and it appears in the credentials table.
Chapter 20: Configuring P2000 G3 Modular Smart Arrays from the controller that was not discovered could be lost. d. Click Add. 4. Click Start Discovery. Verify Communication Between Monitored Device and Insight RS To verify communication between your monitored device and Insight RS, complete the following steps: Verify Service Event Monitoring To send a test event from the P2000, complete the following steps: 1. In a web browser, log on to the HP MSA Storage Management Utility (SMU). 2.
Chapter 21: Configuring MSA23xx G2 Modular Smart Arrays Fulfill Configuration Requirements To configure your MSA23xx G2 Modular Smart Arrays to be monitored by Insight RS, complete the following steps: Table 21.1 P2000 and Modular Smart Array Configuration Steps Task Complete? Make sure Insight RS supports your Modular Smart Array by checking the HP Insight Remote Support Release Notes. Configure SNMP on the MSA. Configure WBEM on the MSA. Add the SNMP protocol to the Insight RS Console.
Chapter 21: Configuring MSA23xx G2 Modular Smart Arrays Important: SNMP should be active by default, but if it for any reason it is not, Insight Remote Support will not be supported. It is critical to verify SNMP is active. 4. From the menu select Configuration → Services → SNMP Notification. 5.
Chapter 21: Configuring MSA23xx G2 Modular Smart Arrays 6. Click Apply to commit your changes. 7. Exit the utility and discover your 23xx in the Insight RS Console. Install WBEM SMI-S Proxy Provider Software The MSA2000 G2 SMI-S Proxy Provider software must be installed on a ProLiant host server that will manage your MSA23xx devices. It provides a WBEM-based management framework. Insight RS can interact with this proxy provider to gather collections on your MSA23xx devices.
Chapter 21: Configuring MSA23xx G2 Modular Smart Arrays Add Protocol Credentials and Start Discovery To discover your monitored devices, complete the following steps: Create an SNMP Protocol Credential in Insight RS If your device's SNMP community string is set to public and your community access mode is read only, Insight RS automatically associates an SNMPv1 protocol with your device.
Chapter 21: Configuring MSA23xx G2 Modular Smart Arrays 1. In a web browser, log on to the Insight RS Console. 2. In the main menu, select Discovery and click the Sources tab. 3. Expand the IP Addresses section and add the IP address to be discovered. When discovering the MSA23xx G2, add the IP address of each MSA23xx G2 as well as the ProLiant server running the SMI-S Proxy Provider software. This ensures that the necessary event and collection services are configured. a. Click New. b.
Chapter 22: Configuring MSA2xxx G1 Modular Smart Arrays Important: Configuration collections are not supported, except when the MSA2xxx G1 is part of a SAN collection. Fulfill Configuration Requirements To configure your MSA2xxx G1 Modular Smart Arrays to be monitored by Insight RS, complete the following steps: Table 22.1 P2000 and Modular Smart Array Configuration Steps Task Complete? Make sure Insight RS supports your Modular Smart Array by checking the HP Insight Remote Support Release Notes.
Chapter 22: Configuring MSA2xxx G1 Modular Smart Arrays 3. In the expanded list select the Event Notification link. HP Insight Remote Support 7.0.
Chapter 22: Configuring MSA2xxx G1 Modular Smart Arrays 4. On the Event Notification Summary page, verify that the SNMP notification types (Visual Alerts, Email Alerts, and SNMP Traps) are enabled, and click Change Notification Settings to commit the changes. 5. Click the SNMP configuration link under the Event Notification heading in the left panel. 6. Modify the SNMP settings to include the Hosting Device as an SNMP Trap Host and make sure the SNMP Traps Enabled option is set to Yes.
Chapter 22: Configuring MSA2xxx G1 Modular Smart Arrays 7. Click Change SNMP Traps Configuration to commit your changes. Note: If your Insight Remote Support Hosting Device is fully configured, you can send the test event from this page. If the Hosting Device is not yet configured, you can return to this page later to send the Test Event. 8. Exit the utility and discover your 2012/2112 in the Insight RS Console.
Chapter 22: Configuring MSA2xxx G1 Modular Smart Arrays 5. Enter the Community String you have configured on your device. 6. Click Add. Insight RS creates the protocol credential and it appears in the credentials table. Discover the Device in the Insight RS Console To discover the device from the Insight RS Console, complete the following steps: 1. In a web browser, log on to the Insight RS Console. 2. In the main menu, select Discovery and click the Sources tab. 3.
Chapter 23: Configuring MSA15xx Modular Smart Arrays Fulfill Configuration Requirements To configure your MSA15xx Modular Smart Arrays to be monitored by Insight RS, complete the following steps: Table 23.1 P2000 and Modular Smart Array Configuration Steps Task Complete? Make sure Insight RS supports your Modular Smart Array by checking the HP Insight Remote Support Release Notes. Configure SNMP on the MSA. Add the SNMP protocol to the Insight RS Console.
Chapter 23: Configuring MSA15xx Modular Smart Arrays 3. On the Configure tab, expand the Management Port list for the MSA 1510i. 4. Select the SNMP Service link from the list. 5. Modify any necessary configuration fields and make sure that the IP address of the Hosting Device is listed as a Trap Address. 6. Click OK to commit your changes. 7. Exit the utility and discover your 1510i in the Insight RS Console.
Chapter 23: Configuring MSA15xx Modular Smart Arrays Create an SNMP Protocol Credential in Insight RS If your device's SNMP community string is set to public and your community access mode is read only, Insight RS automatically associates an SNMPv1 protocol with your device. If you use a different community string or use a nonstandard port, you must create an SNMPv1 protocol credential in the Insight RS Console. To configure SNMPv1 in the Insight RS Console, complete the following steps: 1.
Chapter 24: Configuring StoreEasy Storage Systems Insight Remote Support (RS) requires WMI to be installed and configured on your StoreEasy Storage system (formerly Commercial NAS) in order for Insight RS to communicate with your device for discovery, event monitoring, and collections. WMI comes pre-installed on StoreEasy Storage systems. No additional configuration of WMI is necessary.
Chapter 24: Configuring StoreEasy Storage Systems n Windows Management Instrumentation (WMI-In) 5. Select the Outbound Rules link from the left menu and make sure the following outbound rules are enabled: n File and Printer Sharing (Echo Request - ICMPv4-Out) n Windows Management Instrumentation (WMI-Out) More information regarding security in Insight RS can be found in the HP Insight Remote Support Security White Paper at: http://www.hp.com/go/insightremotesupport/docs.
Chapter 24: Configuring StoreEasy Storage Systems a. Click New. b. Select the Single Address, Address Range, or Address List option. c. Type the IP address(es) of the devices to be discovered. d. Click Add. 4. Click Start Discovery.
Chapter 24: Configuring StoreEasy Storage Systems 5. In the Send Test Indication screen, select an Event ID type (any will work) and click Send. Viewing Test Events In the Insight RS Console After sending the test indication, verify it arrived in the Insight RS Console. To verify the test indication arrived, complete the following steps: 1. In a web browser, log on to the Insight RS Console. 2. In the main menu, select Service Events.
Chapter 25: Configuring StoreAll Network Storage Systems Note: HP StoreAll Storage is the new name for HP IBRIX Storage. Note the following limitations: l For X9000 systems, the Insight Remote Support implementation is limited to hardware events. l Some manual configurations require that the X9320 and X9300 nodes be recognized as a X9000 solution. See section "Configure Warranty and Contract Information" on page 204.
Chapter 25: Configuring StoreAll Network Storage Systems #
Chapter 25: Configuring StoreAll Network Storage Systems # service snmpd restart l HP SNMP Agents: # service hp-snmp-agents start To ensure that hp-snmp-agents restarts when the system is rebooted, type the following command: # chkconfig hp-snmp-agents on Add Protocol Credentials and Start Discovery To discover your monitored devices, complete the following steps: Create an SNMP Protocol Credential in Insight RS If your device's SNMP community string is set to public and your community access mode is re
Chapter 25: Configuring StoreAll Network Storage Systems Configure Warranty and Contract Information Configure the Insight RS Console to enable remote support for X9000 systems. l Custom field settings for X9300/X9320 Servers are discovered with their IP addresses. When a server is discovered, edit the system properties in the Insight RS Console. In the main menu, click Devices, then click the device name of your system.
Chapter 25: Configuring StoreAll Network Storage Systems For example, if the Hosting Device IP address is 10.2.2.2 and the X9000 node is 10.2.2.10, type the following: snmptrap -v1 -c public 10.2.2.2 .1.3.6.1.4.1.232 10.2.2.10 6 11003 1234 .1.3.6.1.2.1.1.5.0 s test .1.3.6.1.4.1.232.11.2.11.1.0 i 0 .1.3.6.1.4.1.232.11.2.8.1.0 s "X9000 remote support testing" For Insight Remote Support, replace the Hosting Device IP address with the IP address of the Insight Remote Support server.
Chapter 26: Configuring Virtual Library Systems Fulfill Configuration Requirements To configure your Virtual Library Systems to be monitored by Insight RS, complete the following steps: Table 26.1 Virtual Library System Configuration Steps Task Complete? Make sure Insight RS supports your Virtual Library System by checking the HP Insight Remote Support Release Notes. Configure SNMP on the Virtual Library System. Discover the Virtual Library System in the Insight RS Console.
Chapter 26: Configuring Virtual Library Systems 5. In the Community String field, if you select a non-standard trap community name (for example, something other than public), verify the Insight RS Console recognizes this name. 6. The trap version is 1. 7. Click Add. Add Protocol Credentials and Start Discovery To discover your monitored devices, complete the following steps: Discover the Device in the Insight RS Console To discover the device from the Insight RS Console, complete the following steps: 1.
Chapter 27: Configuring StoreOnce Backup (D2D) Systems Fulfill Configuration Requirements To configure your StoreOnce Backup (D2D) Systems to be monitored by Insight RS, complete the following steps: Table 27.1 StoreOnce Backup (D2D) System Configuration Steps Task Complete? Make sure Insight RS supports your StoreOnce Backup (D2D) System by checking the HP Insight Remote Support Release Notes. Verify Firmware version on the StoreOnce Backup (D2D) System.
Chapter 27: Configuring StoreOnce Backup (D2D) Systems Configure SNMP on Your StoreOnce Backup (D2D) Systems You must add the Hosting Device as a trap destination on your D2D Backup Systems for service events to reach Insight RS. Configure SNMP for StoreOnce Gen2 Backup (D2D) Systems To configure SNMP for StoreOnce Backup (D2D) Systems, complete the following steps: 1. Log on to the StoreOnce Backup System as "administrator" using https://. 2. Click the Configuration tab. 3.
Chapter 27: Configuring StoreOnce Backup (D2D) Systems Configure SNMP for StoreOnce Gen3 B6200 and 2600/4200/4400 Backup Systems To configure the StoreOnce Backup B6200 and 2600/4200/4400 Backup Systems to send traps to Insight Remote Support, complete the following steps: 1. Log on to the StoreOnce Backup System using the SSH protocol (Using "putty.exe" or a similar tool). 2. Check the current SNMP configuration by issuing the CLI command: snmp show config. 3.
Chapter 27: Configuring StoreOnce Backup (D2D) Systems 1. In a web browser, log on to the Insight RS Console. 2. In the main menu, select Discovery and click the Sources tab. 3. Expand the IP Addresses section and add the IP address for your device: a. Click New. b. Select the Single Address, Address Range, or Address List option. c. Type the IP address(es) of the devices to be discovered. d. Click Add. 4. Click Start Discovery. HP Insight Remote Support 7.0.
Chapter 28: Configuring StoreEver Tape Libraries HP’s physical tape libraries require a combination of their own web-based management interfaces and aggregated HP Command View for Tape Libraries (TL) library management software to work with Insight Remote Support (RS). Users configure each library to send SNMP traps for hardware events, such as fan failures, directly to the Insight RS server. Users configure Command View TL to send TapeAssure events over SMI-S such as poor drive margin.
Chapter 28: Configuring StoreEver Tape Libraries Configure Command View TL TapeAssure In addition to managing the tape libraries, Command View for Tape Libraries supplies the WBEM protocol that is necessary for Insight RS to gather collections on your tape libraries.
Chapter 28: Configuring StoreEver Tape Libraries 2. Select the TapeAssure tab and check that the monitored libraries appear in the TapeAssure Overview window. Important: TapeAssure can also monitor standalone tape drives (those not in a tape library) and a host name appears instead of a library name; however, standalone drives cannot be configured for Insight RS.
Chapter 28: Configuring StoreEver Tape Libraries 3. In the left panel, select SNMP Alerts. The current SNMP traps appear in the right panel. 4. Do one of the following: n In the right panel, right-click an SNMP trap, and then select Add Trap Entry. or n Select Actions → Add Trap Entry. The SNMP Trap Entry screen appears. 5. In the Trap Destination field, type the Hosting Device IP address or Fully Qualified Domain Name (FQDN). 6.
Chapter 28: Configuring StoreEver Tape Libraries To allow Insight RS to register for your Enterprise Systems Library (ESL) G3 library health events using SNMP, complete the following steps: 1. Log on to the ESL G3 user interface as admin. 2. In the console, go to Setup → Network Configuration → Network Security Settings. 3. In the Security Configuration screen, select the SNMP/SMI-S tab. Note: Library health events are monitored with SNMP only.
Chapter 28: Configuring StoreEver Tape Libraries the Hosting Device. Use public for the community name. Click Create. Configure Modular Systems Library G3 Series To allow Insight RS to register for your Modular Systems Library (MSL) G3 library health events using SNMP, complete the following steps: 1. Log on to the Command View MSL web interface as Administrator. 2. Click the Configuration tab. 3. Click the Network Management tab. HP Insight Remote Support 7.0.
Chapter 28: Configuring StoreEver Tape Libraries 4. Verify the SNMP Enabled check box is selected. 5. In the IPv4 Target address field type the Hosting Device IP address or FQDN. 6. Verify SNMPv1 is the version selected. 7. In the SNMP Trap Notification Filter, select Critical and Warning Events as the filter level. 8. Click Submit.
Chapter 28: Configuring StoreEver Tape Libraries 4. Verify the SNMP Enabled check box is selected. 5. In the SNMP Targets table, click Edit next to a target without an IP/Hostname. 6. In the IP/Hostname field type the Hosting Device IP address or FQDN. 7. Verify SNMPv1 is the version selected and enter the community string of the Hosting Device. 8. Click Submit. 9. Click OK in the confirmation dialogue box.
Chapter 28: Configuring StoreEver Tape Libraries 5. Enter the Community String you have configured on your device. 6. Click Add. Insight RS creates the protocol credential and it appears in the credentials table. Create a WBEM Protocol Credential in Insight RS For ESL and EML tape libraries, you must create a WBEM protocol in the Insight RS Console for the Command View TL server that monitors your tape libraries. To configure WBEM in the Insight RS Console, complete the following steps: 1.
Chapter 28: Configuring StoreEver Tape Libraries 3. Check that all of the monitored tape libraries and the Command View TL host(s) appear in the devices table. 4. Click the device name and expand the Hardware pane. Verify the correct product number and serial number for the tape library was discovered. Edit the individual devices if any appear to be missing any warranty and contract information. HP Insight Remote Support 7.0.
Chapter 29: Configuring StoreFabric B-Series Switches Fulfill Configuration Requirements To configure your StoreFabric B-Series Switches to be monitored by Insight RS, complete the following steps: Note: Test trap support for B-series SAN switches requires the installation of Fabric Operating System v6.3.0b firmware or higher. For more details, refer to the HP Fabric OS 6.3.0b Customer Advisory at: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectI D=c01924282. Table 29.
Chapter 29: Configuring StoreFabric B-Series Switches SNMPv1 community and trap recipient configuration: Community 1: public (rw) No trap recipient configured yet Community 2: public (rw) No trap recipient configured yet Community 3: public (rw) No trap recipient configured yet Community 4: public (ro) No trap recipient configured yet Community 5: common (ro) No trap recipient configured yet Community 6: FibreChannel (ro) No trap recipient configured yet 3.
Chapter 29: Configuring StoreFabric B-Series Switches Community 1: gcc-public (rw) Trap recipient: 1.2.3.4 Trap port: 162 Trap recipient Severity level: 2 Community 2: public (rw) No trap recipient configured yet Community 3: public (rw) No trap recipient configured yet Community 4: public (ro) No trap recipient configured yet Community 5: common (ro) No trap recipient configured yet Community 6: FibreChannel (ro) No trap recipient configured yet 5.
Chapter 29: Configuring StoreFabric B-Series Switches Entry 1: No access host configured yet Entry 2: No access host configured yet Entry 3: No access host configured yet Entry 4: No access host configured yet Entry 5: No access host configured yet 8.
Chapter 29: Configuring StoreFabric B-Series Switches Customizing MIB-II system variables ... At each prompt, do one of the following: o to accept current value, o enter the appropriate new value, o to skip the rest of configuration, or o to cancel any change. To correct any input mistake: erases the previous character, erases the whole line, sysDescr: [Fibre Channel Switch.] Brocade 4/16 FC Switch sysLocation: [End User Premise.] HP Building 11th floor sysContact: [Field Support.
Chapter 29: Configuring StoreFabric B-Series Switches 1. In a web browser, log on to the Insight RS Console. 2. In the main menu, select Discovery and click the Sources tab. 3. Expand the IP Addresses section and add the IP address for your device: a. Click New. b. Select the Single Address, Address Range, or Address List option. c. Type the IP address(es) of the devices to be discovered. d. Click Add. 4. Click Start Discovery.
Chapter 29: Configuring StoreFabric B-Series Switches 1. Telnet or SSH to the B-Series switch. 2. Show the available traps you can send as tests: snmptraps --show 3. Send a blanket test trap for all tests: snmptraps --send 4. Or send a specific test trap: snmptraps --send --trap_name For example: snmptraps --send -trap_name cp-status-change-trap -ip_address where is the IP address of the Hosting Device.
Chapter 30: Configuring StoreFabric C-Series Switches Fulfill Configuration Requirements To configure your StoreFabric C-Series Switches to be monitored by Insight RS, complete the following steps: Table 30.1 StoreFabric C-Series Switch Configuration Steps Task Complete? Make sure Insight RS supports your C-Series switch by checking the HP Insight Remote Support Release Notes. Configure SNMPv1 on the C-Series switch. Add the SNMP protocol to the Insight RS Console.
Chapter 30: Configuring StoreFabric C-Series Switches Add Protocol Credentials and Start Discovery To discover your monitored devices, complete the following steps: Create an SNMP Protocol Credential in Insight RS If your device's SNMP community string is set to public and your community access mode is read only, Insight RS automatically associates an SNMPv1 protocol with your device.
Chapter 30: Configuring StoreFabric C-Series Switches l Modify any incorrect or missing Warranty and Contract information and customer contact details in the Insight RS Console. Verify Warranty and Contract Information Verify that the warranty and contract information was discovered correctly in the Insight RS Console: 1. In the Insight RS Console, navigate to Devices and click the switch Device Name. 2.
Chapter 31: Configuring StoreFabric H-Series Switches Fulfill Configuration Requirements To configure your StoreFabric H-Series Switches to be monitored by Insight RS, complete the following steps: Table 31.1 StoreFabric H-Series Switch Configuration Steps Task Complete? Make sure Insight RS supports your H-Series switch by checking the HP Insight Remote Support Release Notes. Configure SNMPv1 on the H-Series switch. Add the SNMP protocol to the Insight RS Console.
Chapter 31: Configuring StoreFabric H-Series Switches Create an SNMP Protocol Credential in Insight RS If your device's SNMP community string is set to public and your community access mode is read only, Insight RS automatically associates an SNMPv1 protocol with your device. If you use a different community string or use a nonstandard port, you must create an SNMPv1 protocol credential in the Insight RS Console. To configure SNMPv1 in the Insight RS Console, complete the following steps: 1.
Chapter 31: Configuring StoreFabric H-Series Switches Verify Warranty and Contract Information Verify that the warranty and contract information was discovered correctly in the Insight RS Console: 1. In the Insight RS Console, navigate to Devices and click the switch Device Name. 2. Expand the Hardware section, and make sure the Acquired Serial Number and Acquired Product Number are correct.
Chapter 32: Configuring ProVision-based Networking Switches ProVision-based networking switches (formerly E-series/ProCurve) require SNMP for discovery and event monitoring. ProVision-based switches ship with SNMP installed and enabled. You can use either Telnet or SSH for configuration collections. Telnet is enabled on ProVision-based switches by default. If you want to use SSH for configuration collections, you must enable it (see section "Enabling SSH").
Chapter 32: Configuring ProVision-based Networking Switches Configure SSH Generate the Public/Private key for SSH 1. Type the config command to enable the global configuration mode: # config 2. Type the crypto command to generate an RSA key pair, which includes one public RSA key and one private RSA key. # crypto key generate ssh rsa Enable SSH You only need to enable SSH if you want to use it instead of Telnet. If you choose to use Telnet, you can skip this section.
Chapter 32: Configuring ProVision-based Networking Switches ready. 4. Type the exit command to disconnect. Configure SNMP Communication To verify that SNMP communication is working properly, complete the following steps: 1. Type the show version command to determine which software version your ProVision-based switch is running: # sho ver 2. Type the config command to enable the global configuration mode: # config 3. The output should show a version number similar to x.14.
Chapter 32: Configuring ProVision-based Networking Switches Configure SSH Public Key Authentication Option 1: Using the Hosting Device Certificate Prerequisites l TFTP server — used to move the public key to the ProVision-based switch. Copy the Certificate to the Switch To copy the certificate to the ProVision-based switch, complete the following steps: 1. On the Hosting Device, export the Hosting Device public key.
Chapter 32: Configuring ProVision-based Networking Switches c. Leave the File Upload field blank because the certificate is already in the certificate store and it is identified by using the alias name. d. Type the Certificate Alias of “jetty-manager”, which is the alias given to the certificate when it was exported above. 2. Click Add. Option 2: Using Other Certificates Prerequisites l PuTTYgen — used to generate a key pair if required.
Chapter 32: Configuring ProVision-based Networking Switches 6. Enter configuration mode: configure 7. Turn off filetransfer using SSH: no ip ssh filetransfer 8. Enable the TFTP client: tftp client 9. Move the public key to the switch: copy tftp pub-key-file manager 10. Enable public key authentication: aaa authentication ssh login public-key 11. Enable user/password authentication: aaa authentication ssh enable local 12.
Chapter 32: Configuring ProVision-based Networking Switches uses the -manager portion of the alias as the user name during log on. 2. Click Add. Add Protocol Credentials and Start Discovery To discover your monitored devices, complete the following steps: Discover the Device in the Insight RS Console To discover the device from the Insight RS Console, complete the following steps: 1. In a web browser, log on to the Insight RS Console. 2. In the main menu, select Discovery and click the Sources tab. 3.
Chapter 33: Configuring ComWare-based Networking Switches ComWare-based networking switches (formerly A-Series or h4C/3COM) require SNMP for discovery and event monitoring. Important: Switches configured to use the HP proprietary Intelligent Resilient Framework (IRF) technology or switch stacking capabilities are currently not supported. HP Insight RS only supports standalone mode for these switches.
Chapter 33: Configuring ComWare-based Networking Switches 1. Enter system view, and enable the Telnet service. system-view [Sysname] telnet server enable 2. Configure an IP address for VLAN interface 1. This address will serve as the destination of the Telnet connection. [Switch] interface vlan-interface 1 [Switch-Vlan-interface1] ip address 255.255.255.0 [Switch-Vlan-interface1] quit 3. Set the authentication mode for the user interfaces to AAA.
Chapter 33: Configuring ComWare-based Networking Switches [Switch] local-user manager [Switch-luser-client001] password simple [Switch-luser-client001] service-type ssh [Switch-luser-client001] authorization-attribute level 3 [Switch-luser-client001] quit Verifying Telnet/SSH Communication To verify that Telnet or SSH communication is working properly, complete the following steps: 1. From the Hosting Device, connect to the ComWare-based switch using the protocol you want to verify.
Chapter 33: Configuring ComWare-based Networking Switches Discover the Device in the Insight RS Console To discover the device from the Insight RS Console, complete the following steps: 1. In a web browser, log on to the Insight RS Console. 2. In the main menu, select Discovery and click the Sources tab. 3. Expand the IP Addresses section and add the IP address for your device: a. Click New. b. Select the Single Address, Address Range, or Address List option. c.
Chapter 33: Configuring ComWare-based Networking Switches # snmp-agent snmp-agent community read public snmp-agent sys-info version v1 snmp-agent target-host trap address udp-domain params securitynam e public v1 # If any of the settings are incorrect, use the undo command to remove the setting, for example, undo snmp-agent community read public. Then return to "Setup SNMP Traps" on page 244 and reconfigure the setting that was incorrect. HP Insight Remote Support 7.0.
Chapter 34: Configuring Uninterruptable Power Supplies Uninterruptable Power Systems (UPS) come with either a Management Module or a Network Module installed, depending on the model. Use the appropriate configuration procedure below for your model: l To configure a UPS that uses a Management Module, see "Configuring UPS Management Modules" below. l To configure a UPS that uses a Network Module, see "Configuring UPS Network Modules" on page 249.
Chapter 34: Configuring Uninterruptable Power Supplies For more details about configuring SNMP, see the HP UPS Management Module User Guide. To configure SNMP trap notifications, complete the following steps: 1. Log on to the UPS Management Module web interface. 2. Click the Setup tab, and in the left menu, click Event Notifications. 3. Add the Insight RS Hosting Device as an SNMP trap recipient on the SNMP Traps tab. a. Click the SNMP Traps tab.
Chapter 34: Configuring Uninterruptable Power Supplies 4. Click New. The New Credential dialog box appears. 5. Enter the Community String you have configured on your device. 6. Click Add. Insight RS creates the protocol credential and it appears in the credentials table. Discover the Device in the Insight RS Console To discover the device from the Insight RS Console, complete the following steps: 1. In a web browser, log on to the Insight RS Console. 2.
Chapter 34: Configuring Uninterruptable Power Supplies Fulfill Configuration Requirements To configure your UPS Network Modules to be monitored by Insight RS, complete the following steps: Table 34.2 UPS Network Module Configuration Steps Task Complete? Make sure Insight RS supports your UPS Network Module by checking the HP Insight Remote Support Release Notes. Configure SNMP on the UPS Network Module and set the Hosting Device as a trap receiver. Add the SNMP protocol to the Insight RS Console.
Chapter 34: Configuring Uninterruptable Power Supplies 3. Select the SNMP version from the SNMP Version drop-down list. 4. Fill in the appropriate fields. 5. Click Save. 6. Set the Hosting Device as a trap receiver UPS Network Module web interface. The Trap Receivers Settings screen allows an administrator to configure management applications to receive SNMP traps from the UPS Network Module.
Chapter 34: Configuring Uninterruptable Power Supplies c. Type the host name or the IP address of the management server on which the application is running in the Hostname or IP address field. d. Select the SNMP version from the Protocol drop-down menu. e. If you selected SNMPv1, type the community string in the Trap Community field. f. Select the check box for the appropriate MIB: o HP MIB (cpqpower.mib)—The HP Power MIB o IETF MIB (RFC1628)—A standard UPS MIB g. Click Save.
Chapter 34: Configuring Uninterruptable Power Supplies Verify Communication Between Monitored Device and Insight RS To verify communication between your monitored device and Insight RS, complete the following steps: Send a Test Trap To send a test trap, complete the following steps: 1. Log on to the UPS Network Module web interface. 2. In the left menu, click Notified Applications, then click Add Trap Receiver. Up to three applications can be configured to receive SNMP traps from the UPS Network Module.
Chapter 35: Configuring Modular Cooling Systems Modular Cooling Systems are monitored through the management module that is installed on the Modular Cooling System. Insight Remote Support automatically detects management modules as part of the device discovery process. The management module should be installed and running before attempting discovery. Important: Configuration collections are not supported.
Chapter 35: Configuring Modular Cooling Systems 3. Type the name of the management module in the System Name field. 4. Type the name of the contact person in the System Contact field. 5. Type the name of the location in the System Location field. 6. Type the Read community string. 7. Type the Write community string. 8. Type the Trap community string. 9. Click Save Settings to save the information. 10. In the Modular Cooling System web interface, set the Hosting Device as a trap receiver.
Chapter 35: Configuring Modular Cooling Systems Add Protocol Credentials and Start Discovery To discover your monitored devices, complete the following steps: Create an SNMP Protocol Credential in Insight RS If your device's SNMP community string is set to public and your community access mode is read only, Insight RS automatically associates an SNMPv1 protocol with your device.
Chapter 35: Configuring Modular Cooling Systems Send a Test Trap To send a test trap to the Hosting Device, complete the following steps: 1. Log on to the Modular Cooling System web interface. 2. Navigate to Setup → Management → Trap Receivers. 3. Click Send Test Trap to send a test SNMP trap to all enabled trap receivers. HP Insight Remote Support 7.0.
Chapter 36: Configuring VMware vCenter Servers Insight RS can collect virtual machine configuration information for your IT environment from your vCenter installation. Insight RS automatically discovers any VMware vCenter installations when the ProLiant Windows server it is installed on is discovered as long as the proper security credentials are configured. Insight RS supports collections for vCenter virtual machine guests, but does not support monitoring of the virtual machine guests.
Chapter 36: Configuring VMware vCenter Servers Credentials in the Insight RS Console" on the next page.) If any of the ESXi hosts are Gen8 ProLiant devices, then appropriate RIBCL credentials must also be provided prior to discovery. Important: The CIM ticket capability only applies to ESXi, not to ESX clusters. When Insight RS discovers the vCenter server, it will also discover ESX hosts, but you must enter the SNMP credentials in Insight RS before discovery for them to be monitored correctly.
Chapter 36: Configuring VMware vCenter Servers 4. Type the username and password you use to log on to vCenter. 5. Click Add. Discover the ProLiant vCenter Server To discover the ProLiant vCenter server, complete the following steps: 1. In a web browser, log on to the Insight RS Console. 2. In the main menu, select Discovery and click the Sources tab. 3. Expand the IP Addresses section and set up the IP address.
Chapter 36: Configuring VMware vCenter Servers 3. Make sure the Status column contains a success icon ( ). If there is no success icon, determine which column has the problem and consult the Online Help for troubleshooting information. HP Insight Remote Support 7.0.
Glossary collections The term within HP SIM for grouping system or event searches. While HP SIM uses the term collection in reference to a group of monitored devices, Insight Remote Support uses the term configuration collection in reference to data collected from a monitored device. This data is communicated to HP for proactive analysis. A Agentless Management Service (AMS) iLO 4 Agentless Management uses out-ofband communication for increased security and stability.
Glossary: Enterprise Virtual Array (EVA) - iLO Systems Insight Manager, the Hosting Device can act as a Central Management Server (CMS). E Enterprise Virtual Array (EVA) An EVA is a high performance, high capacity and high availability virtual RAID storage solution for high-end enterprise environments. Hosting Device Setup Wizard Step-by-step screens that helps users with the initial configuration of their Hosting Device.
Glossary: iLO Remote Insight Board Command Language (RIBCL) - P4000 CLI iLO Remote Insight Board Command Language (RIBCL) Communication protocol required for Insight Remote Support to communicate with ProLiant Gen8 servers. remote monitoring, diagnostics, and troubleshooting of devices. M management group Insight Online HP Insight Online provides one-stop personalized, secure access to support the devices in your IT environment.
Glossary: Remote Support Eligible Systems - System Management Homepage (SMH) SNMP trap R Remote Support Eligible Systems Systems that are eligible for Remote Support, and when enabled will submit events to the HP Data Center for incident resolution. Systems must also be entitled to Remote Support, otherwise submitted events will be closed. You can verify that an eligible system is actually supported by using the Remote Support Entitlement Check.
Glossary: Systems Insight Manager (SIM) - workflow case Systems Insight Manager (SIM) SIM is a unified server and storage management platform. From a single management console, administrators can manage their complete HP server and storage environment with a secure management tool set. V virtual node The P4000 Virtual SAN Appliance uses captive server disk drives to build a virtual iSCSI SAN consisting of Virtual Nodes that create the storage pool from which virtualized volumes are created.
Index M maintenance mode 42 A monitored devices prerequisites Active Health System Report 41 communication protocols and software components 21 C c-Class BladeSystem Enclosure configuring 141, 145 O Onboard Administrator configuring SNMP 145 Command View registering Remote Support 142 Enterprise Virtual Array 154 configuring Insight Remote Support 68 configuring SNMP ProLiant Citrix 70 ProLiant Linux 57 ProLiant VMware ESX 62 ProLiant Windows 45 P ProLiant Citrix Server 70 ProLiant Gen8 Server 36
