Ericsson LBI-39169 - Manuals

Page 3 - TABLE OF CONTENTS; Page

LBI-39169 3 TABLE OF CONTENTS Section/Paragraph Page 1. PREFACE ........................................................................................................................................................... 9 1.1 MANUAL ORGANIZATION .........................................................

Page 6 - LIST OF FIGURES AND TABLES; Figure

LBI-39169 6 LIST OF FIGURES AND TABLES Figure Title Page Figure 1 - EDACS Menu on Main Menu Bar ...........................................................................................................17 Figure 2 - Example of Map Traversal..............................................................

Page 8 - This page intentionally left blank

Page 9 - PREFACE; This is one of four manuals for the EDACS; MANUAL ORGANIZATION; The manual is divided into the following sections:

PREFACE LBI-39169 9 1. PREFACE This is one of four manuals for the EDACS  Network Manager. This manual provides operating instructions for users and administrators of the Network Manager system. Additional documentation for the Network Manager is available in the following publications: • EDACS Net...

Page 13 - INTRODUCTION; A report can be generated listing the past and present alarms.

INTRODUCTION LBI-39169 13 3. INTRODUCTION The International Organization for Standards (ISO) Network Management forum identifies five functional areas of network management, often referred to simply as “FCAPS.” This model serves as the basis for the Network Managementsystem. The five management area...

Page 14 - The following features are available through Fault Management:; Fault Notification; CONFIGURATION MANAGEMENT

LBI-39169 INTRODUCTION 14 3.1 FAULT MANAGEMENT Fault Management is responsible for detecting, isolating, and reporting anomalous conditions affecting network operation. Central to the concept of a fault is the fact that some corrective action must be taken, whether automatically over aLocal Area Net...

Page 15 - conceptually composed of three major areas:; Multisite Monitor; SECURITY MANAGEMENT; through the profile configuration of remote elements.

INTRODUCTION LBI-39169 15 3.4 PERFORMANCE MANAGEMENT Performance Management is responsible for characterizing the usage and efficiency of the network. This area is conceptually composed of three major areas: • Utilization -- Provides information regarding which aspects of, and the degree to which, t...

Page 16 - Customized Maps

LBI-39169 INTRODUCTION 16 3.5.2 System Access Security Management is responsible for administering user access to network resources, including the Network Elements (NEs) themselves. The approach will encompass: • Password Protection: Native Access Mode -- Native access refers to currently existing s...

Page 17 - Customizable Icons; EDACS NM MENUS AND THEIR FUNCTIONALITY; Figure 1 - EDACS Menu on Main Menu Bar

INTRODUCTION LBI-39169 17 Background NetworkMap Overlays This standard HP OpenView Network Node Manager feature allows customers toflexibly place network icons on top of actual area maps. Topological maps (instandard GIF format) are easily added, but are not provided. Customizable Icons The labels o...

Page 18 - NETWORK MANAGER BASICS; PULLDOWN MENU SELECTION PROCEDURE USING THE MOUSE; Select one of the two options below to select the Pulldown Menu:; PULLDOWN MENU SELECTION PROCEDURE USING THE KEYBOARD; when the user chooses to edit a file.

LBI-39169 NETWORK MANAGER BASICS 18 4. NETWORK MANAGER BASICS 4.1 PULLDOWN MENU SELECTION PROCEDURE USING THE MOUSE Select one of the two options below to select the Pulldown Menu: Position the cursor to the desired menu option, and quickly press/release the left mouse button once. The pulldownmenu ...

Page 19 - last two do not. Background graphics may be loaded in all submaps.; Figure 2 - Example of Map Traversal

NETWORK MANAGER BASICS LBI-39169 19 4.4 MAP TRAVERSAL The following submaps are examples of map traversal. The first two submaps contain background graphics, while the last two do not. Background graphics may be loaded in all submaps. Exploding the EDACS icon brings up a screen similar to that shown...

Page 20 - similar to the screen shown below.; Figure 3 - Example of Exploding a Switching Center and Site Icon

