ADC Digivance CXD Скачать руководство пользователя

Страница: 4 / 74

ADCP-75-192 • Issue 2 • June 2007 • Preface

Page 2

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.4

Setting RAN Measured Forward Gain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3.4.5

Setting FSC Gain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3.4.6

Setting RAN Forward Gain Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3.4.7

Setting Reverse Gain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3.4.8

Setting Reverse Cable Loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

3.4.9

Using Tenant Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

3.4.10 Enabling FGC/RGC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

3.4.11 Using Tenant Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

3.4.12 Enabling/Disabling Delay Compensation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

3.4.13 Forward/Reverse Target Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.4.14 Enabling/Disabling RAN Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.4.15 FSC Atttenuator Offsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.4.16 Target Simulcast Degree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.4.17 Module Attenuators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.5

Managing the Tenant OAM Address and Hostname Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.5.1

RAN Ordering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.5.2

Bracketing of Lost RANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

3.5.3

Clearing of RANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

3.6

Hub Node Access/Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

3.6.1

Managing Hub Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

3.6.2

Identification Using the Network IP Receiver/Sender (NIP R/S) . . . . . . . . . . . . . . . . . . . . . . . . . . 34

3.6.3

Accessing Nodes Locally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

3.6.4

Accessing Nodes via TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

3.6.5

Using a Third Party Network Management System with Digivance CXD/NXD . . . . . . . . . . . . . . . . . 35

3.7

Configuring the Hubmaster Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

3.7.1

Using the Configure-Hubmaster Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

3.7.2

Using Dynamic Host Configuration Protocol With Digivance CXD/NXD . . . . . . . . . . . . . . . . . . . . . 38

3.8

Configuring the “Slave” and RAN Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

3.8.1

Managing the Hub Node MIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

3.8.2

Managing the RAN Node MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3.9

BTS Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.9.1

BTS Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.9.2

Path Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.9.3

Reverse Path Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

3.9.4

Functional RAN Call Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

OTHER SYSTEM TASKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

4.1

Updating System Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

4.1.1

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Содержание Digivance CXD

Страница 1: ...ADCP 75 192 Issue 2 June 2007 1404422 Rev A Digivance CXD NXD Multi Band Distributed Antenna System With FIC Operation Manual ...

Страница 2: ...pecial consequential or other similar damages This disclaimer of liability applies to all products publications and services during and after the warranty period This publication may be verified at any time by contacting ADC s Technical Assistance Center at 1 800 366 3891 extension 73475 in U S A or Canada or 952 917 3475 outside U S A and Canada or by e mail to connectivity_tac adc com ISSUE DATE...

Страница 3: ...GURATION DETAILS 14 2 1 Node and Equipment Identification 14 2 1 1 Identification Using the Network IP Receiver Sender System 14 2 1 2 Node Identification Schemes 14 2 1 3 Hub Equipment Identifications 14 2 2 MIB Relationships 15 2 2 1 MIB Software Relationships 16 2 2 2 MIB Hub RAN Connection Relationships 17 2 3 Tenant Relationships 18 2 4 Pathtrace Format 19 2 4 1 Pathtrace Creation 19 2 4 2 Pa...

Страница 4: ...the Tenant OAM Address and Hostname Tables 32 3 5 1 RAN Ordering 32 3 5 2 Bracketing of Lost RANs 33 3 5 3 Clearing of RANs 33 3 6 Hub Node Access Management 33 3 6 1 Managing Hub Nodes 33 3 6 2 Identification Using the Network IP Receiver Sender NIP R S 34 3 6 3 Accessing Nodes Locally 35 3 6 4 Accessing Nodes via TCP IP 35 3 6 5 Using a Third Party Network Management System with Digivance CXD NX...

Страница 5: ...e 52 4 3 Backup Restore 52 4 3 1 Backup 53 4 3 2 Restore 53 4 4 Adding Removing SNMP Traps 53 4 5 Updating Spare CPUs 54 4 6 MIB Extraction 55 4 7 Gain Management and Fault Detection 56 4 7 1 Forward Gain Management 56 4 7 2 Reverse Automatic Gain Control 56 4 7 3 Forward Delay Management 56 4 7 4 Reverse Delay Management 56 4 7 5 Forward Continuity 57 4 7 6 Reverse Continuity 57 4 7 7 PA Overpowe...

