HPE SIM for NonStop Manageability

Transcription

1 HPE SIM for NonStop Manageability Part Number: R Published: January 2016 Edition: J06.03 and subsequent J-series RVUs, H06.03 and subsequent H-series RVUs, and G06.15 and subsequent G-series RVUs.

2 Copyright 2015, 2016 Hewlett Packard Enterprise Development LP The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise 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. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise website. Acknowledgments Intel, Itanium, Pentium, Intel Inside, and the Intel Inside logo are trademarks of Intel Corporation in the United States and other countries. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Java and Oracle are registered trademarks of Oracle and/or its affiliates. UNIX is a registered trademark of The Open Group. Motif, OSF/1, UNIX, X/Open, and the "X" device are registered trademarks, and IT DialTone and The Open Group are trademarks of The Open Group in the U.S. and other countries. Open Software Foundation, OSF, the OSF logo, OSF/1, OSF/Motif, and Motif are trademarks of the Open Software Foundation, Inc. OSF MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THE OSF MATERIAL PROVIDED HEREIN, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. OSF shall not be liable for errors contained herein or for incidental consequential damages in connection with the furnishing, performance, or use of this material. 1990, 1991, 1992, 1993 Open Software Foundation, Inc. The OSF documentation and the OSF software to which it relates are derived in part from materials supplied by the following: 1987, 1988, 1989 Carnegie-Mellon University. 1989, 1990, 1991 Digital Equipment Corporation. 1985, 1988, 1989, 1990 Encore Computer Corporation Free Software Foundation, Inc. 1987, 1988, 1989, 1990, 1991 Hewlett-Packard Company. 1985, 1987, 1988, 1989, 1990, 1991, 1992 International Business Machines Corporation. 1988, 1989 Massachusetts Institute of Technology. 1988, 1989, 1990 Mentat Inc Microsoft Corporation. 1987, 1988, 1989, 1990, 1991, 1992 SecureWare, Inc. 1990, 1991 Siemens Nixdorf Informationssysteme AG. 1986, 1989, 1996, 1997 Sun Microsystems, Inc. 1989, 1990, 1991 Transarc Corporation.OSF software and documentation are based in part on the Fourth Berkeley Software Distribution under license from The Regents of the University of California. OSF acknowledges the following individuals and institutions for their role in its development: Kenneth C.R.C. Arnold, Gregory S. Couch, Conrad C. Huang, Ed James, Symmetric Computer Systems, Robert Elz. 1980, 1981, 1982, 1983, 1985, 1986, 1987, 1988, 1989 Regents of the University of California.

3 Contents About This Document...4 Supported Release Version Updates (RVUs)...4 Intended Audience...4 New and Changed Information in R Edition...4 New and Changed Information in Edition...4 Related Information Introduction...6 Insight Remote Support Advanced...6 NonStop Software Essentials...6 NonStop I/O Essentials...7 NonStop Cluster Essentials...7 NonStop Cluster Performance Essentials...8 Insight Control Power Management Requirements...10 CMS Configuration Guidelines and Requirements...10 Windows CMS Requirements...14 Linux CMS Requirements...15 OSM Configuration Requirements Monitoring NonStop Systems in HPE SIM...16 NonStop-specific Features...16 Discovering a NonStop System...17 Viewing Tasks...20 Viewing your NonStop BladeSystems...22 Monitoring Events...24 Registering for WBEM Alerts and Lifecycle Events...25 Using the Tools and Links Tab...26 Getting or Text Notifications Monitoring the Power Regulator with HPE SIM...29 About Power Regulator...29 Enable Power Regulator...30 Alter Power Regulator Setting...31 Disable Power Regulator Monitoring a Virtual TapeServer (VTS) in HPE SIM Monitoring a Modular Storage Adapter (MSA) Attached to a VTS in HPE SIM Monitoring a NonStop System Console (NSC) in HPE SIM Monitoring a BackBox Virtual Tape Controller (VTC) in HPE SIM Support and other resources...48 Accessing Hewlett Packard Enterprise Support...48 Accessing updates...48 Websites...48 Customer self repair...49 Remote support...49 Documentation feedback...49 Contents 3

4 About This Document This document describes how to manage NonStop systems and system resources in HPE Systems Insight Manager (HPE SIM). Supported Release Version Updates (RVUs) This topic supports J06.03 and subsequent J-series RVUs, H06.03 and subsequent H-series RVUs, and G06.15 and subsequent G-series RVUs. Intended Audience This document is intended for customers or service providers who will install or use HPE SIM or SIM plug-in products to monitor or provide services for NonStop systems. New and Changed Information in R Edition Updated Hewlett Packard Enterprise references. New and Changed Information in Edition This version of the document contains updated information about important products that are no longer HPE SIM plug-ins and therefore do not require the presence of HPE SIM to install and use these products on NonStop system consoles (see Insight Remote Support Advanced (page 6) and NonStop Software Essentials (page 6)). This document is located at: Under NonStop Technical Library, select HP Integrity NonStop Service Information. Related Information Document HPE SIM documentation NonStop Software Essentials Installation and Quick Start Guide Location Select HP Systems Insight Manager (HPE SIM) Software. Select the desired Integrity NonStop Series collection: HPE Integrity NonStop, HP Integrity NonStop J-Series, or HP Integrity NonStop H-Series. NonStop Software Essentials User s Guide Select the desired Integrity NonStop Series collection: HP Integrity NonStop L-Series, HP Integrity NonStop J-Series, or HP Integrity NonStop H-Series. Insight Remote Support Advanced for NonStop HPE Insight Control Power Management User Guide NonStop I/O Essentials Installation and Quick Start Guide NonStop Cluster Essentials Installation and Quick Start Guide Select HP Integrity NonStop Service Information. Select the guide under Insight Control Function-Specific Guides. Select the desired Integrity NonStop Series collection: HP Integrity NonStop L-Series, HP Integrity NonStop J-Series, or HP Integrity NonStop H-Series. Select the desired Integrity NonStop Series collection: HP Integrity NonStop L-Series, HP Integrity NonStop J-Series, or HP Integrity NonStop H-Series. 4