LBI-39169 NETWORK MANAGER BASICS 20 Exploding the Switching Center icon (SW Ctr #37) on the IMC Node 37 submap brings up a Switch Center 37 submap similar to the screen shown below. Exploding a Site icon (such as Site 1) on the IMC Node 37 submap brings up the Site 1 submap similar to the screen sho...

Page 21 - STARTUP PROCEDURES; STARTING A NETWORK MANAGER WORK SESSION; Figure 4 - Network Manager Login Dialog Box

STARTUP PROCEDURES LBI-39169 21 5. STARTUP PROCEDURES Use the following procedures to login and start a Network Manager work session. A Network Manager work session is described as the time between logging in and logging out. 5.1 STARTING A NETWORK MANAGER WORK SESSION The Ericsson Login Screen is t...

Page 22 - LOGGING OUT OF THE NETWORK MANAGER SESSION

LBI-39169 STARTUP PROCEDURES 22 5.2 ENDING A NETWORK MANAGER WORK SESSION Use the following procedures to properly end a work session. CAUTION When you finish a working session, DO NOT turn off the Network Manager Station. This equipment is part of amulti-user network, and other people may be using ...

Page 23 - RETRIEVING THE SOFTWARE VERSION; SUBCOMPONENT SOFTWARE VERSIONS; boards) directly connected to the selected device.; Figure 6 - Software Version Screen Example

RETRIEVING THE SOFTWARE VERSION LBI-39169 23 6. RETRIEVING THE SOFTWARE VERSION The Software Version feature allows you to obtain the versions of software installed on the Network Manager platform and software installed on directly connected devices and the devices they proxy for. 6.1 SUBCOMPONENT S...

Page 24 - Major Version; NETWORK MANAGER SOFTWARE APPLICATION VERSIONS

LBI-39169 RETRIEVING THE SOFTWARE VERSION 24 Major Version The Minor Software vision is an integer number representing the minor software revision number, forexample the number “1” in 2.1. Description The description field provides a brief description of the software component. Software Path This fi...

Page 25 - EDACS HELP; preceded with “EDACS” to make them easily identifiable.; Figure 7 - EDACS Help Menu; The display will list the various OpenView and EDACS tasks.

EDACS HELP LBI-39169 25 7. EDACS HELP EDACS Help has been integrated into the OpenView Network Node Manager help system. EDACS Help items are preceded with “EDACS” to make them easily identifiable. File... On Help Display Legend Index Glossary On Version Help Index Application Tasks F1 Functions App...

Page 26 - MONITORING EDACS FAULT CONDITIONS; Notification through the Event Notification Interface

LBI-39169 MONITORING EDACS FAULT CONDITIONS 26 8. MONITORING EDACS FAULT CONDITIONS Fault Management is responsible for detecting, isolating, and reporting alarm or fault conditions affecting the various Managed Elements (ME) in the EDACS network. 8.1 DETECTING AND ISOLATING FAULTS (ALARMS) Fault (a...

Page 27 - Category

MONITORING EDACS FAULT CONDITIONS LBI-39169 27 Table 1 - Status Colors/Levels Category Status Condition Status Meaning Icon Color Administrative Unmanaged Users can set this value, which indicates that the object should not be monitored and that thestatus should be ignored. When the user setsthe obj...

Page 28 - Produce an audible beep.

LBI-39169 MONITORING EDACS FAULT CONDITIONS 28 The user is able to determine the Managed Element’s operating condition at a glance by observing the icon’s color. Upon receiving an alarm, the event is logged and the icon color is changed to the color representing the severity of the alarm.To ensure a...

Page 29 - setting and clearing event.; NOTE: If the event has the concept of setting and; Erroneous events, which may be caused by broken; Figure 9 - Event Configuration; NOTE

MONITORING EDACS FAULT CONDITIONS LBI-39169 29 /usr/EDACS/conf/C/ed_trapd.conf. The severity levels and category will not be restored and will remain as customized bythe user. The restore operation will not erase the actions which have been associated with individual alarms. NOTE Modifications to se...

Page 31 - any submap associated with the icon.; Figure 10 - Using Hierarchical Maps to Identify Fault Events; Alarm Summary

MONITORING EDACS FAULT CONDITIONS LBI-39169 31 8.3 IDENTIFYING THE CAUSE OF ALARMS 8.3.1 Using Hierarchical Maps After the Network Manager alerts the user to an alarm either by changing an icons color or through a popup window, it will be necessary to identify the responsible element causing the fau...

Page 32 - Figure 11 - EDACS Fault Menu

LBI-39169 MONITORING EDACS FAULT CONDITIONS 32 device polling will be displayed. The display is in a short report (list) format, with each entry in the report listing thetime stamp, alarm description, and severity level of the event. 5. If an object in the map has an operational status color other t...

Page 33 - Figure 12 - EDACS Event Browser Example

MONITORING EDACS FAULT CONDITIONS LBI-39169 33 8.3.2.1 Notification of New Events To know when events have been received, examine the event notification indicator lights in the Event Categories window. The indicator lights will change to corresponding color of the most severe alarm logged. To see ne...

Page 34 - Events” category list, you need only delete the event from one list.; Events; As an example, to see all the Critical events:; Source; Select the source object and use the menu items in the; Description from the Event Browser menu bar.

LBI-39169 MONITORING EDACS FAULT CONDITIONS 34 8.3.2.3 Deleting Events Events continue to appear in an Event Browser list until you delete them or the maximum number of events for the browser has been reached. The primary reason to delete events is so you can determine when new events occur. If you ...

Page 35 - 0) using the Telnet features described later in this manual.