Страница 6: ...ADCP 75 192 Issue 2 June 2007 Preface Page 4 2007 ADC Telecommunications Inc TABLE OF CONTENTS Content Page ...

Страница 7: ... outside U S A and Canada All ADC technical publications are available for downloading from the ADC web site at www adc com Digivance CXD NXD Hub Installation and Maintenance Manual 75 193 Provides instructions for installing and operating the CXD NXD system Hub Digivance CXD NXD SNMP Agent and Fault Isolation User Guide 75 195 Describes how to troubleshoot the system using the objects accessed th...

Страница 8: ...ving an electrical shock when installing or using electrically powered equipment To prevent electrical shock never install or use electrical equipment in a wet location or during a lightning storm Danger This equipment uses a Class 1 Laser according to FDA CDRH rules Laser radiation can seriously damage the retina of the eye Do not look into the ends of any optical fiber Do not look directly into ...

Страница 9: ...n manual may cause harmful interference to radio communications Changes and modifications not expressly approved by the manufacturer or registrant of this equipment can void your authority to operate this equipment under Federal Communications Commissions rules In order to maintain compliance with FCC regulations shielded cables must be used with this equipment Operation with non approved equipmen...

Страница 10: ...rmediate Frequency Div Diversity EMS Element Management System ESD Electrostatic Discharge F Fahrenheit FBHDC Full Band Hub Down Converter FDA U S Food and Drug Administration FCC U S Federal Communications Commission FIC Fiber Interface Controller FSC Forward Simulcast Card GPS Global Positioning System Div Diversity HUC Hub Up Converter IF Intermediate Frequency IN Inch IP Internet Protocol KG K...

Страница 11: ...wn Converter RDC2 RAN Down Converter Version 2 RF Radio Frequency RSC Reverse Simulcast Card RUC RAN Up Converter RUC2 X RAN Up Converter Version 2 X RUC3 RAN Up Converter Version 3 SFP Small Form Factor Pluggable Optical Transceiver SIF Sonet Interface Module SNMP Simple Network Management Protocol SONET Synchronous Optical Network STF2 System Interface Module UL Underwriters Laboratories VAC Vol...

Страница 12: ...ADCP 75 192 Issue 2 June 2007 Preface Page 10 2007 ADC Telecommunications Inc ...

Страница 13: ...ected via optical fibers to Radio Access Nodes RANs distributed over the geographical area of interest Each RAN provides one RF antenna The Digivance system allows the RF signals to be transported to remote locations to expand coverage into areas not receiving service or to extend coverage into difficult to reach areas such as canyons tunnels or underground roadways 1 2 Basic Components Figure 1 s...

Страница 14: ...pment as required for the more limited functions required at the RAN The CXD RAN and the NXD RAN have different sets of electronic modules but the basic function is the same 1 3 Data Flow Forward and Reverse Paths Digivance CXD NXD is a multi frequency multi protocol Distributed Antenna System DAS providing microcellular SMR Cellular and PCS coverage via its distributed RF antennas Figure 2 shows ...

Страница 15: ...everse path the antenna receives RF signals from a mobile and sends those signals through a multicoupler to the RAN Down Converter RDC which down converts the RF back to IF and digitizes the signals The DIF signals are passed to the FIC which sends digital optical signals from the RAN to the HUB FIC The Hub FIC combines that DIF signals with DIF signals from other RANs that are in that simulcast c...

Страница 16: ...k is similar to that of a computer local area network LAN Network control information is passed using a portion of the bandwidth of the optical fibers connecting the Hub and RAN In addition to the Hubmaster CPU the Digivance system may contain other CPUs referred to as slave CPUs under control of the Hubmaster If the system is large enough to require more than one Digital Chassis in the Hub each D...

Страница 17: ...nctions conform to SNMP specifications EMS is described in the next topic Figure 5 shows the MIBs used in the Digivance system and indicates which node type each MIB is used in and how the MIBs are related to one other Within the Digivance network there are four node types Hub Node RAN Node Location Services Equipment LSE node and Hubmaster Node Node is simply shorthand for network node Figure 5 D...

