April 2012 Version 8.6.
| 1 Copyright Copyright © 2012 4RF Limited. All rights reserved. This document is protected by copyright belonging to 4RF Limited and may not be reproduced or republished in whole or part in any form without the prior written permission of 4RF Limited. Trademarks Aprisa and the 4RF logo are trademarks of 4RF Limited. Windows is a registered trademark of Microsoft Corporation in the United States and other countries.
2 | Compliance General The Aprisa XE digital radio predominantly operates within frequency bands that require a site license be issued by the radio regulatory authority with jurisdiction over the territory in which the equipment is being operated. It is the responsibility of the user, before operating the equipment, to ensure that where required the appropriate license has been granted and all conditions attendant to that license have been met.
| 3 Informal Declaration of Conformity Dansk Undertegnede 4RF Limited 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 Limited, dass sich dieses Aprisa Radio in Übereinstimmung mit den grundlegenden Anforderungen und den anderen relevanten Vorschriften der Richtlinie 1999/5/EG befindet.
4 | Compliance FCC The Aprisa XE radio 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 27 Misc Wireless Communication Services 47CFR part 15 Radio Frequency Devices Safety EN 60950 Frequency band limits Channel size Power input Authorization FCC ID 421 MHz to 512 MHz 25 kHz 48 VDC Part 90 Cer
| 5 RF Exposure Warning WARNING: The installer and / or user of Aprisa XE radio terminals shall ensure that a separation distance as given in the following table is maintained between the main axis of the terminal’s antenna and the body of the user or nearby persons. Minimum separation distances given are based on the maximum values of the following methodologies: 1. Maximum Permissible Exposure non-occupational limit (B or general public) of 47 CFR 1.
Contents | 7 Contents 1. Getting Started .......................................................................... 15 2. Introduction .............................................................................. 19 About This Manual ............................................................................... 19 What It Covers ............................................................................ 19 Who Should Read It ......................................................................
8 | Contents 6. Connecting to the Terminal .......................................................... 45 Connecting to the Terminal's Setup Port .................................................... 45 Connecting to the Terminal's Ethernet Interface ........................................... 48 PC Requirements for SuperVisor ....................................................... 49 PC Settings for SuperVisor .............................................................. 50 IP Addressing of Terminals ....
Contents | 9 9. Configuring the Traffic Interfaces .................................................. 91 Viewing a Summary of the Interfaces ........................................................ 91 Configuring the Traffic Interfaces ............................................................ 92 Ethernet Switch ................................................................................. 93 VLAN tagging ..............................................................................
10 | Contents 10. Cross Connections ..................................................................... 145 Embedded Cross Connect Switch............................................................ Link Capacity Utilization .............................................................. The Cross Connections Application ......................................................... The Cross Connections System Requirements ...................................... Installing the Cross Connections Application ....
Contents | 11 12. In-Service Commissioning ............................................................ 197 Before You Start ............................................................................... What You Will Need .................................................................... Applying Power to the Terminals ........................................................... Review the Link Configurations Using SuperVisor ........................................ Antenna Alignment ...................
12 | Contents 15. Interface Connections ................................................................ 257 RJ-45 Connector Pin Assignments ........................................................... Interface Traffic Direction ................................................................... QJET Interface Connections ................................................................. Ethernet Interface Connections ............................................................. Q4EM Interface Connections .
Contents | 13 18. Specifications ........................................................................... 287 RF Specifications .............................................................................. ETSI ....................................................................................... FCC ....................................................................................... Industry Canada ........................................................................ Receiver Performance ......
Getting Started | 15 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 23 2. Ensure that the site preparation is complete: Page 26 Power requirements Tower requirements Environmental considerations, for example, temperature control Rack space 3. Confirm the interface card configuration. Phase 2: Installing the terminals 1.
16 | Getting Started Phase 3: Establishing the link 1. If you don't know the terminal's IP address : Page 58 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 2. Connect the Ethernet cable between the terminal's 4-port Ethernet switch and the PC. 3.
Getting Started | 17 Phase 4: Configuring the traffic 1. Confirm that the interface hardware and software slot configurations match. 2. Confirm the interface card settings. 3. Open the Cross Connections application and configure the cross connections: Page 92 Page 146 Download the configuration. Confirm or modify the traffic cross connections. Save the configuration to the terminal. Activate the configuration. 4. Save the configuration to disk and close the Cross Connections application. 5.
Introduction | 19 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 8.6.77. It is recommended that you read the relevant sections of this manual before installing or operating the terminal.
20 | Introduction Aprisa XE CD Contents The Aprisa XE CD contains the following: Software The latest version of the terminal software (see ‘Terminal Upgrades’ on page 214) The Cross Connections application - required if you want to use the Cross Connections application offline (see ‘Installing Cross Connections application’ on page 146). Java VM - Java plug-in needed to run the Supervisor software. Web browsers - Mozilla Firefox and Internet Explorer are included for your convenience.
Introduction | 21 Accessory Kit The accessory kit contains the following items: Two mounting brackets and screws Two interface slot blanking plates Setup cable (RJ-45 to RJ-45) 2 m and RS-232 DB9 female adaptor Hardware kit (includes Allen key for fascia screws) Aprisa XE User Manual
22 | Introduction Alarm cable (RJ-45 to RJ-45) 5 m Ground cable 5 m DC power cable 3 m (for use with the ±48 VDC, ±24 and 12 VDC low power power supplies) AC power cable 2 m (for use with the 110 / 230 VAC power supply) Aprisa XE User Manual
Preparation | 23 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.
24 | Preparation 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.
Preparation | 25 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.
26 | Preparation 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.
Preparation | 27 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.
28 | Preparation 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.
About the Terminal | 29 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.
30 | About the Terminal Modules The terminal is modular in design, which helps reduce mean time to repair (MTTR). It is designed for 19inch 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.
About the Terminal | 31 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.
32 | About the Terminal 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).
Mounting and Installing the Terminal | 33 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. CAUTION: You must comply with the safety precautions in this manual or on the product itself. 4RF Limited does not assume any liability for failure to comply with these precautions.
34 | Mounting and Installing the Terminal 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. WARNING: When the link is operating, there is RF energy radiated from the antenna.
Mounting and Installing the Terminal | 35 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.
36 | Mounting and Installing the Terminal 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 257). QJET Q4EM DFXO and DFXS The cabling to the QJET, Q4EM, DFXO and DFXS interface cards must have a minimum conductor size of 0.4 mm2 (26 AWG). Ethernet Standard Ethernet network cables are used for all Ethernet port cabling.
Mounting and Installing the Terminal | 37 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. Before disconnecting the safety earth during maintenance, remove AC or DC power supply connections, antenna cable and all interface cables from the terminal.
38 | Mounting and Installing the Terminal DC Power Input 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.
Mounting and Installing the Terminal | 39 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.
40 | Mounting and Installing the Terminal 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.
Mounting and Installing the Terminal | 41 Brownout Recovery Module A Brownout Recovery Module (BRM) is factory fitted to the Aprisa XE motherboard power connector when the radio is fitted with an AC power supply. The AC power supply has a safety mechanism that trips the power if it detects a power input brownout. The BRM restarts the power supply after 3 seconds.
42 | Mounting and Installing the Terminal 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.
Mounting and Installing the Terminal | 43 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.
Connecting to the Terminal | 45 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.
46 | Connecting to the Terminal 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.
Connecting to the Terminal | 47 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.
48 | Connecting to the Terminal 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.
Connecting to the Terminal | 49 PC Requirements for SuperVisor SuperVisor requires the following minimum PC requirements: Microsoft Windows 2000, NT, XP, Vista or Windows 7 Personal computer with 1.6 GHz Pentium IV 512 MB of RAM 200 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.6.
50 | Connecting to the Terminal 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.
Connecting to the Terminal | 51 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.
52 | Connecting to the Terminal 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 | 53 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.
54 | Connecting to the Terminal Network IP Addressing Same Subnet as the 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 | 55 Different Subnet as the 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 | 57 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.
58 | Managing the Terminal 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.
Managing the Terminal | 59 SuperVisor The SuperVisor management software is pre-loaded into an integrated web-server within the terminal. SuperVisor runs on any Java-enabled web browser.
60 | Managing the Terminal SuperVisor 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 64).
Managing the Terminal | 61 SuperVisor 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.
62 | Managing the Terminal SuperVisor Main Screen The SuperVisor Main Screen presents a summary of both the local and remote terminals and the status of the terminal front panel LED indicators: Aprisa XE User Manual
Managing the Terminal | 63 SuperVisor Menu Bar The SuperVisor Menu Bar at the top of the screen shows the names of the terminals, the top level menus and three status indicators for both the local and remote terminals. These indicators reflect the status LED indicators on the front panel of terminal.
64 | Managing the Terminal 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 58). To change the IP address of the terminals using SuperVisor: 1.
Managing the Terminal | 65 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.
66 | Managing the Terminal 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.
Managing the Terminal | 67 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.
Configuring the Terminal | 69 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.
70 | Configuring the Terminal 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.
Configuring the Terminal | 71 Channel size The RF channel size is a factory-configured setting determined by the Aprisa XE hardware option. Modulation 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.
72 | Configuring the Terminal Modem Performance Settings To view or change the modem performance settings: Select Link or Local or Remote > Terminal > Modem 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.
Configuring the Terminal | 73 Modem Mute Mode The Aprisa XE radio always mutes its interface ports when the modem loses lock. The Modem Mute feature mutes its interface ports when the modem Reed Solomon forward error correction capability can no longer correct errors.
74 | Configuring the Terminal Entering Basic Terminal Information To enter basic terminal information: Select Link or Local or Remote > Terminal > Basic Terminal Information The data entry in these four fields can be up to 40 characters but cannot contain back slashes or double quotes. 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.
Configuring the Terminal | 75 Configuring the IP Settings Select Link or Local or Remote > Terminal > Advanced. Advanced Terminal Settings 1. Enter the static IP Address for the terminal assigned by your site network administrator using the standard format xxx.xxx.xxx.xxx. The default IP address is in the range 169.254.50.xx. 2. Enter the Subnet Mask for the terminal using the standard format xxx.xxx.xxx.xxx. The default subnet mask is 255.255.0.0. 3.
76 | Configuring the Terminal Setting the Terminal Clocking To view the terminal clock status: Select Link or Local or Remote > Terminal > Clocking The current selected clock source and the current status of the primary and secondary external clocks are shown: Clock Status Clock Status 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 o
Configuring the Terminal | 77 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 External The terminal is clocked from the nominated interface port selected as the primary external clock or the secondary external clock.
78 | Configuring the Terminal To select the interface port for the external clock source (external clock source only): Select the traffic interface ports nominated as Primary External Clock or Secondary External Clock sources. The failure of both External Clock sources results in a major alarm. To manually override the automatic clock source selection (external clock source only): Select either Switch to Primary or Switch to Secondary from the drop-down list, and click Apply.
Configuring the Terminal | 79 Setting the Duplexer Parameters To set the duplexer parameters: Select Link or Local or Remote > Terminal > Duplexer Duplexer Parameters The terminal TX and RX frequencies entered are validated against the duplexer parameters entered on this page.
80 | Configuring the Terminal Setting 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 set 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.
Configuring the Terminal | 81 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).
82 | Configuring the Terminal 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’. Yes The external alarm input generates an alarm on the local terminal, displays in the ‘Alarm Table’ and ‘Alarm History’ and the ‘Alarm Summary’. Default 2.
Configuring the Terminal | 83 Configuring the External Alarm Outputs To configure the External Alarm Outputs: Select Link or Local or Remote > Alarms > Ext Alarm Outputs Note: When the MHSB mode is enabled on the terminal, the external alarm output 4 is used for protection switch control 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.
84 | Configuring the Terminal 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). Alarm off When the external alarm output relay contact is closed, the alarm is off (alarm inactive). Default 3. When you have made your changes, click Apply to apply changes or Reset to restore the previous configuration.
Configuring the Terminal | 85 Configuring SNMP Settings 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.
86 | Configuring the Terminal 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.
Configuring the Terminal | 87 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.
88 | Configuring the Terminal 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 | 89 Saving the Terminal's Configuration Note: To save cross connection configurations, see page 155. 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.
Configuring the Traffic Interfaces | 91 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.
92 | Configuring the Traffic Interfaces 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 235). 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.
Configuring the Traffic Interfaces | 93 Ethernet Switch 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.
94 | Configuring the Traffic Interfaces 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.
Configuring the Traffic Interfaces | 95 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.
96 | Configuring the Traffic Interfaces 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.
Configuring the Traffic Interfaces | 97 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.
98 | Configuring the Traffic Interfaces 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 | 99 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.
100 | Configuring the Traffic Interfaces 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.
Configuring the Traffic Interfaces | 101 Ethernet Port Startup In previous Aprisa XE software versions, the Ethernet switch ports where enabled when the radio powered up. In software version 8.6.53, the mode of operation was changed to disable the Ethernet switch ports until the radio software has completed booting. This enhancement has been implemented to meet customer requirements. A hardware modification is required to the Aprisa XE motherboard to enable this enhancement (0 ohm resistor fitted).
102 | Configuring the Traffic Interfaces 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.
Configuring the Traffic Interfaces | 103 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 f t . Cable Length Range 0 ~ 133 f t Def au lt 133 ~ 266 f t 266 ~ 399 f t 399 ~ 533 f t 533 ~ 655 f t 5.
104 | Configuring the Traffic Interfaces 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.
Configuring the Traffic Interfaces | 105 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 It is important that analogue signals presented from the Q4EM interface be normalized to fit within the ± 127 quantizing steps of the encoder.
106 | Configuring the Traffic Interfaces 8. Loopback controls the port loopbacks (see ‘Interface Loopbacks’ on page 242).
Configuring the Traffic Interfaces | 107 Loop Interface Circuits 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.
108 | Configuring the Traffic Interfaces 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.
Configuring the Traffic Interfaces | 109 Circuit Levels The 8 bit digital word for each analogue sample encoded (A law), has a maximum of 255 quantizing code steps, a maximum of + 127 for positive signals and a minimum of - 127 for negative signals. No signal is represented by the code step 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.
110 | Configuring the Traffic Interfaces E1 CAS to DFXS Circuits Function E1 CAS to DFXS circuits can be provisioned over an Aprisa XE link by using a DFXS interface card at the customer end of the link and a QJET at the exchange end of the link. The QJET E1 interface connects to an exchange or PBX Digital Trunk Interface (DTI) to provide FXS foreign exchange circuits.
Configuring the Traffic Interfaces | 111 Cross connect the voice channel on both DFXS cards. Cross connect the signalling (A bit only) using ‘4 wire compatible’ mode on both DFXS cards.
112 | Configuring the Traffic Interfaces 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.
Configuring the Traffic Interfaces | 113 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.
114 | Configuring the Traffic Interfaces 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.
Configuring the Traffic Interfaces | 115 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 600 Ω + 2.16 uF Standard equipment impedance with low frequency roll-off 900 Ω Typically used on loaded cable pairs 900 Ω + 2.
116 | Configuring the Traffic Interfaces 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.
Configuring the Traffic Interfaces | 117 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.
118 | Configuring the Traffic Interfaces 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.
Configuring the Traffic Interfaces | 119 QJET to DFXS CAS Bit Forced Normal Forced Inverted A bit (ring) Sets the CAS A bit to 1 no DFXS ringing output. Sets the CAS A bit to 0 continuous DFXS ringing output.
120 | Configuring the Traffic Interfaces 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.
Configuring the Traffic Interfaces | 121 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.
122 | Configuring the Traffic Interfaces 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.
Configuring the Traffic Interfaces | 123 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 600 Ω + 2.16 uF Standard equipment impedance with low frequency roll-off 900 Ω Typically used on loaded cable pairs 900 Ω + 2.
124 | Configuring the Traffic Interfaces 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.
Configuring the Traffic Interfaces | 125 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 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 Default 13. Select the DFXO ringer Impedance.
126 | Configuring the Traffic Interfaces 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.
Configuring the Traffic Interfaces | 127 QJET to DFXS CAS Bit Forced Normal Forced Inverted A bit (ring) Sets the CAS A bit to 1 no DFXS ringing output. Sets the CAS A bit to 0 continuous DFXS ringing output.
128 | Configuring the Traffic Interfaces QV24 Serial Interface Card There are two modes of operation of the QV24 Serial Interface Card; QV24 asynchronous and QV24S synchronous. The mode is changed with the Slot Summary. Changing the QV24 mode changes all four ports on the interface card. To change the QV24 mode: 1. Select Link or Local or Remote > Interface > Slot Summary, then select the QV24 interface slot and click Configure Slot. 2. Select the QV24 mode required with Expected. 3.
Configuring the Traffic Interfaces | 129 QV24 Port Settings A QV24 interface is always configured as a DCE. 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.
130 | Configuring the Traffic Interfaces QV24S Port Settings There are two modes of operation of the QV24S synchronous, synchronous and over sampling modes. A QV24S interface is always configured as a DCE. Synchronous Mode In synchronous mode, interface data is synchronously mapped to radio capacity using proprietary subrate multiplexing. QV24S interfaces are required at both ends of the circuit. 1.
Configuring the Traffic Interfaces | 131 3. The CTS Source defines the mode in which the CTS signal responds to the remote DTE. Three options are available: CTS Source Function Remote RTS The local CTS follows the remote RTS signal. In the case of radio link failure (when cross connected over the link) the signal goes to OFF. Local RTS The local CTS signal follows the local RTS. The status of the link does not impact on the CTS signal. On Permanent The local CTS is in a permanent ON (+ve) state.
132 | Configuring the Traffic Interfaces 2. Select the QV24S port to configure, and click Edit. 'Slot' shows the slot the QV24S interface card is plugged into in the terminal. 'Port' shows the interface port number (1-4). A Baud Rate of ‘OVRSAMP’ indicates that the QV24S has been configured for synchronous over sampling mode in the Cross Connections application. 3. The CTS Source defines the mode in which the CTS signal responds to the remote DTE.
Configuring the Traffic Interfaces | 133 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’.
134 | Configuring the Traffic Interfaces 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. Enable or disable the HSS XTxC control, as required. Depending on the clocking mode (see ‘HSS Handshaking and Clocking’ on page 135) selected, altering this setting will allow the terminal clock to be substituted for the external XTxC signal. 6.
Configuring the Traffic Interfaces | 135 HSS Handshaking and Clocking Modes This section provides detailed information on selecting the recommended HSS handshaking and clocking modes for the HSS interface card (see ‘HSS port settings’ on page 133). 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.
136 | Configuring the Traffic Interfaces 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.
Configuring the Traffic Interfaces | 137 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 NOT applicable 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.
138 | Configuring the Traffic Interfaces 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.
Configuring the Traffic Interfaces | 139 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.
140 | Configuring the Traffic Interfaces 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 RxC and TxC RxC and TxC Clock passing Comment 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.
Configuring the Traffic Interfaces | 141 DTE to DCE Mode 3: RxC (X.21) - 40 kbit/s overhead (Pass-through clocking) DTE clocks used DCE clocks used RxC RxC DTE to DCE Mode 6: RxC DTE clocks used DCE clocks used RxC and TxC RxC and TxC Clock passing 40 kbit/s of overhead used to transport RxC from the DTE to DCE. Comment Preferred option for X.21.
142 | Configuring the Traffic Interfaces DTE to DCE Mode 7: RxC DTE clocks used DCE clocks used RxC and TxC RxC and TxC RxC - 40 kbit/s overhead (Pass-through clocking) Clock passing 40 kbit/s of overhead used to transfer RxC from the DTE to the DCE RxC and TxC. Aprisa XE User Manual Comment Receiver derived clock system.
Configuring the Traffic Interfaces | 143 HSS Clocking DCE to DCE ‘Cloud Mode’ DCE to DCE Mode 0: Internal clocks – No overhead (internal clocking) DCE clocks used RxC, TxC, XTxC Clock passing Both RxC and TxC are derived from the terminal clock. Comment Default setting. All clocks sourced internally. XTxC will be used if it is detected.
144 | Configuring the Traffic Interfaces DCE to DCE Mode 4: RxC (X.21) - No overhead (internal clocking) DCE clocks used RxC Clock passing RxC is derived from the terminal clock. DCE to DCE Mode 5: XTxC DCE clocks used RxC, TxC, XTxC Comment Suggested for X.21 Cloud Configuration. Single clock X.21 system.
Cross Connections | 145 10. Cross Connections Embedded Cross Connect Switch The embedded cross-connect switch distributes capacity to each of the interfaces. Traffic can be distributed to any of the possible 32 interface ports as well as the integrated Ethernet interface. This provides the flexibility to reconfigure traffic as the network demand changes, or groom user traffic onto E1 / T1 bearers between equipment. The maximum number of simultaneous cross connections per terminal is 256.
146 | Cross Connections Installing the Cross Connections Application The Cross Connections application is usually started directly from SuperVisor without the need for installation. However, if you want to use the Cross Connections application offline (without any connection to the terminals), you can install it on your PC. Working offline enables you to simulate new cards or terminal capacities. The cross connections can then be configured and the resulting configuration file saved for later deployment.
Cross Connections | 147 The Cross Connections Page The Cross Connections page is split into two panes with each pane displaying one terminal. The local terminal is displayed in the left pane and the remote terminal is displayed in the right pane. The local terminal is defined as the terminal that SuperVisor is logged into (not necessarily the near end terminal). The cards displayed depend on the type of cards and where they are inserted in the chassis.
148 | Cross Connections Radio Link and Local Drop And Insert Capacity At the bottom of the Cross Connections page, the capacity pane displays the Radio and Local drop and insert capacities for both the local and remote terminals. The Radio Capacity field shows the available radio link capacity (6032 kbit/s shown) and the shaded bar graph shows the capacity used for cross connections over the radio link (2600 kbit/s) between the terminals as a percentage of the total capacity of the radio link (30 % used).
Cross Connections | 149 Cross Connections Toolbar The cross connections toolbar has buttons for commonly-used functions. Button Explanation Saves the cross connection configuration file to disk. The button turns amber when you have made changes that have not yet been saved. Gets the cross connection configuration from the local and remote terminals. Saves the cross connection configuration to the local and remote terminals.
150 | Cross Connections Management and User Ethernet Capacity The maximum ethernet capacity of an Aprisa XE terminal is dependant on the motherboard version: Motherboard Version Maximum Ethernet Capacity Rev C 32768 kbit/s Rev D 49152 kbit/s The maximum ethernet capacity available is the lesser of the maximum ethernet capacity or the available radio link capacity. The management ethernet capacity and user ethernet capacity must be identical on both terminals for the ethernet link to work correctly.
Cross Connections | 151 Setting Card Types Note: You only need to do this when creating configurations offline (that is, there is no connection to the terminal). When you are connected to the terminal, the Cross Connections application automatically detects the card types fitted in the terminal slots. You can specify the card type for any of the slots (A-H). 1. Right-click a slot. 2. Select Card Type and then select the interface card.
152 | Cross Connections Creating Cross Connections Point to point cross connections Three examples of point to point cross connections are shown below: Example 1 One 2 wire DFXO interface on the near end terminal slot E port 1 is cross connected via the radio link to a 2 wire DFXS on the far end terminal slot E port 1.
Cross Connections | 153 Example 2 One 2 wire DFXS interface on the near end terminal slot E port 1 is cross connected via the radio link to a framed E1 on the far end terminal slot D port 1 in timeslot 1. This cross connection includes four bits of signalling as the DFXS signalling is configured as 'non-multiplexed signalling' (ABCD bits). This cross connection uses 96 kbit/s of radio link capacity, 64 kbit/s for the voice and 32 kbit/s for the signalling bits.
154 | Cross Connections Local Drop and Insert Cross Connections An example of a local drop and insert cross connection is shown below: Two 4 wire E&M interfaces on the near end terminal slot C ports 3 & 4 are dropped out of a framed E1 on the near end terminal slot D port 1 in timeslots 1 & 2. This cross connection includes one bit of signalling (A bit).
Cross Connections | 155 Sending Cross Connection Configuration to the Terminals You can send the entire cross connection configuration to the terminals. 1. To send the new cross connection configuration into the terminals, click ‘Send cross connection configuration to terminal’. 2. When the transfer is successfully complete, a message appears asking if you want to activate the configuration now. If you click Yes, a message appears showing the activation progress.
156 | Cross Connections Printing the Cross Connection Configuration You can print out a summary of the cross connection configuration so that you can file it for future reference. Using the printout, you can recreate the cross connection configuration. If you don't have the configuration saved to disk see ‘Saving cross connection configurations’ on page 155, or use it to review the cross connections without connecting to the terminal.
Cross Connections | 157 Deleting Cross Connections Note: It is not possible to delete the management and user Ethernet cross connections. These are made automatically and are required for correct terminal operation. To delete cross connections for an interface card: 1. Right-click over an interface card. 2. Select Delete All Connections on this Card. To delete the cross connections associated with a particular port: 1. Right-click over a port. 2. Select Delete All Connections on this Port.
158 | Cross Connections Configuring the Traffic Cross Connections Once you have configured the interface cards (see ‘Configuring the traffic interfaces’ on page 91), you can configure the traffic cross connections between compatible interfaces.
Cross Connections | 159 QJET Cross Connections Expand the E1 / T1 display by clicking on the relevant icons. The QJET card can operate in several modes allowing you greater flexibility in tailoring or grooming traffic. The Data type selection are Off, E1, or T1 rates. Note: An unframed E1 / T1 port requires 5 bits (or 40 kbit/s) of overhead traffic per port for synchronization. An unframed E1 port with 2048 kbit/s of traffic requires 2088 kbit/s of link capacity.
160 | Cross Connections For each port that you want to put into service, choose the required mode (either Unframed or Framed): Unframed Mode Leave the Framed checkbox unticked. Select the required Data type from the drop-down list E1 or T1. Local drop and insert connections are not possible between Unframed E1 / T1 ports. Framed Mode Tick the Framed checkbox.
Cross Connections | 161 E1 Framed Modes Framed Mode Description E1 – PCM 30 Provides 30 timeslots to transport traffic. Timeslot 16 carries channel associated signalling data (CAS). E1 – PCM 31 Provides 31 timeslots to transport traffic. Timeslot 16 can be used for common channel signalling or to transport traffic. E1 – PCM 30C Same as E1 – PCM 30 mode but supports CRC-4. E1 – PCM 31C Same as E1 – PCM 31 mode but supports CRC-4.
162 | Cross Connections T1 Framed Modes Framed Mode Description T1 SF - PTS Provides 24 timeslots to transport traffic using the G.704 12 frame Super Frame with Pass Thru Signalling (PTS). There is no CRC capability with the SF. T1 SF - DMS Provides 24 timeslots to transport traffic using the G.704 12 frame Super Frame with DeMultiplexed Signalling (CAS AB bits). There is no CRC capability with the SF. T1 ESF - PTS Provides 24 timeslots to transport traffic using the G.
Cross Connections | 163 T1 ESF - PTS mode T1 ESF - PTS mode provides 24 timeslots to transport traffic using the G.704 24 frame Extended Super Frame without demultiplexing the signalling. Pass Thru Signalling provides cross connection of the entire framed T1 timeslot between T1 ports (including the inherent robbed bit signalling).
164 | Cross Connections T1 ESF - DMS T1 ESF - DMS mode provides 24 timeslots to transport traffic using the G.704 24 frame Extended Super Frame with sixteen state demultiplexed signalling using the ABCD bits each with a bit rate of 333 bit/s. DeMultiplexed Signalling allows the cross connection of framed T1 ports to other interface ports e.g. to a Q4EM or HSS. An additional 8 kbit/s of radio link capacity is required to transport each CAS bit over the radio link.
Cross Connections | 165 QJET Spare CAS Bit Control The Aprisa XE can currently provide E1 CAS to DFXS circuits using the 1 bit '4 wire compatible' signalling mode (uses the CAS A bit) but to enable some exchange DTIs to operate, the state of the spare CAS bits sent to the exchange must be preset. The available CAS bits can be preset to High (1) or Low (0) for the QJET framed modes of E1 - PCM30, E1 - PCM30C, T1 SF - DMS and T1 ESF – DMS for all timeslots of the port.
166 | Cross Connections Selecting and Mapping Bits and Timeslots This section describes how to select and map: a single bit multiple bits a 64 kbit/s timeslot multiple timeslots Selecting a Single Bit Each timeslot is represented by 8 rectangles (each representing a single bit). Each bit can carry 8 kbit/s. One or more consecutive bits can be selected in a timeslot if a rate of greater than 8 kbit/s is required. 1. Click on the rectangle that represents the bit you require. It will turn red. 2.
Cross Connections | 167 Selecting Multiple Bits It is possible to select multiple consecutive bits if circuit capacity of greater than 8 kbit/s is required. 1. Click the first bit, and then hold down the Ctrl key while selecting the remaining bits. 2. Click and drag the whole block by clicking the bit on the left hand side of your selection, and drag to the required interface. Release the mouse button.
168 | Cross Connections Selecting a 64 kbit/s Timeslot 1. Click on the TSX timeslot number (where X is the desired timeslot from 1 to 31). Alternatively, right-click over any of the bits in the timeslot, and click on Select Timeslot. 2. Drag and drop in the normal way to complete the cross connection. Selecting Multiple Non Consecutive Timeslots 1. Click on one TSn timeslot number (where n is the desired timeslot 1 to 31). 2.
Cross Connections | 169 Selecting Multiple Consecutive Timeslots 1. Click on the first TSn timeslot number (where n is the desired timeslot 1 to 31). 2. Hold down the Shift key while clicking on the last required timeslot number. 3. Drag and drop in the normal way to complete the cross connection. Selecting All Timeslots in a Port 1. Right-click over any of the rectangles. 2. Click Select All.
170 | Cross Connections Q4EM Cross Connections 1. Expand the Q4EM display by clicking the relevant icon. 2. Set the Voice capacity by selecting 16, 24, 32, or 64 kbit/s rates. 3. Drag and drop from the Voice mapping connection box to the required partner interface to create the voice cross connection. 4. If E&M signalling is required, drag and drop from the Signalling mapping connection box to the required partner interface to create the E&M cross connection.
Cross Connections | 171 DFXS and DFXO Cross Connections 1. On one side of the link, expand the DFXS display, as required, by clicking . 2. On the other side of the link, expand the corresponding DFXO display, as required, by clicking . 3. For the DFXS card and corresponding DFXO card, select the Signalling type as required, according to the table below. The CAS signalling between DFXO / DFXS interfaces uses 4RF proprietary allocation of control bits.
172 | Cross Connections QV24 Cross Connections 1. Expand the QV24 displays, as required, by clicking the relevant icons. 2. Select the Port Baud Rate as required (default is 9600). 3. Drag and drop to the required partner interface to create the V.24 Data connection. If the partner interface is a QJET: If the V.24 Baud Rate selected is 38400 is less, drag from the QV24 mapping connection box to the QJET timeslot. The correct QJET capacity for the baud rate selected will automatically be assigned.
Cross Connections | 173 QV24S Cross Connections Synchronous Mode 1. Expand the QV24S displays, as required, by clicking the relevant icons. 2. Select the Port Baud Rate as required (default is 9600). 3. Drag and drop to the required partner interface to create the V.24 Data connection. If the partner interface is a QJET, drag from the QV24S mapping connection box to the QJET timeslot. The correct QJET capacity for the baud rate selected will automatically be assigned.
174 | Cross Connections HSS Cross Connections 1. Expand the HSS displays, as required, by clicking the relevant icons. 2. Select the Synchronous Clock Selection mode (see ‘HSS Synchronous Clock Selection Modes’ on page 138). 3. Set the Data rate to a value between 8 and 2048 (in multiples of 8 kbit/s). The net data rate available to the user is defined by Data Rate – overhead e.g. a date rate set to 2048 kbit/s with an overhead of 40 kbit/s provides a user data rate of 2008 kbit/s. 4.
Cross Connections | 175 Cross Connection Example This is an example of cross connection mapping: Circuit Local port Remote port Radio management User Ethernet Capacity (kbit/s) Connection numbers 64 1 1024 2 4 wire E&M circuit Q4EM port 1 (slot C) Q4EM port 1 (slot C) 72 7/15 Unframed E1 data QJET port 1 (slot D) QJET port 1 (slot D) 2088 65 Unframed T1 data QJET port 2 (slot D) QJET port 2 (slot D) 1584 66 2 wire loop Interface DFXO port 1 (slot E) DFXS port 1 (slot E) 72 8/3
176 | Cross Connections Symmetrical Connection Wizard The Cross Connections application has a Symmetrical Connection Wizard which simplifies the cross connection configuration when the terminals are fitted with symmetrical / matching interface types. A symmetrical connection is a connection between the local and the remote terminal where the local slot, card type, port and connection details are identical to those of the remote terminal.
Cross Connections | 177 Setting the Cross Connections IP Address If the local or remote terminal IP addresses have been setup, they will be displayed in the Local and Remote fields. If the IP addresses are not displayed, enter the IP addresses of the local and remote terminals. Click on 'Get Configuration' to upload the existing cross connections configuration from the local terminal. The Radio bandwidth bar will show the available bandwidth and will be updated as bandwidth is assigned to cards.
178 | Cross Connections Cross Connections Card Selection If the Cross Connections Application is opened from SuperVisor, existing cards installed in the local terminal that match cards installed in the remote terminal will be displayed. Mismatched cards will be shown as 'Empty Slot'. If the Cross Connections Application is opened as a stand alone application, select the card types that will be fitted in the terminal.
Cross Connections | 179 Cross Connections Interface Configurations Setup the interface configurations as per the wizard instructions. Existing asymmetrical connections will be replaced with symmetrical connections if an interface parameter is changed. Q4EM QJET DFXO / DFXS QV24 HSS Ethernet To copy the port configuration selected in Port 1 to all the other ports on the card, click on the Copy Port button.
180 | Cross Connections Symmetrical Connection Summary Click Finish. Send Symmetrical Connection Configuration Click OK to send the configuration to the terminals. The process is completed. Note: The wizard may change the connection numbers of existing connections.