5 Document Location NonStop System Console Installer Guide NonStop Cluster Performance Essentials User's Guide Select the desired Integrity NonStop Series collection: HP Integrity NonStop L-Series, HP Integrity NonStop J-Series, or HP Integrity NonStop H-Series. Select the desired Integrity NonStop Series collection: HP Integrity NonStop L-Series, HP Integrity NonStop J-Series, or HP Integrity NonStop H-Series. Related Information 5

6 1 Introduction HPE SIM is a centralized solution for managing Hewlett Packard Enterprise servers and storage. For NonStop, HPE SIM provides the ability to manage NonStop servers and components alongside other Hewlett Packard Enterprise servers and storage, from a single interface. It also works with various HPE SIM plug-in products and HPE NonStop Open System Management (OSM) software to provide both vital and additional, value-add services. Update: These products that provide vital services for NonStop systems are no longer HPE SIM plug-ins, so they no longer require HPE SIM to be installed. This makes it easier and more feasible to install and use these products on the NonStop system consoles or other supported PCs: HPE Insight Remote Support 7.x is the go-forward remote support solution for NonStop systems, replacing Insight Remote Support Advanced, which was an HPE SIM plug-in. References to using Insight Remote Support Advanced still apply for as long as that product continues to be supported. However, Insight Remote Support 7.x does not require HPE SIM, so HPE SIM considerations do not apply. For more information on installing and using Insight Remote Support 7.x in the NonStop environment, see Insight Remote Support 7.x for NonStop, located in the NonStop Service Information collection of the NonStop Technical Library. NonStop Software Essentials is the go-forward solution for upgrading and managing software on NonStop systems. With NonStop Software Essentials 5.0 and later, the NonStop Software Essentials Windows client is no longer an HPE SIM plug-in and does not require HPE SIM to be installed. References to using NonStop Software Essentials as a SIM plug-in apply only to pre-5.0 versions and only for as long as the required versions of HPE SIM are still supported. For information on installing NonStop Software Essentials versions that no longer require HPE SIM, see the NonStop Software Essentials Installation and Quick Start Guide. Other HPE SIM plug-in products that provide value-add services in the NonStop environment include: NonStop Cluster Essentials NonStop Cluster Performance Essentials NonStop I/O Essentials Insight Control Power Management Insight Remote Support Advanced Insight Remote Support Advanced was the remote support solution for NonStop systems that replaced the OSM Notification director in both modem-based and HPE Instant Support Enterprise Edition (ISEE) remote support solutions. Statements and examples in this document regarding its installation and use as an HPE SIM plug-in apply for as long as those products are supported. However, Insight Remote Support 7.x is the go-forward remote support solution for NonStop systems, replacing Insight Remote Support Advanced. Insight Remote Support 7.x does not require HPE SIM, making it easier and more feasible to install and use on NonStop system consoles or other supported PCs. For more information, see Insight Remote Support 7.x for NonStop, located in the NonStop Service Information collection of the NonStop Technical Library. NonStop Software Essentials NonStop Software Essentials is the go-forward solution for upgrading and managing software on NonStop systems. Statements and examples in this document regarding its installation and use as an HPE SIM plug-in apply to NonStop Software Essentials versions 4.0 and earlier, for as long as those products are supported. However With NonStop Software Essentials 5.0 and later, the NonStop Software Essentials Windows client does not require HPE SIM, making it easier and more feasible to install and use on NonStop system consoles or other supported PCs. 6 Introduction

7 For information on installing NonStop Software Essentials versions 5.0 and later, see the NonStop Software Essentials Installation and Quick Start Guide. NonStop I/O Essentials The NonStop I/O Essentials product is a plug-in for HPE SIM that provides support for all configuration and control tasks in the CIP (Cluster I/O Protocols) subsystem for NonStop systems with CLIMs. It provides a graphical user interface alternative to the command line interfaces of the CLIMCMD tool and SCF. It can perform actions on multiple CLIMs in different systems with a single action. Major benefits of using NonStop I/O Essentials are: Ability to perform all CIP management tasks without knowing the syntax of NonStop or Linux commands. Ability to perform CIP management tasks on multiple targets (for example CLIMs, disks, tapes, and so on) in parallel. Pre-created management tasks shipped out-of-box to configure and control all aspects of CIP. Secure and encrypted communication between the system console and NonStop systems. All data in motion between the console and the NonStop system is encrypted over SSH (Secure Shell) Remote management via a web browser. Can be used together with NonStop Cluster Essentials 2.0 or later to extend NonStop system management functionality. Supports volume level encryption. Supports Telco CLIMs and INS management on SS7 network. NonStop I/O Essentials can be used stand-alone or with NonStop Cluster Essentials. When used in conjunction with NonStop Cluster Essentials, all functionality of NonStop I/O Essentials can be deployed across a cluster of NonStop systems. For more information, see the NonStop I/O Essentials Installation and Quick Start Guide and the online help available from within the NonStop I/O Essentials interface. NonStop Cluster Essentials HPE NonStop Cluster Essentials is a plug-in for HPE SIM that acts as a central integration point for cluster management. It provides integrated cluster management for homogeneous clusters of NonStop systems or Linux systems and for heterogeneous clusters of NonStop systems and Linux systems. It supports clusters consisting of Integrity NonStop BladeSystems, NonStop NS-series systems, and NonStop S-series systems and optionally, Proliant systems running Linux. NonStop Cluster Essentials supports all clustering technologies, such as Expand, TCP/IP, or ServiceGuard. NonStop Cluster Essentials adds a new type of cluster to HPE SIM, the NonStop Cluster. As systems are discovered in HPE SIM over the network, the software automatically associates the systems with their defined clusters. The cluster is identified as a single managed entity in HPE SIM. NonStop Cluster Essentials accumulates health status from individual NonStop and Linux systems and provides an aggregated health status indicator for each NonStop cluster. NonStop Cluster Essentials includes an integrated event viewer that can be used in an integrated manner to look at EMS events from NonStop and evlog events from Linux. NonStop I/O Essentials 7

