4RF N2500AAAA0200A Fixed point to point digital radio terminal User Manual Manual

4RF Limited Fixed point to point digital radio terminal Manual

Contents

Manual

Aprisa XE User Manual Version 7.3.1 September 2006
Copyright Copyright © 2001-2005 4RF Communications Ltd. All rights reserved. This document is protected by copyright belonging to 4RF Communications Ltd and may not be reproduced or republished in whole or part in any form without the prior written permission of 4RF Communications Ltd. Trademarks The 4RF, Aprisa, Aprisa XE, SuperVisor and Surveyor names and logotypes are trademarks or registered trademarks of 4RF Communications Ltd. Windows is a registered trademark of Microsoft Corporation in the United States and other countries. Java and all Java-related trademarks are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. All other marks are the property of their respective owners. GoAhead WebServer. Copyright © 2000 GoAhead Software, Inc. All Rights Reserved. Disclaimer Although every precaution has been taken preparing this information, 4RF Communications Ltd assumes no liability for errors and omissions, or any damages resulting from use of this information. This document or the equipment may change, without notice, in the interests of improving the product. RoHS and WEEE compliance The Aprisa XE is fully compliant with the European Commission’s RoHS (Restriction of Certain Hazardous Substances in Electrical and Electronic Equipment) and WEEE (Waste Electrical and Electronic Equipment) environmental directives. Restriction of hazardous substances (RoHS) The RoHS Directive prohibits the sale in the European Union of electronic equipment containing these hazardous substances: lead*, cadmium, mercury, hexavalent chromium, polybrominated biphenyls (PBBs), and polybrominated diphenyl ethers (PBDEs). 4RF Communications has worked with its component suppliers to ensure compliance with the RoHS Directive which came into effect on the 1st July 2006. *The European Commission Technical Adaptation Committee (TAC) has exempted lead in solder for high-reliability applications for which viable lead-free alternatives have not yet been identified. The exemption covers communications network infrastructure equipment, which includes 4RF Communications’ Aprisa XE microwave radios. End-of-life recycling programme (WEEE) The WEEE Directive concerns the recovery, reuse, and recycling of electronic and electrical equipment. Under the Directive, used equipment must be marked, collected separately, and disposed of properly. 4RF Communications has instigated a programme to manage the reuse, recycling, and recovery of waste in an environmentally safe manner using processes that comply with the WEEE Directive (EU Waste Electrical and Electronic Equipment 2002/96/EC). 4RF Communications invites questions from customers and partners on its environmental programmes and compliance with the European Commission’s Directives (sales@4RF.com).
Compliance ETSI The terminal is designed to comply with the European Telecommunications Standards Institute (ETSI) specifications as follows: Radio performance EN 302 217 Parts 1, 2.1, and 2.2 EMC EN 301 489 Parts 1 & 4 Environmental EN 300 019, Class 3.2 Safety EN 60950 A terminal operating in the following frequency bands / channel sizes has been tested and is compliant to the ETSI radio specifications and suitably displays the CE logo. Other bands are compliant to the same radio performance specifications as adapted by 4RF and therefore may be used in regions where compliance requirements demand CE performance at other frequencies. Frequency band Channel size Power input Notified body 300 MHz 400 MHz 25 kHz, 50 kHz, 75 kHz, 150 kHz, 250 kHz, 500 kHz, 1.0 MHz, 1.75 MHz, 3.50 MHz 12 VDC, 24 VDC, 48 VDC, 115/230 VAC Notified Body 0678 600 MHz 700 MHz 800 MHz 900 MHz 500 kHz 12 VDC, 24 VDC, 48 VDC, 115/230 VAC Notified Body 0678 1400 MHz 75 kHz, 150 kHz, 250 kHz, 500 kHz, 1.0 MHz, 1.75 MHz, 3.50 MHz 12 VDC, 24 VDC, 48 VDC, 115/230 VAC 2000 MHz 2500 MHz 250 kHz, 500 kHz, 1.0 MHz, 1.75 MHz, 3.50 MHz, 7 MHz, 14 MHz 12 VDC, 24 VDC, 48 VDC, 115/230 VAC Compliance FCC The terminal is designed to comply with the Federal Communications Commission (FCC) specifications as follows: Radio performance / EMC (dependant on variant) 47CFR part 90 Private Land Mobile Radio Services 47CFR part 101 Fixed Microwave Services 47CFR part 15 Radio Frequency Devices Safety EN 60950 Available in 1Q 2007 Frequency band Channel size Power input FCC ID 400 MHz 25 kHz 48 VDC 900 MHz 100 kHz 48 VDC 900 MHz 200 kHz 48 VDC Verified part 101
Informal declaration of conformity Dansk Undertegnede 4RF Communications Ltd erklærer herved, at følgende udstyr Aprisa™ Radio overholder de væsentlige krav og øvrige relevante krav i direktiv 1999/5/EF. Deutsch Hiermit erklärt 4RF Communications Ltd, dass sich dieses Aprisa™ Radio in Übereinstimmung mit den grundlegenden Anforderungen und den anderen relevanten Vorschriften der Richtlinie 1999/5/EG befindet. (BMWi) Dutch Hierbij verklaart 4RF Communications Ltd dat het toestel Aprisa™ Radio in overeenstemming is met de essentiële eisen en de andere relevante bepalingen van richtlijn 1999/5/EG. English Hereby, 4RF Communications Ltd, declares that this Aprisa™ Radio equipment is in compliance with the essential requirements and other relevant provisions of Directive 1999/5/EC. Español Por medio de la presente 4RF Communications Ltd declara que el Aprisa™ Radio cumple con los requisitos esenciales y cualesquiera otras disposiciones aplicables o exigibles de la Directiva 1999/5/CE. Σλληνας    4RF Communications Ltd   Aprisa™ Radio             1995/5/. Français Par la présente 4RF Communications Ltd déclare que l'appareil Aprisa Radio est conformé aux exigences essentielles et aux autres dispositions pertinentes de la directive 1999/5/CE. Italiano Con la presente 4RF Communications Ltd dichiara che questo Aprisa™ Radio è conforme ai requisiti essenziali ed alle altre disposizioni pertinenti stabilite dalla direttiva 1999/5/CE. Português 4RF Communications Ltd declara que este Aprisa™ Radio está conforme com os requisitos essenciais e outras provisões da Directiva 1999/5/CE. Suomalainen 4RF Communications Ltd vakuuttaa täten että Aprisa™ Radio tyyppinen laite on direktiivin 1999/5/EY oleellisten vaatimusten ja sitä koskevien direktiivin muiden ehtojen mukainen. Svensk Härmed intygar 4RF Communications Ltd att denna Aprisa™ Radio står I överensstämmelse med de väsentliga egenskapskrav och övriga relevanta bestämmelser som framgår av direktiv 1999/5/EG. A formal Declaration of Conformity document is shipped with each Aprisa XE terminal.
Contents | v Contents 1. Getting started ................................................................................................11 2. Introduction.....................................................................................................15 About this manual..........................................................................................................15 What it covers ......................................................................................................15 Who should read it ...............................................................................................15 Contact us............................................................................................................15 What's in the box...........................................................................................................15 Aprisa CD contents ..............................................................................................16 Accessory kit ........................................................................................................17 3. Preparation......................................................................................................19 Path planning ................................................................................................................19 Antenna selection and siting ................................................................................19 Coaxial feeder cables...........................................................................................22 Link budget...........................................................................................................22 Site requirements ..........................................................................................................23 Power supply........................................................................................................23 Equipment cooling................................................................................................23 Earthing and lightning protection..........................................................................24 4. About the terminal ..........................................................................................25 Introduction....................................................................................................................25 Modules.........................................................................................................................26 Front panel connections and indicators.........................................................................27 Interface card types.......................................................................................................28 5. Mounting and installing the terminal ............................................................29 Required tools ...............................................................................................................29 Installing the terminal ....................................................................................................29 Installing the antenna and feeder cable ........................................................................30 External alarms .............................................................................................................31 Alarm circuit setup................................................................................................31 Interface cabling ............................................................................................................32 Power supplies ..............................................................................................................32 DC power supply..................................................................................................32 AC power supply ..................................................................................................35 Safety earth..........................................................................................................36 Bench setup ..................................................................................................................37 6. Connecting to the terminal.............................................................................39 Connecting to the terminal's setup port.........................................................................39 Connecting to the terminal's ethernet interface.............................................................42 PC requirements for SuperVisor ..........................................................................43 PC settings for SuperVisor...................................................................................44 IP addressing of terminals.............................................................................................47 Network IP addressing ..................................................................................................48 Same subnet as local PC.....................................................................................48 Different subnet as local PC.................................................................................49
Contents | vi 7. Managing the terminal....................................................................................51 The setup menu ............................................................................................................51 4RF SuperVisor.............................................................................................................53 Logging in.............................................................................................................54 Logging out ..........................................................................................................54 SuperVisor opening page..............................................................................................55 Changing the terminal’s IP address ..............................................................................56 Setting up users ............................................................................................................57 User groups..........................................................................................................57 Adding a user .......................................................................................................57 Disabling a user ...................................................................................................58 Deleting a user.....................................................................................................58 Saving user information .......................................................................................58 Changing passwords............................................................................................59 Viewing user session details................................................................................59 8. Configuring the terminal ................................................................................61 Configuring the RF settings...........................................................................................61 Modem Performance Settings..............................................................................63 Entering terminal information ........................................................................................64 Configuring the IP settings ............................................................................................65 Saving the terminal's configuration................................................................................66 SNMP (Simple Network Management Protocol) ...........................................................67 SNMP access controls .........................................................................................68 SNMP trap destinations .......................................................................................69 Viewing the SNMP traps ......................................................................................70 Viewing the SNMP MIB details ............................................................................70 Setting the terminal clock sources.................................................................................71 Configuring the RSSI alarm threshold...........................................................................73 Configuring the external alarms ....................................................................................74 Configuring the external alarm inputs ..................................................................74 Configuring the external alarm outputs ................................................................76 9. Configuring the traffic interfaces ..................................................................77 Viewing a summary of the interfaces ............................................................................77 Configuring the traffic interfaces....................................................................................79 Ethernet.........................................................................................................................80 VLAN tagging .......................................................................................................80 Quality of Service .................................................................................................82 Viewing the status of the ethernet ports...............................................................86 Resetting the Ethernet settings............................................................................86 QJET port settings.........................................................................................................87 Q4EM port settings........................................................................................................89 DFXO / DFXS loop interface circuits .............................................................................91 DFXS port settings ...............................................................................................94 DFXO port settings.............................................................................................101 QV24 port settings.......................................................................................................108 HSS port settings ........................................................................................................109 HSS handshaking and clocking...................................................................................111 HSS handshaking and control line function .......................................................111 HSS synchronous clock selection modes ..........................................................114 10. Cross Connections .......................................................................................121 Embedded cross connect switch.................................................................................121 Link Capacity Utilization.....................................................................................121 The Cross Connections application.............................................................................121 The Cross Connections system requirements ...................................................121 Installing the Cross Connections application .....................................................122
Contents | vii Opening the Cross Connections application ......................................................122 The Cross Connections page.............................................................................123 Setting the terminal's address............................................................................125 Management and user ethernet capacity...........................................................125 Setting card types ..............................................................................................126 Getting cross connection configuration from the terminals ................................126 Creating cross connections................................................................................127 Sending cross connection configuration to the terminals...................................130 Saving cross connection configurations.............................................................130 Using existing cross connection configurations .................................................130 Printing the cross connection configuration .......................................................131 Deleting cross connections ................................................................................132 Configuring the traffic cross connections ....................................................................133 Compatible interfaces ........................................................................................133 QJET cross connections ....................................................................................134 Selecting and mapping bits and timeslots..........................................................139 Q4EM cross connections ...................................................................................143 DFXS & DFXO cross connections .....................................................................144 QV24 cross connections ....................................................................................145 HSS cross connections ......................................................................................146 Cross connection example ..........................................................................................147 Symmetrical Connection Wizard .................................................................................148 Starting the wizard .............................................................................................148 Wizard Navigation ..............................................................................................148 Setting the IP address........................................................................................149 Setting the bandwidth.........................................................................................149 Card Selection....................................................................................................150 Interface configurations......................................................................................151 Symmetrical connection summary .....................................................................152 Send symmetrical connection configuration.......................................................152 11. Protected terminals ......................................................................................153 Monitored Hot Stand By (MHSB) ................................................................................153 Tributary switch front panel ................................................................................154 RF switch front panel .........................................................................................155 MHSB cabling ....................................................................................................157 MHSB power supply...........................................................................................157 Configuring the radios for protected mode.........................................................158 12. In-service commissioning............................................................................163 Before you start ...........................................................................................................163 What you will need .............................................................................................163 Applying power to the terminals ..................................................................................164 Review the link configurations using SuperVisor.........................................................164 Antenna alignment ......................................................................................................165 Checking the antenna polarization.....................................................................165 Visually aligning antennas..................................................................................166 Accurately aligning the antennas .......................................................................167 Synchronizing the terminals ...............................................................................169 Checking performance .......................................................................................169 Checking the receive input level ........................................................................169 Checking the fade margin ..................................................................................170 Checking long-term BER....................................................................................171 Bit Error Rate tests.............................................................................................171 Additional tests...................................................................................................172 Checking the link performance...........................................................................173 Viewing a summary of the link performance ......................................................174
Contents | viii 13. Maintenance ..................................................................................................175 Routine maintenance ..................................................................................................175 Terminal upgrades ......................................................................................................176 Upgrade process................................................................................................176 Installing RF synthesizer configuration files.......................................................176 Upgrading the terminal using TFTP ...................................................................177 Upgrading the terminal by uploading system files..............................................182 Viewing the image table .....................................................................................187 Changing the status of an image file..................................................................188 Rebooting the terminal ................................................................................................189 Support summary ........................................................................................................190 Installing interface cards..............................................................................................191 Preparing the terminal for new interface cards ..................................................192 Installing an interface card .................................................................................194 Configuring a slot ...............................................................................................196 14. Troubleshooting............................................................................................197 Loopbacks ...................................................................................................................197 RF radio loopback..............................................................................................197 Interface loopbacks............................................................................................198 Timeslot loopbacks ............................................................................................198 Alarms .........................................................................................................................199 Diagnosing alarms .............................................................................................199 Viewing the alarm history ...................................................................................201 Viewing interface alarms ....................................................................................202 Clearing alarms ..................................................................................................203 Identifying causes of alarms...............................................................................204 E1 / T1 alarm conditions ....................................................................................206 System log...................................................................................................................207 Checking the syslog...........................................................................................207 Setting up for remote logging .............................................................................209 15. Interface connections...................................................................................211 RJ-45 connector pin assignments ...............................................................................211 Interface traffic direction ..............................................................................................211 QJET Interface connections ........................................................................................212 Ethernet interface connections....................................................................................213 Q4EM Interface connections .......................................................................................214 E&M Signalling types .........................................................................................215 DFXS Interface connections........................................................................................217 DFXO Interface connections .......................................................................................218 HSS Interface connections..........................................................................................219 Synchronous cable assemblies..........................................................................220 Cable WAN connectors......................................................................................227 QV24 Interface connections ........................................................................................228 16. Alarm types and sources .............................................................................229 Alarm types .................................................................................................................229 Transmitter alarms .............................................................................................229 Receiver alarms .................................................................................................230 MUX alarms .......................................................................................................230 Modem alarms ...................................................................................................230 Motherboard alarms ...........................................................................................231 QJET alarms ......................................................................................................231 DFXO alarms .....................................................................................................232 DFXS alarms......................................................................................................232 HSS alarms ........................................................................................................232 QV24 alarms ......................................................................................................232
Contents | ix External alarm inputs .........................................................................................233 Remote terminal alarms .....................................................................................233 Cross connect alarms ........................................................................................233 MHSB alarms .....................................................................................................233 17. Country specific settings .............................................................................235 18. Specifications................................................................................................237 RF specifications .........................................................................................................237 System performance specifications.............................................................................238 Interface specifications................................................................................................244 Ethernet interface...............................................................................................244 QJET Quad E1 / T1 interface.............................................................................244 Q4EM Quad 4 wire E&M interface .....................................................................245 DFXO Dual foreign exchange office interface....................................................246 DFXS Dual foreign exchange subscriber interface ............................................248 QV24 Quad V.24 asynchronous data interface..................................................250 HSS Single high speed synchronous data interface ..........................................250 External alarm interfaces ...................................................................................251 Auxiliary interfaces .............................................................................................251 Power specifications....................................................................................................252 AC Power supply................................................................................................252 DC Power supply ...............................................................................................252 Power consumption............................................................................................252 MHSB specifications ...................................................................................................253 MHSB protection ................................................................................................253 General specifications .................................................................................................253 Environmental ....................................................................................................253 Mechanical.........................................................................................................253 ETSI performance ..............................................................................................253 19. Product end of life ........................................................................................255 End-of-life recycling programme (WEEE)....................................................................255 The WEEE symbol explained.............................................................................255 WEEE must be collected separately ..................................................................255 Return and collection programmes in your area ................................................255 Your role in the recovery of WEEE ....................................................................255 EEE waste impacts the environment and health................................................255 20. Abbreviations ................................................................................................257 21. Acknowledgments and licensing ................................................................259 22. Commissioning Forms .................................................................................265 23. Index ..............................................................................................................267
Getting started | 11 1. Getting started This section is an overview of the steps required to commission a link in the field. Phase 1: Pre-installation 1. Confirm path planning. Page 19 2. Ensure that the site preparation is complete:  Power requirements  Tower requirements  Environmental considerations, for example, temperature control  Rack space Page 22 3. Confirm the interface card configuration. Phase 2: Installing the terminals 1. Before installing the terminal into the rack, check that all the required interface cards are fitted. Position and mount the terminal in the rack. Page 29 2. Connect earthing to the terminal. Page 24 3. Confirm that the:  Antenna is mounted and visually aligned.  Feeder cable is connected to the antenna.  Feeder connections are tightened to recommended level.  Tower earthing is complete. 4. Install lightning protection. Page 24 5. Connect the coaxial jumper cable between the lightning protection and the terminal duplexer. 6. Connect the power supply to the terminal and apply power. Page 31
Getting started | 12 Phase 3: Establishing the link 1. If you don't know the terminal's IP address : Connect the setup cable between the terminal's Setup port and the PC using accessory kit adaptor. Use HyperTerminal to confirm the IP settings for the terminal:  Local IP address  Local subnet mask  Remote terminal IP address Reboot the terminal Page 52 2. Connect the Ethernet cable between the terminal's 4-port Ethernet switch and the PC. 3. Confirm that the PC IP settings are correct for the 4-port Ethernet switch:  IP address  subnet mask Page 44 4. Confirm that Java is installed on the PC. Page 43 5. Start the web browser, and log into the terminal. Page 54 6. Set or confirm the RF characteristics:  TX and RX frequencies  Modulation type  TX output power Page 61 7. Compare the actual RSSI to the expected RSSI value (from your path planning). 8. Fine-align the antennas. Page 167 9. Confirm that the terminal clock sources are set correctly. Page 63 10. Confirm that the TX and RX LEDs are green. Disregard the OK LED status for now.
Getting started | 13 Phase 4: Configuring the traffic 1. Confirm that the interface hardware and software slot configurations match. 2. Confirm the interface card settings. Page 79 3. Open the Cross Connections application and configure the cross connections:  Download the configuration.  Confirm or modify the traffic cross connections.  Save the configuration to the terminal.  Activate the configuration. Page 122 4. Save the configuration to disk and close the Cross Connections application. Page 130 5. Connect the connection of interface cables. 6. Confirm or adjust the terminal clocking for network synchronization, if required. 7. Test that the traffic is passing over the link as configured. 8. Confirm or configure the external alarm settings in SuperVisor. Page 74 9. Setup an external alarm connection cable, if required. 10. Reset any alarms and error counters. Page 199 11. Perform traffic pre-commissioning tests (optional) 12. Complete the commissioning form (at the back of the manual) and file. Page 265
Introduction | 15 2. Introduction About this manual What it covers This user manual describes how to install and configure Aprisa XE™ fixed point-to-point digital radio links. It specifically documents an Aprisa XE terminal running system software version 7.3.1. It is recommended that you read the relevant sections of this manual before installing or operating the terminal. Who should read it This manual has been written for professional field technicians and engineers who have an appropriate level of education and experience. Contact us If you experience any difficulty installing or using Aprisa XE after reading this manual, please contact Customer Support or your local 4RF representative. Our area representative contact details are available from our website: 4RF Communications Ltd 26 Glover Street, Ngauranga PO Box 13-506 Wellington 6032 New Zealand E-mail support@4rf.com Web site www.4rf.com Telephone +64 4 499 6000 Facsimile +64 4 473 4447 Attention Customer Services What's in the box Inside the box you will find:  Aprisa XE terminal  Accessory kit  Aprisa CD  Aprisa XE Quick Start Guide  Commissioning Form  Configuration sheet
Introduction | 16 Aprisa CD contents The Aprisa CD contains the following: Software  The latest version of the terminal software (see "Terminal upgrades” on page 176)  The Cross Connections application - required if you want to use the Cross Connections application offline (see "Installing Cross Connections application" on page 122).  Java VM - Java plug-in needed to run the Supervisor software.  Web browsers - Mozilla Firefox and Internet Explorer are included for your convenience.  Adobe™ Acrobat® Reader® which you need to view the PDF files on the Aprisa CD. Documentation  User manual — an electronic (PDF) version for you to view online or print.  Product collateral — application overviews, product description, case studies, and white papers. Tools  Surveyor - a path propagation calculator developed by 4RF (see "Path planning" on page 19).
Introduction | 17 Accessory kit The accessory kit contains the following items: Setup cable (RJ-45) and adaptor Mounting brackets and screws Hardware kit (includes Allen key for fascia screws) Alarm cable (RJ-45)
Introduction | 18 Ground cable DC power cable (for use with the -48 VDC and -24 VDC power supplies) AC power cable (for use with the 110 / 230 VAC power supply)
Preparation | 19 3. Preparation Path planning Proper path planning is essential. When considering the components of your radio system, think about:  antenna selection and siting  coaxial cable selection  link budget You can also use Surveyor to help you with path feasibility planning. Surveyor is a path propagation calculator developed by 4RF to assist path planners quickly and efficiently verify the viability of point-to-point transmission links deploying the Aprisa™ microwave radio systems. The software program calculates the anticipated link performance for the transmission system elements you have selected. However, it is not a substitute for in-depth path planning. You will find Surveyor a valuable addition to your planning toolbox. A copy of Surveyor is provided on the Aprisa CD supplied with this manual. You can download updates from www.4rf.com. Antenna selection and siting Selecting and siting antennas are important considerations in your system design. There are three main types of directional antenna that are commonly used with the radios parabolic grid, Yagi and corner reflector antennas. The antenna that should be used for a particular situation is determined primarily by the frequency of operation and the gain required to establish a reliable link. Parabolic grid antennas Factor Explanation Frequency Often used in 1350-2700 MHz bands Gain Varies with size (17 dBi to 30 dBi typical) Wind loading Can be significant Tower aperture required Can be significant Size Range from 0.6 m to 3 m diameter Front to back ratio Good Cost High
Preparation | 20 Yagi antennas Factor Explanation Frequency Often used in 330-960 MHz bands Gain Varies with size (typically 11 dBi to 16 dBi) Stackable gain increase 2 Yagi antennas (+ 2.8 dB) 4 Yagi antennas (+ 5.6 dB) Wind loading Less than a parabolic grid antenna Tower aperture required Unstacked: Less than a parabolic grid antenna Stacked: about the same as a parabolic grid antenna Size Range from 0.6 m to 3 m in length Front to back ratio Low Cost Low It is possible to increase the gain of a Yagi antenna installation by placing two or more of them in a stack. The relative position of the antennas is critical. Example of stacked antennas
Preparation | 21 Corner reflector antennas Factor Explanation Frequency Often used in 330-960 MHz bands Gain Typically 10 dBd Wind loading Less than a parabolic grid antenna Tower aperture required About the same as a parabolic grid antenna Size Range from 0.36 m to 0.75 m in length Front to back ratio High (typically 30 dB) Beamwidth Broad (up to 60°) Cost Medium Antenna siting When siting antennas, consider the following points:  A site with a clear line of sight to the remote terminal is needed. Pay particular attention to trees, buildings, and other obstructions close to the antenna site. Example of a clear line-of-sight path  Any large flat areas that reflect RF energy along the link path, for instance, water, could cause multi-path fading. If the link path crosses a feature that is likely to cause RF reflections, shield the antenna from the reflected signals by positioning it on the far side of the roof of the equipment shelter or other structure. Example of a mid-path reflection path  The antenna site should be as far as possible from other potential sources of RF interference such as electrical equipment, power lines and roads.  The antenna site should be as close as possible to the equipment shelter. Note: Wide angle and zoom photographs taken at the proposed antenna location (looking down the proposed path), can be useful when considering the best mounting positions.
Preparation | 22 Coaxial feeder cables To ensure maximum performance, it is recommended that you use good quality low-loss coaxial cable for all feeder runs. For installations requiring long antenna cable runs, use Andrew Heliax™ or equivalent. When using large diameter feeders, use a short flexible jumper cable between the feeder and the terminal to reduce stress on the antenna port connector. All coaxial cable has loss, that is, the RF energy traveling through it is attenuated. Generally speaking, the larger the diameter of the cable, the less the loss. When selecting a coaxial cable consider the following: Factor Effect Attenuation Short cables and larger diameter cables have less attenuation Cost Smaller diameter cables are cheaper Ease of installation Easier with smaller diameter cables or short cables When running cables:  Run coaxial cable from the installation to the antenna, ensuring you leave enough extra cable at each end to allow drip loops to be formed.  For 19-inch rack mount installations, cables may be run from the front of the rack directly onto the antenna port. They may also be run through the back of the rack to the front.  Terminate and earth or ground the cables in accordance with the manufacturers' instructions. Bond the outer conductor of the coaxial feeder cables to the base of the tower mast. Link budget All of the above factors (and many others not mentioned) combine in any proposed installation to create a link budget. The link budget predicts how well the radio link will perform after it is installed. Use the outputs of the link budget during commissioning testing to confirm the link has been installed correctly, and that it will provide reliable service.
Preparation | 23 Site requirements Power supply Ensure that the correct power supply is available for powering the terminal. The nominal input voltage for a terminal is 12, 24 or 48 volts DC or 115 / 230 volts AC rms. The DC supply voltage is factory preset at time of order and cannot be adjusted in the field. The terminal voltage is indicated on the chassis label by the DC input connector and on the specification label fitted to the terminal. Warning: Before connecting power, ground the chassis using the safety earth terminal on the front panel. Equipment cooling Mount the terminal so that air can flow through it. Do not obstruct the free flow of air around the terminal. The two internal, speed-controlled fans fitted into the chassis provide sufficient cooling. The fans are microprocessor-controlled to run at the minimum speed required to keep the terminal below a preset temperature. They are constantly monitored and an alarm is raised under failure conditions. The environmental operating conditions are as follows: Operating temperature -10°C to +50°C Storage temperature -20°C to +70°C Humidity Maximum 95% non-condensing Altitude Up to 5000 metres
Preparation | 24 Earthing and lightning protection Warning: Lightning can easily damage electronic equipment. To avoid this risk, install primary lightning protection devices on any interfaces that are reticulated in the local cable network. You should also install a coaxial surge suppressor on the antenna port of the duplexer Earth the antenna tower, feeders and lightning protection devices in accordance with the appropriate local and national standards. The diagram below shows the minimum requirements. Use grounding kits as specified or supplied by the coaxial cable manufacturer to properly ground or bond the cable outer.
About the terminal | 25 4. About the terminal Introduction The terminals operate in a number of frequency bands from 300 MHz up to 2.7 GHz carrying ethernet, voice and data traffic over distances up to 100 kilometres. They are designed to meet the demands of a wide range of low to medium capacity access and backhaul applications. The digital access terminal is a compact, powerful point-to-point linking solution with up to 64 Mbit/s of radio link capacity, and customer-configurable interface options integrated within the radio platform.
About the terminal | 26 Modules The terminal is modular in design, which helps reduce mean time to repair (MTTR). It is designed for 19-inch rack mounting and is only 2U high for standard configurations. The five main modules housed inside the chassis are the transceiver, modem, motherboard, power supply, and duplexer. Interface cards are fitted into the eight interface slots on the motherboard. Modules are interconnected via several buses on the motherboard. A duplexer can be mounted inside or outside the chassis. The interrelationships between the components are shown below:
About the terminal | 27 Front panel connections and indicators All connections to the terminal are made on the front panel of the terminal. No. Label Description 1 AC or DC power input DC and AC power supplies are available (AC is shown) 2 Safety earth stud An M5 stud for connection to an external protection ground for protection against electric shock in case of a fault. 3 Antenna connector N-type 50 female connector for connection of antenna feeder cable. 4 Interface slots A to H Eight interface slots on the motherboard to fit interface cards. 5 ETHERNET Integrated four-port layer 2 switch. 6 SETUP RJ-45 serial connection to PC for initial configuration. 7 ALARM RJ-45 connector for two external alarm input and four external alarm output connections. 8 LED indicators OK Indicates normal operation and minor and major alarm conditions. RX Indicates status of receive path including normal operation and alarms such as BER, RSSI and loss of synchronization. TX Indicates status of transmit path including normal operation and alarms such as forward / reverse power and temperature. ON Blue LED indicates that there is power to the terminal. 9 RSSI RSSI test point suitable for 2 mm diameter multimeter test lead pin.
About the terminal | 28 Interface card types Each terminal has eight interface slots labeled A to H. Each slot can be fitted with any interface card type. Typically, the terminal is delivered pre-configured with the requested interface cards. The following interface card types are currently available: Name Interface card type Function QJET Quad E1/T1 interface card Four E1 / T1 interfaces (Framed or Unframed). Q4EM Quad 4 wire E&M interface card Four 4 wire E&M voice channels DFXS Dual 2 wire FXS interface card Two 2 wire loop signalling foreign exchange subscriber (POTS) channels DFXO Dual 2 wire FXO interface card Two 2 wire loop signalling foreign exchange office channels HSS High-Speed Synchronous interface card A single high speed serial data channel configured as synchronous V.24, V.35, X.21, V.36 / RS 449, or EIA/TIA 530. QV24 Quad V.24 serial asynchronous interface card Four asynchronous V.24/RS232 data channels.
Mounting and installing the terminal | 29 5. Mounting and installing the terminal This section covers installing the hardware associated with the terminal. Before you begin a terminal installation, read this section thoroughly. Warning: You must comply with the safety precautions in this manual or on the product itself. 4RF does not assume any liability for failure to comply with these precautions. Required tools No special tools are needed to install the terminal other than those required to physically mount the terminal into the rack. Installing the terminal The terminal is designed for 19-inch rack mounting and is supplied with rack mounting brackets. The rack brackets can be front, mid, or rear mounted (as shown below) to suit individual installation requirements. Once the rack brackets are attached, carefully lift the terminal into position in the rack, and fasten with screws and washers.
Mounting and installing the terminal | 30 Installing the antenna and feeder cable Carefully mount the antenna following the antenna manufacturers' instructions. Run feeder cable from the antenna to the terminal mounting location. Lightning protection must be incorporated into the antenna system. For more information, please contact Customer Support. Caution: When the link is operating, there is RF energy radiated from the antenna. Do not stand in front of or touch the antenna while the terminal is operating. 1. Fit the appropriate male or female N-type connector to the antenna feeder at the antenna end. Carefully follow the connector manufacturers' instructions. 2. Securely attach the feeder cable to the mast and cable trays using cable ties or cable hangers. Follow the cable manufacturer's recommendations about the use of feeder clips, and their recommended spacing. 3. Connect the antenna and feeder cable. Ensure the N-type connector is tight. Weatherproof the connection with a boot, tape, or other approved method. 4. Fit the appropriate N-type male connector to the antenna feeder at the terminal end (the terminal is N-type female). Carefully follow the connector manufacturer's instructions. 5. Connect the feeder cable to the antenna port on the terminal. Use a jumper cable, if needed. Ensure the N-type connector is tight. 6. Connect a coaxial surge suppressor or similar lightning protector between the feeder and jumper cables (or at the point where the cable enters the equipment shelter). Earth the case of the lightning protector to the site Lightning Protection Earth. Also earth the terminal M5 earth stud to a protection earth.
Mounting and installing the terminal | 31 External alarms Two external alarm inputs and four external alarm outputs are provided on the RJ-45 ALARM connector on the front panel. These enable an internal alarm to provide an external alarm to the network operator's existing network management system via contact closure or opening, or for an external alarm to be transported via the radio link. The latency for an alarm presented on an external alarm input to the alarm being output on an external alarm output is < 2 seconds. Alarm outputs are isolated semiconductor relay type contacts rated to 0 to 60 VDC or AC rms with a maximum current of 100 mA. Alarm inputs are isolated current detectors with an operating voltage range of 9 to 60 VDC or AC rms (effective current threshold of 5.0 to 6.5 mA constant current). The common reference potential for the two external alarm inputs must be applied to pin 3 and the common reference potential for the four external alarm outputs must be applied to pin 4. Alarm circuit setup A typical alarm circuit setup is:  An external battery applied to the ‘common alarm inputs reference’ and a normally open relay contact connected to the alarm input. Closing the contact applies the source to the alarm input detector which turns the alarm on (setup for ‘alarm on when source on’). See “Configuring the external alarm inputs” on page 74 for the setup options.  An external earth applied to the ‘common alarm outputs reference’ and a ground contact detector connected to the alarm output. When the alarm is on (active), the external alarm output relay contact closes (setup for ‘relay closed when alarm on’). See "5Configuring the external alarm outputs” on page 76 for the setup options. MCommon alarminputs referenceTerminal TerminalAlarm inputCommon alarmoutputs referenceAlarm output The terminal front panel RJ-45 ALARM connections are: RJ-45 pin Connection description TIA-568A wire colour 1 External alarm input 1 green / white 2 External alarm input 2 green 3 Common reference for alarm inputs 1 to 2 orange / white 4 Common reference for alarm outputs 1 to 4 blue 5 External alarm output 1 blue / white 6 External alarm output 2 orange 7 External alarm output 3 brown / white 8 External alarm output 4 brown
Mounting and installing the terminal | 32 Interface cabling All interface cabling connections are made with RJ-45 male connectors which plug into the front of the interface cards (see “Interface connections” on page 211). The cabling to the QJET, DFXO and DFXS interface cards must have a minimum conductor size of 0.4 mm2 (26 AWG). Power supplies US and Canada: Installations should be in accordance with US National Electrical Code ANSI / NFPA 70, and Canadian Electrical Code, Part 1 C22.1. Warning: Do not apply power to the terminal until you have completed installing the interface cards and connecting the antenna. Warning: Before disconnecting the safety earth during maintenance, remove AC or DC power supply connections, antenna cable and all interface cables from the terminal. DC power supply There are three DC power supplies for the terminal 12 VDC, 24 VDC and 48 VDC. As the terminal DC input is isolated above ground, the DC power input can be either positive grounded or negative grounded. Nominal voltage Input voltage range Power consumption Maximum input current Recommended DC breaker rating ±12 VDC 10.5 to 18 VDC 63 - 180 W 18 A 25 A ±24 VDC 20.5 to 30 VDC 63 - 180 W 8 A 10 A ±48 VDC 40 to 60 VDC 63 - 180 W 4 A 5 A Caution: An all-pole switch or DC circuit breaker of the rating shown in the table above must be fitted between the terminal DC input and the DC power source. Each terminal or MHSB terminal should have its own separate fuse or DC circuit breaker.
Mounting and installing the terminal | 33 DC Cabling The DC power input is terminated on the front panel of the terminal with two high-current M3 screw clamps for the positive and negative DC input and a M5 stud for the earth connection. The DC power cables have pre-terminated lugs to fit into the power input M3 screw clamps on one end and bare wire at the other end. The appropriate power cable for the power supply ordered is included in the accessory kit. Ensure that one terminal of the DC power supply is earthed from the power ground. 24 VDC / 48 VDC cable The 24 VDC and 48 VDC power supplies are supplied with a 3 metre red/black cable of 2.0 mm2 (23 strands of 0.32 mm2). Terminal Power input Cable colour +V Positive DC input Red -V Negative DC input Black
Mounting and installing the terminal | 34 12 VDC cable The 12 VDC power supply is supplied with a 3 metre red/black cable of two pairs of 2.3 mm2 (72 strands of 0.2 mm2) making a total of 4.6 mm2 per connection. This increase in wire size is to carry the increased current consumption of the 12 VDC supply (max 18 Amps per terminal). This 3 metre cable is engineered to power a fully loaded terminal from a 12 VDC supply. A longer cable should not be used as the additional voltage drop could cause the power supply to fail. If longer cable runs are required between the 12 VDC power supply and the terminal, it is suggested that high current distribution bus bars are used to feed the rack and the supplied power cable used between the bus bars and the terminals. Terminal Power input Cable colour +V Positive DC input Red -V Negative DC input Black 1. Fit both pairs of lugs into the terminal screw clamps. 2. Twist the other ends together when fitting to the source.
Mounting and installing the terminal | 35 AC power supply There is one AC power supply for the terminal. This AC power supply is auto-sensing to operate with a nominal input voltage of 115 Vrms or 230 Vrms. The power input is terminated on the front panel of the terminal using a standard IEC plug. This power supply has a power on/off switch. A power cable is included in the accessory kit and is pre-fitted with an IEC socket connector and the country-specific plug that was specified when the order was placed. Nominal voltage Input voltage range Power consumption Max VA Frequency 115 VAC 103 - 127 Vrms 63 - 180 W 400 VA 47 - 63 Hz 230 VAC 207 - 254 Vrms 63 - 180 W 400 VA 47 - 63 Hz Terminal Power input Cable colour E Earth Green/yellow N Neutral Blue L Line / Phase Brown Important: Please check with your local power authority about correct colour usage and pinouts. AC power cords used must be in accordance with national requirements. Norway and Sweden: PLUGGABLE CLASS I EQUIPMENT intended for connection to a telephone network or similar communications system requires a label stating that the equipment must be connected to an earthed mains socket outlet.
Mounting and installing the terminal | 36 Safety earth The terminal chassis must have a protection / safety earth connected between the terminal earth stud and a common protection earth in the rack. The DC power input can be either positive grounded or negative grounded depending on the power supply system available. Ground the terminal chassis using the terminal earth stud on the front panel as shown:
Mounting and installing the terminal | 37 Bench setup Before installing the link in the field, it is recommended that you bench-test the link. A suggested setup for basic bench testing is shown below: When setting up the equipment for bench testing, note the following:  Earthing—the terminal should be earthed at all times. The terminal earth stud must be connected to a protection earth.  Attenuators— In a bench setup, there must be 60 - 80 dB at up to 3 GHz of 50 ohm coaxial attenuation (capable of handling the transmit power of +35dBm) between the terminals’ N type antenna connectors. This can be achieved with two fixed attenuators fitted to the antennas 'N' connectors and a variable attenuator with a  60 dB range. You can use other attenuator values as long as you consider the transmit power output level (max +33 dBm) and the receiver signal input (max -20 dBm).  Cables—use double-screened coaxial cable that is suitable for use up to 3 GHz at  1 metre. Caution: Do not apply signals greater than -20 dBm to the antenna connection as they can damage the receiver.
Connecting to the terminal | 39 6. Connecting to the terminal Connecting to the terminal's setup port You can configure basic terminal settings by connecting to the terminal using the Setup cable. This can be useful if you need to confirm the terminal's IP address, for example. You can password-protect the setup menu to prevent unauthorized users from modifying terminal settings. A straight RJ-45 connection cable and a RJ-45 to DB-9 adapter is provided with each terminal. 1. Plug the DB-9 into serial port of the PC. 2. Plug the RJ-45 connection cable into the adaptor as shown below: 3. Plug the other end of the RJ-45 connection cable into the SETUP port of the terminal. Note: Connecting the PC serial port to the Interface Cards or ALARM connectors may result in damage to the PC or terminal. Ensure that the RJ-45 connection cable is connected to the RJ-45 connector marked 'SETUP'. Cable pinouts (RJ-45 to DB-9) If you need a conversion connector or cable, refer to the following table: Console port (DCE, RJ-45) RJ-45 to RJ-45 cable RJ-45 to DB-9 adaptor PC port (DTE, DB-9) Signal RJ-45 pin RJ-45 pin RJ-45 pin DB-9 pin Signal RTS 1 1 1 7 RTS DTR 2 2 2 4 DTR TXD 3 3 3 3 TXD GND 4 4 4 5 GND GND 5 5 5 NC NC RXD 6 6 6 2 RXD DSR 7 7 7 6 DSR CTS 8 8 8 8 CTS
Connecting to the terminal | 40 Configure the PC COM port settings Terminal emulation software e.g. HyperTerminal is used to setup the basic configuration of a terminal. The PC's COM port settings must be setup as follows: Bits per second 115200 Data bits 8 Parity None Stop bits 1 Flow Control None Start a HyperTerminal session 1. On the PC, select Start > Programs > Accessories > Communications > HyperTerminal. 2. Enter a name for the connection and click OK. 3. Select the designated COM Port from the Connect Using drop-down box. Ensure it is the same COM port that you configured earlier on your PC. Click OK. Note: The Country/region, Area code, and Phone number information will appear automatically.
Connecting to the terminal | 41 4. Set the COM Port settings as follows: 5. When you have completed the settings, click OK, which will open the HyperTerminal window. 6. Apply power to the terminal. Note: If power was applied to the terminal before launching HyperTerminal, hit the Enter key to initiate the link. When the terminal has completed startup, you will be presented with the Setup menu:
Connecting to the terminal | 42 Connecting to the terminal's ethernet interface The main access to a terminal for management is with the ethernet interface using standard IP networking. There should be only one ethernet connection from the terminal to the management network. The terminals are pre-configured to use IP addressing in one of the common 'non-routable' IP address ranges. This means the terminals are usually recognized by your operating system without any reconfiguration. However, you should change these default addresses (see “Changing the terminal’s IP address” on page 56) to comply with your IP addressing scheme. In the example below, the active management PC must only have one connection to the link as shown by path c. There should not be any alternate path that the active management PC can use via an alternate router or alternate LAN that would allow the management traffic to be looped as shown by path d.
Connecting to the terminal | 43 PC requirements for SuperVisor SuperVisor requires the following minimum PC requirements:  Microsoft Windows 95/98, 2000, NT or XP  Personal computer with 800 MHz Pentium III  128 MB of RAM (the Java plug-in requires at least 32 MB of physical RAM)  108 MB of free hard disk space  Ethernet interface (Local Area Network)  COM port  Web browser with a Java plug-in such as Mozilla FireFox (recommended), Microsoft Internet Explorer 5.0, or Netscape Navigator 6.0, but SuperVisor also supports other major web browsers.  Java JRE 1.5. Note: Mozilla Firefox, Internet Explorer and the Java JRE are provided on the Aprisa CD (see "5Aprisa CD contents” on page 16)
Connecting to the terminal | 44 PC settings for SuperVisor To change the PC IP address: If your PC has previously been used for other applications, you may need to change the IP address and the subnet mask settings. You will require Administrator rights on your PC to change these. Windows XP example: Configure IP settings 1. Open the 'Control Panel'. 2. Open 'Network Connections' and right click on the 'Local Area Connection' and select 'Properties'. 3. Click on the 'General' tab. 4. Click on 'Internet Protocol (TCP/IP)' and click on properties. 5. Enter the IP address and the subnet mask (example as shown). 6. Click 'OK' then close the Control Panel. If the terminal is on a different subnet from the network the PC is on, set the PC default gateway address to the network gateway address which is the address of the router used to connect the subnets (for details, consult your network administrator).
Connecting to the terminal | 45 To change the PC connection type: If your PC has previously been used with Dial-up connections, you may need to change your PC Internet Connection setting to 'Never dial a connection'. Windows XP example: Configure Windows to Never Dial a Connection 1. Open the 'Control Panel'. 2. Open 'Internet Options' and click on the 'Connections' tab. 3. Click the 'Never dial a connection' option. 4. Click 'OK' then close the Control Panel.
Connecting to the terminal | 46 To change the PC pop-up status: Some functions within SuperVisor require Pop-ups enabled e.g. saving a MIB Windows XP example: Configure explorer to enable Pop-ups 1. Open the 'Control Panel'. 2. Open 'Internet Options' and click on the 'Privacy' tab. 3. Click on 'Settings'. 4. Set the 'Address of Web site to allow' to the terminal address or set the 'Filter Level' to 'Low: Allow Pop-ups from secure sites' and close the window. 5. Click 'OK' then close the Control Panel.
Connecting to the terminal | 47 IP addressing of terminals When logging into a link, it is important to understand the relationship between the Local / Remote and the Near end / Far end terminals. The Near end terminal is the terminal that has its ethernet port physically connected to your IP network. The Far end terminal is the terminal that is at the other end of the link from the Near end terminal and communicates through the management connection over the radio link to the Near end terminal. The Local terminal is the terminal that SuperVisor is logged into and is displayed on the left hand side of the SuperVisor screen. The Local terminal can be the Near end or Far end terminal. The Remote terminal is the terminal that is at the other end of the link from the Local terminal and is displayed on the right hand side of the SuperVisor screen. To prevent confusion when operating SuperVisor, determine the IP address of the Near end terminal and log into that terminal. This is now the Local terminal. The distinction is important as:  Some functions can only be carried out on the Local terminal.  Having different configurations at each end of the link will disrupt communications between the terminals. In these circumstances it is important to make changes to the Far end terminal of the link first. The link is then lost only until the near end configuration is completed and communication restored. If the Near end terminal is modified first, the link is lost for much longer as staff will have to either physically visit the Far end terminal to restore the link, or restore the near end to match the far end, re-establish the link, then start the process again, this time with the Far end terminal first.
Connecting to the terminal | 48 Network IP addressing Same subnet as local PC The following diagram shows a link interconnected on the same subnet as the local PC terminal used for configuration. In this example, the local PC, as well as the local and remote terminals, are on the same subnet and therefore have the same subnet mask 255.255.255.0. This will allow the PC and the terminals to communicate with each other.
Connecting to the terminal | 49 Different subnet as local PC The following diagram shows a link interconnected on a different subnet as the local PC used for configuration, and communicating through a network. This can be achieved on the condition that network router(s) 1 and 2 are programmed to recognize each other and the various subnets on the overall network.
Managing the terminal | 51 7. Managing the terminal The command line setup menu can be used to:  Provide basic access to the terminal to set IP addresses  Check or set basic settings of the terminal 4RF SuperVisor is an embedded element manager for the Aprisa XE terminal which is used to:  Configure radio and interface parameters  Setup cross connections between traffic interfaces  Monitor performance, terminal status and alarm details The setup menu 1. Initiate the link by either applying power to the terminals or, if the terminals are already powered up, pressing the Enter key. 2. At the prompt, enter your selection: Selection Explanation 1) Dump terminal configuration This shows basic terminal data such as ID, IP data, TX and RX frequency. 2) Use DHCP configuration This deletes any preset IP addresses and looks for a new address via DHCP. 3) Configure IP addresses Use this if you want to set the IP address of the local terminal. 4) Configure SNMP Use this to set the SNMP community string. 5) Set hostname Use this to set a name that can be used in conjunction with DNS. 6) Configure remote terminal address Use this to set the IP address of the remote terminal. 7) Reset web server users Restores all the default web usernames and passwords. 8) Reset to defaults Resets all the configurable terminal settings (such as frequencies, power, IP settings SNMP settings) to pre-defined defaults. This means that when the terminal restarts, the link will be lost. 9) Reboot Reboots the terminal. 10) Configure Ethernet Use this to reset the Ethernet configuration to the default settings, and display the Ethernet configuration. 11) Password Protect Menu Use this to password-protect the menu to prevent unauthorized users from modifying terminal settings. The password is setupxe.
Managing the terminal | 52 To get or set the IP address of a terminal using setup To get the IP address of a terminal using setup: 1. At the prompt, type 1 and enter. The following information appears:  the IP addresses of the local and remote terminals  the subnet mask and gateway of the local terminal  the TFTP of the remote terminal To set the IP address of a terminal using setup: 1. At the prompt, enter 1. 2. Enter 3 to configure the local terminal IP address. Set the following for the terminal using the standard format xxx.xxx.xxx.xxx:  1) IP address  2) Subnet mask  3) Gateway address 3. Enter 4 (Quit) to return to the main menu. 4. Enter 6 to configure the remote terminal IP address. Important: You must ensure that the IP addresses of the local and remote terminals are on the same subnet as the PC being used to configure the terminals. 5. Enter 4 (Quit) to return to the main menu. 6. Enter 9 (Are you sure y/n) to reboot the terminal.
Managing the terminal | 53 4RF SuperVisor 4RF SuperVisor management software is pre-loaded into an integrated web-server within the terminal. SuperVisor runs on any Java-enabled web browser. You can use SuperVisor to:  display and configure terminal parameters  view the terminal alarms  monitor the performance and status of the link  upgrade the terminal software  save and load configuration files  save performance and error information to a log file
Managing the terminal | 54 Logging in The maximum number of concurrent users that can be logged into a terminal is 5. If SuperVisor is inactive for a period of 30 minutes, the terminal will automatically log out the user. To log in to SuperVisor: 1. Open your web browser and enter the IP address of the terminal. Note: If you haven't yet assigned IP addresses to the terminals, use the factory-configured IP addresses (see “Changing the terminal’s IP address” on page 56). If you don't know the IP address of the terminal, you can determine it using terminal emulation software (see “To get or set the IP address of a terminal using setup” on page 52). 2. Login with the user name and password assigned to you. Note: If unique user names and passwords have not yet been configured, use the default user names and passwords (see "Setting up users" on page 57). Important: After you login for the very first time, it is recommended that you change the default admin password for security reasons (see "Changing passwords" on page 59). 3. Tick the ‘Use Popup Window’ tick box if you want a separate browser window to launch after you have logged in. The login page remains open in one window allowing you to view or configure settings in another page. This is useful if you have more than one link to configure, for example, protected terminals. 4. When you have logged in, the Summary page shows a summary of both the Local and Remote terminals’ parameters. Logging out As the maximum number of concurrent users that can be logged into a terminal is 5, not logging out correctly can restrict access to the terminal until the after the timeout period (30 minutes). Logging out from a terminal will logout all users logged in with the same user name. If the SuperVisor window is closed without logging out, the terminal will automatically log the user out after a timeout period of 30 minutes. To log out of SuperVisor: 1. Click on the ‘Logout’ button on the Summary Bar.
Managing the terminal | 55 SuperVisor opening page SuperVisor terminal status and menu bar The terminal status and menu bar at the top of the screen shows the name of the terminal and three status indicators for both the local and remote terminals. The indicators reflect the status LED indicators on the front panel of terminal. There are four menus available:  Link - menu options for both terminals in a link  Local - menu options for the local terminal in a link  Remote - menu options for the remote terminal in a link  Help - provides details about the terminal Note: The local terminal is the terminal that you are logged into. SuperVisor summary bar The summary bar at the bottom of the screen shows the login name of the person currently logged in together with the name of the local terminal and its IP address.
Managing the terminal | 56 Changing the terminal’s IP address You can use SuperVisor to change the IP address of the terminal from the default. Alternatively, you can assign the IP address using the SETUP port (see "To get or set the IP address of a terminal using setup” on page 52). To change the IP address of the terminals using SuperVisor: 1. Launch your web browser and connect to the terminal using the one of the factory-configured default IP addresses shown below: Terminal IP address Unprotected terminals Terminal 1 (local) 169.254.50.10 Terminal 2 (remote) 169.254.50.20 Protected terminals Terminal 1, terminal A (local) 169.254.50.10 Terminal 1, terminal B (local) 169.254.50.11 Terminal 2, terminal A (remote) 169.254.50.20 Terminal 2, terminal B (remote) 169.254.50.21 Note: The factory default settings for the subnets is 255.255.0.0; the gateway is 0.0.0.0. 2. Log into the terminal as the administrator with the user name 'admin' and the password 'admin'. Note: For security reasons, change the admin password (see "Changing passwords" on page 59) as soon as possible. 3. Select Link or Local or Remote > Terminal > Advanced and make the necessary changes. Note: If this IP address change is being made over the RF link, it is important to change the far end of the link first. 4. Once you have changed the IP address of a terminal, reconnect to it using the new IP address.
Managing the terminal | 57 Setting up users Note: You must login with 'admin' privileges to add, disable, delete a user or change a password. User groups There are three pre-defined user groups to allocate access rights to users. These user groups have associated default user names and passwords of the same name. User Group Default User Name Default Password Access Rights View view view Users in this group can only view terminal parameters. Modify modify modify Users in this group can view and edit terminal parameters. Admin admin admin Users in this group have full access to all terminal parameters including the ability to add and change users. Adding a user 1. Select Local or Remote > Maintenance > User Admin > User Table. 2. Select an empty line (that isn't allocated to an existing user) and then click Edit. 3. Enter the user name. A user name can be up to 32 characters but cannot contain back slashes, forward slashes, spaces, tabs, single or double quotes. 4. Enter the Password and the Confirm Password. A password can be up to 32 characters but cannot contain back slashes, forward slashes, spaces, tabs, single or double quotes. 5. Select the group that they will belong to (View, Modify, or Admin). 6. If the user requires immediate access, enable the user by clicking on Yes. 7. Click Apply. Note 1: The new user must be setup on both the Local and Remote terminals. Note 2: For the changes to take effect, you must reboot the terminal (Local > Maintenance > Reboot).
Managing the terminal | 58 Disabling a user 1. Select Local or Remote > Maintenance > User Admin > User Table. 2. Select the user who you want to disable. 3. Click Edit to display the User details and set Enabled to 'No'. 4. When you have made your changes, click Apply to apply changes or Reset to restore the previous configuration. Note: For the changes to take effect, you must reboot the terminal (Local > Maintenance > Reboot). Deleting a user 1. Select Local or Remote > Maintenance > User Admin > User Table. 2. Select the user you want to delete. 3. Click Edit to display the user details and delete the User Name and Password. 4. Reset the Group to 'View' and set Enabled to 'no'. 5. When you have made your changes, click Apply to apply changes or Reset to restore the previous configuration. Note: For the changes to take effect, you must reboot the terminal (Local > Maintenance > Reboot). Saving user information You can save the list of users to your PC and then load this file to another terminal. This is useful if you have multiple terminals to configure. To save the user table to file: 1. Select Local > Maintenance > User Admin > Save User List. 2. Select the 'Save to disk' option in the dialog box that appears. 3. In the next dialog box that appears, navigate to the directory where you want to save the file, enter a suitable filename, and then click Save (The default name for this file is 'downloadUsers'). Note: If this dialog box does not appear, change your Internet security settings to allow downloads. You may also need to check your file download location setting. To save the file to another terminal: 1. Select Local > Maintenance > User Admin > Load User List. 2. On the Upload Users page, select Browse and navigate to the file on your PC. 3. Click Apply. The User Table appears and you can edit users, as required.
Managing the terminal | 59 Changing passwords 1. Select Local or Remote > Maintenance > User Admin > User Table. 2. Select the user whose password you want to change and click Edit. 3. Enter the new Password and the new Confirm Password. A password can be up to 32 characters but cannot contain back slashes, forward slashes, spaces, tabs, single or double quotes. 4. When you have made your changes, click Apply. Viewing user session details Administrators can check who is currently logged in, the computer they are logging in from, and how long they have been logged in for. Note: A 'session' is the period of time that begins when someone logs into the terminal and ends when they logout. To view user session details: 1. Select Local > Maintenance > User Admin > Session Details. The 'Session Details' shows a list of the current users:  User Name: the User Name logged into the terminal.  Time: the number of minutes the user has been logged in.  Last Access: the number of minutes the user last accessed the terminal in this session.  Address: the address of the computer or proxy server address logged into the terminal.
Configuring the terminal | 61 8. Configuring the terminal Configuring the RF settings The RF settings are factory-configured before dispatch to the customer requirements. However, you can change the RF settings, if required. Select Link or Local or Remote > Terminal > Basic: Note: Transmit frequency, transmit power, channel size, modulation and antenna polarization would normally be defined by a local regulatory body and licensed to a particular user. Refer to your site license details when setting these fields.
Configuring the terminal | 62 RX and TX Frequency The local terminal transmit frequency must match the receive frequency of the remote terminal and the remote terminal transmit frequency must match the receive frequency of the local terminal. When setting the RX and TX frequency with SuperVisor, the frequency entered is automatically resolved to the synthesizer step size for the terminal frequency band e.g. a 1400 MHz band frequency entry of 1474,010,000 Hz will be changed to 1474,012,500 Hz (see synthesizer step size in the table “RF specifications” on page 237). The RX and TX frequency entered must be:  Within the frequency band limits of the chosen RF frequency band of the terminal as specified in “RF specifications” on page 237 e.g. for a frequency band of 1400 MHz, the frequency band limits are 1350 to 1550 MHz  Within the TX/RX passbands of the duplexer fitted in the terminal e.g. for a frequency band of 1400 MHz, the duplexer passband is 7 MHz and the TX/RX split is > 49 MHz (see Duplexer (bandpass) “RF specifications” on page 237). The duplexer passband and center frequencies are written on the duplexer label. Important: Changing the remote terminal RX or TX frequency will disable all management communication to the remote terminal but by changing the local terminal to match the remote terminal, the radio link will be restored as will the management communication BUT if the remote terminal RX or TX frequency is changed to be outside the operating range of the terminal, changing the local terminal to match the remote terminal will not restore the radio link and management communication The remote terminal TX and RX frequencies cannot be changed simultaneously i.e. change one direction and ‘Apply’ the change and then change the other direction and ‘Apply’ the change. To change both TX and RX frequencies: 1. Change the remote terminal RX frequency and ‘Apply’ the change. The radio link will fail. 1. Change the local terminal TX frequency to that of the remote RX frequency and ‘Apply’ the change. The radio link will restore. 2. Change the remote terminal TX frequency and ‘Apply’ the change. The radio link will fail. 2. Change the local terminal RX frequency to that of the remote TX frequency and ‘Apply’ the change. The radio link will restore. Transmit power The transmitter power is the power measured at the duplexer output port. The transmitter power adjustment range varies depending on the Modulation type and frequency band of the terminal (see “System performance specifications” on page 238). Channel size The RF channel size is a factory-configured setting determined by the Aprisa XE hardware option. Modulation type Both terminals must be set to the same modulation type. When you change the modulation type in an operational terminal, traffic across the link will be interrupted and you may need to change the cross connections capacity, as the Total Capacity of the radio link may be exceeded.
Configuring the terminal | 63 Modem Performance Settings Select Local or Remote > Performance > Summary and Quick Links of Modem Performance Settings. There are two Modem Performance Settings, Modem QPSK Coding and Modem Interleaver Mode. Modem QPSK Coding When the Modulation type is set to QPSK, the default QPSK Coding setting is ‘Non-Gray Coded’ but the QPSK Coding can use ‘Gray Coded’ for interoperability with older hardware. Modem Interleaver Mode The Modem Interleaver improves modem bit error rate but increases the end to end link delay so the Modem Interleaver should be enabled where a low bit error rate is required and disabled where a low end to end link delay is required. The ‘Default’ Modem Interleaver Mode setting is on for channel sizes of 250 kHz and greater and off for channel sizes of 200 kHz and less. The specification of End to End Link Delay for both interleaver on and off is given in “System performance specifications” on page 238. When you change the Modem Interleaver Mode in an operational terminal, traffic across the link will be interrupted Both terminals must be set to the same Modem Interleaver Mode.
Configuring the terminal | 64 Entering terminal information To enter basic terminal information: Select Link or Local or Remote > Terminal > Basic Terminal Information 1. Enter the terminal Name. This appears in the Terminal status and menu bar at the top of every page. 2. Enter a unique Terminal ID. 3. Enter the Location of the terminal. 4. Enter a contact name or an email address in Contact Details. The default value is ‘support@4RF.com’. 5. Click Apply to apply changes or Reset to restore the previous configuration.
Configuring the terminal | 65 Configuring the IP settings 1. Select Link or Local or Remote > Terminal > Advanced. 2. Select either DHCP or Static IP addressing. 3. If you select Static IP, you must also:  Enter the IP Address for the terminal assigned by your site network administrator. Use the standard format xxx.xxx.xxx.xxx. The default IP address is in the range 169.254.50.xx.  Enter the Subnet Mask for the terminal using the standard format xxx.xxx.xxx.xxx. The default subnet mask is 255.255.0.0.  Enter the Default Gateway for the terminal, if required, using the standard format xxx.xxx.xxx.xxx (There is no default gateway set by default.) 4. In Remote Address, enter the IP address of the remote terminal using the standard format xxx.xxx.xxx.xxx (The default IP address is in the range 169.254.50.xx.) 5. If you are setting up for remote logging (see page 209), enter the Syslog Address and the Syslog Port for the remote terminal. 6. In Time Zone Offset from GMT, select the time zone from the list (optional) . 7. To set the Time to the PC real-time clock, click Now. 8. Click Apply to apply changes or Reset to restore the previous configuration.
Configuring the terminal | 66 Saving the terminal's configuration Note: To save cross connection configurations, see page 130. To save a configuration: 1. Ensure you are logged in with either 'modify' or 'admin' privileges. 2. Select Local > Maintenance > Config Files > Save MIB. 3. Select the 'Save to disk' option in the dialog box that appears. 4. In the next dialog box that appears, navigate to the directory where you want to save the file, enter a suitable filename, and then click Save (The default name for this file is backupForm). Note 1: If this dialog box does not appear, change your Internet security settings to allow downloads. You may also need to check your default download location. Note 2: Pop-ups must be enabled on you PC for this function to work (see “PC settings for SuperVisor” on page 44). To load a configuration into a terminal: Important: Only load a saved configuration file to another terminal that has exactly the same configuration (RF variant and interface cards). 1. Ensure you are logged in with either 'modify' or 'admin' privileges. 2. Select Local or Remote > Maintenance > Config Files > Load MIB. 3. Click Browse and then navigate to the file and select it. 4. Click Upload to load the configuration file into the terminal.
Configuring the terminal | 67 SNMP (Simple Network Management Protocol) In addition to web-based management (SuperVisor), the terminal can also be managed using the Simple Network Management Protocol (SNMP). MIB files are supplied, and these can be used by a dedicated SNMP Manager, such as Castle Rock's SNMPc (www.castlerock.com), to access most of the terminal's configurable parameters. However, it is recommended that SNMP is only used for status and alarm monitoring of your entire network. SuperVisor is the best means to configure individual terminals. For communication between the SNMP manager and the terminal, Access Controls, Trap Destinations, and Community strings must be set up as described in the following sections. A SNMP Access Control is the IP address of the terminal used by an SNMP manager or any other SNMP device to access the terminal. Entering an IP address of ‘Any’ (not case sensitive) or * will allow any IP address access to the terminal. A community string is sent with the IP address for security. Commands are sent from the SNMP manager to the terminal to read or configure parameters of the terminal e.g. setting of interface parameters. A SNMP Trap Destination is the IP address of a station running an SNMP manager. A community string is sent with the IP address for security. Events are sent from the terminal to the SNMP manager e.g. alarm events. A SNMP Community String is used to protect against unauthorized access (similar to a password). The SNMP agent (terminal or SNMP manager) will check the community string before performing the task requested in the SNMP message . Trap Destinations and Access Controls both use community strings for protection. To configure Trap Destinations and Access Controls: Select Local > Maintenance > SNMP > SNMP Settings Note: SNMP Settings can only be setup on the local terminal.
Configuring the terminal | 68 SNMP access controls To add an access control: 1. Click on the ‘Add Read Only’ button to enter a Read Only access control or click on the ‘Add Read/Write’ button to enter a Read/Write access control. 2. Enter the IP address of each SNMP manager allowed access to the terminal (read/write access control shown). The IP address entered must be a valid dot delimited IP address. Entering an IP address of ‘Any’ or * will allow any IP address access to the terminal. 3. Enter the community string for the access control. The Community string is usually different for Read Only and Read/Write operations. There is no default 'public' community string for an access control, but a 'public' community string can be entered which will have full MIB access, including the 4RF MIB. 4. Click Add. To delete an access control: 1. Select the access control you want to delete and click Delete. 2. Click OK to delete the access control or Cancel to abort the delete.
Configuring the terminal | 69 SNMP trap destinations To add a trap destination: 1. Click on the ‘Add SNMPv1’ button to enter a SNMPv1 trap destination or click on the ‘Add SNMPv2c’ button to enter a SNMPv2c trap destination. The differences between SNMPv1 and SNMPv2c are concerned with the protocol operations that can be performed. Selection of SNMPv1 and SNMPv2c must match the setup of the SNMP manager. 2. Enter the IP address of the server to which you want SNMP traps sent (SNMPv1 trap destination shown). The IP address entered must be a valid dot delimited IP address. 3. Enter the community string for the trap destination. There is no default 'public' community string for a trap destination, but a 'public' community string can be entered. 4. Click Add. To delete a trap destination: 1. Select the trap destination you want to delete and click Delete. 2. Click OK to delete the trap destination or Cancel to abort the delete.
Configuring the terminal | 70 Viewing the SNMP traps Any event or alarm in the SNMP objects list can be easily viewed. This also enables you to verify, if required, that SNMP traps are being sent. Select Local > Maintenance > SNMP > View Traps. Viewing the SNMP MIB details This is useful to see what MIB (Management Information Base) objects the terminal supports. Select Link or Local or Remote > Maintenance > SNMP > View MIB Details.
Configuring the terminal | 71 Setting the terminal clock sources Select Link or Local or Remote > Terminal > Clocking The current selected clock source and the current states of the primary and secondary network clocks are shown: Clock State Clock State Description Inactive This clock source is either not configured at all, or is not in current use Active This clock source is providing the clocking for the terminal Holdover This clock source is nominated as Primary or Secondary but is currently unavailable, due to a problem with the interface. You can select which traffic interface ports are nominated as Primary or Secondary Clock sources in the configuration for the relevant interface ports (see "Configuring the traffic interfaces" on page 77). The failure of both Network Clock sources results in a major alarm. This situation should be attended to promptly.
Configuring the terminal | 72 To select the terminal clock source: The Clock Source selected for the terminal will be used to clock all interface ports requiring clocking and send a clocking signal over the RF link. Select Link or Local or Remote > Terminal > Clocking > Clock Source and select one of the following: Clock Source Terminal Clocking Network The terminal is clocked from the nominated interface port. Internal The terminal is clocked from the terminal's internal clock. Link The terminal is clocked from the RF link. If the terminal Clock Source is set to Network, the terminal will automatically clock from the nominated primary clock source if that clock source is available. If the nominated primary clock source is not available, the terminal will clock from the nominated secondary clock source if that clock source is available. If the nominated secondary clock source is not available, the terminal will clock from the internal clock source. When a nominated clock source becomes available (primary or secondary), the terminal will then clock from that clock source. The terminal at one end of the link must have its clock source set to Internal or Network and the terminal at the other end of the link must have its clock source set to Link. QJET or HSS To manually force the terminal to change its clock source: Select either Primary Active or Secondary Active from the Network Clock Command drop-down list, and click Apply. Note: The Network Clock Command option is only available if the clock source is set to Network
Configuring the terminal | 73 Configuring the RSSI alarm threshold The threshold (in dB) at which the RSSI alarm activates can be set for each of the modulation types over the adjustment range of -40 dBm to -110 dBm and the default values are as per the following screen shot. The alarm threshold has a +1 dB hysteresis for the inactive state. To configure the RSSI alarm threshold: Select Link or Local or Remote > Alarms > RSSI Thresholds 1. Enter the alarm threshold required for each of the modulation types. 2. Click Apply to apply changes or Reset to restore the previous configuration.
Configuring the terminal | 74 Configuring the external alarms Each terminal has two external alarm inputs and four external alarm outputs, terminated on the ALARM RJ-45 connector on the terminal front panel. Each external alarm input can activate the Major / Minor terminal alarm or be mapped to a remote terminal external alarm output. The ‘Alarm On When’ (active alarm state) for both inputs can be configured for 'External Source On' or 'External Source Off' (default is External Source On). Each external alarm output can be triggered by a local terminal Major / Minor alarm or a remote terminal Major / Minor alarm or either of the remote external alarm inputs. The ‘Relay Closed When’ for the four outputs can be configured for 'Alarm On' or 'Alarm Off' (default is Alarm Off). Configuring the external alarm inputs To configure the External Alarm Inputs: Select Link or Local or Remote > Alarms > Ext Alarm Inputs Note: When the terminal MHSB mode is enabled, the external alarm input 2 is used by the protection switch system so is not available for user alarms. The state of the local terminal external alarm input is always sent to the remote terminal and the external alarm input can be mapped to a remote terminal external alarm output. Alarms present on a local terminal external alarm input will only be displayed in the remote terminal Alarm Table / Alarm History if it has been mapped to one of the remote terminal external alarm outputs.
Configuring the terminal | 75 1. Select the Display Locally setting for each alarm input. Display Locally External Alarm Input Function No The external alarm input does not generate an alarm on the local terminal, does not appear in the ‘Alarm Table’ or ‘Alarm History’, and shows as grayed out on the ‘Alarm Summary’. Default Yes The external alarm input generates an alarm on the local terminal, displays in the ‘Alarm Table’ and ‘Alarm History’ and the ‘Alarm Summary’. 2. Select the Severity setting for each alarm input. This option is only relevant when the ‘Display Locally’ option is set to ‘Yes’. Severity External Alarm Input Severity Minor The external alarm input generates a minor alarm on the local terminal. Default Major The external alarm input generates a major alarm on the local terminal. 3. Enter a Description for each alarm input. The default is ‘External Input 1’ / ‘External Input 2’. 4. Select the Alarm On When setting for the two alarm inputs Alarm On When External Alarm Input State External Source On The alarm is on (alarm active) when a source of voltage is applied to the external alarm input and current is flowing. Default External Source Off The alarm is on (alarm active) when no source of voltage is applied to the external alarm input and hence no current is flowing. 5. When you have made your changes, click Apply to apply changes or Reset to restore the previous configuration.
Configuring the terminal | 76 Configuring the external alarm outputs To configure the External Alarm Outputs: Select Link or Local or Remote > Alarms > Ext Alarm Outputs Note: When the terminal MHSB mode is enabled, the external alarm output 4 is used by the protection switch system so is not available for user alarms. 1. Select the Mapping required for each alarm output. Mapping External Alarm Output Function None No external alarm output. Default Local Major The external alarm is present when the local terminal has a major alarm. Local Minor The external alarm is present when the local terminal has a minor alarm. Remote Major The external alarm is present when the remote terminal has a major alarm. Remote Minor The external alarm is present when the remote terminal has a minor alarm. Remote Input 1 The external alarm is present when the remote terminal external alarm input 1 is present. Remote Input 2 The external alarm is present when the remote terminal external alarm input 2 is present. 2. Select the Relay closed when setting for the four alarm outputs. Relay closed when External Alarm Output State Alarm on When the external alarm output relay contact is closed, the alarm is on (alarm active). Default Alarm off When the external alarm output relay contact is closed, the alarm is off (alarm inactive). 3. When you have made your changes, click Apply to apply changes or Reset to restore the previous configuration.
Configuring the traffic interfaces | 77 9. Configuring the traffic interfaces Important: When configuring a link, it is important that you configure the remote terminal first as the new configuration may break the management connection to the remote terminal. Once the remote terminal has been configured, the local terminal should be configured to match the remote terminal. Viewing a summary of the interfaces To view a summary of the interfaces fitted: Select Link or Local or Remote > Interface > Interface Summary. The Interface Summary page shows:
Configuring the traffic interfaces | 78  The interface type for each slot that has been configured with the capacity used by each port.  Total Capacity. The total capacity of the radio link.  Ethernet Capacity. The capacity allocated to the Ethernet traffic over the radio link. This includes the user and management capacity assigned.  Management Capacity. The capacity allocated to the management conduit over ethernet.  Allocated Capacity. The percentage of the total capacity of the radio link that has been allocated to traffic interfaces.  Drop and insert capacity. The percentage of the total drop and insert capacity used for local drop and insert cross connections. The total drop and insert capacity is 65536 kbit/s minus the assigned radio link capacity. Some interfaces also require extra bandwidth to be allocated to transport signalling, such as CTS / DTR handshaking or E&M signals. The cross connections application automatically allocates capacity for signalling when it is needed.
Configuring the traffic interfaces | 79 Configuring the traffic interfaces Important: Before you can configure the traffic interfaces, the interface cards must be already installed (see "Installing interface cards” on page 191). Configuring each traffic interface involves the following steps (specific instructions for each interface card follow this page). First, specify the port settings for the Remote terminal: 1. Select Remote > Interface > Interface Summary, select the interface card and click Configure Interface. 2. Select the port you want to configure and modify the settings, as necessary. 3. Click Apply to save the changes you have made. Now specify the port settings for the Local terminal: 1. Select Local > Interface > Interface Summary, select the interface card and click Configure Interface. 2. Select the port you want to configure and modify the settings, as necessary. 3. Click Apply to save the changes you have made. Once you have done this, you will need to configure the traffic cross-connects (see "Configuring the traffic cross connections" on page 121) for each interface card.
Configuring the traffic interfaces | 80 Ethernet In the default mode the Ethernet switch passes IP packets (up to 1522 bytes) as it receives them. However, using SuperVisor you can configure VLAN, QoS and port speed settings to improve how IP traffic is managed. This is useful for operators who use virtual networks to segment different groups of users or different types of traffic in their network. These groups can be maintained across the radio link thus ensuring users in one virtual network cannot access data in other virtual networks. The switch also has a high-speed address lookup engine, supporting up to 2048 preferential MAC addresses as well as automatic learning and aging. Traffic is filtered through this table and only traffic destined for the remote end is sent across the link improving bandwidth efficiency. Note: You need "modify" or "admin" privileges to configure the Ethernet for VLAN and Quality of Service (QoS). VLAN tagging By default, all user and management traffic is allocated the same VLAN across the link. Alternatively, you can assign each of the four Ethernet ports to a VLAN. Each VLAN can be configured to carry user traffic, or user traffic and radio management traffic. The VLAN tagging conforms to IEEE 802.1Q standard. Configuring the Ethernet switch for VLAN tagging 1. Select Link or Local or Remote > Interface > Ethernet Settings. Note: Always configure the remote terminal before the local terminal 2. In the Quick Links box at the bottom of the page, click Ethernet General Settings. 3. From Ethernet Grouping drop-down list select 'Enabled' ('Disabled' is the default setting; Ethernet traffic is not segregated). Important: Changing this setting will disrupt Ethernet traffic. 4. Click Apply to apply changes or Reset to restore the previous configuration. You now need to select the VLAN groups for each of the four Ethernet ports.
Configuring the traffic interfaces | 81 Specifying the VLAN ID for the Ethernet ports Each Ethernet port can be configured with one of five VLAN IDs. You can configure each of the physical ports, numbered 1 to 4 with a VLAN ID (numbered User1 to User4 and User+Mgmt). These VLAN IDs are applied at the ingress port and only used internally across the link. The VLAN ID is removed when traffic exits the switch at the egress port. Data entering the Ethernet switch on ports 1 to 4 or the internal management port can only exit on ports that are associated with the same VLAN ID as the ingress port. For example, the physical RJ-45 port 1 may be on VLAN 3 at the local end, but at the remote end, the physical RJ-45 port 4 may be associated with VLAN 3. Traffic entering the local end on port 1 will exit the remote end on port 4. To allow the radio link to transport traffic using existing VLAN ID information, the radio adds an extra VLAN ID over the top of an existing VLAN ID (double-tagging). This extra VLAN ID is added at the ingress port and removed at the egress port. This adds 4 bytes to the packet and the maximum packet size supported by the radio is 1526 bytes. Note 1: Tagged flows can only have one port per VLAN ID on each terminal. Note 2: The ethernet switch only supports packets up to 1522 bytes in size at the ingress port. 1. Select Link or Local or Remote > Interface > Ethernet Settings. Note: Always configure the remote terminal before the local terminal 2. In the Quick Links box at the bottom of the page, select the port you want to configure: 3. The Ethernet Port Settings page appears for the port you selected: 4. From the Ethernet Group drop-down list, select the VLAN group to which you want this port to belong. Important: To access radio management traffic, you need to allocate one of the VLANs to ‘User and Management’. It is strongly recommended that you indicate which port or group of ports is associated to the management traffic first. 5. Click Apply. 6. Repeat steps 1-4 for the Ethernet switch in the other terminal in the link.
Configuring the traffic interfaces | 82 Quality of Service Quality of Service (QoS) enables network operators to classify traffic passing through the Ethernet switch into prioritized flows. Each port can have a priority tag set at the ingress port, or it can be read directly from the Ethernet traffic. When read directly from the Ethernet traffic, the following fields are used to determine the traffic’s QoS priority.  The IEEE 802.1p Priority information in the IEEE 802.3ac Tag.  The IPv4 Type of Service field.  The IPv6 Traffic Class field. You can select one of two queuing methods:  IEEE 802.1p standard method  Cisco-proprietary method The queuing method determines how the traffic is prioritized. Each port has four egress queues (queues 0-3) of differing priorities. Queue 0 is the lowest priority and Queue 3 is the highest priority. Configuring the Ethernet switch for QoS 1. Select Link or Local or Remote > Interface > Ethernet Settings. 2. In the Quick Links box at the bottom of the page, click Ethernet General Settings. The Ethernet General Settings page appears: 3. Leave Ethernet Grouping set to 'Disabled' (unless you want to enable VLAN tagging).
Configuring the traffic interfaces | 83 4. Select the Priority Queue Scheduling. There are two methods for transmitting the Ethernet traffic queues across the link:  Strict: the queue is transmitted based on the priority. The first queue transmitted is the highest priority queue and the terminal will not transmit any other traffic from any other queue until the highest priority queue is empty. Then the next highest priority queue is transmitted, and so on.  Weighted (default): each of the queues will transmit a number of packets based on a weighting. The following table shows how the weighting is applied to each queue. Queue Priority Number of packets transmitted Queue 3 Highest Priority 8 packets Queue 2 4 packets Queue 1 2 packets Queue 0 Lowest Priority 1 packets 5. Select the IEEE 802.1 Priority Queue Mapping. This determines the standard (or scheme) used for prioritizing traffic into one of four queues numbered 0 to 3 (3 being the highest priority queue). There are two possible methods for queuing the ethernet traffic. One is based on the IEEE 802.1D standard (which is the default setting), and the other is based on the Cisco-proprietary method. The following table shows how traffic is queued using the two methods: Output Queue Priority Traffic Type Cisco Priority Queuing IEEE 802.1D Priority Queuing 0 (default) Best Effort 0 1 1 Background 0 0 2 Spare 1 0 3 Excellent Effort 1 1 4 Controlled Load 2 2 5 ‘Video’ < 100ms latency and jitter 2 2 6 ‘Video’ < 10ms latency and jitter 3 3 7 Network Control 3 3
Configuring the traffic interfaces | 84 Configuring the Ethernet ports for QoS Each Ethernet port can be configured for Ingress Rates and Priority queues. To configure the Ethernet ports for QoS: 1. Select Link or Local or Remote > Interface > Ethernet Settings. 2. Select the port you want to configure and click Port Configuration.
Configuring the traffic interfaces | 85 3. Select the required Ingress Rate for this port. The ingress rate (input data rate) limits the rate that traffic is passed into the port. Operators can protect the terminal’s traffic buffers against flooding by rate-limiting each port. Ingress Rate Unlimited Default 128 kbit/s 256 kbit/s 512 kbit/s 1 Mbit/s 2 Mbit/s 4 Mbit/s 8 Mbit/s 4. Select the Priority for all Ethernet data entering this port. The priority specifies where the priority control information is sourced from. From Frames Traffic is prioritized into one of the following traffic types (numbered 0 to 7) by the originating device or application. Generally, the higher the priority, the higher the priority rating. However, in the IEEE standard queuing scheme, the ordering of the priority is 1, 2, 0, 3, 4, 5, 6, 7. In this case 0 has a higher priority than 1 and 2. If priority control information is present in the Ethernet header, this information is used to priorities the traffic but if there is no priority control information in the Ethernet header, the IP header is used to priorities the traffic. Low, Medium, High, Very High The priority rating you select is applied to all traffic on the port and is applied to all traffic irrespective of traffic type and the priority control information in the traffic. 5. Click Apply to apply changes or Reset to restore the previous configuration.
Configuring the traffic interfaces | 86 Viewing the status of the ethernet ports Select Link or Local or Remote > Interface > Switch Summary. For each port the following is shown:  Speed — the data rate (in Mbit/s) of the port.  Duplex — whether half or full duplex.  Status — whether there is a cable plugged into the port (active) or not (inactive). Note: The Ethernet ports on the terminal are set to auto-configure the speed and duplex for the best performance. Resetting the Ethernet settings You can easily reset the VLAN and QoS settings to the default values, if required. This is useful if you want the Ethernet switch to operate in the default mode, that is, IP packets are passed across the link as received. Note: You can also do this using the Setup menu (on page 66). 1. Select Link or Local or Remote > Interface > Default Ethernet Settings. Set Ethernet Groupings To Default Values. This resets the Ethernet Grouping setting to 'Disabled', which means that the Ethernet switch no longer operates as a VLAN. In addition, all the Ethernet ports will default to the 'User and Management' Ethernet Group. Set Ethernet QoS To Default Values. This resets the ingress rate for all the ports to 'Unlimited' and the priority to 'From Frames'. In addition, the Ethernet QoS settings are reset to the defaults: Priority Queue Scheduling reverts to 'Weighted' and IEEE 802.1 Priority Queue Mapping reverts to 'IEEE Standard'. 2. Click Apply to apply changes or Reset to restore the previous configuration.
Configuring the traffic interfaces | 87 QJET port settings 1. Select Link or Local or Remote > Interface > Interface Summary, then select the QJET interface and click Configure Interface. 2. Select the QJET port to be configured and click Edit. 3. Set the QJET Line Encoding: For an E1 port, set the E1 Line Encoding as required to either HDB3 or AMI. The default is HDB3. For a T1 port, set the T1 Line Encoding as required to either B8ZS or AMI. The default is B8ZS. 4. Set the QJET T1 Tx Waveform Shaper (T1 only). The Tx Waveform Shaper applies 1/f pre-emphasis to the transmit waveform to ensure the waveform meets the G.703 pulse mask at the interconnect point. Waveform shaping assumes the use of 22 gauge (0.32 mm2) twisted-pair cable. The default is 0 ~ 133 ft. Cable Length Range 0 ~ 133 ft Default 133 ~ 266 ft 266 ~ 399 ft 399 ~ 533 ft 533 ~ 655 ft
Configuring the traffic interfaces | 88 5. Set the QJET interface Clock Source. One interface port in each terminal can be set to 'primary' and one interface port to 'secondary' (an error message will appear if you try to set more than one primary source or more than one secondary source). A port currently set to primary must be set to 'None' and applied before it can be reset to secondary. Note: The terminal clock source is selected in Local or Remote > Terminal > Clocking 6. Set the QJET interface Loopback, if required, to either line-facing (tests E1 / T1 traffic across the interface card but not across the link) or terminal-facing (tests E1 / T1 traffic across the link). Note: The E1 / T1 port green LED flashes when the loopback is active. 7. Click Apply to apply changes or Reset to restore the previous configuration.
Configuring the traffic interfaces | 89 Q4EM port settings 1. Select Link or Local or Remote > Interface > Interface Summary, select the Q4EM interface, and click Configure Interface. 2. Select the Q4EM port to be configured, and click Edit. 'Slot' shows the slot the Q4EM interface card is plugged into in the terminal (A – H). 'Port' shows the interface port number (1-4). ‘PCM Mode’ shows the current mode assigned to the port by the cross connect. ‘E&M’ shows if the E&M signalling on the port has been activated by the cross connect. ‘Loopback’ loops back the port 4 wire analogue path to the customer. 3. Set the Q4EM Output level and the Input level required. Signal Direction Level adjustment range Default setting Input level (Li) -14.0 dBr to +4.0 dBr in 0.5 dB steps +0.0 dBr Output level (Lo) -14.0 dBr to +4.0 dBr in 0.5 dB steps +0.0 dBr
Configuring the traffic interfaces | 90 4. Set the Q4EM E wire interface to either Normal or Inverted. This determines the state of the CAS bit relative to the state of the E wire: E wire output CAS bit Normal (default) CAS bit Inverted Output Active 0 1 Output Inactive 1 0 5. Set the Q4EM M wire interface to either Normal or Inverted. This determines the state of the CAS bit relative to the state of the M wire: M wire input CAS bit Normal (default) CAS bit Inverted Input Active 0 1 Input Inactive 1 0 6. Click Apply to apply changes or Reset to restore the previous configuration. 7. Select Q4EM PCM Law Control from the Quick Links box. This option sets the companding law used by the four ports on the Q4EM card.  A-Law is used internationally (default).  µ-Law is used in North America and Japan. Note: The PCM Law Control controls all four ports on the Q4EM card. To run a mixture of µ-Law and A-Law interfaces, multiple Q4EM cards are necessary.
Configuring the traffic interfaces | 91 DFXO / DFXS loop interface circuits Function The function of DFXO / DFXS 2 wire loop interface circuits is to transparently extend the 2 wire interface from the exchange line card to the telephone / PBX, ideally without loss or distortion. The DFXO interface simulates the function of a telephone and a DFXS interface simulates the function of an exchange line card. These circuits are known as ‘ring out, dial in’ 2 wire loop interface circuits. Network Performance The overall Network Performance is dependant on the number of D-A and A-D conversions and 2 wire to 4 wire / 4 wire to 2 wire conversions in the end to end circuit (telephone to telephone). To achieve the best overall Network Performance, the number of D-A and A-D conversions and 2 wire to 4 wire / 4 wire to 2 wire conversions should be minimized. Circuit Performance The circuit quality achieved with a 2 wire voice circuit is very dependant on the external interface parameters and the interconnecting copper line. Short interconnecting copper lines (< 100 meters), have little effect on the circuit performance so the interface parameters have the dominant affect on circuit performance. As the length of the interconnecting copper line is increased, the attenuation of the analogue signal degrades circuit performance but also the impedance of the copper line also has a greater effect on the circuit performance. For this reason, complex line impedance networks (e.g. TBR21, TN12) were created which model the average impedance of the copper network. The factors that affect the quality of the circuit achieved are; DFXO interface • The degree of match between the DFXO line termination impedance, the impedance of the interconnecting copper line and the exchange line card line termination impedance. This affects the return loss. • The degree of match between the DFXO line termination impedance, the impedance of the interconnecting copper line and the exchange line card hybrid balance impedance. This affects the exchange line card transhybrid balance. • The degree of match between the DFXO hybrid balance impedance, the impedance of the interconnecting copper line and the exchange line card line termination impedance. This affects the DFXO transhybrid balance. • The circuit levels of both the DFXO and the exchange line card. DFXS interface • The degree of match between the DFXS line termination impedance, the impedance of the interconnecting copper line and the telephone line termination impedance. This affects the return loss. • The degree of match between the DFXS line termination impedance, the impedance of the interconnecting copper line and the telephone hybrid balance impedance. This affects the telephone transhybrid balance. • The degree of match between the DFXS hybrid balance impedance, the impedance of the interconnecting copper line and the telephone line termination impedance. This affects the DFXS transhybrid balance. • The circuit levels of both the DFXS and the telephone.
Configuring the traffic interfaces | 92 Line Termination Impedance The line termination impedance (Zt) is the impedance seen looking into the DFXO or DFXS interface. The line termination impedance is not the same as the hybrid balance impedance network (Zb) but can be set to the same value. Changing the DFXO / DFXS impedance setting on the Aprisa XE changes both the line termination impedance and the hybrid balance impedance to the same value. Hybrid Balance Impedance The hybrid balance impedance (Zb) is the impedance network on the opposite side of the hybrid from the DFXO / DFXS line interface. The purpose of this network is to balance the hybrid to the impedance presented to the DFXO / DFXS line interface. Changing the DFXO / DFXS impedance setting on the Aprisa XE changes both the line termination impedance and the hybrid balance impedance to the same value. Transhybrid loss Transhybrid loss is a measure of how much analogue signal received from the remote terminal is passed across the hybrid and sent to the remote terminal. The transhybrid loss is maximized when the hybrid balance impedance matches the impedance presented to the DFXO / DFXS line interface. An optimized hybrid minimizes circuit echo.
Configuring the traffic interfaces | 93 Circuit Levels The 8 bit digital word for each analogue sample encoded (A law), has a maximum of 255 quantizing code steps, + 127 for positive signals, -127 for negative signals and 0. A nominal level of 0 dBm generates a peak code of ± 118 which allows up to +3.14 dBm0 of headroom before the maximum step of 127 is obtained. Any level greater than +3.14 dBm0 will be distorted (clipped) which will cause severe problems with analogue data transmission. It is therefore important that analogue signals presented from the DFXO / DFXS line interface be normalized to fit within the ± 127 quantizing steps. This is done by adjusting the circuit levels relative to the 0 dBm (± 118 peak code) for example:  If a nominal input level of +1 dBm is applied to the DFXS line interface, the DFXS Input Level must be set to +1.0 dBr. This will effectively attenuate the sent signal by 1 dB.  If a nominal output level of -6 dBm is required from the DFXS line interface, the DFXS Output Level must be set to -6.0 dBr. This will effectively attenuate the received signal by 6 dB. The circuit levels and the transhybrid loss of both ends of the circuit, also determine the stability of the circuit. If the circuit levels are too high and the transhybrid loss figures achieved are too low, the circuit can have a positive loop gain and can recirculate (sometimes called singing). Typically, an end to end 2 wire voice circuit is engineered to have a 2-3 dB loss in both directions of transmission. 2WS2WR 2WS input2WR output0 dBr -6.0 dBr+1.0 dBr-8.0 dBm+1.0 dBm-2.0 dBm0 dBr0.0 dBm-4.0 dBr-1.0 dBr-6.0 dBmDFXSInterfaceDFXOInterface2WS2WR-6.0 dBr+1.0 dBr-1.0 dBm0 dBr0.0 dBm0 dBr-2.0 dBmExchangeLine CardAprisa XEOverall Loss = 3.0 dBOverall Loss = 8.0 dBDerived System Level PlanNote 1: The derived system loss is 2 dB in both directions due to the deliberate 2 dB level mismatch betweenthe exchange line card and the DFXO interface unitZBZBZBTransmissionReference Point4WR4WS4WR4WS4WR4WS
Configuring the traffic interfaces | 94 DFXS port settings 1. Select Link or Local or Remote > Interface > Interface Summary, then select the DFXS interface and click Configure Interface. 2. Select the DFXS port to configure, and click Edit. 'Slot' shows the slot the DFXS interface card is plugged into in the terminal (A – H). 'Port' shows the interface port number (1-2). ‘PCM Mode’ shows the current mode assigned to the port by the cross connect. ‘Loopback’ loops back the port digital paths to return the port analogue signal back to the customer. ‘Path Mute’ mutes the TX or RX digital path. This function is used to mute the return direction of transmission during A-A intrinsic performance testing as recommended in ITU G.712 para 1.2 Port definitions. Path Mute Description No Mute Normal signal transmission in both directions Default Mute TX Mutes the transmit digital path i.e. the signal from the DFXS to the DFXO is muted Mute RX Mutes the receive digital path i.e. the signal from the DFXO to the DFXS is muted
Configuring the traffic interfaces | 95 3. Set the DFXS Input Level and the Output Level required: Signal Direction Level adjustment range Default setting Input Level (Li) -9.0 dBr to +3.0 dBr in 0.5 dB steps +1.0 dBr Output Level (Lo) -9.5 dBr to +2.5 dBr in 0.5 dB steps -6.0 dBr In the example shown below, the Customer Premises Equipment is a telephone connected to a DFXS card. The levels are set based on the system using a 0 dBr transmission reference point. Output level+1.0 dBrInput level-6.0 dBrOutput level-6.0 dBrInput level+1.0 dBrTransmission Reference point0 dBr DFXS Input Level setting The telephone has a nominal output level of +1 dBr. To achieve a transmission reference point transmit level of 0 dBr, the DFXS Input Level is set to +1 dBr (effective T pad loss of 1 dB). DFXS Output Level setting The telephone has a nominal input level of -6 dBr. With a transmission reference point received level of 0 dBr, the DFXS Output level is set to -6 dBr (effective R pad loss of 6 dB). 4. Click Apply to apply changes or Reset to restore the previous configuration.
Configuring the traffic interfaces | 96 5. Select the DFXS Control. The DFXS Control page sets values for both ports on the DFXS card. The cards are shipped with the default values shown in the illustration below: 'Slot' shows the slot the DFXS interface card is plugged into in the terminal (A – H). 6. Select the DFXS PCM Law. This option sets the companding law used by both ports on the DFXS card.  A-Law is used internationally (default)  µ-Law is used in North America and Japan. Note: To run a mixture of µ-Law and A-Law interfaces, multiple DFXS cards are necessary.
Configuring the traffic interfaces | 97 7. Select the DFXS Line Impedance This option sets the DFXS line termination impedance and the hybrid balance impedance to the same value. Selection Description 600  Standard equipment impedance Default 600  + 2.16 uF Standard equipment impedance with low frequency roll-off 900  Typically used on loaded cable pairs 900  + 2.16 uF Typically used on loaded cable pairs with low frequency roll-off TN12 Standard complex impedance for Australia TBR21 Widely deployed complex impedance BT3 Standard complex impedance for New Zealand  On a short line (< 100 meters), the selected impedance should match the impedance of the phone (off-hook).  On a long line (> 1000 meters), the selected impedance should match the impedance of the phone (off-hook) as seen through the line. If you are not sure what the expected impedance value should be, check with the CPE equipment supplier. 8. Set the DFXS Transhybrid Balance (usually not required to change). The default Transhybrid Balance value (0 dB), provides the best circuit performance where the balance impedance (set by the Line Impedance setting) matches the impedance of the line. You should only adjust the transhybrid balance when the balance impedance does not match the actual line impedance. You can achieve small circuit improvements using this option. 9. Set the DFXS Ringer Frequency. This option sets the DFXS Ringing Frequency. Selection Description 17 Hz Used in older networks 25 Hz Standard ringing frequency Default 50 Hz Used by some telephone exchanges
Configuring the traffic interfaces | 98 10. Set the DFXS Ringer Output Voltage. This option sets the DFXS open circuit Ringing Output Voltage which is sourced via an internal ringing resistance of 178 Ω per port. The DC offset on the AC ringing signal enables ring trip to occur with a DC loop either during ringing cycles. The normal DC line feed voltage enables ring trip to occur with a DC loop in the silent period between the ringing cycles. Selection Description 60 Vrms + 0 VDC Outputs 60 VRMS ringing with no DC offset Maximum ringing voltage for high ringing load applications but no DC ring trip 55 Vrms + 10 VDC Outputs 55 VRMS ringing with a 10 VDC offset Medium ringing load applications 50 Vrms + 18 VDC Outputs 50 VRMS ringing with a 18 VDC offset Above average ringing load applications 45 Vrms + 22 VDC Outputs 45 VRMS ringing with a 22 VDC offset Typical application Default 40 Vrms + 24 VDC Outputs 40 VRMS ringing with a 24 VDC offset Lowest terminal power consumption 11. Select the DFXS Billing Tone Frequency. This option sets the frequency of billing tone generation. If you are not sure what the expected frequency of the billing tone should be, check with the exchange equipment supplier. Selection Description 12 kHz Use if the CPE requires a 12 kHz billing tone signal 16 kHz Use if the CPE requires a 16 kHz billing tone signal Default
Configuring the traffic interfaces | 99 12. Select the DFXS Billing Tone Level. This option sets the DFXS billing tone output level which is defined as the voltage into 200  with a source impedance equal to the Line Impedance setting. The billing tone voltage into 200  is limited by the maximum open circuit voltage of 1 Vrms. The drop down list reflects the maximum allowable billing tone output voltage for the Line Impedance setting selected. Selection Description 400 mV rms Billing tone voltage setting available for line impedances of TN12, BT3 and TBR21. 300 mV rms Billing tone voltage setting available for line impedances of TN12, BT3, TBR21 and 600 . Default 200 mV rms Billing tone voltage setting available for line impedances of TN12, BT3, TBR21, 600  and 900 . 100 mV rms Billing tone voltage setting available for all line impedance settings. 13. The DFXS billing tone Attack Ramp time can be adjusted to reduce the interference which can be produced when a signal turns on quickly. The attack ramp time is how long the billing tone generator takes to ramp up to full level when it is turned. The default ramp time is 1 ms.
Configuring the traffic interfaces | 100 14. The DFXS Signalling Advanced options are used to control the four CAS bits ABCD in the DFXO to DFXS direction of transmission and one CAS bit A in the DFXS to DFXO direction of transmission. This option sets the signalling for both DFXS card ports. Transparent Normal mode is used for normal traffic and Transparent Inverted mode can be used for special signalling requirements when a function needs to be reversed e.g. to change the idle polarity of the DFXS line feed voltage. Forced modes are used to disable particular functions e.g. when polarity reversals are not required. They can also be used for system testing e.g. to apply DFXS continuous ringing output Selection Description Transparent Normal Normal transparent transmission of the CAS bit Default Transparent Inverted Transparent transmission of the CAS bit but inverts the polarity. Forced Normal Sets the CAS bit to 1 (inactive). Forced Inverted Sets the CAS bit to 0 (active). DFXO to DFXS CAS Bit Forced Normal Forced Inverted A bit (fault) Sets the CAS A bit to 1 continuous fault state Sets the CAS A bit to 0 no fault state B bit (ring) Sets the CAS B bit to 1 no DFXS ringing output. Sets the CAS B bit to 0 continuous DFXS ringing output. C bit (billing) Sets the CAS C bit to 1 no DFXS billing tone output. Sets the CAS C bit to 0 continuous DFXS billing tone output.D bit (reversal) Sets the CAS D bit to 1 no DFXS polarity reversal Sets the CAS D bit to 0 continuous DFXS polarity reversal DFXS to DFXO CAS Bit Forced Normal Forced Inverted A bit (off hook) Sets the CAS A bit to 1 no DFXO off hook Sets the CAS A bit to 0 continuous DFXO off hook 15. Once the DFXS card has been set up, you can ensure optimal performance by plugging in the telephone (on-hook), and selecting Recalibrate from the Calibrate drop-down menu. This calibrates the DFXS to the line length. 16. Click Apply to apply changes or Reset to restore the previous configuration.
Configuring the traffic interfaces | 101 DFXO port settings 1. Select Link or Local or Remote > Interface > Interface Summary, then select the DFXO interface and click Configure Interface. 2. Select the DFXO port to configure, and click Edit. 'Slot' shows the slot the DFXO interface card is plugged into in the terminal (A – H). 'Port' shows the interface port number (1-2). ‘PCM Mode’ shows the current mode assigned to the port by the cross connect. ‘Loopback’ loops back the port digital paths to return the port analogue signal back to the customer.
Configuring the traffic interfaces | 102 3. Set the DFXO Input Level and the Output Level required: Signal Direction Level adjustment range Default setting Input Level (Li) -10.0 dBr to +1.0 dBr in 0.5 dB steps -4.0 dBr Output Level (Lo) -10.0 dBr to +1.0 dBr in 0.5 dB steps -1.0 dBr In the example shown below, the PSTN exchange line card is connected to a DFXO card. The levels are set based on the system using a 0 dBr transmission reference point. Output level-6.0 dBrInput level+1.0 dBrOutput level-1.0 dBrInput level-4.0 dBrTransmission Reference point0 dBr DFXO Input Level setting The exchange line card has a nominal output level of -6 dBr. To achieve a digital reference point transmit level of -2.0 dBm0, the DFXO input level is set to -4.0 dBr (effective T pad gain of 4.0 dB). The deliberate 2 dB of loss between the exchange line card and the DFXO provides a 2 dB of overall circuit loss between the DFXO and the DFXS. DFXO Output Level setting The exchange line card has a nominal input level of +1.0 dBr. With a transmission reference point received level of -2.0 dBm0, the DFXO output level is set to -1.0 dBr (effective R pad loss of 1.0 dB). The deliberate 2 dB of loss between the exchange line card and the DFXO provides a 2 dB of overall circuit loss between the DFXS and the DFXO. 4. Click Apply to apply changes or Reset to restore the previous configuration.
Configuring the traffic interfaces | 103 5. Select the DFXO Control. The DFXO Control page sets values for both ports on the DFXO card. The cards are shipped with the default values shown in the illustration below: 'Slot' shows the slot the DFXO interface card is plugged into in the terminal (A – H). 6. Select the DFXO PCM Law. This option sets the companding law used by both ports on the DFXO card.  A-Law is used internationally (default)  µ-Law is used in North America and Japan. Note: To run a mixture of µ-Law and A-Law interfaces, multiple DFXO cards are necessary.
Configuring the traffic interfaces | 104 7. Select the DFXO Impedance This option sets the DFXO line termination impedance and the hybrid balance impedance to the same value. Selection Description 600  Standard equipment impedance Default 600  + 2.16 uF Standard equipment impedance with low frequency roll-off 900  Typically used on loaded cable pairs 900  + 2.16 uF Typically used on loaded cable pairs with low frequency roll-off TN12 Standard complex impedance for Australia TBR21 Widely deployed complex impedance BT3 Standard complex impedance for New Zealand BT Network Standard complex impedance for UK China Standard complex impedance for China  On a short line (< 100 metres), the selected impedance should match the impedance of the exchange line card.  On a long line (> 1000 metres), the selected impedance should match the impedance of the exchange line card as seen through the line. If you are not sure what the expected impedance value should be, check with the exchange equipment supplier. 8. Enable the DFXO Echo Canceller if required. The DFXO Echo Canceller provides up to 64 ms of echo cancellation. This feature is only available on Rev D (and later) DFXO cards. Analogue data devices e.g. modems send a disable signal to disable any echo canceller in circuit while it trains its own echo canceller. There are two possible disable signals. ITU G.164 specifies a disable signal of a single 2100 Hz tone and ITU G.165 specifies a disable signal of 2100 Hz tone with phase reversals every 450 ms. Selection Description Off No echo canceller operation. Default On Echo canceller operational but without disabling. Auto Disable G.164 Echo canceller operational with automatic disabling using ITU G.164 2100 Hz tone. Auto Disable G.165 Echo canceller operational with automatic disabling using ITU G.165 2100 Hz tone with phase reversals every 450 ms.
Configuring the traffic interfaces | 105 9. Set the DFXO Loop Current Limiter. This option turns on a current limiter which limits the maximum current that can be drawn from the exchange line card by the DFXO interface. As a general rule, only one interface should current limit so if the exchange interface current limits, the DFXO interface should be set to current limit off. Selection Description Off Use if the exchange line interface uses current limiting. Default On (60 mA) Use if the exchange line interface does not use current limiting. The DFXO limits the line loop current to 60 mA. Note: The DFXO provides an early warning over current alarm ‘fxoCurrentOvld’ if the loop current exceeds 100 mA for 2 seconds. This alarm clears when the loop current is less than 90 mA. The DFXO also provides an over current safety shut down limit which removes its line loop if the loop current exceeds 160 mA. 10. Select the DFXO Billing Tone Frequency. This option sets the frequency of billing tone detection. If you are not sure what the expected frequency of the billing tone should be, check with the exchange equipment supplier. Selection Description 12 kHz Use if the exchange outputs 12 kHz billing tone 16 kHz Use if the exchange outputs 16 kHz billing tone Default 11. The DFXO Billing Tone Advanced sets the billing tone Bandwidth and the billing tone Level Sensitivity. The DFXO billing tone Bandwidth determines the bandwidth of the band pass filter that is used by the billing tone detector in terms of +/- % of the billing tone frequency. The adjustment range is +/- 1.5% to +/- 7.5% and the default value is +/- 5.0%. The DFXO billing tone Level Sensitivity determines the DFXO detection sensitivity. The adjustment range is 0 dB (metering detection threshold of -17 dBm measured across 200 Ω) to 27 dB (metering detection threshold of -40 dBm measured across 200 Ω) in 1 dB steps and the default value is 0 dB.
Configuring the traffic interfaces | 106 12. Select the DFXO On Hook Speed. This option sets the slope of the transition between off-hook and on-hook. Selection Description < 500 s Off-hook to on-hook slope of < 500 s Default 3 ms Off-hook to on-hook slope of 3 ms ± 10% that meets ETSI standard 25 ms Off-hook to on-hook slope of 25 ms± 10% used to reduce transient interference in copper cable 13. Select the DFXO ringer Impedance. This option sets the DFXO ringing input impedance as seen by a sine wave ringing signal applied to the DFXO 2 wire port at the frequency of ringing. Selection Description > 10 MΩ DFXO input impedance to ringing of > 10 MΩ Default 30 kΩ DFXO input impedance to ringing of 30 kΩ 14. Select the DFXO ringer Detection Threshold. This option sets the DFXO ringing detect threshold. Selection Description 16 Vrms DFXO detects ringing voltages of 16 Vrms or greater (does not detect ringing below 13 Vrms) Default 26 Vrms DFXO detects ringing voltages of 26 Vrms or greater (does not detect ringing below 19 Vrms) 49 Vrms DFXO detects ringing voltages of 49 Vrms or greater (does not detect ringing below 40 Vrms) It is recommended that the ringer Detection Threshold be set to 49 Vrms if a DFXO ringer impedance of 30 kΩ is selected. Note: The Signalling Mode is set in the Cross Connections application (see page 144).
Configuring the traffic interfaces | 107 15. The DFXO Signalling Advanced options are used to control the four CAS bits ABCD in the DFXO to DFXS direction of transmission and one CAS bit A in the DFXS to DFXO direction of transmission. This option sets the signalling for both DFXO card ports. Transparent Normal mode is used for normal traffic and Transparent Inverted mode can be used for special signalling requirements when a function needs to be reversed e.g. to change the idle polarity of the DFXS line feed voltage. Forced modes are used to disable particular functions e.g. when polarity reversals are not required. They can also be used for system testing e.g. to apply DFXO continuous off hook Selection Description Transparent Normal Normal transparent transmission of the CAS bit Default Transparent Inverted Transparent transmission of the CAS bit but inverts the polarity. Forced Normal Sets the CAS bit to 1. Forced Inverted Sets the CAS bit to 0. DFXO to DFXS CAS Bit Forced Normal Forced Inverted A bit (fault) Sets the CAS A bit to 1 continuous fault state Sets the CAS A bit to 0 no fault state B bit (ring) Sets the CAS B bit to 1 no DFXS ringing output. Sets the CAS B bit to 0 continuous DFXS ringing output. C bit (billing) Sets the CAS C bit to 1 no DFXS billing tone output. Sets the CAS C bit to 0 continuous DFXS billing tone output.D bit (reversal) Sets the CAS D bit to 1 no DFXS polarity reversal Sets the CAS D bit to 0 continuous DFXS polarity reversal DFXS to DFXO CAS Bit Forced Normal Forced Inverted A bit (off hook) Sets the CAS A bit to 1 no DFXO off hook Sets the CAS A bit to 0 continuous DFXO off hook 16. Click Apply to apply changes or Reset to restore the previous configuration.
Configuring the traffic interfaces | 108 QV24 port settings 1. Select Link or Local or Remote > Interface > Interface Summary, then select the QV24 interface and click Configure Interface. 2. Select the QV24 port to configure, and click Edit. 'Slot' shows the slot the QV24 interface card is plugged into in the terminal. 'Port' shows the interface port number (1-4). ‘Baud Rate’ shows the current baud rate assigned to the port by the cross connect. ‘Loopback’ loops back the port data to the customer (default is no loopback). 3. Set the number of Data Bits (default is 8 bits). 4. Set the number of Stop Bits (default is 1 bit). 5. Set the number of Parity Bits (default is 0 bits). 6. Click Apply to apply changes or Reset to restore the previous configuration. Tip: The Quick Links box provides links to other related pages.
Configuring the traffic interfaces | 109 HSS port settings 1. Select Link or Local or Remote > Interface > Interface Summary, then select HSS (High-speed Synchronous Serial) interface and click Configure Interface. 'Slot' shows the slot the HSS interface card is plugged into in the terminal (A – H). 'Mode' shows the interface mode provided by the HSS interface (either DTE or DCE). If there is no interface cable plugged into the HSS port, the ‘Mode’ will show ‘No Cable’. 'Serial Mode' shows interface type provided by the HSS interface (X.21, V.35 etc). If there is no interface cable plugged into the HSS port, the ‘Serial Mode’ will show ‘None’. ‘Baud Rate (kbit/s)’ shows the current baud rate assigned to the port by the cross connect. ‘Loopback’ loops back the port data to the customer (default is no loopback). ‘Synchronous Clock Selection’ shows the current clocking mode assigned to the port by the cross connect. 2. Set the HSS RTS CTS Mode as required. The RTS CTS mode controls the state of the outgoing interface RTS CTS control line. When the HSS interface is DCE, the outgoing control line is CTS. When the HSS interface is DTE, the outgoing control line is RTS. Note: Refer to “HSS handshaking and clocking” on page 111 for additional information on setting the recommended handshaking mode for each application. 3. Set the HSS DSR DTR Mode as required. The DSR DTR mode controls the state of the outgoing interface DSR DTR control line. When the HSS interface is DCE, the outgoing control line is DSR. When the HSS interface is DTE, the outgoing control line is DTR.
Configuring the traffic interfaces | 110 4. Set the HSS DCD Mode as required. The DCD mode controls the state of the outgoing interface DCD control line. This setting is only relevant if the HSS interface is DCE. 5. Set the HSS interface Clock Source. The interface clock source allows the HSS card to provide the master clocking for the terminal. This setting is compulsory in certain clocking modes. One interface port in each terminal can be set to 'primary' and one interface port to 'secondary' (an error message will appear if you try to set another port to either primary or secondary). A port currently set to primary must be set to 'None' and applied before it can be reset to secondary. Note: The terminal clock source is selected in Local or Remote > Terminal > Clocking 6. Enable or disable the HSS XTxC control, as required. Depending on the clocking mode (see “HSS handshaking and clocking” on page 111) selected, altering this setting will allow the terminal clock to be substituted for the external XTxC signal. 7. Click Apply to apply changes or Reset to restore the previous configuration.
Configuring the traffic interfaces | 111 HSS handshaking and clocking This section provides detailed information on selecting the recommended handshaking and clocking modes for the HSS interface card (see "HSS port settings" on page 109). HSS handshaking and control line function HSS X.21 compatibility In general X.21 usage, the C and I wires function as handshaking lines analogous to RTS/CTS handshakes. For switched carrier applications, the I wire is used to emulate carrier indications (DCD) function. HSS RTS / CTS mode Set the RTS CTS Mode as required according to the table below. This field controls the state of the outgoing interface control line.  When the HSS interface is DCE, the outgoing control line is CTS.  When the HSS interface is DTE, the outgoing control line is RTS. RTS CTS Mode HSS as a DCE HSS as a DTE Comment Always Off CTS driven to off state RTS driven to off state Always On CTS driven to on state RTS driven to on state Follows Carrier CTS follows the state of the RF link RTS follows the state of the RF link To follow carrier is to indicate the state of synchronization of the RF link Follows Carrier + Remote RTS/CTS CTS follows the state of the RF link and the remote terminal RTS input control line if the remote is a DCE. If the remote HSS is a DTE, then CTS follows the state of the RF link and the remote HSS CTS input. RTS follows the state of the RF link and the remote terminal RTS input control line. The remote HSS can only be a DCE. Control line pass-through mode where RTS and CTS are carried over the link from end to end. The carrier (as above) plus the remote terminal input control line must be present to output the local control line signal. The HSS Control bit in the Cross Connections application must be set for the remote signalling to operate. Follows Carrier + Remote DCD CTS follows the state of the RF link if the remote HSS is a DCE. If the remote HSS is a DTE, then CTS follows the state of the RF link and the remote HSS DCD input control line. This setting is only applicable when the local HSS card in the local terminal is a DCE. The HSS Control bit in the Cross Connections application must be set for the remote signalling to operate.
Configuring the traffic interfaces | 112 HSS DSR / DTR mode Set the DSR DTR Mode as required according to the table below. This field controls the state of the outgoing interface control line.  When the HSS interface is DCE, the outgoing control line is DSR  When the HSS interface is DTE, the outgoing control line is DTR DSR DTR Mode HSS as a DCE HSS as a DTE Comment Always Off DSR driven to off state DTR driven to off state Always On DSR driven to on state DTR driven to on state Follows Carrier DSR follows the state of the RF link DTR follows the state of the RF link To follow carrier is to indicate the state of synchronization of the RF link. Follows Carrier + Remote DSR/DTR DSR follows the state of the RF link and the remote terminal DSR control line if the remote terminal is a DTE, or the remote DTR if the remote terminal is a DCE. DTR follows the state of the RF link and the remote terminal DTR control line if the remote terminal is a DCE. The remote HSS can only be a DCE. Control line pass-through mode where DSR and DTR are carried over the link from end to end. The carrier (as above) plus the remote terminal input control line must be present to output the local control line signal. The HSS Control bit in the Cross Connections application must be set for the remote signalling to operate.
Configuring the traffic interfaces | 113 HSS DCD mode Set the DCD Mode as required according to the table below. This setting is only relevant in DCE mode. DCD Mode HSS as a DCE HSS as a DTE Comment Always Off DCD driven to off state Always On DCD driven to on state Follows Carrier + Remote DCD DCD follows the state of the RF link and the remote terminal DCD input control line if the remote HSS is a DTE. If the remote terminal is a DCE, then DCD only follows the state of the RF link. Control line pass-through mode where DCD is carried over the link from end to end. The carrier (as above) plus the remote terminal input control line must be present to output the local control line signal. The HSS Control bit in the Cross Connections application must be set for the remote signalling to operate. Follows Carrier + Remote RTS DCD follows the state of the RF link and the remote terminal RTS input control line when the remote HSS is a DCE. NOT applicable For switched carrier applications this provides RTS-DCD pass through (DCE to DCE configuration) and DCD-DCD pass-through (DTE to DCE configuration). Set the XTxC Enabled control as required. Depending on the synchronous clock selection mode selected, disabling XTxC will allow the terminal clock to be substituted for the external XTxC signal.
Configuring the traffic interfaces | 114 HSS synchronous clock selection modes The following section describes in detail each of the recommended HSS Synchronous Clock Selection modes for both DTE to DCE and DCE to DCE modes of operation. The HSS clocking can be configured for clocking types of Internal clocking, pass-through clocking, and primary / secondary master clocking. The topology of the client network determines the clock mode that is used. Note: Modes 3 and 4 provide only physical layer support, not X.21 protocol support. Terminal 1 HSS as a DTE and terminal 2 HSS as a DCE - “Pipe Mode” Mode Synchronous Clock Selection mode Clocking Type 0 Internal Clocks – No overhead Not supported 1 RxC + XTxC – 40 kbit/s overhead Not supported 2 RxC + TxC – 56 kbit/s overhead Pass-through clocking 3 RxC (X.21) – 40 kbit/s overhead Pass-through clocking (X.21 only) 4 RxC (X.21) – No overhead Not supported 5 XTxC → RxC – 40 kbit/s overhead Pass-through clocking 6 RxC → RxC – No overhead Primary/ Secondary Master clocking Note: The designation for mode 5 is shown as ‘XTxC → RxC – 40 kbit/s overhead’ but currently relates to ‘RxC → RxC - 40 kbit/s overhead’ for DTE to DCE. Terminal 1 HSS as a DCE and terminal 2 HSS as a DCE - “Cloud Mode” Mode Synchronous Clock Selection mode Clocking Type 0 Internal Clocks – No overhead Internal clocking 1 RxC + XTxC– 40 kbit/s overhead Not supported 2 RxC + TxC– 56 kbit/s overhead Not supported 3 RxC (X.21) – 40 kbit/s overhead Not supported 4 RxC (X.21) – No overhead Internal clocking (X.21 only) 5 XTxC → RxC – 40 kbit/s overhead Pass-through clocking 6 RxC → RxC – No overhead Not supported
Configuring the traffic interfaces | 115 HSS clocking types HSS internal clocking Internal clocking relies on the (highly accurate) terminal system clock, that is, it does not allow for any independent clocks coming in from client equipment. For this mode, all incoming clocks must be slaved to a clock emanating from the HSS card. HSS pass-through clocking The HSS card is capable in hardware of passing two clocks from one side of a link to the other. Passing a clock means that the difference between the client clock(s) and the terminal clock is transferred across the link continuously. Passing a single clock in each direction requires 40 kbit/s additional link overhead, passing two clocks from DTE to DCE requires 56 kbit/s overhead, whereas relying on internal clocking requires no overhead. Network topology determines if passing a clock makes sense. Passing a clock is used where a client's incoming clock must be kept independent of the clock sourced by the HSS card. The only time it makes sense to pass two clocks is when a client DCE in one of the HSS modes provides two independent clocks, that is, the HSS is set to Clock Mode 2. Pass-through clocking does not require using the HSS incoming clock as a Primary or Secondary master clock for the link, but does not preclude it either. HSS primary / secondary master clocking When implementing an external clock master, all other interfaces in the terminal and internal system timings are slaved to this external clock. The remote terminal is also slaved to this master clock. This master clock must be within 100 ppm of the accuracy of the terminal system clock, otherwise the terminal will revert to using its internal clock. Ideally, the external clock should be much better than 100 ppm. Mode 6 is offered for those network topologies that require RxC and TxC to be locked. For example, this is useful when interworking with an Aprisa SE HSS interface.
Configuring the traffic interfaces | 116 HSS clocking DTE to DCE “Pipe Mode” DTE to DCE Mode 2: RxC + TxC - 56 kbit/s overhead (Pass-through clocking) DTE clocks used DCE clocks used Clock passing Comment RxC and TxC RxC and TxC 56 kbit/s of overhead is used to transport RxC and TxC from HSS DTE to HSS DCE. This is the preferred dual external clock system. Both clocks travel in the same direction from DTE to DCE. This mode is used when it is important that the externally supplied RxC and TxC are maintained independently. This is almost only required in cascaded (that is, multi-link) networks. This mode cannot be used in conjunction with any interface conversion to / from X.21.
Configuring the traffic interfaces | 117 DTE to DCE Mode 3: RxC (X.21) - 40 kbit/s overhead (Pass-through clocking) DTE clocks used DCE clocks used Clock passing Comment RxC RxC 40 kbit/s of overhead used to transport RxC from the DTE to DCE. Preferred option for X.21. DTE to DCE Mode 5: RxC → RxC - 40 kbit/s overhead (Pass-through clocking) DTE clocks used DCE clocks used Clock passing Comment RxC and TxC RxC and TxC 40 kbit/s of overhead used to transfer RxC from the DTE to the DCE RxC and TxC. Receiver derived clock system.
Configuring the traffic interfaces | 118 DTE to DCE Mode 6: RxC → RxC - No overhead (Primary/ Secondary Master clocking) DTE clocks used DCE clocks used Clock passing Comment RxC and TxC RxC and TxC The DTE XTxC is derived from the RxC and is used to generate the terminal network clock. The DCE generates RxC and TxC from the terminal clock. HSS becomes the network master clock, avoiding explicit clock passing, but foregoing the use of passing a clock in either direction (Modes 1, 5). The DTE HSS card must be set as the Network clock for the terminal.
Configuring the traffic interfaces | 119 HSS clocking DCE to DCE “Cloud Mode” DCE to DCE Mode 0: Internal clocks – No overhead (internal clocking) DCE clocks used Clock passing Comment RxC, TxC, XTxC Both RxC and TxC are derived from the terminal clock. Default setting. All clocks sourced internally. XTxC will be used if it is detected.
Configuring the traffic interfaces | 120 DCE to DCE Mode 4: RxC (X.21) - No overhead (internal clocking) DCE clocks used Clock passing Comment RxC RxC is derived from the terminal clock. Suggested for X.21 Cloud Configuration. Single clock X.21 system. DCE to DCE Mode 5: XTxC → RxC - 40 kbit/s overhead (Pass-through clocking) DCE clocks used Clock passing Comment RxC, TxC, XTxC XTxC is transported to RxC and TxC in both directions

Navigation menu