ehealth SPECTRUM Integration

Similar documents
ehealth SPECTRUM Integration

CA ehealth and CA SPECTRUM

ehealth Integration for HP OpenView User Guide

CA ehealth Integration for HP OpenView

CA Spectrum. Remote Operations Suite User Guide. Release 9.3

Concord OneClick for ehealth

Cisco Unified Serviceability

ehealth Administration Overview Guide

Online Help StruxureWare Data Center Expert

Using the Prime Performance Manager Web Interface

CA ehealth. Setting Up Service Availability 2.0. r6.1

CA Spectrum MPLS Transport Manager

New Features in ehealth Release 5.7

CA Spectrum. Cluster Manager Solution Guide. Release 9.4

SERVICE ASSURANCE MANAGEMENT SYSTEM (SAMS 2.0)

Using Integration Utility

ZENworks Service Desk 8.0 Using ZENworks with ZENworks Service Desk. November 2018

Getting Started with ehealth for Voice--Cisco CallManager

Advanced Application Reporting USER GUIDE

NMS300 Network Management System Application

Veeam ONE. Version 8.0. User Guide for VMware vsphere Environments

Configuring Communication Services

Configuring and Managing WAAS Legacy Print Services

Using vrealize Operations Tenant App as a Service Provider

CA NSM and CA SPECTRUM Integration Demo. Roger Craig

CA Spectrum. Policy Manager User Guide. Release 9.4

KYOCERA Net Admin User Guide

10ZiG Manager Cloud Setup Guide

Managing Cisco QoS Using ehealth

Checking System Status General Steps

Performance Monitor Administrative Options

Novell Access Manager

Getting Started with ESX Server 3i Installable Update 2 and later for ESX Server 3i version 3.5 Installable and VirtualCenter 2.5

CA Spectrum. Operator Guide. Release 9.2.3

Evaluation Guide for SNMPc v7.0

C.A. Unicenter Integration User s Manual

Getting Started Using Cisco License Manager

SPECTRUM. Control Panel User Guide (5029) r9.0.1

NNMI140 - Network Node Manager i Software 9.x for Operators

Distributed ehealth Concepts

Remote Operation Services

Integration with Network Management Systems. Network Management System (NMS) Integration

IMC VAN Fabric Manager v7.0 (E0201) Copyright (c) Hewlett-Packard Development Company, L.P. and its licensors.

BlackBerry Enterprise Server for Microsoft Office 365. Version: 1.0. Administration Guide

Getting Started with ehealth for Voice Cisco Unity & Unity Bridge

10 BEST PRACTICES TO STREAMLINE NETWORK MONITORING. By: Vinod Mohan

Network Performance Monitor

CA Unicenter NSM Agent

SNMP Agent Setup. Simple Network Management Protocol Support. SNMP Basics

Table of Contents HOL-PRT-1463

Citrix SCOM Management Pack for XenServer

EMC SourceOne Management Pack for Microsoft System Center Operations Manager

Avaya IQ 5.2 Service Pack 2 (SP2) Release Notes Issue 1.3 Dec

Oracle Enterprise Manager 11g Ops Center 2.5 Hands-on Lab

DEPLOYMENT GUIDE DEPLOYING F5 WITH ORACLE ACCESS MANAGER

SPECTRUM MPLS Transport Manager

Power IQ DCIM Monitoring Evaluation Copy A Step-By-Step Guide

Getting Started with ESX Server 3i Embedded ESX Server 3i version 3.5 Embedded and VirtualCenter 2.5

UDP Director Virtual Edition

CA ehealth CA Performance Center

Modeling Your IT Infrastructure

OneClick. Installation Guide. Document 5142

SPECTRUM. Multicast Manager User Guide (5132) r9.0

Microsoft Operations Manager

SPECTRUM. QoS Manager User Guide (5165) r9.1.1

Dell SupportAssist Version For Dell OpenManage Essentials Quick Start Guide

HP ProLiant Agentless Management Pack (v 3.2) for Microsoft System Center User Guide

This guide details the deployment and initial configuration necessary to maximize the value of JetAdvantage Insights.

OpenManage Integration for VMware vcenter Quick Installation Guide for vsphere Web Client Version 3.2

What s New in Release 9.2 Martin Adamčík