8 NonStop Cluster Essentials includes a single-click boot application to boot both from NonStop and Linux systems together in correct sequence or in parallel, as desired, thus orchestrating the NonStop and Linux system provisioning. NonStop Cluster Essentials provides virtualized configuration and control of the whole cluster, which obviates the need to learn NonStop or Linux-specific command syntax. NonStop Cluster Essentials can check software consistency across all NonStop systems in the cluster and across all Linux systems in the cluster. The Account Management Application of NonStop Cluster Essentials manages OS and maintenance accounts across the whole cluster by one click. NonStop Cluster Essentials provides an aggregated report of all hardware inventory across all NonStop and Linux systems in the cluster. For more information, see the NonStop Cluster Essentials Installation and Quick Start Guide and the online help available from within the NonStop Cluster Essentials interface. NonStop Cluster Performance Essentials HPE NonStop Cluster Performance Essentials is a plug-in to NonStop Cluster Essentials that provides integrated performance monitoring of homogeneous clusters of NonStop systems or heterogeneous clusters of NonStop and Linux systems. With it, you can monitor the performance of individual NonStop or Linux systems or clusters of them, using the HPE SIM and NonStop Cluster Essentials user interface. NonStop Cluster Performance Essentials provides these features: Performance monitoring of processor, disk, process, transaction, (Expand) line, SQL procedure, ServerNet, File Open and CLIM entities Alert notifications for defined and configured performance threshold values Security by encryption of all communications between NonStop Cluster Performance Essentials and the managed systems NonStop Cluster Performance Essentials provides the following functionality: Integrates with HPE SIM and NonStop Cluster Essentials Provides seamless HPE SIM user interface performance monitoring Supports NonStop systems and clusters Supports Linux systems and clusters Supports mixed NonStop and Linux clusters Provides integrated performance monitoring of NonStop and Linux clusters from a single user interface Provides integrated alert notification management of NonStop and Linux clusters from a single user interface For more information, see the NonStop Cluster Performance Essentials User's Guide. Insight Control Power Management Insight Control Power Management is a plug-in for HPE SIM that provides the ability to visualize the layout of servers and devices in racks and data center floors, summarizing temperature and power consumption. It provides the capability to monitor and manage power capacity and utilization for blades and c-class enclosures, and power delivery devices for data centers. It also enables you to monitor inlet air temperature and 24-hour peak temperature for blades and c-class enclosures. For Integrity NonStop BladeSystems, Insight Control Power Management provides both power and thermal monitoring. It can also provide alerts on potential errors, lack of redundancy and configuration anomalies. 8 Introduction

9 OSM has been enhanced to allow a NonStop system to be powered down gracefully from Insight Control Power Management. OSM also allows Insight Control Power Management to display CPU utilization data for NonStop systems as it does for other platforms. The Insight Control Power Management installer is included on the HPE Insight Control for NonStop DVD that ships with NonStop System Console Installer DVD, Update 17 (and later). For information on installing Insight Control Power Management, see the NonStop System Console Installer Guide. For information on using Insight Control Power Management, see the HPE Insight Control Power Management User Guide for the version you are using. Insight Control Power Management 9

10 2 Requirements Hewlett Packard Enterprise recommends that you install HPE SIM, Insight Remote Support Advanced, and NonStop Essentials products on a separate Central Management Server (CMS) rather than on the NonStop system consoles. However, if you have to, you can install them on NonStop system consoles as Hewlett Packard Enterprise supports this configuration as well. HPE SIM, Insight Control Power Management and NonStop Software Essentials are included on the Insight Control for NonStop DVD that ships with the NonStop System Console Installer DVD, Update 17 (and later). For information on installing those products on the system consoles, see the NonStop System Console Installer Guide. NOTE: If you plan to change the name of your NonStop system console or CMS, do so before installing HPE SIM. If you need to change the name after installing HPE SIM or HPE SIM plug-in products, you must follow these steps: 1. Uninstall any HPE SIM plug-in products. 2. Uninstall HPE SIM. 3. Change the system console or CMS name. 4. Re-install HPE SIM. 5. Re-install HPE SIM plug-in products. CMS Configuration Guidelines and Requirements You can install and use HPE SIM and SIM plug-in products on a Windows-based Central Management Server (CMS), NonStop system console (NSC) being used as a CMS, or Linux-based CMS, provided they meet the requirements described in this chapter. Your configuration options, where you can install and use HPE SIM and SIM plug-in products, will depend on the products or functionality to be used in your NonStop environment. Hewlett Packard Enterprise recommends installing HPE SIM and SIM plug-ins on a pair of CMSs (for fault-tolerance) that are not the NSCs. However, for products or functionality that require connectivity to the dedicated service LAN, it is necessary to install HPE SIM and at least certain SIM plug-ins on the NonStop system consoles instead of, or in addition to, the other CMSs. Those products or functionality are: Insight Control Power Management, as it requires access to ilos and OAs. HPE SIM functionality works on either NSCs or CMSs, with one exception: the physical layout of NonStop BladeSystems (display of the racks, enclosures, blades and switches), as this data is obtained via OA and ilo both of which are only available within the dedicated service LAN. Using the Cluster Boot Application, a component of NonStop Cluster Essentials, to load NonStop systems, as that functionality requires access to SPs/MEs. Some HPE SIM products require a Windows-based CMS (as opposed to Linux), as follows: Insight Remote Support Advanced The Cluster Boot Application, a component of the NonStop Cluster Essentials As for using a Linux-based CMS, all functionality of NonStop Software Essentials and NonStop I/O Essentials is supported on Linux (as well as Windows-based CMS), as is HPE SIM and NonStop Cluster Essentials functionality other than that noted above. If the functionality in one or more SIM plug-ins requires you to install HPE SIM and that plug-in on the NonStop system consoles, you still have the option of using additional CMSs to run other SIM plug-in products. 10 Requirements

11 NOTE: The following examples do not represent all possible options. Your needs might allow you to use HPE SIM and various plug-in products on Windows-based and/or Linux-based CMSs and not on the NSCs. Conversely, you might choose to run HPE SIM and plug-ins on the NSCs only, and not use any addition HPE SIM CMSs. Use the product requirements described earlier in this section to design a strategy for installing and using HPE SIM in your environment. CMS Configuration Guidelines and Requirements 11

12 12 Requirements Example 1 Using HPE SIM and SIM plug-ins only on Windows-based CMSs other than the NonStop system consoles

13 Example 2 Using HPE SIM and SIM plug-ins on Windows-based CMSs in addition to the NonStop system consoles CMS Configuration Guidelines and Requirements 13

14 Example 3 Using HPE SIM and SIM plug-ins on Linux-based CMSs in addition to the NonStop system consoles Windows CMS Requirements To install and use HPE SIM and SIM plug-in products, your Windows-based console whether a NonStop system console or other Windows-based CMS -- must be running Windows Server 2003 or Windows Server 2008, have at least 4 GB of memory, and meet the minimum requirements for the version of HPE SIM and all plug-in products that you plan to install and use on it. 14 Requirements