Страница 18: ...nt System EMS The Digivance Element Management System is a Web based system that provides the various control and monitoring functions required for local management of each CXD NXD system The user interface into the EMS is a PC type laptop computer loaded with a standard Web browser Figure 6 is a diagram showing the relationship of EMS to the Digivance MIBs described in the previous topic Figure 6...

Страница 19: ...ses imposed by the various connectors and splices The system provides an optical budget of 9 dB typical when used with 9 125 single mode fiber or 26 dB with extended optics The optical wavelengths used in the system are 1310 nm for the forward path and 1310 nm for the reverse path Different wavelengths may be used for the forward and reverse paths allowing for a pair of bi directional wavelength d...

Страница 20: ... F Humidity 10 to 90 Non condensing IP interface RJ 45 DC power connector Screw type terminal Power Input 48 VDC Floating Input current 34 A 42 VDC Per rack assembly Reliability MTBF 80 000 Excluding fan assemblies Digital Chassis Dimensions HxWxD 19 0 x 7 0 x 7 9 in body 17 1 x 7 0 x 7 9 in mount 43 4 x 17 8 x 20 1 cm 48 3 x 17 8 x 20 1 cm Color Brushed aluminum Backplane connections RJ 45 Power ...

Страница 21: ...J 45 RF connections 50 ohm SMA type female 50 ohm input output impedance RS 232 connection DB 9 Power Input 48 VDC Floating Power Consumption 17 Watts Typical Optical Hub SFP Fiber type 9 125 single mode Number of fibers required Without WDM With WDM With CWDM 2 1 1 per 4 RANS Requires CWDM optical transceivers and wavelength division multiplexers WDM which are accessory items Optical transceiver ...

Страница 22: ...erature 40º to 85º C 40 to 185º F Humidity 10 to 90 IP interface RJ 45 AC power ingress inch box spacer Threaded fitting Fiber optical cable ingress inch service entrance cable fit ting Power input 100 to 240 VAC 47 to 63 Hz Battery backup options Internal RFA Slot Assembly External 1 hour 2 hour Takes one RFA slot Requires Extended Cabinet Battery Weight Internal RFA Slot Assembly External 61 lbs...

Страница 23: ...ons HxWxD 36 5 x 31 0 x 24 0 inches 92 7 x 78 7 x 60 1 cm Weight with extended batteries 4 300 lbs 136 4 kg 625 lbs 284 1 kg RAN without batteries Total RAN 4 batteries Color Putty white Bands per box Up to 4 Boxes per RAN site Up to 2 RANs RF connections RAN cabinet has 5 Type N plugs Cable type CommScope PN 540ANM or equivalent Environmental and Thermal Box thermal management External air Variab...

Страница 24: ...or ring Ran ring limited to 3 SIFs Fiber data link protocol OC 48 Wavelengths per fiber with WDM option with CWDM option 1 1310 nm 2 1310 1550 8 1470 1610 Without WDM CWDM option 20 nm increments ITU GRID Optical transceiver type SFP Dual LC connector Optical Tx power 3 dBm Max 10 dBm Min Finistar FTRJ 1320 1 or equivalent Optical Rx sensitivity 22 dBm Typical 18 dBm Max Optical link margin 2 dB E...

Страница 25: ...analog gain and digital gain change will be timed correctly 15 dB noise figure at 14 dB gain Gain in series with BTS 10 to 10 dB Lower limit for simulcast with a host tower site the max reduces effect of cascaded noise figure Gain parallel to BTS 0 to 30 dB Allows injection after BTS amplifiers Gain stability 2dB Over temperature frequency and aging valid for input signals below AGC threshold Syst...

Страница 26: ...ally keeps track of which nodes are under its control using a script called NIPR Network IP Receiver The Hubmaster Node receives an IP and hostname from every node it controls via NIPS Network IP Sender which runs on all slave nodes NIPR senses any changes to its list of slave nodes and updates the Hubmaster DNS accordingly The NIPR S system is also a key component to maintaining the Hub RAN Node ...