Leveraging CA ehealth Performance Manager Proactive Performance Alerting. Joel Kaufman & Kathy Hickey

OpenManage Integration for VMware vcenter Quick Install Guide for vsphere Client, Version 2.3

Transport Gateway Installation / Registration / Configuration

CELLTRAQ Battery Monitoring Software

UDP Director Virtual Edition Installation and Configuration Guide (for Stealthwatch System v6.9.0)

vrealize Operations Manager Customization and Administration Guide vrealize Operations Manager 6.4

Using ZENworks with Novell Service Desk

QUICK INSTALLATION GUIDE Minder 4.2

Fault Management. Overview of Polling and Thresholds CHAPTER

NeuralStar Installation Guide

Configuring an IMAP4 or POP3 Journal Account for Microsoft Exchange Server 2003

Best Practices for Using the ehealth Discover Process

Understanding the Relationship with Domain Managers

HPE Operations Agent. Concepts Guide. Software Version: For the Windows, HP-UX, Linux, Solaris, and AIX operating systems

Installing and Configuring Cisco Unified Real-Time Monitoring Tool

User Manual. (updated March 27, 2014) Information in this document is subject to change without notice.

EMC Voyence Integration Adaptor

OpenManage Integration for VMware vcenter Quick Install Guide for vsphere Client, Version 2.3.1

BROWSER-BASED SUPPORT CONSOLE USER S GUIDE. 31 January 2017

Data Protection Guide

User s Guide. Duralink Server Manager

About the SPECTRUM Control Panel

Navigating Cisco Prime Health and Utilization Monitor Tasks in LMS 4.1

IMPLEMENTING SINGLE SIGN-ON (SSO) TO KERBEROS CONSTRAINED DELEGATION AND HEADER-BASED APPS. VMware Identity Manager.

Legal Notes. Regarding Trademarks KYOCERA MITA Corporation

VPN Manager. User Guide. Document 5150

DefendX Software Control-Audit for Hitachi Installation Guide

SPECTRUM. VPN Manager User Guide (5150) r9.0

Dell SupportAssist Version 1.0 For Microsoft System Center Operations Manager User's Guide

Parallels Remote Application Server

Transcription:

User Guide March 2007 ehealth SPECTRUM Integration Whether you are a large enterprise or a service provider, your operations team faces a significant challenge maintaining critical service levels across complex network environments. ehealth SPECTRUM Integration helps address this challenge by combining the strength of ehealth s automated availability and performance management with the SPECTRUM network service and analysis platform, adding value to both industry-leading applications. SPECTRUM manages networks, pinpoints and corrects problems, and alerts you to changes in network or device status. The system creates a model of every entity in the network, including cables, network devices, servers, and applications. Since SPECTRUM also understands the relationship between network components, it provides a seamless view of the enterprise network. ehealth s historical data and automated reporting capabilities build on the SPECTRUM platform to automate the tasks of calculating long-term trends, baselining network resources, and providing performance reports for critical network components such as backbones, server clusters, and Internet links. ehealth s proactive troubleshooting and capacity planning features complete the picture, providing the full solution to manage your critical business services. The ehealth SPECTRUM integration gives you significant time and productivity benefits. The integration allows you to: Use ehealth to automatically discover devices managed by SPECTRUM, eliminating the need to manually re-enter and continually update configuration data. Access ehealth reports, such as At-a-Glance and Trend, directly from the SPECTRUM OneClick topology, giving you a quick overview of device status and in-depth historical information. Manage Live Exceptions alarms from the SPECTRUM OneClick console, viewing Alarm Detail reports and clearing alarms to reduce the mean-time-to-repair for network issues. Access ehealth reports from SPECTRUM alarms, giving you a historical context for more effective troubleshooting. Use ehealth for capacity planning, proactive troubleshooting, performance optimization, and service level management of your network components managed by SPECTRUM. These productivity benefits allow you to maximize the return on your network investments, plan future growth, and document service levels, ultimately ensuring the long-term success of your business. ehealth SPECTRUM Integration combines the best in fault and performance management into a complete solution, ensuring the high availability and responsiveness of your mission-critical business services. Overview of this Guide This document explains how to set up the ehealth SPECTRUM Integration. This document provides the following information: Getting Started Review the system requirements and prepare the Setup Checklist. Setting Up Configure both ehealth and SPECTRUM to support the Integration. Using SPECTRUM Use the integration features in the SPECTRUM OneClick Console. Using ehealth Use the integration features in ehealth. Setup Checklist Record information needed to complete the setup process.

