Digivance CXD/NXD Element Management System EMS. User Manual ADCP Part Number Rev A Issue 1

Transcription

1

2

3 Digivance CXD/NXD Element Management System EMS User Manual ADCP Part Number Rev A Issue 1

4 Page ii

5 About This Manual This manual tells how to install and use the Digivance CXD/NXD Element Management System (EMS). EMS is a web-based software application that may be accessed using a PC or laptop computer. Revision History Issue Date Reason for Change Issue 1 12/2005 Original. Trademark Information The following trademarks are referenced in this guide: ADC is a registered trademark of ADC Telecommunications, Inc. Digivance is a registered trademark of ADC Telecommunications, Inc. Related ADC Publications The following ADC technical publications contain information related to the Element Management System. Copies of these documents can be ordered by calling ADC Technical Assistance Center ( extension 73475, in U.S.A. and Canada; outside U.S.A. and Canada). All ADC technical publications are also available online at Digivance CXD Multi-Band Distributed Antenna System Operation Manual (ADCP ) Digivance CXD/NXD Hub Installation and Maintenance Manual (ADCP ) Digivance CXD Radio Access Node Installation and Maintenance Manual (ADCP ) Digivance CXD/NXD SNMP Agent and Fault Isolation User Guide (ADCP ) Page iii

6 Page iv

7 ABLE OF CONTENTS SECTION 1. INTRODUCTION TO EMS General Description Basic Function System Components Overview of MIBs Common Use Scenarios Direct Connection at Hub Site Remote Connection Overview of User Interface Overview of EMS Tasks SECTION 2. INSTALLATION GUIDELINES System Requirements System Administrator Connecting to the EMS Server SECTION 3. USING EMS FOR NETWORK TASKS Master List of Tasks Login and Logout Assign Usernames and Passwords (Administrator Level Only) View Active Alarms View Alarm History View Filtered Alarm List Hub Nodes RAN Nodes BTS connection Tenant Sector-Node Relationship System Control Parameters Forward Gain Reverse Gain Delay RAN Disable RUC (Administrator Level Only) RDC (Administrator Level Only) HDC (Administrator Level Only) FSC (Administrator Level Only) Network Parameters View System Performance Graphs Page v

8 Table of Contents 3.19 Setup System Performance Graphs System Performance Tables Forward RF Power Browse MIBs (Administrator Level Only) Host Node Information Troubleshooting SECTION 4. EMS ALARM REFERENCE Introduction Alarm Reference Table ACRONYMS GLOSSARY Page vi

9 1 INTRODUCTION TO EMS

10

11 INTRODUCTION TO EMS 3 This section is an introduction to help you understand the ADC Digivance CXD/ NXD Element Management System (EMS). 1.1 General Description EMS is a software application that provides control and monitoring functions for network elements in a Digivance CXD/NXD system. These network elements include a Hubmaster and Hub Nodes in a centralized Hub and remotely located Radio Access Nodes (RANs). The EMS application resides within the CXD/NXD system software on the Hubmaster, as indicated in Figure 1. Radio Access Node Digital Fiber Distribution Hub - EMS Server, located on Hub Master, monitors Hub Nodes and RANs BTS BTS BTS BTS A Figure 1. CXD/NXD System

12 4 Basic Function Section Basic Function Figure 2 illustrates the basic function of EMS in terms of the data flow within the CXD/NXD system. EMS accesses the network at the EMS hub, where RF signals received from Base Transceiver Stations (BTSs) are converted to optical signals for distribution to the RANs. EMS is thus in a position to monitor both types of signals. EMS may be accessed either at the hub by a direct physical connection to the Ethernet switch on the hub rack or remotely by an internet connection to the same Ethernet switch. NOTE: Though EMS provides a means to monitor the CXD/NXD system, it is not a necessary part of the system. For a comprehensive description of the CXD/NXD system, refer to ADCP , Digivance CXD Multi-Band Distributed Antenna System Operation Manual. BTS RF SIGL RF SIGL EMS HUB HUB MASTER HUB NODES OPTICAL SIGLS LOCAL COVERAGE AREA REMOTE ACCESS NODE USER REQUESTS STATUS ALARMS RF SIGL LEVELS A OR DIGIVANCE ELEMENT MAGEMENT SYSTEM Figure 2. EMS Basic Function

13 Introduction to EMS 1.3 System Components System Components 5 EMS is a web-based application based on Simple Network Management Protocol (SNMP), an international standard for remote management of online devices. The main components, shown in Figure 3, are the EMS application on the Hubmaster, which functions as an SNMP manager, and SNMP agents located one each on the Hub Nodes and RANs. SNMP data bases called Management Information Bases (MIBs) contain CXD/NXD system values (called objects in SNMP terms). HUB NODE n RAN n HUB NODE 3 RAN 3 HUB NODE 2 RAN 2 HUB NODE 1 RAN 1 MIBs MIBs SNMP AGENT SNMP AGENT HUB NODE STATUS ALARMS GET SET TRAP ETHERNET SWITCH RAN STATUS ALARMS HUBMASTER HUBMASTER SNMP AGENT EMS MIBs A USER Figure 3. EMS System Components

14 6 Overview of MIBs Section 1 Data flow in the EMS SNMP system consists of GET, SET, and TRAP messages exchanged between EMS and SNMP agents. Using GET and SET messages, EMS queries for or sets CXD/NXD system values (i.e., MIB objects) in response to user requests. TRAP messages, sent in a reverse direction, from SNMP agents to EMS, indicate alarms in network elements. A TRAP message is generated automatically whenever a fault is detected in the CXD/NXD system. 1.4 Overview of MIBs Although each Host Node and RAN in the CXD/NXD system has a single SNMP agent, each SNMP agent interacts with multiple MIBs arranged into a hierarchy for reporting of TRAPs. Figure 4 shows the MIB structure. Having a sense of this structure will help in understanding EMS alarms (for acronyms, see appendix). NOTE: For a complete description of these SNMP agents and MIBs, see ADCP , Digivance CXD/NXD SNMP Agent and Fault Isolation User Guide. HUBMASTER SNMP AGENT RAN SNMP AGENT BTS CONNECTION MIB RAN NODE MIB NETWORK NODE MIB HUB NODE MIB TENENT OAM MIB EQUIPMENT MIB NETWORK NODE MIB HUB RF CONNECTION MIB NODE PATH MIB EQUIPMENT MIB NODE PATH MIB PATHTRACE MIB MUC MIB STF MIB GPS MIB NODE PATH MIB GPS MIB SIF MIB RDC MIB BIM MIB HDC MIB HUB MIB FSC MIB RSC MIB SIF MIB STF MIB GPS MIB RUC MIB HUB NODE SNMP AGENT A Figure 4. CXD/NXD MIBs

15 Introduction to EMS 1.5 Common Use Scenarios Common Use Scenarios 7 EMS functions are typically accessed using two common use scenarios described in the next two topics Direct Connection at Hub Site In this scenario, shown in Figure 5, an application engineer or technician carries a laptop to the hub site and connects into the Ethernet switch located in the CXD/ NXD hub rack. Alarms can be viewed, RF signal levels can be checked, and attenuation and gain values can be entered. GET SET RANs HUB nodes ETHERNET SWITCH TRAP EMS LAPTOP HUB RACK ASSEMBLY HUB A Figure 5. Rack With Ethernet Switch

16 8 Overview of User Interface Section Remote Connection In this use scenario, shown in Figure 6, an engineer accesses EMS from a desktop computer using an internet connection to the Ethernet switch on the hub rack. IT personnel need to ensure that the engineer has access to the system s unique subnet. RANs GET SET HUB nodes ETHERNET SWITCH TRAP INTERNET CONNECTION EMS PC HUB RACK ASSEMBLY HUB A Figure 6. Local Office Scenario 1.6 Overview of User Interface EMS provides a Graphical User Interface (GUI) for requesting and viewing CXD/ NXD data and performing EMS tasks. Figure 7 shows a screen example, a display of alarms.