15 Linux CMS Requirements For HPE SIM plug-ins that support using a Linux-based CMS, HPE SIM and the plug-in's client component can be installed on any Linux CMS that meets these minimum requirements: Any HPE IA-32 or IA-64 AMD64 or EM64T system running one of the following Linux versions: Red Hat Enterprise Linux 5, Update 4 (32 bit) Red Hat Enterprise Linux 5, Update 5 (32 bit) Red Hat Enterprise Linux 6 (32 bit) Red Hat Enterprise Linux 4, Update 8 (64 bit) Red Hat Enterprise Linux 5, Update 4 (64 bit) Red Hat Enterprise Linux 5, Update 5 (64 bit) At least a 1.5-GHz processor and 4 GB RAM; 2.4-GHz processor and 8 GB RAM is recommended. Network connectivity to a secure operations LAN. Software: HPE SIM 6.3 or later. HPE SIM 6.3 can be installed from the HPE SIM DVD that shipped with NonStop System Console DVD, Update 15 and later. For Update 17, the DVD that ships along with the NSC DVD was retitled the Insight Control for NonStop DVD; it now contains the NonStop Software Essentials client component for both Windows and Linux in addition to HPE SIM. You can also download HPE SIM at: The Linux CMS (as with a Windows CMS) can be a physical server running Linux (or Windows) directly on the bare metal, or a virtual server running Linux (or Windows) on a VM with the hypervisor being VMWare ESX 3.5 (and later) or ESXi 4.1 (and later). OSM Configuration Requirements You must configure OSM on each NonStop system that will be monitored by HPE SIM. If not already present, for Integrity NonStop NS-series or HPE NonStop S-series systems, add the UseSSL=ON parameter in your OSMCONF configuration file. The OSMCONF file is located on a NonStop system at $SYSTEM.ZSERVICE.OSMCONF. For information on creating and using an OSMCONF file, see the OSM Configuration Guide. If the CMS used to discover and manage the NonStop system is outside of the dedicated maintenance LAN, you must specify stack parameter(s) for OSM in your OSMCONF file as follows: stack = <TCPIP process name> For example: stack = $ZTC00 stack = $ZTC01 After modifying the OSMCONF file, you must stop and restart the OSM processes in order for the change to take effect, as follows: scf abort process $zzkrn.#osm* scf start process $zzkrn.#osm* Linux CMS Requirements 15

16 3 Monitoring NonStop Systems in HPE SIM HPE SIM lets you monitor your NonStop systems as well as your system resources, such as your Virtual TapeServer (VTS), M8201R, maintenance switches, NonStop System Consoles (NSC), Modular Storage Adapter (MSA), ilo, and UPS. You can start OSM Service Connection and OSM Event Viewer from HPE SIM. You can also access NonStop Software Essentials, NonStop I/O Essentials, NonStop Cluster Essentials, NonStop Cluster Performance Essentials, and Insight Control Power Management. HPE SIM gives you the ability to setup and send either or text notifications to yourself when an issue arises on a specific system or server. This chapter discuss the steps and procedures to do those tasks. IMPORTANT: SSL must be enabled for HPE SIM or any of its plug-in to work. For NonStop J-Series systems, SSL is enabled by default. For NonStop H-Series and G-Series systems, you must manually enable SSL. NonStop-specific Features HPE SIM displays features that are available for NonStop systems and that are not related to any Essentials product. You can view these features from the All Systems main screen: The features displayed include: HS Health status. The HS column displays the overall system health status, which is determined by the default Hardware Status Polling task and is a roll up of all the status sources, which can be SNMP, WBEM, HTTP, and cluster status. SW PE The HS status reflects the OSM system status. The SW column, available for servers only, indicates both the availability of software updates and if they are critical. NonStop Performance Essentials status. The PE column is only present after NonStop Performance Essentials is installed. 16 Monitoring NonStop Systems in HPE SIM

17 ES System Name System Type System Address Product Name OS Name Aggregate Event status. The ES column is a summary of all uncleared events. This status is updated whenever an event is added, updated, or removed. To view all events for a system, including cleared events, click the ES status icon. This column contains the actual system name of all discovered systems. Systems appear as a single system or as a system in a container. When you place the cursor over the system name, the full system DNS name appears. This column displays the system type (for example, Server or Desktop). The system type Unmanaged indicates systems that have no management protocol that HPE SIM can detect (for example, no SNMP, WBEM, or SSH). The system type Unknown indicates systems that have some management protocol but have not matched any identification rule in HPE SIM. This column displays the primary IP address of the system that HPE SIM uses to communicate with the system. Not all systems have an IP address, including HPE Serviceguard clusters. This column displays the product name of the system. The OS Name column displays the system's operating system. From the All Systems screen, click on a particular system to view these features. In this example, we selected blosm4: Discovering a NonStop System In order to view and manage your NonStop system in HPE SIM, it must be discovered first. There are several system discovery options in HPE SIM and the methods vary slightly in some versions of HPE SIM. For NonStop systems, discovery involves establishing the necessary WBEM (Web-based Enterprise Management) communication between HPE SIM and OSM. A NonStop user needs to be added to the WBEM credentials in HPE SIM, either individually per system, by defining a Discovery-setup configuration, or through the Global Credentials setting. The Global Credentials option might be the easiest, if you are managing only NonStop systems from this Discovering a NonStop System 17

18 CMS, as HPE SIM will try all Global Credentials during discovery and will start using WBEM on the connection to the OSM automatically if the credentials match. NOTE: You do not need to use NonStop super group user credentials when establishing the communication necessary to discover NonStop systems in HPE SIM. You do, however, have to update HPE SIM when you change the password. To successfully discover a NonStop system, you must meet the following requirements: The OSM server must be running with SSL enabled, as specified in OSM Configuration Requirements. Discovery must be done via an IP address that is active on a NonStop system enabled on OSM as specified in OSM Configuration Requirements. You must have a valid Guardian username and password. When discovering a NonStop system with HPE SIM: Do not use SNMP to discover NonStop systems. You can use multiple IP addresses of the same system. Hewlett Packard Enterprise recommends this practice for fault-tolerance. To discover a NonStop system, follow these steps. In this example, we are discovering the NonStop system blosm4. 1. Make sure you meet the requirements listed above. 2. Sign-in to HPE SIM on the CMS using the appropriate credentials. The All Systems screen gives you a list of all the discovered systems. 3. To discover your NonStop system, from the Options menu, select Discovery Create a discovery task for your NonStop system as follows: a. From the Discovery screen, click New... and the New Discovery selections are displayed: 18 Monitoring NonStop Systems in HPE SIM

