Transcript
EMC® ITOI Enablement Pack For Nortel Version 8.1
User Guide P/N 300-013-796 A01
Copyright © 2007 - 2012 EMC Corporation. All rights reserved. Published in the USA. Published May, 2012 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners. For the most up-to-date regulatory document for your product line, go to the technical documentation and advisories section on the EMC online support website.
2
EMC ITOI VoIP Enablement Pack for Nortel Version 8.1 User Guide
CONTENTS
Preface Chapter 1
Introduction EMC ITOI Enablement Pack for Nortel........................................................... Nortel CS1000 requirements ................................................................. VoIP Availability Manager and other EMC ITOI products ............................... VoIP Performance Manager and client tools................................................. Processing flow........................................................................................... Discovery and monitoring............................................................................ Requirements for discovery ................................................................... Trap processing........................................................................................... Installation .................................................................................................
Chapter 2
Integrating the Enablement Pack with VoIP Specifying device-access login credentials for Nortel CLI discovery.............. Creating credentials with login environment variables........................... Nortel Signaling Server node IP addresses .................................................. Excluding Nortel node IP addresses from the topology ................................ Procedure to exclude a Nortel node IP address ...................................... CLI log file during discovery.........................................................................
Chapter 3
12 12 13 14 15 16 16 17 18
20 20 22 22 22 23
Discovering Elements and Monitoring Events Discovering Nortel CS1000 elements .......................................................... Discovery considerations for Nortel devices .......................................... Nortel Enablement Pack object classes ....................................................... Nortel Enablement Pack attributes .............................................................. Card ...................................................................................................... CallManager.......................................................................................... CallManagerRedundancyGroup ............................................................. IPPhone ................................................................................................ IPPhoneGroup ....................................................................................... GatewayService..................................................................................... MediaService ........................................................................................ SignalingService ................................................................................... SignalingRedundanyGroup.................................................................... VoiceMailApplication ............................................................................ VoipApplication .................................................................................... VoipCluster ........................................................................................... VoipProcess .......................................................................................... Events for VoIP Availability Manager Nortel elements .................................. Impact Analysis........................................................................................... Aggregates Analysis ....................................................................................
EMC ITOI VoIP Enablement Pack for Nortel Version 8.1 User Guide
26 26 27 28 28 28 28 29 29 30 30 31 31 32 32 33 33 34 36 38
3
Contents
Appendix A
Understanding the sm_edit Utility sm_edit ...................................................................................................... 40 sm_edit example ........................................................................................ 40
Appendix B
Default Notification Attributes Default notification attributes ..................................................................... 42
Appendix C
Wildcard Patterns Types of wildcard patterns........................................................................... 46
Index
4
EMC ITOI VoIP Enablement Pack for Nortel Version 8.1 User Guide
TABLES Title 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Page
Device-access login environment variables for Nortel CLI discovery ............................. Enablement Pack for Nortel CS1000 element classes .................................................. Key attributes for Card................................................................................................. Key attributes for the CallManager class...................................................................... Key attributes for the CallManagerRedundancyGroup class ......................................... Key attributes for the IPPhone class ............................................................................ Key attributes for the IPPhoneGroup class ................................................................... Key attributes for the GatewayService class................................................................. Key attributes for the MediaService class .................................................................... Key attributes for the SignalingService class ............................................................... Key attributes for the SignalingRedundancyGroup class .............................................. Key attributes for the VoiceMailApplication class ........................................................ Key attributes for VoipApplication ............................................................................... Key attributes for the VoipCluster class ....................................................................... Key attributes for the VoipProcess ............................................................................... Events reported by VoIP Availability Manager for Nortel EP .......................................... Down root-cause problems and impacts...................................................................... ServiceExeption root-cause problems and impacts...................................................... Aggregates.................................................................................................................. Default notification attributes...................................................................................... Basic wildcard patterns............................................................................................... Compound wildcard patterns ......................................................................................
EMC ITOI VoIP Enablement Pack for Nortel Version 8.1 User Guide
21 27 28 28 28 29 29 30 30 31 31 32 32 33 33 34 36 37 38 42 46 47
5
Tableses
6
EMC ITOI VoIP Enablement Pack for Nortel Version 8.1 User Guide
PREFACE
As part of an effort to improve its product lines, EMC periodically releases revisions of its software and hardware. Therefore, some functions described in this document might not be supported by all versions of the software or hardware currently in use. The product release notes provide the most up-to-date information on product features. Contact your EMC representative if a product does not function properly or does not function as described in this document. Note: This document was accurate at publication time. New versions of this document might be released on the EMC online support website. Check the EMC online support website to ensure that you are using the latest version of this document.
Purpose This document describes how to use EMC® IT Operations Intelligence (ITOI) VoIP Availability Manager to manage and monitor Nortel Communication Server 1000 Voice over IP (VoIP) environments. It presents procedures for initiating and customizing the VoIP Availability Manager discovery process.
Audience This document is part of the EMC ITOI VoIP Management Suite documentation set. It is intended for IT managers who are seeking to understand the VoIP discovery process that is performed by EMC ITOI VoIP Availability Manager, and for system administrators who are responsible for the administration, configuration, or use of VoIP Availability Manager. The assumption is that VoIP Availability Manager has been configured in accordance to the EMC ITOI VoIP Availability Manager Configuration Guide and, if VoIP Performance Manager is integrated with VoIP Availability Manager, in accordance to the EMC ITOI VoIP Management Suite Overview and Integration Guide.
EMC ITOI VoIP Management Suite installation directory In this document, the term BASEDIR represents the location where EMC IT Operations Intelligence (ITOI) software is installed: ◆
For UNIX, this location is /opt/InCharge/
.
◆
For Windows, this location is C:\InCharge\.
On UNIX operating systems, VoIP Management Suite is, by default, installed to /opt/InCharge/VoIP/smarts. On Windows operating systems, this product is, by default, installed to C:\InCharge\VoIP\smarts. This location is referred to as BASEDIR/smarts. Optionally, you can specify the root of BASEDIR to be something different, but you cannot change the location under the root directory. The EMC ITOI System Administration Guide provides detailed information about the directory structure for EMC ITOI software.
EMC ITOI Enablement Pack for Nortel Version 8.1 User Guide
7
Preface
EMC ITOI VoIP Management Suite products The EMC ITOI VoIP Management Suite includes the following products: ◆
EMC ITOI VoIP Availability Manager
◆
EMC ITOI Enablement Pack for Avaya
◆
EMC ITOI Enablement Pack for Cisco
◆
EMC ITOI Enablement Pack for Nortel
◆
EMC Ionix Enablement Pack for ACME
◆
EMC ITOI VoIP Integration Pack for VoIP Performance Manager
◆
EMC ITOI VoIP Performance Manager
◆
EMC ITOI VoIP Performance Reporter
Related documentation In addition to this document, EMC Corporation provides a Help system for command line programs as well as product documentation.
Help for command line programs Descriptions of command line programs are available as HTML pages. The index.html file, which provides an index to the various commands, is located in the BASEDIR/smarts/doc/html/usage directory.
EMC ITOI documentation Readers of this guide may find the following related documentation helpful. These documents are updated periodically. Electronic versions of the updated manuals are available on the EMC online support website: ◆
EMC ITOI System Administration Guide
◆
EMC ITOI ICIM Reference
◆
EMC ITOI ASL Reference Guide
◆
EMC ITOI Perl Reference Guide
◆
EMC ITOI MODEL Reference Guide
EMC ITOI VoIP Management Suite documentation The following documents are relevant to users of the EMC ITOI VoIP Management Suite:
8
◆
EMC ITOI VoIP Management Suite Release Notes
◆
EMC ITOI VoIP Availability Manager Installation Guide
◆
EMC ITOI VoIP Availability Manager Third-Party Copyright Read Me
◆
EMC ITOI VoIP Management Suite Overview and Integration Guide
◆
EMC ITOI VoIP Availability Manager Configuration Guide
◆
EMC ITOI VoIP Availability Manager Discovery Guide
◆
EMC ITOI VoIP Availability Manager User Guide
EMC ITOI Enablement Pack for Nortel Version 8.1 User Guide
Preface
◆
EMC ITOI Enablement Pack for Avaya User Guide
◆
EMC ITOI Enablement Pack for Cisco User Guide
◆
EMC ITOI Enablement Pack for Nortel User Guide
◆
EMC ITOI VoIP Management Suite Certification Framework Technical Notes
◆
EMC ITOI VoIP Availability Manager Certification Matrix
◆
EMC ITOI VoIP Availability Manager Documentation Portfolio
◆
EMC ITOI VoIP Performance Manager and Performance Reporter Documentation Portfolio
Conventions used in this document EMC uses the following conventions for special notices:
NOTICE is used to address practices not related to personal injury. Note: A note presents information that is important, but not hazard-related. IMPORTANT An important notice contains information essential to software or hardware operation.
Typographical conventions EMC uses the following type style conventions in this document: Normal
Used in running (nonprocedural) text for: • Names of interface elements, such as names of windows, dialog boxes, buttons, fields, and menus • Names of resources, attributes, pools, Boolean expressions, buttons, DQL statements, keywords, clauses, environment variables, functions, and utilities • URLs, pathnames, filenames, directory names, computer names, links, groups, service keys, file systems, and notifications
Bold
Used in running (nonprocedural) text for names of commands, daemons, options, programs, processes, services, applications, utilities, kernels, notifications, system calls, and man pages Used in procedures for: • Names of interface elements, such as names of windows, dialog boxes, buttons, fields, and menus • What the user specifically selects, clicks, presses, or types
Italic
Used in all text (including procedures) for: • Full titles of publications referenced in text • Emphasis, for example, a new term • Variables
EMC ITOI Enablement Pack for Nortel Version 8.1 User Guide
9
Preface
Courier
Used for: • System output, such as an error message or script • URLs, complete paths, filenames, prompts, and syntax when shown outside of running text
Courier bold
Used for specific user input, such as commands
Courier italic
Used in procedures for: • Variables on the command line • User input variables
<>
Angle brackets enclose parameter or variable values supplied by the user
[]
Square brackets enclose optional values
|
Vertical bar indicates alternate selections — the bar means “or”
{}
Braces enclose content that the user must specify, such as x or y or z
...
Ellipses indicate nonessential information omitted from the example
Where to get help EMC support, product, and licensing information can be obtained as follows: Product information — For documentation, release notes, software updates, or information about EMC products, licensing, and service, go to the EMC online support website (registration required) at: http://Powerlink.EMC.com
Technical support — For technical support, go to EMC online support and select Support. On the Support page, you will see several options, including one to create a service request. Note that to open a service request, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account.
Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Send your opinions of this document to: [email protected]
10
EMC ITOI Enablement Pack for Nortel Version 8.1 User Guide
CHAPTER 1 Introduction This chapter contains the following information: ◆ ◆ ◆ ◆ ◆ ◆ ◆
EMC ITOI Enablement Pack for Nortel....................................................................... VoIP Availability Manager and other EMC ITOI products ........................................... VoIP Performance Manager and client tools ............................................................. Processing flow....................................................................................................... Discovery and monitoring........................................................................................ Trap processing....................................................................................................... Installation .............................................................................................................
Introduction
12 13 14 15 16 17 18
11
Introduction
EMC ITOI Enablement Pack for Nortel The EMC® ITOI Enablement Pack for Nortel is a software package that discovers and monitors Nortel IP-enabled call signaling and call processing elements in a Nortel Communication Server 1000 (CS1000) Voice over IP (VoIP) environment. The Nortel Enablement Pack is part of the VoIP Management Suite, and operates in conjunction with VoIP Availability Manager to diagnose problems and monitor the Nortel CS1000 VoIP environment. The Nortel Enablement Pack includes the following functionality: ◆
Automated discovery of the elements in a Nortel Communication Server 1000 environment using SNMP and Command Line Interface (CLI) polling.
◆
Monitoring of CS1000 discovered components.
◆
Root-cause analysis for problems in VoIP cards and CallPilot software services.
◆
Call Server redundancy group analysis.
◆
Impact analysis within the VoIP domain and impact propagation to VoIP services.
◆
Cross-domain correlation with IP connectivity problems.
◆
Mapping of nonsymptomatic alarms to notifications that are passed up to the Global Console.
The Nortel Enablement Pack discovers and monitors the following devices and services in the Nortel VoIP environment: ◆
Nortel Call Server 1000 Models E, M, and S R4.0, R4.5, and R5.0
◆
Nortel Media Gateway Models E and M R4.0, R4.5, and R5.0
◆
Nortel Signaling Server Models E and M R4.0, R4.5, and R5.0
◆
Nortel Survivable Remote Gateway (SRG) 50, 200, 400 R2.0 and R4.0
◆
Business Communications Manager (BCM) 50, 200, 400 R2.0 and R4.0
◆
Nortel Call Pilot R4.0 and R5.0
◆
Symposium R5.0 and Contact Center R6.0
◆
MCS 5100 R5.0
◆
Telephony Manager
◆
ELAN and TLAN Connections
◆
Nortel IP phones
Nortel CS1000 requirements Nortel requirements, specifically the Nortel Inventory Reporting feature and multiple user setup, as well as vendor version requirements are provided in the EMC ITOI VoIP Management Suite Release Notes. You must ensure that these requirements are satisfied for proper operation with the EMC ITOI Enablement Pack for Nortel.
12
EMC ITOI VoIP Enablement Pack for Nortel Version 8.1 User Guide
Introduction
VoIP Availability Manager and other EMC ITOI products The Nortel Enablement Pack is part of the VoIP Management Suite and operates in conjunction with VoIP Availability Manager. During the installation of the VoIP Management Suite, you need to select the Nortel Enablement Pack for installation if you want to manage Nortel CS1000 VoIP environments. (The EMC ITOI VoIP Availability Manager Installation Guide provides complete information about the installation process.) EMC ITOI VoIP Availability Manager provides discovery and monitoring of the VoIP environment. Discovery and monitoring is performed over a combination of infrastructure and applications. The infrastructure includes: Call Servers, Signaling Servers, Media Gateways, Call Pilots, IP PBXs, IP phones, VoIP switches and routers. The applications include the VoIP network and telephony applications and software services. The relationships between these elements are represented by the VoIP topology. VoIP Availability Manager requires following EMC ITOI software: ◆
EMC ITOI Service Assurance Manager Consolidates the topology and events from underlying Domain Managers. The VoIP Availability Manager also operates in conjunction with the software that is installed with Service Assurance Manager: Adapter Platform and SNMP Trap Adapter.
◆
IP Availability Manager and, optionally, IP Performance Manager Provides topology information about the infrastructure elements and Unitary Computer Systems, as well as event information about whether the Unitary Computer Systems are reachable.
The EMC ITOI VoIP Management Suite Release Notes provides information on interoperability with other EMC ITOI products.
VoIP Availability Manager and other EMC ITOI products
13
Introduction
VoIP Performance Manager and client tools Client tools enable Global Console operators to invoke programs on a particular target object, such as a topology object, or a map object. Right-clicking a target object launches a pop-up menu that lists the available tools for the target object. Client tools created to access VoIP Performance Manager data are available only for VoIP topology objects which are imported by the Global Manager from VoIP Availability Manager. They enable Global Console operators to use the Java-based GUI available from the VoIP Performance Manager to access drill-down displays. The client tools that are available for use are dependent on the configuration of the VoIP Availability Manager and VoIP Performance Manager implementation, as well as the managed elements on the network. For example, these client tools may be available for the following VoIP Availability Manager topology objects: ◆
VoIP Performance Manager—Launch VoIP PM View
◆
SignalingService— • Launch PBX View • Launch Server Details View
◆
Gateway Service (running on the VGMC card)—Launch Gateway Details View
◆
Gateway Service—Launch Media Card Details View Note: The Media Card Details View appears for a gateway service representing the VGMC card. It does not appear for a gateway service that is running on a media gateway controller (MGC) or signaling server.
To access the tools, open the Service Assurance Manager Topology Browser Console, select a VoIP Availability Manager object from the topology, and right click the object. Select Client Tools from the drop-down list. The list of client tools displayed are context based to the selected object. Click on one of the tools to launch it. The EMC ITOI VoIP Availability Manager Configuration Guide provides configuration information for VoIP client tools. The EMC ITOI VoIP Management Suite Overview and Integration Guide provides an overview about the use of client tools.
14
EMC ITOI VoIP Enablement Pack for Nortel Version 8.1 User Guide
Introduction
Processing flow The flow of information among the components of a VoIP Availability Manager and Enablement Pack deployment proceeds as follows. During discovery: ◆
The IP Availability Manager performs discovery of routers, switches, and hosts, as well as VoIP devices, along with their physical and logical connectivity.
◆
The IP Availability Manager groups the VoIP devices into a Topology Collection using deployment customization. This Topology Collection may be used to filter the devices monitored by VoIP Availability Manager based on customers’ organizational partitioning.
◆
VoIP Availability Manager imports the VoIP device information from the IP Availability Manager, and uses that information as the foundation for its own discovery.
◆
VoIP Availability Manager uses SNMP discovery probes and a CLI (Command Line Interface) probe to discover the VoIP specific entities: physical elements (for example, Cards and Trunks) as well as logical (applications, such as Voicemail Service and Call Forwarding Service).
◆
After a successful discovery, VoIP Availability Manager creates a VoIP topology with relationships between the associated elements.
During event processing: ◆
The IP Availability Manager polls network elements and performs root-cause and impact analysis for the IP domain.
◆
The IP Availability Manager sends notifications to the VoIP Availability Manager.
◆
VoIP Availability Manager, in conjunction with the installed Enablement Pack(s), uses SNMP and traps to monitor the health of the VoIP topology and generate appropriate symptoms and events.
◆
VoIP Availability Manager includes a built-in SNMP trap receiver which listens for VoIP related traps. Traps generated by the monitored devices and forwarded to the VoIP Availability Manager are processed to set the state of the referenced component. Note that the traps must be enabled and their destinations set.
◆
At regular intervals,VoIP Availability Manager imports the performance-oriented data collected by VoIP Performance Manager to enrich the VoIP Availability Manager topology.
◆
The Global Manager receives notifications from the IP Availability Manager and the VoIP Availability Manager for presentation to network operations personnel.
The EMC ITOI VoIP Availability Manager Configuration Guide provides detailed information about the architecture of VoIP Availability Manager and its Enablement Packs.
Processing flow
15
Introduction
Discovery and monitoring The Nortel Enablement Pack includes Nortel-specific probes that are activated when the VoIP Availability Manager starts. The probes are invoked as follows: ◆
The VoIP Availability Manager waits for the Nortel CS1000 components to be identified during the topology synchronization process with the IP Availability Manager.
◆
After all of the components of the CS1000 system are collected, Call Servers, Signaling Servers, Media Gateway cards, Call Pilot, SRG/BCM, Contact Center, IP phones, and IP phone groups are detected. Then, the appropriate probes are launched to discover them.
◆
Once the Signaling Server is identified, CLI is used to collect the Site ID and all the IP addresses of the components of the CS1000 system. The IP Addresses are used to create and establish appropriate relationships.
After discovery, the VoIP Availability Manager and Nortel Enablement Pack monitor the status of the Communication Server 1000 VoIP environment as reported by the Communication Server 1000 components. Incoming events or traps, such as Host/Service Down, are analyzed and symptoms such as Unresponsive or Down are generated.
Requirements for discovery The following are discovery requirements or deployment considerations for the EMC ITOI Enablement Pack for Nortel (Nortel Enablement Pack):
16
◆
Considerations for discovey and the Communication Server 1000 element classes that are discovered by the Nortel Enablement Pack are described in Chapter 3, “Discovering Elements and Monitoring Events.”
◆
The discovery of IP phones needs to be enabled during configuration. By default, discovery for these devices is not enabled. To do so, modify the parameters in the BASEDIR/smarts/conf/voip/voip.conf file, as described in the EMC ITOI VoIP Availability Manager Configuration Guide.
EMC ITOI VoIP Enablement Pack for Nortel Version 8.1 User Guide
Introduction
Trap processing The VoIP Availability Manager includes an integrated Trap Receiver and Notification Processor that provide the ability to utilize traps from external monitoring systems and map them into symptom events that are used for root-cause or impact analysis. The following summarizes how external traps are processed by the system. ◆
The integrated SNMP Trap Receiver receives a raw trap from an agent on a managed device.
◆
Traps received can indicate issues such as the failure of a CallServer or the degradation of a software service.
◆
The VoIP Availability Manager integrated Trap Receiver processes the traps and generates appropriate symptoms.
◆
The VoIP Availability Manager performs correlation and root-cause analysis and forwards the results to the Global Manager.
The EMC ITOI VoIP Availability Manager Configuration Guide provides detailed information on enabling trap processing.
Trap processing
17
Introduction
Installation The Nortel Enablement Pack is installed from the media on which the EMC ITOI VoIP Availability Manager resides. It is installed onto the same host and into the same folder as VoIP Availability Manager. A separate feature license is required and must be installed in order to use the Nortel Enablement Pack. The name of the feature is AP_VOIP_NORTEL. After the Nortel Enablement Pack is installed and properly licensed, it starts whenever the VoIP Availability Manager is started. For example, here is the UNIX command for starting the VoIP Availability Manager: /opt/InCharge/VoIP/smarts/bin/sm_service start ic-voip-server
When the VoIP Availability Manager starts, it loads the nortel.conf file and probes the unitary computer systems that are discovered by the IP Availability Manager in the VoIP environment for Nortel CS1000 components. Installation instructions for the EMC ITOI Enablement Pack for Nortel and verification steps such as starting services are described in the EMC ITOI VoIP Availability Manager Installation Guide.
18
EMC ITOI VoIP Enablement Pack for Nortel Version 8.1 User Guide
CHAPTER 2 Integrating the Enablement Pack with VoIP This chapter contains the following information: ◆ ◆ ◆ ◆
Specifying device-access login credentials for Nortel CLI discovery.......................... Nortel Signaling Server node IP addresses .............................................................. Excluding Nortel node IP addresses from the topology ............................................ CLI log file during discovery.....................................................................................
Integrating the Enablement Pack with VoIP
20 22 22 23
19
Integrating the Enablement Pack with VoIP
Specifying device-access login credentials for Nortel CLI discovery Since SNMP cannot be used to obtain complete topology data from Nortel Communication Server 1000 (CS 1000) systems, the discovery probes available through the Nortel Enablement Pack use CLI to obtain the topology data from these servers. For the Command Line Interface (CLI) discovery probes to establish communication sessions with the Nortel servers, you need to specify CLI login credentials (Device_User_ID and password). To do so, use the Device Access tab in Polling and Thresholds Console. This is the recommended method. In the Device Access tab, you can: ◆
Specify CLI login credentials for the default settings.
◆
Specify CLI login credentials per device or groups of devices.
In the Global Console, select Configure > Domain Manager Administration Console > Polling and Thresholds to open the Polling and Thresholds Console for the attached VoIP Availability Manager. In the Device Access tab, select the setting for the Nortel Servers group and specify the login credentials. EMC ITOI VoIP Availability Manager Configuration Guide describes default access device groups and default settings as well as the procedure for specifying CLI login credentials. When Signaling Server discovery starts, a CLI discovery probe retrieves the login credentials, establishes a Telnet connection to the master Signaling Server using the credentials, collects information from the Signaling Server, and executes a cslogin command to connect to the Call Server to gather information about the Call Server and its components. EMC ITOI VoIP Availability Manager Discovery Guide provides detailed information about discovery probes and phases. Note: For a testing or lab environment, you can specify CLI login credentials for the entire environment in the runcmd_env.sh file. This alternate method is described in “Creating credentials with login environment variables” on page 20. EMC Corporation does not recommend using this method in a production environment.
Creating credentials with login environment variables For the CLI discovery probes to establish communication sessions with the Nortel servers, you may add the device-access login environment variables identified in Table 1 on page 21 to the runcmd_env.sh file. Setting credentials in this manner is useful in a lab environment where all devices share the same user ids and passwords.
20
EMC ITOI VoIP Enablement Pack for Nortel Version 8.1 User Guide
Integrating the Enablement Pack with VoIP
Table 1 Device-access login environment variables for Nortel CLI discovery Environment variable
Description
SM_P_EXPECT_USERID=
Username for the Nortel Signaling Servers in the managed VoIP environment. Users should have permission to run ld 117, ld 22, and ld 97 programs on the Signaling Servers. ld is the syntax of Nortel CLI Command, as explained in the Nortel documentation.
SM_P_EXPECT_PASSWORD=
Password for the Nortel Signaling Servers in the managed VoIP network.
For CLI discovery to succeed, all managed Signaling Servers must be configured with the single set of credentials specified in Table 1 on page 21. Note: This will be operated in an unsecure mode. The username and password mentioned here will be in ASCII and readable. This method is used when you have the same userids and passwords for all of your signaling servers, usually in a test lab environment. To create device-access login credentials: 1. Go to the BASEDIR/smarts/bin directory in the VoIP Availability Manager installation area and type the following command to open the runcmd_env.sh file: sm_edit conf/runcmd_env.sh
2. Add the following lines to the file: SM_P_EXPECT_USERID= SM_P_EXPECT_PASSWORD=
Replace and with the appropriate values for your deployment. 3. Save and close the file. The modified version of the runcmd_env.sh file is saved to the BASEDIR/smarts/local/conf directory. 4. If VoIP Availability Manager was running before you edited the runcmd_env.sh file, restart VoIP Availability Manager. Upon completing this procedure, the runcmd_env.sh file will automatically set the device-access environment variables (and any other environment variables that the file contains) for each application or utility started from this installation area. To ensure successful CLI discovery, you should also ensure that enough terminal types (TTYs) are available for this communication (two additional TTYs from the existing configuration), as explained in the Nortel documentation, NTP 553-3031-210, Configuring Pseudo Terminals (PTYs). The EMC ITOI VoIP Availability Manager Discovery Guide provides detailed information about CLI discovery.
Specifying device-access login credentials for Nortel CLI discovery
21
Integrating the Enablement Pack with VoIP
Nortel Signaling Server node IP addresses As with most vendors, Nortel uses node IP addresses to provide redundancy in a hot standby configuration. In VoIP networks, that redundancy is between the server systems running the Signaling Server applications that together form a Signaling Server (redundancy) group. A backup server is able to inherit the IP address (hence the term “node IP address”) of the failed active (master) server and respond to client requests. To client devices, the signaling services appear running on a single call server. Currently, IP Availability Manager does not recognize Nortel node IP addresses and, therefore, discovers and monitors them as if they are regular management-type or access-type IP addresses. As a consequence, when the currently active Signaling Server fails and a backup Signaling Server takes over, IP Availability Manager does not detect an Unresponsive event—and thus does not diagnose a Down problem—for the failed server because the node IP address continues to respond to IP Availability Manager monitoring.
Excluding Nortel node IP addresses from the topology Eventually, the EMC ITOI certifications for the Nortel Call Manager servers will be changed so that IP Availability Manager will recognize the node IP addresses and automatically exclude them from its discovered topology. Until then, you can perform the procedures in this section to exclude node IP addresses from the topology. To exclude a node IP address, you create an ipExcludeList filter in the IP Availability Manager discovery.conf file. Note: In general, do not include any node IP addresses in a seed file and do not use the Add Agent command to enter node IP addresses. Seed files and the Add Agent command are described in the EMC ITOI IP Management Suite documentation.
Procedure to exclude a Nortel node IP address Upon identifying the node IP address, use the ipExcludeList parameter in the discovery.conf file to prevent the IP address from being added to the discovered topology. You can use wildcards, described in Appendix C, “Wildcard Patterns,”to specify matching patterns in the IP exclude patterns. Any IP address that matches an exclude pattern will NOT be added to the topology. To exclude a Nortel node IP address from the topology: 1. Go to the BASEDIR/smarts/bin directory in the IP Availability Manager installation area and type the following command to open the discovery.conf file: sm_edit conf/discovery/discovery.conf
2. Add your ipExcludeList filter to the file. Here is an example of an ipExcludeList filter: ipExcludeList += "192.11.13.6"
The filter excludes IP address 192.11.13.6 from being added to the topology.
22
EMC ITOI VoIP Enablement Pack for Nortel Version 8.1 User Guide
Integrating the Enablement Pack with VoIP
3. Save and close the file. The modified version of the discovery.conf file is saved to the BASEDIR/smarts/local/conf/discovery directory. 4. If IP Availability Manager was running before you edited the discovery.conf file, restart IP Availability Manager.
CLI log file during discovery During VoIP Availability Manager discovery, a temporary CLI log file is created and discarded. To retain the temporary file, set the TraceCLI or TraceDiscovery parameter in the voip.conf file to TRUE. If one of the trace parameters is set to TRUE, the CLI probe writes a record of the Telnet session with the Nortel Signaling Server or Call Server to a CLI log file. The log file includes the CLI commands issued by the probe and the responses returned by the server. The CLI log file is located in the BASEDIR/smarts/local/logs directory in the VoIP Availability Manager installation area. The naming convention for a CLI log file is: NORTEL--.txt
Where is the host of the target Nortel Signaling Server or Call Server, and is the number of seconds since January 1, 1970, 00:00:00 GMT. An example of a CLI log file name is: NORTEL-lwqnt012.lss.emc.com-1193308870.txt
Here is a typical error message recorded in a CLI log file when device-access login credentials are not specified in the Polling and Thresholds Console Device Access Tab for the Nortel Servers group: ***Warning: Can't find Security Settings object for .
CLI log file during discovery
23
Integrating the Enablement Pack with VoIP
24
EMC ITOI VoIP Enablement Pack for Nortel Version 8.1 User Guide
CHAPTER 3 Discovering Elements and Monitoring Events This chapter contains the following information: ◆ ◆ ◆ ◆ ◆ ◆
Discovering Nortel CS1000 elements ...................................................................... Nortel Enablement Pack object classes ................................................................... Nortel Enablement Pack attributes .......................................................................... Events for VoIP Availability Manager Nortel elements............................................... Impact Analysis....................................................................................................... Aggregates Analysis ................................................................................................
Discovering Elements and Monitoring Events
26 27 28 34 36 38
25
Discovering Elements and Monitoring Events
Discovering Nortel CS1000 elements To discover Nortel CS1000 devices in the VoIP environment and include those devices in the topology, you can either use the Add Agent option of the Domain Manager Administration Console or create a seed file for the IP Availability Manager. ◆
The seed file for the Availability Manager should contain the Nortel CS1000 components that need to be discovered: • All signalling servers IP addresses • All call servers IP addresses • All VGMC cards IP addresses • All MG (Cards) IP addresses • All Call Pilot IP addresses • All SRG/BCM IP addresses • All Symposium/Contact Center IP addresses • Other Nortel certified devices/applications
◆
After the seed file is created, perform discovery.
The EMC ITOI VoIP Availability Manager Discovery Guide provides detailed information about performing discovery. The EMC ITOI IP Management Suite documentation provides detailed information about creating a seed file.
Discovery considerations for Nortel devices To ensure that Nortel devices are discovered properly and that the correct topology for the Nortel CS1000 System is created, you need to consider the following: ◆
Traps in the Nortel VoIP environment come from a Call Server, Signaling Server, or VGMC. The Nortel administrator needs to configure these to handle the traps appropriately.
◆
On the Nortel Call Server, the Nortel administrator needs to specify these CLI commands so that Nortel cards will be discovered: ld 117 inv generate Cards
◆
Access is available. You need to verify that the IP Availability Manager and VoIP Availability Manager have access to the devices via SNMP (on default UDP ports 161 and 162). Also, you need to verify that all signaling servers discovered by IP Availability Manager and VoIP Availability Manager can connect to them.
◆
During discovery, ensure that no one is logged onto a signaling server or call server. If someone is logged in, discovery may not be completed successfully.
The EMC ITOI VoIP Availability Manager Discovery Guide provides detailed information about the discovery process.
26
EMC ITOI VoIP Enablement Pack for Nortel Version 8.1 User Guide
Discovering Elements and Monitoring Events
Nortel Enablement Pack object classes The VoIP Availability Manager builds a data model of the discovered Nortel CS1000 VoIP elements in its domain. The model represents the object classes and their relationships. Table 2 on page 27 lists the object classes that VoIP Availability Manager discovers for Nortel and displays in its topology. Table 2 Enablement Pack for Nortel CS1000 element classes Element
Description
Card
A physical container that typically resides in a chassis. VoIP Availability Manager is able to discover cards related to IP phones.
CallServer
A Unitary Computer System that is responsible for hosting the VoIP Call Manager
CallManager
A network service executing within a Nortel call server. The service provides call processing and control.
CallManagerRedundancyGroup
A redundant group of Nortel CallServers
IPPhone
An IP phone is a physical instrument that acts as a telephone using Voice over IP technology. An IP phone has the capability to communicate either only audio information or video and audio information.
IPPhoneGroup
A pool of phones sharing access to a specific set of VoIP network services. Member of VoipCluster.
GatewayService
A VGMC service, SSC service, or MGC card
MediaService
A service supported by all cards
SignalingService
A VoIP network service of a signaling server
SignalingRedundancyGroup
A redundancy group composed of Signaling Servers and VGMC, each running on its own server system
VoiceMailApplication
An application that provides a voice mail service
VoipApplication
A VoiceMailService, ConferenceService, or CTIService
VoipCluster
A group of CallServers and their components
VoipProcess
A process which makes up an application like CallPilot
The EMC ITOI VoIP Availability Manager User Guide provides a complete list of VoIP Availability Manager object classes.
Nortel Enablement Pack object classes
27
Discovering Elements and Monitoring Events
Nortel Enablement Pack attributes This section lists attributes for the Nortel Enablement Pack object classes.
Card Table 3 on page 28 lists some key attributes for the Card class. Table 3 Key attributes for Card Attribute
Description
Name
CARD-, with IP or host name
IsProxyDown
true or false
HasDownTrap
true or false
CallManager Table 4 on page 28 lists some key attributes for the CallManager class. Table 4 Key attributes for the CallManager class Attribute
Description
Name
SVC-, with host name and service name
Status
RESPONSIVE, UNRESPONSIVE
IsCritical
true or false
Type
Call server (CS1000), SRG
Vendor
The name of the vendor
SiteID
The ID of the CallManager site (318807827)
CallManagerRedundancyGroup Table 5 on page 28 lists some key attributes for the CallManagerRedundancyGroup class. Table 5 Key attributes for the CallManagerRedundancyGroup class
28
Attribute
Description
Name
RGRP-CS1000 and SiteID
NumberOfComponents
The number of components for the group
Type
HOT_STANDBY_FAILOVER
PctDown
The percentage of component services that are currently unavailable
EMC ITOI VoIP Enablement Pack for Nortel Version 8.1 User Guide
Discovering Elements and Monitoring Events
IPPhone Table 6 on page 29 lists some key attributes for the IPPhone class. Table 6 Key attributes for the IPPhone class Attribute
Description
CallAgentDiscovered
IP address of the discovered call agent to which the IP phone is registered
Description
Type and model of an IP phone
Extensions
List of phone extensions associated with this phone
IPAddress
IP address of the IP phone
MACAddress
MAC address of the IP phone
Model
Model of the IP phone
PrimaryPhoneDN
Primary phone extension number
RegistrationStatus
Registration state of the IP phone: • Registered (default). The IP phone is active. • Unregistered. The connection from the signaling server to the IP phone closed in the normal manner. • Deceased. The connection from the signaling server to the IP phone closed because the amount of time exceeded the keep-alive timeout limit. • Failed. The IP phone failed to registered to the signaling server. • Unknown.
Type
Type of the IP phone
Vendor
Name of the IP phone’s supplier
IPPhoneGroup Table 7 on page 29 lists some key attributes for the IPPhoneGroup class. Table 7 Key attributes for the IPPhoneGroup class Attribute
Description
DisplayName
Name of the IP phone group as displayed in the Global Console
IsManaged
Monitoring of the IP phone group is enabled or disabled. The default is False (disabled).
RegisteredPhones
The number of registered IP phones in this group
TotalPhones
The total number of IP phones in this group
UnregisteredPhones
The number of unregistered IP phones in this group
UnregisteredThreshold
The threshold value (percentage) of unregistered IP phones in the group
Vendor
Name of the IP phone’s supplier
Nortel Enablement Pack attributes
29
Discovering Elements and Monitoring Events
GatewayService Table 8 on page 30 lists some key attributes for the GatewayService class. Table 8 Key attributes for the GatewayService class Attribute
Description
Name
SVC-, with host name and service name
Status
RESPONSIVE, UNRESPONSIVE
IsCritical
true or false
Type
Service type: VGMC, MGC, or SSC
SiteID
The ID of the GatewayService site (318807827)
ExternalParams
List of parameter name and value pairs to construct the VoIP Performance Manager display URL
Description
Role of master, model number, or both (for example, 1000|MASTER)
RegisteredPhones
The number of IP phones registered to this gateway service
RegistrationStatus
Registration state of the IP phone: • Registered (default). The IP phone is active. • Unregistered. The connection from the gateway service to the IP phone closed in the normal manner. • Deceased. The connection from the gateway service to the IP phone closed because the amount of time exceeded the keep-alive timeout limit. • Failed. The IP phone failed to registered to the gateway service. • Unknown.
NumberOfComponents
The number of components for the gateway service
MediaService Table 9 on page 30 lists some key attributes for the MediaService class. Table 9 Key attributes for the MediaService class
30
Attribute
Description
Name
SVC-, with host name and service name
Status
RESPONSIVE, UNRESPONSIVE
IsCritical
true or false
Type
The card type: Ex, DLC, TMDI, ITG, DTR, etc.
SiteID
The ID of the MediaService site (318807827)
NumberOfComponents
The number of components for the media service
EMC ITOI VoIP Enablement Pack for Nortel Version 8.1 User Guide
Discovering Elements and Monitoring Events
SignalingService Table 10 on page 31 lists some key attributes for the SignalingService class. Table 10 Key attributes for the SignalingService class Attribute
Description
Name
SVC-, with host name, SignalingService
SystemName
Signaling server IP
Status
RESPONSIVE, UNRESPONSIVE
IsCritical
True or false
Type
Role of the Signaling service. Values can be: FOLLOWER or LEADER.
SiteID
The ID of the SignalingService site
Version
Signaling Server version
ExternalParams
List of parameter name and value pairs to construct the VoIP Performance Manager display URL
Description
Role of master, model number, or both (for example, 1000|MASTER)
RegisteredPhones
The number of IP phones registered to this signaling service
NumberOfComponents
The number of components for the signaling service
SignalingRedundanyGroup Table 11 on page 31 lists some key attributes for the SignalingRedundancyGroup class. Table 11 Key attributes for the SignalingRedundancyGroup class Attribute
Description
Name
RGRP-CS1000 and SiteID
NumberOfComponents
The number of components for the group
Type
HOT_STANDBY_FAILOVER
Nortel Enablement Pack attributes
31
Discovering Elements and Monitoring Events
VoiceMailApplication Table 12 on page 32 lists some key attributes for the VoiceMailApplication class. Table 12 Key attributes for the VoiceMailApplication class Attribute
Description
Name
APP-, host DNS name, CallPilot
IsCritical
True or false
Status
RESPONSIVE, UNRESPONSIVE
SystemName
CALLPILOT
Type
CallPilot
NumberOfComponents
The number of components for the voice mail application
VoipApplication Table 13 on page 32 lists some key attributes for the VoipApplication class. Table 13 Key attributes for VoipApplication
32
Attribute
Description
AgentSysName
Administratively-assigned name for service’s host
ApplicationName
Name of the application
IPAddress
Last known IP address of the service
Status
The current status of the Service. Value can be: RESPONSIVE, UNRESPONSIVE, DEGRADED, MALFUNCTION, STANDBY or UNKNOWN.
Type
Application type
Vendor
Manufacturer of the service
EMC ITOI VoIP Enablement Pack for Nortel Version 8.1 User Guide
Discovering Elements and Monitoring Events
VoipCluster Table 14 on page 33 lists some key attributes for the VoipCluster class. Table 14 Key attributes for the VoipCluster class Attribute
Description
TotalRoutes
Total number of routes in this cluster
TotalDegradedRoutes
The number of routes with degraded status
TotalDownRoutes
The number of routes with down status
TotalTrunks
Total number of trunks
TotalDownTrunks
The number of trunks with down status
ExternalParams
List of parameter name and value pairs to construct the VoIP Performance Manager display URL
TotalPhones
Total number of phones registered to this cluster
TotalDownPhones
The number of phones with down status
VoipProcess Table 15 on page 33 lists some key attributes for the VoipProcess class. Table 15 Key attributes for the VoipProcess Attribute
Description
Name
PROC-, CallPilot DNS name, service name
ProcessName
Service name.exe
Status
RESPONSIVE, UNRESPONSIVE
Nortel Enablement Pack attributes
33
Discovering Elements and Monitoring Events
Events for VoIP Availability Manager Nortel elements Table 16 on page 34 lists the classes of elements managed by VoIP Availability Manager with the Nortel Enablement Pack and the events that may occur for each class. Table 16 Events reported by VoIP Availability Manager for Nortel EP (page 1 of 2) Class
Events
Description
Card
ProxyDown
The card is down
CallManager
Unresponsive
This entity is unresponsive according to the status received or all of its critical components are unresponsive
CallManager RedundancyGroup
AllComponentsDown
All of the components in the redundancy group are down
AtRisk
The number of functioning components is below the AtRiskThreshold
ReducedRedundancy
GatewayService
Unresponsive
Unregistered
At least one component is not functioning but the total number of functioning components is above AtRiskThreshold This entity is unresponsive according to the status received or all of its critical components are unresponsive IP phone is not registered with any gateway service
PartialUnresponsive Partial components are unresponsive IPPhone
Unregistered
IP phone is not registered with any call agent
RegistrationRejected
Attempts by the IP phone to register with the call agent were rejected
IPPhoneGroup
Degraded
Unregistered IP phone percentage exceeds the threshold.
MediaService
Unresponsive
This entity is unresponsive according to the status received or all of its critical components are unresponsive
PartialUnresponsive
Partial components are unresponsive
34
EMC ITOI VoIP Enablement Pack for Nortel Version 8.1 User Guide
Discovering Elements and Monitoring Events
Table 16 Events reported by VoIP Availability Manager for Nortel EP (page 2 of 2) Class
Events
Description
SignalingService
Unresponsive
This entity is unresponsive according to the status received or all of its critical components are unresponsive
PartialUnresponsive
SignalingRedundancyGroup
AllComponentsDown
All of the components in the redundancy group are down
AtRisk
The number of functioning components is below the AtRiskThreshold
ReducedRedundancy
UnitaryComputerSystem
Partial components are unresponsive
At least one component is not functioning but the total number of functioning components is above AtRiskThreshold
ProxyDown (not visible)
Received Down event from IP Manager
Unresponsive
This entity is unresponsive according to the status received or all of its critical or key components are unresponsive
Host; Switch; Router; Node; CallServer; MediaGateway VoiceMailApplication
PartialUnresponsive
VoipApplication
Unresponsive
PartialUnresponsive
VoipNetworkService
Unresponsive
PartialUnresponsive
VoipProcess
Unresponsive
Partial components are unresponsive This entity is unresponsive according to the status received or all of its critical or key components are unresponsive Partial components are unresponsive This entity is unresponsive according to the status received or all of its critical or key components are unresponsive Partial components are unresponsive This entity is unresponsive according to the status received or all of its critical components are unresponsive
Events for VoIP Availability Manager Nortel elements
35
Discovering Elements and Monitoring Events
Impact Analysis Impacts describe the effect of an event or aggregate of events on other elements in the system. Table 17 on page 36 lists Down root-cause problems and their impacts. Table 17 Down root-cause problems and impacts
36
Problem
Impacts
Card
ProxyDown (not visible) Card CardImpact PackagesSystemUSC SystemImpact ComposedCard CardImpact CardRedundancyGroup GroupImpact RealizedNetworkAdapterImpact
CallManager Down
CallManager Unresponsive MediaService Unresponsive SignalingService Unresponsive
CallManagerRedundancyGroup Down
CallManagerRedundancyGroup AllComponentsDown/ ReducedRedundancy/AtRisk;
GatewayService Down
GatewayService Unregistered; VoipProcess Unresponsive; IPPhone Unregistered; IPPhoneGroup Degraded; SignalingRedundancyGroup AllComponentsDown/ ReducedRedundancy/AtRisk;
MediaService Down
Unresponsive ComposedOfMediaService Unresponsive
Port Down
ProxyDown ConnectedIPPhone Unregistered
SignalingService Down
IPPhone Unregistered IPPhoneGroup Degraded SignalingServiceRedundancyGroup AllComponentsDown/ ReducedRedundancy/AtRisk;
VoipApplication Down
Unresponsive VoipProcess Unresponsive
VoipNetworkService Down
Unresponsive VoipProcess Unresponsive
VoiceMailApplication Down
Unresponsive VoipProcess Unresponsive;
UnitaryComputerSystem Down (including subclasses)
Hosting Service DownSymptoms Composed Card CardImpact Composed UCS SystemImpact
EMC ITOI VoIP Enablement Pack for Nortel Version 8.1 User Guide
Discovering Elements and Monitoring Events
Table 18 on page 37 lists ServiceException root-cause problems and their impacts. Table 18 ServiceExeption root-cause problems and impacts Problem
Impacts
CallManager ServiceException
PartialUnresponsive VoipProcess Unresponsive
GatewayService ServiceException
PartialUnresponsive VoipProcess Unresponsive;
MediaService ServiceException
PartialUnresponsive MediaService Unresponsive
SignalingService ServiceException
PartialUnresponsive VoipProcess Unresponsive
VoipApplication ServiceException
PartialUnresponsive VoipProcess Unresponsive VoipElement Unresponsive
VoipNetworkService ServiceException
PartialUnresponsive VoipProcess Unresponsive
VoiceMailApplication ServiceException
PartialUnresponsive VoipProcess Unresponsive
Impact Analysis
37
Discovering Elements and Monitoring Events
Aggregates Analysis Aggregates indicate impacts on the logical group or application from services or components which have performance or availability exceptions. Table 19 on page 38 lists the current aggregates. Table 19 Aggregates Class
Aggregate name/description
Component events
VoipCluster
AvailabilityExceptions
CallManagerRedundancyGroup AllComponentsDown; SignalingServiceRedundancyGroup AllComponentsDown
VoipCluster issues a single notification to aggregate availability exceptions on redundancy group, voice mail, unavailable phones, or any components. PerformanceExceptions VoipCluster issues a single notification to aggregate performance exceptions on processor overload; call overload; media resource overload; media resource request being rejected; DS1 trunk overload; large phone registration changes, etc.
38
VoipCluster ResourceException; VoipCluster RoutesUnavailable; VoipCluster TrunksUnavailable;
IPPhone
Impacted
NetworkAdapter_Performance HighUtilization; NetworkAdapter_Performance HighErrorRate; NetworkAdapter_Performance HighDiscardRate; NetworkAdapter_Performance HighBroadcastRate; NetworkAdapter_Performance HighCollisionRate; NetworkAdapter_Performance HighQueueDropRate;
IPPhoneGroup
Impacted When one or more of the call manager groups it registers are down, or all CTI devices have unregistered with call managers in the group, or all gateway devices have unregistered with call managers in the group, or all media devices have unregistered with call managers in the group.
SignalingRedundancyGroup AllComponentsDown; SignalingService Unresponsive; GatewayService Unresponsive; NetworkAdapter_Performance HighUtilization; NetworkAdapter_Performance HighErrorRate; NetworkAdapter_Performance HighDiscardRate; NetworkAdapter_Performance HighBroadcastRate; NetworkAdapter_Performance HighCollisionRate; NetworkAdapter_Performance HighQueueDropRate;
RegistrationExceptions
IPPhone Unregistered
EMC ITOI VoIP Enablement Pack for Nortel Version 8.1 User Guide
APPENDIX A Understanding the sm_edit Utility Invisible Body Tag
This appendix describes how to use the sm_edit utility. It consists of the following topics: ◆ ◆
sm_edit .................................................................................................................. 40 sm_edit example .................................................................................................... 40
Understanding the sm_edit Utility
39
Understanding the sm_edit Utility
sm_edit As part of the EMC ITOI deployment and configuration process, you need to modify certain files. User modifiable files include configuration files, rule set files, templates, and seed files that contain encrypted passwords. Original versions of these files are installed into appropriate subdirectories under the BASEDIR/smarts/ directory. The original versions of files should not be altered. If a file must be modified, a new version should be created and then stored as a local copy of the file in BASEDIR/smarts/local or one of its subdirectories. When EMC ITOI software requires one of these files, it is designed to first search for a modified file in BASEDIR/smarts/local or one of its subdirectories. If a modified version of a file is not found in the local area, EMC ITOI software then searches corresponding BASEDIR/smarts directories for the original version of the file. To ease file editing and storage, EMC Corporation provides the sm_edit utility with every EMC ITOI product suite. When invoked, sm_edit opens the specified file in a text editor. This utility ensures that modified files are always saved to the appropriate local area and that non-local copies of all files remain unchanged. If an appropriate subdirectory does not exist for the file you are modifying, sm_edit creates the appropriate subdirectory before saving the modified file to that location. For files with header information set for encryption, sm_edit encrypts certain fields in the file. In addition, sm_edit preserves the file permissions of modified files, which helps ensure that important configuration files are not altered by unauthorized users. The EMC ITOI System Administration Guide provides instructions on how to configure the utility to use a specific editor.
sm_edit example To use sm_edit from the command line, specify the file name and include the subdirectory under BASEDIR/smarts/local where the file resides. For example, to edit the trapd.conf, enter the following command from the BASEDIR/smarts/bin directory: sm_edit conf/trapd/trapd.conf
In this example, sm_edit searches in the BASEDIR/smarts/local/conf/trapd directory for the trapd.conf file. If it finds the trapd.conf file, it opens the file in a text editor. If sm_edit does not find the trapd.conf file in the BASEDIR/smarts/local/conf/trapd directory, it creates a local copy of the trapd.conf file and writes it to the BASEDIR/smarts/local/conf/trapd directory. The EMC ITOI System Administration Guide provides additional information about the sm_edit utility.
40
EMC ITOI VoIP Enablement Pack for Nortel Version 8.1 User Guide
APPENDIX B Default Notification Attributes Invisible Body Tag
This appendix contains the following information: ◆
Default notification attributes ................................................................................. 42
Default Notification Attributes
41
Default Notification Attributes
Default notification attributes The VoIP Manager with the Nortel Enablement Pack displays various default notification attributes for events in the SAM Global Console. Table 20 on page 42 lists the default attributes. Table 20 Default notification attributes (page 1 of 2)
42
Notification Attribute
Description
AutoAcknowledgmentInterval
Automatically acknowledge this event if it is cleared for this interval 0 means never autoAcknowledge.
Category
Category of this event. The event category represents a broad categorization of the event, e.g. availability vs. performance.
Certainty
The certainty of this event. Defaults to 100.
ClassName
Class name of the object where this event occurred. This attribute along with InstanceName and EventName uniquely identify this event.
ClassDisplayName
Display name for the event class. Defaults to ClassName.
ClearOnAcknowledge
Indicates if this event should be cleared when it is acknowledged. Set this to TRUE only for events that do not expire nor have sources that generate a clear. Defaults to FALSE.
Description
A textual description of the object. Defaults to “ ”.
DisplayName
The string shown in the GUI when this object is displayed. Defaults to Name.
EventName
Name of the event. This attribute along with ClassName and InstanceName uniquely identify this event.
EventDisplayName
Display name for the event Name. Defaults to EventName.
EventText
The textual representation of the event.
EventType
Indicates the nature of the event. A MOMENTARY event has no duration. An authentication failure is a good example. A DURABLE event has a period during which the event is active and after which the event is no longer active. An example of a durable event is a link failure. (Possible values: DURABLE, MOMENTARY).
InstanceName
Instance name of the object where this event occurred. This attribute along with ClassName and EventName uniquely identify this event.
InstanceDisplayName
Display name for the event instance. Defaults to InstanceName.
OccurredOn
The element the indication is associated with. Setting this value causes ElementClassName and ElementName to be set appropriately.
OriginalSources
This table maps an original source to corresponding immediate sources.
ServiceName
Name of external server used for imported events and instrumented attributes.
EMC ITOI VoIP Enablement Pack for Nortel Version 8.1 User Guide
Default Notification Attributes
Table 20 Default notification attributes (page 2 of 2) Notification Attribute
Description
Severity
An enumerated value that describes the severity of the event from the notifier's point of view: 1 - Critical is used to indicate action is needed NOW and the scope is broad, e.g. an outage to a critical resource. 2 - Major is used to indicate action is needed NOW. 3 - Minor should be used to indicate action is needed, but the situation is not serious at this time. 4 - Unknown indicates that the element is unreachable, disconnected or in an otherwise unknown state. 5 - Normal is used when an event is purely informational. Default = 5.
SourceDomainName
The name(s) of the domain(s) that have originally diagnosed and notified - directly or indirectly - current occurrences of this event. If there are more than one original domain, the attribute lists each separated by a comma. When the notification is cleared, the last clearing domain stays in the value.
TroubleTicketID
Trouble ticket ID. Defaults to "".
UserDefined1-10
Ten user defined fields. Each field defaults to "".
Default notification attributes
43
Default Notification Attributes
44
EMC ITOI VoIP Enablement Pack for Nortel Version 8.1 User Guide
APPENDIX C Wildcard Patterns This appendix shows you how to use a wildcard pattern in a text field to match a number of objects instead of specifying each object by name. (EMC ITOI programs, such as the Global Console, enable you to specify wildcard patterns in text fields.) It consists of the following sections: ◆
Types of wildcard patterns....................................................................................... 46
Wildcard Patterns
45
Wildcard Patterns
Types of wildcard patterns A wildcard pattern is a series of characters that are matched against incoming character strings. You can use these patterns when you define pattern matching criteria. Matching is done strictly from left to right, one character or basic wildcard pattern at a time. Basic wildcard patterns are defined in Table 21 on page 46. Characters that are not part of match constructs match themselves. The pattern and the incoming string must match completely. For example, the pattern abcd does not match the input abcde or abc. A compound wildcard pattern consists of one or more basic wildcard patterns separated by ampersand (&) or tilde (~) characters. A compound wildcard pattern is matched by attempting to match each of its component basic wildcard patterns against the entire input string. Compound wildcard patterns are listed in Table 22 on page 47. If the first character of a compound wildcard pattern is an ampersand (&) or tilde (~) character, the compound is interpreted as if an asterisk (*) appeared at the beginning of the pattern. For example, the pattern ~*[0-9]* matches any string not containing any digits. A trailing instance of an ampersand character (&) can only match the empty string. A trailing instance of a tilde character (~) can be read as “except for the empty string.” Note: Spaces are interpreted as characters and are subject to matching even if they are adjacent to operators like “&”. Table 21 Basic wildcard patterns (page 1 of 2)
46
Character
Description
?
Matches any single character. For example, server?.example.com matches server3.example.com and serverB.example.com, but not server10.example.com.
*
Matches an arbitrary string of characters. The string can be empty. For example, server*.example.com matches server-ny.example.com and server.example.com (an empty match).
[set]
Matches any single character that appears within [set]; or, if the first character of [set] is (^), any single character that is not in the set. A hyphen (-) within [set] indicates a range, so that [a-d] is equivalent to [abcd]. The character before the hyphen (-) must precede the character after it or the range will be empty. The character (^) in any position except the first, or a hyphen (-) at the first or last position, has no special meaning. For example, server[789-].example.com matches server7.example.com through server9.example.com, but not server6.example.com. It also matches server-.example.com. For example, server[^12].example.com does not match server1.example.com or server2.example.com, but will match server8.example.com.
EMC ITOI VoIP Enablement Pack for Nortel Version 8.1 User Guide
Wildcard Patterns
Table 21 Basic wildcard patterns (page 2 of 2) Character
Description
Matches numbers in a given range. Both n1 and n2 must be strings of digits, which represent nonnegative integer values. The matching characters are a non-empty string of digits whose value, as a nonnegative integer, is greater than or equal to n1 and less than or equal to n2. If either end of the range is omitted, no limitation is placed on the accepted number. For example, 98.49.<1-100>.10 matches a range of IPv4 addresses from 98.49.1.10 through 98.49.100.10. Example of an omitted high end of the range: <50-> matches any string of digits with a value greater than or equal to 50. Example of an omitted low end of the range: <-150> matches any value between zero and 150. For a more subtle example: The pattern <1-10>* matches 1, 2, up through 10, with * matching no characters. Similarly, it matches strings like 9x, with * matching the trailing x. However, it does not match 11, because <1-10> always extracts the longest possible string of digits (11) and then matches only if the number it represents is in range.
|
Matches alternatives. For example,”ab|bc|cd” without spaces matches exactly the three following strings: “ab”, “bc”, and “cd”. A | as the first or last character of a pattern accepts an empty string as a match. Example with spaces “ab | bc” matches the strings “ab” and “ bc”.
\
Removes the special status, if any, of the following character. Backslash (\) has no special meaning within a set ([set]) or range () construct.
Special characters for compound wildcard patterns are summarized in Table 22 on page 47. Table 22 Compound wildcard patterns Character
Description
&
“And Also” for a compound wildcard pattern. If a component basic wildcard pattern is preceded by & (or is the first basic wildcard pattern in the compound wildcard pattern), it must successfully match. Example: *NY*&*Router* matches all strings that contain NY and also contain Router. Example: <1-100>&*[02468] matches even numbers between 1 and 100 inclusive. The <1-100> component only passes numbers in the correct range and the *[02468] component only passes numbers that end in an even digit. Example: *A*|*B*&*C* matches strings that contain either an A or a B, and also contain a C.
~
“Except” for a compound wildcard pattern (opposite function of &).If a component basic wildcard pattern is preceded by ~, it must not match. Example: 10.20.30.*~10.20.30.50 matches all devices on network 10.20.30 except 10.20.30.50. Example: *Router*~*Cisco*&*10.20.30.*~10.20.30.<10-20>* matches a Router, except a Cisco router, with an address on network 10.20.30, except not 10.20.30.10 through 10.20.30.20.
Types of wildcard patterns
47
Wildcard Patterns
48
EMC ITOI VoIP Enablement Pack for Nortel Version 8.1 User Guide
INDEX
A
I
Aggregates analysis 38
Impact analysis 36 Installation 18 Inventory Reporting feature Requirement 12 IP Availability Manager 13 IP Performance Manager 13 IP phone Class 27 Class attributes 29 Enable 16 ipExcludeList 22 IPPhoneGroup 27 Class attributes 29
B Backup Signaling Server 22
C Call Server 12 Class 27 CallManager 27 CallManagerRedundancyGroup 27 CallPilot 12 Card 27 Class attributes 28 Classes and events 34 Client tools 14 Command Line Interface (CLI) Discovery and monitoring 16 Polling 12 Communication Server 12, 16 Credentials CLI login 20 Cross-domain correlation 12
D Device Access tab 20 Device-access login 20 Credentials, specifying 20 Environment variables 20 Discovery And monitoring 16 Considerations 26 Nortel command for cards 26 Nortel CS1000 elements 26 discovery.conf ipExcludeList 22
L Log file CLI 23
M Mapping notification attributes to events 42 Matching Pattern 46 MediaService 27 Multiple user setup Requirement 12
N Nortel CS1000 requirements 12 Nortel Enablement Pack 12, 13 Discovery 15 Event processing 15 Processing flow 15 Nortel node IP addresses 22 nortel.conf 18 Notification attributes 42
E
O
Element classes 27 EMC online support website 7 Events 34 And impacts 36
Operator Wildcard 46
F Feature license 18
G GatewayService 27
P Pattern 46 Pattern matching 46 Probes 16 Processing flow 15
R Requirements 12 Discovery 16 Root-cause analysis 12 EMC ITOI VoIP Enablement Pack for Nortel Version 8.1 User Guide
49
Index
Down 36 ServiceException 36 runcmd_env.sh file 21
S Seed file 26 Service Assurance Manager 13 SignalingRedundancyGroup 31 SignalingRedundanyGroup 27 SignallingService 27 Site ID 16 SM_P_EXPECT_PASSWORD variable 21 SM_P_EXPECT_USERID variable 21 SNMP polling 12
T TraceCLI parameter 23 TraceDiscovery parameter 23 Trap processing 17
V VoiceMailApplication 27 VoIP Availability Manager 13, 27 VoipApplication 27, 32 VoipCluster 27 VoipProcess 27
W Wildcard 46 Chart of operators 46
50
EMC ITOI VoIP Enablement Pack for Nortel Version 8.1 User Guide