Страница 27: ...signations Each base station sector is cabled to a separate attenuator and BIM unit in the Hub rack 2 2 MIB Relationships As explained in Section 1 4 2 on Page 4 the Digivance CXD NXD system uses Management 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 ...

Страница 28: ... to the Network Node MIB at each node It is also responsible for preparing the Hubmaster to have tenant relationships established The Hub RAN Config Process uses the information set in the Hub Node MIB and BTS Connection MIB to configure the tenant relationships Information that is provided in the BTS Connection MIB as part of tenant setup will be pushed down to the Hub RF Connection MIB in the Hu...

Страница 29: ...rocess to manage information about that CPU or FIC where the interface is the Network Node MIB The Network Node MIB contains information about the CPU or FIC itself for example IP Address Hostname and so on Hub RAN specific information for example Pole ID RAN Box ID and so on and other miscellaneous status information In addition the Network Node MIB reports a high level fault status for each HCP ...

Страница 30: ...ment process on each Hub RAN node will process all Equipment MIB requests and will report all tenant equipment status in the Equipment MIB In the Hub RAN nodes the Node Paths process is responsible for detecting tenant equipment using the results of the Pathtrace MIB and reporting this information in the Node Path MIB In effect the information of the Node Path MIB is just a reorganization of the P...

Страница 31: ... 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 2 4 1 Pathtrace Creation Pathtrace is automatically created ...

Страница 32: ...eates up to two new pathtrace strings primary diversity if present starting with the Tenant ID that was provided in its MIB by the Pathtrace Process The RDC HCP appends its own CPU IP Address to the pathtrace strings and then appends the primary diversity flags 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...

Страница 33: ...s 2 4 6 Pathtrace Detection Reporting On each node in the system a Pathtrace Process is responsible for gathering up all the pathtrace strings reported in the HCP MIBs on its own CPU The Pathtrace Process then reports all the discovered pathtrace strings in its own Pathtrace MIB which indicates the HCP type I2C PCI address MIB index and pathtrace string value On each node in the system a Node Path...

Страница 34: ... the BIM forward output ports are connected to FBHDC modules in its related HUB RF chassis not used if BTS is directly cabled to FBHDC 2 Ensure that RF cables from the BIM reverse input ports are connected to HUC modules primary to primary and diversity to diversity if diversity is used Ensure that any HUC and FBHDC modules connected to a given BIM must reside in the same Hub RF chassis 3 Ensure t...

Страница 35: ... contain tables with 96 separate objects where each object in the table belongs to a given tenant base station sector The index value used for each base station sector is constant across the entire system such that once a tenant sector is configured and an index is established the same index will be associated with that tenant sector in all tenant based MIBs 3 3 2 BTS Connection MIB Within the Hub...

Страница 36: ...ionTable transceptBtsConnectionTenantName 3 3 2 2 Setting the BTS ID The BTS ID identifies the BTS being used by the WSP for this particular tenant Since WSPs may have more than one base station BTS in the system it is important to uniquely identify each one The allowable value is a string of 1 8 characters The MIB field is transceptBtsConnectionTable transceptBtsConnectionBTSID 3 3 2 3 Setting th...

Страница 37: ...h these ID strings down to the Network Node MIB of the CPU that controls this BIM This will allow the NMS to identify the location of the BIM when it is reporting a fault condition The MIB fields are transceptBtsConnectionTable transceptBtsConnectionBimRackID and transceptBtsConnectionTable transceptBtsConnectionBimShelfID 3 3 2 6 Designating the Tenant Hardware The BTS Connection MIB contains sev...

Страница 38: ...sceptBtsConnectionFscI2cSlot When using receive diversity the BIM module belonging to this tenant must have two RF connections to a single HUC module One for primary reverse signals and the other for diversity reverse signals Without receive diversity only the Primary HUC output need be cabled to the BIM The location of the HUC module for this tenant must be co located with the FBHDC and FSC modul...

