Network Management System Product Manual

Network Management System Product Manual
Version 1.3
025-9575B
Software License
The Zetron software described in this manual is subject to the terms and conditions of Zetron's Software License Agreement, a copy of which is contained on the product distribution media or otherwise provided or presented to buyer. Installation and/ or use of the Zetron software constitutes acceptance of Zetron's Software License Agreement.
Limited Warranty
Buyer assumes responsibility for the selection of the Products to achieve buyer's or its customer's intended results obtained from the Products. If buyer has provided Zetron with any requirements, specifications or drawings, or if Zetron provides buyer with such materials, such materials are provided solely for buyer's convenience and shall not be binding on Zetron unless agreed in writing by the President of Zetron. ZETRON DOES NOT WARRANT THAT THE PRODUCTS OR ITS CUSTOMER'S REQUIREMENTS OR SPECIFICATIONS OR THAT OPERATION OF THE PRODUCTS WILL BE UNINTERRUPTED OR ERROR FREE. SUBJECT TO THE LIMITATIONS SET FORTH BELOW, Zetron warrants that all Zetron Products and Zetron Accessories will be free from material defects in material and workmanship for one year from date of shipment (except where indicated otherwise in the Zetron Price Book). For buyer's convenience, Zetron may purchase and supply additional items manufactured by others. In these cases, although Zetron's warranty does not apply, buyer shall be the beneficiary of any applicable third party manufacturer's warranties, subject to the limitations therein. Zetron's warranty covers parts and Zetron factory labor. Buyer must provide written notice to Zetron within the warranty period of any defect. If the defect is not the result of improper or excessive use, or improper service, maintenance or installation, and if the Zetron Products or Zetron Accessories have not been otherwise damaged or modified after shipment, AS ZETRON'S SOLE AND EXCLUSIVE LIABILITY AND BUYER'S SOLE AND EXCLUSIVE REMEDY, Zetron shall either replace or repair the defective parts, replace the Zetron Products or Zetron Accessories or refund the purchase price, at Zetron's option, after return of such items by buyer to Zetron. Shipment shall be paid for by the buyer. No credit shall be allowed for work performed by the buyer. Zetron Products or Zetron Accessories which are not defective shall be returned at buyer's expense, and testing and handling expense shall be borne by buyer. Out-of-warranty repairs will be invoiced at the then - current Zetron hourly rate plus the cost of needed components. THE FOREGOING WARRANTY AND THE THIRD PARTY MANUFACTURER'S WARRANTIES, IF ANY, ARE IN LIEU OF ANY AND ALL OTHER WARRANTIES EXPRESSED, IMPLIED OR ARISING UNDER LAW, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT AND FITNESS FOR A PARTICULAR PURPOSE.
Limitation of Liability
Zetron makes no representation with respect to the contents of this document and/or the contents, performance, and function of any accompanying software. Further, Zetron reserves the right to revise this document or the accompanying software and to make changes in it from time to time without obligation to notify any person or organization of such revisions or changes. ZETRON SHALL NOT UNDER ANY CIRCUMSTANCES BE LIABLE TO BUYER OR ANY THIRD PARTY FOR ANY INCIDENTAL, SPECIAL, CONSEQUENTIAL OR INDIRECT LOSS OR DAMAGE ARISING OUT OF OR CONNECTED WITH BUYER'S PURCHASE OR USE OF PRODUCTS OR SERVICES, INCLUDING WITHOUT LIMITATION, LOSS OF USE, LOSS OR ALTERATION OF DATA, DELAYS, LOST PROFITS OR SAVINGS, EVEN IF ZETRON HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES AND EVEN IF THE LIMITED REMEDY ABOVE IS FOUND TO FAIL OF ITS ESSENTIAL PURPOSE. IN NO EVENT SHALL ZETRON'S LIABILITY (WHETHER FOR NEGLIGENCE OR OTHER TORT, IN CONTRACT OR OTHERWISE) EXCEED THE PRICE PAID TO ZETRON FOR THE PRODUCTS. IP networks by their nature are subject to a number of limitations, such as security, reliability, and performance. Anyone using non-dedicated IP networks, such as shared WANs or the Internet, to connect to any Zetron Products or systems should consider and is responsible for these limitations.
Zetron, Inc. All rights reserved. This publication is protected by copyright; information in this document is subject to change without notice. Zetron and the Zetron logo are registered trademarks of Zetron, Inc. Other company names and product names may be the trademarks or registered trademarks of their respective owners. This publication may not be reproduced, translated, or altered, in whole or in part, without prior written consent from Zetron, Inc.
Compliance Statements The compliance statements for any particular piece of Acom hardware can be found in the front matter to the applicable Acom hardware manual.
Information on Disposal of Old Electrical and Electronic Equipment and Batteries (applicable for EU countries that have adopted separate waste collection systems ) Products and batteries with the symbol (crossed-out wheeled bin ) cannot be disposed as household waste. Old electrical and electronic equipment and batteries should be recycled at a facility capable of handling these items and their waste byproducts . Contact your local authority for details in locating a recycle facility nearest to you . Proper recycling and waste disposal will help conserve resources whilst preventing detrimental effects on our health and the environment . Notice: The sign Pb below the symbol for batteries indicates that this battery contains lead .
Change List for Rev B, 13 Jun 2011 Added the Call Detail Record (CDR) Management feature, which involves call event collection, processing, archiving, and querying. This entailed adding: the Call Detail Record Distributor service (pages 15, 64) MIS database views for CDR queries (83) and several new network attributes: Console Type (45) Console (50) Operator (52) Communication Device (48) and Trunk Group (47)
Also, the Network Management Console user interface was redesigned to a great extent. Accordingly, the manual was completely overhauled. Removed Windows 2000 from the list of supported operating systems and added Windows 7, see Computer Systems on page 17, also added Enabling MSMQ under Windows 7 on page 23 Removed the following sections from the manual: Defining Switch/System Types Defining Device Types Defining Alarm Event Status Types Defining Call Event Types Defining Radio and Telephone Interface Line Types Defining Statistic Types Added a section describing the use of the NMS Database Purge Utility, see Purge Utility on page 111
3
025-9575B
Contents
Contents
List of Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event Collectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CDR Distributors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing NMS Components and Related Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Windows 7 User Account Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database Server and Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Order of Software Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing MSMQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting Network Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 14 14 14 15 15 15 17 19 19 19 20 22 24 26
Defining Attributes of the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

For All Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . For Fault Event Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . For CDR Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Alarm Event Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Alarm Event Severity Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Network Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying Alarm Events to Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying Alarm Events by Network Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying Alarm Events by Alarm Event Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Console Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Trunk Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Communication Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Consoles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 29 30 32 34 36 38 39 41 42 43 45 47 48 50 52
Contents
Managing NMS Collector and Processor Services. . . . . . . . . . . . . . . . . . . . . . . 55

Event Processor Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event Collector Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CDR Distributor Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 58 64 67 68
Viewing Active Alarm Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Viewing Alarm Events in Real Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Viewing Alarm Event History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Device Alarm Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 MIS Database Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 View Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Abandoned Calls (VR_AbandonedCalls) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 ACD Queue Attachments (VR_AcdQueueAttachments) . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 ACD Session Details (VR_AcdSessionDetails) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 ACD Sessions (VR_AcdSessions) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 ACD Status Changes (VR_AcdStatusChanges). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Active Call List (VR_ActiveCallList) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Call Details (VR_CallDetails) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Call List (VR_CallList). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Console List (VR_ConsoleList). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Current ACD Queue Attachments (VR_CurrentAcdQueueAttachments) . . . . . . . . . . . . . . . 92 Current Agent Status (VR_CurrentAgentStatus). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Current Operators (VR_CurrentOperators) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Grouped Calls (VR_GroupedCalls) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Hourly Call Summary (VR_HourlyCallSummary) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Line Last Activity (VR_LineLastActivity) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Line List (VR_LineList) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Non-Call Details (VR_Non-CallDetails) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Operator Calls (VR_OperatorCalls) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Operator List (VR_OperatorList). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Operator Sessions (VR_OperatorSessions). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Operator Session Summary (VR_OperatorSessionSummary) . . . . . . . . . . . . . . . . . . . . . 101 Viewing NMS CDR Records with Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Excel Database Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Creating a Query in Excel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 What is it good for?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Diagnostic Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Purge Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Using the Purge Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Filtering by Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
025-9575B
Contents
Deleting by Date. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Contents
025-9575B
List of Procedures
This is a list of all of the procedures given in this manual. It is not necessarily an exhaustive list of all of the tasks that can be done with the NMS Network Management Console.
List of Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Confirming that Named Pipes and TCP/IP connections are enabled: . . . . . . . . . . . . . . . . . . 18 Installing NMS Components and Related Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 To adjust Windows 7 UAC:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 To install all NMS services and client on a single machine: . . . . . . . . . . . . . . . . . . . . . . . . . . 21 To install software on any computer that is to have the NMS user interface (Network Management Console) installed on it: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 To make Network Management Console UMS-enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 To install software on any computer that is to be a database host: . . . . . . . . . . . . . . . . . . . . 22 To install software on any computer that is to have an NMS Event Collector installed on it: . 22 To install software on any computer that is to have an NMS Event Processor installed on it: 22 To install software on any computer that is to have a CDR Distributor installed on it: . . . . . . 22 Installing MSMQ under Windows XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Enabling MSMQ under Windows 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Starting Network Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 To start Network Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 To restore a lost shortcut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 To define the network attributes (basic workflow) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Defining Attributes of the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

For All Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . For Fault Event Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To set up Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . For CDR Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To set up CDR Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To add a site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To modify a site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 29 30 30 31 32 32 33
List of Procedures
To delete a site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 System Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 To add a system entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 To modify a system entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 To delete a system entry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Defining Alarm Event Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 To modify an alarm event type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Defining Alarm Event Severity Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 To add an alarm event severity type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 To modify an alarm event severity type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 To delete an alarm event severity type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Managing Network Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 To add a network device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 To modify a network device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 To delete a network device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Specifying Alarm Events to Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 To select alarm events to monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Managing Console Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 To add a console type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 To modify a console type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 To delete a console type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Managing Trunk Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 To add a trunk group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 To modify a trunk group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 To delete a trunk group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Managing Communication Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 To add a communication device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 To modify a communication device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 To delete a communication device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Managing Consoles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 To add a console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 To modify a console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 To delete a console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Managing Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 To add an operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 To modify an operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 To delete an operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Managing NMS Collector and Processor Services. . . . . . . . . . . . . . . . . . . . . . . 55

