Aprisa XE User Manual Version 7.3.
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.
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.
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.
Contents | v Contents 1. Getting started ................................................................................................11 2. Introduction .....................................................................................................15 About this manual..........................................................................................................15 What it covers ......................................................................................................
Contents | vi 7. Managing the terminal....................................................................................51 The setup menu ............................................................................................................51 4RF SuperVisor.............................................................................................................53 Logging in.............................................................................................................
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 ...........................................................
Contents | viii 13. Maintenance ..................................................................................................175 Routine maintenance ..................................................................................................175 Terminal upgrades ......................................................................................................176 Upgrade process................................................................................................
Contents | ix External alarm inputs .........................................................................................233 Remote terminal alarms .....................................................................................233 Cross connect alarms ........................................................................................233 MHSB alarms .....................................................................................................233 17. Country specific settings .........
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: Page 22 3. Power requirements Tower requirements Environmental considerations, for example, temperature control Rack space Confirm the interface card configuration. Phase 2: Installing the terminals 1.
Getting started | 12 Phase 3: Establishing the link 1. If you don't know the terminal's IP address : Page 52 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 | 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: Page 122 Download the configuration. Confirm or modify the traffic cross connections. Save the configuration to the terminal. Activate the configuration. 4.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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).
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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).
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 unav
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.
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.
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).
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’. 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 | 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 600 Ω + 2.16 uF Standard equipment impedance with low frequency roll-off 900 Ω Typically used on loaded cable pairs 900 Ω + 2.
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.
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.
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.
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.
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.
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.
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 600 Ω + 2.16 uF Standard equipment impedance with low frequency roll-off 900 Ω Typically used on loaded cable pairs 900 Ω + 2.
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.
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 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.
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.
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.
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’.
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.
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.
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.
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 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.
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.
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.
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 RxC and TxC RxC and TxC Clock passing 56 kbit/s of overhead is used to transport RxC and TxC from HSS DTE to HSS DCE. Comment This is the preferred dual external clock system. Both clocks travel in the same direction from DTE to DCE.
Configuring the traffic interfaces | 117 DTE to DCE Mode 3: RxC (X.21) - 40 kbit/s overhead (Pass-through clocking) DTE clocks used RxC DCE clocks used RxC Clock passing 40 kbit/s of overhead used to transport RxC from the DTE to DCE. Comment 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 RxC and TxC RxC and TxC Clock passing 40 kbit/s of overhead used to transfer RxC from the DTE to the DCE RxC and TxC.
Configuring the traffic interfaces | 118 DTE to DCE Mode 6: RxC → RxC - No overhead (Primary/ Secondary Master clocking) DTE clocks used DCE clocks used RxC and TxC RxC and TxC Clock passing Comment 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).
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 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.
Configuring the traffic interfaces | 120 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. Comment Suggested for X.21 Cloud Configuration. Single clock X.21 system.