Страница 39: ...ite mode entry to disabled and follow instructions on setting channels in Section 7 Tenant Configuration The MIB field is transceptBtsConnectionForwardGainTable transceptBtsConnectionForwardGainCompositeMo deFlag 3 3 2 9 Power Attenuator IDs The BTS Connection MIB contains two fields that allow the external power attenuators to be identified The attenuators reside in a shelf at the top of each rac...

Страница 40: ...ed by the Digivance CXD NXD system currently No Protocol 0 CDMA 1 TDMA 2 GSM 3 IDEN 4 AMPS 5 CW_WB 6 CW_NB 7 In Composite Mode protocol need not be selected and defaults to No Protocol 0 3 4 2 Setting Channels transceptTenantOAMTable transceptTenantChannelXVal where X 1 8 Each Tenant sector in the Digivance CXD NXD system can support from 1 8 RF paths Each of these RF paths can be individually ena...

Страница 41: ...m counts active FSC channels and governs FSC gain accordingly To begin using a desired override value set FscOutputGainOverride to enabled 3 4 6 Setting RAN Forward Gain Offset transceptTenantOAMTable transceptTenantRanForwardGainOffsetX where X 1 8 The RAN Forward Gain Offset is a object in the Tenant OAM MIB that allows the target RAN Gains for this tenant to be adjusted This effectively allows ...

Страница 42: ... CXD NXD software 3 4 10 Enabling FGC RGC transceptTenantOAMTable transceptTenantForwardAGCDisable and transceptTenantOAMTable transceptTenantReverseAGCDisable The Forward and Reverse Gain Continuity Management processes can be disabled on a per tenant basis using the enable disable objects in the Tenant MIB These MIB fields are enumerated types with values Enabled 0 and Disabled 1 The reason for ...

Страница 43: ...le transceptTenantRanDisableX where X 1 8 The RAN paths belonging to a tenant can be disabled using the RAN Enable Disable objects of the Tenant OAM MIB Doing so will disable the PA in the RAN 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 For...

Страница 44: ...Balancing Section 4 Subsection 2 It is also important to note that the attenuator offset values configured in the Tenant OAM MIB will supercede and therefore overwrite those configured in the HCP MIBs The following is the list of all supported tenant attenuators in the Tenant OAM MIB TransceptTenantGenTwoTable transceptTenantRucYAttenOffset Y RAN 1 8 TransceptTenantGenTwoTable transceptTenantRdcYA...

Страница 45: ...mmunicate with one of its RANs then that RAN ID in the Hostname table is bracketed For example hostname would be reported as hostname In addition the RAN ID in the Address table is also reported in a different fashion when a RAN is lost The IP address is bracketed with the IP address string being replaced by another form of the number For example 172 20 1 248 could be replaced by 1921681 248 The p...

Страница 46: ...ty of NIPR S which runs on all slave nodes NIPR S senses any changes to its list of slave nodes and updates the Hubmaster DNS accordingly The NIPR S script is also a key component to maintaining the HUB RAN Node MIBs and ultimately tenant processing as a whole since it is the mechanism by which the HUB RAN Node MIB entries are filled There are two main ways to access the output of NIPR S for use i...

Страница 47: ...ork The operator account has access to the Digivance CXD NXD binaries and is used for regular maintenance The root account has full access privileges to the entire file system In addition the operator account has soda privileges which may be modified by the network operator to tailor operator access To learn more about soda log onto any Linux operating system and type man soda at the prompt Note t...

Страница 48: ...ver usr sbin dhcpd3 Domain Name Server usr sbin named Node IP Receiver Sender usr sbin niprs server side properties discussed in Section 9 2 Digivance CXD NXD Tenant processing usr bin tenantscan and usr bin tenant 3 7 1 Using the Configure Hubmaster Script Use the following procedure to invoke the configure hubmaster script 1 Login locally to the target node as operator 2 Type sudo usr sbin confi...

Страница 49: ...lave nodes try to talk to the wrong Hubmaster The default value is Digivance CXD NXD which is suggested to be changed to something more descriptive in the target network At a minimum numbering the domains serially will achieve the desired result i e Digivance CXD NXD Digivance CXD NXD 4XD G22 etc 3 7 1 5 DNS Forwarding The script will prompt Enter a list of upstream DNS servers one per line contro...

