ADCP-75-192 Issue 2 June 2007 Digivance® CXD/NXD Multi-Band Distributed Antenna System With FIC Operation Manual 1404422 Rev A
ADCP-75-192 • Issue 2 • June 2007 • Preface COPYRIGHT © 2007, ADC Telecommunications, Inc. All Rights Reserved Printed in the U.S.A. REVISION HISTORY ISSUE DATE 1 07/2006 REASON FOR CHANGE Original. 2 04/2007 Updated for new card configuration (Fiber Interface Controller replaces Synchronous Interface Card). Expanded to include NXD descriptions and settings. Updated for other general changes in format and content.
ADCP-75-192 • Issue 2 • June 2007 • Preface TABLE OF CONTENTS Content Page About This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 RELATED PUBLICATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Admonishments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ADCP-75-192 • Issue 2 • June 2007 • Preface TABLE OF CONTENTS Content Page 3.4.1 Setting Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 3.4.2 Setting Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 3.4.3 Setting Hub Measured Forward Gain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 3.4.
ADCP-75-192 • Issue 2 • June 2007 • Preface TABLE OF CONTENTS Content Page 4.2 4.3 5 Upgrading an Existing System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 4.2.1 Preliminary Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 4.2.2 Upgrade Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ADCP-75-192 • Issue 2 • June 2007 • Preface TABLE OF CONTENTS Content Page 4 © 2007, ADC Telecommunications, Inc.
ADCP-75-192 • Issue 2 • June 2007 • Preface ABOUT THIS MANUAL This manual provides the following information: • An overview of the Digivance CXD/NXD system; • A description of the CXD/NXD system Radio Access Node (RAN); • Installation procedures for the RAN; • Maintenance procedures for the RAN; • Product support information.
ADCP-75-192 • Issue 2 • June 2007 • Preface ADMONISHMENTS Important safety admonishments are used throughout this manual to warn of possible hazards to persons or equipment. An admonishment identifies a possible hazard and then explains what may happen if the hazard is not avoided. The admonishments — in the form of Dangers, Warnings, and Cautions — must be followed at all times.
ADCP-75-192 • Issue 2 • June 2007 • Preface SAFE WORKING DISTANCES The Digivance CXD/NXD antenna, which is mounted on top of a pole, radiates radio frequency energy. For the occupational worker, safe working distance from the antenna depends on the workers location with respect to the antenna and the number of wireless service providers being serviced by that antenna. Emission limits are from OET Bulletin 65 Edition 97-01, Table 1 A.
ADCP-75-192 • Issue 2 • June 2007 • Preface BIM BTS C CDRH C/MCPLR CM cPCI CPU CWDM CXD DAS DHCP dB(FS) DC DIF Div EMS ESD F FBHDC FDA FCC FIC FSC GPS Div HUC IF IN IP KG LED LSE LVD MHz MIB MTBF MUX NIPR Div NMS NXD Base Station Interface Module Base Transceiver Station Centigrade Center for Devices and Radiological Health Cellular SMR Multicoupler Centimeter CompactPCI Central Processing Unit Coarse Wave Division Multiplex Compact RAN Distributed Antenna System Dynamic Host Configuration Protocol deciba
ADCP-75-192 • Issue 2 • June 2007 • Preface OAM OSP PA PAA PC PCI PIC P/MCPLR RAN RDC RDC2 RF RSC RUC RUC2.X RUC3 SFP SIF SNMP SONET STF2 UL VAC VDC VSWR WDM WSP Operations Administration and Maintenance Outside Plant Power Amplifier Power Amplifier Assembly Personal Computer Peripheral Component Interconnect bus PA Interface Controller PCS Multicoupler Radio Access Node RAN Down Converter RAN Down Converter Version 2 Radio Frequency Reverse Simulcast Card RAN Up Converter RAN Up Converter Version 2.
ADCP-75-192 • Issue 2 • June 2007 • Preface Page 10 © 2007, ADC Telecommunications, Inc.
ADCP-75-192 • Issue 2 • June 2007 1 SYSTEM OVERVIEW This section provides an overview of the Digivance CXD/NXD system intended for someone configuring system parameters (referred to as “objects” in the software used). This overview includes a general description of the physical components and a more detailed description of the software components because the tasks in this manual involve mostly the software components. 1.
ADCP-75-192 • Issue 2 • June 2007 The Hub is a rack assembly containing electronic equipment. Included are two types of Compact PCI (cPCI) “chassis” containing “electronic modules.” The two types of cPCI chassis are the Digital Chassis and the RF Chassis. The electronic modules include CPU boards, optical to RF data converters, an optical interface board, and so on.
ADCP-75-192 • Issue 2 • June 2007 On a more detailed level, in both the forward and reverse paths, the signal data passes through a series of electronic modules: • In the forward path, the Full Band Hub Down Converter (FBHDC) receives RF signals from the BTS and down converts the signals to Intermediate Frequency (IF). The Forward Simulcast Card (FSC) digitizes the IF signals and passes digital IF (DIF) signals into the Fiber Interface Controller (FIC).
ADCP-75-192 • Issue 2 • June 2007 1.4 System Control System control in a Digivance CXD/NXD system involves three main components: (1) a LANtype network connecting a Hubmaster CPU with other electronic modules including slave CPUs and FICs; (2) a set of alarms and settable objects provided through an SNMP interface and MIBs; (3) and an ADC graphical user interface called the Element Management System (EMS). These components are described in the following topics. 1.4.
ADCP-75-192 • Issue 2 • June 2007 These databases are provided through Management Information Bases (MIBs) and an SNMP proxy agent embedded in the system software. SNMP (Simple Network Management Protocol) is an internet standard protocol enabling online devices to be queried and controlled remotely using an IP interface. A MIB is a table-like set of “objects” conforming to SNMP specifications.
ADCP-75-192 • Issue 2 • June 2007 The LSE node is a regular Hub node with additional functionality particular to location services applications.There is also a distinction between RAN Nodes in NXD vs. CXD systems. In an NXD system, there is a one to one relationship between CPUs and nodes because each NXD RAN has its own CPU where its own MIBs reside. In a CXD system, the term RAN Node refers conceptually to the individual RAN but all RAN MIBs reside on the Hubmaster CPU. 1.4.
ADCP-75-192 • Issue 2 • June 2007 All CPUs in the Digivance network support SNMP to provide NMS monitoring and access. The NMS software (whether generic or EMS) sends SNMP GET and SET messages to the various nodes in the Digivance network to access MIBs in response to a user entry. • A GET message gets the current value of an identified object. • A SET message sets the object to a given value. Only a limited subset of objects can be set to a new value. Note: MIBs are described in more detail in Section 2.
ADCP-75-192 • Issue 2 • June 2007 1.7 Specifications Table 1 lists specifications for the Hub. Table 2 lists specifications for the CXD RAN. Table 3 lists specifications for the NXD RAN. Table 1. Hub Specifications ITEM SPECIFICATION COMMENT Dimensions (HxWxD) 78 x 24 x 24 Inches 198.1 x 61.0 x 61.
ADCP-75-192 • Issue 2 • June 2007 Table 1. Hub Specifications, continued ITEM SPECIFICATION Power Consumption RF Chassis FBHDC HUC FSC 55.0 Watts 11.0 Watts 7.7 Watts 13.5 Watts COMMENT Typical Fans and 12 VDC P/S Base Station Interface Module (BIM) Dimensions (HxWxD) 17.1 x 1.75 x 7.9 inches (body) 43.4 x 4.4 x 20.
ADCP-75-192 • Issue 2 • June 2007 Table 2. CXD RAN specifications ITEM SPECIFICATION COMMENT Dimensions (HxWxD) CXD RAN Standard Cabinet CXD RAN Extended Cabinet 23 x 18 x 11 Inches 23 x 18 x 17 Inches 2.6 cubic feet 4.1 cubic feet Weight CXD RAN Standard Cabinet CXD RAN Extended Cabinet Pole mount bracket 23 lbs. (10.45 kg.) 49 lbs. (45.45 kg.) 7 lbs. (3.18 kg.
ADCP-75-192 • Issue 2 • June 2007 Table 2.
ADCP-75-192 • Issue 2 • June 2007 Table 3. NXD RAN Specifications ITEM SPECIFICATION COMMENT Power AC power ingress 240 VAC, 20 Amps, single phase Battery backup options extended glitch 120 minutes 5 minutes RAN box power use 2700 Watts Max. 16 Amps Max. cPCI rack power -48 VDC -48 volts @25 degrees C (degrees F) for four bands Optical Fiber cable ingress Nylon connector accommodates cable diameters in range 0.380.50 inches (0.97-1.27 cm). For larger cable sizes, refer to the note in .
ADCP-75-192 • Issue 2 • June 2007 Table 3. NXD RAN Specifications ITEM SPECIFICATION COMMENT Receiver noise figure PCS band Cellular band 6 dB 5 dB Measured at Hub output connector (BIM, RxP) without BTS at 10 dB gain and a single RAN Input IP3 -21 dBm Two tone tests at -56 dBm Received signals In band Out of band +/- 8.
ADCP-75-192 • Issue 2 • June 2007 2 NETWORK CONFIGURATION DETAILS This section provides details on items that are important to understand when configuring the Digivance system. 2.1 Node and Equipment Identification In the Digivance CXD/NXD system, a “node” is a hardware focus of activity. The main Hub CPU (the system’s Master CPU) and the RANs are each a separate node. They are referred to as the “Hubmaster Node” and “RAN Nodes.” In a large system, there may be additional CPUs at the Hub.
ADCP-75-192 • Issue 2 • June 2007 Table 4. Hub Rack Numbering CHASSIS OR SHELF HEIGHT LOCATION* Ethernet Hub 1U U38 Digital Chassis (top) 4U U37 BIM 1U U33 RF Chassis (top) 4U U32 BIM 1U U28 Digital Chassis (top) 4U U27 BIM 1U U23 RF Chassis (top) 4U U22 BIM 1U U18 Digital Chassis (top) 4U U17 BIM 1U U13 RF Chassis (top) 4U U12 BIM 1U U8 Reference Module (bottom) 1U U7 *’U’ numbers are printed on the rack rails of the OP-HUB2 rack.
ADCP-75-192 • Issue 2 • June 2007 2.2.1 MIB Software Relationships In Figure 7, the solid lines between the Hubmaster and Hub/RAN nodes illustrate Hub/RAN connection relationships. As shown in the figure, the Hubmaster contains a process called the Hub/RAN Config Process. This process is responsible for managing the connections between the Hubmaster and the other nodes in the network. The Hub/RAN Config Process uses the Hub Node MIB and RAN Node MIB to manage these connections.
ADCP-75-192 • Issue 2 • June 2007 2.2.2 MIB Hub/RAN Connection Relationships In Figure 8, the dashed lines seen in the Hub and RAN Nodes show the relationships among MIBs associated with specific hardware modules. As shown, a separate software HCP (hardware control process) is used to manage each hardware module in a node. The HCP MIBs are the interface to these HCPs. A single MIB instance is used in each node for each type of hardware (FBHDC, RDC, and so on).
ADCP-75-192 • Issue 2 • June 2007 2.3 Tenant Relationships In Figure 8 on the previous page, the dotted lines among Hubmaster and Hub/RAN nodes illustrate tenant relationships. Once a tenant is created using the BTS Connection of the previous section, a Tenant process is launched to manage that new tenant. This tenant process uses the Tenant OAM MIB in the Hubmaster node to allow tenant specific objects to be configured.
ADCP-75-192 • Issue 2 • June 2007 2.4 Pathtrace Format Pathtrace is a term used to describe the 64-byte data stream that is transmitted between all DIFconnected modules in the Digivance CXD/NXD system. The contents of the pathtrace strings have been designed such that each set of connected tenant equipment will transmit/receive a pathtrace string containing information about that particular tenant.
ADCP-75-192 • Issue 2 • June 2007 In each of the simulcasted RANs, the RUC module receives the pathtrace string into its FPGA from one of its two DIF input connections. The RUC HCP then reports the received pathtrace strings in its MIB for use by tenant processing and other higher-level processes.
ADCP-75-192 • Issue 2 • June 2007 2.4.5 Pathtrace Reverse Reception In the reverse path, the SIF or FIC modules in the RANs that are connected to the RDC outputs, as well as the SIFs or FICs in the Hub, pass-through the pathtrace strings from their inputs to their outputs. In addition, the SIF/FIC HCPs report the passed-through pathtrace strings in the SIF MIB for use by tenant processing and other higher-level processes.
ADCP-75-192 • Issue 2 • June 2007 3 NETWORK AND SYSTEM INSTALLATION AND SETUP This section discusses the steps necessary to set up the Digivance CXD/NXD system communications and operating objects. It is assumed for the purposes of this discussion that the required system elements have already been installed and powered on, and that the reader has an understanding of TCP/IP networking basics. 3.
ADCP-75-192 • Issue 2 • June 2007 4. Ensure that the electronic modules within the RF chassis are in the correct position. An RF chassis in a Hub rack contains enough slots for two sets of tenant RF equipment, where a set of tenant RF equipment consists of one FSC, one HUC, and up to two FBHDCs. A set of tenant equipment in an RF chassis is installed in a particular manner, from bottom to top; the order of modules is HUC, FBHDC, FSC, and FBHDC.
ADCP-75-192 • Issue 2 • June 2007 The software in the Hubmaster continues to send requests to all configured Hub Nodes to determine if there are any BIM modules that have come online. When a new BIM module is located, the Hub Config Process creates an “Unconfigured” tenant in the BTS Connection MIB. This can be seen by noticing that the Tenant ID in the BTS Connection MIB is “Unconfigured”, where X is 1-96.
ADCP-75-192 • Issue 2 • June 2007 US1900C (3) - PCS band C US1900D (4) - PCS band D US1900E (5) - PCS band E US1900F (6) - PCS band F US800AAPP (7) - Cellular A and A'' bands US800BBP (8) - Cellular B and B' bands US800AP (9) - Cellular A' band US800SMRA (10) – SMR 800 band (806-821/851-866MHz) US800SMRUpper (11) – SMR 800 band Extended (818-824/862-869MHz) US900SMRB(12) – SMR 900 band US1900G (13) - PCS band G The MIB field is: transceptBtsConnectionTable.transceptBtsConnectionTenantBand 3.3.2.
ADCP-75-192 • Issue 2 • June 2007 transceptBtsConnectionTable.transceptBtsConnectionBimI2cSlot • The BIM module belonging to this tenant must have RF connections to one FBHDC modules. Select the I2C Bus of the FBHDC module that matches the BIM I2C bus value. Set the FBHDC I2C slot value to “1”. The FBHDCs belonging to a single tenant (i.e. having RF connections to the same BIM module) should be co-located in the RF chassis, with an FSC and HUC modules separating them.
ADCP-75-192 • Issue 2 • June 2007 3.3.2.7 HUC Invalid Config The BTS Connection MIB contains a read-only field that reports the state of the HUC Invalid Configuration fault field. This information will allow the person configuring the system to know that the tenant has been completely and correctly configured - this is known when the value in this field is reported as “No Fault” or '0'. The MIB field is: transceptBtsConnectionTable.transceptBtsConnectionHucInvalidConnection. 3.3.2.
ADCP-75-192 • Issue 2 • June 2007 3.4 Tenant Configuration The Tenant Operations Management and Maintenance (OAM) MIB is the primary interface for configuring the operating objects of tenants in the Digivance CXD/NXD system. The Tenant OAM MIB is used exclusively at the Hubmaster node, where any changes made to operating objects are validated and pushed down to the proper node(s) by Tenant processing. Note: In EMS, the Tenant OAM MIB is accessed from the menu tree by selecting Configuration-Tenants. .
ADCP-75-192 • Issue 2 • June 2007 3.4.4 Setting RAN Measured Forward Gain transceptTenantOAMTable.transceptTenantRanXMeasuredForwardGain, where X = 1-8 This object is no longer used in the Digivance CXD/NXD system. 3.4.5 Setting FSC Gain transceptTenantMoreControlsTable.transceptTenantMoreControlsFscOutputGain and transceptTenantMoreControlsTable.transceptTenantMoreControlsFscOutputGainOverride This feature allows the user to adjust FSC output gain outside of the default setting.
ADCP-75-192 • Issue 2 • June 2007 3.4.8 Setting Reverse Cable Loss transceptTenantOAMTable.transceptTenantReverseCableLoss Reverse Cable Loss is a object in the Tenant OAM MIB to allow the signal loss due to cabling between the base stations and the Digivance CXD/NXD system to be factored into the reverse gain management processing. This object has a valid range of values of 0 to 450, which is 0 to +45 dB in 1/10 dB units. The maximum cable loss between the BTS and the BIM is 45 dB. 3.4.
ADCP-75-192 • Issue 2 • June 2007 The Forward and Reverse Delay Compensation processes, which balance the signal delay in a simulcast group, can be enabled/disabled using the associated objects in the Tenant OAM MIB. These MIB fields are enumerated types with values “Enabled” = 0 and “Disabled” = 1. The reason for the inverse boolean logic is so that the desired default values are set to be zero, which is the MIB default value. 3.4.13 Forward/Reverse Target Delay transceptTenantTargetDelayTable.
ADCP-75-192 • Issue 2 • June 2007 3.4.16 Target Simulcast Degree In order for the Digivance CXD/NXD software to determine the correct number of tenant paths throughout the system, it can be provided with the target simulcast degree. This will allow the Tenant process to properly determine and report missing boards and path conditions and quantities. The Tenant Simulcast Degree field in the Tenant OAM MIB is used to configure this object.
ADCP-75-192 • Issue 2 • June 2007 Tenant processing uses a least-recently-used scheme to determine the RAN ID to assign to newly discovered RANs. When Tenant processing discovers new RANs that contain hardware associated with that tenant (based on Tenant ID of pathtrace string), the new RAN is assigned the next sequential “never-been-used” RAN ID, a value from 1-8.
ADCP-75-192 • Issue 2 • June 2007 There can be many CPUs at a single Hub Site within the many racks and chassis, but there is no way to correlate an IP address to its physical rack/chassis location automatically. Therefore, a convention for identifying racks and chassis needs to be established. At installation time, each hostname, as written on the front tag of each CPU, must be recorded in conjunction with its physical location.
ADCP-75-192 • Issue 2 • June 2007 3.6.3 Accessing Nodes Locally Nodes can be accessed locally through the serial link. The required hardware is as follows: • Terminal with serial interface and terminal software such as Tera-Term Pro or Hyperlink. • RS-232 cable 9 pin D shell male to male type. • Adapter for the Digivance CXD/NXD CPU low profile I/O connector (DB-9F to RJ-11). Once the link is made, run the terminal software.
ADCP-75-192 • Issue 2 • June 2007 • Trouble ticket generation • The Digivance CXD/NXD system outputs a wealth of raw event information. It is up to the NMS to determine what alarms are generated, and how to dispatch resources to rectify the situation. • E-mail, pager, and cell phone notification methods are recommended for a user-defined subset of fault conditions. • Scheduling tables are a plus for those operators who are not on call 24 hours a day.
ADCP-75-192 • Issue 2 • June 2007 3.7.1.2 DHCP Address Range The DHCP address range portion of the script first prompts the operator for the beginning of the range. It uses the IP address and netmask input described previously to provide a default lower limit of XXX.YYY.ZZZ.3. When in doubt, depress the enter key to select the default lower limit. Likewise, a default upper limit will be generated, servicing nodes up to and including XXX.YYY.ZZZ.250.
ADCP-75-192 • Issue 2 • June 2007 script will then prompt “Enter a list of SNMP v2 trap-sinks, one per line: (control-d when done)” in order to set up any SNMP-V2 trap receivers that traps should be transmitted to. Any number of trap-sinks can be configured, though the quantity should be kept to a minimum in order to minimize processor load on network nodes. Also, SNMP V1 and V2 trap-sinks can configured simultaneously within the same domain.
ADCP-75-192 • Issue 2 • June 2007 It is also important to have a mechanism in place to update the LAN DNS with the Hubmaster IP address, so that the Digivance CXD/NXD nodes know where to send data. Since the Hubmaster IP is static, this can be manually entered at installation time. The setup becomes more complicated when multiple subnets are introduced. However, it is recommended that in such a case the Hubmaster DHCP server be utilized instead. 3.7.2.
ADCP-75-192 • Issue 2 • June 2007 The Site ID designates the physical location of the CXD/NXD Hub. Often, wireless operators already have site IDs laid out for their markets and BTS installations, such as “Memphis203” or “Cell29PA”, and these designators work well for pinpointing the location of the CXD/NXD Hub. GPS coordinates or road names also work well. The Site ID can be up to 64 characters long. 3.8.1.2 CPU Rack ID transceptHubNodeTable.
ADCP-75-192 • Issue 2 • June 2007 exist. To remove old and unwanted node information from this MIB, the operator must set the “Clean” field to 1. The old node information will be removed. No further action is required. Note if the node is valid, it will re-appear within seconds, even if it is cleared. 3.8.1.7 Setting the RF Rack/Chassis ID transceptHubNodeRfTable.transceptHubNodeRfRackID and transceptHubNodeRfTable.
ADCP-75-192 • Issue 2 • June 2007 3.8.2.1 IP Address This entry (transceptRanNodeTable.transceptRanNodeIPAddress) displays the IP Address of each RAN attached to the Hubmaster node. RAN IP addresses are assigned by DHCP. This entry is automatically entered by Digivance CXD/NXD system software. 3.8.2.2 Hostname transceptRanNodeTable.transceptRanNodeHostname This entry displays the hostname of each RAN attached to the Hubmaster node.
ADCP-75-192 • Issue 2 • June 2007 The RFA configuration options are pcsA, pcsB, pcsC, pcsD, pcsE, pcsF, smrA, smrB, pcsADB, pcsEFCG, smrA, smrB, cellA, and cellB. 3.8.2.6 Multicoupler/LNA Connection transceptRanNodeTable.transceptRanNodeRdcZMucOrLnaConnection, Z=1-5 These entries manually record the RF connection path between the RAN downConverter’s outputs and the RFA. For example, if the RFA attached to RDC A2’s output is connected to a PCS ADB RFA, then transceptRanNodeTable.
ADCP-75-192 • Issue 2 • June 2007 3.8.2.10 Setting The GPS Coordinates transceptRanNodeGpsCoordTable.transceptRanNodeGpsLongitude and transceptRanNodeGpsCoordTable.transceptRanNodeGpsLatitude For cases where a GPS receiver is not present on a given node and it is desired to manually enter the GPS coordinates, the RAN Node MIB contains two MIB fields to configure the GPS longitude and latitude settings.
ADCP-75-192 • Issue 2 • June 2007 • RAN Output Power – PA Output Power Minus 2dB diplexer/cable loss. • RUC Attn Offset – Tenant MIB value used to adjust PA output power to account for variations in RF chain. HUB RAN COMPOSITE INPUT POWER FBHDC PA OUTPUT POWER RUC ATTN PA OUTPUT LOSS RAN OUTPUT POWER RUC ATTN OFFSET 21945-A Figure 11. FBHDC Direct Cable Balancing Table 8 shows the recommended power levels and gains for the various CXD/NXD bands. Table 8.
ADCP-75-192 • Issue 2 • June 2007 BIM Input High Power duplexed interfaces requires the use of the High Power Attenuator and the BIM Module. A block diagram of the forward path balancing components is shown in Figure 12. RAN HUB COMPOSITE INPUT POWER BIM INPUT 20 dB HP POWER PAD BIM BIM ATTN RUC ATTN BIM ATTN OFFSET RUC ATTN OFFSET PA OUTPUT POWER PA OUTPUT LOSS RAN OUTPUT POWER 21944-A Figure 12.
ADCP-75-192 • Issue 2 • June 2007 The BIM input balancing procedure is as follows: 1. Insert signals into the HP Attenuator at the recommended input level (composite). 2. If the input level is lower than the recommended value, adjust the transceptTenantMoreAttenTable.transceptTenantBimForwardAttenZOffset fields in the Tenant OAM MIB by a comparable amount. Note: For example: If the PCS composite input is 44 dBm, enter a -30 into the transceptTenantMoreAttenTable.transceptTenantBimForwardAttenZOffset field.
ADCP-75-192 • Issue 2 • June 2007 3. Enter reverse gain setting (-10 to +10 dB, typically +10 dBm) into the transceptTenantReverseGain field of the Tenant OAM MIB for this Tenant Sector. Note: The +/- 10 dB reverse gain setting assumes a 20 dB attenuator. Without the attenuator, the gain is +10 to +30 dB. 3.9.4 Functional RAN Call Verification At the completion of BTS integration, it is recommended that the coverage area be driven to insure all RANs are operational.
ADCP-75-192 • Issue 2 • June 2007 4.2 Upgrading an Existing System The most common upgrade scenario is one where an existing, fielded, operational system is having all of its CPUs upgraded to the next version of software. 4.2.1 Preliminary Steps The following are some general notes that need to be considered when upgrading a fielded system: • The Hub Master should be the final CPU upgraded in the network to ensure that any new network-level functions are managed and supported properly.
ADCP-75-192 • Issue 2 • June 2007 • If the autonomous actions taken by the upgrade executable discover that the upgrade was not successful, the upgrade executable will report this information in the log file located at /var/log/opencell-upgrade. Otherwise, a successful status message will be reported to that log. • Manual steps must also be taken to ensure that the upgrade process completed successfully.
ADCP-75-192 • Issue 2 • June 2007 On the upgraded CPU, verify pathtrace values are as expected by viewing the transceptOpencellPathtraceTable MIB. Refer to the above “Preliminary Steps” section for details. On the upgraded RAN CPU, verify PAs are functioning and power levels are as expected. Refer to the above “Preliminary Steps” section for details. 4.2.
ADCP-75-192 • Issue 2 • June 2007 4.2.6 FIC Software Upgrade Use this procedure to upgrade the software on the FIC compact flash card. 1. FTP the upgrade.tar file to /tmp on the FIC. 2. ssh to the FIC using the “root” login. 3. cd to the /tmp directory and untar the upgrade.tar file. 4. If needed, shut down the running software on the FIC using the command: /etc/init.d/digivance stop 5. Overwrite the current software with the files that were untarred using the commands: cd upgrade cp -r * / 6.
ADCP-75-192 • Issue 2 • June 2007 Upgrading a CPU does not require that a restore of the backed up files be performed unless a problem is encountered. Any data contained in the MIBmap files and any configuration data in the system configuration files will remain untouched through a software upgrade. The only time that backup data needs to be recovered is when an upgrade has failed and the CPU is being reverted to the previous version using the downgrade script.
ADCP-75-192 • Issue 2 • June 2007 After completing the desired number of lines, finish by entering two blank lines and then a Ctrl-D. To remove a trap-sink, do as above except at the prompt for input (‘>’), enter: update delete version-trap-sink.domain A address 4.5 Updating Spare CPUs There are times when it is desirable to update the software on a spare CPU.
ADCP-75-192 • Issue 2 • June 2007 • In the event that a spare CPU cannot be updated because of the above restriction, the CPU will have to be upgraded on a standalone chassis that is not resident on the fielded system or be returned to the factory for upgrading. • It is NOT possible to update a spare Hub Master CPU while the fielded system's Hub Master is still installed, because two Hub Masters in the same domain will cause chaos on the network.
ADCP-75-192 • Issue 2 • June 2007 4.7 Gain Management and Fault Detection This section outlines the concepts and performance objectives involved in the gain management and fault detection (continuity) of the Digivance CXD/NXD system. This section breaks these topics down into the following areas: • Forward gain management • Reverse Automatic Gain Control • Forward delay management • Reverse delay management • Forward continuity • Reverse continuity. • PA Overpower Protection • Hub Overpower Protection 4.
ADCP-75-192 • Issue 2 • June 2007 4.7.5 Forward Continuity Forward Continuity Management (FCM) is a software function that may be used to verify that the forward RF paths are functioning properly and are able to pass signals. This function is disabled by default. 4.7.
ADCP-75-192 • Issue 2 • June 2007 4.7.6.3 Hub Up Converter (HUC) Tone Test The HUC tone will be enabled at all times, unless explicitly disabled via the HUC MIB. Its frequency corresponds to the last channel in the band set for that tenant-sector. Additional requirements are: • The HUC tone level is –70 dBm relative to the antenna port at the RAN. • If the test tone is not detected at the BIM, it and the HUC are reported as faulting. • See “SNMP Agent and Fault Isolation Guide” for details. 4.7.
ADCP-75-192 • Issue 2 • June 2007 4.7.8 Hub Overpower Protection Hub Overpower Protection (HOP) is a software function to control the output levels of the FSC. HOP periodically measures the FSC output power. If the power exceeds a target level (-3.5 dBFS), HOP will decrease the FSC output gain until the power level is below the allowable threshold. HOP will continue to monitor the FSC Output Power until the level drops sufficiently to allow the gain level to be returned to normal.
ADCP-75-192 • Issue 2 • June 2007 5 CUSTOMER INFORMATION AND ASSISTANCE PHONE: U.S.A.
www.adc.