GETTING STARTED Setup Time The setup process typically requires about 1.5 to 6 hours to set up the integration. 1 hour To verify requirements and complete the setup checklist(s) 10 min. To add a license 1/2 hour To run the setup program and configure alarms. 15 min. 5 hrs.to configure SPECTRUM Global Collections, run ehealth discovery, and map elements to models. The mapping time depends on the size of the environment, and could be longer in large environments. Verify System Requirements Before you run the ehealth SPECTRUM Integration setup program, verify that your ehealth and SPECTRUM systems meet the following requirements: ehealth System ehealth Release 6.0 or later. This release supports Solaris, Windows, and HP- UX platforms. SPECTRUM OneClick Server SPECTRUM Release 8.1 or later. This release supports Solaris, Windows, and Linux platforms. For information on installing ehealth software, refer to the ehealth Installation Guide for your platform. For information on installing SPECTRUM software, refer to the SPECTRUM Installation Guide. Understand Your Software Configuration There are three possible configurations for the ehealth SPECTRUM Integration: One ehealth system, one SPECTRUM server. One ehealth system, multiple SPECTRUM servers. Distributed ehealth, multiple SPECTRUM servers. Multiple standalone ehealth systems (not using Distributed ehealth) are not supported. Single ehealth System, Single (Separate) SPECTRUM Server. This configuration includes a SPECTRUM OneClick server and a SpectroSERVER, which can be separate systems. No special steps are required for this configuration. Single ehealth System, Multiple SPECTRUM Servers. You can configure ehealth to monitor multiple SPECTRUM servers, all of which can view ehealth reports. However, Live Health alarms can only be sent to one SPECTRUM server. When configuring Live Exceptions or Health reports to forward traps, specify a single SpectroSERVER as the SPECTRUM Trap Director to handle all traps. Distributed ehealth, Multiple SPECTRUM Servers. If you use Distributed ehealth, you can connect multiple ehealth systems with multiple SPECTRUM servers. When using Distributed ehealth: Configure each Distributed ehealth System to import information from a separate Global Collection on the SPECTRUM OneClick server. Configure each Distributed ehealth System to forward Live Exceptions traps to the single SPECTRUM Trap Director, as above. Configure Health reports on each ehealth system and the Distributed ehealth Console to forward traps to the single SPECTRUM Trap Director. Configure SPECTRUM to access reports on a single Distributed ehealth Console (front end). In this configuration the SPECTRUM OneClick server can view reports from any ehealth system. Complete the Setup Checklist For each SPECTRUM OneClick server you want to configure, copy and complete the Setup Checklist on the last page of this document. The checklist helps you to supply the information for the setup program. 2

SETTING UP Add a License ehealth Release 6.0 SP1 or later does not require a license to use the SPECTRUM integration. However, if you are using an earlier release of ehealth, and you have a SPECTRUM license key, you can enter the license using the ehealth Console interface. For detailed steps to enter license information, refer to the ehealth Web Help. Run the Setup Program The setup program prompts you for the information that you recorded on the ehealth SPECTRUM Integration Setup Checklist on page 11. To run the setup program: 1. Log in to the ehealth system as the ehealth administrator. 2. Open a terminal window and change to the ehealth directory by entering the following command, where ehealth is the full pathname: cd ehealth 3. Run the setup program by entering the following command: Windows: nhspectrumsetup UNIX:./bin/nhSpectrumSetup The SPECTRUM Import Setup dialog box opens. 4.Using the Setup Checklist that you prepared (page 11), enter the following information: Hostname or IP address of the SPECTRUM OneClick server. Port number for OneClick server Web requests. Path where OneClick is installed on the server. Username used to log in to the OneClick server. Password for the specified user name. 5.Click OK. ehealth verifies your settings and displays a message notifying you if they are valid. The validation process may take a few seconds. 6.Restart the ehealth Console. Configure the ehealth Alarm Notifier If you use Live Health, you can configure the Live Exceptions browser to forward Live Health alarm traps to a SpectroSERVER. To configure Live Exceptions to forward traps: 1.Launch the Live Exceptions browser. 2.Select Setup > Trap Destinations. The Trap Destinations Manager dialog box appears. 3.Click New. 4.Using the Setup Checklist, specify the following under Edit Trap Destination: Hostname of the SpectroSERVER. IP address of the SpectroSERVER. Port number for the SpectroSERVER. If you are using Secure Domain Manager, specify a port number of 4748. Figure 1. SPECTRUM Import Setup Dialog Box 5.Click Add. 6.Confirm that the name of the SpectroSERVER appears in the Existing Trap Destinations list, then click OK. 7.Select Setup > Notifier Rules. The Notifier Manager dialog box appears. 8.Click New. The Notifier Rule Editor dialog box appears. 9.In the Name field, enter SPECTRUM. 10.In the Action list, select Send Trap. 11.In the To NMS list, select the SpectroSERVER you specified in Step 4. 12.Under When an alarm is, select both Raised and Cleared. 3

