ADCP-75-192 Preliminary Issue D October 2005 Digivance CXD Multi-Band Distributed Antenna System Installation and Operation Manual 1343155 Rev 1
ADCP-75-192 Preliminary Issue D October 2005 Digivance CXD Multi-Band Distributed Antenna System Installation and Operation Manual 1343155 Rev 1
ADCP-75-192 • Issue D • October 2005 • Preface COPYRIGHT 2005, ADC Telecommunications, Inc. All Rights Reserved Printed in the U.S.A. REVISION HISTORY ISSUE DATE Issue D 10/2005 REASON FOR CHANGE Original release LIST OF CHANGES The technical changes incorporated into this issue are listed below. SECTION IDENTIFIER - - DESCRIPTION OF CHANGE Original release TRADEMARK INFORMATION ADC and Digivance are registered trademarks of ADC Telecommunications, Inc.
ADCP-75-192 • Issue D • October 2005 • Preface TABLE OF CONTENTS Content Page FRONT MATTER ABOUT THIS MANUAL ....................................................................... v RELATED PUBLICATIONS ..................................................................... v ADMONISHMENTS ........................................................................ vi GENERAL SAFETY PRECAUTIONS............................................................... vi SAVE WORKING DISTANCES ...........................
ADCP-75-192 • Issue D • October 2005 • Preface TABLE OF CONTENTS Content Page 3.4 4 CompactPCI Power Supply ....................................................... 2-16 HUB............................................................................ 2-16 4.1 Full Band HDC (FBHDC) ........................................................ 2-16 4.2 Forward Simulcast Module, FSC ................................................... 2-18 4.3 Hub Upconverter Module, HUC .....................................
ADCP-75-192 • Issue D • October 2005 • Preface TABLE OF CONTENTS Content Page 7.19 Module Attenuators ........................................................... 3-16 8 9 10 11 MANAGING THE TENANT OAM ADDRESS AND HOSTNAME TABLES ................................. 3-17 8.1 RAN Ordering ............................................................... 3-17 8.2 Bracketing of Lost RANs ........................................................ 3-17 8.3 Clearing of RANs ...................................
ADCP-75-192 • Issue D • October 2005 • Preface TABLE OF CONTENTS Content Page 2.3 iDEN....................................................................... 5-3 SECTION 6 SOFTWARE UPDATES 1 SOFTWARE RELEASE DELIVERABLE ....................................................... 6-1 2 RELEASE NOTES .................................................................... 6-1 3 UPGRADING EXISTING SYSTEM .......................................................... 6-1 3.1 Preliminary Steps ....................
ADCP-75-192 • Issue D • October 2005 • Preface TABLE OF CONTENTS Content Page SECTION 9 GENERAL INFORMATION 1 WARRANTY/SOFTWARE ............................................................... 9-1 2 SOFTWARE SERVICE AGREEMENT ........................................................ 9-1 3 REPAIR/EXCHANGE POLICY ............................................................ 9-1 4 REPAIR CHARGES ................................................................... 9-2 5 REPLACEMENT/SPARE PRODUCTS.......
ADCP-75-192 • Issue D • October 2005 • Preface ABOUT THIS MANUAL This installation and operation manual provides the following information: • An overview of the Digivance CXD system. • A description of the basic system components including the Digital Chassis, RF Chassis, CPU, STF, HDC, HUC, SIF, FSC, RSC, cPCI Power Supplies, RAN, RDC, RUC, and LPA. • Installation procedures for the HUB assembly. • Procedures for tuning-up the system and verifying that the system is functioning properly.
ADCP-75-192 • Issue D • October 2005 • 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 D • October 2005 • Preface Caution This system is a RF Transmitter and continuously emits RF energy. Maintain 3 foot minimum clearance from the antenna while the system is operating. Wherever possible, shut down the RAN before servicing the antenna. Caution: Always allow sufficient fiber length to permit routing of patch cords and pigtails without severe bends. Fiber optic patch cords or pigtails may be permanently damaged if bent or curved to a radius of less than 2 inches (50 mm).
ADCP-75-192 • Issue D • October 2005 • Preface COMPLIANCE STATEMENT Each respective SMR, Cellular, and PCS system in this CXD platform is singularly FCC and IC approved. Information in this manual explains applicable portions of these systems. FCC: This Digivance CXD complies with the applicable sections of Title 47 CFR Part 15, 22, 24 and 90. The Digivance CXD Hub has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC rules.
ADCP-75-192 • Issue D • October 2005 • Preface CD-ROM COM Config CUL DAS DC DCE Div DTE EIA EMS ESD F FCC FDA FSO Fwd GFC GUI IC LED LPA MHz MI MPE MTBF NC NEM NO NOC NPT OSP PA PC PCS Prg Pwr Re RF RIM RMA RU Page xii 2005, ADC Telecommunications, Inc.
ADCP-75-192 • Issue D • October 2005 • Preface RX SMR STM TX UL VAC VDC VSWR WECO WDM Receive or Receiver Specialized Mobile Radio Spectrum Transport Module Transmit or Transmitter Underwriters Laboratories Volts Alternating Current Volts Direct Current Voltage Standing Wave Ratio Western Electric Company Wave Division Multiplexer Common Items (HUB or RAN) CPU NMS BTS BIF STF SIF MAC RAN Node WBDOT Central Processing Unit Network Management System Base TRANsceiver Station Backplane Interface System Inte
ADCP-75-192 • Issue D • October 2005 • Preface C/MCPLR RDC PQP CTP CDP IB EB RPS LVD RIC ANT RAN APEC DPEC CPCIP Page xiv 2005, ADC Telecommunications, Inc.
ADCP-75-192 • Issue D • October 2005 • Section 1: Overview SECTION 1: OVERVIEW Content 1 INTRODUCTION .................................................................... 1-1 2 DIGIVANCE CXD SYSTEM OVERVIEW ...................................................... 1-1 3 1 Page 2.1 Basic Components ............................................................. 1-2 2.2 General Description ............................................................ 1-2 2.3 Local Service Interface ....................
ADCP-75-192 • Issue D • October 2005 • Section 1: Overview 2.1 Basic Components Figure 1-1 illustrates a Digivance CXD system with RAN’s distributed over a desired geographical area, connected back to a group of Wireless Service Provider (WSP) base stations at a Hub locale. The illustration shows utility pole mounted RAN’s, with pole top antennas. The Digivance CXD Hub Equipment is comprised of Digital and RF cPCI chassis’ in a 19” rack assembly.
ADCP-75-192 • Issue D • October 2005 • Section 1: Overview In the reverse path, the antenna receives RF signals from a mobile and sends those signals into the RFA which contains a diplexer and Low Noise Amplifier. The output of the RFA is connected the RAN Down Converter (RDC) which down converts the RF back to IF and digitizes the signals. The DIF signals are passed to the SIF, which sends digital optical signals from the RAN to the HUB SIF.
ADCP-75-192 • Issue D • October 2005 • Section 1: Overview The Digivance CXD Element Management System is a Web based system that provides the various control and monitoring functions required for local management of each CXD system. The user interface into the EMS is a PC-type laptop computer loaded with a standard Web browser. The EMS is connected to the Master CPU through an Ethernet connection. Operation is effected through the EMS Graphical User Interface (GUI).
ADCP-75-192 • Issue D • October 2005 • Section 1: Overview 3.2 Control and Monitoring Software The Digivance CXD EMS or customer supplied NMS using the Digivance CXD SNMP Agent is used to provision and configure the system for operation. This includes initializing the system, setting up the Hub and RAN element identification schemes, tenant processing, setting alarm thresholds, and setting forward and reverse path RF gain adjustments.
ADCP-75-192 • Issue D • October 2005 • Section 1: Overview Hub Power Off • Power to the Hub racks is disabled at the power system supplied by the customer. Hub CompactPCI Chassis Power Off • Identify the power supply module for the chassis to be powered off • Extract the power supply module(s) from the chassis 3.4.2 RAN Power on/off RAN Equipment Power On • Plug the AC line cord into the receptacle located between the cPCI power supplies.
ADCP-75-192 • Issue D • October 2005 • Section 1: Overview 3.6.1 Central Processing Unit (CPU) The RAN has a cPCI based single-board computer with a Central Processing Unit (CPU) operating LINUX. RAN CPU: 1. Manages all RAN hardware including RF and Digital equipment 2. Manages gain & delays 3. Monitors signal presence and quality 3.6.2 System Interface (STF) The System Interface (STF) module provides the ability to communicate between the CPU and other modules (RDC, RUC, RIC) using four I2C busses.
ADCP-75-192 • Issue D • October 2005 • Section 1: Overview 3.6.8 DC Power Entry Card (DPEC) The DPEC is used to distribute DC power to the cPCI power supplies in the RAN and is used when the battery backup option is used. 3.6.9 CompactPCI RAN Power Supply (RPS) The CompactPCI (cPCI) Power Supplies provide +/-12V, 5V and 3.3 V DC power to the cPCI backplane for use by the RAN modules. These units are hot swappable and can be redundant when used in pairs. 3.6.
ADCP-75-192 • Issue D • October 2005 • Section 1: Overview support the desired coverage objectives. Proper antenna selection and the mounting installation is the responsibility of the customer. When using customer supplied antenna, they should meet or exceed the following antenna specifications: • VSWR (all bands): 1.5:1 typ, 1.65:1 max • Maximum power input: 200W (average) 1000W (peak) • Passive Intermodulation Distortion: -153dBc (maximum) 3.
ADCP-75-192 • Issue D • October 2005 • Section 1: Overview 3.7.1 Digital CompactPCI Chassis & Backplane The CompactPCI Digital Chassis houses cooling fans, the CPU, System Interface Module, Sonet Interface Module, Reverse Simulcast Module and power supplies. The backplane provides the distribution for clock, communication, control data and timing. 3.7.
ADCP-75-192 • Issue D • October 2005 • Section 1: Overview 3.7.5 Sonet Interface (SIF) The Sonet Interface module provides the fiber interface between the Hub and RAN’s. This interface includes: 1. Digitized RF Signal information 2. 10BaseT Ethernet for command and control between Hub and the RAN’s. 3.7.6 Hub Down Converter (HDC) The HDC down converts the forward RF carrier to an intermediate frequency (IF) that can be digitized. Each HDC can support up to four separate RF carriers.
ADCP-75-192 • Issue D • October 2005 • Section 1: Overview 3.7.12 Ethernet Hub Each Hub rack is equipped with a 24 port Ethernet Hub, at the top of the rack, below the HRM. It is powered by 120 VAC. An optional –48 VDC can be chosen. The Ethernet Hub is used to connect RAN CPU’s (through Hub SIF’s) and Hub CPU’s to and existing LAN/WAN and to each other. 3.8 Communication Interfaces 3.8.1 I2C I2C is a bi-directional serial bus that provides a simple, efficient method of data exchange between devices.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description SECTION 2: DESCRIPTION Content 1 2 3 4 1 Page INTRODUCTION .................................................................... 2-1 1.1 Digital Chassis ............................................................... 2-1 1.2 RF Chassis .................................................................. 2-3 1.3 Radio Access Node (RAN) ....................................................... 2-4 ELEMENTS COMMON TO HUB AND RAN ............
ADCP-75-192 • Issue D • October 2005 • Section 2: Description Figure 2-1. Digital Chassis The following is specified per the Digivance CXD system configuration: • Sonet Interface Module • Systems Interface Module • Reverse Simulcast Module • Master Processor Module • Slave Processor Module The quantity for each module is determined by the tenant network configuration. Note that each card slot is not equivalent, thus requiring certain modules to be specifically located within the chassis.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description 1.2 RF Chassis The RF Chassis, shown in Figure 2-2, is a rack-mounted chassis that can house up to 8 industry standard cPCI circuit card modules (non-CPU only). Modules may be extracted by pushing outward on the extractor release buttons and then withdrawing the module from the chassis. They are inserted by aligning the module into the desired slot and then pressing inward on the extractor button until the module is securely seated.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description Connection of power is described per wiring diagram. Air baffles are inserted into unused slots. Modules are extracted by pushing outward on the extractor release buttons and drawing the module out of chassis. They are inserted by aligning the module into desired slot and pressing inward on the extractor button until the module is securely seated. Refer to Table 2-3 for slot assignments.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description Figure 2-3. CXD RAN Cabinet • Provides a point for terminating the coaxial antenna cable, the fiber optic cable, the AC power cable, and ground cable. • Provides AC power surge protection • Provides lightning protection • Provides limited storage for fiber optic pigtails. The RAN cabinet is weather-tight but contact with salt-air mist should be avoided as it may degrade the MTBF of the product.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description The front panel controls for the CPU are: • Reset – Recessed reset button The front panel indicators for the CPU are: • Activity LED’s – 8 Yellow LED’s flashing when the OS is operating ( 1) UN IVE R S A L S ER IA L B US C O N N E C T O R ( 6 ) E T H ER N E T C O N N E C TO R (2 ) C OM 1 C ON N EC TOR ( 5 ) A C T IVIT Y LE D 'S ( 3 ) H O T S WA P LE D ( 4 ) R ES E T B UT T O N Figure 2-4. CPU Front Panel Table 2-4.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description 2.2 STF2 The System Interface (STF2) module is installed into the Digital Chassis and provides the ability to communicate between the CPU and other modules (e.g., HDC, FSC, and HUC), using four I2C busses. The STF also communicates with the GPS module found in the Master Hub Reference Module. STF modules are specified according to the number of qualifying communications devices being utilized.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description ( 2 ) R E S E T S WIT C H ( 1) GP S LE D ( 3 ) S T A T US LE D 1 ( 4 ) S T A T US LE D 2 ( 5 ) I2 C C O M M LE D ( 10 ) I2 C C O N N E C T O R S ( 6 ) I2 C E R R O R LE D ( 7 ) F A ULT LE D ( 9 ) P O WE R LE D ( 8 ) H O T S WA P LE D Figure 2-5. STF Front Panel Table 2-5. STF User Interface REFN o.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description Table 2-5. STF User Interface, continued REF No. USER INTERFACE DESIGNATION 8 DEVICE FUNCTIONAL DESCRIPTION Hot Swap LED Single-colored LED (Blue) Status indicator turns blue when board can be hot swap extracted. (not used) 9 Power LED Single-colored LED (Green) Status indicator turns green when module has power. 10 I2C Connectors RJ-45 connectors I2C interface 2.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description • FLT LED – Red fault LED lighted when module has failed lite upon startup until the module has been initialized • PWR LED – Green Power LED lighted when module has power • HS LED – Hot Swap Blue LED, turns blue when board can be hot swap extracted If this LED is lighted without the green PWR LED lighted then the hot swap controller failed to initialize. Remove and reinstall module.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description Table 2-6. SIF User Interface, continued 3 REF No. USER INTERFACE DESIGNATION 6 DEVICE FUNCTIONAL DESCRIPTION Fault LED Single-colored LED (Red) Status indicator turns red when module has failed. Indicator is lit during start-up until the module has initialized.. 7 SFP Fiber Optic Connector Dual-LC connectors Fiber connector on SFP optical transceiver.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description ( 1) C H A N N E L 1 ( 4 ) P O WE R LE D ( 2 ) F A ULT LE D ( 3 ) C H A N N EL 2 Figure 2-7. RDC2 Front Panel Table 2-7. RDC2 User Interface REFN o. USER INTERFACE DESIGNATION 1 DEVICE FUNCTIONAL DESCRIPTION Channel 1 RF Connector SMA connector RF input for Channel 1 2 Fault LED Single-colored LED (Red) Status indicator turns red when module has failed. Indicator is lit during start-up until the module has initialized.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description 3.2 RUC The RAN Up Converter (RUC3) takes IF signals from a DIF signal generated by a SIF and up converts the signals to RF. The RF is connected to The front panel indicators for the RAN Up Converter are: • COM 1/3 – Yellow LED indicting DIF lock to SIF channel 3 • COM 2/4 – Yellow LED indicting DIF lock to SIF channel 4 • FLT LED – Red LED lighted when module has failed or upon startup until the module has been initialized.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description Table 2-8. RUC3 User Interface, continued REFN o. USER INTERFACE DESIGNATION 4 DEVICE FUNCTIONAL DESCRIPTION Fault LED Single-colored LED (Red) Status indicator turns red when module has failed. Indicator is lit during start-up until the module has initialized.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description ( 1) P O WE R A M P LIF E R F A N S ( 9 ) I2 C C O N N E C T O R ( 2 ) A C IN P UT ( 8 ) P O WE R LE D ( 7 ) P A 1 F A ULT LE D ( 3 ) R F TX P OR T ( 6 ) P A 2 F A ULT LE D (4 ) R F TX P OR T (5 ) A N TEN N A C ON N EC TOR Figure 2-9. RF Assembly Module Front Panel Table 2-9. RFA User Interface REF No.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description 3.4 CompactPCI Power Supply The front panel indicators for the RAN CompactPCI power supplies are: • Fault LED – Yellow LED lighted when module is failed • Power LED – Green LED lighted when module has power ( 2 ) F A ULT LE D ( 1) P O WER LE D Figure 2-10. CompactPCI Power Supply Front Panel Table 2-10. cPCI User Interface 4 REFN o.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description ( 1) IF 1 A N D T X1 C O N N EC T O R S ( 2 ) IF 2 A N D T X2 C ON N EC TOR S ( 6 ) P O WE R LE D ( 3 ) F A ULT LE D ( 4 ) IF 3 A N D T X3 C ON N EC TOR S ( 5 ) IF 4 A N D T X4 C O N N EC T O R S Figure 2-11. Full Band HDC Module Table 2-11. Full Band HDC User Interface REF No.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description Additionally, the EEPROM will contain the offset from the +12 dB gain setting. This includes: • Data for each channel (1-4) • Offset for the start and end of each band This data will be used when balancing a system. It is intended that software will automatically normalize the gains across channels to insure that the output data from the FSC has all channels equalized in gain to within 1 dB. Figure 2-12. Full Band HDC Interface 4.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description • FLT LED – Red LED lighted when module has failed or upon startup until the module has been initialized. This light will blink after the module receives a system clock and is awaiting initialization. • PWR LED – Green LED lighted when module has power. ( 1) E TH E R N E T C ON N EC TOR ( 2 ) IF C O N N E C T O R S 1- 8 ( 4 ) F A ULT LE D ( 3 ) P O WE R LE D Figure 2-13. Forward Simulcast Card Front Panel Table 2-12.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description 4.3 Hub Upconverter Module, HUC The front panel indicators for the Hub Up Converter are: • FLT LED – Red LED lighted when module has failed or upon startup until the module has been initialized.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description Table 2-13. HUC User Interface, continued REF No. USER INTERFACE DESIGNATION DEVICE FUNCTIONAL DESCRIPTION 4 Power LED Single-colored LED (Green) Status indicator turns green when module has power. 5 Diversity Path RF connector SMA connector RF connector for diversity receive path 6 Diversity Path Locked LED Single-colored LED (Yellow) Status indicator turns yellow when diversity receive path is locked to RSC or SIF 4.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description Each RSC module supports primary and diversity reverse DIF path summation and outputs two (2) separate DIF signals. ( 1) D IF IN P UT LE D 1- 8 ( 2 ) D IF O UT P UT LE D 1- 4 ( 5 ) F A ULT LE D ( 4 ) P O WE R LE D ( 3 ) H O T S WA P LE D Figure 2-15. Reverse Simulcast Card Front Panel Table 2-14. RSC User Interface REFN o.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description 4.5 Hub Reference Module, HRM The Hub Reference Module (HRM) provides GPS timing and clocking data that gets distributed throughout a Digivance CXD Hub. ( 1) G P S IN ( 2 ) GP S A UXILLA R Y (8) R S -2 3 2 C ON N EC TOR ( 3 ) C LO C K T E S T P O IN T S ( 7 ) 1 H Z LE D ( 4 ) F A ULT LE D ( 6 ) P P L LO C K LE D ( 5 ) P O WE R LE D Figure 2-16. Hub Reference Module Front Panel Table 2-15. HRM Front Panel User Interface REF No.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description • Clock Test Points 1 PPS – One Pulse Per Second from GPS REF – 9.6 MHz RF Reference Clock Samp – 42.912 MHz Sample Clock • LED’s PLL lock – Yellow – indicates the phase lock loop circuit is locked FLT – Red – indicates there is a fault with the HRM PWR – GRN – indicates power is applied to the HRM Refer to the Digivance CXD Installation Manual for details on I2C configuration.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description 4.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description • SMR/CELL/PCS LED – Yellow LED lighted indicating BIM band configuration • I2C Address display – Displays I2C address, 0-5 • SMR/CELL/PCS – Indicates Protocol • PWR - Indicates Power is applied • FAULT – Indicates BIM Fault ( 1) B A S E S T A T IO N D UP LE XE D R F C ON N EC TOR S ( 2 ) T R A N S M IT S IM P LE XE D R F C ON N EC TOR S ( 3 ) F A ULT ( 6 ) R E C E IVE P R IM A R Y A N D D IVE R S IT Y R F C O N N E C T O R S ( 4 )
ADCP-75-192 • Issue D • October 2005 • Section 2: Description Figure 2-20. Attenuator Shelf 4.9 Specifications The specifications for the Digivance CXD are provided in Table 2-19. All specifications apply after a five minute warm-up period. Table 2-19.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description Table 2-19. Digivance CXD Specifications, continued PARAMETER SPECIFICATION SMR 900 MHz 935 to 940 MHz 1900 MHz Lowerband 1930 to 1965 MHz 15 MHz bandwidth selectable 1900 MHz Upperband 1965 to 1995 MHz 15 MHz bandwidth selectable Intermodulation -60 dBc At remote output, two tone Spurious -60 dBc RF gain 10 dB Gain flatness Band flatness Channel flatness REMARKS ±2.0 dB across freq. Range ±1 dB variation across any 1.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description Table 2-19.
ADCP-75-192 • Issue D • October 2005 • Section 2: Description Table 2-19. Digivance CXD Specifications, continued PARAMETER SPECIFICATION REMARKS Battery backup options Internal – Slot assembly External 1 hour 2 hour Takes one RFA slot Power consumption 600 W Two 10 W PA option Reliability at 25º MTBF 50,000 Excluding fan assemblies Note 1: Per Industry Canada Section 5.3 - The rated output power of this equipment is for single carrier operation.
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup SECTION 3: NETWORK AND SYSTEM INSTALLATION AND SETUP Content Page 1 INTRODUCTION .................................................................... 3-2 2 NETWORKING OVERVIEW.............................................................. 3-2 3 NODE IDENTIFICATION SCHEMES ........................................................ 3-3 4 IDENTIFICATION USING THE NETWORK IP RECEIVER/SENDER SYSTEM ................
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup 10.2 11 1 Using Dynamic Host Configuration Protocol with Digivance CXD .............................. 3-22 CONFIGURING THE HUB “SLAVE” AND RAN NODES............................................ 3-24 11.1 Managing The Hub Node MIB ..................................................... 3-24 11.2 Managing the RAN Node MIB .....................................................
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup A CPU called the Hub Master is a special Hub node that controls tenant processing for Digivance CXD nodes on its subnet. For a definition of tenant sectors, see Section 6.1. The Hub Master also functions as a time server for a Digivance CXD subnet (using Network Timing Protocol), and can be set up to provide DHCP (Dynamic Host Configuration Protocol) and DNS (Domain Name Service) to its subnet as well.
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup Table 3-1.
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup • Ensure that HDC modules are connected to FSC modules as shown in the diagram. HDC’s below an FSC have their outputs connected to FSC inputs 1, 3, 5, and 7. HDCs above an FSC have their outputs connected to FSC inputs 2, 4, 6, and 8. HDCs using composite mode will only require HDC Output IF 1 to be connected to FSC CH 1.
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup 6.2 BTS Connection MIB Within the Hub Master node, the BTS Connection MIB is used to create new tenant base station sector instances (simply called "tenants" from here on) to be configured, monitored, and controlled in the Digivance CXD system.
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup 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 US800SMR (10) - Cellular SMR band The MIB field is: transceptBtsConnectionTable.transceptBtsConnectionTenantBand 6.2.5 Setting the BIM Rack/Shelf ID The location information (rack/shelf) of the BIM module belonging to this tenant must be configured.
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup transceptBtsConnectionTable.transceptBtsConnectionHdcXI2cBus and transceptBtsConnectionTable.transceptBtsConnectionHdcXI2cSlot, where X = 1 or 2. • The HDC modules belonging to this tenant are cabled to a single FSC module, which is located in a chassis slot either directly above and/or below the tenant's HDC module(s).
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup 6.2.9 Maximum Number Of Carriers This parameter is no longer used in the Digivance CXD system. transceptBtsControlParamsTable.transceptBtsControlParamsMaxCarriers. 6.2.10 Composite Mode The Digivance CXD default forward gain balance is called “composite mode”. In this mode, an RF input signal of -4 dBm RMS at HDC input “RF 1” will yield an output of 38 dBm RMS at each RAN antenna port.
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup • The Path Flag is a one-character string, “M”, "P" or "D" that indicates the path on which the path trace was transmitted (“M”=Main Forward, “P”=Primary Reverse, “D”=Diversity Reverse). The delimiter used to separate the primary sub-strings of the pathtrace string is a single character, currently a comma (","). An example of a complete pathtrace string is as follows: wspname:bts4:alpha:us1900A,172.20.1.1,P 6.3.
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup 6.3.2 Pathtrace Forward Transmission Though the BIM, HDC(s), and FSC all create the pathtrace string and report it in their MIB’s, the FSC is the originator of the pathtrace string in the forward path of the system. The FSC HCP writes the pathtrace string to its FPGA, which transmits the pathtrace string through all eight (8) of its simulcasted outputs.
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup pathtrace based on Tenant ID sub-strings. When the majority input is discovered, the RSC will parse the Tenant ID from one of the majority inputs, append its own CPU IP Address, and transmit the newly created pathtrace string to its two outputs (primary/diversity). Finally, the HUC module receives the primary/diversity reverse pathtrace strings into its FPGA from its two DIF input connections.
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup 7.2 Setting Channels transceptTenantOAMTable.transceptTenantChannelXVal, where X = 1-8 Each Tenant sector in the Digivance CXD system can support from 1-8 channels. Each of these eight (8) channel values can be individually set in the Tenant OAM MIB. The valid range of values is based on the band and protocol selected for this tenant, per the specifications used to define each protocol.
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup 7.7 Setting Reverse Gain transceptTenantOAMTable.transceptTenantReverseGain The Reverse Gain parameter in the Tenant OAM MIB allows the Reverse Gain Target to be set. This value sets the gain for the entire reverse path - it is not separated into a separate Hub and RAN parameter as in the forward path. The valid range of values for this parameter is -100 to +300, which is -10 to +30 dB in 1/10 dB units.
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup 7.13 Enabling / Disabling Delay Compensation transceptTenantOAMTable.transceptTenantForwardDelayCompensationDisable and transceptTenantOAMTable.transceptTenantReverseDelayCompensationDisable The Forward and Reverse Delay Compensation processes, which balance the signal delay in a simulcast group, can be enabled/disabled using the associated parameters in the Tenant OAM MIB.
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup 7.17 FSC Attenuator Offsets transceptTenantCalTable.transceptTenantFscAttenX If not using Composite Mode, there is a step during Forward RF Path Balancing that requires that the FSC Digital path attenuators to be adjusted. These adjustments need to be made in the Tenant OAM MIB in the FSC Attenuator Offset fields, of which there is one per channel in the Tenant OAM MIB with the naming convention.
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup 8 MANAGING THE TENANT OAM ADDRESS AND HOSTNAME TABLES Within the Tenant OAM MIB, there are two (2) tables used to capture the current IP Addresses and Hostnames of all CPUs that are associated with a given tenant sector. The ordering of the CPUs in the MIB tables is such that the RAN CPUs are listed first from 1-8, followed by the Hub CPUs.
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup 8.3 Clearing of RAN’s In order to facilitate swap outs of RAN CPUs, it is possible for the RAN Hostname values in the Hostname table of the Tenant OAM MIB to be cleared by writing a NULL string into the MIB from the NMS. Doing so will allow that RAN ID to be cleared, and will allow the next RAN CPU discovered to occupy that RAN ID. 9 HUB NODE ACCESS/MANAGEMENT 9.
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup +172.20.1.1 +172.20.1.249 +172.20.1.250 -172.20.1.246 +172.20.1.247 +172.20.1.242 Figure 3-3. Typical NIPR/S Output Using Telnet 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. 9.
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup 9.5 Using a Third Party Network Management System with Digivance CXD Digivance CXD control and monitoring is executed via Simple Network Management Protocol (SNMP). As such, any Network Management System (NMS) based on SNMP will be compatible with the Digivance CXD system. However, not all NMS products are the same.
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup 10.1 Utilizing The Configure-Hubmaster Script Use the following procedure to invoke the configure-hubmaster script: • Login locally to the target node as operator • Type “sudo /usr/sbin/configure-hubmaster” and enter the password when prompted. • Enter the information as shown in the following paragraphs. 10.1.
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup 10.1.5 DNS Forwarding The script will prompt “Enter a list of upstream DNS servers, one per line: (control-d when done)” to set up DNS forwarding. It is expecting as input the IP address of each Domain Name Server that the Hub Master node can connect to. If there are no upstream DNS servers, leave this entry blank. Hit CNTRL-D when finished entering DNS upstream servers.
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup 10.2.2 Incorporating Existing LAN DHCP Using a pre-existing LAN DHCP server is ideal when the Digivance CXD network only contains one Hub Master node. In this configuration, there is no need for a router between the Hub Master and the rest of the LAN, since all nodes are on the same subnet.
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup 10.2.5 Incorporating Existing LAN DNS The method of incorporating an existing LAN DNS begins with configuring the Hub Master DNS forwarding as outlined in Section 10.1.5 and continues with some maintenance at the upstream DNS. At a minimum, the upstream DNS needs to be updated with each Hub Master node’s IP address and full hostname (including its domain).
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup 11.1.4 Hostname transceptHubNodeTable.transceptHubNodeHostname This entry shows the hostname of the CPU occupying a specific row of the Hub Node MIB. This entry is automatically set up by Digivance CXD system software. Changing hostnames on Digivance CXD nodes is not recommended, but can be accomplished by logging into the target node. 11.1.5 IP Address transceptHubNodeTable.
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup For cases where a GPS receiver is not present and it is desired to manually enter the GPS coordinates, the Hub Node MIB contains two MIB fields to configure the GPS longitude and latitude settings. Since only the Hub Master node in the Digivance CXD system contains a GPS receiver, these MIB fields will not be used for Hub Slave nodes.
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup 11.2.5 RucXPaY Connection transceptRanNodeTable.transceptRanNodeRucXPaYConnection, where X=1-3, Y=1-2 These entries manually record the RF connection path between the RAN UpConverter’s PA outputs and the antenna. For example, if the PA attached to RUC A1’s “1/3” output is connected to a PCS quadplexer through the B-band port, then transceptRanNodeTable.
ADCP-75-192 • Issue D • October 2005 • Section 3: Network and System Installation and Setup 11.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 D • October 2005 • Section 4: BTS Integration SECTION 4: BTS INTEGRATION Content 1 BTS VALIDATION ................................................................... 4-1 2 CHANNEL SELECTION ................................................................ 4-1 3 1 Page 2.1 iDEN – SMR ................................................................. 4-1 2.2 CDMA Cellular – EIA/TIA-97....................................................... 4-2 2.3 GSM 850 ........................
ADCP-75-192 • Issue D • October 2005 • Section 4: BTS Integration 2.2 CDMA Cellular – EIA/TIA-97 BLOCK VALID CHANNEL # MOBILE TX (MHZ) BTS TX (MHZ) A” No 991-1012 824.040-824.670 869.040-869.670 Yes 1013-1023 824.700-825.000 869.700-870.000 Yes 1-311 825.030-834.330 870.030-879.330 No 312-333 834.360-834.990 879.360-879.990 No 334-355 835.020-835.650 880.020-880.650 Yes 356-644 835.680-844.320 880.680-889.320 No 645-666 844.350-844.980 889.350-889.980 No 667-688 845.
ADCP-75-192 • Issue D • October 2005 • Section 4: BTS Integration 2.5 TDMA 1900 BLOCK VALID CHANNEL # MOBILE TX (MHZ) BTS TX (MHZ) TDMA 1900 Yes 2-1998 1850.040 + 0.030 * (N-2) 1930.080 + 0.030 * (N-2) 2.6 GSM 1900 BLOCK VALID CHANNEL # MOBILE TX (MHZ) BTS TX (MHZ) GSM 1900 Yes 512-810 1850.200 + 0.200 * (N-512) 1930.200 + 0.200 * (N-512) 2.7 CDMA 1900 3 BLOCK VALID CHANNEL # MOBILE TX (MHZ) BTS TX (MHZ) CDMA 1900 Yes 1-1200 1850.000 + 0.050 * (N-1) 1930.000 + 0.
ADCP-75-192 • Issue D • October 2005 • Section 4: BTS Integration For Tenants that require a different number of RF channels, then the forward PA output powers are changed using the following equation: • Forward PA output change = 10*log10(baseline # RF channels /new # RF channels). For example, if a PCS/CDMA WSP requires 6 RF channels, then the forward PA output power per RF channel is adjusted by 10*log10(3/6) = -3.0 dB. The per RF channel power is changed from 34 to 31dBm.
ADCP-75-192 • Issue D • October 2005 • Section 4: BTS Integration Table 4-3. RAN Output - 8 Tenant BAND PCS PROTOCOL CDMA PCS PCS PCS CELL CELL CELL CELL SMR GSM TDMA EDGE CDMA GSM TDMA EDGE IDEN # Carrier 1 39.5 40.5 40.5 40.5 36.5 37.5 37.5 37.5 37.5 2 36.5 37.5 37.5 37.5 33.5 34.5 34.5 34.5 34.5 3 34.7 35.7 35.7 35.7 31.7 32.7 32.7 32.7 32.7 4 33.5 34.5 34.5 34.5 30.5 31.5 31.5 31.5 31.5 5 32.5 33.5 33.5 33.5 29.5 30.5 30.5 30.5 30.
ADCP-75-192 • Issue D • October 2005 • Section 4: BTS Integration 3.1.2 HDC Setup This section outlines the procedure for balancing the Hub forward output. 1. Using the transceptTenantOAMTable.transceptTenantChannelXVal fields of the Tenant OAM MIB, enable the first (X=1) BTS RF channel (disable all other channels by entering zero into Tenant O&M MIB) 2. Record RMS power reported by the FSC in the transceptTenantFscPowerTable. transceptTenantFsc1OutputPower field of the Tenant OAM MIB. 3.
ADCP-75-192 • Issue D • October 2005 • Section 4: BTS Integration 5. Using the transceptTenantGenTwoTable.transceptTenantRucYAttenOffset field in the Tenant OAM MIB, adjust the RUC attenuator offset until the “per carrier” PA output is as shown in the Standard Digivance CXD-4XD-G1 Configuration Table shown above. (+/- 1.0 dB) 6. Repeat steps 2-5 for all RANs for this Tenant Sector. 7. Using the transceptTenantOAMTable.transceptTenantChannelXVal fields of the Tenant OAM MIB, enable all RF channels. 8.
ADCP-75-192 • Issue D • October 2005 • Section 4: BTS Integration In order to balance the reverse path the following procedure is followed: 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 3.
ADCP-75-192 • Issue D • October 2005 • Section 5: BTS Optimization SECTION 5: BTS OPTIMIZATION Content Page 1 NEIGHBOR LIST UPDATES ............................................................. 5-1 2 BTS PARAMETER CHANGES ............................................................ 5-1 2.1 1 TDMA ..................................................................... 5-1 2.2 CDMA ..................................................................... 5-2 2.3 iDEN ....................................
ADCP-75-192 • Issue D • October 2005 • Section 5: BTS Optimization Table 5-1.
ADCP-75-192 • Issue D • October 2005 • Section 5: BTS Optimization The receive propagation delay compensates for the reverse link delay from the receive antenna of the nearest RAN to the channel card of the cell. This parameter determines the ‘zero time’ for the sector from which all other reverse link delays are calculated. The maximum differential transmit delay compensates for the delay differential from the nearest RAN to the furthest RAN within the sector.
ADCP-75-192 • Issue D • October 2005 • Section 5: BTS Optimization 2.3.2 Receiver Multicoupler Setup In the simplex configuration shown in Figure 5-2, the ETBS transmit feen is attenuated by a 30dB pad. The reverse paths are not attenuated and can provide as much as 40dB of gain. As shown in figure 5-2, each simplex receive path (primary and diversity) is connected to two external 6-way power dividers respectively.
ADCP-75-192 • Issue D • October 2005 • Section 6: Software Updates SECTION 6: SOFTWARE UPDATES Content 1 1 Page SOFTWARE RELEASE DELIVERABLE ....................................................... 6-1 2 RELEASE NOTES .................................................................... 6-1 3 UPGRADING EXISTING SYSTEM.......................................................... 6-1 3.1 Preliminary Steps ............................................................. 6-2 3.2 Upgrade Steps ...............
ADCP-75-192 • Issue D • October 2005 • Section 6: Software Updates 3.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. • It is assumed that a network administrator will be performing the upgrade.
ADCP-75-192 • Issue D • October 2005 • Section 6: Software Updates 3.3 Verification It is important to be sure that the upgrade was successful before continuing on with upgrading other CPUs in the network. Some of this verification is done automatically by the upgrade executable, but there are certain steps that need to be done manually as well.
ADCP-75-192 • Issue D • October 2005 • Section 6: Software Updates When evaluating the process list, it is important to be sure that the process IDs of each of the listed processes above stay stable to ensure that processes are not continually restarting. Run the command ps ax | grep /usr/bin/ multiple times over the course of a minute or two to be sure that this is the case. In addition to the above processes, it must be verified that the SNMP agent software is running.
ADCP-75-192 • Issue D • October 2005 • Section 6: Software Updates The HCP’s (FSC, HUC, RDC, and RUC) will automatically evaluate the hardware module revision and determine if the FPGA image in the FPGA Prom is outdated. If this is the case, the HCP will generate a “mismatched Revision” fault. This indicates to the operator that the FPGA’s must be updated by following the manual restart process outlined below.
ADCP-75-192 • Issue D • October 2005 • Section 6: Software Updates 3.6.2 Restore: Again, note that a restore only needs to be performed if problems with the upgrade have been encountered and the CPU is going to be downgraded. Telnet to the target CPU, using operator/operate as the username/password. Run the restore script: sudo backup-hubmaster -r operator@:/var .tar Reboot by entering: sudo reboot Note that the restore script is simply the backup script invoked with a "-r" switch.
ADCP-75-192 • Issue D • October 2005 • Section 6: Software Updates • 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 IP and DHCP interference on the network.
ADCP-75-192 • Issue D • October 2005 • Section 6: Software Updates Blank Page 6-8 2005, ADC Telecommunications, Inc.
ADCP-75-192 • Issue D • October 2005 • Section 7: Autonomous Software Functionality SECTION 7: AUTONOMOUS SOFTWARE FUNCTIONALITY Content 1 INTRODUCTION .................................................................... 7-1 2 FORWARD GAIN MANAGEMENT.......................................................... 7-1 3 REVERSE GAIN MANAGEMENT .......................................................... 7-2 4 FORWARD DELAY MANAGEMENT ........................................................
ADCP-75-192 • Issue D • October 2005 • Section 7: Autonomous Software Functionality 3 REVERSE GAIN MANAGEMENT The Digivance CXD system autolimits any strong in-band signal which reaches the RAN at a peak input level of -40 dBm relative to the antenna port. The process does this by continuously monitoring digital input at the FPGA adding attenuation at the RDC if the threshold is reached. This “AGC event” is logged on the CPU running the RDC process.
ADCP-75-192 • Issue D • October 2005 • Section 7: Autonomous Software Functionality Set the delay value in the Hub SIF’s to make them equal to the base delay plus some delay skew based on the RAN ID. The amount of delay skew is based on the Reverse Delay Skew configured in the Tenant OAM MIB (See Tenant Configuration section of this document) and the RAN ID using the following: Total Delay = Base delay + (delay skew X(RAN ID -1)).
ADCP-75-192 • Issue D • October 2005 • Section 7: Autonomous Software Functionality • If the channel faults are confined to channels 1-4, then either the HDC #1 or the FSC module is declared to be at fault. • If channel faults are confined to channels 5-8, then either the HDC #2 or the FSC module is declared to be at fault. 6.2 RAN As the forward RF detectors in the RAN are geared for accuracy at high-power outputs, they are not suited for the power levels required for FGC non-destructive tests.
ADCP-75-192 • Issue D • October 2005 • Section 7: Autonomous Software Functionality • Integrated power for 24.6 to 39.6 MHz (dBm) using lowest 33% of the bins (Noise Power) • Integrated power for 24.6 to 39.6 MHz (dBm) using lowest 100% of the bins (Signal Plus Noise Power) The RCM software will generate faults if the integrated power levels are below the specified thresholds. 7.2 RDC Tone The RDC Tone will be enabled at all times, unless explicitly disabled via the RDC MIB.
ADCP-75-192 • Issue D • October 2005 • Section 7: Autonomous Software Functionality 9 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, HOP will decrease the FSC output gain until the power level is below the allowable threshold.
ADCP-75-192 • Issue D • October 2005 • Section 8: MIB Structure SECTION 8: MIB STRUCTURE Content 1 Page 1 MIB RELATIONSHIPS ................................................................. 8-1 2 HARDWARE RELATIONSHIPS ........................................................... 8-2 2.1 Hub/RAN Connection Relationships: ................................................ 8-3 2.2 Tennant Relationships ..........................................................
ADCP-75-192 • Issue D • October 2005 • Section 8: MIB Structure MIB RELATIONSHIPS HUB MASTER HUB NODE MIB HUB CONFIG MIB RAN NODE TENANT OAM MIB FGC MIB RGC MIB BTS CONNECTION MIB RAN NODE MIB NODE PATH MIB HUB NODE BUS SCANNER MIB NETWORK NODE MIB PATHTRACE MIB RGC MIB NODE PATH MIB NETWORK NODE MIB PATHTRACE MIB HRM MIB BUS SCANNER MIB GPS MIB STF MIB PSI MIB HDC MIB BIM MIB HUC MIB FSC MIB RSC MIB SIF MIB WD MIB SIF MIB RDC MIB FGC MIB EQUIPMENT MIB HUB RF CONN MIB EQUIPMENT
ADCP-75-192 • Issue D • October 2005 • Section 8: MIB Structure Each Hub/RAN node contains a Bus Scanner process whose responsibility is to discover the presence/absence of hardware modules and to start/stop HCP’s to manage those hardware modules. The Bus Scanner MIB reports the information defining the hardware “discovered” at that node. Each node contains a Network Node process to manage information about that CPU, where the interface is the Network Node MIB.
ADCP-75-192 • Issue D • October 2005 • Section 8: MIB Structure In addition, the Tenant process uses the Tenant OAM MIB to report any status information about the tenant, such as hardware faults and RAN location information, which is gathered from the Equipment MIB’s at the Hub/RAN nodes. Tenant processing determines the location of its related nodes and hardware using a process called the Tenant Scan process that polls the Equipment MIB’s located at each node in the network.
ADCP-75-192 • Issue D • October 2005 • Section 9: General Information SECTION 9: GENERAL INFORMATION Content 1 Page 1 WARRANTY/SOFTWARE ............................................................... 9-1 2 SOFTWARE SERVICE AGREEMENT ........................................................ 9-1 3 REPAIR/EXCHANGE POLICY ............................................................ 9-1 4 REPAIR CHARGES ...................................................................
ADCP-75-192 • Issue D • October 2005 • Section 9: General Information 4 REPAIR CHARGES If the defect and the necessary repairs are covered by the warranty, and the applicable warranty period has not expired, the Buyer’s only payment obligation is to pay the shipping cost to return the defective Product. ADC will repair or replace the Product at no charge and pay the return shipping charges.
ADCP-75-192 • Issue D • October 2005 • Section 9: General Information 7 CUSTOMER INFORMATION AND ASSISTANCE PHONE: EUROPE Sales Administration: +32-2-712-65 00 Technical Assistance: +32-2-712-65 42 EUROPEAN TOLL FREE NUMBERS Germany: 0180 2232923 UK: 0800 960236 Spain: 900 983291 France: 0800 914032 Italy: 0800 782374 U.S.A.
ADCP-75-192 • Issue D • October 2005 • Section 9: General Information Blank Page 9-4 2005, ADC Telecommunications, Inc.
www.adc.