19 b. Select the Discover a single system radio button. c. The Automatically execute discovery check box is selected by default. You can deselect it or enter a time at which you want this task to run. d. Enter the task name for the discovery task. This can either be the system name or a name that describes what the task is meant to discover. If you have multiple tasks to discover a system via multiple TCP/IP stacks, the task name for example can be Systemname-$ZTCP0 or Systemname-$ZTC0. e. Enter the IP address or DNS name of a TCP/IP stack enabled for OSM. f. Click Credentials and enter a valid Guardian username or alias and password and click OK. g. Click Save. You now have created a new discovery task. h. Click Run Now. 5. Select All Systems to go back to the main screen. The NonStop blosm4 system now appears on the list. 6. If you have already created a discovery task (as described in Step 4), and you wish to rerun the task, from the Options menu, select Discovery... and select the desired system. In this example, we selected blosm4. Click Run Now. Discovering a NonStop System 19

20 7. If you want to edit a task, click Edit. In this example, we click Credentials to edit the Guardian username and password. Once done, click OK. Click Save to finish editing the discovery task. Viewing Tasks To view discovery task results associated with your system, from the Discovery screen, click View Task Results... To view a particular task, select the task ID. In this example, we selected task ID by clicking the link. 20 Monitoring NonStop Systems in HPE SIM

21 To check if your NonStop system was discovered successfully, from the Discovery page, click View Task Results. A numbered list of all discovery tasks that were run on the system is displayed. The default sort order displays the most recent task on top. Click on the desired task number. The Target Details for the selected task displays key information. In this example, we selected blosm4 and the information displayed (and highlighted for this example) indicates that the system has been discovered successfully via the required WBEM protocol: Viewing Tasks 21

22 Viewing your NonStop BladeSystems When you discover a NonStop BladeSystem using HPE SIM, all the blades that are associated with the NonStop system that you discovered are displayed. These are the Processor Blades. To view all the blades that were discovered with your NonStop system, go to the All Systems screen. In this example, we scroll down and find all the blades associated with blosm4. You can also see the blade servers associated with your NonStop system from your NonStop system's screen. From the NonStop system's screen, click on Associations to see the list of blade servers that were discovered for your system. In this example, we select the NonStop system blosm4 and click on Associations to view the associated blade servers. 22 Monitoring NonStop Systems in HPE SIM

23 When you run a discovery task for an Onboard Administrator (OA) of a NonStop system, much more system components are discovered such as racks and enclosures. If HPE SIM discovers OAs for a NonStop BladeSystem, the pictorial representation of the system is displayed when that rack or enclosure is selected. In this example, we selected the enclosure BLOSM4_100: Viewing your NonStop BladeSystems 23

24 Monitoring Events The Events tab shows three types of events for NonStop systems: OSM alerts Insight Remote Support Advanced-created events on behalf of the NonStop system (for example, a service event that was created) HPE SIM-created events for the selected NonStop system (for example, system discovery and lost connectivity) NOTE: The HPE SIM Events tab does not show EMS events from the NonStop system. Events are not cleared automatically by default. A large number of events retained can cause performance problems on the CMS. Refer to the HPE SIM documentation for methods on how to manage and delete events. Follow these steps to view your system's events. In this example, we view the events of blosm4. 1. To view your system's events, click on your system to go to your system's view page. From your system's view page, click on the Events tab. the events for your system will be displayed. For this example, we selected the blosm4 NonStop system, as shown below: Examples of HPE SIM created events are Rediscovery in progress and System is reachable. Examples of Insight Remote Support Advanced-created events are A Service Incident has been reported (Type 3) and A Service Incident has been reported (Type 4). All other event types in this example are OSM alerts. 2. To view an event's details, click on the desired event under the Event Type column. In this example, we selected the SNMP Test Trap Not Received OSM event and the details are shown below: 24 Monitoring NonStop Systems in HPE SIM

25 Registering for WBEM Alerts and Lifecycle Events Hewlett Packard Enterprise recommends that you register NonStop systems to receive both WBEM alerts and lifecycle events. Registering for WBEM alerts causes OSM alarms to be displayed in HPE SIM. Registering for WBEM lifecycle events (or health indications) causes OSM system status to be displayed within HPE SIM in real time. The icon displayed in the HS column of the All Systems page in HPE SIM will reflect the current status of the system, as reported by OSM. NOTE: You must register for WBEM alerts and lifecycle events once for each NonStop system when using Insight Remote Support Advanced and/or most Nonstop Essentials products it is done automatically for NonStop Cluster Essentials. Therefore, if you have already installed NonStop Cluster Essentials or performed these steps while configuring the system for one of those other products, you do not need to repeat them as part of Insight Remote Support Advanced. Registering for WBEM Alerts You can register a NonStop system to receive WBEM alerts in several ways. Two of these methods are as follows: 1. Discover your system as described in Discovering a NonStop System. 2. Click on the Options menu, select Events followed by Subscribe for WBEM events. or 1. In the First Time Wizard, under Configure Managed Systems, select Configure newly managed systems when they are first discovered. 2. From the Configure WBEM/WMI check list, select Create subscription for WBEM events. This option is useful if you are managing only NonStop systems from the CMS, as HPE SIM will try all Global Credential, or those specified in the discovery task for individual systems during discovery and will start using WBEM to receive alerts from OSM automatically, provided the credentials match. NOTE: If you have entered global credentials in Discovering a NonStop System, this step might already be done. Registering for WBEM Alerts and Lifecycle Events 25