13.Under Elements within, specify either a specific subject or All Subjects. 14.Click OK to save your Notifier rule. Configure Health Reports You can also configure individual Health reports to forward traps for Health exceptions to the SpectroSERVER. When the scheduled Health report runs, ehealth sends an SNMP trap to the SpectroSERVER for each element in the Exceptions section of the Health report. Only scheduled Health reports forward exceptions. If you run a Health report on-demand, it will not forward exceptions. To forward exceptions from Health reports: 1. Launch the ehealth Console. 2. Select Reports > Customize > Health Reports. 3. Select the report from which you want to forward Health exceptions. 4. In the Presentation Attributes drop-down list, select General. 5. Select NMS IP and Port Trap Address in the Attribute table. 6. In the Value field, specify the SpectroSERVER IP address and port number, separated by a colon. For example: 001.02.03.004:162 7. In the Presentation Attributes drop-down list, select Exceptions. 8. Select Send Exceptions SNMP Trap in the Attribute table. 9. Select Yes in the value field. 10.Click OK. Configure SPECTRUM to Recognize the ehealth Server and to Clear Alarms After completing the ehealth setup, you must also configure SPECTRUM to recognize the ehealth server. To enable SPECTRUM to access ehealth reports: 1. Log in to the SPECTRUM OneClick home page as a SPECTRUM Administrator. 2. Click Administration. The Administration Pages menu appears. 3. Select ehealth Configuration. The ehealth Configuration window appears. 4. Using the Setup Checklist that you prepared (page 11), enter the following information: ehealth Server Name The hostname or IP address of the ehealth server. ehealth Server Port The port number on which ehealth listens for Web requests. ehealth Admin Username The ehealth Web Administrator user name. ehealth Admin Password The ehealth Web Administrator password. ehealth Mapping Update Frequency The rate at which the integration updates the mappings between ehealth elements and SPECTRUM models. For more information, see Maintain Mappings on page 6. SSL access required If the ehealth server uses Secure Sockets Layer (SSL) for secure web communications, set this field to Yes. Use legacy report launching With SPECTRUM Release 8.1 and later, if you set this field to no, drill-down report options appear only for those models in SPECTRUM which are mapped to ehealth elements. If you select yes, drill-downs appear for all host, router, switch, and port models. If the model does not map to an element, an error message appears if you try to drill-down to an ehealth report for that model. To enable SPECTRUM to clear Live Health alarms, select Active in the Alarm Notifier for ehealth Status section. If you configure ehealth to forward alarms to SPECTRUM, and configure SPECTRUM to view ehealth alarms, the alarm notifier enables you to clear those alarms directly from the OneClick console. 5. Optionally, click Test to verify that the server name, port, user name, and password result in a successful connection to the ehealth server. 6. Click Save. 4