Страница 50: ...porating Existing LAN DHCP Using a pre existing LAN DHCP server is ideal when the Digivance CXD NXD network only contains one Hubmaster node In this configuration there is no need for a router between the Hubmaster and the rest of the LAN since all nodes are on the same subnet To use this configuration the Hubmaster DHCP must be disabled using the following steps 1 Login to Hubmaster node 2 Type s...

Страница 51: ...TER DNS The Digivance CXD NXD DNS is automatically updated via NIPR S so there is no need to manually configure it As this process does not interfere with existing upstream DNS activities it need not be disabled 3 7 2 5 Incorporating Existing LAN DNS The method of incorporating an existing LAN DNS begins with configuring the Hubmaster DNS forwarding as outlined in Section 10 1 5 and continues with...

Страница 52: ...assisID Any chassis in a rack needs to be uniquely identifiable by using the CPU Chassis ID field The convention is to number the chassis based on the highest U number they occupy in the rack The CPU Chassis ID can be comprised of up to 15 characters 3 8 1 4 Hostname transceptHubNodeTable transceptHubNodeHostname This entry shows the hostname of the CPU occupying a specific index of the Hub Node M...

Страница 53: ...Hubmaster Only transceptHubNodeGpsCoordTable transceptHubNodeGpsLongitude and transceptHubNodeGpsCoordTable transceptHubNodeGpsLatitude 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 Hubmaster node in the Digivance CXD NXD system contai...

Страница 54: ... physical location GPS can also be used where available The pole number may be 15 characters long 3 8 2 4 Site ID transceptRanNodeTable transceptRanNodeSiteID This entry displays the RF Network s Site ID where each RAN is installed In conjunction with the Pole Number this is the mechanism used to pinpoint any RAN s physical location GPS can also be used where available The Site ID may be 64 charac...

Страница 55: ...in the RAN Node MIB will be set to true This will alert the NMS to clear that node entry in the RAN Node MIB 3 8 2 8 Clean transceptRanNodeExtTable transceptRanNodeExtClean This entry resides in the expansion MIB table of the RAN Node MIB The RAN Node MIB keeps a history of every RAN ever seen by the Hubmaster node At times these entries will become invalid as CPUs are swapped out etc To remove ol...

Страница 56: ...ting degrees as follows xxx yyyyyy where the leading minus sign is optional 3 9 BTS Integration 3 9 1 BTS Validation Prior to connecting the base station to the Digivance CXD NXD HUB the host BTS should be tested to assure the BTS is operating per the manufacturer s specification 3 9 2 Path Balancing This section defines the procedure for balancing the forward and reverse paths for a given Tenant ...

Страница 57: ...RanYOutputPower fields of the Tenant OAM MIB examine the PA output power for each RAN in the simulcast 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 Table 8 Forward Setting BAND COMPOSITE INPU...

Страница 58: ...power to account for variations in RF chain BIM Attn Offset MIB value used to adjust for lower input levels Table 9 shows the recommended power levels and gains for the various CXD NXD bands when interfaced to the 20 dB Attenuator and the BIM Subtract 1 dB when using CDMA signals Table 9 Recommended Forward Balance BAND COMPOSITE INPUT LEVEL PA OUTPUT POWER RAN OUTPUT POWER FORWARD GAIN SMR A 44 d...

Страница 59: ... 4 Using the transceptTenantGenTwoTable transceptTenantRucYAttenOffset field in the Tenant OAM MIB adjust the RUC attenuator to perform final adjustments with all carriers present 3 9 3 Reverse Path Balancing The reverse gain indicates how much gain the Digivance CXD will give to a reverse path signal before presenting it to the base station e g a 100 dBm signal at the RAN input will be 90 at the ...

Страница 60: ...executable named so as to reflect the revision of the contained software for example hr 3 4 0 upgrade would be used to upgrade a target Hub or RAN CPU to a new software version 3 4 0 When invoked the upgrade executable will automatically take the appropriate actions to upgrade the target CPU 4 1 1 Release Notes The release notes delivered with each software release distribution contain specific de...