17 Introduction to EMS Overview of EMS Tasks 9 Figure 7. Typical EMS Screen in Browser Window For other examples of EMS screens, see Section 3 of this manual. 1.7 Overview of EMS Tasks Table 1 summarizes the tasks done using EMS. Table 1: Summary of EMS Tasks TASK Determine which network elements are currently connected Change Hub Node and RAN names DESCRIPTION EMS allows the maintainer to quickly identify which hubs and RANs are found within the system. EMS also identifies which RANs are associated with each tenant/ tenant sector. EMS allows the maintainer to create useful hub and RAN IDs. The IDs may be in the customer format to help them identify each node.

18 10 Overview of EMS Tasks Section 1 Table 1: Summary of EMS Tasks (Continued) TASK Set system gain and system delay Determine current status (alarms) Check RF signal levels View performance graphs (future EMS feature) Troubleshoot problems DESCRIPTION EMS allows the maintainer to change the system gain and overall system delay for any RF signal path. This typically would be done at installation, if the customer has a need to change the default values (due to system configuration, protocol, etc.). EMS allows the maintainer to view the status of the system via alarms. The alarm table is color coded and the active alarm table updates automatically for ease of use. EMS allows the maintainer to easily view the RF signal strength through any Downlink path. The RAN powers are displayed by tenant/tenant sector for ease of use. EMS (future release) allows the maintainer to create and view system performance graphs. This trend data may come in handy to avoid possible future outages/ system degradation. EMS allows the maintainer to access all system data to help trouble problems that may arise (MIB Browser).

19 2 INSTALLATION GUIDELINES

20

21 INSTALLATION GUIDELINES The EMS application resides within the CXD/NXD system software. As a result, there is no EMS-specific software to install on an operator s computer. EMS can be accessed via any computer that can communicate with the CXD/ NXD system subnet (check with your company s IT personnel on subnet accessibility) System Requirements For EMS access, the computer must have: Web browser (for example, MS Explorer, Netscape, or FireFox) Access to the CXD/NXD system subnet (for remote access, see IT personnel for assistance) 2.2 System Administrator EMS has two levels of operators: Administrator The administrator is a high-level operator. The Administrator Level operator can complete all EMS tasks. User The user is a lower level operator. The user can complete all tasks EXCEPT the following: - Assign username & passwords (Topic 3.3 on page 21) - View and adjust ALL system control parameters (Topic 3.11 on page 34) -- Browse MIBs (Topic 3.21 on page 45) A system administrator must be assigned for each system. The administrator is responsible for controlling the personnel allowed to use EMS and their level of access. Since passwords are not visible, the administrator may allow multiple individuals to have Administrator Level access. These individuals would be able to utilize all EMS features, such as the Advanced MIB browser capability.

22 Connecting to the EMS Server Section 2 The initial administrator username is admin. This username cannot be removed. The password cannot be changed, either. Consult ADC personnel for the current admin password. 2.3 Connecting to the EMS Server After opening the web browser on a computer, enter the following in the URL line: 14 of EMS server>/opencell-ems/login.php where the <ipaddress of EMS server> is the IP address of the CXD/ NXD system Hubmaster. For more information on logging in to the system, refer to Topic 3.2, Login and Logout, on page 19.

23 3 USING EMS FOR NETWORK TASKS

24

25 USING EMS FOR NETWORK TASKS The section contains instructions for all tasks that can be executed using EMS. Please note that, while this section shows all steps required to complete each task, it does NOT discuss if the system values entered or changed are valid for a desired configuration. For proper configuration of the system, see ADCP , Digivance CXD Multi-Band Distributed Antenna System Operation Manual. 3.1 Master List of Tasks Table 2 lists important EMS tasks and tells where to look for instructions. Table 2: Master List of EMS Tasks YOU CAN SEE TOPIC Log in & log out. 3.2 on page 19 Assign usernames & passwords. 3.3 on page 21 View active alarms. 3.4 on page 23 View entire history of alarms. 3.5 on page 25 View a filtered list of alarms. 3.6 on page 25 View and adjust parameters related to Hub Nodes. 3.7 on page 27 View and adjust parameters related to RAN nodes. 3.8 on page 29 View and adjust parameters for BTS connections. 3.9 on page 31 View tenant sector node relationship on page 33 View and adjust parameters related to system control (e.g., gain) on page 34 View and adjust parameters related to trap interval and subnet ID on page 42 View system performance graphs (future release) on page 43 Set up system performance graphs (future release) on page 44 17

26 Master List of Tasks Section 3 Table 2: Master List of EMS Tasks (Continued) YOU CAN SEE TOPIC Browse MIBs on page 45 View Host Node information on page 46 All tasks can be completed on the system s Hubmaster. The only tasks that can be completed on any system node are browsing MIBs (3.21) and viewing Host Node Information (3.22). In most pages, there are buttons to display the information in a new window (Open in New Window button) and to display all data rows (View All Rows button). The Open in New Window button, as expected, displays the system data in a separate new window. This window can be manipulated like any standard window. 18 The View All Rows button allows the user to display all rows associated with the table. This is not recommended for normal viewing as some tables may become rather large (too many rows). The pages, by default, display just the system configured rows (active data), which is the most useful view during normal operations. Depending on the table, some system values may be displayed and changed. This manual identifies which system values can be changed (see Settable column in the upcoming tables). To change a value on a page (unless otherwise noted in this document): 1. Find a settable value to change. 2. If it s a pulldown, select the field and select the desired choice (the change is automatically executed). 3. If it s a field, select the field and enter in the desired value, then select Enter key on the computer keyboard. 4. The table will refresh showing the updated information.

27 Task-Based Reference Login and Logout 3.2 Login and Logout NOTE: EMS has two levels of operators, administrator and user, with each having a different introduction screen. For a summary of administrative functions, see Topic 2.2 on page 13. To display the login page 1. Enter the EMS url in the web browser address line. 2. The following screen appears (Figure 8). 19 Figure 8. EMS Login Page To Login 1. In the Username field, enter: <username> (where <username> is provided by System Administrator). 2. In the Password field, enter: <password> 3. In the Host field, enter: <ipaddress or hostname.domain of the desired node> NOTE: This is the IP address of the Hubmaster.

28 Login and Logout Section 3 4. Select the Login button. 5. If the operator enters a valid name and password, the introduction screen is displayed with a menu tree on the left side. The menu tree depends on the level of operator (administrator or user; see Topic 3.3 on page 21). NOTE: A login is successful if a valid username and password are entered (i.e., the hostname does not have to be valid). Entering a valid hostname is the responsibility of the user. 6. Figure 9 shows the introduction screen for an administrator. 20 Figure 9. Introduction Screen for Administrator 7. Figure 10 shows the introduction screen for a user (where the Advanced folder does not exist).