Configure SPECTRUM to View ehealth Alarms If you configured ehealth to forward Live Health alarms or Health exceptions to a SpectroSERVER, you must also configure SPECTRUM to receive the alarms. To enable SPECTRUM to view ehealth alarms: 1. Select Start Console at the top of the OneClick page to launch the OneClick Console. 2. Log in as a SPECTRUM administrator. 3. In the Explorer tab of the OneClick Navigation panel, select your SpectroSERVER, then select Universe. If you are monitoring multiple SpectroSERVERs, select Universe under the landscape for the Trap Director SpectroSERVER. 4. In the Contents panel, select the Topology tab. 5. In the Topology tab toolbar area, click the Create a new model by type icon. The Select Model Type dialog box appears. 6. Select the All Model Types tab. 7. Select EventAdmin, then click OK. The Create Model of Type dialog box appears. 8. Using the Setup Checklist that you prepared (page 11), enter the name and IP address of the ehealth server, then click OK. The ehealth server is added to the topology as an EventAdmin model. If you are monitoring multiple SpectroSERVERS, you must model the ehealth server in each landscape. Repeat steps 3 through 8 for each SpectroSERVER you are monitoring to create EventAdmin models. The remaining steps are only needed for the Trap Director SpectroSERVER. For more information on creating a model in OneClick, see the Modeling Your IT Infrastructure Administrator Guide. 9. Select the EventAdmin model in the OneClick Topology. 10.Right-click the EventAdmin model, then select Utilities > Attribute Editor. The Attribute Editor dialog box appears. 11.In the Attributes tree, select User Defined, then click add. The Attribute Selector dialog box appears. 12.In the Select Model Type window, select Other > EventAdmin. 13.In the Attributes for EventAdmin window, select map_traps_to_this_model_using_ IP_header, then click OK. The attribute is added to the User Defined list in the Attribute Editor. 14.Click the arrow that points to the right. The attribute is moved to the right window. 15.In the right window, select map_traps_to_this_ model_using_ IP_header, then select Yes. 16.In the Attributes tree, select add. The Attribute Selector dialog box appears. 17.In the Attributes for EventAdmin window, select SBG_AlertForwardingEnabled, then click OK. The attribute is added to the User Defined list in the Attribute Editor. 18.Click the arrow that points to the right. The attribute is moved to the right window. 19.In the right window, select SBG_AlertForwardingEnabled, then select Yes. 20.In the Attributes tree, select add. The Attribute Selector dialog box appears. 21.In the Attributes for EventAdmin window. select traps_per_sec_storm_threshold, then click OK. The attribute is added to the User Defined list in the Attribute Editor. 22.Click the arrow that points to the right. The attribute is moved to the right window. 23.In the right window, select traps_per_sec_storm_threshold, then set the value to the maximum number of traps ehealth sends per second, as specified in the Setup Checklist (page 11). 24.Click Apply. The attributes are applied to the model and the Attribute Edit Results dialog box appears. 25.Confirm your changes in the Attribute Edit Results window, then click Close. 26.Click OK in the Attribute Editor. Create SPECTRUM Global Collections Global Collections help you organize the network elements managed by SPECTRUM into logical groups in the SPECTRUM OneClick Topology. ehealth uses specified Global Collections as a starting point to discover network elements managed by SPECTRUM. Therefore, before running the ehealth 5