Страница 61: ...CPU and follow instructions found in the section in this document labeled Verification The upgrade executable should be FTP d to all target machines prior to upgrading any machine This is more efficient than updating one machine at a time The RAN CPUs should be upgraded first as upgrading the HUB CPUs may interrupt telnet sessions to the RAN thereby stopping the RAN upgrades 4 2 2 Upgrade Steps Th...

Страница 62: ... upgraded and include HDC BIM FSC HUC MUC RUC RDC SIF and RSC There should be one instance of each HCP per module managed by the target CPU When evaluating the process list it is important to be sure that the process ID s 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 m...

Страница 63: ...vious revision will work exactly as the 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 It is important that upon completion of a downgrade the ve...

Страница 64: ...ount the backup partition using the command mount mnt part3 If part2 mount the partition using the command mount mnt part2 b Overwrite the software on the backup partition using the untarred files with the command cp r mnt part c Unmount the backup partition using the command umount mnt part 8 Remove the upgrade files using the commands cd tmp rm rf upgrade upgrade tar 4 3 Backup Restore There are...

Страница 65: ... 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 1 Telnet to the target hubmaster CPU using operator operate as the username password 2 Run the restore script sudo backup hubmaster r operator target IP var backupname tar 3 Reboot by entering sudo reboot 4 4 Adding Removing SNMP Traps SNMP traps ...

Страница 66: ...e to Generation 1 Hubs since Generation 2 Hub chassis only contain one CPU Unplug a CPU that resides in the existing fielded system and replace it temporarily with the spare CPU When finished upgrading the spare CPU return the original CPU to that slot in the chassis Dedicate a chassis to be used strictly for this type of update and for verification and test This is the recommended option for CPUs...

Страница 67: ... MIB extraction is needed to update the NMS after a software update Once the software upgrade is complete FTP to one of the updated CPUs logging in as username operator and password operate Change to the MIB directory by entering cd usr share mibs transept Extract get all of the MIB text files located there by entering mget TRANSCEPT txt answering yes to each prompt Extracting the MIBs in this fas...

Страница 68: ... Automatic Gain Control The Digivance CXD NXD system autolimits any strong in band signal which reaches the RAN at a peak input level of greater than 38 dBm relative to the antenna port The process does this by monitoring A D overflows and adding attenuation in the RDC when these overflow occur AGC events are logged on the CPU running the RDC process Attenuation is backed out as the signal strengt...

Страница 69: ...yzed The in band noise power N and total signal power S N will be measured and analyzed in the SIF using an FFT analysis as follows The RCM software will generate faults if the integrated power levels are below the specified thresholds 4 7 6 2 RAN Down Converter RDC Tone Test The RDC Tone will be enabled at all times unless explicitly disabled via the RDC MIB Its frequency corresponds to the first...

Страница 70: ...n POP is a software function that prevents damage to the PA as well as preventing the PA from exceeding FCC spurious output limits POP measures the PA Output Power once per second from the RUC PA MIB If the PA Output Power exceeds a determined threshold then POP will deactivate the FGC process for the tenant sector in question add attenuation to the RUC and set a fault in the FGC MIB Once the PA O...

Страница 71: ...ow 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 If HOP is required to take autonomous action on any of the FSC output a HOP Status field in the 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 tr...

Страница 72: ...This publication may be verified at any time by contacting ADC s Technical Assistance Center ADC Telecommunications S PORE PTE LTD 100 Beach Road 18 01 Shaw Towers Singapore 189702 ADC Telecommunications INC PO Box 1101 Minneapolis MN 55440 1101 USA ADC European Customer Service INC Belgicastraat 2 1930 Zaventem Belguim connectivity tac adc com wireless tac adc com euro tac adc com asiapacific tac...

Страница 73: ......

Страница 74: ...i www adc com ...

Результаты поиска

Содержание Digivance CXD

Отзывы:

Похожие инструкции для Digivance CXD

Бренды по названию

Популярные бренды

ADC Digivance CXD, Руководство по эксплуатации

Результаты поиска

Содержание Digivance CXD

Отзывы:

Похожие инструкции для Digivance CXD

Бренды по названию

Популярные бренды