26 Registering for WBEM Lifecycle Events You can register a NonStop system to receive WBEM lifecycle events as follows: 1. Discover your system as described in Discovering a NonStop System. 2. Enter the following command at a command prompt: mxwbemsub a n <system_name_address> -t health Where <system_name_address> is either the DNS name or the IP address of the NonStop system. 3. To verify if the system is currently registered for the WBEM lifecycle events, enter: mxwbemsub -l -n <system_name_address> Once you have registered for WBEM lifecycle events, the following occurs: OSM receives the indication subscription from HPE SIM along with a query for CIM_AlertIndication and the destination. OSM generates an event 1146 with the trace message Indication Subscription CREATING. The event detail contains the query and destination that destination being a URL containing 50004, the CMS port used by HPE SIM to receive alarms, in the format of WBEM events, from OSM, as follows: Trace Subject: "Indication Subscription CREATING " Trace Message:- "Subscription: CIM_IndicationSubscription.Filter=R"CIM_IndicationFilter.CreationClassName=\"" "CIM_IndicationFilter\",Name=\"HPSIM_TYPE_1_blosm4-nsc_0\",SystemCreationClassName=\"CIM_Com" "putersystem\",systemname=\"blosm3\"",handler=r"cim_indicationhandlerxmlhttp.creationclassna" "me=\"cim_indicationhandlerxmlhttp\",name=\"hpsim_type_1_blosm4-nsc\",systemcreationclassnam" "e=\"cim_computersystem\",systemname=\"blosm3\""filter: CIM_IndicationFilter.CreationClassNa" "me="cim_indicationfilter",name="hpsim_type_1_blosm4-nsc_0",systemcreationclassname="cim_com" "putersystem",systemname="blosm3",query="select * from CIM_AlertIndication",QueryLanguage="W" "QL""?10 "Handler: CIM_IndicationHandlerXMLHTTP.CreationClassName="CIM_IndicationHandlerXML" "HTTP",Name="HPSIM_TYPE_1_blosm4-nsc",SystemCreationClassName="CIM_ComputerSystem",SystemNam" "e="blosm3",destination=" Using the Tools and Links Tab The Tools and Links tab offers additional information for your NonStop systems: The System Web Application Pages offer OSM related information for your NonStop system. The links to OSM Service Connection and Event Viewer are context-sensitive. The NonStop Server Tools offer links to launch and manage NonStop Software Essentials and NonStop I/O Essentials. The NonStop Cluster Tools lets you invoke the Performance Essential monitor view and alerts for your NonStop cluster. This option is only available if the selected system belongs to a cluster. The HP Systems Insight Manager Pages lets you view or set various properties, settings, and tasks. The PE Tools lets you manage your Performance Essential configuration settings for your agents or your SIM. This option is only available if the selected system belongs to a cluster. 26 Monitoring NonStop Systems in HPE SIM

27 Getting or Text Notifications You can setup HPE SIM to send you either an or a text when an issue arises on a specific system or server, as follows: NOTE: Before adding an address, you must add an SMTP host in the first time wizard. 1. Select Send an and fill out the fields. You can also do this from the Options menu. Select Events -> Automatic Event Handling -> Settings... Enter the SMTP host and the Sender's address of your choice, for example: 2. From the Options menu, select Events -> Automatic Event Handling > New Task...: Getting or Text Notifications 27

28 3. Select a task name and click Next. 4. Select an event and click Next. In this example, we select All Events and click Next. 5. Select the use system attributes that I will specify radio button and click Next. Select the system that you will be monitoring from the drop down menu on the right that contains a list of all systems being managed on the CMS. Click Next. 6. Select Use time filter if desired and click Next. 7. Review your summary and click Finish to approve it. Once you have done the above steps, you can send test traps. 28 Monitoring NonStop Systems in HPE SIM

29 4 Monitoring the Power Regulator with HPE SIM You can set up or disable Power Regulator on NonStop BladeSystem NB54000c, NB54000c-cg, NB56000c, and NB56000c-cg to provide centralized control of server power consumption. First use the OSM Service Connection to enable Power Regulator as described in Enable Power Regulator, and then immediately use Insight Control Power Management to set the Power Regulator as described in Alter Power Regulator Setting. To disable Power Regulator, use the the OSM Service Connection as described in Disable Power Regulator. NOTE: You must have a NonStop BladeSystem NB54000c, NB54000c-cg, NB56000c, or NB56000c-cg. About Power Regulator The Power Regulator feature is available for NonStop BladeSystem NB54000c, and NB54000c-cg running RVU J06.14 or later and OSM server SPR T0682ACZ or later. The Power Regulator feature is available for NonStop BladeSystem NB56000c and NB56000c-cg running RVU J06.16 or later and OSM server SPR T0682ADF or later. The Power Regulator settings supported for NonStop BladeSystem NB54000c, NB54000c-cg, NB56000c, and NB56000c-cg are described below. See the HPE Insight Control Power Management User Guide for more information about Power Regulator. HPE Power Regulator Setting HPE Static High Performance Mode (default) HPE Dynamic Power Savings Mode Description In Static High Performance Mode, the CPU 1 runs at the maximum performance/power consumption that is supported by your NonStop configuration. This mode ensures maximum performance, but does not provide any power savings. This is the default mode for all systems, including shipped systems. In Dynamic Power Savings Mode, IPUs 2 run at maximum power/performance until an IPU idles. Once the IPU idles (and as long as it does not need to off-load work from other IPUs) it moves to the Itanium power saving state until a task needs to run on it, whereupon the IPU executes instructions at maximum power/performance again. HPE Static Low Power Mode In Static Low Power Mode, the CPU is set to a lower power state. This state saves power by having the CPU operate at a lower frequency, with resulting lower performance capacity. The performance impact is workload-dependent. 1 CPU is a Logical Processor that consists of a set of one or more IPUs. 2 IPU (Instruction Processing Unit) is a microprocessor core. NOTE: The OS Control Mode is not supported on NonStop systems. If OS Control Mode is selected, the command will fail, and the Power Regulator setting is left unchanged. The first time Power Regulator is enabled for a CPU, Dynamic Power Savings Mode becomes the default Power Regulator setting, unless a different Power Regulator setting is stored in the ilo flash memory. When a command is issued to alter the Power Regulator setting, ilo stores the new Power Regulator setting in ilo flash memory, and that new Power Regulator setting becomes the default. The OSM Service Connection provides the action Enable/Disable Blade Power Regulator Management on the System object to control the participation of a NonStop BladeSystem in Power Regulator. About Power Regulator 29