discover process, use Global Collections to specify which network elements you want ehealth to monitor. To create a Global Collection: 1. Log in to the SPECTRUM OneClick Console. 2. Create one or more Global Collections containing the devices you want to monitor with ehealth. If you are using Distributed ehealth, you must create a separate Global Collection for each Distributed ehealth System, so that different ehealth systems are not polling the same device. For more information on SPECTRUM Global Collections, refer to the Modeling Your IT Infrastructure Administrator Guide. Set Up ehealth Discovery The ehealth discover process reads the device information from the SPECTRUM collection To run the discover process: 1. On the ehealth Console, select Setup > Discover. The Discover dialog box opens. 2. In the Mode section, select the type of discover process that you want to run. 3. In the Discover Using section, select SPECTRUM Import. 4. In the Global Collection drop down menu, select the SPECTRUM Collection that you created in the previous section. 5. Click Discover. ehealth connects to the OneClick server and extracts the information from the SPECTRUM Collection, then discovers the appropriate elements. The Discovery Results are displayed in the Discovering dialog box. 6. When the discover process is complete, click Save. The results are saved to the Poller Configuration. 7. If you want to discover another SPECTRUM collection, repeat steps 4 through 6. Map ehealth and SPECTRUM Elements SPECTRUM/eHealth mapping matches ehealth elements such as routers and systems to corresponding models in SPECTRUM. By mapping a one-to-one relationship, SPECTRUM can provide ehealth reporting options for the model in OneClick. It also allows LAN/WAN alarms to appear on the appropriate port model in SPECTRUM (unmapped LAN/WAN elements put their alarms on the device model instead). The following mapping methods are available: Initial mapping enables you to map models and elements for the first time. You can also use initial mapping when you add a new Distributed ehealth System to a cluster. Incremental mapping allows you to update your existing mappings after you add new or remove elements from an ehealth system, or new models in SPECTRUM. Map by IP address maps a specific IP address on the specified ehealth system to the models in SPECTRUM. Update landscape overrides applies the changes that you have made to the mapping-overrides.xml file. For more information, see Override Mappings on page 7. An initial mapping process (and incremental if many element and model changes have occurred) may take a long time. This phase of the setup could take several hours to complete, depending upon the size of your environment. Create Initial Mapping. After you create your global collections and discover the models in ehealth, you typically run an initial mapping to map the SPECTRUM models and ehealth elements. To perform an initial SPECTRUM ehealth mapping: 1. Log in to the SPECTRUM OneClick home page. 2. Select Administration at the top of the page. The administration pages menu appears. 3. Select ehealth Configuration. The ehealth Configuration window appears. 4. Scroll down to the ehealth mapping utilities section. 5. Click Use ehealth Topology. OneClick loads the topology information for the ehealth system specified in the ehealth Configuration section. Maintain Mappings. SPECTRUM automatically maintains ehealth mapping through an incremental mapping process. This process ensures that new ehealth elements and SPECTRUM models are mapped on an ongoing basis. The frequency of incremental mapping is determined by the ehealth Mapping Update Frequency 6

field on the ehealth Configuration Window. By default, incremental mapping is run every 720 minutes (12 hours). You can run an incremental mapping after you complete an initial mapping. You can also manually run incremental mapping by clicking the Run Incremental Mapping button. Map by IP Address. You can map models and elements on a one-by-one basis to determine how or even whether the mapping can be resolved. To map by an IP address: 1.Log in to the SPECTRUM OneClick home page. 2.Select Administration at the top of the page. The administration pages menu appears. 3.Select ehealth Configuration. The ehealth Configuration window appears. 4.Scroll down to the ehealth mapping utilities section. 5.Click Use ehealth Topology. OneClick loads the topology information for the ehealth system specified in the ehealth Configuration section. Clear Mappings. After you map SPECTRUM models and ehealth mappings, you can clear the mappings. This allows you to remove any existing mappings and start again with either a new initial mapping session or manual mappings. To clear the SPECTRUM mappings: 1.Log in to the SPECTRUM OneClick home page. 2.Select Administration at the top of the page. The administration pages menu appears. 3.Select ehealth Configuration. The ehealth Configuration window appears. 4.Scroll down to the ehealth mapping utilities section. 5.Click Clear Map. Override Mappings. In SPECTRUM, you can control the mapping process with manual overrides. This may be useful for situations in which a mapping cannot be determined programmatically, or if you want to use a different mapping other than the default. For instance, if multiple ports on a device cannot be mapped because their values are not unique, but you know the correct mapping to use, you can manually specify those mappings in an XML file. Also, in large environments it is a best practice to use a different ehealth console for each SPECTRUM landscape. The current ehealth integration uses the same ehealth IP address for every mapping. You can use the overrides to point models on each landscape to a different ehealth console. To override SPECTRUM ehealth mappings: 1.Log in to the SPECTRUM server as the SPECTRUM administrator. 2.Open a command prompt window and change to the following directory: $SPECROOT/tomcat/webapps/spectrum/WEB- INF/ehlth/config 3.Copy the mapping-overrides.xml file to the $SPECROOT/custom/ehlth/config directory. 4.Change to the $SPECROOT/custom/ehlth/config directory. 5.Review the mapping-overrides.xml file for more information about types of overrides and examples of override settings. 6.Edit the mapping-overrides.xml file to add your override settings, then save the file. The next time that you map models to elements, the mapping process checks for and uses applicable overrides in the mapping-overrides.xml file. If you create landscape overrides in the mapping-overrides.xml file, you must update the landscape overrides using the ehealth Configuration window of the OneClick Web console. Click the Update Landscape Overrides button to update the OneClick server with the configured overrides. Any new OneClick clients will use the new settings; any open OneClick clients should be closed and reopened to update to the latest settings. Mapping overrides (element-to-model) are added only after any of the mapping activities are executed. Mappings are not updated with the landscape overrides. 7