MONITORING EDACS FAULT CONDITIONS LBI-39169 35 The Network Manager will display the Event Description window providing the technical details associated with theevent and possible corrective action. 2. If the event is associated with a site, the user may optionally consult the System Manager Alarm Co...

Page 36 - CONFIGURING EDACS DEVICES; Automatically reboots the EDACS device.; The CEC/IMC Manager client is invoked using the EDACS-; R estart. Restarts traffic after a shutdow n.; Figure 15 - EDACS Configuration Menu

LBI-39169 CONFIGURING EDACS DEVICES 36 9. CONFIGURING EDACS DEVICES The Network Manager provides a single point of control and can configure devices by either bringing up clients running on the Network Manager or by logging into devices with the native access mode. The PI, BCU/CAL, and EDG are acces...

Page 37 - On the Switch Center submap, highlight the IMC Manager icon.; Figure 16 - CEC/IMC Manager Main Window and Menu Bar; Selecting any of the choices from the CEC/IMC Manager menu bar (

CONFIGURING EDACS DEVICES LBI-39169 37 9.1.1 Starting The CEC/IMC Session From the Network Manager, invoke the CEC/IMC Manager client using the following procedure: 1. On the Switch Center submap, highlight the IMC Manager icon. 2. From the Main Menu bar, select the EDACS->Configuration->Confi...

Page 38 - Windows NT. Complete instructions may be found in LBI-39224.; Figure 19 - Site Channel Configuration Example Screen

LBI-39169 CONFIGURING EDACS DEVICES 38 Before proceeding, it is recommended that the user be completely familiar with using the CEC/IMC Manager for Windows NT. Complete instructions may be found in LBI-39224. 9.1.2 Sample CEC/IMC Manager Screens Some sample CEC/IMC Manager screens for configuration ...

Page 39 - Figure 20 - Console User Profile Configuration Example Screen; On the Switch Center submap, highlight the device’s icon.; TELNETING TO THE SYSTEM MANAGER; On the Switch Center submap, highlight the System Manager icon.

CONFIGURING EDACS DEVICES LBI-39169 39 Figure 20 - Console User Profile Configuration Example Screen 9.2 TELNET SESSIONS TO THE PI, BCU, CAL, AND EDG Telnet access into each device is password-protected. Therefore, the user requesting access must have login privileges for the remote device. The norm...

Page 40 - Figure 21 - System Manager Login Screen

LBI-39169 CONFIGURING EDACS DEVICES 40 This brings up the the System Manager User Menu screen (Figure 22). From this point on all System Manageroperations are as described in LBI-38984. NOTE When telneting into the System Manager, the keyboard is remapped for use with the VAX/VMS operating system.A ...

Page 42 - TRANSFERRING DEVICE FILES; Highlight the device’s icon on the Network Manager’s submap.

LBI-39169 TRANSFERRING DEVICE FILES 42 10. TRANSFERRING DEVICE FILES Occassionally, it may be necessaary to transfer device files; such as configuration files for editing, activity data for billing, etc. Device files may be transfered from the device’s storage location to a more easily accessible lo...

Page 43 - PI Activity Data Transfer Example

TRANSFERRING DEVICE FILES LBI-39169 43 PI Activity Data Transfer Example This is an example of transferring the PI activity record sep01.log to the users HOME directory. Connected to 192.168.201.30.220 192.168.201.30 pSOSystem FTP server (NTL68K/1.0.4) ready.Name (192.168.201.30:lab): user331 Passwo...

Page 44 - BCU CDR Data Transfer Example; may then use a third party application that reads CDR records.; Figure 24 - Transferring a BCU Billing Record Using FTP

LBI-39169 TRANSFERRING DEVICE FILES 44 BCU CDR Data Transfer Example This is an example of transferring a CDR record, t2250609.CDR, from the BCU to the user’s home directory. The user may then use a third party application that reads CDR records. Connected to 192.168.201.20.220 192.168.201.20 pSOSys...

Page 45 - System Manager Activity Data Transfer Example

TRANSFERRING DEVICE FILES LBI-39169 45 System Manager Activity Data Transfer Example This is an example of transferring an Activity data file, ACT_01-SEP-1996.03;1, from the System Manger to the user’s home directory. The user may then use a third party application that reads CDR records. Connected ...

Page 46 - MONITORING PERFORMANCE TRENDS; Provides totals for call types pertaining to this EDACS device.

LBI-39169 MONITORING PERFORMANCE TRENDS 46 11. MONITORING PERFORMANCE TRENDS Performance trends can be used to determine utilization and accessibility or to tune system performance. Trends can be viewed on a per site or Radio Switch basis. The results of these trends are presented on the 2-D line gr...

Page 47 - Figure 26 - Example of a Two-Dimensional Line Graph; available for the following selections:

MONITORING PERFORMANCE TRENDS LBI-39169 47 11.1.1 Line Graph Example The example of a line graph, shown in Figure 26, illustrates the ease and clarity with which the EDACS Network Manager platform presents data. The performance groupings display logically similar performance items on one graph,depic...

Page 49 - for either nodes or sites.

MONITORING PERFORMANCE TRENDS LBI-39169 49 11.2 TRACKING EDACS DEVICE UTILIZATION The Performance -> Utilization menu item allows the user to chart the totals for call types pertaining to this EDACS device. The entries on the Performance sub-bar, see Figure 27, are detailed below. All of the foll...

Page 50 - Figure 28 - EDACS Performance / Accessibility Menu

LBI-39169 MONITORING PERFORMANCE TRENDS 50 11.3 TRACKING EDACS DEVICE ACCESSIBILITY The Performance -> Accessibility menu item allows the user to chart the queued, busy, and denied call information for this EDACS device. All of the following graphs will be displayed for either nodes or sites. • D...

Page 51 - Queues - Total Queues for all call types.

MONITORING PERFORMANCE TRENDS LBI-39169 51 11.4 COMPARING PERFORMANCE FROM MULTIPLE SITES OR NODES The Performance -> Compare menu item allows the user to chart a single MIB value for multiple nodes or sites. The following graphs will display a single performance parameter for multiple nodes or s...

Page 52 - MONITORING REAL-TIME CALL ACTIVITY; Invokes Site Monitor

LBI-39169 MONITORING REAL-TIME CALL ACTIVITY 52 12. MONITORING REAL-TIME CALL ACTIVITY Real-time call activity can be displayed on both node (Multisite Monitor) and site (Site Monitor) levels. In the Multisite Monitor (MSM), active call types are indicated by the application of color to the button r...

Page 53 - File; Figure 31 - Multisite Monitor Display Example

MONITORING REAL-TIME CALL ACTIVITY LBI-39169 53 12.1 USING THE MULTISITE MONITOR APPLICATION The Multisite Monitor application monitors call activity for one user-specified node. All windows can be manipulated (i.e., resized, iconized, closed) via standard window border operations. The Multisite Mon...

Page 54 - ) the display continues to display the textual information; Figure 32 - Multisite Monitor Menu Bar