30 Two OSM Service Connection attributes under the System object relate to Power Regulator: Power Regulator Management Supported and Power Regulator Management Status. Power Regulator Management Supported has the value True on a NonStop BladeSystem NB54000c, NB54000c-cg, NB56000c, or NB56000c-cg running an RVU supporting power management. Otherwise, it is not reported. Power Regulator Management Status is only reported on NonStop BladeSystems if Power Regulator Management Supported is reported (the value of attribute Power Regulator Management Supported is True). The Power Regulator Management Status attribute in OSM shows one of these values: Unknown whenever Power Regulator Management Supported has the value True, but the OSM action Enable/Disable Blade Power Regulator Management has never been issued to enable or disable Power Regulator. Not Supported whenever the attribute Power Regulator Management Supported has the value False. Disabled whenever the OSM action Enable/Disable Blade Power Regulator Management has attempted to disable Power Management on all processor blades or if the RVU does not support Power Regulator. Enabled whenever the OSM action Enable/Disable Blade Power Regulator Management has successfully enabled Power Regulator on all processor blades. Use the OSM Service Connection action Enable/Disable Blade Power Regulator Management to enable/disable Power Regulator, as described in Enable Power Regulator or Disable Power Regulator. Super Group user authorization is required. Immediately after enabling Power Regulator, use Insight Control Power Management within HPE SIM to view and alter the Power Regulator setting for each processor blade in this NonStop BladeSystem. See Alter Power Regulator Setting. Either all blades in a NonStop BladeSystem should support Power Regulator if proper firmware is installed, or none should support Power Regulator. If Power Regulator is enabled, all blades must be set to the same Power Regulator setting. Enable Power Regulator This procedure immediately enables Power Regulator on every supported processor blade in the system when the NonStop operating system is running in that blade. Afterwards, the OSM server attempts to enable Power Regulator whenever a processor is reloaded. This OSM action should be used only at a time when potential processor performance degradation (for example, decreased instruction processing speed or increased latency) is permissible until the Power Regulator setting for each processor blade is set in Insight Control Power Management. See Alter Power Regulator Setting. Do the following to enable Power Regulator: 1. The OSM Service Connection displays action Enable/Disable Blade Power Regulator Management in the Available Actions pane of the Actions dialog for the System object in the OSM tree. Select Enable/Disable Blade Power Regulator Management. 2. A confirmation dialog is displayed. Click Perform Action. 3. The OSM Service Connection displays a confirmation dialog box. Read it and click OK. 4. The OSM Service Connection presents the Power Regulator Mode Management pull-down menu. Select Enable in the menu. This procedure changes the OSM attribute Power Regulator Management Status under the System object to Enabled. 30 Monitoring the Power Regulator with HPE SIM

31 NOTE: Immediately after enabling Power Regulator, use Insight Control Power Management to view and alter the Power Regulator setting for each processor blade in this NonStop BladeSystem. See Alter Power Regulator Setting. Alter Power Regulator Setting After Power Regulator is enabled as described in Enable Power Regulator, immediately use Insight Control Power Management to change the Power Regulator setting for this NonStop BladeSystem, as follows: 1. In the HPE SIM Options menu, select Power Management. 2. Enter the credentials for each blade ilo and OA in the section labeled Default Management Processor Access Credentials. 3. If the blades have not already been discovered, do the following: a. In the HPE SIM Options menu, select Discovery. b. Create and run a Discovery task to discover the OAs of the NonStop BladeSystem. This task may take a few minutes to complete the discovery. For more information, see the online help for the version of HPE SIM that you are using. 4. In the Systems and Event Collections tree on the left, select the NonStop BladeSystem. 5. Click the Power/Thermal tab: 6. Scroll down and expand the Power Management Actions node: Alter Power Regulator Setting 31

32 The HP Power Regulator Status displays the current power regulator setting. To change the power regulator setting, click Power Control. 7. Under Power Usage Controls, click the arrow to open the drop-down menu of HP Power Regulator Status and select the desired mode: 8. Click the Next button to see the current and new power settings. Click the Confirm Change button. 9. Power Usage Controls displays the Previous Power Regulator Setting, the Current Power Regulator Setting, and whether the change succeeded. 32 Monitoring the Power Regulator with HPE SIM

33 10. Wait 5 minutes and then use the OSM Service Connection to look for alarms on the System object. If Power Regulator settings on all blades in the NonStop BladeSystem do not match, an alarm is generated on the System object. If there is an alarm on the System object, click the System object, select the alarms tab and then right-click the alarm and select Detail to determine whether the alarm is due to a mismatch of Power Regulator settings. If there is a mismatch of Power Regulator settings, use the alarm repair actions to correct the mismatch. Disable Power Regulator To disable Power Regulator, do the following: 1. The OSM Service Connection displays action Enable/Disable Blade Power Regulator Management in the Available Actions pane of the Actions dialog for the System object in the OSM tree. Select Enable/Disable Blade Power Regulator Management. 2. A confirmation dialog is displayed. Click Perform Action. 3. The OSM Service Connection displays a confirmation dialog box. Read it and click OK. 4. The OSM Service Connection presents the Power Regulator Mode Management pull-down menu. Select Disable in the menu. This procedure changes the OSM attribute Power Regulator Management Status under the System object to Disabled. Disable Power Regulator 33

34 5 Monitoring a Virtual TapeServer (VTS) in HPE SIM You can monitor a VTS with HPE SIM. NOTE: You must have a VTS version 8.0 or later. You can only monitor the disks on a DL185G5 based VTS. To monitor a VTS with HPE SIM, follow these steps: 1. Using the DVD that is provided with your VTS, install the agents on your VTS as follows: a. Burn HPSIM.iso to a DVD or via HPE Integrated Lights-Out (ilo) and create a virtual image. On the VTS, enter the following command: [bill@gmcsc-vts ~]$ su - Password: [root@gmcsc-vts ~]# mkdir /media/cdrom [root@gmcsc-vts ~]# mount /dev/cdrom /media/cdrom mount: block device /dev/cdrom is write-protected, mounting read-only [root@gmcsc-vts ~]# /media/cdrom/installhptools.bash Stopping HP services Uninstalling previously installed HPE SIM RPMs... Installing/upgrading HPE SIM support RPMs... SIM support RPMs were successfully installed. Installing/upgrading HPE SIM... HPE SIM was successfully installed. Reboot system to complete installation. [root@gmcsc-vts ~]# umount /media/cdrom [root@gmcsc-vts ~]# eject [root@gmcsc-vts ~]# reboot b. Review the SIM-install-YYYYMMDD.log file for any errors or messages located in the /usr/local/tape/log/ log file. c. Ensure that all services are started: $ su - d. Enter the root password. e. Enter the following service commands: $ service hp-snmp-agents status $ service hpsmhd status $ service snmpd status $ service snmptrapd status NOTE: If any of these services are not running, replace status with start. 2. Discover your VTS in HPE SIM as a ProLiant providing valid credentials for the VTS using the discovery steps described in Discovering a NonStop System. 3. To determine what model of Proliant server VTS you are running, as root, enter: # dmidecode -t 1 # dmidecode 2.7 SMBIOS 2.5 present. Handle 0x0001, DMI type 1, 27 bytes. System Information Manufacturer: HP Product Name: ProLiant DL185 G5 Version: Serial Number: UUID: 805DAD17-D21D-B CC45F64BE Wake-up Type: Power Switch 34 Monitoring a Virtual TapeServer (VTS) in HPE SIM