USING SPECTRUM With ehealth SPECTRUM Integration, you can perform the following tasks directly from the SPECTRUM OneClick console: Generate ehealth At-a-Glance and Trend reports for elements in the OneClick Topology. Generate At-a-Glance and Trend reports for alarms. View Alarm Detail reports for Live Health alarms. Clear Live Health alarms. Running Reports from the OneClick Console In SPECTRUM Release 8.1, you can generate ehealth At-a-Glance and Trend reports from the OneClick console for any models that have been mapped to ehealth elements. If the SPECTRUM model is not mapped to an ehealth element, drill-down reports are not available from the Topology view. ehealth SPECTRUM Integration can restore this legacy report drill-down capability for unmapped elements using the Use legacy report launching if model is not mapped option on the OneClick ehealth Configuration window. Trend Reports. ehealth Trend reports display the performance of an element or a group of elements based on specific variables. You use these reports to identify the cause of unsatisfactory health ratings on specified elements. These reports display information for the previous 24 hours. To generate a Trend report: 1.Select the icon in your Topology that represents the interface, router, switch, or system for which you want to generate a report. 2.Right-click the icon, then select ehealth Trend Type Report, where Type is a resource such as System, Router, LAN/WAN, and so on. If you are using the legacy reporting option, the menu option is ehealth Trend Type Report (Legacy). 3.Select the Trend variable that you want to display. A new browser window opens. 4.Enter your ehealth Web user name and password. A status window appears displaying progress as the report generates. After several seconds, the report appears (Figure 3). Figure 2. OneClick Topology In previous releases, the integration feature allowed users to generate ehealth At-a-Glance and Trend reports for any router, switch, LAN/WAN interface, or system represented in the OneClick Topology (Figure 2); however, if there was no corresponding ehealth element, the drill-down displayed an error. You Figure 3. ehealth Trend Report 8

At-a-Glance Reports. ehealth At-a-Glance reports provide detailed information for all critical performance parameters through a series of charts. These charts show the trends for important variables such as the following: CPU utilization Buffer management Total throughput Disk faults Disk input and output To generate an At-a-Glance report: 1. Select the icon in your Topology that represents the interface, router, switch, or system for which you want to generate a report. 2. Right-click the icon, then select ehealth At-a- Glance Type Report, where Type is a resource such as System, Router, and so on. A browser window opens. If you are using the legacy reporting option, the menu option is ehealth At-a-Glance Type Report (Legacy). 3. Enter your ehealth Web user name and password. A status window appears displaying progress as the report generates. After several seconds, the report appears. Viewing ehealth Reports for Alarms When you see an alarm in the OneClick alarm list, you can generate ehealth At-a-Glance and Trend reports to view historical data about the element generating the alarm. To generate reports from the OneClick alarm list: 1. Right-click the appropriate row in the alarm list, then select one of the following: ehealth At-a-Glance Type Report ehealth Trend Type Report A new browser window opens. 2. Enter your ehealth Web user name and password. A status window appears displaying progress as the report generates. After several seconds, the report appears. Viewing Alarm Detail Reports When you see a Live Exceptions alarm in the OneClick alarm list, you can view an Alarm Detail report for the alarm, in addition to the At-a-Glance and Trend reports. The alarm detail report provides in-depth information about the alarm, including: Time The time the problem started, and the duration the alarm has been active. Elements The name of the element that has the alarm, its technology type, IP address, and the total number of traps it has generated. Alarm Type The condition that generated the alarm, and the severity level of the alarm. You can use this information to troubleshoot the cause of a problem. To view Alarm Detail reports: 1.Right-click the row in the alarm list, then select Alarm Detail Report (ehealth). A new browser window opens. 2.Enter your ehealth Web user name and password. A status window appears on the screen and displays the progress as the report generates. After several seconds, the Alarm Detail report appears in the browser. Clearing Live Health Alarms When the problem causing a Live Health alarm has been fixed, or you determine it is not a real problem, you can clear the alarm from the OneClick console. To clear an alarm from the OneClick console: 1.Right-click the appropriate row in the alarm list, then select Clear Alarm. The alarm is cleared in both SPECTRUM and the ehealth Live Exceptions Browser. 9