Event Processor Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 To add an Event Processor service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 To modify an Event Processor connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 To delete an Event Processor service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Event Collector Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 To add an Event Collector connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 To modify an Event Collector connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 To add or modify an Event Collector service input (System Connection) . . . . . . . . . . . . . . . 60 To delete an Event Collector service input (System Connection) . . . . . . . . . . . . . . . . . . . . . 62 To add or modify an Event Collector service output (Reporter) . . . . . . . . . . . . . . . . . . . . . . 62 To delete an Event Collector service output (Reporter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 To delete an Event Collector service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 CDR Distributor Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
10 025-9575B
To add a CDR Distributor service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To modify a CDR Distributor service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To add or modify a CDR Distributor serial connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To delete a CDR Distributor serial connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To delete a CDR Distributor service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To view the trace log for a service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
64 65 66 67 67 67 68 68
Viewing Active Alarm Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Viewing Alarm Events in Real Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To clear alarms manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Alarm Event History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To generate an alarm event history report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To view a formatted version of the report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To print the formatted report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To save the formatted report in a file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 71 71 72 72 73 73
Device Alarm Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 MIS Database Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 View Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Viewing NMS CDR Records with Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Setting up an Excel database link: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 USing the Excel Query Wizard: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Diagnostic Viewer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

To run the Diagnostic Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Purge Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Purge Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Alarm tab of the purge utility: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing the oldest records from the database: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 112 112 113
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
11
List of Procedures
12
025-9575B
System Overview
Getting Started
This chapter includes an overview of Zetrons Network Management System (NMS), description of its components, and information on installing and starting the system. A graphical overview of the system is shown on page 16.
System Overview
NMS adds two major capabilities to Zetrons Acom communication switching platform: Fault Event Management collecting, archiving, and ad hoc querying of system device fault events that generate defined alarms Call Event Management collecting, archiving, and reporting of Call Detail Record (CDRs) NMS is connected to the various switches in the Acom system, from which it collects fault data and call detail data as they occur. It processes the data and writes records to a database. The database can be queried to generate reports based on user-specified parameters. Alarms can also be viewed in realtime. NMS is comprised of the following modules: one or more Event Collectors, which can collect fault and/or call events one or more Event Processors, which can process fault and/or call events one or more CDR Distributors, which can assemble processed call events into complete call detail records (CDRs) one or more message queues, which queue event data messages and pass them from Event Collectors to Event Processors a relational database, which is used to archive processed data and respond to queries a graphical user interface for configuring the Event Collectors, Event Processors, and CDR Distributors
13
Getting Started
defining the various attributes of your network and data (sites, systems, switch types, device types, alarm event types, alarm event severity types, alarm event status types, console types, consoles, operators, radio and telephone interface line types, trunk groups, and statistic types) specifying the network devices, communication devices, and events to monitor viewing alarm events in realtime generating alarm event history reports diagnostics
Event Collectors
An Event Collector listens for and receives incoming datagrams from the various network devices and communication devices, interprets these raw messages, translates those applicable to the event categories it is configured to monitor (faults and/or call events) into XML-formatted messages, and stores these events in a queue for further processing/ storage by the event processor service. The Event Collector is implemented as a Windows-based service.
Note Some configuration changes may require a service to be stopped and restarted in order for the change to take affect. This is done by way of the Windows Services control panel. On the Windows Start menu, select Settings, Control Panel, Administrative Tools, Services. Tip: All Zetron service names begin with NMS. The three services are: NMS.Collector, NMS.Processor, NMS.CdrDistributor.
Message Queues
Events received from a Zetron communication switch are written to a message queue by an Event Collector and read from the queue by an Event Processor. This queuing allows for operation of the processor or the database to be stopped briefly without giving up the messages that have been deposited in the queue. If there is an interruption in either the network or an Event Processor service, when the connections are restored the Event Processor will retrieve accumulated messages from the queue. The message queues are managed by Microsoft Message Queuing (MSMQ). Multiple instances of MSMQ may be implemented. The same instance of MSMQ can serve multiple Event Processors.
Event Processors
An Event Processor retrieves the collected events from the queue, parses them according to certain attributes of the system configuration, and ultimately makes them available for storage in the NMS database or sent to an appropriate event reporter.
14 025-9575B
System Overview
The Event Processor is implemented as a Windows-based service.
Databases
Event messages collected and processed by NMS are stored in a Microsoft SQL Server database.
CDR Distributors
CDR Distributor retrieves parsed call event messages from a TCP port, parses them according to certain attributes of the system configuration, and outputs them to another TCP port and/or one or more serial ports. CDR Distributors are implemented as a Windows-based service.
User Interface
The NMS user interface (Network Management Console on the Windows Start menu) is used for system administration, alarm event viewing and reporting, and diagnostics. It can be installed on any PC that has access to the network in which the NMS services are installed. The Active Event Viewer module supports the following features: A display of all active alarm events in a sortable list. A query interface for specifying the search criteria for reported alarm events. Reports can be filtered by any combination of the following query criteria: Start and end date and time Alarm event type Alarm event status Alarm event severity Device associated with the event Network location of the device in which the fault occurred (site, system, network address) Option of viewing a formatted report of the query results. Option of printing formatted reports. Option of saving formatted reports in several file formats, including: RTF PDF HTML
15
Getting Started
Note
Active Alarm Events on page 69.
For more information on the Active Event Viewer, see Viewing
Figure 1: Network Management System overview
Acom DS3 Switch A
Acom DS3 Switch B
Event Collector Service
TCP/IP or Serial
Collector Connection Event Filter
TCP/IP or Serial
Alarm File Reporter
Alarm MSMQ Reporter
CDR MSMQ Reporter
CDR File Reporter TCP/IP Configuration
FaultEvent Microsoft Message Queue
CallEvent Microsoft Message Queue
SQL Server
Event Processor Service
Alarm Consumer File Reporter Alarm Reporter
CDR Consumer CDR Reporter
CDR Distributor Service
Serial Listener
TCP/IP Listener
TCP/IP Configuration
NMS Client
3rd party Application Telnet logging client
16
025-9575B
System Overview
System Requirements
Computer Systems The following table lists the minimum and recommended requirements for each PC running any of the NMS processes.
Paramete r CPU Operating System Requirements Pentium III or equivalent minimum, Pentium IV recommended. Windows XP Professional with Service Pack 3 Windows Installer 4.5 (an add-on for Windows XP) Net Framework 3.5 (an add-on for Windows XP) Windows 7 Professional 1 GB minimum, 2 GB recommended. An 80 GB hard drive is required, possibly larger for database host. The NMS component software and related software occupy 285 MB (total), but the databases will be of indeterminate size. If connecting to a Zetron Communications Switch by means of serial port, the minimum is 1 serial port. Additional serial ports can be used for redundancy if desired and/or serial ports to support the Event Collector services. See To add or modify an Event Collector service input (System Connection) on page 60. 800 x 600 x 256 colors minimum, 1024 x 768 True Color recommended.
RAM Disk Space
Ports
Monitor
Tip
If you are using Windows 7, UAC should be disabled before installing or using Zetron software. See Windows 7 User Account Control on page 19.
Network Each PC that will be running NMS needs a 10/100 Base-T Ethernet network interface and TCP/IP. Static IP addresses must be used on the PCs running the Event Collector and Event Processor services. Record the IP addresses; they will be needed when configuring NMS services. SQL Database NMS stores and maintains data in a SQL Server database. The database versions currently supported are: SQL Server 2008 Standard Edition SQL Server 2008 Standard Edition R2 (release 2 update)
17
Getting Started
The information in the database can be accessed and used to generate reports either by using the Report Builder, Management Studio, and Reporting Services that are a part of the SQL Server 2008 Standard Edition or you can install a copy of Crystal Reports 2008 (Redistributable). When installing NMS in something other than a network Domain, choose the Mixed Mode Authentication option and set a sa password to allow for remote access for SQL management. Additionally, both Named Pipes and TCP/IP connections should be enabled.
Confirming that Named Pipes and TCP/IP connections are enabled:
1. From the START menu open the SQL Server Configuration Manager 2. Expand the node for SQL Server Network Configuration 3. Double-click on the option for Protocols for MSSQLSERVER 4. Make sure that both Shared Memory and Named Pipes & TCP/IP are enabled, you can enable an option by right-clicking on it and choosing ENABLE 5. If you have had to make any changes, reboot the server or at least restart the SQL Server Services Acom Firmware For use with Acom systems, the following minimum versions of Acom device firmware are required: ACS 4.272 ACU 1.82 ADS 2.05 ALS 4.45 DCU 4.41 MCU4 2.05 AOS 4.34 RVA 1.02 SMU 1.70
Note With ASB26+ the event time will be passed to the database with a time zone offset. The Acom backbone can be set to local time or GMT without affecting NMS. When using NMS with versions previous to Acom System Build 26, the Acom does not include the needed time zone offset so the Acom backbone time MUST be set to GMT. NMS collector machine Time Zone will affect how records are added to the database. If the Acom is configured for GMT/UTC, and the NMS Collector PC is set to GMT, then records are stored in the SQL database as GMT. If the Acom is configured for GMT and the NMS collector PC is set for local, then the records are stored in the SQL database with local time.
18
025-9575B
Installing NMS Components and Related Software

All NMS components can be installed on the same computer. They may also be divided among any networked computers in the system, if desired for performance improvement or system resiliency.
Windows 7 User Account Control

If you are using Windows 7, User Account Control (UAC) popup requests can interfere with NMS operation. UAC should be disabled prior to installing Zetron software.
To adjust Windows 7 UAC:
1. Open the Start menu and navigate to Control Panel, System and Security, and finally Change User Account Control Settings. 2. Lower the slider all the way down to Never Notify. 3. Restart the PC if prompted to do so.
Database Server and Instance

During installation of each of the NMS components, on the Database Server and Instance screen, you will be prompted for the name of the database server and database instance, in the form:
ServerName\InstanceName
For ServerName, use the Computer Name or IP address of the PC on which the instance of SQL Server that this component will use is installed. If the default value for database instance name was accepted when SQL Server was installed, you do not need to enter an InstanceName. Otherwise, follow ServerName by \ and the name of the database instance. On a computer with SQL installed, you can list possible SQL server instances by using the command line entry OSQL -L.
19
Getting Started
Database Connections The database connections can be verified after starting Network Management Console, by selecting Database Connections on the File menu.
The database connection can be changed from this window. If you do so, you will need to restart Network Management Console for the change to take effect. This updates the database pointer for Network Management Console only; the Processor service database pointer is specified in the Zetron.NetworkManagement.Processor.exe.config file. This menu only changes pointers for the Management console. If you need to change the database pointer used by the NMS services, please uninstall and reinstall the NMS services and specify the new database\instance during the install process.
Order of Software Installation

Note All of the software components mentioned in this section are installed by way of the NMS distribution CD, with the exception of Microsoft Message Queuing, which is a component of Microsoft Windows. To install it, see Installing MSMQ on page 22.
Following is the order of installation for NMS components and prerequisite software. The first case has all NMS services and client software on a single computer. The following cases break the installation up between two or more computers.
20
025-9575B
To install all NMS services and client on a single machine:
1. Windows Installer 3.1 or later 2. .NET Framework 2.0, if not already installed 3. MS Message Queue 4. SQL SVR 5. NMS Database (using Database Maintenance Utility) 6. NMS Collector, Processor, and CDR reporter services 7. NMS Management Console 8. Crystal Reports 9. Acrobat Reader 10. (optional) Zetron UMS 11. (optional) SQL management Studio (may have been installed with SQL) 12. (optional) Report Builder for SQL Server Reporting Services
To install software on any computer that is to have the NMS user interface (Network Management Console) installed on it:
1. .NET Framework 2.0, if not already installed. 2. Network Management Console program Run the installer NMS.ManagementConsole.msi. 3. UMS Parts of the interface can be logon-restricted by way of the Zetron User Management System. If this is desired, install Zetron AMI Server version 6 or later, UMS version 5.6.3.1506 or later, and then proceed to the following section. 4. Crystal Reports Version 2008 of the freely redistributable Crystal Reports Viewer for .NET Framework 2.0 is included in the NMS distribution. NMS uses the Crystal Reports Viewer for displaying alarm event query results in report format, for printing query reports, and for saving query reports in several file formats. Making Network Management Console UMS-enabled If desired, user access to Network Management Console can be controlled by UMS.
To make Network Management Console UMS-enabled
1. Edit this configuration file:

C:\Program Files\Zetron\Applications\NMS\ Management Console\ Zetron.MaintenanceConsole.exe.config
2. Find this section:

<appSettings> <add key=UmsEnabled value=false /> </appSettings>
3. Change the value to true.
21
Getting Started
4. For information on using UMS, see the User Management System Product Manual (part # 025-9516).
To install software on any computer that is to be a database host:
1. SQL Server. For supported versions, see SQL Database on page 17. 2. NMS Database Run the installer Zetron.NetworkManagement.Setup.Database.msi.
To install software on any computer that is to have an NMS Event Collector installed on it:
1. Microsoft .NET Framework 2.0, if not already installed. 2. MSMQ. All components except the Active Directory component must be installed. Each PC on which an Event Collector service will be running must have MSMQ installed on it, even if the Event Collector service will be using a remote instance of MSMQ. 3. NMS Event Collector service Run the installer NMS.Collector.msi.
To install software on any computer that is to have an NMS Event Processor installed on it:
1. .NET Framework 2.0, if not already installed. 2. NMS Event Processor service Run the installer NMS.Processor.msi.
Caution!
If the database server or database instance specified during installation are ever changed, you will need to stop, uninstall, reinstall, and restart the Event Processor service.
To install software on any computer that is to have a CDR Distributor installed on it:
1. .NET Framework 2.0, if not already installed. 2. NMS CDR Distributor service Run the installer NMS.CdrDistributor.msi.
Installing MSMQ
Installing MSMQ under Windows XP
1. On the Windows Start menu, select Settings, Control Panel, Add or Remove Programs. 2. In the Add or Remove Programs window, click Add/Remove Windows Components. 3. In the Windows Components Wizard window, select Message Queuing, then click Details.
22
025-9575B
4. In the Message Queuing window, select at least Common, then click OK. (The other options are not needed, but it will not make any difference if you install them.) You may need to provide your Windows XP product CD to finish the installation.
Enabling MSMQ under Windows 7
1. On the Windows Start menu, select the Control Panel link. 2. In the header of the Control Panel window, click on the down arrow to the right of the Control Panel and select the option Programs from the submenu that opens.
3. In the Programs Window window, under the heading Programs & Features, select the group labeled Turn Windows Features On or Off.
4. In the Windows Features window that opens, expand the Microsoft Message Queue (MSMQ) Server option, then expand the MSMQ Server Core.
23
Getting Started
5. Select the following three MSMQ services in order to enable them: MSMQ Triggers and Multicasting Support. 6. Click the OK button at the bottom of the dialog box. Windows will respond with a prompt cautioning you that it will be busy for a few minutes making the necessary changes. The prompt window closes automatically when the process is complete. 7. Close all of the Control Panel windows.
Starting Network Management Console
Tip
The term click is used commonly throughout this manual to indicate the act of selecting an object using a standard mouse interface. Network Management Console will also operate with a touch screen. Substitute touch if appropriate.
To start Network Management Console
Do either of the following: Double-click the shortcut icon labeled Network Management Console on the Windows Desktop. On the Windows Start menu, select Programs, Zetron, Network Management Console. Network Management Console loads the licensed NMS modules and establishes communication with the various services and switches. When the startup sequence
24
025-9575B
Starting Network Management Console
completes, the real-time alarm event viewer is displayed (it can also be accessed by way of Event Viewer on the main menu).
The main menu, in the left pane, is always displayed and does not change, regardless of the menu item selected.
Tip You may have to click twice on a main menu item to activate it.
For information on a main menu item, see the section of this manual cited in the following table.
Main Menu Item Event Viewer Event Manager Device Manager Diagnostic Viewer Configure Services Console Manager Communication Devices Operator Manager Trunk Group Manager To restore a lost shortcut Manual Section Viewing Alarm Events in Real Time on page 69 Specifying Alarm Events to Monitor on page 41 Managing Network Devices on page 39 Diagnostic Viewer on page 109 Managing NMS Collector and Processor Services on page 55 Managing Console Types on page 45 Managing Communication Devices on page 48 Managing Operators on page 52 Managing Trunk Groups on page 47
If for some reason both of the above shortcuts get deleted and cannot be recovered from the Windows Recycle Bin, they can be rebuilt by creating a new shortcut, using the following parameters: Target:
Zetron.MaintenanceConsole.exe Zetron.MaintenanceConsole.NMSViewer.zmc
Start in:
25
Getting Started
C:\Program Files\Zetron\NMS\Management Console\
Initial Configuration
Before putting the Network Management System into operation, various attributes of the network whose devices you want to monitor must be defined. The NMS Network Management Console provides the means to define all attributes of the network, but most of this work will be done automatically by NMS.
To define the network attributes (basic workflow)
After installing all of the NMS modules, this is the basic workflow: 1. Verify that all of your systems communication switches are started up. 2. Start up the Network Management Console. Initially, Event Viewer will be displayed. Select Configure Services. 3. Select the System Type Definition tab and set the Name list box to Sites. Click the New button and enter a Code, Name, and Description for the site you are setting up. A good choice for Name would be the customers name. 4. Select the System Setup tab, and create a new System Name for the site. Set the Type parameter to Zetron Acom System, then click Save. See System Setup on page 34. 5. Select the Processor tab, and configure an Event Processor. See To add an Event Processor service on page 55. 6. Select the Collector tab, and configure an Event Collector. See To add an Event Collector connection on page 58. Add at least one collector connection to the Acom network. 7. Switch to the NMS Device Manager (see Specifying Alarm Events to Monitor on page 41). Within a few minutes, NMS should have discovered all of the communication switches in the system and auto populated the list of network Devices than it can monitor. A default set of events to monitor is enabled. You may need to refine the list to your needs. 8. Switch to the Event Viewer. Within a few minutes NMS will display active alarms from the Acom network. 9. As applicable, you may need to adjust the default setup for Fault Event Management (see For Fault Event Management on page 29 and/or Call Event (Call Detail Record) Management (see For CDR Management on page 30).
26
025-9575B
Initial Configuration
If you do not see any progress with communications, as described in the preceding procedures, you should go ahead and attempt to troubleshoot it at this time.
Tip To troubleshoot potential problems, enable the Diagnostic Viewer for the Processor TCP/IP Fault reporter port 30202. (See Diagnostic Viewer on page 109.) This viewer can be used to monitor the messaging during NMS startup.
27
Getting Started
28
025-9575B
For All Systems
Defining Attributes of the Network
The initial definition of the devices within a Zetron Communication Switch is done automatically by NMS (you can always add, modify, or delete attributes later), but you should step through this process to verify that all configuration is correct, and to add or edit information if appropriate to your site needs.
For All Systems

See Initial Configuration on page 26.
For Fault Event Management

If Fault Event Management is not to be implemented, disregard this section. Fault Event Management setup is done automatically by NMS, but the setup can be modified manually. NMS is aware of the communication switch types and network device types that it can monitor and receive alarm event messages from. When an Acom switch comes online and is connected to NMS, it broadcasts its presence and that of the network devices it contains. NMS receives these messages and automatically populates its lists of known network devices. NMS associates a default set of alarm event types with each known network device type and a default alarm event severity type with each alarm event type. It uses this information to automatically populate its list of alarm events to monitor.
29
Entries in these automatically generated lists of network attributes can be modified, added, or deleted, according to customer needs. In particular, the alarm event severities assigned by default may need to be adjusted, according to customer needs.
To set up Fault Management
This procedure covers the network attributes that are relevant to Fault Event Management: 1. Network Device Types NMS can manage alarms generated by various types of Zetron network devices. A fixed set of device types is provided in NMS. 2. Alarm Event Types NMS can manage many types of alarm events. NMS assigns a default list of event types for each known device type. You may wish to refine the names and descriptions in the list of event types that NMS monitors in order to make the records easier to read. See Defining Alarm Event Types on page 36. 3. Alarm Event Severity Types Alarm events can be classified under various levels of severity. NMS assigns a default severity level for each known alarm event type. You may redefine list to better meet you needs. See Defining Alarm Event Severity Types on page 38. 4. Alarm Event Status Types NMS reports the status of alarm events. When initially installed, NMS creates the necessary status types; customers have the option of modifying this list if desired. Alarm events can be classified under various statuses. You need to define the statuses that you want to associate with the various alarm events. 5. Network Devices You create specific names and descriptions of the individual Zetron network devices that NMS finds to monitor. See Managing Network Devices on page 39. 6. Alarm Events For each specified Zetron network device, you need to select the alarm events that you want NMS to listen for. See Specifying Alarm Events to Monitor on page 41.
For CDR Management

If CDR Management is not to be implemented, disregard this section. CDR Management setup is done automatically by NMS, but the setup can be modified manually. NMS is aware of the communication device types it can monitor and receive call event messages from. When an Acom line subrack comes online, it broadcasts the presence of the lines it contains. NMS receives these messages and automatically populates its lists of known communication devices. In like manner NMS learns automatically about the presence of consoles and operators as they use the system.
30
025-9575B
For CDR Management
NMS associates a default set of call event types and statistic types with each known communication device type. It uses this information to automatically populate its list of call events to monitor. NMS is aware of the console types it can monitor and receive call event messages from. When Acom console comes online, they broadcast their presence. NMS receives these messages and automatically populates its lists of known consoles. NMS learns automatically about the presence of operators as they log on. Entries in these automatically generated lists of network attributes can be modified to change names and descriptions according to customer needs. However, it is not practical to add to or delete items from the list. Lines, consoles, operators and other system information is populated automatically as its discovered. After NMS has been running long enough to discover these resources, you may begin to customize them to make your reports more detailed. For example you could rename Acom line #1 to have a title of VHF Scanner or rename console 8 to be Flight Ops Dispatcher Desk1.
Note With default types, customers do not need to change any information for the system to work. The primary reason for editing any of these would be change the descriptions to match their own local definitions.
To set up CDR Management
This procedure covers the network attributes that are relevant to CDR Management: 1. Call Event Types NMS creates CDRs based on the call events that are received from the communications switch. Typically, the default CDRs are sufficient and should not need to be edited. 2. Console Types NMS assigns a default list of console types for each known type system. See Managing Console Types on page 45. 3. Consoles As consoles come on line, NMS adds them to the list of valid consoles within the system. You may wish to customize the name/description for reporting purposes. See Managing Consoles on page 50. 4. Operators As operators log on, NMS adds them to the list of valid operators within the system. You may wish to customize the name/description for reporting purposes. See Managing Operators on page 52. 5. Communication Devices NMS automatically includes all known devices in the list of devices to collect call events from. You may wish to customize the name/ description for reporting purposes. See Managing Communication Devices on page 48. 6. Trunk Groups A trunk group is not necessarily a physical group, but a logical group of phone trunk lines or radio channels that have the same or similar properties. They are optional. If you want to define them for query purposes, see Managing Trunk Groups on page 47.
31
7. Radio and Telephone Interface Line Types NMS assigns a default list of line types. The defaults are typically sufficient and do not need to be edited. 8. Statistic Types NMS assigns a default list of statistic types. The defaults are typically sufficient and do not need to be edited.
Defining Sites
Each Site may have one or more Systems. Instead of thinking of a site as a physical location, think of it as the entity or organization that owns/administers the systems that belong to it. The sites have an NMS port assigned in order to be connected into the NMS database. Database records are tagged with the originating site name to facilitate filtering the records at a later time. In the case of an Acom console system, a single port provides all fault and MIS record data for the entire site (all systems). The Acom supports a redundant NMS link to the same system for backup purposes but they both are tagged with the same System/Site name. You may utilize the single Default system/site in most cases. As far as NMS is concerned, an ACOM system includes all of the ADS units that are connected by the DS3 ring. Also included in that system are all of the ALS and ACU units that are connected to the ADS units making up the ring. This equipment may be installed at several physical locations, but it is all considered to be a single system and a single Collector is used to send records to NMS. Acom systems that are connected to one another by means of Inter-Site Bearers (ISB) are regarded as separate systems and each system must have its own connection to a Collector in order to be monitored by NMS. Sites are managed under Configure Services, on the System Type Definition tab. During installation, the list of sites will be populated only with code 0 (Default site).
To add a site
1. Select Sites from the list of system types in the Name box. 2. Click New. The fields in the lower area will become populated with default values where applicable. 3. Specify a Code. It must be all numeric, in the range 1-255. It must be unique among the entries in the list of site codes. It will be used in all records of events related to this site. 4. Specify a Name. This is expected to be a user-friendly term by which users will recognize the site. It can be up to 100 alphanumeric characters. Spaces are permitted. It will be used in all records of events related to this site.
32
025-9575B
Defining Sites
5. Optional: Specify a Description. It can be up to 200 characters of any kind. It will not be used in any event records.
STOP
Warning! Once a Site Code is added to the database (by clicking Save), it can never be edited. This is because it is the primary key in the database.
6. Click Save to add the entry, or click Cancel to discard it.

To modify a site
1. Select Sites from the list of system types in the Name box. 2. Select it from the list in the middle area. The fields in the lower area will become populated with the values for the selected site. The list can be sorted by any column by clicking the column heading. To sort in reverse order, click the heading again. 3. Edit the fields as necessary. 4. Click Save.
To delete a site
Deleting a site does not actually lose its information. It is marked as deleted, and it will no longer be included in any NMS data collection, but it remains in the configuration database. It will still be used in query results if applicable, and it can be recovered if needed again in the system. If a site is added in the future, and the
33
same Code is used, you will be prompted as to whether you want to reuse the information that was entered when the Code was previously used. 1. Select Sites from the list of system types in the Name box. 2. Select it from the list in the middle area. 3. Click Remove, or press Delete.
System Setup
The system setup consists of one or more system entries, each of which specifies the relationship between one switch/system and one site. The system setup is managed under Configure Services, on the System Setup tab. During installation, the list of system entries will be populated only with code 0 (Default system, Default site).
34
025-9575B
System Setup
Note
The installer must change the site Type to Zetron Acom System to collect Acom NMS events.
To add a system entry
PREREQUISITES: Define the associated site. See Defining Sites on page 32. 1. Click New. The fields in the lower area will become populated with default values where applicable. 2. Specify a Code. It must be all numeric, in the range 1-99. It must be unique among the entries in the list of system entries. It will be used in all records of events related to this system. 3. Specify a Name. This is expected to be a user-friendly term by which users will recognize the system entry. It can be up to 100 alphanumeric characters. Spaces are permitted. It will be used in all event records related to this system. 4. Select the related Site from the drop-down list. 5. Select the related switch/system from the Type drop-down list. 6. Optional: Specify a Description. It can be up to 200 characters of any kind. It will not be used in any event records. 7. Click Save to add the entry, or click Cancel to discard it.
To modify a system entry
1. Select it from the list in the upper area. The fields in the lower area will become populated with the values for the selected site. The list can be sorted by any column by clicking the column heading. To sort in reverse order, click the heading again. 2. Edit the fields as necessary. 3. Click Save.
To delete a system entry
Deleting a system entry does not actually lose its information. It is marked as deleted, and it will no longer be included in any NMS reporting, but it remains in the configuration database and can be recovered if needed again. If a system entry is added in the future, and the same Code is used, you will be prompted as to whether you want to reuse the information that was entered when the Code was previously used. 1. Select it from the list in the upper area. 2. Click Remove, or press Delete. The list updates automatically.
35
Defining Alarm Event Types

Alarm event types are managed under Configure Services, on the System Type Definition tab. Select Alarm event type codes from the Name drop-down list. During installation, the list of alarm event types is automatically populated with all alarm event types that can be associated with the known network device types and monitored through NMS. The installer may wish to update the name/description for fault events to something more obvious or descriptive.
Caution!
While it is possible to edit the name and description for the alarm event types automatically generated by NMS, the user should not attempt to remove alarm events from the list. Adding a new alarm to the list is pointless since NMS only receives events based on the hardware actually installed in the Acom.
To modify an alarm event type
1. Select it from the list in the middle area. The fields in the lower area will become populated with the values for the selected item. The list can be sorted by any column by clicking the column heading. To sort in reverse order, click the heading again.
36
025-9575B
Defining Alarm Event Types
2. Edit the fields as desired. You can change an event types name or description if that will make it more obvious to you. For example, ACU E1 Link1 NOS alarm could have a description of E1 link A between ACU-1A and ACU-1B has been broken. If you make any changes, they will only affect future alarm events after the Processor service is stopped and restarted. 3. Click Save.
37
Defining Alarm Event Severity Types

Alarm event severity types are managed under Configure Services, on the System Type Definition tab. Select Alarm event severity codes from the Name drop-down list. During installation, the list of alarm event severity types is automatically populated with six default codes.
To add an alarm event severity type
1. Click New. The fields in the lower area will become populated with default values where applicable. 2. Specify a Code. It can be up to 50 characters, but no spaces or special characters are permitted. It must be unique among the entries in the list of alarm event severity type codes. It will be used in all records of alarm events of this severity. 3. Specify a Name. This is expected to be a user-friendly term by which users will recognize the alarm event severity. It can be up to 100 alphanumeric characters. Spaces are permitted. It will be used in all records of alarm events of this severity. 4. Optional: Specify a Description. It can be up to 200 characters of any kind. It will not be used in any event records. 5. Click Save to add the entry, or click Cancel to discard it.
38 025-9575B
Managing Network Devices
To modify an alarm event severity type
1. Select it from the list in the middle area. The fields in the lower area will become populated with the values for the selected item. The list can be sorted by any column by clicking the column heading. To sort in reverse order, click the heading again. 2. Edit the fields as desired. You can change an event severity types name or description if that will make it more obvious to you. If you make any changes, they will only affect future alarm events after the Processor service is stopped and restarted. 3. Click Save.
To delete an alarm event severity type
Deleting an alarm event severity type does not actually lose its information. It is marked as deleted, and it will no longer be included in any NMS data collection, but it remains in the configuration database. It will still be used in query results if applicable, and it can be recovered if needed again in the system. If an alarm event severity type is added in the future, and the same Code is used, you will be prompted as to whether you want to reuse the information that was entered when the Code was previously used.
STOP
Warning! Deleting an alarm event severity type will change the alarm event severity of associated alarm events to 0 (Unknown severity).
1. Select it from the list in the middle area. 2. Click Remove, or press Delete. The list updates automatically.
Managing Network Devices

Individual network devices are managed under Device Manager. The installer/system maintenance technician may find it worthwhile to assign descriptive aliases to devices so that the reports are more readable for him/her-self and others.
39
To add a network device
PREREQUISITES: A network device is one instance of a specific network device type in a specific switch/system type at a specific site. Define the associated network device type.
Note The list of valid devices that NMS can report on will be automatically populated the first time a switch is connected to NMS. It is rarely necessary to manually add/remove a device instance.
1. Select the System/Site from the drop-down list. (This is the list of system entries from the system setup.) 2. Select the Device Type from the drop-down list.
3. Specify the network Address of the device in the system. For Acom systems, this can be determined through IMS Terminal. It will be used in all records of alarm events associated with this device. 4. Optional: Specify a Description. It can be up to 200 characters of any kind. The description will not be seen in the Event Viewer, but it will be recorded in the AlarmEventLog table in the database. 5. Click Add.
40
025-9575B
Specifying Alarm Events to Monitor
To modify a network device
1. Select it from the list in the upper area. The fields in the lower area will become populated with the values for the selected item. 2. Edit the fields as necessary. 3. Click Update.
To delete a network device
When a network device is physically removed from the system, the Acom system will stop reporting events for that device. you may remove the device is you wish. Deleting a network device does not actually lose its information. It is marked as deleted, and it will no longer be included in any NMS data collection, but it remains in the configuration database. It will still be used in query results if applicable, and it can be recovered if needed again in the system. If a network device is added in the future, and you fill in all of the required fields with values that existed previously in a single network device description, you will be prompted as to whether you want to reuse the information that was entered for the network device when it was previously used. 1. Select it from the list in the upper area. 2. Click Remove.

The list of alarm events that NMS is to monitor is managed under Event Manager.
41
To select alarm events to monitor
PREREQUISITES: An alarm event is defined as a specific alarm event type associated with a specific alarm event severity type occurring in a specific network device. Define all alarm event types. Unmonitored events are still saved into the NMS database, the Monitored flag is used to filter unwanted events from being displayed in the Event Viewer of the NMS Management Console. There are two ways to specify alarm events to monitor, as described in the following two subsections.
Specifying Alarm Events by Network Device

This method entails selecting a network device, then selecting alarm events to associate it with. 1. Select View by Device. All network devices will be listed in a hierarchy on the left. 2. Click the + next to the site name to display the systems at the site. 3. Click the + next to the system name to display the communication switches in the system. 4. Click the + next to the switch name to display the network devices in the switch.
42
025-9575B
5. Select the device by clicking its name. The alarm event types that can be associated with the selected device are listed on the right. 6. Select the Event Severity from the drop-down list. The Events list can be sorted by any column by clicking the column heading. To sort in reverse order, click the heading again. 7. By checking the appropriate boxes under Monitor, select one or more alarm event types that you want to monitor in association with the selected device and that you want to assign the same severity type to.
Note Only alarm events that have the Monitor box selected will be displayed in the Event Viewer (see Viewing Alarm Events in Real Time on page 69).
Tip
By selecting a device type and then selecting the Monitor box, the monitor setting will be applied to all devices of that type.
8. Optional: You may modify the On severity of the Device Description alarm event(s). 9. Click Save. The Devices tree collapses. 10. Repeat steps 2-9 as necessary for all network devices and alarm event severity types.
Tip Clicking Undo resets all settings to the last saved state.
Specifying Alarm Events by Alarm Event Type

This method entails selecting an alarm event, then selecting network devices that you want to monitor/report the event. 1. Select View by Event. The Events pane will list all alarm event types alphanumerically.
43
2. Select the alarm event type by clicking its name. The network devices that can be associated with the selected alarm event type are listed on the right. 3. Select the Event Severity from the drop-down list. 4. By checking the appropriate boxes under Monitor, select one or more network devices that you want to monitor in association with the selected alarm event type and that you want to assign the same alarm event severity type to. The Target Device list can be sorted by any column by clicking the column heading. To sort in reverse order, click the heading again.
Note Only alarm events that have the Monitor box selected will be displayed in the Event Viewer (see Viewing Alarm Events in Real Time on page 69).
Tip
By selecting a device type and then selecting the Monitor box, the monitor setting will be applied to all devices of that type.
5. Click Save.
44
025-9575B
Managing Console Types
6. Repeat steps 2-5 as necessary for all alarm event severity types and network devices.
Tip Clicking Undo resets all settings to the last saved state.
Managing Console Types

Console types are managed under Configure Services, on the System Type Definition tab. Select Console type codes from the Name drop-down list. During installation, the list of console types is automatically populated with the available console types that NMS finds in the system. The console types are used when defining specific consoles (see Managing Consoles on page 50).
45
To add a console type

Note This procedure will only be useful when Zetron adds a new console type that NMS is able monitor.
1. Click New. The fields in the lower area will become populated with default values where applicable. 2. Specify a Code. It can be up to 50 characters, but no spaces or special characters are permitted. It must be unique among the entries in the list of console type codes. It will be used in all records of call events associated with this console type. 3. Specify a Name. This is expected to be a user-friendly term by which users will recognize the console type. It can be up to 100 alphanumeric characters. Spaces are permitted. It will be used in all records of call events associated with this console type. 4. Optional: Specify a Description. It can be up to 200 characters of any kind. It will be not used in any event records. 5. Click Save to add the entry, or click Cancel to discard it.
To modify a console type
1. Select it from the list in the middle area. The fields in the lower area will become populated with the values for the selected item. The list can be sorted by any column by clicking the column heading. To sort in reverse order, click the heading again. 2. Edit the fields as desired. You can change a console types name or description if that will make it more obvious to you. 3. Click Save.
To delete a console type
Deleting a console type does not actually lose its information. It is marked as deleted, and it will no longer be included in any NMS CDR collection, but it remains in the configuration database. It will still be used in query results if applicable, and it can be recovered if needed again in the system. If a console type is added in the future, and the same Code is used, you will be prompted as to whether you want to reuse the information that was entered when the Code was previously used. 1. Select it from the list in the middle area. 2. Click Remove, or press Delete. The list updates automatically.
46
025-9575B
Managing Trunk Groups
Managing Trunk Groups

Trunk groups are logical groups of either phone trunk lines or radio channels, grouped because they have the same or similar properties. Trunk groups are optional; no list of trunk groups is automatically generated. Trunk groups can be defined and managed under Trunk Group Manager. The trunk groups are used when defining specific communication devices (see Managing Communication Devices on page 48). The trunk group tag may make your reports more useful by grouping like lines together.
To add a trunk group
1. Select the System from the drop-down list. 2. Specify a Name. This is expected to be a user-friendly term by which users will recognize the trunk group. It can be up to 100 alphanumeric characters. Spaces are permitted. It will be used in all records of call events associated with this trunk group. 3. Specify a Number. Valid range is 1-1000. It must be unique among the entries in the list of trunk groups. It will be used in all records of call events associated with this trunk group.
47
4. Optional: Specify a Description. It can be up to 200 characters of any kind. It will be not used in any event records. 5. Click Add.
To modify a trunk group
1. Select it from the list in the upper area. The fields in the lower area will become populated with the values for the selected item. The list can be sorted by any column by clicking the column heading. To sort in reverse order, click the heading again. 2. Edit the fields as desired. You can change a trunk groups name or description if that will make it more obvious to you.
Note The trunk group number cannot be changed. Editing the Number field will cause the system to assume you are adding a trunk group.
3. Click Update.
To delete a trunk group
Deleting a trunk group does not actually lose its information. It is marked as deleted, and it will no longer be included in any NMS data collection, but it remains in the configuration database. It will still be used in query results if applicable, and it can be recovered if needed again in the system. If a trunk group is added in the future, and you fill in all of the required fields with values that existed previously in a single trunk group description, you will be prompted as to whether you want to reuse the information that was entered for the trunk group when it was previously used. 1. Select it from the list in the upper area. 2. Click Remove, or press Delete. The list updates automatically.
Managing Communication Devices

The list of communication devices that NMS is to monitor is managed under Communication Devices. The list of communication devices is automatically populated by NMS the first time a communications switch is connected to NMS. Individual lines are added to the database as they are used.
48
025-9575B
Managing Communication Devices
To add a communication device

Tip Rather than adding comm devices manually, it is recommend that the installer select each radio or phone line at the console one at a time to trigger NMS to add the device to the database automatically. Then the installer edits the created device.
PREREQUISITES: A communication device is one instance of a specific device type in a specific system. Define the associated system (see System Setup on page 34). If the device is to be a member of a trunk group, also define the trunk group (see Managing Trunk Groups on page 47). 1. Select the System from the drop-down list. 2. Select the Device Type from the drop-down list. 3. If applicable, select the Trunk Group from the drop-down list. 4. Select the Category from the drop-down list. 5. Specify an Alias. This is expected to be a user-friendly term by which users will recognize the device. It can be up to 100 alphanumeric characters. Spaces are permitted. It will be used in all records of call events associated with this device. 6. Specify an Interface ID. This is the line or channel number as defined in the Acom system. Refer to the line or channels definition in the appropriate Acom program (IMS ALS or IMS ADS). It must be unique among the entries in the list of
49
communication devices. It will be used in all records of call events associated with this device.
To modify a communication device
1. Select it from the list in the upper area. The fields in the lower area will become populated with the values for the selected item. The list can be sorted by any column by clicking the column heading. To sort in reverse order, click the heading again. 2. Edit the fields as desired. You can change a devices alias or description if that will make it more obvious to you. 3. Click Update.
To delete a communication device
Deleting a communication device does not actually lose its information. It is marked as deleted, and it will no longer be included in any NMS data collection, but it remains in the configuration database. It will still be used in query results if applicable, and it can be recovered if needed again in the system. If a communication device is added in the future, and you fill in all of the required fields with values that existed previously in a single communication device description, you will be prompted as to whether you want to reuse the information that was entered for the communication device when it was previously used. 1. Select it from the list in the upper area. 2. Click Remove, or press Delete. The list updates automatically.
Managing Consoles
The list of consoles is automatically populated the first time that an operator logs onto the console position. Rather than adding consoles manually it is recommended that the installer log on to each console in the system before customizing their names/descriptions.
To add a console
PREREQUISITES: A console is one instance of a specific console type in a specific system. Define the associated system (see System Setup on page 34) and console type (see Managing Console Types on page 45). It is suggested to log on to each console to trigger record creation in the database rather than add them manually. 1. Select the System from the drop-down list. 2. Select the Console Type from the drop-down list.
50
025-9575B
Managing Consoles
3. Specify an Alias. This is expected to be a user-friendly term by which users will recognize the console. It can be up to 100 alphanumeric characters. Spaces are permitted. It will be used in all records of call events associated with this console. 4. Specify the Number. This is the console number that the console is known by in the communication network. 5. Click Add.
To modify a console
1. Select it from the list in the upper area. The fields in the lower area will become populated with the values for the selected item. The list can be sorted by any column by clicking the column heading. To sort in reverse order, click the heading again. 2. Edit the fields as desired. You can change a consoles alias if that will make it more obvious to you. 3. Click Update.
To delete a console
Deleting a console does not actually lose its information. It is marked as deleted, and it will no longer be included in any NMS data collection, but it remains in the configuration database. It will still be used in query results if applicable, and it can be recovered if needed again in the system. If a console is added in the future, and
51
you fill in all of the required fields with values that existed previously in a single console description, you will be prompted as to whether you want to reuse the information that was entered for the console when it was previously used. 1. Select it from the list in the upper area. 2. Click Remove, or press Delete. The list updates automatically.
Managing Operators
The list of console operators that NMS is to monitor is managed under Operator Manager. The list of operators is automatically populated with all that have been detected as they logged on, either through UMS or (in the case of Acom only) ACS.
To add an operator
PREREQUISITES: Operators are associated with a specific site. Define the associated site (see Defining Sites on page 32). 1. Select the Site from the drop-down list.
52
025-9575B
Managing Operators
2. Specify an Alias. This is expected to be a user-friendly term by which users will recognize the operator. It can be up to 100 alphanumeric characters. Spaces are permitted. It will be used in all records of call events associated with this operator. 3. Specify the operators First Name and Last Name. 4. Click Add.
To modify an operator
1. Select the operator from the list in the upper area. The fields in the lower area will become populated with the values for the selected operator. The list can be sorted by any column by clicking the column heading. To sort in reverse order, click the heading again. 2. Edit the fields if necessary.
Note The operators alias is provided automatically when the operator logs on, whether through UMS or ACS. If the operator logs on through UMS, the first and last name will also be provided. The alias cannot be changed. Editing the Alias field will cause the system to assume you are adding an operator.
3. Click Update.
To delete an operator
Deleting an operator does not actually lose its information. It is marked as deleted, and it will no longer be included in any NMS data collection, but it remains in the configuration database. It will still be used in query results if applicable, and it can be recovered if needed again in the system. If an operator is added in the future, and you fill in all of the required fields with values that existed previously in a single operator description, you will be prompted as to whether you want to reuse the information that was entered for the operator when it was previously used. 1. Select it from the list in the upper area. 2. Click Remove, or press Delete. The list updates automatically.
53
54
025-9575B
Event Processor Services
Managing NMS Collector and Processor Services
After defining all of the network attributes, use Network Management Console to specify where the NMS Event Collector and Event Processor services are installed, how they communicate, and the sites, switch/system types, and event categories they monitor. This chapter includes instructions for configuring the services. To display the work area, select Configure Services.
Note You should configure the services in this order: Processor, Collector, CDR Distributor (optional).

The Processor tab displays the configuration information for all NMS Event Processor Connections. If any Event Processor Connections have been configured, they are listed in the upper area. The Event Processor service consumes events from the MS Message Queue and archives it into the SQL database and reporters. While the might be multiple Event Processor Connections, there is typically only a single Processor service.
To add an Event Processor service
PREREQUISITE: Install the Event Processor module (see Installing NMS Components and Related Software on page 19). 1. Click New. 2. Specify a Name. This is expected to be a user-friendly term by which users will recognize this service. It can be up to 50 alphanumeric characters. Spaces are
55
permitted. It will not be used in any event records. It must be unique among the entries in the list of Events Processor Services. 3. Specify the IP address of the PC hosting this service. 4. Specify the number of the host PCs TCP Port through which Network Management Console should connect to this service for configuration purposes. The default processor service port is 30102 and can only be changed by manually editing the service's config file.
5. Click Apply. Network Management Console attempts to connect to the IP address and port you have specified, to see if there is an Event Processor service running there. If there is not, the message Connection failed is displayed in the upper area. Verify that the Event Processor module is installed, the service is started, and that the correct IP address and port are specified. If there is, the message Connected Successfully and the Update From Remote button are displayed in the upper area.
Tip Network Management Console maintains a copy of each services configuration in a RAM cache on the local PC and a copy on disk where the service is running, which could be a remote PC but could be the local PC. The Update From Remote button can be used to replace the cached configuration information with the configuration information from the file. Think of it as Update From File.
56
025-9575B
Note
The connection message relates only to the Network Management Consoles connection with the service, for configuration purposes. It has nothing to do with the services connection to the switches.
To modify an Event Processor connection
1. Select the services name in the list of Events Processor. 2. If you want to use the configuration information for the service as it is saved in the configuration file (or perhaps you just want to see whether there are any differences between it and the cached configuration information), click Update From Remote. 3. If you clicked Update From Remote in the previous step but then decide to start with the cached configuration, click Cancel. 4. The Queue Consumer area contains the location where the queue for the related events is installed. This must match the reporter type defined for the event collection connection. If this Event Processor is to receive alarm event messages from a queue, select Report Alarms. If it is to receive call event messages, select Report MIS Events.
Note Only one Event Processor can be implemented to draw from each message queue.
5. In the Host field for each of those event message categories that are to be received through this input, specify the PC Name for the machine that is hosting the instance of MSMQ that will be managing the event message queue. (Typically this will be the PC Name for the NMS host machine.) You may leave this field blank, and the system will assume localhost. 6. The Reporters area lists this services outputs, which are optional. (The Event Processor also outputs to an SQL database, but that is not configurable here; the database is specified during installation of the Event Processor service.) Under TCP, specify the TCP port(s) on this services host PC, through which other functions should connect to retrieve data, as follows: CDR Reporter Listen Port The port through which the CDR Distributor service should connect. This must match the Port field for the associated CDR Distributor service, on the CDR Distributor tab. This port is also used with the Diagnostic Viewer to monitor Processor CDR activity. Alarm Reporter Listen Port The port through which the Diagnostic Viewer should connect. This must match the Port field on the Diagnostic Viewer screen. This port is also used by the Diagnostic Viewer to monitor processor fault activity. 7. Click Apply unless you only want to save the new or modified configuration without actually applying it to the service at this time. 8. Click Save or Cancel.
57
Clicking Save adds or modifies the services entry in the cached configuration. You will be prompted as to whether you want to also update the information in the configuration file. If you click Yes, the information will be saved to both the cache and the file. If you click No, it will be saved in the cache only. Once saved, the service will be restarted automatically to activate your changes. If you have not clicked Apply, you will be prompted as to whether you want to save the configuration without applying it. Click Yes to save without applying, No to return to editing. Clicking Cancel discards the new entry or any changes you have made since the last save. No changes are made to either the cached configuration or the configuration file, either local or remote.
To delete an Event Processor service
Note Deleting the processor service in the NMS Management Console does not remove the Windows service from the computer.
1. Select the services name in the list of Events Processor Services. 2. Click Remove. 3. Click Save or Cancel. Clicking Save deletes the services entry from the cached configuration. You will not be prompted for confirmation. No changes are made to the configuration file. Clicking Cancel cancels the deletion. No changes are made to either the cached configuration or the configuration file, either local or remote.
Event Collector Services

The Collector tab displays the configuration information for all NMS Event Collector connections. If any Event Collector connections have been configured, they are listed in the upper area. The Event Collector service connects to the Acom system via serial or TCP/IP to collect events and store them in the MS Message Queue and other reporters.
Note Typically there is only one Event Collector service, which connects to as many Acom Systems as is required.
To add an Event Collector connection
PREREQUISITES: Install the Event Collector module (see Installing NMS Components and Related Software on page 19). Define the site (see Defining Sites on page 32). 1. Click New.
58 025-9575B
2. Specify a Name. This is expected to be a user-friendly term by which users will recognize this service. It can be up to 50 alphanumeric characters. Spaces are permitted. It will not be used in any event records. It must be unique among the entries in the list of Events Collector Services. 3. Specify the IP address of the PC hosting this service. 4. Specify the number of the host PCs TCP Port through which Network Management Console should connect to this service for configuration purposes. 5. Click Apply. Network Management Console attempts to connect to the IP address and port you have specified, to see if there is an Event Collector service running there. If there is not, the message Connection failed is displayed in the upper area. Verify that the Event Collector module is installed and that the correct IP address and port are specified. If there is, the message Connected Successfully and the Update From Remote button are displayed in the upper area.
Note
To modify an Event Collector connection
1. Select the services name in the list of Events Collector Services. 2. If you want to use the configuration information for the service as it is saved in the configuration file (or perhaps you just want to see whether there are any differences between it and the cached configuration information), click Update From Remote. 3. If you clicked Update From Remote in the previous step but then decide to start with the cached configuration, click Cancel. 4. The System Connections area lists this services inputs from the various Acom switches and shows the connection configuration for each. See To add or modify an Event Collector service input (System Connection) on page 60 or To delete an Event Collector service input (System Connection) on page 62. 5. The Reporters area lists this services outputs and shows the connection configuration for each. See the procedure To add or modify an Event Collector service output (Reporter) on page 62 or To delete an Event Collector service output (Reporter) on page 63.
59
To add or modify an Event Collector service input (System Connection)
PREREQUISITE: This procedure is a continuation from step 3 of To modify an Event Collector connection on page 59.
Note If the Acom system has two ADSes, you can define two system connections. Then if one connection fails, the other will take over. Any two ADSes can be used; it does not have to be a Main/Standby system.
1. If this is an existing input, select its name in the list of System Connections. or If this is a new input, click New in the middle area. Some fields in the area will become populated with default values if applicable. 2. Specify a Name in the middle area. This is expected to be a user-friendly term by which users will recognize this input. It can be up to 50 alphanumeric characters. Spaces are permitted. It will not be used in any event records. It must be unique among the entries in the list of System Connections. 3. Specify the system and site from which the input comes. Select from the System/ Site drop-down list. (The System Type is derived automatically from the System/
60
025-9575B
Site entry and cannot be edited.) The System Type must be Acom to communicate with an Acom DS3 Subrack (ADS). This is set in the System Setup tab of the Configure Services menu. 4. Specify the Transport type of the input connection. Select from the drop-down list. a. If TCP is selected, the IP area will become available for editing. Specify the IP address of the device providing the input and the TCP Port on that device, through which this service connects. For Acom ADS the IP Address of a DCU is used and the port number must be 5000. b. If Serial is selected, the Serial area will become available for editing. Specify the communication parameters (Port Name, Baud Rate, Data Bits, Parity, Stop Bits, and Hand Shake) for the serial port through which this service will receive data from this input. These will depend on the sending device. Select from the drop-down lists. Connect from the COM port on the Event Collector host to the Acom switch, as follows: Acom DS3 Subrack (ADS): Connect to the left RJ45 port on J8 on the DCU card. Use a Zetron P/N 709-7615-xxx cable. 1 Acom Optical Switch (AOS): Connect to the port labeled MGT PORT on the rear of the unit. Use a Zetron P/N 709-7614-xxx cable. 1
Caution!
If you change the configuration from one communication type to the other, all of the end-point connection information (shown in the middle area) will be deleted. For example, changing from serial to TCP transport, the serial communication parameters will be deleted, and you will need to add a network devices IP address and TCP port number.
5. Under Event Filters, specify the event categories that this service will receive through this input. For fault events, select Alarm. For call events, select MIS Events, and then select the categories of call events to receive: Radio, Telephone, and/or ACD (Automatic Call Distribution, call queues and such). 6. Click Apply unless you only want to save the new or modified configuration without actually applying it to the service at this time. 7. Click Save or Cancel. Clicking Save adds or modifies the services entry in the cached configuration. You will be prompted as to whether you want to also update the information in the configuration file. If you click Yes, the information will be saved to both the cache and the file. If you click No, it will be saved in the cache only. If you have not clicked Apply, you will be prompted as to whether you want to save the configuration without applying it. Click Yes to save without applying, No to return to editing.
1. xxx is the cable length, in feet. Specify length when ordering.

61
Clicking Cancel discards the new entry or any changes you have made since the last save. No changes are made to either the cached configuration or the configuration file, either local or remote.
To delete an Event Collector service input (System Connection)
1. Select the services name in the list of Events Collector Services. 2. Select the inputs name in the list of System Connections. 3. Click Remove in the middle area. 4. Click Save or Cancel. Clicking Save deletes the inputs entry from the cached configuration. You will not be prompted for confirmation. No changes are made to the configuration file. Clicking Cancel cancels the deletion. No changes are made to either the cached configuration or the configuration file, either local or remote.
To add or modify an Event Collector service output (Reporter)
Note The MSMQ reporter is required to report events to the Message Queue.
PREREQUISITE: This procedure is a continuation from step 3 of To modify an Event Collector connection on page 59. 1. If this is an existing output, select its name in the list of Reporters. or If this is a new output, click New in the lower area. Some fields in the area will become populated with default values if applicable. 2. Specify a Name in the lower area. This is expected to be a user-friendly term by which users will recognize this output. It can be up to 50 alphanumeric characters. Spaces are permitted. It will not be used in any event records. It must be unique among the entries in the list of Reporters. 3. If alarm events are to be reported through this output, select Report Alarms. If call events are to be reported through this output, select Report MIS Events. 4. Specify the Reporter Type. Select from the drop-down list. If MSMQ is selected (which must be the case for at least one output if event messages are to be sent to an Event Processor), the fields below Report Alarms and Report MIS Events will be labeled Host. For each of those event categories that are to be reported through this output, specify the PC Name of the machine that is hosting the instance of MSMQ you want to use to queue the event messages for the Event Processor. You may leave the Host fields blank, and the system will assume localhost. (Typically the name will be the NMS host PC name.) You must
62
025-9575B
define an MSMQ reporter for the processor service to use. If using one Collector service, you should consume both alarms and MIS events from the MSMQ.
Note The File reporter is not hard coded. Collector messages are archived to disk C:\Program Files\Zetron\NMS\Collector Service\Logs as AlarmsFromXXX [date time].txt and CallsFromXXX [date time].txt.
5. Click Apply unless you only want to save the new or modified configuration without actually applying it to the service at this time. 6. Click Save or Cancel. Clicking Save adds or modifies the services entry in the cached configuration. You will be prompted as to whether you want to also update the information in the configuration file. If you click Yes, the information will be saved to both the cache and the file. If you click No, it will be saved in the cache only. If you have not clicked Apply, you will be prompted as to whether you want to save the configuration without applying it. Click Yes to save without applying, No to return to editing. Clicking Cancel discards the new entry or any changes you have made since the last save. No changes are made to either the cached configuration or the configuration file, either local or remote.
To delete an Event Collector service output (Reporter)
1. Select the services name in the list of Events Collector Services. 2. Select the outputs name in the list of Reporters. 3. Click Remove in the lower area. 4. Click Save or Cancel. Clicking Save deletes the outputs entry from the cached configuration. You will not be prompted for confirmation. No changes are made to the configuration file. Clicking Cancel cancels the deletion. No changes are made to either the cached configuration or the configuration file, either local or remote.
To delete an Event Collector service
1. Select the services name in the list of Events Collector Services. 2. Click Remove in the upper area. 3. Click Save or Cancel. Clicking Save deletes the services entry from the cached configuration. You will not be prompted for confirmation. No changes are made to the configuration file. Clicking Cancel cancels the deletion. No changes are made to either the cached configuration or the configuration file, either local or remote.
63
CDR Distributor Services
Note
This is optional.
A CDR Distributor can receive completed call detail records (not individual call event messages) from an Event Processor and pass them on to downstream devices or services such as a serial CDR printer. The CDR Distributor tab displays the configuration information for all NMS CDR Distributors. If any CDR Distributors have been configured, they are listed in the upper area.
To add a CDR Distributor service
PREREQUISITE: Install the CDR Distributor module (see Installing NMS Components and Related Software on page 19). 1. Click New. 2. Specify a Name. This is expected to be a user-friendly term by which users will recognize this service. It can be up to 50 alphanumeric characters. Spaces are
64
025-9575B
CDR Distributor Services
permitted. It will not be used in any event records. It must be unique among the entries in the list of Events CDR Distributor Services. 3. Specify the IP address of the PC hosting this service. 4. Specify the number of the host PCs TCP Port through which Network Management Console should connect to this service for configuration purposes. 5. Click Apply. Network Management Console attempts to connect to the IP address and port you have specified, to see if there is a CDR Distributor service running there. If there is not, the message Connection failed is displayed in the upper area. Verify that the CDR Distributor module is installed and that the correct IP address and port are specified. If there is, the message Connected Successfully and the Update From Remote button are displayed in the upper area. This now becomes a matter of modifying the service. Go to the following procedure.
Note
To modify a CDR Distributor service
1. Select the services name in the list of Events CDR Distributor Services. 2. If you want to use the configuration information for the service as it is saved in the configuration file (or perhaps you just want to see whether there are any differences between it and the cached configuration information), click Update From Remote. 3. If you clicked Update From Remote in the previous step but then decide to start with the cached configuration, click Cancel. 4. Under System Connections, enter the input connection information for this CDR Distributor service: a. In the Processor IP field, specify the IP address of the PC hosting the Event Processor that will send data to this service. b. In the Port field, specify the TCP port on that host, through which this service will connect to the Event Processor service. This must match the CDR Reporter Listen Port field for the associated Event Processor service, on the Processor tab. 5. Optional: The CDR Output To area lists outputs to which this CDR Distributor could send CDRs to one or more devices or services that can connect to it. It could
65
output to a TCP port and/or one or more serial ports. It is left to the customer to provide, if desired, a device or service that can retrieve data from the specified port. a. TCP/IP Listen Port would be the number of a TCP port on this CDR Distributors host PC. An example usage would be to accommodate a Microsoft HyperTerminal connection from a remote PC. b. Serial Connections can list one or more serial port connection configurations. An example usage would be printing to a serial printer. To add or modify a serial port connection configuration, see To add or modify a CDR Distributor serial connection on page 66 or To delete a CDR Distributor serial connection on page 67. 6. Click Apply in the lower area unless you only want to save the new or modified configuration without actually applying it to the service at this time. 7. Click Save or Cancel. Clicking Save adds or modifies the services entry in the cached configuration. You will be prompted as to whether you want to also update the information in the configuration file. If you click Yes, the information will be saved to both the cache and the file. If you click No, it will be saved in the cache only. If you have not clicked Apply, you will be prompted as to whether you want to save the configuration without applying it. Click Yes to save without applying, No to return to editing. Clicking Cancel discards the new entry or any changes you have made since the last save. No changes are made to either the cached configuration or the configuration file, either local or remote.
To add or modify a CDR Distributor serial connection
PREREQUISITE: This procedure is a continuation from step 5 of To modify a CDR Distributor service on page 65. 1. If this is an existing output, select its name in the list of Serial Connections. or If this is a new output, click New in the lower area. Some fields in the area will become populated with default values if applicable. 2. Specify a Name in the lower area. This is expected to be a user-friendly term by which users will recognize this output. It can be up to 50 alphanumeric characters. Spaces are permitted. It will not be used in any event records. It must be unique among the entries in the list of Serial Connections. 3. Specify the communication parameters (Port Name, Baud Rate, Data Bits, Parity, Stop Bits, and Hand Shake) for this serial port configuration. These will depend on the receiving device or service. Select from the drop-down lists. 4. Click Apply in the lower area unless you only want to save the new or modified configuration without actually applying it to the service at this time. 5. Click Save or Cancel. Clicking Save adds or modifies the services entry in the cached configuration. You will be prompted as to whether you want to also update the information in
66 025-9575B
Service Configuration Files
the configuration file. If you click Yes, the information will be saved to both the cache and the file. If you click No, it will be saved in the cache only. If you have not clicked Apply, you will be prompted as to whether you want to save the configuration without applying it. Click Yes to save without applying, No to return to editing. Clicking Cancel discards the new entry or any changes you have made since the last save. No changes are made to either the cached configuration or the configuration file, either local or remote.
To delete a CDR Distributor serial connection
1. Select the configurations name in the list of Serial Connections. 2. Click Remove in the lower area. 3. Select the services name in the list of Events CDR Distributor Services. 4. Select the outputs name in the list of Serial Connections. 5. Click Remove in the lower area. 6. Click Save or Cancel. Clicking Save deletes the connections entry from the cached configuration. You will not be prompted for confirmation. No changes are made to the configuration file. Clicking Cancel cancels the deletion. No changes are made to either the cached configuration or the configuration file, either local or remote.
To delete a CDR Distributor service
1. Select the services name in the list of Events CDR Distributor Services. 2. Click Remove in the lower area. 3. Click Save or Cancel. Clicking Save deletes the services entry from the cached configuration. You will not be prompted for confirmation. No changes are made to the configuration file. Clicking Cancel cancels the deletion. No changes are made to either the cached configuration or the configuration file, either local or remote.
Service Configuration Files

Each computer configured to run an Event Collector or Event Processor service will store a local copy of the necessary configuration file(s). One file will contain all of the configuration information for every Event Collector service connection that is to be established by the computer. Another file will contain all of the configuration information for every Event Processor service connection that is to be established by the computer. These files are in XML format.
67
When a service starts up, it loads its configuration information from the appropriate file. If the file is not found, the service will create a default one. You should maintain a backup of these configuration files as a standard precaution. If NMS is uninstalled or upgraded to a newer version, the configuration files will not be deleted or overwritten. The service configuration files are written and maintained by way of Network Management Console. They are not intended to be edited manually, and this is not supported, except to enable or disable the dependency of NMS on UMS (see Making Network Management Console UMS-enabled on page 21).
Service Logs
The service logs contain general information about the health of the service. If there are any errors or connection problems they will be reported in the service log.
To view the trace log for a service
1. In Windows Explorer, go to the service-specific folder under C:\Program Files\Zetron\NMS. 2. Open the Logs sub-folder for the service. 3. Double-click the trace log file name.
Service Event Processor Event Collector CDR Distributor Service-specific Folder
Zetron EventsProcessorService Zetron EventsCollectorService Zetron CDRDistributor
Trace Log File Name

processor_trace.log collector_trace.log CDR_Distributor_trace.log
68
025-9575B
Viewing Alarm Events in Real Time
Viewing Active Alarm Events
Alarm events can be viewed in real-time, and the alarm event records database can be queried to display alarm event history.
Note In the event of a network disconnection from the database, Network Management Console will need to be restarted.
Viewing Alarm Events in Real Time

Select Event Viewer. This area displays all alarm event records in the database, for which the alarm event type was flagged for monitoring (see Specifying Alarm Events to Monitor on page 41), and for which the Status is Active. The display will refresh automatically after the number of seconds you specify in the Refresh interval field. You can refresh it manually by clicking Refresh Now. Alarm event record fields displayed are as follows:
Field Date Time Description Local date and time, in the format used by the PC when the event occurred. See the Windows Control Panel Regional Options (under Windows 2000) or Regional and Language Options (under Windows XP). The Short date format is used by NMS. Note: NMS assumes that the timestamps on received event messages are in GMT, and it stores them in the database without changing the timestamp. (Be sure the GMT Offset is set in Acom IMS ALS.) But events are displayed in the Event Viewer with the time shown as per the local time zone as set on the PC. If you change the time zone on the PC, you must restart Network Management Console. Alarm Alarm code. For a list of supported alarms, see Device Alarm Codes on page 75.
69
Field Site System Device Address Severity Event Description Status Comment
Description The site at which the alarm occurred, as defined under Configure Services, System Setup tab. The system in which the alarm occurred, as defined under Configure Services, System Setup tab. The device in which the alarm occurred, as defined under Manage Devices. Network address of the device, as defined under Manage Devices. Status of the alarm, as defined under Configure Services, System Type Definition tab, Alarm event severity codes. The Description of the alarm event type, as defined under Configure Services, System Type Definition tab, Alarm event type codes. Status of the alarm, as defined under Configure Services, System Type Definition tab, Alarm event status codes. This column is used for annotating scheduled maintenance items or other notes.
The list can be sorted by any column by clicking the column heading. To sort in reverse order, click the heading again. Columns can be resized by dragging the heading dividers. The Windows-standard column resizer also works (hold down the Ctrl key while pressing
70
025-9575B
Viewing Alarm Event History
+ on the numeric keypad). Network Management Console will remember the sort order between sessions.
To clear alarms manually
Though it should seldom be desired to do so, you can clear one or more alarms manually. It is possible that the Collector missed the Alarm inactive message if the message was sent before the device was in communications with NMS. You can check the alarm status using the Zetron Information Management System (IMS) to confirm alarms are safe to delete/ignore. 1. In the Active Event Viewer window, click anywhere in the line representing the record of the alarm you want to delete. 2. To clear more than one alarm at once, use the Shift or Ctrl key to select multiple lines. 3. Click Clear Selected Alarms.
Tip Individual alarms may be cleared by selecting the Status field for that alarm and manually changing the value.

You can generate an alarm event history report based on any of the fields displayed in the Active Event Viewer window. To display the query dialog screen, select Event Viewer, then click Query. Initially this window will be blank, until you specify the query criteria and click the Query button. You can get some troubleshooting information about faults/ alarms from the Acom System Maintenance manual (Zetron part number 025-9574).
71
Figure 2: Event Query window
To generate an alarm event history report
1. In the Event Query window, select any combination of the search criteria shown. These represent the database record fields described in the preceding table. For Date/Time Range, select a date from the drop-down calendar. The time that the Event Query window was opened is inserted by default. Edit the time fields as necessary, by clicking in them and typing new values. If you wish to include all alarm events (even though you have unmonitored some of them), set the Include Unmonitored Alarms check box. 2. Click Query. The alarm events that match the search criteria will be displayed in the list at the top of the Event Query window. The list can be sorted by any column by clicking the column heading. To sort in reverse order, click the heading again. Columns can be resized by dragging the heading dividers. The Windows-standard method for resizing a column also works (hold down the Ctrl key while pressing + on the numeric keypad).
To view a formatted version of the report
1. Click Report to send the query results to the Event Query Report window, which then displays a formatted, printable version of the report.
72
025-9575B
Figure 3: Event Query Report window
2. To close the window, press Alt+F4 or click the X in the top right corner of the window.
To print the formatted report
1. View the formatted report in the Event Query Report window. 2. Click the Print Report icon. You will be prompted to select a printer.
To save the formatted report in a file
1. View the formatted report in the Event Query Report window. 2. Click the Export Report icon. displayed. The Export Report dialog box will be
3. In the Save as type drop-down list, select one of the following formats: Crystal Reports (*.rpt), for importing into Business Objects Crystal Reports. For information on Crystal Reports, visit businessojects.com. Adobe Acrobat (*.pdf), Portable Document Format, for importing into Adobe Acrobat or any PDF reader. Microsoft Excel (*.xls), spreadsheet format with some formatting, for importing into Microsoft Excel. Microsoft Excel Data Only (*.xls), spreadsheet format with no formatting (one record per line), for importing into Microsoft Excel. Microsoft Word (*.doc), document format, for importing into Microsoft Word.
73
Rich Text Format (*.rtf), Rich Text Format, for importing into any RTF reader. 4. In the File name field, type a name for report file. 5. Click OK. When the file is saved, the message Export completed will be displayed.
74
025-9575B
Device Alarm Codes
This chapter lists all of the fault alarm codes for every supported device, sorted by Device Type Code and then by Alarm Code. Further description of the device types can be found in Network Management Console under Configure Services, on the System Type Definition tab, by selecting Zetron device type codes from the Name drop-down list.
Device Type Code and Description ACOM_ACU (Acom Console Unit) Alarm Code 0 1 2 1100 1110 1120 1130 1140 1230 1240 1260 1280 1320 1321 1322 1323 1324 1325 1326 1327 1328 Alarm Description Unknown system alarm System OK System Dead Configuration alarm Configuration alarm - missing card Configuration alarm - extra card Configuration alarm - version mismatch Configuration alarm - different card Test alarm PCMUX alarm Realtime clock alarm Alarm Acked ACU user alarm 1 ACU user alarm 2 ACU user alarm 3 ACU user alarm 4 ACU user alarm 5 ACU user alarm 6 ACU user alarm 7 ACU user alarm 8 ACU user alarm 9 Default Severity 5 5 1 2 2 2 2 2 5 2 2 5 5 5 5 5 5 5 5 5 5
75
Device Alarm Codes
Device Type Code and Description ACOM_ACU (Acom Console Unit) (continued)
Alarm Code 1329 1350 1351 1352 1353 1354 1355 1690 1750 1760
Alarm Description ACU user alarm 10 ACU input alarm 1 ACU input alarm 2 ACU input alarm 3 ACU input alarm 4 ACU input alarm 5 ACU input alarm 6 MUSAC alarm FLEX alarm DSP alarm Unknown system alarm System dead ACU codec alarm ACU codec muted alarm Unknown system alarm System dead ACU codec alarm ACU codec muted alarm Unknown system alarm System dead ACU codec alarm ACU codec muted alarm Unknown system alarm System dead ACU device read alarm ACU device write alarm ACU device calibration alarm ACU device communication alarm Unknown system alarm System dead Unknown system alarm System dead No signal alarm Loss of sync alarm Alarm indication signal Receive remote alarm SLIP alarm
Default Severity 5 5 5 5 5 5 5 2 2 2 5 1 2 2 5 1 2 2 5 1 2 2 5 1 2 2 2 2 5 1 5 1 2 2 2 2 2
ACOM_ACU_4WVF (Acom 4-wire E&M Module)
0 2 4000 4010
ACOM_ACU_BDRM (Acom Basic Dual Radio Module)
0 2 4000 4010
ACOM_ACU_DCOAM (Acom Dual Console Operators Audio Module)
0 2 4000 4010 0 2 4020 4030 4040 4050
ACOM_ACU_DEM (Acom Dual Exchange Module)
ACOM_ACU_DPM (Acom Dual Phone Module) ACOM_ACU_E1 (Acom console interface to E1 loop)
0 2 0 2 2000 2010 2020 2030 2040
76
025-9575B
Device Type Code and Description ACOM_ACU_E1 (Acom console interface to E1 loop) (continued)
Alarm Code 2050 2060 2070 2080 2090 2100
Alarm Description Excessive bit error alarm CRC4 alarm Multiframe alignment alarm Multiframe receive remote alarm Remote alarm 1 Remote alarm 2 Unknown system alarm System dead ACU codec alarm ACU codec muted alarm Unknown system alarm System dead ACU codec alarm ACU codec muted alarm ACU UART overrun alarm ACU UART parity alarm ACU UART framing alarm Unknown system alarm System dead Configuration alarm ADS input alarm 1 ADS input alarm 2 ADS input alarm 3 ADS input alarm 4 ADS input alarm 5 ADS input alarm 6 ADS input alarm 7 ADS input alarm 8 Fiber alarm NVRAM alarm Boot alarm Clock 2M alarm Packet server alarm Packet size alarm Backplane alarm ACU port configuration alarm
Default Severity 2 2 2 2 2 2 5 1 2 2 5 1 2 2 2 2 2 5 1 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
ACOM_ACU_OAM (Acom Operators Audio Module)
0 2 4000 4010
ACOM_ACU_TRM (Acom TETRA Radio Module)
0 2 4000 4010 4060 4070 4080
ACOM_ADS (Acom Digital Switch)
0 2 1100 1360 1361 1362 1363 1364 1365 1366 1367 1630 1640 1650 1660 1710 1720 1810 4090
77
Device Alarm Codes
Device Type Code and Description ACOM_DCU (Acom DS3 Control Unit card)
Alarm Code 0 2 2000 2010 2020 2130 3000 4090
Alarm Description Unknown system alarm System dead No signal alarm Loss of sync alarm Alarm indication signal Failure alarm Fiber wrap alarm ACU port configuration alarm Unknown system alarm System dead Unknown system alarm System dead No signal alarm Alarm indication signal SLIP alarm Unknown system alarm System dead No signal alarm SLIP alarm Clock alarm HDLC alarm Unknown system alarm System dead Unknown system alarm System dead EIU Packet Memory Exhausted alarm EIU Configuration alarm EIU LAN alarm EIU Connected Device alarm EIU Remote alarm Unknown system alarm System dead Unknown system alarm System dead
Default Severity 5 1 2 2 2 2 2 2 5 1 5 1 2 2 2 5 1 2 2 2 2 5 1 5 1 2 2 2 2 2 5 1 5 1
ACOM_DIU (Acom Data Interface Unit card) ACOM_DIU3 (Acom Data Interface Unit 3 card)
0 2 0 2 2000 2020 2040
ACOM_DIU4 (Acom Data Interface Unit 4 card)
0 2 2000 2040 2110 2120
ACOM_EIE (Acom Exchange Interface Equipment card) Acom_EIU (Acom Ethernet Interface Unit)
0 2 0 2 2300 2301 2302 2304 2305
ACOM_EMU (Acom Ear and Mouth (E&M) Unit card) ACOM_ISDN (Integrated Services Digital Network interface)
0 2 0 2
78
025-9575B
Device Type Code and Description ACOM_LR (Acom Optical Switch)
Alarm Code 0 2 1610 1620 1630 1700 1710 1720 1730 1740 2000 2010 2020 2030 2070 2080 2090 2100 3000
Alarm Description Unknown system alarm System dead LCB missing alarm LCB is backup device alarm Fiber alarm MSC alarm Packet server alarm Packet size alarm BSYNC server alarm NMS alarm No signal alarm Loss of sync alarm Alarm indication signal Receive remote alarm Multiframe alignment alarm Multiframe receive remote alarm Remote alarm 1 Remote alarm 2 Fiber wrap alarm Unknown system alarm System OK System dead Configuration alarm Configuration alarm - missing card Configuration alarm - extra card Configuration alarm - version mismatch Configuration alarm - different card Self test alarm Ringer alarm Test alarm PCMUX alarm Realtime clock alarm External realtime clock alarm Alarm Acked ALS user alarm 1 ALS user alarm 2 ALS user alarm 3
Default Severity 5 1 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 5 5 1 2 2 2 2 2 2 2 5 2 2 2 5 5 5 5
ACOM_LSR (Acom Line Subrack)
0 1 2 1100 1110 1120 1130 1140 1200 1210 1230 1240 1260 1270 1280 1290 1291 1292
79
Device Alarm Codes
Device Type Code and Description ACOM_LSR (Acom Line Subrack) (continued)
Alarm Code 1293 1296 1297 1298 1299 1300 1301 1340 1341 1342 1343 1344 1345 1500 1510 1520 1530 1540 1550 1560 1580 1600 1660 1670 1680 1690 1750 1800
Alarm Description ALS user alarm 4 ALS user alarm 7 ALS user alarm 8 ALS user alarm 9 ALS user alarm 10 ALS user alarm 11 ALS user alarm 12 MSU input alarm 1 MSU input alarm 2 MSU input alarm 3 MSU input alarm 4 MSU input alarm 5 MSU input alarm 6 Line alarm Line connection alarm EIE voltage loss alarm Line console request alarm Line disabled alarm Line test alarm Line detector failure alarm Line invalid state alarm LCB alarm Clock 2M alarm Epic error alarm Epic loss of sync alarm MUSAC alarm FLEX alarm ALS alarm
Default Severity 5 5 5 5 5 5 5 5 5 5 5 5 5 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
80
025-9575B
Device Type Code and Description ACOM_MCU (Acom Main Control Unit card)
Alarm Code 0 2 1600 1610 1620 1710 2000 2010 2020 2030 2040 2050 2060 2070 2080 2090 2100
Alarm Description Unknown system alarm System dead LCB alarm LCB missing alarm LCB is backup device alarm Packet server alarm No signal alarm Loss of sync alarm Alarm indication signal Receive remote alarm SLIP alarm Excessive bit error alarm CRC4 alarm Multi frame alignment alarm Multi frame receive remote alarm Remote alarm 1 Remote alarm 2 Unknown system alarm System dead Unknown system alarm System dead Unknown system alarm System dead SMU ping alarm SMU LAN alarm SMU alarm Unknown system alarm System dead Unknown system alarm System dead Unknown system alarm System dead IMS Event Collector communication alarm
Default Severity 5 1 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 5 1 5 1 5 1 2 2 2 5 1 5 1 5 1 1
ACOM_MSU (Acom Main Supply Unit card) ACOM_RVA (Acom Recorded Voice Announcement card) ACOM_SMU (Acom Signaling Management Unit card)
0 2 0 2 0 2 1900 1910 1920
ACOM_TIE (Acom Telephone Interface Equipment card) ACOM_UIO (Acom Universal Input/Output card) IMS_FAULT_COLLECTOR (NMS Alarm Event Collector service)
0 2 0 2 0 2 5000
81
Device Alarm Codes
Device Type Code and Description IMS_FAULT_POST (NMS Alarm Event Processor service)
Alarm Code 0 2 5010
Alarm Description Unknown system alarm System dead IMS Event Processor communication alarm Unknown system alarm System dead Unknown system alarm System dead Unknown system alarm System dead IMS general exception alarm Unknown system alarm System dead
Default Severity 5 1 1 5 1 5 1 5 1 1 5 1
IMS_MIS_COLLECTOR (NMS Call Detail Event Collector service) IMS_MIS_POST (NMS Call Detail Record Distributor service) IMS_SERVICE (NMS core)
0 2 0 2 0 2 5020 0 2
UNKNOWN (unknown device type)
82
025-9575B
Overview
MIS Database Views
Overview
This chapter describes the set of database views that Zetron has defined for looking at the call detail records in an NMS database. These views enable users to produce custom MIS reports related to call and operator activity. The views can be accessed by way of thirdparty reporting tools that are able to connect to the NMS database and query it using SQL query statements. This chapter is intended only to describe the data that is available through use of the views and to provide a minimal set of SQL query statement examples showing how the data can be queried using the views.
83
MIS Database Views
Glossary
The following table contains a list of terms and abbreviations that are used in this chapter.
Term Abandoned Call Call Duration Call Event Channel CLI Line NMS PTT Receive (Rx) Talk Time Transmit (Tx) Definition An incoming phone call that disconnected prior to any console operator answering the call The entire span of time of a call, from its initial detection by the communication switch to its termination by either the caller or the console operator An individual message sent from a communication switch, describing an activity that has occurred within the system A band of radio frequencies of sufficient width to support a single radio communication path Calling Line Identification A single phone circuit interface that connects a Zetron communication system with another exchange Zetron's Network Management System Push To Talk For radio type calls, the receipt within a Zetron communication switch of a radio call from a mobile subscriber The elapsed time that a calling party spent communicating with a console operator For radio type calls, the assertion of PTT from a Zetron operator console
84
025-9575B
View Details
View Details
Abandoned Calls (VR_AbandonedCalls)
Provides a detailed list of missed inbound calls (Abandoned, that is, the caller hung-up before they were answered).
Column Name Device Category CLI CND EventStartTime EventEndTime Duration DurationSeconds Priority Area TrunkGroup Site System SystemTrunkGroup Description Device number from communications switch based on Category. Line number for Radio or Telephone. T = Telephone, Q = ACD Queue, A = ACD Area, R = Radio Caller number reported for in-bound telephone calls; for outbound calls this represents the number that was dialed. Called number received for inbound phone calls Time and date when call was recognized within the communications switch as an active call. Includes a TZ offset in SQL2008. Time and date when call was terminated within the communications switch. Includes a TZ offset in SQL2008. Total ringing time in hh:mm:ss. Total ringing time in seconds. Line configured priority from NMS DB ACD Area if Category = Q. The Area is determined by a calling number lookup. TrunkGroup (line grouping) from NMS database. Customer defined title of the communication site reporting the event. Customer defined title of the communication switch reporting the event. ISDN trunk group attached to the call
85
MIS Database Views
ACD Queue Attachments (VR_AcdQueueAttachments)

Real-time Queue status of ACD agents.
Column Name Console Queue AcdSession StartDtTm EndDtTm Duration DurationSeconds Site SiteID System SystemID The ACD Queue ID. The ACD Session ID. See VR_AcdSessions. Time and date console was attached to the queue. Time and date console was unattached from the queue. Total elapsed time in hh:mm:ss. Total elapsed time in seconds. Customer defined title of the communication site reporting the event. Internal ID from NMS database. Customer defined title of the communication switch reporting the event. Internal ID from NMS database. Description Console address from communications switch.
86
025-9575B
View Details
ACD Session Details (VR_AcdSessionDetails)

ACD session status changes (agent events). A new record is created for each change in Status, WalkawayCode or CallHeld flag.
Column Name Console AcdSession StartDtTm EndDtTm Duration Status CallHeld OnCall Supervisor LogonName FirstName LastName DurationSeconds WalkawayCode ConsoleID OperatorID Site SiteID System SystemID Description Console address from communications switch. The ACD Session ID. See VR_AcdSessions. Time and date console was logged in to ACD. Time and date console was logged out of ACD. Session duration in hh:mm:ss. Console login status or walkaway code. Logged On, Logged Off, Overflow Only, Failed to Answer, or walkaway code. Y for call on hold. Y for on a call. Y for supervisor console. Console logon alias. Agent first name. Agent last name. Session duration in seconds. Console login status or walkaway code. 0 = Logged On, 1 = Logged Off, 2 = Overflow Only, 3 = Failed to Answer, or walkaway code 4+ Internal ID from NMS database. Internal ID from NMS database. Customer defined title of the communication site reporting the event. Internal ID from NMS database. Customer defined title of the communication switch reporting the event. Internal ID from NMS database.
87
MIS Database Views
ACD Sessions (VR_AcdSessions)

ACD session summary showing the number of times the operator had each Status (Status = Walkaway code) and the duration spent in each Status.
Column Name Console AcdSession SessionStart SessionEnd Duration Supervisor LogonName FirstName LastName StatusX Description Console address from communications switch. The ACD Session ID. See VR_AcdSessions. Time and date console was logged in to ACD. Time and date console was logged out of ACD. Session duration in hh:mm:ss. Y for supervisor console. Console logon alias. Agent first name. Agent last name. 9 columns, one for each ACD status. Count of the number of times session was set to this status. Status 0 = Logged On, 1 = Logged Off, 2 = Overflow Only, 3 = Failed to Answer, or walkaway code 4+. 9 columns, one for each ACD status. Duration the session was in this status. Status 0 = Logged On, 1 = Logged Off, 2 = Overflow Only, 3 = Failed to Answer, or walkaway code 4+. Session duration in seconds. Internal ID from NMS database. Internal ID from NMS database. Customer defined title of the communication site reporting the event. Internal ID from NMS database. Customer defined title of the communication switch reporting the event. Internal ID from NMS database.
DurationX
DurationSeconds ConsoleID OperatorID Site SiteID System SystemID
88
025-9575B
View Details
ACD Status Changes (VR_AcdStatusChanges)

Agents most recent status and count of status changes such as walkaway codes.
Column Name Console LogonName FirstName LastName Status StartDtTm EndDtTm Duration StatusChanges AcdSession DurationSeconds WalkawayCode ConsoleID OperatorID Site SiteID System SystemID Console logon alias. Agent first name. Agent last name. Console login status or walkaway code. Logged On, Logged Off, Overflow Only, Failed to Answer, or walkaway code. Time and date the status was set. Time and date the status was cleared. Total elapsed time in hh:mm:ss. Count of status changes for this ACD session. The ACD Session ID. See VR_AcdSessions. Total elapsed time in seconds for the session. Console login status or walkaway code. 0 = Logged On, 1 = Logged Off, 2 = Overflow Only, 3 = Failed to Answer, or walkaway code 4+ Internal ID from NMS database. Internal ID from NMS database. Customer defined title of the communication site reporting the event. Internal ID from NMS database. Customer defined title of the communication switch reporting the event. Internal ID from NMS database. Description Console address from communications switch.
Active Call List (VR_ActiveCallList)

A list of active calls.
Column Name AcomID Name ResourceID Category EventTime Number Console CLIType System title Internal ID from NMS database. R = Radio, T = Telephone, A = Area, Q = Queue Time and date the call started. Caller number reported for in-bound telephone calls; for outbound calls this represents the number that was dialed. Console address from communications switch. Description Internal ID from NMS database. Identifies communications system.
89
MIS Database Views
Call Details (VR_CallDetails)

Provides users with a detailed report of all the events that transpired during the course of a call. A call is made up of several call segments, each segment has a start event and an end event. This can be used when creating queries to get all the Call Segment details.
Column Name Device Category Direction CLI PostDialedDigits CND EventStartTime EventEndTime Duration StartEventCD StartEvent EndEventCD EndEvent Console LogonName Priority GroupNumber TrunkGroup Area CallHistoryID DurationSeconds Site SiteID System SystemID DeviceAlias DeviceTypeID DeviceType SessionID ConsoleID OperatorID SystemTrunkGroup Description Device number from communications switch based on Category. Line number for Radio or Telephone. R = Radio, T = Telephone, A = Area, Q = Queue I = Incoming, O = Outgoing Caller number reported for in-bound telephone calls; for outbound calls this represents the number that was dialed. Secondary dial strings separated by semicolons. Called number received for inbound phone calls Time/date of the start event. Includes a TZ offset in SQL2008. Time/date of the end event. End of the call segment. Includes TZ offset in SQL2008. Total elapsed time in hh:mm:ss. Internal ID from NMS database. MIS event that started this call segment. Internal ID from NMS database. MIS event that ended this call segment. Console address from communications switch. Console logon alias. Device priority defined in NMS database. Conference, patch, or working group number TrunkGroup (line grouping) from NMS database. ACD Area if Category = Q. The Area is determined by a calling number lookup. Internal ID from NMS database. Used to link details to call summary. See VR_CallList. Total elapsed time in seconds. Customer defined title of the communication site reporting the event. Internal ID from NMS database. Customer defined title of the communication switch reporting the event. Internal ID from NMS database. Device alias from NMS database. Internal ID from NMS database. Device type title from NMS database. Internal ID from NMS database. Internal ID from NMS database. Internal ID from NMS database. ISDN trunk group attached to the call
90
025-9575B
View Details
Call List (VR_CallList)

Radio and phone calls. Single record for each call. This can be used when creating queries to get all the Call details.
Column Name Device Category Direction CLI PostDialedDigits CND StartTime EndTime Duration Console LogonName Priority TrunkGroup Area CallHistoryID DurationSeconds Site SiteID System SystemID DeviceAlias DeviceTypeID DeviceType SessionID ConsoleID OperatorID SystemTrunkGroup Description Device number from communications switch based on Category. Line number for Radio or Telephone. R = Radio, T = Telephone, A = Area, Q = Queue I = Incoming, O = Outgoing Caller number reported for in-bound telephone calls; for outbound calls this represents the number that was dialed. Secondary dialstrings separated by semicolons. Called number received for inbound phone calls Time and date when call was recognized within the communications switch as an active call. Includes a TZ offset in SQL2008. Time and date when call was terminated within the communications switch. Includes a TZ offset in SQL2008. Total elapsed time in hh:mm:ss. Console address from communications switch. Console logon alias. Device priority defined in NMS database. TrunkGroup (line grouping) from NMS database. ACD Area if Category = Q. The Area is determined by a calling number lookup. Internal ID from NMS database. Used to link details to call summary. See VR_CallDetails. Total elapsed time in seconds. Customer defined title of the communication site reporting the event. Internal ID from NMS database. Customer defined title of the communication switch reporting the event. Internal ID from NMS database. Device alias from NMS database. Internal ID from NMS database. Internal ID from NMS database. Internal ID from NMS database. Internal ID from NMS database. Internal ID from NMS database. ISDN trunk group attached to the call
91
MIS Database Views
Console List (VR_ConsoleList)

List of all known consoles and their current state. This can be used when creating queries to get all the console details.
Column Name Console ConsoleType Alias LastLogon CurrentOperator FirstName LastName Queues AgentStatus ConsoleStatus ConsoleID Site SiteID System SystemID Description Console address from communications switch. Console type from NMS database. Console alias from NMS database. Time and date of last console logon. Console logon alias of current operator. Operator/agent first name. Operator/agent last name. Active ACD queues of this console. Last status update; Logged Off, Logged On, Overflow Only, Failed to Answer, or walkaway code# A = Active, D = Deleted Internal ID from NMS database. Customer defined title of the communication site reporting the event. Internal ID from NMS database. Customer defined title of the communication switch reporting the event. Internal ID from NMS database.
Current ACD Queue Attachments (VR_CurrentAcdQueueAttachments)

Real-time ACD queue attachment status. This can be used when creating queries to get the console attached to a queue or associated with the AcdSession
Column Name Console Queue AcdSession Site SIteID System SystemID ConsoleID The ACD Queue ID. The ACD Session ID. See VR_AcdSessions. Customer defined title of the communication site reporting the event. Internal ID from NMS database. Customer defined title of the communication switch reporting the event. Internal ID from NMS database. Internal ID from NMS database. Description Console address from communications switch.
92
025-9575B
View Details
Current Agent Status (VR_CurrentAgentStatus)

ACD agent real-time status.
Column Name Console LogonName LastAction Status CallHeld OnCall Supervisor FirstName LastName WalkawayCode Site SiteID System SystemID AcdSession AgentId ConsoleID OperatorID Description Console address from communications switch. Console logon alias of current operator/agent. Time and date of last status change. Last status update; Logged Off, Logged On, Overflow Only, Failed to Answer, or walkaway code# Y for call on hold. Y for on a call. Y for supervisor console. Operator/agent first name. Operator/agent last name. Console login status or walkaway code. 0 = Logged On, 1 = Logged Off, 2 = Overflow Only, 3 = Failed to Answer, or walkaway code 4+ Customer defined title of the communication site reporting the event. Internal ID from NMS database. Customer defined title of the communication switch reporting the event. Internal ID from NMS database. The ACD Session ID. See VR_AcdSessions. Internal ID from NMS database. Internal ID from NMS database. Internal ID from NMS database.
93
MIS Database Views
Current Operators (VR_CurrentOperators)

Operator logon status. This can be used when creating queries to get the console/operator details for each Session.
Column Name Console LogonName FirstName LastName LogonDtTm Site SiteID System SystemID SessionID ConsoleID OperatorID Description Console address from communications switch. Console logon alias of current operator. Operator/agent first name. Operator/agent last name. Time and date of last logon event. Customer defined title of the communication site reporting the event. Internal ID from NMS database. Customer defined title of the communication switch reporting the event. Internal ID from NMS database. Internal ID from NMS database. Internal ID from NMS database. Internal ID from NMS database.
94
025-9575B
View Details
Grouped Calls (VR_GroupedCalls)

Call segments for Patch, Conference, and Working Group (global patch) actions.
Column Name GroupNumber GroupType Device Category EventStartTime EventEndTime Duration StartEventCD StartEvent EndEventCD EndEvent Console LogonName DurationSeconds CallHistoryID Site SIteID System SystemID SessionID ConsoleID OperatorID Description Conference, patch, working group number, or alias. Patch, Global Patch, Conference Device number from communications switch based on Category. Line number for Radio or Telephone. T = Telephone, Q = ACD Queue, A = ACD Area, R = Radio Time and date of the start event. Includes a TZ offset in SQL2008. Time and date of the end event. End of the call segment. Includes a TZ offset in SQL2008. Total elapsed time in hh:mm:ss. Internal ID from NMS database. MIS event that started this call segment. Internal ID from NMS database. MIS event that ended this call segment. Console address from communications switch. Console logon alias of current operator. Total elapsed time in seconds. Internal ID from NMS database. Used to link details to call summary. See VR_CallDetails Customer defined title of the communication site reporting the event. Internal ID from NMS database. Customer defined title of the communication switch reporting the event. Internal ID from NMS database. Internal ID from NMS database. Internal ID from NMS database. Internal ID from NMS database.
95
MIS Database Views
Hourly Call Summary (VR_HourlyCallSummary)

One record for each hour with overall statistics for radio and phone calls
Column Name Site System CallTime IncomingCalls OutgoingCalls AcdCalls MissedCalls IncomingPTT OutgoingPTT IncomingDuration OutgoingDuration AcdDuration IncomingPttDuration OutgoingPttDuration AvgPhoneAnswerTime AvgAcdAnswerTime IncomingSeconds OutgoingSeconds AcdSeconds IncomingPttSeconds OutgoingPttSeconds AvgPhoneAnswerSeconds AvgAcdAnswerSeconds Description Customer defined title of the communication site reporting the event. Customer defined title of the communication switch reporting the event. Time and date of hourly summary start time. Count of phone calls into the communications switch. Count of phone calls made from the communications switch. Count of ACD calls into the communications switch. Count of incoming calls that went unanswered. Count of carrier events-incoming radio transmissions. Count of Push To Talk events from the communications switch. Total elapsed time of incoming phone calls in hh:mm:ss. Total elapsed time of outgoing phone calls in hh:mm:ss. Total elapsed time of incoming ACD calls in hh:mm:ss. Total elapsed time incoming carrier events in hh:mm:ss. Total elapsed time of outgoing PTT events in hh:mm:ss. Average ringing time of incoming phone calls in hh:mm:ss. Average ringing time of incoming ACD calls in hh:mm:ss. Total elapsed time of incoming phone calls in seconds. Total elapsed time of outgoing phone calls in seconds. Total elapsed time of incoming ACD calls in seconds. Total elapsed time of incoming CD events in seconds. Total elapsed time of outgoing PTT events in seconds. Average ringing time of incoming phone calls in seconds. Average ringing time of incoming ACD calls in seconds.
96
025-9575B
View Details
Line Last Activity (VR_LineLastActivity)

One record for each line, queue, or area with last call info.
Column Name Line Category Type LastActivity Priority TrunkGroup Alias Status Site System Description Device number from communications switch based on Category. Line number for Radio or Telephone. R = Radio, T = Telephone, A = Area, Q = Queue Device type title from NMS database. Time and date of last event. Device priority defined in NMS database. TrunkGroup (line grouping) from NMS database. Line alias Line status (A = active/enabled) Customer defined title of the communication site reporting the event. Customer defined title of the communication switch reporting the event.
Line List (VR_LineList)

Full line details for each line, queue, or area. This can be used when creating queries to get all the Line details.
Column Name Line Category Type Priority TrunkGroup Alias Status DeviceID TypeID TypeCD Site SiteID System SystemID Description Device number from communications switch based on Category. Line number for Radio or Telephone. R = Radio, T = Telephone, A = Area, Q = Queue Device type title from NMS database. Device priority defined in NMS database. TrunkGroup (line grouping) from NMS database. Line alias Line status (A = active/enabled) Internal ID from NMS database. Internal ID from NMS database. Internal ID from NMS database. Customer defined title of the communication site reporting the event. Internal ID from NMS database. Customer defined title of the communication switch reporting the event. Internal ID from NMS database.
97
MIS Database Views
Non-Call Details (VR_Non-CallDetails)

Line events not associated with a call. Patch, conference, and monitor are examples. This can be used when creating queries to get all the Non-Call Segment details.
Column Name Device Category EventStartTime EventEndTime Duration StartEventCD StartEvent EndEventCD EndEvent TrunkGroup Console LogonName DurationSeconds Site SiteID System SystemID CallSegmentID DeviceAlias DeviceTypeID DeviceType SessionID ConsoleID OperatorID Description Device number from communications switch based on Category. Line number for Radio or Telephone. T = Telephone, Q = ACD Queue, A = ACD Area, R = Radio Time and date of the start event. Includes a TZ offset in SQL2008. Time and date of the end event. End of the call segment. Includes a TZ offset in SQL2008. Total elapsed time in hh:mm:ss. Internal ID from NMS database MIS event that started this call segment. Internal ID from NMS database MIS event that ended this call segment. TrunkGroup (line grouping) from NMS database. Console address from communications switch. Console logon alias of current operator. Total time of call event in seconds. Customer defined title of the communication site reporting the event. Internal ID from NMS database. Customer defined title of the communication switch reporting the event. Internal ID from NMS database. Internal ID from NMS database. See CallSegments table. Device alias from NMS database. Internal ID from NMS database. Device type title from NMS database. Internal ID from NMS database. Internal ID from NMS database. Internal ID from NMS database.
98
025-9575B
View Details
Operator Calls (VR_OperatorCalls)

Sub-set of VR_CallList. Only includes calls that have been associated with a console session. Excludes abandoned calls. This can be used when creating queries to get all the details on Operator calls. The are situations where the call can change consoles so this view just gets the first operator to handle the call so the call count is accurate.
Column Name Device Category Direction CLI PostDialedDigits CND StartTime EndTime Duration Console LogonName Priority TrunkGroup Area CallHistoryID DurationSeconds Site SiteID System SystemID DeviceAlias DeviceTypeID DeviceType SessionID ConsoleID OperatorID SystemTrunkGroup Description Device number from communications switch based on Category. Line number for Radio or Telephone. T = Telephone, Q = ACD Queue, A = ACD Area, R = Radio I = Incoming, O = Outgoing Caller number reported for in-bound telephone calls; for outbound calls this represents the number that was dialed. Secondary dialstrings separated by semicolons. Called number received for inbound phone calls Time and date when call was recognized within the communications switch as an active call. Includes a TZ offset in SQL2008. Time and date when call was terminated within the communications switch. Includes a TZ offset in SQL2008. Total elapsed time in hh:mm:ss. ID of the console position that processed the call. Console logon alias. Device priority defined in NMS database. TrunkGroup (line grouping) from NMS database. ACD Area if Category = Q. The Area is determined by a calling number lookup. Internal ID from NMS database. See CallHistory table. Total time of call in seconds. Customer defined title of the communication site reporting the event. Internal ID from NMS database. Customer defined title of the communication switch reporting the event. Internal ID from NMS database. Device alias from NMS database. Internal ID from NMS database. Device type title from NMS database. Internal ID from NMS database. Internal ID from NMS database. Internal ID from NMS database. ISDN trunk group attached to the call
99
MIS Database Views
Operator List (VR_OperatorList)

One record for each Operator or Agent. This can be used when creating queries to get all the Operator details.
Column Name LogonName FirstName LastName LastLogon CurrentConsole AgentStatus OperatorStatus OperatorID Site SiteID First name of operator/agent. Last name of operator/agent. Time and date of last operator logon. NULL if logged off NULL if not logged in as ACD A = Active record Internal ID from NMS database. Customer defined title of the communication site reporting the event. Internal ID from NMS database. Description Logon name/alias of operator/agent.
Operator Sessions (VR_OperatorSessions)

One record for each console session. A session starts with a Operator logon, and ends with them exiting the program or logging off. This can be used when creating queries to get all the Session details.
Column Name SessionID LogonDtTm LogoffDtTm Duration Status Console LogonName FirstName LastName ConsoleID OperatorID DurationSeconds Site SiteID System SystemID Time and date of session start. Time and date of session end. Session duration in hh:mm:ss. A = Active, I = Inactive Console address from communications switch. Console logon alias. Agent first name. Agent last name. Internal ID from NMS database. Internal ID from NMS database. Session duration in seconds. Customer defined title of the communication site reporting the event. Internal ID from NMS database. Customer defined title of the communication switch reporting the event. Internal ID from NMS database. Description Internal ID from NMS database.
100
025-9575B
View Details
Operator Session Summary (VR_OperatorSessionSummary)

Summary of each Operator Session (i.e. from logon to logoff) giving call counts and duration by type.
Column Name SessionID LogonName FirstName LastName LogonDtTm LogoffDtTm Duration IncomingCalls OutgoingCalls AcdCalls PTTs PhoneDuration AvgAnswerTime PttDuration DurationSeconds PhoneDurationSeconds AvgAnswerSeconds PttDurationSeconds Console OperatorID Site System Console logon alias. Agent first name. Agent last name. Time and date of session start. Time and date of session end. Session duration in hh:mm:ss. Count of incoming phone calls. Count of outgoing phone calls. Count of incoming ACD calls. Count of outgoing PTT events. Total time of telephone use in hh:mm:ss. Average telephone ringing time in hh:mm:ss. Total time of PTT events in hh:mm:ss. Session duration in seconds. Total time of telephone use in seconds. Average ringing time of incoming phone calls. Total time of PTT events in seconds. Console address from communications switch. Internal ID from NMS database. Customer defined title of the communication site reporting the event. Customer defined title of the communication switch reporting the event. Description Internal ID from NMS database.
101
MIS Database Views
Viewing NMS CDR Records with Excel

This section provides a brief overview of how Network Management System (NMS) Call Detail Records (CDR) can be viewed using Microsoft Excel.Once the call data has been imported into Excel, there are a number of options available for manipulating the data. Once a spreadsheet has been created, it can be used over and over again simply by loading it and refreshing the data.
Excel Database Link

The procedure presented here covers setting up a link between the instance of Excel being used to generate reports and the NMS database being queried for call data. The first time you work with Excel to process NMS data you will need to establish this link. In future, this connection can be reused.
Setting up an Excel database link:
1. 1.From the Excel menu bar, choose Data > Import External Data > New Database Query.
2. In the Choose Data Source list box that opens, select the entry <New Data Source> and click OK. 3. In the Create New Data Source dialog that opens, enter the name NMS for the data source and SQL Server for the driver.
Note The preceding step assumes that SQL Server 2003 or SQL Server 2008 is being used to support the NMS database. If a different database server is used, then that service needs to be named as the driver.
102
025-9575B
4. After entering the data source and the driver, click the Connect button. 5. In the SQL Server Login dialog, specify server name and instance name, for example; MaintTerm\SQL2008. You may be able to browse through available servers and instances using the Server pull down list.
6. You can select the Use Trusted Connection option if the SQL server is installed on the local machine. It might work over a network as well if TCP/IP and Named Pipes are enabled and the Windows user or group is authenticated in SQL Server. Otherwise specify a valid Windows or SQL account and password. This feature uses the Shared Memory option enabled in the SQL Server Configuration Manager.
103
MIS Database Views
7. Click the Options button in the SQL Server Login dialog and set the Database to com_zetron_ims. 8. You could get the following error if the Server\instance does not exist or shared memory, Named Pipes, or TCPIP are disabled.
9. To complete the process: a. Click OK to return to the Create New Data Source dialog. b. Click OK to return to the Choose Data Source dialog. c. In the Choose Data Source dialog, select the new NMS database and click OK.
Creating a Query in Excel

When you choose the NMS database connection (created in previous section), Excel will prompt you to use the Query Wizard. You can move tables or views to the right window to add data to your report.
USing the Excel Query Wizard:
1. When the Choose Columns dialog opens, drag database views or tables from the list on the left to the list on the right to create a query. To get started pull the first View to the right by selecting VR_AbandonedCalls and clicking on the > button.
104
025-9575B
2. If you chose to add more than one table, Excel will ask you to connect the tables to show the relationships. If you only pull in a view (predefined views all start with VR_ ) or just pull in one table you will not need to do this. As a matter of practice, foreign keys are named with the ForeignTable_Column to make relationships obvious. 3. You can further filter your results using the Filter Data step or just click Next to continue.
4. You can specify data sorting in the Sort Order step or just continue and use one of the other sort methods provided by Excel.
105
MIS Database Views
5. As a final step select the options to Return Data to MS Office Excel. 6. When prompted drop the data into a new spreadsheet. Rename the sheet according to the View name (VR_AbandonedCalls).
7. Save the Excel file and in the future it can be refreshed to display current data for your configured views/queries. 8. The next time you open the data spreadsheet, select the top left most cell 1A, then open the Data menu and select Refresh Data! Or use the Refresh All button on the Data Toolbar (View > Toolbars > External Data).
106
025-9575B
What is it good for?

Once you have created/run your report, what else can you do? You could edit the query from Excel menu Data > Import External Data > Edit Query. The Choose Columns popup will be shown. You could create automatic filters for each column. This would allow filtering to one type of column result. From Excel choose Data > Filter > Autofilter. In this example you could filter by calls to/from a particular number.
You could filter results by a date range. If you choose (Custom) from the possible AutoFilter, you can create data ranges for the filtering the data.
You can delete any columns you do not want or re-arrange the columns to the order you want.
107
MIS Database Views
You could create totals, count, Min, Max, or Avg aggregates for the data. Use the Tools > Subtotals menu to get started. You could create sub-totals for console or another column. For example: At each change in Console (sorted by console) use the Average function and Add subtotal to column DurationSeconds. This would get you average call duration by console as sub-totals.
You could create a Pivot Table/Chart.
108
025-9575B
Diagnostic Viewer
The Diagnostic Viewer shows in real time all event messages being passed downstream from an Event Processor or any reporter by way of TCP/IP. This can be helpful in verifying that the service is operating correctly.
109
Diagnostic Viewer
To run the Diagnostic Viewer
1. Select Diagnostic Viewer on the main menu. The Diagnostic Viewer screen opens. 2. In the Events Processor field, type the IP address of the PC hosting the Event Processor service or any reporter, from which the messages are to be monitored. This must match the Alarm Reporter Listen Port or CDR Reporter Listen Port field for the associated Event Processor service, under Configure Services, Processor tab. 3. In the Port field, type the number of the TCP port on the above PC that the Event Processor service outputs data to. 4. Click Start Display. 5. Clicking Clear Display clears the window, then starts showing new event messages as they are received. This may be useful for determining whether a certain event is recurring, eliminating the possibility of confusing it with an existing event, or having to scroll through screens of existing events. 6. Click Stop Display to cease getting diagnostic data from the Event Processor.
110
025-9575B
Overview
Purge Utility
Overview
As the system is operated over time, the NMS database of alarms and events can grow to the point where it becomes cumbersome and inefficient to use. A purge utility is provided along with the NMS Management Console that allows the system maintenance technicians to trim away database records that no longer serve any useful purpose. Two approaches to trimming the size of the database are offered: to sort the database by specific event types and delete them wherever found or to simply remove all records prior to a specified date/time. The default tab displayed when the NMS Purge Utility opens is the Alarm tab. This tab provides the filters necessary to search any one of the available NMS databases for very specific record types and ranges. Once the query is complete, you are offered the option of removing the listed records from the database that was searched. The filters offered on the Alarm tab are: Date/Time range Site - System Alarm Alarm Status Event Severity Device Type Network Address The other tab offered by the NMS Purge Utility is the MIS tab. This tab offers only the ability to trim the database based on the date/time stamp of the records. Once a database is selected and a cutoff date entered, the option provided is to delete all records in that database that were made prior to the date specified.
111
Purge Utility
Using the Purge Utility

The NMS Purge Utility is installed at the same time as the NMS Management Console. Unlike the NMS Management Console, the Purge Utility does not get a desktop or Start menu short cut created for it. The executable file is loaded into the same folder as the NMS Management Console. The path to this folder is:
C:\Program Files\Zetron\NMS\Management Console
The file for the NMS Purge Utility is:

NMS.DBPurgeUtility.exe
Filtering by Type
Using the Alarm tab of the purge utility:
1. From the Start menu, select the RUN option. 2. From the Run dialog box, select the Browse function button and browse to the following folder and file:
C:\Program Files\Zetron\NMS\Management Console\NMSDBPurge.exe
3. Select the NMSDBPurge.exe file and then click the Open button in the browser box. 4. When returned to the Run dialog, click the OK button to start the database purge utility. 5. In the dialog box that opens, on the Alarm tab, enter the Network Address for the server to be queried, set the from-to date/time range for the records to be searched,
112 025-9575B
Using the Purge Utility
configure any additional filters you wish to use, and click the Query function button. 6. The record display window will be populated with the results of the search. Use the scroll bar on the right to move through the list. 7. You can use to the Purge button to remove the listed records from the database or the Close button to exit the purge utility without making any changes to the database.
Deleting by Date
Removing the oldest records from the database:
1. From the Start menu, select the RUN option. 2. From the Run dialog box, select the Browse function button and browse to the following folder and file:
C:\Program Files\Zetron\NMS\Management Console\NMSDBPurge.exe
3. Select the NMSDBPurge.exe file and then click the Open button in the browser box. 4. When returned to the Run dialog, click the OK button to start the database purge utility. 5. In the dialog box that opens, select the MIS tab. Enter the name of a database and the cutoff date for the purge. (All records older than the date entered will be purged.) 6. Click the Purge button to remove the records from the database. 7. To exit the program, click the Close button.
113
Purge Utility
114
025-9575B
Index
Index
A
abandoned calls report, 85 ACD queue attachments report, 86 ACD session details report, 87 ACD sessions report, 88 ACD status changes report, 89 Acom firmware, 18 active alarm events, viewing, 69 active call list report, 89 active event viewer, 15 ACU alarm codes, 75 ACU_4WVF, alarm codes, 76 ACU_BDRM, alarm codes, 76 ACU_DCOAM, alarm codes, 76 ACU_DEM, alarm codes, 76 ACU_DPM, alarm codes, 76 ACU_E1, alarm codes, 76 ACU_OAM, alarm codes, 77 ACU_TRM, alarm codes, 77 ADS, alarm codes, 77 alarm codes ACU, 75 ACU_4WVF, 76 ACU_BDRM, 76 ACU_DCOAM, 76 ACU_DEM, 76 ACU_DPM, 76 ACU_E1, 76 ACU_OAM, 77 ACU_TRM, 77 ADS, 77 DCU, 78 DIU, 78 DIU3, 78 DIU4, 78
EIE, 78 EIU, 78 EMU, 78 IMS_FAULT_COLLECTOR, 81 IMS_FAULT_POST, 82 IMS_MIS_COLLECTOR, 82 IMS_MIS_POST, 82 IMS_SERVICE, 82 ISDN, 78 LR, 79 LSR, 79 MCU, 81 MSU, 81 RVA, 81 SMU, 81 TIE, 81 UIO, 81 UNKNOWN, 82
C
call details report, 90 call list report, 91 CDR distributor services, 64 CDR distributors, 15 CDR management, 30 clear alarms manually, 71 collector services event, 58 computer systems, 17 configuration files, services, 67 console list report, 92 creating a query in Excel, 104 Crystal Reports, 18 current ACD queue attachments report, 92
115
Index
current agent status report, 93 current operators report, 94
D
database connections, 20 database reports abandoned calls, 85 ACD queue attachments, 86 ACD session details, 87 ACD sessions, 88 ACD status changes, 89 active call list, 89 call details, 90 call list, 91 console list, 92 current ACD queue attachments, 92 current agent status, 93 current operators, 94 grouped calls, 95 hourly call summary, 96 line last activity, 97 line list, 97 non-call details, 98 operator calls, 99 operator list, 100 operator session summary, 101 operator sessions, 100 database reports using SQL tools, 83 database server and instance, 19 database terms glossary, 84 databases, 15 DCU, alarm codes, 78 defining alarm event severity types, 38 defining alarm event types, 36 defining attributes of the network, 29 defining sites, 32 deleting records by date, 113 device alarm codes, 75 diagnostic viewer, 109 DIU, alarm codes, 78 DIU3, alarm codes, 78 DIU4, alarm codes, 78
event collector services, 58 event collectors, 14 event processor services, 55 event processors, 14 Excel creating a query, 104 database link, 102 using reports, 107 viewing CDR records with, 102
F
fault event management, 29 file formats for reports, 15 filtering by type, purge utility, 112
G
getting started, 13 glossary of database terms, 84 grouped calls report, 95
H
history of alarm events, viewing, 71 hourly call summary report, 96
I
IMS_FAULT_COLLECTOR, alarm codes, 81 IMS_FAULT_POST, alarm codes, 82 IMS_MIS_COLLECTOR, alarm codes, 82 IMS_MIS_POST, alarm codes, 82 IMS_SERVICE, alarm codes, 82 initial configuration, NMS, 26 installing all NMS services and client on single machine, 20 installing CDR distributor, 22 installing event collector, 22 installing event processor, 22 installing MSMQ Windows 7, 23 Windows XP, 22 installing Network Management Console on a machine, 21 installing NMS components and related software, installing SW on database host, 22 ISDN, alarm codes, 78
E
EIE, alarm codes, 78 EIU, alarm codes, 78 EMU, alarm codes, 78
19
116
025-9575B
Index
L
line last activity report, 97 line list report, 97 logs, services, 68 lost shortcut, restoring, 25 LR, alarm codes, 79 LSR, alarm codes, 79
M
making NMS console UMS-enabled, 21 managing communications devices, 48 managing console types, 45 managing consoles, 50 managing network devices, 39 managing NMS collector and processor services, managing operators, 52 managing truk groups, 47 manually clear alarms, 71 MCU, alarm codes, 81 message queues, 14 MIS database views, 83 MSMQ installing under Windows 7, 23 installing under Windows XP, 22 MSU, alarm codes, 81
55
system setup, 34 Network Management Console, 15 installation, 21 making UMS-enabled, 21 network management console, starting, 24 NMS CDR distributors, 15 database host SW install, 22 databases, 15 diagnostic viewer, 109 event collectors, 14 event processors, 14 initial configuration, 26 installing CDR distributor, 22 installing event collector, 22 installing event processor, 22 message queues, 14 system overview, 13 non-call details report, 98
O
operator calls report, 99 operator list report, 100 operator session summary report, 101 operator sessions report, 100 order of software installation, 20 overview, purge utility, 111
N
network, 17 network attributes CDR management, 30 defining alarm event severity types, 38 defining alarm event types, 36 defining sites, 32 fault event management, 29 managing communications devices, 48 managing console types, 45 managing consoles, 50 managing network devices, 39 managing operators, 52 managing trunk groups, 47 specifying alarm events by alarm event type, specifying alarm events by network device, specifying alarm events to monitor, 41
P
processor services event, 55 purge utility delete by date, 113 filtering by type, 112 overview, 111 using, 112
Q
query criteria, 15
R
real time alarm events, viewing, 69 report file formats, 15 restoring a lost shortcut, 25 RVA, alarm codes, 81
43 42
117
Index
S
service configuration files, 67 service logs, 68 shortcut, lost, restoring, 25 SMU, alarm codes, 81 specifying alarm events by alarm event type, 43 specifying alarm events by network device, 42 specifying alarm events to monitor, 41 SQL database, 17 SQL Server 2008, 18 starting network management console, 24 system overview, 13 system requirements Acom firmware, 18 computer systems, 17 network, 17 SQL database, 17 system setup, 34
T
TIE, alarm codes, 81
U
UIO, alarm codes, 81 UNKNOWN, alarm codes, 82 user interface, 15 using Excel reports, 107 using the purge utility, 112
V
viewing alarm events active, 69 history, 71 real time, 69 viewing CDR records with Excel, 102
W
Windows 7 user account control, 19
118
025-9575B

Network Management System Product Manual

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Network Management System Product Manual

Загружено:

Авторское право:

Доступные форматы

Network Management System Product Manual

List of Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Defining Attributes of the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Managing NMS Collector and Processor Services. . . . . . . . . . . . . . . . . . . . . . . 55

Viewing Active Alarm Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Device Alarm Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 MIS Database Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Diagnostic Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Purge Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Deleting by Date. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

List of Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Defining Attributes of the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Managing NMS Collector and Processor Services. . . . . . . . . . . . . . . . . . . . . . . 55

Viewing Active Alarm Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Device Alarm Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 MIS Database Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Diagnostic Viewer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Purge Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

The Event Processor is implemented as a Windows-based service.

Active Alarm Events on page 69.

For more information on the Active Event Viewer, see Viewing

Figure 1: Network Management System overview

Acom DS3 Switch A

Acom DS3 Switch B

Event Collector Service

Collector Connection Event Filter

Alarm File Reporter

Alarm MSMQ Reporter

CDR MSMQ Reporter

CDR File Reporter TCP/IP Configuration

FaultEvent Microsoft Message Queue

CallEvent Microsoft Message Queue

Event Processor Service

Alarm Consumer File Reporter Alarm Reporter

CDR Consumer CDR Reporter

CDR Distributor Service

RAM Disk Space

Installing NMS Components and Related Software

Installing NMS Components and Related Software

Windows 7 User Account Control

Database Server and Instance

Order of Software Installation

Installing NMS Components and Related Software

To install all NMS services and client on a single machine:

1. Edit this configuration file:

2. Find this section:

3. Change the value to true.

Installing NMS Components and Related Software

Starting Network Management Console

To start Network Management Console

Starting Network Management Console

C:\Program Files\Zetron\NMS\Management Console\

For All Systems

Defining Attributes of the Network

For All Systems

For Fault Event Management

Defining Attributes of the Network

For CDR Management

For CDR Management

To set up CDR Management

Defining Attributes of the Network

6. Click Save to add the entry, or click Cancel to discard it.

Defining Attributes of the Network

To add a system entry

Defining Attributes of the Network