LBI-39169 MONITORING REAL-TIME CALL ACTIVITY 54 The Options menu has four options: Traffic Filter, Legend, Statistics Rows, and Quiet Drops. The Options menu is discussed in the next section. These options allow the user to customize the Multisite Monitor application to suit particularneeds The Help...

Page 55 - No textual information is displayed.; Figure 33 - Traffic Filter Window

MONITORING REAL-TIME CALL ACTIVITY LBI-39169 55 Each filter type also has a textual setting. There are five textual options. Only one may be in effect at a time for a specific call type. 1. None No textual information is displayed. 2. Filter ID One- or two-letter default designation for filter type ...

Page 56 - Figure 34 - Multisite Monitor Legend

LBI-39169 MONITORING REAL-TIME CALL ACTIVITY 56 12.1.2 Viewing Call Type Colors The Legend button activates a small window that serves as a key for the current Traffic Filter settings (see Figure 34). Beside each filter is a buttonthat conveys the filter’s current state, color, and textual settings....

Page 57 - Figure 35 - Site Monitor Display Example

MONITORING REAL-TIME CALL ACTIVITY LBI-39169 57 12.2 USING THE SITE MONITOR APPLICATION The Site Monitor application monitors call activity for an individual site. The Site Monitor window contains a main menu bar, work area, and scroll bars (see Figure 35). All windows can be manipulated (i.e., resi...

Page 58 - Figure 36 - Site Monitor Menu Bar; Changing Phone Call Keying Update Parameters

LBI-39169 MONITORING REAL-TIME CALL ACTIVITY 58 File q S tatistics R ow s q P hone D igits q Fine T im ing q Q uiet D rops q K eying U pdates O ptions H elp Statistics R ow s. Turns O N or O FF the Statistic R owdisplaying Last Q ueued C all, L ast D enied Call, L astSystem Busy Call and last C onve...

Page 59 - USING OPENVIEW NETWORK NODE MANAGER; default, the EDACS MIBs are automatically loaded into OpenView.; VIEWING/GRAPHING PERFORMANCE PARAMETERS; MIBs must be loaded to perform these operations.; ADDING CUSTOM MENU ITEMS

USING OPENVIEW NETWORK NODE MANAGER LBI-39169 59 13. USING OPENVIEW NETWORK NODE MANAGER This section briefly describes some of the features available through OpenView Network Node Manager. We suggest the you become familiar with the HP OpenView Network Node Manager User’s Guide. This guide contains...

Page 60 - Figure 37 - Modify Event Screen

LBI-39169 USING OPENVIEW NETWORK NODE MANAGER 60 13.5 THRESHOLD TRAPS ON COLLECTED DATA The user may specify the generation of an event based upon the value of a monitored performance parameter or that parameter’s exceeding a user-defined threshold. For example, the user may wish to be notified via ...

Page 61 - major Canadian provinces; Snapshots may consume noticeable amounts of memory.

USING OPENVIEW NETWORK NODE MANAGER LBI-39169 61 The ringBell utility takes two arguements. The value of the auguments are insignificant as long as the format iscorrect. ringBell <selectionName> <message in quotes> The ringBell utility performs two actions. It sounds the bursts of beeps ...

Page 62 - X-Station or by using a PC running PC Xware.; INTEGRATION WITH OTHER NETWORK MANAGER APPLICATIONS

LBI-39169 USING OPENVIEW NETWORK NODE MANAGER 62 13.11 MULTIPLE EDACS NETWORK MANAGER SESSIONS OpenView Network Node Manager supports multiple login sessions. Multiple sessions can be accomplished by using an X-Station or by using a PC running PC Xware. Certain restrictions apply in situations where...

Page 63 - Enter the information in the “Label” field.

USING OPENVIEW NETWORK NODE MANAGER LBI-39169 63 13.13 CUSTOMIZING ICONS 13.13.1 Icon Labels Modifications to fields other than “Label” in the Symbol Description are not supported and may adversely affectsystem behavior. To change icon labels, depress the right mouse button while positioned on the i...

Page 64 - users; DEVICE POLLING INTERVAL

LBI-39169 PROCEDURES 64 14. PROCEDURES 14.1 REBOOTING THE NETWORK MANAGER From the root profile enter: > /etc/shutdown -r now 14.2 SYSTEM SHUTDOWN PROCEDURES Use the following procedure to properly shutdown the Network Manager system. CAUTION Stopping the system improperly can corrupt (damage) th...

Page 65 - PROCEDURES; MODIFYING EVENT DESCRIPTIONS; OK to save the changes.

PROCEDURES LBI-39169 65 • Console • Jessica PBX Interface (PI) • Billing Correlation Unit/ Centralized Activity Logger (BCU/CAL) NOTE: The site devices are not included in this list. Their status is obtained through the System Manager Proxy Agent. The EDACS Initialization attribute section of the po...

Page 67 - the

PROCEDURES LBI-39169 67 HP application which finds IPs. It is also possible that directly connected elements may be added prior to their discovery bythe IPMAP application. Care must be taken to ensure that the object created is also used by IPMAP. Not only must theselection name equal the IP address...

Page 68 - DELETING ORPHANED SUBMAPS

LBI-39169 PROCEDURES 68 4. Enter the following command to restore permissions. > chmod 444 /usr/EDACS/nls/C/msm_msg.msg <ENTER> (MSM message file) or > chmod 444 /usr/EDACS/nls/C/sm_msg.msg <ENTER> (SM message file) 5. As the root user, generate new catalog files by executing the f...

Page 69 - Filename; VIEWING/MODIFYING EDACS IDENTIFIERS; OR; VIEWING/MODIFYING TRAP SEVERITY LEVELS

PROCEDURES LBI-39169 69 The beginning of this output will list the number of objects in the database. There should be roughly three times thenumber of EDACS elements. 2. Enter: > /usr/OV/bin/ovobjprint > Filename This will output the contents to a file called “Filename.” 3. The individual obje...

Page 71 - System will shutdown and come back up in single-user mode.

PROCEDURES LBI-39169 71 14.18 RESTORING A FULL SYSTEM IMAGE FROM THE BACKUP To restore a full system image from the backup, perform the following steps: 1. As root user: Use console login. > /etc/shutdown now <ENTER> System will shutdown and come back up in single-user mode. 2. Insert the t...

Page 72 - TROUBLESHOOTING; /etc/update exits with error that all devices are not mounted.; ATTEMPT TO LOG IN FAILS

LBI-39169 TROUBLESHOOTING 72 15. TROUBLESHOOTING This section presents various methods for solving technical difficulties with the Network Manager. 15.1 CD-ROM DOES NOT WORK Problem: /etc/update exits with error that all devices are not mounted. Solution: The /etc/checklist file should have only lis...

Page 73 - The EDACS icon is blue.; EDACS ICON IS BROWN; The EDACS icon is brown.; MAP GENERATION VERIFY OPERATION IS NOT WORKING PROPERLY

TROUBLESHOOTING LBI-39169 73 15.4 EDACS ICON IS BLUE Problem: The EDACS icon is blue. Solution: A blue icon indicates that the element is not managed by the EDACS Network Manager application. This canhappen if another icon is added with the same EDACS Identifiers as this one. To view the EDACS Ident...

Page 74 - Use ls_stat to determine if either of these conditions exist.; PERFORMANCE NOT SHOWING TRAFFIC; System is slower than usual.

LBI-39169 TROUBLESHOOTING 74 15.8 POPUP STATES NO NODE LICENSE Problem: This popup will occur either if there is no node license or if there is no application license. Solution: Use ls_stat to determine if either of these conditions exist. 15.9 PERFORMANCE NOT SHOWING TRAFFIC Problem: No traffic ind...

Page 75 - Be sure there are no other users on the system.; SYSTEM MANAGER SNMP “SETS” FAILING

TROUBLESHOOTING LBI-39169 75 15.11 APPLICATION DOES NOT RESPOND TO VERIFICATION REQUEST WHENADDING ICON Problem: Application does not respond to Verification request when adding icon. When hit verify a second time,OpenView will not call application again. Solution: Must modify a field, even if setti...

Page 76 - The IMC reports a link failure.

LBI-39169 TROUBLESHOOTING 76 Network Manager stations and ensure the interval is set to a value of 30 seconds or more. This will significantlyreduce the number of nuisance failures. 15.14 IMC DETECTED LINK FAILURES Problem: The IMC reports a link failure. Solution: For link fail tests involving all ...

Page 77 - Reinsert the card into the card cage. This will clear the NOV RAM.

TROUBLESHOOTING LBI-39169 77 The only viable solution is to refrain for using color-intensive background graphics in the OpenView submaps. 15.16 POPUP WARNING Problem: An xnmevent popup warns that only 10 popups can be generated at a time. Solution: The /usr/OV/appdefaults/XNm resource file sets the...

Page 79 - The CAM is a CEC/IMC interface module that

GLOSSARY LBI-39169 79 TERM DEFINITION SCAT, and CNI systems. Callee The party to whom the call is placed, i.e., an individual or group of radios. Caller The originating party of the call request, i.e., an individual radio. CAM Centralized Activity Module − The CAM is a CEC/IMC interface module that ...

Page 80 - A conventional base station can be

LBI-39169 GLOSSARY 80 TERM DEFINITION CNI Conventional Network Interface − A conventional base station can be connected to the CEC/IMC switch via a CNI. The CNI is formed by a GETCshelf located at the conventional station that makes the station appear to aMIM as an EDACS site. In the CNI system, dif...

Page 82 - Integrated EDACS Alarm.

LBI-39169 GLOSSARY 82 TERM DEFINITION HP OV NNM Hewlett-Packard OpenView Network Node Manager. Management platformthat provides common management functions, such as data collection andreporting, using standard protocols and software interfaces. Hub Used to concentrate several 10BaseT (Twisted Pair E...

Page 85 - The RSM is an IBM PC compatible computer

GLOSSARY LBI-39169 85 TERM DEFINITION enables the RSM computer to request status information from radios within thenetwork. Router A system used to connect separate LANs and WANs into an internet, and toroute traffic between the networks. In the Network Manager system, a router isneeded to go from E...

Page 86 - See Simple Network Management Protocol.

LBI-39169 GLOSSARY 86 TERM DEFINITION SNMP See Simple Network Management Protocol. StarGate In EDACS trunking, links up to eight EDACS wide-area multisite networks tocreate a single, seamless network. StarGate Controller A StarGate Controller is an IMC switch specifically configured fordistributed m...

Page 87 - A message that reports a problem or significant event.; ConVentional Interface Module; The VMIM couples the CIA secondary; C3 Modular/Desktop Console Translator; Using data protocol conversion

GLOSSARY LBI-39169 87 TERM DEFINITION login information is databased to allow the CEC/IMC to track individual radiounits as they move from system-to-system. The CEC/IMC can then route widearea calls based on this database. Transmission Control Protocol The Transmission Control Protocol (TCP) is the ...

Page 88 - INDEX

LBI-39169 INDEX 88 17. INDEX —A— Accounting Management, 14 Transferring Device Files, 42 Adding a Connection, 68Adding Custom Menu Items, 60Adding Descriptions To Objects, 69Adding Object Descriptions, 64Adding Symbols to the EDACS Maps, 67Attempt to Log In Fails, 73 —B— Background Geographical Maps...

Page 89 - Jessica

INDEX LBI-39169 89 Introduction, 13 —J— Jessica Manuals, 12 —L— Line Graphs, 47Loading MIBs, 64Loading/Unloading MIBS, 60logging Out of Network Manager, 22Login Screen, 21 —M— Managing and Unmanaging Devices, 30Map Background Overlays, 17 Map Generation Verify Operation Is Not Working Properly,74Map...

Page 90 - Two-Dimensional Line Graph

LBI-39169 INDEX Ericsson Inc.Private Radio SystemsMountain View RoadLynchburg, Virginia 245021-800-592-7711 (Outside USA, 804-592-7711) Printed in U.S.A. Map Generation Verify Operation Is Not WorkingProperly, 74MSM/SM Does Not Show PI Traffic,, 73MSM/SM Out of Color Map Entries, 77Multinode Traffic...