1. Manuals
  2. Brands
  3. ADC Manuals
  4. Antenna
  5. Digivance CXD
  6. Operation manual

ADC Digivance CXD Operation Manual

Multi-band distributed antenna system with fic
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
ADCP-75-192
Issue 2
June 2007
®
Digivance
CXD/NXD Multi-Band
Distributed Antenna System With FIC
Operation Manual
1404422 Rev A

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Digivance CXD and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for ADC Digivance CXD

Summary of Contents for ADC Digivance CXD

  • Page 1 ADCP-75-192 Issue 2 June 2007 ® Digivance CXD/NXD Multi-Band Distributed Antenna System With FIC Operation Manual 1404422 Rev A...

  • Page 2: Adcp

    DISCLAIMER OF LIABILITY Contents herein are current as of the date of publication. ADC reserves the right to change the contents without prior notice. In no event shall ADC be liable for any damages resulting from loss of data, loss of use, or loss of profits and ADC further disclaims any and all liability for indirect, incidental, special, consequential or other similar damages.

  • Page 3: Table Of Contents

    Tenant Configuration ............. . 28 Page 1 © 2007, ADC Telecommunications, Inc.
  • Page 4 Release Notes ............48 Page 2 © 2007, ADC Telecommunications, Inc.
  • Page 5 CUSTOMER INFORMATION AND ASSISTANCE ........... 60 Page 3 © 2007, ADC Telecommunications, Inc.
  • Page 6 ADCP-75-192 • Issue 2 • June 2007 • Preface TABLE OF CONTENTS Content Page Page 4 © 2007, ADC Telecommunications, Inc.

  • Page 7: About This Manual

    Listed below are related manuals, their content, and their publication numbers. Copies of these publications can be ordered by contacting the Technical Assistance Center at 1-800-366-3891, extension 73476 (in U.S.A. or Canada) or 952-917-3476 (outside U.S.A. and Canada). All ADC technical publications are available for downloading from the ADC web site at www.adc.com.

  • Page 8: Admonishments

    Fiber optic patch cords or pigtails may be permanently damaged if bent or curved to a radius of less than 2 inches (5.1 cm). Caution: Exterior surfaces of the RAN may be hot. Use caution during servicing. Page 6 © 2007, ADC Telecommunications, Inc.

  • Page 9: Safe Working Distances

    Industry Canada Technical Specifications were met. LIST OF ACRONYMS AND ABBREVIATIONS The acronyms and abbreviations used in this manual are detailed in the following list: Alternating Current Multiband Antenna Page 7 © 2007, ADC Telecommunications, Inc.
  • Page 10 Light Emitting Diode Location Services Equipment Low Voltage Disconnect Mega Hertz Management Information Base MTBF Mean Time Between Failure Multiplexer NIPR Network IP Receiver Diversity Network Management System Digivance Neutral Host Product Line Page 8 © 2007, ADC Telecommunications, Inc.
  • Page 11 Sonet Interface Module SNMP Simple Network Management Protocol SONET Synchronous Optical Network STF2 System Interface Module Underwriters Laboratories Volts Alternating Current Volts Direct Current VSWR Voltage Standing Wave Ratio Wave Division Multiplex Wireless Service Provider Page 9 © 2007, ADC Telecommunications, Inc.
  • Page 12 ADCP-75-192 • Issue 2 • June 2007 • Preface Page 10 © 2007, ADC Telecommunications, Inc.

  • Page 13: System Overview

    SMR A SMRA/ RAN 4 SMRB SMR B SMRA/ RAN 5 SMRB SMRA/ RAN 6 SMRB SMRA/ RAN 7 SMRB SMRA/ RAN 8 SMRB 20799-A Figure 1. Digivance Architectural Summary Diagram (CXD System Shown) Page 1 © 2007, ADC Telecommunications, Inc.

  • Page 14: Issue

    FBHDC 800 MHz RDC2 800/900 800/ DUPLEXED OUTPUT FBHDC 900 MHz RDC2 FBHDC 1900 MHz 1900 1900 DUPLEXED OUTPUT 21879-C STF2 Figure 2. Digivance CXD System Block Diagram (Three Bands Shown) Page 2 © 2007, ADC Telecommunications, Inc.
  • Page 15 DUPLEXER MULTI OUTPUT 800 MHz COUPLER 1900 1900 MULTI DUPLEXED DUPLEXER COUPLER OUTPUT FBHDC 1900 MHz 1900 REVERSE PATH DIVERSITY 21989-A STF2 STF2 Figure 3. Digivance NXD System Block Diagram (Three Bands Shown) Page 3 © 2007, ADC Telecommunications, Inc.

  • Page 16: System Control

    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.
  • Page 17 To do this, the user requires either a generic SNMP manager called a Network Management System (NMS) or the ADC Element Management System (EMS), both of which, in their underlying functions, conform to SNMP specifications. EMS is described in the next topic.

  • Page 18: Element Management System (Ems)

    HUB NODE 1 RAN 1 MIBs MIBs SNMP SNMP AGENT AGENT TRAP HUB NODE STATUS STATUS ALARMS ALARMS ETHERNET SWITCH HUBMASTER HUBMASTER SNMP AGENT MIBs HTTP 21033-C USER Figure 6. EMS Relationship to MIBS Page 6 © 2007, ADC Telecommunications, Inc.

  • Page 19: Fiber Optical Transport

    EMS software with normally open and normally closed alarm contacts for connection to a customer-provided external alarm system. All Hub and RAN alarms can be accessed through the SNMP manager or the EMS software GUI. Page 7 © 2007, ADC Telecommunications, Inc.

  • Page 20: Specifications

    19.0 x 7.0 x 7.9 in. (body) 43.4 x 17.8 x 20.1 cm 17.1 x 7.0 x 7.9 in. (mount 48.3 x 17.8 x 20.1 cm Color Brushed aluminum Backplane connections RJ-45 Power Input -48 VDC Floating Page 8 © 2007, ADC Telecommunications, Inc.
  • Page 21 Standard range (typical) 0 dB m Extended range (typical) Optical receive input -9 dBm Standard range -26 dBm Extended range Optical budget 9 dB Standard range (typical) 26 dB Extended range (typical) Optical connectors Dual-connector Page 9 © 2007, ADC Telecommunications, Inc.
  • Page 22 Requires CWDM optical trans- ceivers and wavelength division With CWDM 1 per 4 RANS multiplexers (WDM) which are accessory items. Optical transceiver type Forward and reverse path wave- length Standard range 1310nm Extended range 1550 nm Page 10 © 2007, ADC Telecommunications, Inc.
  • Page 23 Storage temperature -40 to +85 degrees C -40 to 185 degrees F Internal air temperature 0 to 60 degrees C 32 to 140 degrees F Weather resistance NEMA-3R Operational humidity Acoustic emissions 63 dBA Page 11 © 2007, ADC Telecommunications, Inc.
  • Page 24 Receive Path Transmit Path PCS band 1850-1910 MHz 1930-1990 MHz Cellular band 824-849 MHz 869-894 MHz SMR 800 band 806-824 MHz 851-869 MHz SMR 900 band 896-901 MHz 935-940 MHz Instantaneous bandwidth 15 MHz Page 12 © 2007, ADC Telecommunications, Inc.
  • Page 25 At antenna port PCS 20 Watt MCPA 12.5 Watts (+41 dBm) composite At antenna port Gain resolution 1 dB Gain measurement Configured at startup using fac- tory calibration of modules and user data Page 13 © 2007, ADC Telecommunications, Inc.

  • Page 26: Network Configuration Details

    Hub Equipment Identifications Table 4 shows the recommended convention to be used for identifying and placing Hub equipment: Table 4. Hub Rack Numbering CHASSIS OR SHELF HEIGHT LOCATION* Attenuator Shelf 2U PDU 2U Page 14 © 2007, ADC Telecommunications, Inc.

  • Page 27: Mib Relationships

    Information Bases (MIBs) accessed with an SNMP manager (or EMS) to provide a user interface for querying and configuring perrformace objects and being notified of alarms. This section describes the relationships between MIBs that are relevant when cofiguring and operating the system. Page 15 © 2007, ADC Telecommunications, Inc.

  • Page 28: Mib Software Relationships

    PATH *STF NETWORK HUB RF NODE EQUIPMENT NODE CONNECTION PATH PATHTRACE BACK- SIF/ NODE PLANE PATH SIF/ BACK- POWER PLANE ENTRY *NXD HUB NODE SNMP AGENT ONLY 21942-A Figure 7. Digivance MIB Structure Page 16 © 2007, ADC Telecommunications, Inc.

  • Page 29: Mib Hub/Ran Connection Relationships

    PATH *STF NETWORK HUB RF NODE EQUIPMENT NODE CONNECTION PATH PATHTRACE BACK- SIF/ NODE PLANE PATH SIF/ BACK- POWER PLANE ENTRY *NXD HUB NODE SNMP AGENT ONLY 21943-A Figure 8. Digivance MIB Structure Page 17 © 2007, ADC Telecommunications, Inc.

  • Page 30: Tenant Relationships

    The Forward/Reverse Gain processes then access the HCP MIBs to read power values and set attenuator values as part of gain control. The results of the gain control processes are then reported into the Forward/Reverse Gain MIBs. Page 18 © 2007, ADC Telecommunications, Inc.

  • Page 31: Pathtrace Format

    In addition, the SIF Hardware Control Process (HCP) report the passed- through pathtrace strings in the SIF or FIC MIB for use by tenant processing and other higher- level processes. Page 19 © 2007, ADC Telecommunications, Inc.

  • Page 32: Pathtrace Reverse Transmission

    (“P” or “D”). Finally, the RDC transmits the pathtrace strings out on up to two outputs. The pathtrace strings are then transmitted back to the Hub reverse modules belonging to this tenant. Page 20 © 2007, ADC Telecommunications, Inc.

  • Page 33: Pathtrace Reverse Reception

    Control Table of the Equipment MIB. Tenant processing in the Hubmaster node is the primary user of the Equipment MIB for status and control of tenant hardware. The details of this are described in more detail in the following section. Page 21 © 2007, ADC Telecommunications, Inc.

  • Page 34: Network And System Installation And Setup

    Note: Except for the first, all of these tasks involving setting SNMP objects and are done using an SNMP manager or the ADC Element Management System. Table 5. System Setup Tasks ITEM...

  • Page 35: Assigning Tenants

    Hub Config Process in the Hubmaster must first locate a unique BIM instance controlled by one of the Hub CPUs. This requires that the Hub Node first be configured such that the CPU Rack ID and Chassis ID (described in Section 2.1 on Page 14) are known. Page 23 © 2007, ADC Telecommunications, Inc.
  • Page 36 Digivance CXD/NXD system, currently: No Band (0) - no band selected, will not result in a configured tenant US1900A (1) - PCS band A US1900B (2) - PCS band B Page 24 © 2007, ADC Telecommunications, Inc.
  • Page 37 The I2C addresses of the RF modules belonging to the tenant being configured can be set (if changes from default values are required) as follows: • The BIM I2C Address (bus/slot) will automatically be filled in by the Hub Config Process. The MIB fields are: transceptBtsConnectionTable.transceptBtsConnectionBimI2cBus Page 25 © 2007, ADC Telecommunications, Inc.
  • Page 38 Clear field in the BTS Connection MIB for this tenant to a value of '1'. This will allow the configuration process to be restarted from the beginning. The MIB field is: transceptBtsConnectionTable.transceptBtsConnectionClear Page 26 © 2007, ADC Telecommunications, Inc.
  • Page 39 1-16. If both attenuators are configured, then software will configure the BIM to operate in duplexed mode, otherwise, software will configure the BIM to operate in non-duplex mode. The MIB fields are: transceptBtsControlParamsTable.transceptBtsControlParamsPowerAttenXLoc, where X = 1 or 2. Page 27 © 2007, ADC Telecommunications, Inc.

  • Page 40: Tenant Configuration

    RF paths can be individually enabled in the Tenant OAM MIB. Note: In Composite Mode, one (1) RF path is automatically enabled. 3.4.3 Setting Hub Measured Forward Gain transceptTenantOAMTable.transceptTenantHubMeasuredForwardGain This object is no longer used in the Digivance CXD/NXD system. Page 28 © 2007, ADC Telecommunications, Inc.

  • Page 41: Setting Ran Measured Forward Gain

    100 to +100, which is -10 to +10 dB in 1/10 dB units. The system assumes a 20 dB pad between the BIM and the BTS. If the 20 dB pad is not used then the +/- 10 dB gain setting maps to +10 to +30 dB of gain. Page 29 © 2007, ADC Telecommunications, Inc.

  • Page 42: Setting Reverse Cable Loss

    Tenant Mode is a object in the Tenant OAM MIB that will allow the tenant to be put into a special mode such as “disabled”, or “test”,. This functionality is not currently supported in the Digivance CXD/NXD software. 3.4.12 Enabling/Disabling Delay Compensation transceptTenantOAMTable.transceptTenantForwardDelayCompensationDisable transceptTenantOAMTable.transceptTenantReverseDelayCompensationDisable Page 30 © 2007, ADC Telecommunications, Inc.

  • Page 43: Forward/Reverse Target Delay

    Tenant OAM MIB with the naming convention. The values that are set in the Tenant OAM MIB will be pushed down to the appropriate FSC MIB Attenuator fields. Doing these settings in the Tenant OAM MIB will allow consistency with the maintenance of configuration data. Page 31 © 2007, ADC Telecommunications, Inc.

  • Page 44: Target Simulcast Degree

    RAN Ordering The IP Address and Hostname tables in the Tenant OAM MIB indicate which RAN, based on IP address and hostname, corresponds to RAN X, where X is the RAN ID (1-8). Page 32 © 2007, ADC Telecommunications, Inc.

  • Page 45: Bracketing Of Lost Rans

    CPU to its rack and chassis location such that field service personnel can be deployed to the correct location within the Hub when the need arises. Page 33 © 2007, ADC Telecommunications, Inc.

  • Page 46: Identification Using The Network Ip Receiver/Sender (Nip R/S)

    The “+” indicates the IP has been added to the list. A “-“ would indicate the IP has been removed from the list. This would occur, for example, if the communication link to that node was removed due to a power shutdown or other disruption. Page 34 © 2007, ADC Telecommunications, Inc.

  • Page 47: Accessing Nodes Locally

    • At a minimum, a MIB browser capable of SNMP level 2 sets and gets, coupled with a node map generator, would suffice. • Ability to output poll data to a database for customizable GUI operations such as user accounts and data sorting is strongly recommended. Page 35 © 2007, ADC Telecommunications, Inc.

  • Page 48: Configuring The Hubmaster Node

    XXX.YYY.ZZZ.1, to match the default Digivance CXD/NXD DHCP settings. The netmask prompt further defines which subnet the Hubmaster node will service. The default is 255.255.255.0, or a “class C netmask”. This is the recommended netmask value for the Digivance CXD/NXD system. Page 36 © 2007, ADC Telecommunications, Inc.
  • Page 49 The script will prompt “Enter a list of SNMP v1 trap-sinks, one per line: (control-d when done)” in order to set up any SNMP-V1 trap receivers that traps should be transmitted to. The Page 37 © 2007, ADC Telecommunications, Inc.

  • Page 50: Using Dynamic Host Configuration Protocol With Digivance Cxd/Nxd

    “free” addresses in that subnet. To avoid DHCP collisions and the perturbation of preexisting addresses, the operator would increase the DHCP server’s lower address limit from 172.20.88.3 to 172.20.88.4, and set the Hubmaster to be IP 172.20.88.3. Page 38 © 2007, ADC Telecommunications, Inc.

  • Page 51: Configuring The "Slave" And Ran Nodes

    Managing the Hub Node MIB This MIB correlates Hub node IP addresses with their hostnames and physical locations. It resides solely at Hubmaster nodes. It is comprised of the following elements: 3.8.1.1 Site ID transceptHubNodeTable.transceptHubNodeSiteID Page 39 © 2007, ADC Telecommunications, Inc.
  • Page 52 The Hub Node MIB contains a history of any Digivance CXD/NXD CPU ever seen by the Hubmaster. If a CPU is swapped out as part of a maintenance activity, the old entry will still Page 40 © 2007, ADC Telecommunications, Inc.

  • Page 53: Managing The Ran Node Mib

    This MIB correlates RAN node IP addresses with their hostnames and physical locations. It also documents where RF connections are made in each RAN. It resides solely at Hubmaster node. It is comprised of the following elements: Page 41 © 2007, ADC Telecommunications, Inc.
  • Page 54 For example, if the RFA attached to RUC A1’s “1/3” output is connected to a PCS ADB RFA, then transceptRanNodeTable.transceptRanNodeRuc1Pa1Connection should “pcsADB”. This data is best gathered at installation time. Repeat for all RUCs and RFAs as necessary. Page 42 © 2007, ADC Telecommunications, Inc.
  • Page 55 If this value is set to “enabled”, then the RAN Disable states that are maintained on a per-tenant basis in the Tenant OAM MIB will be used instead. Note: This overrides the tenant OAM MIB setting Page 43 © 2007, ADC Telecommunications, Inc.

  • Page 56: Bts Integration

    Figure • Composite Input Power – Sum of all carriers, no more than -4 dBm. • PA Output Power – Tenant MIB value used to measure Output of PA. Page 44 © 2007, ADC Telecommunications, Inc.
  • Page 57 3. Using the transceptTenantGenTwoTable. transceptTenantRucYAttenOffset field in the Tenant OAM MIB, adjust the RUC attenuator to perform final adjustments with all carriers present. A positive offset lowers the output power and negative offset increases it. Page 45 © 2007, ADC Telecommunications, Inc.
  • Page 58 +35.5 dBm (NXD) 47 dBm +40dBm +38 dBm (CXD) -9 dB Cellular +38.5 dBm (NXD) 47 dBm +43 dBm +41 dBm (CXD) -6 dB +41.5 dBm (NXD) Subtract 1 dB when using CDMA signals. Page 46 © 2007, ADC Telecommunications, Inc.

  • Page 59: Reverse Path Balancing

    1. Measure or calculate cable loss from BIM Output to BTS input 2. Enter cable loss value (forward and reverse) into the transceptTenantForwardCableLoss and transceptTenantReverseCable Loss fields of the Tenant OAM MIB field for this Tenant Sector Page 47 © 2007, ADC Telecommunications, Inc.

  • Page 60: Functional Ran Call Verification

    Updating System Software The ADC software upgrade process is based on packaging utilities built into the Linux-based operating system used by ADC. The software upgrade is a set of interdependent packages delivered in a self-extracting executable named so as to reflect the revision of the contained software;...

  • Page 61: Upgrading An Existing System

    • Checks to be sure that upon completion of the upgrade, certain processes are running (or no longer running, as the case may be) as expected. • Test scripts being run to ensure that processes are running as expected. Page 49 © 2007, ADC Telecommunications, Inc.
  • Page 62 Evaluate the software version to be sure that it matches what is intended. This can be done from evaluating Network Node field transceptNetwork NodeOpencellSoftwareRev. Alternatively, this value can be retrieved in the telnet session to the opened previous step entering: snmpget localhost patriots transceptNetworkNodeOpencellSoftwareRev.0. Page 50 © 2007, ADC Telecommunications, Inc.

  • Page 63: Failed Upgrades

    CPU did prior to the upgrade. There are simply too many variables to guarantee this. The regression test cycle here at ADC will include a series of steps to validate that the uninsulated/downgrade process works, but it is extremely difficult to guarantee that all possible failure paths will be exercised.

  • Page 64: Fic Software Upgrade

    These files will be bundled into a file that will be stored on the CPU being upgraded, in the /var directory. This file will be given a name that associates it with version of the upgrade being performed, for example: backup-pre-2.1.0.tar.gz. Page 52 © 2007, ADC Telecommunications, Inc.

  • Page 65: Backup

    “--restore”. Adding/Removing SNMP Traps SNMP traps are sent automatically by the ADC system to all managers named “trap-sink” in DNS. To add an entry to DNS, use the nsupdate (sudo nsupdate) command on the hubmaster. The application nsupdate will prompt for an input, (‘>’) at which point enter:...

  • Page 66: Updating Spare Cpus

    CPU with the method described above. However, if the spare CPU in this example is at 1.7.0, it is not possible. This implies that if an ADC software release is of a new major revision, spare CPUs in stock need to be upgraded at the same time as all of the other CPUs in the fielded system.

  • Page 67: Mib Extraction

    • FTP to one of the updated CPUs, logging in as username = operator and password = operate. • Change to the directory containing the ADC MIBs directory by entering: cd /usr/share/mibs/ • Bundle and zip all the MIBs into a tarball and extract them by entering: get transcept.tar.gz.

  • Page 68: Gain Management And Fault Detection

    Reverse Delay Management (RDM) is a software function that is part of Tenant Processing and whose responsibility is to equalize the path delays to all RANs in a simulcast group. The RDM process is “enabled” in the Tenant OAM MIB (see Section 3, Sub-Section 7 Tenant Configuration). Page 56 © 2007, ADC Telecommunications, Inc.

  • Page 69: Forward Continuity

    If the test tone is not detected in the RAN SIF, then the RDC is reported as faulting. See troubleshooting guide for details. Page 57 © 2007, ADC Telecommunications, Inc.

  • Page 70: Pa Overpower Protection

    The limits are set to 1 dB above the rated output for a given Power Amplifier. For 10 watt PAs (40 dBm), the limit is 41 dBm. For 20 watt PAs (43 dBm), the limit is 44 dBm. See the “SNMP Agent and Fault Isolation Guide” guide for details. Page 58 © 2007, ADC Telecommunications, Inc.

  • Page 71: Hub Overpower Protection

    FSC MIB will be set such that the NMS report the condition and an operator can take corrective action. This MIB entry can be found as follows: transceptFscHopTable.transceptFscHopModeRms Status values include hopActive and hopInactive. See the “SNMP Agent and Fault Isolation Guide” guide for details. Page 59 © 2007, ADC Telecommunications, Inc.

  • Page 72: Customer Information And Assistance

    Contents herein are current as of the date of publication. ADC reserves the right to change the contents without prior notice. In no event shall ADC be liable for any damages resulting from loss of data, loss of use, or loss of profits and ADC further disclaims any and all liability for indirect, incidental, special, consequential or other similar damages.
  • Page 74 www.adc.com...

This manual is also suitable for:

Digivance nxd

Table of Contents