29 Task-Based Reference Assign Usernames and Passwords (Ad- Figure 10. Introduction Screen for User 21 To logout On the menu tree, select Logout. 3.3 Assign Usernames and Passwords (Administrator Level Only) An Administrator Level operator has the ability to add and delete EMS operators. If an operator password is forgotten, the administrator can remove and then re-add the operator. No passwords are viewable on the screen. NOTE: There are no password limitations such as for number of characters or type of characters that can be entered. Figure 11 shows the operator setup screen.

30 Assign Usernames and Passwords (Administrator Level Only) Section 3 22 Figure 11. Operator Setup Screen To add an EMS operator 1. On the menu tree, select Configuration-EMSSetup-Operators. 2. Enter username. 3. Enter password (remember the password it must be forwarded to the new EMS operator). 4. Select level of operator from pulldown menu. 5. Select Add button. To remove an EMS operator 1. On the menu tree, select Configuration-EMSSetup-Operators. 2. Find the user row you wish to remove. 3. Select Remove button.

31 Task-Based Reference View Active Alarms 3.4 View Active Alarms Active alarms are defined as any alarm received by the EMS within the past 10 minutes. The list is also sorted in descending chronological order and is automatically updated once a minute. The CXD/NXD system is designed to send traps to the EMS at a configurable rate. For best alarm viewing, ADC recommends that the system trap interval rate should be set at 10 minutes (600 seconds). To view active alarms 1. On the menu tree, select Alarms-ActiveAlarms. 2. The Alarm list should be displayed in less than five seconds. 23 Figure 12. Active Alarms 3. The Alarm List has several columns, described in Table 3.

32 View Active Alarms Section 3 Table 3: Alarm List 24 COLUMN ID DATE TIME REF # HUB/RAN ID PROBABLE CAUSE PROBLEM TENT SEVERITY DETAILS BUTTON DESCRIPTION A unique number to identify the alarm (for filter purposes). Date the trap is received by the EMS (CXD/NXD system date). Time the trap is received by the EMS (CXD/NXD system time). Reference number used to assist in troubleshooting (see ADCP , Digivance CXD/NXD SNMP Agent and Fault Isolation User Guide). Name of the Hub Node/RAN (as configured in the Ran Node and Hub Node Tables). A general phrase used to indicate the most probable reason for alarming. More detailed explanation of the issue at hand. If the alarm is associated with a given tenant/tenant sector, the tenant name is displayed here. Priority level of the alarm: Critical, Major, Minor, and Warning. The color of the row corresponds to the Severity : Critical (red) Major (orange) Minor (yellow) Warning (blue). Additional information related to the alarm can be displayed (e.g., Module location, MIB field fault value, etc). To view details 1. In the alarm list, for the desired alarm row, select the Details button. 2. The detailed trap information is displayed.

33 Task-Based Reference View Alarm History 3.5 View Alarm History Alarm history shows all the alarms within the EMS database (the latest seven days worth of alarms). The list is divided into pages to help in sorting through the alarms. Note that the Alarm History table does not update automatically. The alarm list will, however, update if the Previous or Next button is selected. To view alarm history 1. On the menu tree, select Alarms-All. 2. The Alarm list should be displayed in less than 30 seconds. 3. See Table 3 on page 24 for alarm table information. 4. If the displayed alarms are the most current alarms, only the Next button is available for selection. The Next button displays the next older set of alarms found in the alarm list (sorted by Trap ID). 5. If the displayed alarms are NOT the most current alarms, the Previous button is also available for selection. The Previous button displays the next most recent set of alarms found in the alarm list (sorted by Trap ID). To view details 1. For the desired alarm row, select the Details button. 2. The trap information is displayed View Filtered Alarm List Alarms may be filtered using simple or complex (more than one condition) logic. All conditions must be met for a successful search. To view a filtered alarm list 1. On the menu tree, select Alarms-Filter. 2. The Filter options should be displayed in less than five seconds. 3. Select desired options for filtering, and then select the Apply Filter button.

34 View Filtered Alarm List Section 3 26 Figure 13. Filtered Alarm List 4. Table 4 identifies the filtering options. They relate to columns found within the alarm table. Table 4: Filtered Alarm List Columns FILTER ALARM NUMBER DATE (START) DATE (END) TIME (START) DESCRIPTION Filter on the unique identifier. When filtering on alarm number, no other fields should be filled in. Default is all. The date to start filter range. If only one date is desired, fill both Date (Start) and Date (End) with the same date. Default is the current date. The date to end the filter range. If only one date is desired, fill both Date (Start) and Date (End) with the same date. Default is the current date. The time to start the filter range. The time is only related to a single date. Default is 0:00:01.

35 Task-Based Reference Hub Nodes Table 4: Filtered Alarm List Columns (Continued) FILTER TIME (END) REFERENCE NUMBER HUB / RAN ID CAUSE SEVERITY SORT DIRECTION LIMIT DESCRIPTION The time to end the filter range. The time is only related to a single date. Default is 23:59:59. The Reference Number used to assist in troubleshooting (See ADCP , Digivance CXD/NXD SNMP Agent and Fault Isolation Guide). This field is a pulldown menu. Default is all. The name of the hub/ran IDs identified in the NXD/CXD system.this field is a pulldown menu. Default is all. A general phrase used to indicate the most probable reason for alarming. This field is a pulldown menu. Default is all. Priority level of the alarm: Critical, Major, Minor, and Warning. Default is all. Filter either Ascending or Descending. Default is Descending. Limits the search to the number selected. If a search does not produce all the desired alarms, try increasing the limit. This field is a pulldown menu. Default is fifteen (15). 27 To view details (once query is complete) 1. For the desired alarm row, select Details button. 2. The trap information is displayed. 3.7 Hub Nodes The Hub Nodes table displays the Hub Nodes within the CXD/NXD system. These Hub Nodes have been automatically detected by the CXD/NXD system. Certain Hub Node values can be configured here. To view the Hub Node page 1. On the menu tree, select Configuration-Hub Nodes. 2. The table should be displayed in less than five seconds.

36 Hub Nodes Section 3 3. Table 5 describes the columns that are displayed. Table 5: Hub Nodes Columns COLUMN ME DESCRIPTION SET- ABLE UNITS Hub Node Index The number of Hub Nodes that can be detected within a system (128 Hub Nodes). No Hostname CPU name (name given at factory). No IP Address CPU address (address given to hub by Hubmaster). No Hub ID Field to enter unique identifier for the hub (customer format). CPU Rack ID Rack location of the Hub Node (customer N/A format). CPU Chassis ID Chassis location of the Hub Node (customer format). N/A 28 RF Rack ID Rack location of the RF chassis managed by this Hub Node (if applicable, customer format) N/A RF Chassis ID Chassis location of the RF chassis managed by this Hub Node (if applicable, customer format). N/A 2nd RF Rack ID In Generation 2 NXD/CXD hubs, this field N/A shows the rack location of the second RF chassis managed by this Hub Node (if applicable, customer format). 2nd RF Chassis ID In Generation 2 NXD/CXD hubs, this field N/A shows the chassis location of the second RF chassis managed by this Hub Node (if applicable, customer format). GPS Latitude Displays the GPS latitude value as detected by the RAN. If there is no GPS at the RAN, Decimal degrees this value can be modified manually.

37 Task-Based Reference RAN Nodes Table 5: Hub Nodes Columns (Continued) COLUMN ME DESCRIPTION SET- ABLE UNITS GPS Longitude Displays the GPS longitude value as detected by the RAN. If there is no GPS at the RAN, Decimal degrees this value can be modified manually. Clean Removes the hub from the list. Cleaning the Button node from the list may take several minutes. To confirm successful cleaning, view table again after several minutes. 3.8 RAN Nodes The RAN Nodes table displays the RANs within the CXD/NXD system. These RANs have been automatically detected by the CXD/NXD system. Certain RAN node values can be configured here. To view the RAN Node page 1. On the menu tree, select Configuration-Ran Nodes. 2. The table should be displayed in less than five seconds Table 6 describes the columns that are displayed. Table 6: RAN Nodes Columns COLUMN ME DESCRIPTION SET- ABLE UNITS Ran Node Index The number of RAN nodes that can be detected within a system (96 RANs). No Hostname CPU name (name given at factory). No IP Address CPU address (address give to RAN by Hubmaster). No RAN ID Field to enter unique identifier for the RAN (customer format).

38 RAN Nodes Section 3 Table 6: RAN Nodes Columns (Continued) COLUMN ME DESCRIPTION SET- ABLE UNITS Pole Field to enter in pole number (if applicablecustomer format). RUC1 PA1 Field to associate RUC module with a power amplifier. Note that this is for configuration/ alarming purposes. The installer needs to ensure the physical connection reflects this setup. RUC1 PA2 Field to associate RUC module with a power amplifier. RUC2 PA1 Field to associate RUC module with a power amplifier. RUC2 PA2 Field to associate RUC module with a power amplifier. 30 RDC{1-4} Multicoupler Field to associate an RDC module with a multicoupler (NXD) or low noise amplifier (CXD). Note that this is for configuration/ alarming purposes. The installer needs to ensure the physical connection reflects this setup. Disable Allows the ability to disable any RF power out of the RAN (regardless of tenant). Diversity Indicates if the RAN is configured with a sec- ond uplink for each tenant (Rx Diversity). GPS Latitude Displays the GPS latitude value as detected by the RAN. If there is no GPS at the RAN, Decimal degrees this value can be modified manually. GPS Longitude Displays the GPS longitude value as detected by the RAN. If there is no GPS at the RAN, Decimal degrees this value can be modified manually.

39 Task-Based Reference BTS connection Table 6: RAN Nodes Columns (Continued) COLUMN ME DESCRIPTION SET- ABLE UNITS Clean Removes the RAN node from the list. Clean- Button ing the node from the list may take several minutes. To confirm successful cleaning, view table again after several minutes. 3.9 BTS connection The BTS Connection table displays the connection information related to each tenant sector (band) within the system. At installation, most of the information has been automatically populated by the CXD/NXD system. Certain BTS Connection values can be configured here. To view the BTS Connection page 1. On the menu tree, select Configuration-BTS Connection. 2. The table should be displayed in less than five seconds. 3. Table 7 describes the columns that are displayed. 31 Table 7: BTS Connection Columns COLUMN ME DESCRIPTION SET- ABLE UNITS Tenant Index The number of tenant sectors (bands) that can be managed within a system (96). No Tenant Name Name given to the tenant sector (customer format). BTS ID Identifier given to the BTS connected to this tenant sector (customer format). BTS Sector Sector of the BTS used for this tenant sector (e.g., alpha, beta, gamma).

40 BTS connection Section 3 Table 7: BTS Connection Columns (Continued) COLUMN ME DESCRIPTION SET- ABLE UNITS Tenant Band Band of the tenant sector. BIM Bus I2C bus location of the tenant sector s BIM. No BIM Slot I2C slot of the tenant sector s BIM. No HDC (1-2) Bus I2C bus location of the tenant sector s HDCs. HDC (1-2) Slot I2C slot of the tenant sector s HDCs. FSC Bus I2C bus location of the tenant sector s FSC. FSC Slot I2C slot of the tenant sector s FSC. HUC Bus I2C bus location of the tenant sector s HUC. HUC Slot I2C slot of the tenant sector s HUC. 32 Composite Mode Indicates if the CXD/NXD system is in composite mode (a set of +42 db gain in the forward path). Default is enabled. Fullband Indicates if the tenant is using fullband HDCs. Default is fullband. Transmit Diversity Indicates if the tenant in the system is config- ured for a second downlink path (transmit diversity). Default is disabled. LSE Indicates if the tenant in the system is associ- ated with location services equipment (LSE). Default is disabled. Clean Removes the tenant information from the list. Button Clearing the node from the list may take several minutes. To confirm successful clearing, view table again after several minutes.

41 Task-Based Reference Tenant Sector-Node Relationship 3.10 Tenant Sector-Node Relationship The Tenant Sector-Node table displays the relationship between the tenant and the RAN nodes on which the tenant resides. Due to system simulcasting, up to eight RANs may be associated with a single tenant/tenant sector. This information is automatically populated by the CXD/NXD system. To view the Tenant Sector-Node page 1. On the menu tree, select Configuration-Relationship. 2. The table should be displayed in less than five seconds. 3. Table 8 describes the columns that are displayed. Table 8: Tenant Sector Node Columns COLUMN ME DESCRIPTION SET- ABLE UNITS Tenant Index The number of tenant sectors (bands) that can be managed within a system (96). No Tenant Info The pathtrace information related to the tenant sector (consists of tenant name, BTS ID, BTS sector, and tenant band). No 33 RAN ID {1-8} Identifier of a RAN that carries the subject tenant sector. The number is automatically assigned by the CXD/NXD system (the RANs appear in the order in which they were initially detected). Note that IDs that are bracketed ( [ ] ) indicate that the Hubmaster no longer relates that node to the tenant sector or cannot communicate with the node. View active alarms to troubleshoot. No WARNING! During normal operations, it is not recommended to adjust these parameters. Changing the number association may affect system gain, delay and attenuation through the given path.

42 System Control Parameters Section System Control Parameters Forward Gain The Forward Gain table displays the gain offset in the forward path for each tenant sector in the CXD/NXD system network. To view the Forward Gain page 1. On the menu tree, select Configuration-Control-GainFwd. 2. The table should be displayed in less than five seconds. 3. Table 9 describes the columns that are displayed. Table 9: Forward Gain Columns COLUMN ME DESCRIPTION SET- ABLE UNITS Tenant Index The number of tenant sectors (bands) that can be managed within a system (96). No 34 Tenant ID The pathtrace information related to the tenant sector (consists of tenant name, BTS ID, BTS sector, and tenant band). No RAN ID {1-8} Identifier of a RAN that carries the subject tenant sector. The number is automatically assigned by the CXD/NXD system (the RANs appear in the order in which they were initially detected). No RAN ID {1-8} Gain Offset The assigned gain offset through the given path. The system is balanced at startup. If a gain adjustment is required, this field may be changed (positive value for more gain and negative value for less gain, e.g., 10 = +1dB, - 20 = -2 db). 1/10 db Forward AGC Enables/Disables the Forward AutoGain Capability (for future use). Hub Overpower Protection (HOP) Indicates if the hub overpower protection is enabled. If it is enabled, the system will reduce the gain in the FSC in the presence of a larger than expected RF signal in the FSC output.

43 Task-Based Reference System Control Parameters Table 9: Forward Gain Columns (Continued) COLUMN ME DESCRIPTION SET- ABLE UNITS PA Overpower Protection (POP) Indicates if the power amplifier overpower protection is enabled. If it is enabled, the system will add attenuation at the RUC in the presence of a larger than expected RF signal at the PA Reverse Gain The Reverse Gain table displays the gain in the reverse paths for each tenant sector in the CXD/NXD system network. To view Reverse Gain page 1. On the menu tree, select Configuration-Control-Gain Rev. 2. The table should be displayed in less than five seconds. 3. Table 10 describes the columns that are displayed. Table 10: Reverse Gain Columns 35 COLUMN ME DESCRIPTION SET- ABLE UNITS Tenant Index The number of tenant sectors (bands) that can be managed within a system (96). No Tenant ID The pathtrace information related to the tenant sector (consists of tenant name, BTS ID, BTS sector, and tenant band). No Reverse Gain The targeted reverse gain for each tenant sector path. Default is 100 (10 db). 1/10 db Cable Loss Loss of the cable connected from the BIM to the BTS. This value is factored into the overall reverse system gain (along with the Reverse gain). 1/10 db Reverse AGC Enables/Disables the Reverse AutoGain Capability.

44 System Control Parameters Section Delay The Delay table displays the delay information for each tenant sector in the CXD/ NXD system network. To view the Delay page 1. On the menu tree, select Configuration-Control-Delay. 2. The table should be displayed in less than five seconds. 3. Table 11 describes the columns that are displayed. Table 11: Delay Columns COLUMN ME DESCRIPTION SET- ABLE UNITS Tenant Index The number of tenant sectors (bands) that can be managed within a system (96). No 36 Tenant ID Reverse Skew The pathtrace information related to the tenant sector (consists of tenant name, BTS ID, BTS sector, and tenant band). Adds the amount of skew for each reverse path. The skew is the amount of time added to the RAN, to vary the delays of simulcasted signals back to the BTS. For example, if the skew is set to 2us and the target delay is 100us., RF signals from RAN ID -1 will have a total delay of 100us, RAN ID-2 will have 102us, RAN ID-3 will have 104us, etc. The total delay already INCLUDES the fiber delay. No us Reverse Target The total delay for each path (except the skew). The default is (100us). us Reverse Delay Compensation Enables/Disables the automated delay processing. When this is disabled, the delay may be changed for a given reverse path HOWEVER, any delay change must be made at the SIF MIB on the appropriate node via the MIB Browser (not recommended).

45 Task-Based Reference RAN Disable Table 11: Delay Columns (Continued) COLUMN ME DESCRIPTION SET- ABLE UNITS Forward Skew Adds the amount of skew for each forward path. The skew is the amount of time added to each RAN to vary the delays of simulcasted signals back to the BTS. For example, if the skew is set to 2us and the target delay is 100us., RF signals to RAN ID -1 will have a total delay of 100us, RAN ID-2 will have 102us, RAN ID-3 will have 104us, etc. The total delay already INCLUDES the fiber delay. us Forward Target The total delay for each forward path (except the skew). The default is (100us). us Forward Delay Compensation Enables/Disables the automated delay processing. When this is disabled, the delay may be changed for a given forward path HOW- EVER, any delay change must be made at the SIF MIB on the appropriate node via the MIB Browser (not recommended) RAN Disable The RAN Disable table displays the RANs related to each tenant sector in the CXD/NXD system network and whether the power amplifier is on or off. To view the RAN Disable page 1. On the menu tree, select Configuration-Control-RANDisable. 2. The table should be displayed in less than five seconds. 3. Table 12 describes the columns that are displayed. Table 12: RAN Disable Columns COLUMN ME DESCRIPTION SET- ABLE UNITS Tenant Index The number of tenant sectors (bands) that can be managed within a system (96). No

46 RUC (Administrator Level Only) Section 3 Table 12: RAN Disable Columns (Continued) COLUMN ME DESCRIPTION SET- ABLE UNITS Tenant ID The pathtrace information related to the tenant sector (consists of tenant name, BTS ID, BTS sector, and tenant band). No RAN ID {1-8} Identifier of a RAN that carries the subject tenant sector. The number is automatically assigned by the CXD/NXD system (the RANs appear in the order in which they were initially detected). No RAN ID {1-8} Disable Indication if the PA at this RAN is enabled or disabled RUC (Administrator Level Only) 38 The RUC table displays the attenuation offset for at the RUC for each RAN. Since the main gain adjustment is completed via Section , only the Administrator Level is able to access this table (troubleshooting purposes). To view the RUC page 1. On the menu tree, select Configuration-Control-RUC. 2. The table should be displayed in less than five seconds. 3. Table 13 describes the columns that are displayed. Table 13: RUC Columns COLUMN ME DESCRIPTION SET- ABLE UNITS Tenant Index The number of tenant sectors (bands) that can be managed within a system (96). No Tenant ID The pathtrace information related to the tenant sector (consists of tenant name, BTS ID, BTS sector, and tenant band). No

47 Task-Based Reference RDC (Administrator Level Only) Table 13: RUC Columns (Continued) COLUMN ME DESCRIPTION SET- ABLE UNITS RAN ID {1-8} Identifier of a RAN that carries the subject tenant sector. The number is automatically assigned by the CXD/NXD system (the RANs appear in the order in which they were initially detected). No RAN ID {1-8} RUC Attenuation Offset The attenuation offset for the RUC module at each RAN. Note: a positive value adds attenuation and reduces system gain, while a negative value removes attenuation and adds system gain e.g., 70 = +7dB attenuation. No 1/10 db 3.14 RDC (Administrator Level Only) The RDC table displays the attenuation offset at the RDC for each RAN. Since the main gain adjustment is completed via Section , only the Administrator Level is able to access this table (troubleshooting purposes). To view the RDC page On the menu tree, select Configuration-Control-RDC. 2. The table should be displayed in less than five seconds. 3. Table 14 describes the columns that are displayed. Table 14: RDC Columns COLUMN ME DESCRIPTION SET- ABLE UNITS Tenant Index The number of tenant sectors (bands) that can be managed within a system (96). No Tenant ID The pathtrace information related to the tenant sector (consists of tenant name, BTS ID, BTS sector, and tenant band). No

48 HDC (Administrator Level Only) Section 3 Table 14: RDC Columns (Continued) COLUMN ME DESCRIPTION SET- ABLE UNITS RAN ID {1-8} Identifier of a RAN that carries the subject tenant sector. The number is automatically assigned by the CXD/NXD system (the RANs appear in the order in which they were initially detected). No RAN ID {1-8} RDC Attenuation Offset Primary The attenuation offset for the RDC module at each RAN (primary path). Note: a positive value adds attenuation and reduces system gain, while a negative value removes attenuation and adds system gain. 1/10 db RAN ID {1-8} RDC Attenuation Offset Diversity The attenuation offset for the RUC module at each RAN (diversity path- if applicable). 1/10 db HDC (Administrator Level Only) The HDC table displays the attenuation offset at the HDC for each carrier (note: in typical scenario of a fullband HDC use, only carrier 1 is used). Since the main gain adjustment is completed via Section , only the Administrator Level is able to access this table (troubleshooting purposes). To view the HDC page 1. On the menu tree, select Configuration-Control-HDC. 2. The table should be displayed in less than five seconds. 3. Table 15 describes the columns that are displayed. Table 15: HDC Columns COLUMN ME DESCRIPTION SET- ABLE UNITS Tenant Index The number of tenant sectors (bands) that can be managed within a system (96). No

49 Task-Based Reference FSC (Administrator Level Only) Table 15: HDC Columns (Continued) COLUMN ME DESCRIPTION SET- ABLE UNITS Tenant ID The pathtrace information related to the tenant sector (consists of tenant name, BTS ID, BTS sector, and tenant band). No HDC Ch {1-4} Attenuation Offset Attenuation offset for each carrier in the HDC module. Note: a positive value adds attenuation and reduces system gain, while a negative value removes attenuation and adds system gain. 1/10 db 3.16 FSC (Administrator Level Only) The FSC table displays the gain information for each FSC associated with a tenant sector. Since the main gain adjustment is completed via Section , only the Administrator Level is able to access this table (troubleshooting purposes). To view the FSC page 1. On the menu tree, select Configuration-Control-FSC. 2. The table should be displayed in less than five seconds Table 16 describes the columns that are displayed. Table 16: FSC Columns COLUMN ME DESCRIPTION SET- ABLE UNITS Tenant Index The number of tenant sectors (bands) that can be managed within a system (96). No Tenant ID The pathtrace information related to the tenant sector (consists of tenant name, BTS ID, BTS sector, and tenant band). No

50 Network Parameters Section 3 Table 16: FSC Columns (Continued) COLUMN ME DESCRIPTION SET- ABLE UNITS Output Gain The gain offset through the FSC module. The FSC has a gain of 12 db. The offset adjusts the this value (e.g., -30 = -3dB offset, which means there is 12 3 = 9 db gain through the FSC). Note that this value cannot be changed when the Output Gain Override is disabled. 1/10 db Output Gain Override In certain circumstances & configurations, the automated output gain needs to be overridden. When this is enabled, the Output Gain can be manipulated Network Parameters 42 The Network table displays miscellaneous data related to the CXD/NXD system network. To view the Network Parameters page 1. On the menu tree, select Configuration-Network. 2. The table should be displayed in less than five seconds. 3. Table 17 describes the columns that are displayed. Table 17: Network Parameters Columns COLUMN ME DESCRIPTION SET- ABLE UNITS Trap Interval The rate at which traps are sent from the CXD/NXD system to the EMS/NMS. Suggest setting the trap interval to 600 seconds. No Sec Subnet ID Name given to the system subnet (customer preference and format). This is useful in an NMS scenario when a NMS is receiving traps from multiple systems.

51 Task-Based Reference View System Performance Graphs 3.18 View System Performance Graphs NOTE: This topic describes a future feature of the EMS software not provided by the current version. EMS has the capability to display performance graphs. The graphs can be created to track system performance such as RF signal strength, temperature, fan speed, etc. To View Graphs: 1. On the menu tree, select Performance-Graphs. 2. The graphing page should be displayed in less than 5 seconds. 3. Select the Graphs tab. 4. If graphs have been created, select the desired graph. 5. The graph is displayed. 6. Figure 14 shows a sample graph for RF signal strength. 43 Figure 14. System Performance Graphs

52 Setup System Performance Graphs Section Setup System Performance Graphs NOTE: This topic describes a future feature of the EMS software not provided by the current version. To complete the graphing capabilities, a shareware application has been embedded into the EMS software (Cacti). For further information related to creating system performance graphs, see the Cacti User Manual ( documentation.php). The user has the capability to select MIB fields to trend, adjust x and y axis, change colors, rename titles and labels, and more System Performance Tables Forward RF Power The Forward RF Power table displays the RF signal power at the input of the RAN (SIF) and at the output of the RAN (PA). To view the Forward RF Power page On the menu tree, select Performance-Power-Fwd. 2. The table should be displayed in less than five seconds. 3. Table 18 describes the columns that are displayed. Table 18: Forward RF Power Columns COLUMN ME DESCRIPTION SET- ABLE UNITS Tenant Index The number of tenant sectors (bands) that can be managed within a system (96). No Tenant ID The pathtrace information related to the tenant sector (consists of tenant name, BTS ID, BTS sector, and tenant band). No FSC Power The RF signal power at the output of the FSC at Hub Node. No 1/10 db

53 Task-Based Reference Browse MIBs (Administrator Level Table 18: Forward RF Power Columns (Continued) COLUMN ME DESCRIPTION SET- ABLE UNITS RAN ID {1-8} Identifier of a RAN that carries the subject tenant sector. The number is automatically assigned by the CXD/NXD system (the RANs appear in the order in which they were initially detected). No Sec RAN ID {1-8} SIF The RF signal power at the input of the RAN (SIF). No 1/10 db RAN ID {1-8} Output The RF signal power at the output of the RAN (PA reading). No 1/10 db NOTE: The powers do NOT update automatically. To refresh, the user must view the Forward RF Power page again Browse MIBs (Administrator Level Only) EMS has the capability to display ALL system data (and set any configurable parameters). Since the amount of system data can be overwhelming (and used only in complex troubleshooting activities), the feature is only available at the Administrator Level. Note that the user can browse MIBs on any node in the system. 45 To use the MIB Browser 1. On the menu tree, select Advanced-MIB Browser. 2. Select MIBs associated with ADC CXD/NXD. 3. There will be a large number of MIB tables to display. It is up to the user to know which MIB table carries the desired data. The table, when selected, is displayed in a single column. Understanding tenant and MIB indexes is critical in digesting the data. For further assistance, see Section 7 of ADCP , Digivance CXD Multi-Band Distributed Antenna System Operation Manual.

54 Host Node Information Section 3 To view MIBs on different node 1. While in MIB Browser, select Host. 2. Enter desired IP or hostname.node. 3. The MIB Browser is displayed for the desired domain. NOTE: Only the MIB Browser host is changed. To continue viewing information from the logged in host, select any option on the menu tree (on the left side of the display) Host Node Information If the operator forgets what node that is logged into, the operator can find out by accessing this table. 46 To view the Host Node Information page: 1. On the menu tree, select HostNodeInfo. 2. The table should be displayed in less than five seconds. 3. Table 19 describes the columns that are displayed.

55 Task-Based Reference Host Node Information Table 19: Host Node Columns COLUMN ME DESCRIPTION SET- ABLE UNITS Device Description Identifies information related to the logged in device. No Node Hostname Hostname of the logged in CPU (set at factory). No IP Address IP address of the logged in CPU (set by the Hubmaster). No Site ID The RAN or Hub ID of the logged in CPU. No Subnet ID Indication of the subnet ID for the logged in CPU. No CPU Unsolicited Reset CPU Watchdog Reset Indicates if an unsolicited reset has occurred (Reference #5). To clear the alarm ( Reset Occurred ), the user must log into the affected node and select No Reset in this field. Indicates if an unsolicited reset has occurred (Reference #4). To clear the alarm ( Reset Occurred ), the user must log into the affected node and select No Reset in this field. 47

56 Troubleshooting Section Troubleshooting In case of EMS problems, refer to the following guidelines: 48 System Value Not Being Set: The most likely cause of this problem is not with EMS, but a parameter has been changed to a value outside the expected range. Check the Operations Manual for the proper range of the parameter. Seeing No Communication or php file Errors in the Configuration Tables: The SNMP read/write communities are most likely not set up. Go to Configuration-EMS Setup-SNMP and ensure the read community is public and the write community is patriots. Another possible reason for No Communication is that the logged-in host name is not valid. Check the Host Node Info for valid information. If there is no valid data, logout and try logging in to a valid hostname. Not Seeing any Active Alarms: This may occur in several situations: - The system has no alarms. - EMS was not correctly setup to receive traps. See ADCP , Digivance CXD/NXD SNMP Agent and Fault Isolation User Guide (section 7.7.3) for details on setting up a SNMP version 2 trap sink to the Hubmaster. - EMS did not start up properly. Telnet into the Hubmaster and check if the trap receiver is running (ps ax grep snmptrapd). The following line should appear: tclsh /usr/lib/opencell-ems-web/snmptrapd.tcl. If not, execute the following command: sudo /etc/init.d/opencell-ems-web start Do Not See the Login Window: Check with the System Administrator that EMS is enabled for the system. If so, confirm that the IP address is correct for the Hubmaster. Doublecheck the entered url on the web browser. Successfully Logged In But No Data is Displayed: Confirm that the hostname logged into is the desired IP address/hostname.domain.

57 4 ALARM REFERENCE

58

59 EMS ALARM REFERENCE 4.1 Introduction This section lists the possible displayed alarms for the CXD/NXD system. The alarms are explained in a large table (starting on the next page). The table has the following columns: Reference #: The identifier as seen in ADCP , Digivance CXD/ NXD SNMP Agent and Fault Isolation User Guide. It represents a pair of trap ids one for the fault and one for the clear. Trap #: The identifier of the SNMP trap received by the EMS. This is the cross reference from the trap to the reference #. Probable Cause: A general category to provide a quick understanding of the issue at hand. This category is CCITT X.733 compliant. Problem: More detailed description of the issue and possible affected module. Severity: A level of importance. This category and the definitions of each level are X.733 compliant. In EMS, alarms are rated as to their importance using severity levels. The severity levels, based on CCITT ITU X.733, are as follows: Critical: Service affecting condition has occurred and an immediate corrective action required (managed object out of service). Major: Service affecting condition has developed and an urgent corrective action is required (managed object in severe degradation). Minor: Non service affecting condition and corrective action should be taken in order to prevent a more serious fault. Warning: Potential or impending service affecting fault. Also configuration related faults. 51

60 Alarm Reference Table Section Alarm Reference Table Table 20 lists all the possible alarms to be displayed. EMS should be used in conjunction with ADCP , Digivance CXD/NXD SNMP Agent and Fault Isolation User Guide to resolve any alarm. Table 20: Alarm Reference Table REF TRAP # PROBABLE CAUSE PROBLEM SEVERITY 1 1 Enclosure Door Open No communication to door sensor Major RAN door is open 2 Ran door is closed 2 3 Power Problem No communication with backup batteries Major Backup battery in use 4 Backup battery no longer in use 3 5 Power Problem One or more expected power entry modules is not present Major Low DC output Low AC input High AC input High battery area temperature High DC output No AC power detected 52 6 RAN Input Power OK 4 7 Processor Problem Internal CPU reset Minor 8 Internal reset acknowledged 5 9 Processor Problem External CPU reset Minor 10 External reset acknowledged

61 EMS Alarm Reference Alarm Reference Table Table 20: Alarm Reference Table (Continued) REF TRAP # PROBABLE CAUSE PROBLEM SEVERITY 6 11 Power Protection Chassis Power Supply - No communication to the supply Major Power Supply - One or more running in a degraded state Power Supply - One or more has failed 12 Chassis power supply OK 7 13 Threshold Exceeded Reverse noise fault- Expected noise floor outside range on primary path Major Reverse noise fault- Expected noise floor outside range on diversity path Reverse noise fault- Expected noise floor outside range on primary AND diversity paths 14 Reverse Noise test OK 8 15 Threshold Exceeded Reverse RAN Tone- Generated test tone below expected range on primary path Minor Reverse RAN Tone- Generated test tone below expected range on diversity path Reverse RAN Tone- Generated test tone below expected range on primary AND diversity paths 16 Reverse RAN tone test OK 53

62 Alarm Reference Table Section 7 Table 20: Alarm Reference Table (Continued) REF TRAP # PROBABLE CAUSE PROBLEM SEVERITY 9 17 Threshold Exceeded Reverse BIM tone- Generated test tone below expected range on primary path Minor Reverse BIM tone- Generated test tone below expected range on diversity path Reverse BIM tone- Generated test tone below expected range on primary AND diversity paths 18 Reverse BIM Tone Test OK Loss of Signal Forward Path- Lost relationship with one or more modules Minor Forward Path- Missing one or more expected paths (Tx Diversity) 20 Forward Path OK Loss of Signal Reverse Primary Path-Lost relationship with one or more modules Minor Reverse Primary Path-Missing one or more expected primary paths 22 Reverse Primary Path OK Loss of Signal Reverse Diversity Path-Lost relationship with one or more modules Minor 54 Reverse Diversity Path-Missing one or more expected diversity paths 24 Reverse Diversity Path OK

63 EMS Alarm Reference Alarm Reference Table Table 20: Alarm Reference Table (Continued) REF TRAP # PROBABLE CAUSE PROBLEM SEVERITY Timing Problem Detected path delay outside expected range Minor 26 Delay OK Detected base delay is outside expected range Target delay is outside expected range Delay skew outside expected range Equipment Malfunction GPS - Expected hardware not detected or hardware detects a fault Minor 28 GPS OK Equipment malfunction GPS - There is an open line detected to the antenna GPS - There is a short detected to the antenna Minor 30 Antenna Feedline OK Loss of Signal SIF - Hub to RAN to Hub optical loopback test failed Critical 32 SIF Loopback test passed Timing Problem SIF - 42MHz Unlocked Critical 34 SIF - 42MHz Locked Timing Problem SIF - 155MHz Unlocked Critical 36 SIF - 155MHz Locked Comm Subsystem Failure STF - I2C Bus A Fault Major 38 STF - I2C Bus A OK Comm Subsystem Failure STF - I2C Bus B Fault Major 38 STF - I2C Bus B OK

64 Alarm Reference Table Section 7 Table 20: Alarm Reference Table (Continued) REF TRAP # PROBABLE CAUSE PROBLEM SEVERITY Comm Subsystem Failure STF - I2C Bus C Fault Major 38 STF - I2C Bus C OK Comm Subsystem Failure STF - I2C Bus D Fault Major 38 STF - I2C Bus D OK Degraded Signal BIM - Forward Continuity Fault Minor BIM - Reverse Continuity Fault 40 BIM - Continuity OK Configuration Error BIM - No Pathtrace Warning BIM - Invalid Pathtrace BIM - Unsupported Band 42 BIM - Configuration OK Degraded Signal FSC - Forward Continuity Fault Minor 44 FSC - Continuity OK Configuration Error FSC - No Pathtrace Warning FSC - Invalid Pathtrace 46 FSC - Configuration OK Degraded Signal HDC - Forward Continuity Fault Minor HDC - Continuity OK Configuration Error HDC No Pathtrace Warning HDC - Invalid Pathtrace HDC - Band Mismatch HDC - Unsupported Band HDC - Bandwidth Mismatch 50 HDC - Configuration OK

65 EMS Alarm Reference Alarm Reference Table Table 20: Alarm Reference Table (Continued) REF TRAP # PROBABLE CAUSE PROBLEM SEVERITY Timing Problem HDC Carrier 1 Unlocked Critical 52 HDC Carrier 1 Locked Timing Problem HDC Carrier 2 Unlocked Major 52 HDC Carrier 2 Locked Timing Problem HDC Carrier 3 Unlocked Major 52 HDC Carrier 3 Locked Timing Problem HDC Carrier 4 Unlocked Major 52 HDC Carrier 4 Locked Timing Problem HRM - Clock Reference Unlocked Critical 54 HRM - Clock Reference Locked Degraded Signal HUC - Reverse Continuity Fault Minor 56 HUC - Continuity OK Configuration Error HUC - No Pathtrace Warning HUC - Invalid Pathtrace HUC - Band Mismatch HUC - Pathtrace Mismatch HUC - Invalid Address 58 HUC - Configuration OK Timing Problem HUC - Unlocked Critical 60 HUC - Locked Power Problem PSI - Voltage Fault Major 64 PSI - Voltage OK

66 Alarm Reference Table Section 7 Table 20: Alarm Reference Table (Continued) REF TRAP # PROBABLE CAUSE PROBLEM SEVERITY Loss of Signal RSC - Expected input is invalid Major RSC - The number of identified primary and diversity paths are not equal 66 RSC - Configuration OK Loss of Signal RSC Primary Output Disabled Critical 68 RSC Primary Output Enabled Loss of Signal RSC Diversity Output Disabled Critical 68 RSC Diversity Output Enabled Degraded Signal RDC - Reverse Continuity Fault Minor 70 RDC - Continuity OK Configuration Error RDC - No Pathtrace Warning RDC - Invalid Pathtrace RDC - Band Mismatch RDC - Unsupported Band 72 RDC - Configuration OK Timing Problem RDC - Unlocked Critical 74 RDC - Locked Timing Problem RUC - 18 MHz Unlocked Critical RUC - 18 MHz Locked Timing Problem RUC - 42 MHz Unlocked Critical 78 RUC - 42 MHz Locked Timing Problem RUC - Unlocked Critical 80 RUC - Locked Timing Problem RUC - Unlocked Critical 82 RUC - Locked

67 EMS Alarm Reference Alarm Reference Table Table 20: Alarm Reference Table (Continued) REF TRAP # PROBABLE CAUSE PROBLEM SEVERITY Degraded Signal PA - Continuity Fault Warning 82 PA - Continuity OK Degraded Signal PA - Continuity Fault Warning 82 PA - Continuity OK Power Problem PA Power Supply identifies an internal fault Critical 84 PA - Power Supply OK Power Problem PA Power Supply identifies an internal fault Critical 84 PA - Power Supply OK Equipment Malfunction STF - Missing Minor 86 STF - Present Loss of Signal SIF - Optical Rx Unlocked Critical 88 SIF - Optical Rx Locked Loss of Signal SIF - Optical Tx Unlocked Critical 90 SIF - Optical Tx Locked Degraded Signal RUC - Forward Continuity Fault Warning 92 RUC - Continuity OK Degraded Signal RUC - Forward Continuity Fault Warning 92 RUC - Continuity OK Configuration Error RUC - No Pathtrace Warning RUC - Invalid Pathtrace RUC - Band Mismatch RUC - Unsupported Band 94 RUC - Configuration OK

68 Alarm Reference Table Section 7 Table 20: Alarm Reference Table (Continued) REF TRAP # PROBABLE CAUSE PROBLEM SEVERITY Configuration Error RUC - No Pathtrace Warning RUC - Invalid Pathtrace RUC - Band Mismatch RUC - Unsupported Band 94 RUC - Configuration OK Power Problem PA - Input voltage outside expected range Critical 96 PA - Voltage OK Equipment Malfunction PA - Input voltage outside expected range Critical 96 PA - Voltage OK Equipment Malfunction BIM - Present Critical 98 BIM - Missing Equipment Malfunction HDC - Present Critical 100 HDC - Missing Equipment Malfunction FSC - Present Critical 102 FSC - Missing Equipment Malfunction SIF - Present Critical 104 SIF - Missing Equipment Malfunction RUC - Present Critical 106 RUC - Missing

69 EMS Alarm Reference Alarm Reference Table Table 20: Alarm Reference Table (Continued) REF TRAP # PROBABLE CAUSE PROBLEM SEVERITY Equipment Malfunction RDC - Present Critical 108 RDC - Missing Equipment Malfunction RSC - Present Critical 110 RSC - Missing Equipment Malfunction HUC - Present Critical 112 HUC - Missing Threshold Crossed PA - Overpower Protection is active (attenuation has been automatically added) Minor PA - Overpower Protection is in recovery (added attenuation being removed) 114 PA - Overpower Protection Not Active Threshold Crossed PA - Overpower Protection is active (attenuation has been automatically added) Minor PA - Overpower Protection is in recovery (added attenuation being removed) 114 PA - Overpower Protection Not Active Degraded Signal FSC - Channel 1 detects high power signal Major 114 FSC - Channel 1 input OK

70 Alarm Reference Table Section 7 Table 20: Alarm Reference Table (Continued) REF TRAP # PROBABLE CAUSE PROBLEM SEVERITY Degraded Signal FSC - Channel 2 detects high power signal Minor 116 FSC - Channel 2 input OK Degraded Signal FSC - Channel 3 detects high power signal Minor 116 FSC - Channel 3 input OK Degraded Signal FSC - Channel 4 detects high power signal Minor 116 FSC - Channel 4 input OK Degraded Signal FSC - Channel 5 detects high power signal Minor 116 FSC - Channel 5 input OK Degraded Signal FSC - Channel 6 detects high power signal Minor 116 FSC - Channel 6 input OK Degraded Signal FSC - Channel 7 detects high power signal Minor 116 FSC - Channel 7 input OK Degraded Signal FSC - Channel 8 detects high power signal Minor FSC - Channel 8 input OK Threshold Crossed FSC - Output overpower protection is active (attenuation has been automatically added) FSC - Output overpower protection is in recovery (added attenuation is being removed) 118 Hub - Overpower Protection Not Active Major

71 EMS Alarm Reference Alarm Reference Table Table 20: Alarm Reference Table (Continued) REF TRAP # PROBABLE CAUSE PROBLEM SEVERITY Configuration Error FSC - FPGA successfully loaded Warning FSC - FPGA load failed FSC - Identified FPGA version not the expected version 120 FSC - FPGA OK FSC - FPGA Loading Prom HUC - FPGA successfully loaded Warning HUC - FPGA load failed HUC - Identified FPGA version not the expected version 122 HUC - FPGA OK HUC - FPGA Loading Prom Configuration Error RDC - FPGA successfully loaded Warning RDC - FPGA load failed RDC - Identified FPGA version not the expected version 124 RDC - FPGA OK RDC - FPGA Loading Prom Configuration Error RUC - FPGA successfully loaded Warning RUC - FPGA load failed RUC - Identified FPGA version not the expected version RUC - FPGA OK RUC - FPGA Loading Prom Power Problem Hub Power Supply Fault Minor 128 Hub Power Supply OK

72 Alarm Reference Table Section 7 Table 20: Alarm Reference Table (Continued) REF TRAP # PROBABLE CAUSE PROBLEM SEVERITY Power Problem Hub Power Supply Degraded Minor 130 Hub Power Supply Degradation OK Degraded Signal FSC - Channel 1 has detected a low RF input signal Warning 132 FSC - Channel 1 OK Degraded Signal FSC - Channel 2 has detected a low RF input signal Warning 132 FSC - Channel 2 OK Degraded Signal FSC - Channel 3 has detected a low RF input signal Warning 132 FSC - Channel 3 OK Degraded Signal FSC - Channel 4 has detected a low RF input signal Warning 132 FSC - Channel 4 OK Degraded Signal FSC - Channel 5 has detected a low RF input signal Warning 132 FSC - Channel 5 OK Degraded Signal FSC - Channel 6 has detected a low RF input signal Warning FSC - Channel 6 OK Degraded Signal FSC - Channel 7 has detected a low RF input signal 132 FSC - Channel 7 OK Degraded Signal FSC - Channel 8 has detected a low RF input signal 132 FSC - Channel 8 OK Warning Warning

73 EMS Alarm Reference Alarm Reference Table Table 20: Alarm Reference Table (Continued) REF TRAP # PROBABLE CAUSE PROBLEM SEVERITY Comm Subsystem Failure PIC - No communications with the PA control module Critical 134 PIC Communications OK Comm Subsystem Failure PIC - No communications with the PA control module Critical 134 PIC Communications OK Threshold Crossed PA - VSWR test has failed Major 136 PA - VSWR Test OK Threshold Crossed PA - VSWR test has failed Major 136 PA - VSWR Test OK 65

74 Alarm Reference Table Section 7 Table 20: Alarm Reference Table (Continued) REF TRAP # PROBABLE CAUSE PROBLEM SEVERITY Equipment Malfunction RAN Alarm from Hub: HDC PLL Out of Lock RAN Alarm from Hub: HUC PLL Out of Lock RAN Alarm from Hub: FSC ADC Overflow RAN Alarm from Hub: RSC Output Disabled RAN Alarm from Hub: RGC BIM Tone Fault RAN Alarm from Hub: BIM Missing RAN Alarm from Hub: HDC Missing RAN Alarm from Hub: FSC Missing RAN Alarm from Hub: RSC Missing RAN Alarm from Hub: HUC Missing Major RAN Trap received from Hub cleared Equipment Malfunction RAN - Dry contact triggered 140 RAN Dry contact cleared Major Equipment Malfunction RAN - L has failed internal test Major 142 RAN - L OK

75 EMS Alarm Reference Alarm Reference Table Table 20: Alarm Reference Table (Continued) REF TRAP # PROBABLE CAUSE PROBLEM SEVERITY Equipment Malfunction RAN - L has failed internal test 142 RAN - L OK 67

76 Alarm Reference Table Section 7 68

77 CRONYMS AC Alternating Current ANT Multiband Antenna APEC AC Power Entry Card ASCII American Standard Code for Information Interchange Atten Attenuation BER Bit Error Rate BIF Backplane Interface BIM Base Station Interface Module BTS Base Transceiver Station C Centigrade C/MCPLR Cellular Multicoupler CAN Controller Area Network CCITT X.733 International Telegraph and Telephone Consultative Committee Recommendation X.733: Information Technology - Open Systems Interconnection - Systems Management: Alarm Reporting Function CDRH Center for Devices and Radiological Health CD-ROM Compact Disk Read Only Memory CDP Cellular Diplexer Config Configuration CPCIP SCPCI Power Supply CPU Central Processing Unit CTP Cellular Triplexer CXD Compact RAN Product Line (formerly OpenCell) DAS Distributed Antenna System db(fs) decibals (Full Scale digital reading) DC Direct Current DCE Data Communications Equipment DHCP Dynamic Host Configuration Protocol Div Diversity DNS Domain Name Service DPEC DC Power Entry Card Page 69

78 EB EHUB EIA EMS ESD F FCC FGC FPGA FSC Fwd GUI HDC HRM HUC IB IC I2C LED L LSE LVD MHz MI MIB MTBF NMS NOC Node NXD PA PA800 PA1900 PASMR PC PCI PCS PDU References: External Battery Ethernet Hub Electronic Industries Association Element Management System Electrostatic Discharge Fahrenheit Federal Communications Commission Forward Gain Control Field Programmable Gate Array Forward Simulcast Card Forward Graphical User Interface Hub Down Converter Hub Reference Module Hub Up Converter Internal Battery Industry Canada Inter IC (integrated circuits) bus Light Emitting Diode Low Noise Amplifier Location Services Equipment Low Voltage Disconnect Mega Hertz Maintenance Interface Management Information Base (SNMP Data Structure) Mean Time Between Failure Network Management System Network Operations Center Any CPU in the Digivance CXD system Digivance Neutral Host Product Line (formerly OpenCell) Power Amplifier Power Amplifier (800 MHz) Power Amplifier (1900 MHz) Power Amplifier (SMR) Personal Computer Peripheral Component Interconnect bus Personal Communications System Power Distribution Unit Page 70

79 Acronyms PLL Phase Locked Loop P/MCPLR PCS Multicoupler PQP PCS Quadplexer Prg Program PROM Programmable Read Only Memory Pwr Power RAN Radio Access Node RAN RAN, Tenant 1 3 RDC RAN Down Converter Rev Reverse RF Radio Frequency RGC Reverse Gain Control RIC RF Assembly Interface Controller RMA Return Material Authorization RMS Root Mean Square RPS RAN CompactPCI Power Supply RSC Reverse Simulcast Card RUC RAN Up Converter (Dual) RX Receive or Receiver SIF Synchronous Interface SNMP Simple Network Management Protocol STF System Interface TX Transmit or Transmitter UL Underwriters Laboratories VAC Volts Alternating Current VDC Volts Direct Current VSWR Voltage Standing Wave Ratio WBDOT Wide Band Optical Transport (see SIF) Page 71

80 References: Page 72

81 NDEX A acronyms 69 alarm reference table 52 alarm severity 24 B browse MIBs 45 BTS connection table 31 C Comm Subsystem Failure 55, 65 common use scenarios 7 Configuration Erro 60 Configuration Error 56, 57, 58, 59, 63 connecting to EMS server 14 CXD/NXD SNMP Agent and Fault Isolation Guide 6 CXD/NXD system operation manual 4 D Degraded Signal 56, 57, 58, 59, 61, 62, 64 E EMS as used at host/remote installation 7 as used with multiple hosts 8 common use scenarios 7 system requirements 13 user interfaces 8 EMS tasks, overview 7 EMS user interface 7 Enclosure Door Open 52 Equipment Malfunction 55, 59, 60, 66 Ethernet switch 7 F filtered alarm list 25 forward RF power table 44 G GET, SET, and TRAP 6 H HDC table 40 host node information 46 Hub Nodes table 27 L list of acronyms 69 Loss of Signal 54, 55, 58 M master list of tasks 17 N network parameters 42 O Open in New Window 18 P Power Problem 52, 57, 59, 60, 63, 64 Power Protection 53 Processor Problem 52 R Ran nodes table 29 Related publications iii RUC table 38 S severity of alarms 24 SNMP 5 system description 3 system diagram 3 system performance graphs 43 system performance tables 44 system requirements 13 T tenant sector node table 33 Threshold Crossed 61, 62, 65 Threshold Exceeded 53, 54 Page 73