USING ehealth Running Reports from the ehealth Console From the ehealth console, you can run additional types of reports on all of your elements, including the elements that you monitor with SPECTRUM. Depending on which ehealth applications you use, you can run the following reports from ehealth: At-a-Glance Show key performance indicators for a specific element to aid in troubleshooting. Top N Show which elements are the highest or lowest performers for key indicators. Trend Show historical performance for multiple variables or multiple elements. Health Provide current and historical data to identify problems proactively, and plan resources. MyHealth Provide custom, multi-chart views of specific, user specified data. What-If Show the effect of changes in capacity and demand to help in capacity planning. Service Level Show and analyze service level information for a complete business unit. You can use the ehealth console or Web interface to generate reports for a specific time period. You can also schedule ehealth reports to run automatically at specified times. For more information about ehealth reports and how to run them, refer to the ehealth Web Help. Launching the OneClick Console You can launch the SPECTRUM OneClick console directly from ehealth to access SPECTRUM s fault management, root cause analysis, and other network management features. To launch the OneClick Console from ehealth: 1. Log in to ehealth Web console. 2. Select the Live Health tab. 3. Click Launch OneClick. The SPECTRUM OneClick console opens. 4. Log in to the OneClick console using your SPECTRUM user name and password. Clearing SPECTRUM Alarms You can clear SPECTRUM alarms from the Live Exceptions Browser in ehealth. To clear an alarm in a Live Exceptions Browser: 1.Select a row in the Event Table that represents an alarm that you want to clear. 2.Right-click the row, and select Clear Alarm. A message appears to confirm clearing the alarm. 3.Click Yes. The alarm is cleared in both the Live Exceptions Browser and in SPECTRUM. Scheduling the Discover Process You can schedule the discover process to run periodically on specific days and times. Scheduling periodic discovery ensures that ehealth has the latest configuration data from SPECTRUM. ehealth can also email you a log that lists any changes. To schedule the discover process: 1.From the ehealth Console, select Setup > Schedule Jobs. The Schedule Jobs dialog box opens. 2.Select Add Discover. The Add Scheduled Discover dialog box opens. 3.In the Mode section, select the type of discover process that you want to run. 4.In the Discover Using section, select SPECTRUM Import. 5.In the Global Collection drop down menu, select the SPECTRUM Collection you created in Create SPECTRUM Global Collections on page 5. 6.Optionally, in the Notify User field under options, specify the email address of the users to whom you want to send the log file. 7.Under Schedule, specify the days and time that you want the discover process to run. 8.Click Schedule. The Add Scheduled Discover dialog box closes. 9.Click OK in the Schedule Jobs dialog box. 10.To schedule additional discover processes for other SPECTRUM collections, repeat the procedure. 10

ehealth SPECTRUM Integration Setup Checklist The following checklists describe the information you need to enter when setting up the ehealth SPECTRUM Integration. Complete the checklist for each ehealth system you want to configure, before you start the setup process. SPECTRUM OneClick Server Information The Hostname or IP Address of the SPECTRUM OneClick server. The Port Number on which OneClick listens for Web requests. Default Value: 80 The Path where OneClick is installed on the server. Default Value: spectrum Note: Use the default value unless you specified another path when installing OneClick. User name and Password for accessing this host. User name: Password: SpectroSERVER Information The Hostname of the SpectroSERVER that is configured to receive traps from ehealth. The IP address of the SpectroSERVER that is configured to receive traps from ehealth. The Port Number on which the SpectroSERVER receives traps. Default Value: 162 Note: If you are running Secure Domain Manager (SDM) or the SNMPv3 Proxy, the port number is defined by the brass_trap_port variable in the file SPECTRUM/SS/.vnmrc. The default value for the brass_trap_port variable is 4748. ehealth Server Information The Hostname or IP Address of the ehealth server. The Port Number on which ehealth listens for Web requests. Default Value: 80 Username and Password for ehealth Web Administrator access. Note: If you use Distributed ehealth, the user must be valid on all ehealth systems. Username: Password: The maximum number of traps ehealth Live Exceptions sends per second. This value is defined by the NH_TRAPS_PER_SECOND environment variable. Default Value: 100 Copyright 2007 CA. All rights reserved. 11