35 SKU Number: Family: The Product Name lists the model type. IMPORTANT: If you are running a VTS DL185G5, go to step 4. Otherwise, go to step If you are running a VTS DL185G5, follows these steps: a. Remove hp-health and its subcomponents from the VTS: rpm e hp-health rpm e hp-smh-templates rpm e hp-snmp-agents b. Download HPASM at c. FTP to the VTS and install the rpm: rpm ivh hpasm rhel5.x86_64.rpm d. As root, enter hpasm activate and select the default choices by pressing enter: e. You will be asked to enter the localhost SNMP Read/Write community string as shown in the graphic below and outlined in the red box. That string has no default, enter private and enter private again to confirm. 35

36 f. Once the installation is complete, enter: # service snmpd restart 5. Setup or text notifications in one of two ways: Use HPE SIM to setup or text notifications when warnings or errors occur on the VTS, as described in Getting or Text Notifications. Use HPE System Management Homepage (SMH) and edit the SNMP configuration file to send trap notifications on the CMS where HPE SIM is installed, as follows: a. Login to HPE SMH as the root user: b. From the Settings page, select SNMP Webagent. c. Select SNMP Configuration. d. The SNMP Configuration page displays the SNMP configuration file. NOTE: If you make a change to the SNMP configuration file, you must restart the SNMP service. 36 Monitoring a Virtual TapeServer (VTS) in HPE SIM

37 Make your desired changes and click change: IMPORTANT: If your VTS is a DL185G5, on the SNMP Configuration page, make the following changes to the configuration file and click change: dlmod cmax /usr/lib64/libcmax64.so rwcommunity private rwcommunity private <ipaddressofcms> rocommunity public rocommunity public <ipaddressofcms> authtrapenable 1 com2sec all default public group MyRWGroup v1 all view all included.1 access MyRWGroup "" any noauth exact all all all trapcommunity public trapsink <ipaddressofcms> An example of an notification failure for a VTS is shown below: 37

38 38 Monitoring a Virtual TapeServer (VTS) in HPE SIM

39 6 Monitoring a Modular Storage Adapter (MSA) Attached to a VTS in HPE SIM You can monitor an MSA with HPE SIM. NOTE: You must have an MSA version To monitor an MSA with HPE SIM, follow these steps: 1. Discover your MSA system, providing valid credentials for the MSA, using the discovery steps described in Discovering a NonStop System. 2. On the MSA, login to the Storage Management Utility: 3. By default, the system overview is displayed. From the Configuration menu, select Services->SNMP Notification. 39

40 4. Enter the IP address of the CMS that you will use to monitor the MSA. You can have up to 3 trap destinations, Trap Host 1 Address, Trap Host 2 Address, and Trap Host 3 Address. Click Apply. Once you have setup your trap notifications, you will receive by alarms for the MSA that you added to the list of systems for which you want to be notified. Example: Notification sent to report warning with MSA Under the System(s) tab in HPE SIM, a warning with the msa-vts system is shown with a yellow triangle ICON: 40 Monitoring a Modular Storage Adapter (MSA) Attached to a VTS in HPE SIM

41 Once the yellow triangle icon is clicked for the msa-vts system, the Events tab for the MSA displays the problem descriptions. To view a problem description in detail, select the desired event type. In this example, we select the first event Warning storage event: Examples of notifications are as follows: 41

42 42 Monitoring a Modular Storage Adapter (MSA) Attached to a VTS in HPE SIM

43 7 Monitoring a NonStop System Console (NSC) in HPE SIM To monitor an NSC with HPE SIM, follow these steps: 1. From a separate CMS, discover your NSC system, providing valid credentials for the NSC using the discovery steps described in Discovering a NonStop System. 2. On the CMS, logon to HPE System Management Homepage (SMH). 3. In HPE SMH, from the Settings menu, select SNMP & Agent Settings: 4. From the SNMP & Agent Settings screen, click the Security side menu option: 5. Add the IP Address of the NSC and local host and click Apply. 6. Open HPE SMH on the NSC itself and click the Trap side menu option and add the IP Address of the CMS where HPE SIM is installed and click Apply. 43

44 You will receive the following notification if NSC goes unresponsive: 44 Monitoring a NonStop System Console (NSC) in HPE SIM

45 8 Monitoring a BackBox Virtual Tape Controller (VTC) in HPE SIM To monitor an HPE BackBox Virtual Tape Controller (VTC) with HPE SIM, follow these steps: 1. From a separate CMS, discover your Backbox VTC, providing valid credentials for the device using the discovery steps described in Discovering a NonStop System. 2. Configure notifications for the Backbox VTC as described in Getting or Text Notifications (page 27). 3. On the CMS, logon to HPE SIM and subscribe to WBEM events. From the Options menu, select Events->Subscribe to WBEM Events. 4. Since the Backbox VTC is a Windows operating system, select the appropriate OS and click View Contents. Select the Backbox system that you wish to monitor, click Apply. 5. Verify that the correct target system is selected, then click Next. 45

46 6. In the Task Confirmation page, click Run Now to run the task. 7. In the Task Results page, under Stdout, verify that the indication subscription was successfully created. 46 Monitoring a BackBox Virtual Tape Controller (VTC) in HPE SIM

47 You will receive an notification if the Backbox VTC goes unresponsive: 47