DXR NET NMT ION-NMS 2-2.5

��

��

�

Copyright © 2001 DMC Stratex Networks

All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated intoany language or computer language, in any form or by any means, electronic, magnetic, optical, chemical, manual or otherwise, without theprior written permission of DMC Stratex Networks.

DISCLAIMER

DMC Stratex Networks makes no representation or warranties with respect to the contents hereof and specifically disclaims any impliedwarranties or merchantability or fitness for any particular purpose. Further, DMC Stratex Networks reserves the right to revise thispublication and to make changes from time to time in the content hereof without obligation of DMC Stratex Networks to notify any personor such revision or changes.

CE MARK

This equipment has been designed to meet the requirements of the European Electromagnetic Compatibility Directive 89/336/EEC(currently amended by 92/31/EEC). Operation of the equipment is designed to provide reasonable protection against harmful interference inits electromagnetic environment without introducing intolerable electromagnetic disturbances.

TRADEMARKS AND REGISTERED TRADEMARKS

The DXR name and logo is a registered Trademark of DMC Stratex Networks.Parts of the DXR product design are protected under Patent Cooperation Treaty Application No: PCT/NZ93/00046.

Corporate HeadquartersAmericas HeadquartersSan Jose HeadquartersDMC Stratex Networks170 Rose Orchard WaySan Jose, CA 95134USA

Tel: +1-408-943-0777Fax: +1-408-944-1801

Europe/Africa/Middle East HeadquartersDMC Stratex NetworksSiskin DriveMiddlemarch Business ParkCoventry CV3 4JAUnited Kingdom

Tel: +44-1203-863838Fax: +44-1203-530126

Asia Pacific HeadquartersDMC Stratex Networks10 Ang Mo Kio Street 65#03-13 TechpointSingapore 569059

Tel: +65-484-7780Fax: +65-484-7768

SeattleDMC Stratex Networks3325 South 116th StreetSeattle, Washington 98168USA

Tel: +1 206 439 9121Fax: +1 206 439 2701

WellingtonDMC Stratex Networks Ltd24 Bridge StreetLower HuttNew Zealand

Tel: +64 4 569 2170Fax: +64 4 566 1247

Note: The DXR NET Help menu gives full details on how to contactDMC Stratex Networks Customer Support personnel, under the Customer Supportheading.

�� DXR NET V2.5k

�� April 2001

�� IOM-NMS-2/2.5

Table of Contents

i DMC STRATEX NETWORKS

APRIL 2001IOM-NMS-2/2.5

��

TABLE OF CONTENTS I

LIST OF FIGURES VIII

1 ABOUT THIS MANUAL 1Introduction 1Terminology 1What is the DXR NET ? 1DXR NET Software 2The DXR NET GUI 2DXRNET NMT Licensing 3DXR NET Language Support 3DXR NET Network Restrictions 3

Network Element Types 3New Features 4

Benefits 4Other DMC Stratex Network Management Solutions 4What You Will Find In This Manual 4What You Need To Know 5

Hardware Supported 6

2 INTRODUCTION TO DXR NET 7Introduction 7The DXR NET Management Domain 7

DXR Software Layering 7Connection Protocols 7Topologies of DXR 200-SMA Networks 10

DXR Software Sets 12Using DXR NET 12

The Network Blueprint Concept 12Using the Network Blueprint 13Using DXR NET to Manage Network Elements 13Storing and Retrieving DXR NET Data 15

The DXR NET GUI 15Title Bar 16Menu Bar 16Toolbar 19Explorer Tree Pane 20Mouse Overs 20Workspace Pane 20Status Bar 21

Configuration Workspace 21General Setup 22Port and EOW Settings 24Routing Table 27

Table of Contents

ii DMC STRATEX NETWORKS


Interface Setup 28Modem/RF Link Setup 32Alarm IO 39Action Table 41External I/O - SMA 42Thresholds 44Option Pages 46Cross-connects Page 52

Commissioning Workspace 54Commissioning 54Terminal Details for DXR 100 and 700 58Terminal Details for DXR 200 65NMS Details 67SMA Details 68Controls 69

Maintenance Workspace 73Constellation 74AGC 76Equalizer Graph 78RSSI 80File System 83

3 INSTALLING DXR NET 84Introduction 84Requirements 84

Software Requirements 84Hardware Requirements 84

Installing DXR NET in Windows 95 85Removing DXR NET from your PC 86Installing TCP/IP on your PC 87Installing DXR NET 88Installing Windows® “Dial-up” Networking 88Installing DMC DXR Driver Utility 89Starting Windows® “Dial-up” Networking for the First Time 89Installing WinSock2 90

Installing DXR NET in Windows 98 90Removing DXR NET from your PC 91Installing TCP/IP on your PC 92Installing DXR NET 93Installing Windows® “Dial-up” Networking 93Installing DMC DXR Driver Utility 94Starting Windows® “Dial-up” Networking for the First Time 94

Installing DXR NET in Windows NT 95Removing DXR NET from your PC 95Installing TCP/IP on your PC 96Installing DXR NET 96Installing DMC DXR Driver Utility 97Installing RAS (Remote Access Service) 98

4 USING DXR NET NMT 100General 100Designing Network Blueprints with the DXR NET 100

Network Blueprint Overview 100Creating a Network Blueprint for a non-NMS Network 101

Creating a non-NMS Blueprint 101Example 1: Non-NMS Blueprint 103

Creating a Network Blueprint for a NMS Network 105

Table of Contents

iii DMC STRATEX NETWORKS


DXR NMS Network IP Addressing Requirements (DXR 100 and 700 only) 105IP Addresses 106Mask IP Addresses 106DXR NMS Element IP Addressing 107NMS Element Ports 107Using Sub-nets 108Creating the Blueprint 109Example 2: NMS Blueprint 110Sending Network Blueprints via E-mail 117

Working with a DXR NETwork and Network Elements 117Network Visibility 117Terminal Connections 118NMS Connections 119Ethernet Connection 120Selecting the DXR NET Connection Type On Your PC 120Connecting to the Radio Network with a Blueprint 121Connecting to a Radio Network without a Blueprint (Autodiscovery) 121

Using DXR NET to Configure a Terminal 123Introduction 123Configuring a Terminal Using a Master Blueprint 124Configuring a terminal from configuration sheets 125DXR 200 Deployment 126Building a Commissioned network blueprint 127

Using DXR NET to Configure a NMS Unit 127Introduction 127Configuring a NMS Unit 127

Setting the IP Address for a NMS Unit 129Setting the Terminal Frequencies and Transmitter Power 130Setting the NMS Unit Real Time Clock 130Setting up the Route to a PC for a NMS Unit 130Setting Up the Routing Tablefor a NMS Unit 131Setting up the SMA Interfaces 132

Setting up the Radio Link Ports 132Configuring the EOW Interface on a SMA 133

Setting up the Clock Source on a SMA 133Setting Up the SMA Alarm Board 134Setting the Terminal Power Alarm Limits 135Setting the AGC Alarm Limits for a DXR 100 Terminal 136Setting the RSSI Alarm Limits for a DXR 700 Terminal 136Setting the RF Modulation for a DXR 700 Terminal 137Setting the Maximum Correctable Bytes per Second Threshold 137Setting the Terminal Diversity Option 138Mapping an Event to an Action 138Removing an Action from an Event 140Setting the Terminal Line Interface 140

Setting the Terminal Line Interface Type 140Setting the Parameters for an E1 Line Interface 141Setting the Parameters for an E3 Line Interface 142Setting the Parameters for a DS1 Line Interface 143Setting the Parameters for a DS3 Line Interface 144Setting the Parameters for a STM-0 Line Interface 145

Setting Up Alarm Inputs for a DXR 100 Terminal 146Setting Up Alarm Outputs for a DXR 100 Terminal 146Checking for Alarms 147Using Loopbacks to Check a Link 148

Sequence of Operations 150Using Loopbacks to Check the Test Equipment and the Terminal Connection 151Using Loopbacks to Check the Link 151Using Loopbacks To Check the Link Terminals 152

Table of Contents

iv DMC STRATEX NETWORKS


Using FEC Disable while Checking DXR 100 Terminals 153Testing Protection Switching 153Viewing the Constellation Diagram 154Viewing the RSSI Graph for a DXR 700 Terminal 154Viewing AGC Graph for a DXR 100 Terminal 156Viewing Equalizer Graph for a DXR 100 Terminal 156Loading Software to Network Elements 157

Installing System Software on Your PC 157Deleting Old Software Files from a NMS Unit 158Loading Softwareto a Network Element 158Software Compatibility Problems 159Alarm Board and Option Board Compatibility Problems 160

Running Script Files 160Producing Reports 161

Producing Commissioning Reports 161Producing Inventory Reports 162

APPENDIX A: PROBLEMS USING DXR NET 163General 163

Problems Accessing the Network 163Problems Changing the Configuration of a Network Element 163DXR NET Warning Messages 163Contacting DMC Stratex Networks 164

APPENDIX B: ALARMS 165General 165Viewing Alarms 165

General 165DXR 100 Alarms 167

NPR Unit Alarm 167Hardware 167Software 168Maintenance 168Traffic 169Modem 170Radio link 170PSW Alarms 171Hardware 172Software 173Maintenance 173Traffic 174Radio link 174TX Switch 174PRA Alarm 175Hardware 175Software 176Maintenance 176Modem 177Radio link 178NMS Board Alarm 179Hardware 179Software 179Maintenance 179Radio Communication 180

DXR 700 RMA Alarm Descriptions 180RMA Unit Alarm 180Hardware 180

Table of Contents

v DMC STRATEX NETWORKS


Software 181Maintenance 182Modem 182

DXR 700 PMA Alarm Descriptions 183PMA Unit Alarm 183Hardware 183Software 184Maintenance 184Traffic 184Radio link 185TX Switch 185

DXR 700 ODU Alarm Descriptions 186ODU Unit Alarm 186Hardware 186Software 187Maintenance 188Radio Link 188

SMA Alarm Descriptions 189SMA Unit Alarm 189Hardware 190Alarm Board Mark I 190Alarm Board Mark II 191Software 192Maintenance 193Traffic 193Radio Communication 194

200 Series Network Alarms for Terminals on the SMA 195DXR 200 Alarms 196

Hardware 196Software 197Maintenance 198Traffic 198Modem 200Radio Link 201

APPENDIX C: CONSTELLATION DIAGRAMS 203General 203

APPENDIX D: DATA TABLES 206General 206Correctable Bytes per Second Calculation 206Frequency Range and Step Size 207

DXR 100 207Tx Output Power 207

DXR 100 207DXR 700 208

APPENDIX E: USING DXR NET WITH SDM BOARDS 209General 209

SDM Boards 209Cross-connects 210Clocking Hierarchy 210

Commissioning Workspace 211SMA Details 211

Maintenance Workspace 212Alarms 212SMA Details 212

Table of Contents

vi DMC STRATEX NETWORKS


Setting up a Serial Data Circuitwith SDM boards 212Configuring a Low Speed Daughter Board in an Option Page 213Configuring a High Speed Daughter Board in an Option Page 214Configuring a Co-directional Daughter Board in an Option Page 215Setting Up Manual Cross-connects in the Cross-connects Page 216Setting Up the Clocking Hierarchy 216

APPENDIX F: USING DXR NET WITH A LAN 217General 217

Ethernet Connection Requirements 217Ethernet Connection Protocol 217Reasons for Connecting to a DXR NETwork via Ethernet 218

LAN Connections to DXR NETworks 218Direct Router Connection to DXR Equipment 218Direct SMA Connection to LAN 219Connection to SMA via a Router 219

Planning a LAN Connection to a DXR NETwork 220LAN/DXR NETwork Interface 220

Setting Up a Direct Router Connection to DXR Equipment 221Setting up a Direct SMA Connection to a LAN 221

Setting up the SMA LAN Port 221Network Blueprint Changes 223Setting up the Route to the SMA 225

Setting up a SMA Connection to a LAN via a Router 226Selecting the DXR NET Ethernet Interface 226

APPENDIX G: USING DXR NET WITH DXR 200 227General 227Connection Protocol for DXR 200 227DXR 200 Network Addressing Requirements 228

Define Terminal Numbers 228Terminal Number Usage 228

DXR 200 Network Blueprint 229Complex Models 229Limits 229There are three possible ways to deploy a DXR 200 network. 229

Configuration Workspace for DXR 200 Terminal 230Deploying the DXR 200 Network 231Tabbed Pages 231General Setup 232Management Setup 233RF Link Setup 234Deploy the DXR 200 236Assign a DXR 200 to a Managing SMA 237Terminal Management Screen 239

Commissioning Workspace for DXR 200 240Commissioning Workspace for SMA 240Maintenance Workspace for DXR 200 240

View DXR 200 Alarms 241View DXR 200 Terminal Details 242Producing a DXR 200 Inventory Report 243

Maintenance Workspace for SMA 244View SMA Alarms 244SMA Details 245File System 245

APPENDIX H: USING DXR NET WITH DIFFERENT DATA RATES 246

Table of Contents

vii DMC STRATEX NETWORKS


Overview 246General 246Setting up a NMS In/Out Connection 247Using Data Rate Converters 248Using Windows “Dial-Up Networking” with a Data Rate Converter 249

APPENDIX I: DXR SOFTWARE SETS 250Set 30 250Set 29 250Set 24 251Set 21 251100-Set 18 251100-Set 17 251100-Set 15 251100-Set 14 252Set 12 252100-Set 11 252100-Set 10 252Set 6 252Set 5 253Set 4 253Set 2 253

APPENDIX J : DXR NET SOFTWARE COMPATIBILITY TABLE 254

APPENDIX K: ABBREVIATIONS 255

INDEX 257

List of Figures

viii DMC STRATEX NETWORKS


��

Page

FIGURE 1: DXR NET GUI 3FIGURE 2: CONNECTION TO DXR 100 8FIGURE 3: CONNECTION TO DXR 100 WITH NMS BOARD 9FIGURE 4: CONNECTION TO A DXR 700 9FIGURE 5: SMA NMS V.24 CONNECTION 9FIGURE 6: CONNECTION TO A DXR 200 - SMA ETHERNET CONNECTION 10FIGURE 7: BLUEPRINT SEQUENCE OF USE 13FIGURE 8: DXR NET GUI 15FIGURE 9: GENERAL SETUP PAGE – DXR 700 22FIGURE 10: PORT AND EOW SETTINGS PAGE 24FIGURE 11: ROUTING TABLE PAGE – SMA 27FIGURE 12: INTERFACE SETUP PAGE – DXR 700 29FIGURE 13: MODEM/RF LINK SETUP PAGE – DXR 700 32FIGURE 14: ALARM I/O PAGE 39FIGURE 15: ACTION TABLE PAGE 41FIGURE 16: EXTERNAL I/O PAGE 43FIGURE 17: THRESHOLDS PAGE – DXR 700 44FIGURE 18: OPTION PAGE WITH NO BOARD SELECTED 47FIGURE 19: OPTION PAGE WITH LOW SPEED DAUGHTER BOARD SELECTED 48FIGURE 20: OPTION PAGE WITH HIGH SPEED DAUGHTER BOARD SELECTED 50FIGURE 21: OPTION PAGE WITH CO-DIRECTIONAL DAUGHTER BOARD SELECTED 51FIGURE 22: CROSS CONNECT PAGE WITH GRID SHOWN 53FIGURE 23: COMMISSIONING PAGE – DXR 700 55FIGURE 24: ALARMS PAGE 57FIGURE 25: TERMINAL DETAILS PAGE 59FIGURE 26: TERMINAL DETAILS PAGE - DXR 200 65FIGURE 27: SMA DETAILS PAGE 68FIGURE 28: CONTROLS PAGE 70FIGURE 29: CONSTELLATION DIAGRAM – SINGLE VIEW SELECTED 74FIGURE 30: AGC GRAPH 77FIGURE 31: EQUALIZER GRAPH 79FIGURE 32: RSSI PAGE 81FIGURE 33: FILE SYSTEM PAGE 83FIGURE 34: NON-NMS BLUEPRINT EXAMPLE – NETWORK DIAGRAM 103FIGURE 35: NMS BLUEPRINT EXAMPLE – NETWORK DIAGRAM 110FIGURE 36: NMS BLUEPRINT EXAMPLE – ELEMENT NAMES 111FIGURE 37: NMS BLUEPRINT EXAMPLE – NMS ELEMENT IP ADDRESSES 112FIGURE 38: NMS BLUEPRINT EXAMPLE – TOWN SMA ROUTING 113FIGURE 39: NMS BLUEPRINT EXAMPLE – BEACH SMA ROUTING 113FIGURE 40: NMS BLUEPRINT EXAMPLE – TOWN NMS ROUTING 113FIGURE 41: NMS BLUEPRINT EXAMPLE – PORT NMS ROUTING 114FIGURE 42: DXR 700 PMA FRONT PANEL LAYOUT - LOCATION OF CONNECTOR V.24 118FIGURE 43: DXR 100 FRONT PANEL LAYOUT - LOCATION OF CONNECTOR V.24 118FIGURE 44: SMA FRONT PANEL LAYOUT - LOCATION OF SETUP CONNECTOR 119FIGURE 45: LINE FACING LOOPBACK 149FIGURE 46: RADIO FACING LOOPBACK 149FIGURE 47: DIGITAL LOOPBACK 150

List of Figures

ix DMC STRATEX NETWORKS


FIGURE 48: IF LOOPBACK 150FIGURE 49: CONSTELLATION DIAGRAM (DQPSK) 203FIGURE 50: CONSTELLATION DIAGRAM (16 QAM) 204FIGURE 51: CONSTELLATION DIAGRAM (DQPSK) - EXAMPLE 1 204FIGURE 52: CONSTELLATION DIAGRAM (16 QAM) - SIGNAL DEGRADATION EXAMPLE 2 205FIGURE 53: CONSTELLATION DIAGRAM (16 QAM) - SIGNAL DEGRADATION EXAMPLE 3 205FIGURE 54: EXAMPLE SDM DATA CIRCUIT – BLOCK DIAGRAM 209FIGURE 55: SDM SMA TO SMA COMMUNICATION – BLOCK DIAGRAM 210FIGURE 56: SDM CROSS-CONNECT SMA – BLOCK DIAGRAM 210FIGURE 57: SDM SMA CLOCKING HIERARCHY 211FIGURE 58: SMA ETHERNET CONNECTION 218FIGURE 59: DIRECT ROUTER CONNECTION TO DXR EQUIPMENT 218FIGURE 60: DIRECT SMA CONNECTION TO LAN 219FIGURE 61: CONNECTION TO SMA VIA A ROUTER 219FIGURE 62: ADVANCED IP ADDRESS DIALOG BOX 222FIGURE 63: IP ADDRESS TABLE WITH ETHERNET ENTRY 223FIGURE 64: ADDING ROUTE TO PC AT DOS PROMPT 226FIGURE 65: SMA NMS V.24 CONNECTION 228FIGURE 66: DEPLOYMENT OPTION 1 - DIRECT CONNECTION 229FIGURE 67: DEPLOYMENT OPTION 2 - INDIRECT CONNECTION. 230FIGURE 68: DEPLOYMENT OPTION 3 - INTERMEDIATE CONNECTION 230FIGURE 69: GENERAL SETUP PAGE - DXR 200 232FIGURE 70: MANAGEMENT SETUP PAGE - DXR 200 234FIGURE 71: RF LINK SETUP PAGE - DXR 200 235FIGURE 72: PORT AND EOW SETTINGS PAGE - DXR 200 238FIGURE 73: TERMINAL MANAGEMENT PAGE - DXR 200 239FIGURE 74: ALARMS PAGE - DXR 200 241FIGURE 75: TERMINAL DETAILS PAGE - DXR 200 242FIGURE 76: INVENTORY REPORT PAGE - DXR 200 243FIGURE 77: ALARMS PAGE - SMA 244FIGURE 78: DXR NET DIRECT CONNECTION TO NETWORK 247FIGURE 79: DXR NET CONNECTION TO NETWORK VIA CHANNEL 247FIGURE 80: DXR NET CONNECTION TO NETWORK VIA SMA NMS CONNECTION 247FIGURE 81: DXR NET CONNECTION TO NETWORK USING DATA RATE CONVERTERS 248FIGURE 82: DXR NET CONNECTION TO NETWORK USING DIAL-UP NETWORKING 249

About This Manua

1 DMC STRATEX NETWORKS


!��

��This manual describes how to use the DXR NET Network Maintenance Tool (NMT) productwith the following DMC Stratex network elements:

• DXR 100 digital radio terminals (with and without optional NMS board)

• DXR 200 digital radio terminals

• DXR 700 digital radio terminals

• Services Management Adaptor (SMA)

� ��"In this manual, we use the terms Terminal, Element and Unit to describe the hardwareinvolved.

The terms general are used as follows:

The radio terminals and SMA devices in a network are called elements

A radio, such as a DXR 100, DXR 200 or a DXR 700 is a terminal

The SMA and DXR 100 NMS boards are NMS units

One exception to this terminology is the license size count for DXR NET Element manager(described below). This counts only NMS units, but refers to them as elements - a SMA iscounted as two elements, the DXR 100 NMS unit counts as one element. The DXR 200 iscounted as two elements in this case.

#�� $%&'�(DXR NET is a software package supplied by DMC Stratex Networks. It is offered in twolevels:

• Network Maintenance Tool (NMT), for configuring, commissioning, and carrying outdiagnostics on the network elements on a radio network

• Element Manager (EM), for monitoring a DXR radio network

This manual covers how to load DXR NET on your PC, connect the PC to any DXR NETwork,and use NMT to manage the DXR 100, DXR 200 and DXR 700 radio terminals and NMS(Network Management Services) units that make up the network. It also describes how to useDXR NET to configure the SMA to work with the DXR 200 radio in order that ProVision andDXR NET can monitor the DXR 200 network.

About This Manual



Note: For information on the DXR NET Element Manager, refer to the “DXR NET EMInstallation and Operation Manual”, Product Code IOM-NMS-3.

�$%&'�)��*�� DXR NET is supplied as one program, and uses a hardware key and software key to enable theNMT and EM levels. These keys will work with all releases of DXR NET, to enable users toupgrade to a later version, and make use of the level of function they have access to using thekeys.

�� $%&'�+,�You interface with DXR NET via the DXR NET GUI.

The DXR NET GUI is divided into a left-hand and a right-hand pane. The Explorer Pane (theleft-hand pane) shows a hierarchical tree view of the network in the Windows Explorerformat. The Workspace (the right-hand pane) displays one of the following:

• Configuration Workspace. This is used to view and modify the configuration of thenetwork elements

• Commissioning Workspace. This contains basic fault and performance monitoringfeatures useful during the network commissioning

• Maintenance Workspace. This contains detailed fault and performance monitoringfeatures used to carry out network diagnostics

The workspace in Figure 1 is selected:

• From the Workspace Selection window at DXR NET start-up

• by clicking an icon in the DXR NET toolbar

• by clicking the View heading in the DXR NET menu bar, and selecting the workspacefrom the drop-down menu

Note: In the Explorer Pane, the icon for the element directly connected to the PC runningDXR NET is sometimes shown with a “plug” to distinguish it from any other shownelements.

About This Manua



Figure 1: DXR NET GUI

�$%&'�&��

DXR NET NMT requires a hardware key to activate it. If the key is connected to the PC whenDXR NET starts, the extra function provided in NMT will be available. The current level ofDXR NET is shown on the Help- About screen.

�$%&'�� )��DMC Stratex Networks can supply you with a customized version of DXR NET to supportyour language requirements.

Note: This customization is available on request from DMC Stratex Networks who willsupply a quotation.

�$%&'�& �*��-% ��

& �*��-'� � ��"� �

DXR NET operates with DXR 700 terminals, DXR 200 terminals DXR 100 terminals, andSMAs.

About This Manual



& *� �� DXR NET software provides a solution for the management of DXR networks that incorporateDXR 100, DXR 200 and DXR 700 radios.

DXR 200 is incorporated into the DXR NET Network Management environment for the firsttime by treating the SMA as a "proxy" for a DXR 200 network. The purpose of this newfunctionality is to create a SNMP bridge to the DXR 200 so that ProVision and DXR NET canmonitor the DXR 200 radio.

. � ��

Previously, it was necessary to use DXRview or DXRsetup to configure and monitor a 200network. Now, the DXR 200 can be part of a DXR NETwork and DXR NET can be used tomonitor DXR 200 units and display the results in a GUI interface.

Network management facilities incorporated into DXR NET for the DXR 200 series include:

Viewing DXR 200 alarms

Ability to configure DXR 200 terminals and alarms

Ability to monitor DXR 200 terminals and alarms

�� )�� /& �*��-�� )��If you require a Network Management Solution (NMS), and DXR NET is not suitable due tonetwork size, or the presence of other radio types on the network, we recommend ProVisionas your NMS solution. ProVision is a DMC Stratex Networks product providing managementof all DMC radios.

#��0��#��This manual is split-up into the following sections:

• About This Manual (this section). This gives an introduction to the manual, including abrief overview of DXR NET

• Introduction to DXR NET. This contains a description of DXR NET Management Domain,and how you can use the DXR NET to manage a radio link

• Installation of DXR NET. This tells you all you need to know to install DXR NET on yourPC, and how to get started using it

• Using the DXR NET. This contains a description of how you can use DXR NET to designand modify network blueprints, and to configure, commission and maintain networkelements

About This Manua



There are also appendices detailing:

• Alarms

• Constellation Diagrams

• Using DXR NET with SDM boards

• Data Tables

• Abbreviations

• Working with the DXR 200

#��0��& ��1��*To obtain the full benefit of DXR NET features, and to use this document, you must befamiliar with the features and terminology of the Microsoft Windows 95 operating system (orlater). This should include installing software from CD. You must also be familiar with DMCStratex Networks equipment you are planning to use the DXR NET with. Ideally, you shouldhave completed any DMC Stratex Networks training courses for the equipment, and haveaccess to the training and installation manuals for the equipment and any other relevantdocumentation

Note: The DMC Stratex Networks training courses cover the installation, configuration,operation and maintenance of DXR products. Please contact your local DMCStratex Networks representative for details.

About This Manual



2��*�� )��

LINK. An entire link must be made up of either RMA-V or original RMAs.

DXR NET supports the following hardware:

DXR 100

• Protected and non-protected configurations and upgradeables

• Version 1 software with NMS

• Version 2 NMS and non-NMS

Note: Version 1 software without NMS requires DXR Tech software.

DXR 200

• All protection and repeater variants

• Control card V2 only

• Each control card is treated as a separate DXR 200

Note: The SMA works as a bridge to the DXR 200 network, and does not carry DXR 200traffic or signalling. There is no communication between DXR 200s on differentSMA ports.

DXR 700Protected and unprotected

IRU and ODU variants

With and without SMA

Note: Without an SMA, some functions are not available with DXR NET (i.e. softwareloading). For these situations, the engineering tool DXRloader is required.

Introduction to DXR NET



3 ��$%&'�

��This section covers:

• The DXR NET Management Domain (ie, how DXR NET fits in with the other DXRproduct software)

• Using DXR net

• The DXR NET GUI

�� $%&'��

�$%)��*�� " ��

DXR NET is a component of the DXR Software Product suite. The other components of thesuite comprise:

• Terminal Unit Software - the software in the DXR 100, DXR 200 or DXR 700 terminals

• NMS Unit Software – the software in the NMS boards or the SMAs

The way in which DXR NET communicates with a network element depends on the type ofsoftware the element contains.

DXR NET software is a single package that has three levels available. The NMT and EMlevels require a hardware and software key to "unlock" the additional function.

��

At present, you can use DXR NET to connect to the following DXR NETwork elements:

• DXR 100 terminals without the optional NMS Board

• DXR 100 terminals with the optional NMS Board

• DXR 200 terminals via the SMA

• DXR 700 terminals

• SMA (Services Management Adaptor)

The type of connection you select for DXR NET depends on the network element you aretrying to connect to.

Note: For details on the actual physical connections to the elements, and how these affectthe level of access you have to the DXR NETwork, refer to Section 4.




Selecting the DXR NET ConnectionDue to interface differences between Terminal Software and NMS Unit Software, you need totell DXR NET the type of element (terminal or NMS unit) it is going to connect to beforeDXR NET can make the connection. You do this by selecting the DXR NET connection type tomatch the type of network element.

DXR NET does not communicate directly with the DXR 200 elements, but does so via theSMA unit. DXR NET does not provide any configuration of the DXR 200, but simplymonitors the alarm and configuration data.

You can select three types of connection:

• Terminal Connection. Select this type of connection when you are connecting to aterminal only (DXR 100 without NMS board, or a DXR 700), your PC is directlyconnected to the terminal, and DXR NET interfaces with the terminal unit software.

• NMS Connection. Select this type of connection when you are connecting to a NMS unit(DXR 100 with NMS board, or a SMA). Your PC can be either directly connected to theNMS unit, or connected to the unit via a modem. In either case, DXR NET interfaces withthe NMS unit software, which also handles any communications required betweenDXR NET and any other network elements.

• Ethernet. Select this type of connection when you are connecting to a SMA via a LAN.Your PC can be either connected to the SMA via the LAN, or via a router connected tothe LAN. In either case, DXR NET interfaces with the SMA software, which also handlesany communications required between DXR NET and any other network elements.

Note: DXR NET will not allow you to connect to a terminal directly if the terminal is partof a network containing NMS units. Instead, you will have to connect to one of theNMS units.

Connection Protocol for DXR 100 without a NMS BoardWhen the PC running DXR NET is connected to a DXR 100 without a NMS Board, DXR NET

communicates with the terminal unit software using a proprietary protocol. The connection ismade directly to the V.24 port on the terminal front panel.

PC Running DXR NET

DXR 100

DXR NET

Proprietary over V.24

DXRproxy

Internal TCP/IP

Figure 2: Connection to DXR 100

Connection Protocol for DXR 100 with a NMS BoardWhen the PC running DXR NET is connected to a DXR 100 with a NMS board, DXR NET

communicates with the NMS Unit Software using SNMP and TFTP over UDP/IP/PPP/V.24.The connection is made via the V.24 port on the terminal front panel, either directly, or via amodem.




PC Running DXR NET

DXR 100 with NMS

Board

DXR NET

TCP/IP over V.24

Figure 3: Connection to DXR 100 with NMS Board

Connection Protocol for DXR 700When the PC running DXR NET is connected to a DXR 700, DXR NET communicates with theterminal unit software using a proprietary protocol. The connection is made directly to theV.24 port on the terminal front panel.

PC Running DXR NET

DXR 700

DXR NET

Proprietary over V.24

DXRproxy

Internal TCP/IP

Figure 4: Connection to a DXR 700

Connection Protocol for SMAThe PC running DXR NET can connect to a SMA using either the NMS Connection orEthernet. When using a NMS Connection, DXR NET communicates with the SMA UnitSoftware using SNMP and TFTP. The connection is made via the Setup port on the SMAfront panel, either directly, or via a modem. Direct connections are made overUDP/IP/PPP/V.24.

The SMA in turn communicates with the DXR 700 or DXR 200 using proprietary protocol.

PC Running DXR NET

SMA

DXR NET

TCP/IP overV.24

DXR 700

DXR 200

V.24 connector

ProVision

V.24 connector

Figure 5: SMA NMS V.24 Connection

When using an Ethernet connection, DXR NET communicates with the SMA Unit Softwareusing SNMP and TFTP. The connection is made via the LAN port on the SMA front panel.




PC Running DXR NET

SMA

DXR NET

TCP/IP overEthernet

SMA

LAN

Figure 6: Connection to a DXR 200 - SMA Ethernet Connection

Connections to a DXR 200DXR 200 connectivity is achieved using SMAs. The SMA acts as an SNMP proxy for DXR200 networks connected to V.24-A, V.24-B, V.24-C or V.24-D.

A SMA can support up to 4 DXR 200 or DXR 700 terminals directly connected to its V.24ports. Each DXR 200 network can include between 1 and 254 terminals, and the SMA canmanage a total of 500 DXR 200 terminals.

�� $%3445)�!& �*��-�

Scenario A - 1:many relationship

All DXR 200s can talk to each other using theirTerminal Numbers.

SMA

DXR 200

Terminal1

V.24 male connector

DXR 200

Terminal 2

Radio Link

DXR 200

Terminal 3

DTI connection

DXR 200

Terminal 4

Radio Link

DXR NET

ProVision

Appendix F: Using DXR NET with a LAN



Scenario B - 1:1 relationship

Scenario C - Multiple occurrence of 1:1 relationship on a single SMA

SMA

DXR 200

Terminal 1

SMA

DXR 200

Terminal 1

DXR NET

ProVision

The DXR 200 radios are not connected andcannot talk to each other. They can thereforeshare the same Terminal Number. If DXR NET

wishes to talk to the DXR 200s, it must do sovia the SMA.

SMA

DXR 200

Terminal 1

DXR 200

Terminal 2 RdiLikDXR 200

Terminal 3 DTI iDXR 200

Terminal 4 RdiLik

DXR NET

ProVision

DXR SETUP

DXR VIEW

DXR 200

Terminal 1V24l

DXR 200

Terminal 2

DXR 200

Terminal 1 DXR 200

Terminal 2 DXR 200

Terminal 3

DXR 200

Terminal 1

DXR 200

Terminal 2

Multiple DXR 200 networks managed by a single SMA. There is no communicationbetween the DXR 200s via the SMA. Shows the 1 SMA to 4 DXR 200 networkscontaining up to 500 terminals relationship.




�$%)��*�� ) ��DXR software, both terminal software and the DXR NET software, are released in "sets". Aset contains all the software that will work together for a specific release. Each set supersedesthe earlier sets. Software that is not contained in a single set is not supported. Many sets willcontain similar levels of software, as a new set is released if any component in the set isupdated.

Details of released sets are contained in Appendix I: DXR Software Sets.

DXR 200 software is not covered. Refer to the DXR 200 library.

,��$%&'�

�� & �*��-.��

The Network Blueprint concept is the heart of the Software Functional Architecture for anyDXR NETwork. The blueprint is used to specify:

• how a DXR NETwork will be built

• the elements that will make up the network

• the connections between the network elements

The Network Blueprint should be defined before the network is set up, and should bemodified to take into account any changes to the network before the changes are carried out.Any changes carried out “on-site” should be incorporated into the blueprint as soon aspossible. Each blueprint will support one network, displaying the network as a collection ofsites. The sites in turn are represented as a collection of network elements (DXR 100, DXR200 and DXR 700 terminals, SMAs, or NMS boards). It is this hierarchical view which isdisplayed in the Explorer Window of DXR NET GUI. DXR 200 terminals can be mixed in aDXR 100 and DXR 700 network. This functionality is covered in detail in Appendix G,"Using DXR NET with DXR 200.




Using DXR NET, you can edit the configuration data held in the blueprint for:

• the DXR NETwork

• the network sites

• the network elements that make up the network sites

,�� & �*��-.��

The advised sequence for using the network blueprint is as follows:

• the Design blueprint is created at the Network Operations Centre (NOC)

• the installers use the Design blueprint to configure the network elements, saving any“on-site” changes to the blueprint. This now becomes the Field blueprint for that part ofthe network

• all the Field blueprints are sent to the NOC, and used to update the original Designblueprint, which now becomes the Commissioned blueprint

NOC

Design

Blueprint

To Installers

Field

Blueprint

Site On-site

Changes

To NOC Commissioned

Blueprint

Figure 7: Blueprint Sequence of Use

,��$%&'�� & �*��-'� � ��

DXR NET has been developed to assist you to install, configure, commission and maintain theDXR series of radios and their associated network management hardware.

DXR 200 configuration is achieved via DXRsetup.

ConfigurationUsing the DXR NET Configuration Workspace, you can either carry out the configuration ofnetwork elements while connected to the element, or create the configurations in the blueprintfor down-loading to the elements later. You can also read details from existing elements formodifying, saving and re-writing. The details comprise:

• Element details (name, description, type, etc)

• Interface setup details

• Link setup details

• Alarm actions, and

• Performance thresholds




Note: You use DXR NET to configure the SMA to communicate with the DXR 200. Youcannot configure the DXR 200 radio using DXR NET. Configuration must beperformed by a PC running DXRsetup that is directly connected to the DXR 200network.

CommissioningUsing the DXR NET Commissioning Workspace, you can view all the details required tocorrectly install and commission a network. The details comprise:

• Terminal details (name, serial numbers, software versions, etc)

• Parameter details

• Dynamic display of performance levels and alarm indications

The workspace also includes a control panel that allows you to carry out Loopbacks andManual protection switching for test purposes.

There are no controls for DXR 200.

MaintenanceUsing the DXR NET Maintenance Workspace, you can carry out troubleshooting and faultdiagnosis on a network. The features provided include numerical readings and graphicaldisplays of:

• Alarms (similar to that provided in the Commissioning Workspace)

• Constellation diagrams (DXR 100 and DXR 700 only)

• Equalizer graphs (DXR 100 only)

• Receive Signal Strength Indicator (RSSI) graphs, (DXR 100 and DXR 700 only) and

• Signal to Noise Ratio (SNR) (DXR 100 and DXR 700 only)

As in the Commissioning Workspace, the Maintenance Workspace also includes a controlpanel that allows you to carry out Loopbacks and Manual protection switching for testpurposes.

For the DXR 200, the Maintenance Workspace is used to view alarms. Other functions mustbe performed via DXRsetup and DXRview.




)��% �� $%&'��

In accordance with the concept of the Network Blueprint, it is very important to be able tostore and retrieve the data used and produced by DXR NET. You can therefore use DXR NET

to:

• create, save and retrieve Network Blueprints to and from disk

• create and save the configuration data of a network element from a blueprint to disk

• import the configuration data of a network element from disk into a blueprint

Figure 8: DXR NET GUI

�� $%&'�+,�The DXR NET GUI contains the following:

• the Title bar

• the Menu bar

• the Toolbar

• the Explorer Tree pane

• the Workspace pane

• the Status Bar

All the DXR NET functions are carried out using the GUI.




�� .��

The left-hand side of the title bar lists the name of the active network blueprint (ie. theblueprint currently being displayed in the GUI), followed by the application name, eg“TRAINING 2000 – DXR NET”.

Note: If the title bar has “Untitled – DXR NET” on the left-hand side, there is either noactive blueprint, or you have not yet assigned a name to the active blueprint.

The right-hand side of the title bar holds the standard Windows minimise, maximise/restore,and close buttons.

� ��.��

The menu bar contains the following drop-down lists:

• File

• View

• Configuration

• Maintenance

• Tools

• Help

The availability of a drop-down list depends on the level of tool you are using, and the currentstate of DXR NET. The item for a menu that cannot currently be selected is shown “greyed-out” in the menu bar. Each of the available drop-down lists can be displayed by selecting theiritem with the mouse, or by holding down the <Alt> key and typing the underlined letter in themenu name in the toolbar.

Note: The Configuration and Maintenance menus are only available if you have selectedthe corresponding workspace.

FileThe File menu contains listings for the following functions:

• New - allows you to load the template for creating a new network blueprint

• Open - allows you to select and load a previously saved network blueprint

• Import Network Element - allows you to select and load a previously saved networkelement configuration file (.cfg)

• Export Network Element - allows you to save the configuration file of the currentlyselected network element for future reference

• Save - allows you to save the active network blueprint, overwriting any previously savedversion

• Save As - allows you to save the active network blueprint under a different name, thuskeeping any previously saved version

• Exit - allows you to shut down DXR NET, and return to the PC desktop




As well as these functions, the menu also lists the last four network blueprints you accessed,starting with the most recent.

Note: If the blueprint files are in a different directory from your current one, the listednames will contain the relative pathname to the blueprint file.

The listing for an item in the File menu that you cannot currently select is shown “greyed-out”. You can select any available item by using the mouse, or by typing the underlined letteror number in the item listing. In addition, you can select some items by holding down the<Ctrl> key, and the underlined letter. These items have the relevant key-strokes listed aftertheir own listing in the menu bar.

ViewThe View menu contains listings for the following functions:

• Toolbar - allows you to “show” or “hide” DXR NET toolbar

• Commissioning Workspace - allows you to select the Commissioning Workspace fordisplay in DXR NET Workspace Area

• Configuration Workspace - allows you to select the Configuration Workspace for displayin DXR NET Workspace Area

• Maintenance Workspace - allows you to select the Maintenance Workspace for display inDXR NET Workspace Area

You can select any of the items in the View menu using the mouse, or by typing theunderlined letter in the item listing.

Note: Currently selected items are identified by having a tick at the start of their name.

ConfigurationThe Configuration menu contains listings for the following functions:

Note: The Configuration menu is only available if you have selected the Configurationworkspace.

• Add Network Element - allows you to add network elements to the site currently selectedin the active network blueprint. You select the elements from a dialog box that contains alist of possible elements

• Add Site - allows you to add a site to the active network blueprint

• Write Configuration - allows you to upload the configuration and settings of the selectednetwork element in the active network blueprint into the corresponding element of aconnected network

• Read Configuration - allows you to download the configuration and settings of theselected network element in the active network blueprint from the corresponding elementof a connected network

• Load Software - available when there is a NMS unit (SMA or a DXR 100 with a NMSboard) in the blueprint. Allows you to download the unit software to the SMA or NMSboard, or to units under their control. DXR 200 cannot be software loaded through DXRNET.




• IP Address Table - available when there is a NMS unit (SMA or a DXR 100 with a NMSboard) in the blueprint. Contains all the IP addresses of all the NMS units in the blueprint,also used to set up the SMA or NMS IP address.

• Software Table - available when there is a NMS unit (SMA or a DXR 100 with a NMSboard) in the blueprint. Lists the versions of the unit software of all the NMS units and theterminals under their control. For DXR 200 this information can be seen on the TerminalDetails page accessed from the Commissioning or Maintenance workspace.

• Set Real Time Clock - available when a SMA or NMS board is selected in the ExplorerPane. Sets the clock used to synchronize operations in the SMA or NMS board

• Commit Configuration - writes the changes made on the screen to the configuration.

You can select any of the functions listed in the Configuration menu with the mouse, or bytyping the underlined letter in the function listing. The Add Network Element and Add Sitefunctions can be used while working “off-line”. The other functions can only be used whenDXR NET is connected to a network.

Note: DXR NET will display an error message if you attempt to use any functions otherthan Add Network Element or Add Site while your PC is not physically connectedto a network.

You cannot configure a DXR 200 using DXR NET.

MaintenanceThe Maintenance menu contains listings for the following functions:

Note: The Maintenance menu is only available if you have selected the Maintenanceworkspace.

• Load Script File - allows you to display the Execute Script File dialog box. This boxenables you to select and run any previously saved test scripts. See Section 4.

• Advanced Options - allows you to display the Advanced Options dialog box. This boxenables you to select either the single or the multi-carrier views for the monitoringfunctions in the Maintenance workspace. Single means the baseband` signal is monitored,multi-carrier means the individual signal channels are monitored. See the MaintenanceWorkspace description is Section 4 for further details.

You can select any of the functions listed in the Maintenance menu with the mouse, or bytyping the underlined letter in the function listing, but we advise you only to do so under theconditions set out in the above warning.

ToolsThe Tools menu contains listings for the following functions:

• Connect – connects DXR NET to the network element your PC is attached to.

• Disconnect - disconnects DXR NET from the network element your PC is attached to.

• Connection Information – details the network element you are connected to, and the typeof connection you are using.




• Communications Setup - allows you to select the type connection by which your PCcommunicates with any attached network.

You can select any of the functions listed in the Tools menu using the mouse, or by typing theunderlined letter in the function listing.

Note: DXR NET displays an error message if you select the Connect function while yourPC is not connected to a network.

HelpThe Help menu contains listings for the following functions:

• Customer Support - displays a dialog box listing the contact details for the Long HaulDivision of DMC Stratex Networks.

• About DXR NET… - displays a dialog box listing DXR NET software version the PC isrunning, the Product level, and the currently available memory.

You can select either of these items with the mouse, or by typing the underlined letter in theitem name.

��

The toolbar contains the following buttons:

• New Blueprint - allows you to load the template for creating a new network blueprint.

• Open Blueprint - allows you to select an already saved network blueprint.

• Save Blueprint - allows you to save the active network blueprint, either under the currentname (overwriting any previously saved version), or under a different name (keeping anypreviously saved version).

• Commissioning Workspace - allows you to select the Commissioning Workspace fordisplay in the workspace area.

• Configuration Workspace - allows you to select the Configuration Workspace for displayin the workspace area.

• Maintenance Workspace - allows you to select the Maintenance Workspace for display inthe workspace area.

• Commit - allows you to “commit” or save any changes that have been made to theconfiguration of the currently selected network element to the active blueprint.

• Write Configuration - allows you to upload the configuration and settings of the selectednetwork element in the active blueprint into the corresponding element of the networkyour PC is connected to.

• Read Configuration - allows you to download the configuration and settings of theselected network element in the active blueprint from the corresponding element of thenetwork your PC is connected to.

• Connect - connects DXR NET to the network element your PC is attached to.

• Disconnect - disconnects DXR NET from the network element your PC is attached to.




Note: DXR NET will display an error message if you select Connect, Read Configurationor Write Configuration, while your PC is not physically connected to a networkelement.

'/��

The Explorer Tree pane displays a representation of the active network blueprint in ahierarchical tree format.

In this hierarchy, networks are made up of collections of sites, which are in turn made up ofcollections of network elements, ie. DXR 100s, DXR 200s, DXR 700s, or SMAs. The treeview uses the standard Windows format.

You can use the tree view to add, edit and delete site and network elements, and to assign andmodify the network, site and the network element names. When you use it with theWorkspace Pane, you can view and modify the configuration of a network element, monitorthe performance of the element, and view any alarms raised on the element.

The tree hierarchy has three main levels:

• Network level

• Site level

• Network Element level

In addition, the Network Element level can be further sub-divided, with any DXR 700 or anyDXR 200 under SMA control displayed under the controlling SMA, and with any NMSboards displayed under the DXR 100s that contain them.

A DXR 200 network can be deployed under a site or under a SMA.

��

You can view the specification of a radio or NUS (SMA, NMS board) by moving the mouseover the relevant icon in the explorer tree pane, A pop up window displays the followinginformation for the selected element from the network blueprint:

SMA, NMS board - IP address

700 radio - Protected/Non-protected, capacity, modulation

200 radio - Protected/Non-protected, capacity, modulation

100 radio - Protected/Non-protected, capacity

Each DXR 200 on a blueprint represents a single control card (CTL-2). Therefore, the mouseover may not accurately describe the entire DXR 200.

#��-��

The Workspace pane displays the currently selected workspace. The workspaces are used todisplay, modify and monitor the settings of the network element that is currently selected inthe Explorer Tree. The available workspaces are:

• The Configuration Workspace

• The Commissioning Workspace.

• The Maintenance Workspace.




You can select a workspace in one of three ways:

• By clicking the relevant icon in the Workspace Selection window displayed when youstart-up DXR NET.

• By selecting the workspace listing in the View menu.

• By selecting one of the three workspace selection buttons in the toolbar.

The workspaces are described in more detail later in this section.

)��.��

The Status Bar can be divided into three sections:

• Text field. This displays information on the current operations of DXR NET, anddescriptions of tools in the GUI

• Network icon. This indicates both the type and status of the network connection

• SSC compatibility checking. This indicates any incompatibility between what thesoftware version of an NMS unit has been set to in the blueprint, and the versionDXR NET detects in the actual unit

��#��-�� You use the Configuration Workspace to manage the configuration data for DXR NETworkelements. You can create these details from new, read them from a network element, modify,save (to equipment or storage device), and re-write them at any time. The details arecontained in the tabbed pages in the workspace area.

Note: The pages displayed in the Configuration Workspace can vary, depending on thenetwork element selected in the Explorer Tree.

You can only change the terminal name and number for the DXR 200 radio in theconfiguration workspace. For more advanced configuration options, use DXRviewand DXRsetup - two PC based programs that enables users to configure terminals toform a network, change the way a terminal operates or load new software.

As Configuration Workspace can work with saved data, you can work with it offline, ie, youcan create and modify element configuration data while your PC is not actually connected toabelement.

Note: The Configuration Workspace is the only workspace that can be used offline, as thepages in the other workspaces use real-time data generated by the network.

The Configuration Workspace has the following tabbed pages:

• General Setup

• Port and EOW Settings (for SMA only)

• Routing Table (for NMS board and SMA only)

• Interface Setup (for DXR 100 , DXR 200 and DXR 700 terminals)

• Modem/RF Link Setup (for DXR 100, DXR 200 and DXR 700 terminals)

• Alarm IO (for DXR 100 and DXR 200 terminals only)




• Action Tables (for DXR 100 terminal, DXR 200 terminal and DXR 700 terminal andSMA)

• Thresholds (for DXR 100, DXR 200 and DXR 700 terminals)

• External I/O (for SMA only)

• Option 1 and 2 (for SMA only)

• Cross-connects (for SMA only)

• Notifications (for NMS board and SMA only)

+ � ��) ��

The General Setup page is divided into the following sections:

• Terminal Details (for DXR 100, DXR 200 and DXR 700 terminals)

• Board Details (for NMS boards only)

• SMA Details (for SMA only)

• Site Information

Figure 9: General Setup Page – DXR 700

Terminal DetailsThe Terminal Details section has two text fields:

• Type

• Terminal Name




The Type field contains the equipment description of the terminal. This is determined byDXR NET, depending on the unit selected in the Explorer Pane, and you cannot change it.

The Terminal Name field is used to hold the name of assigned to the terminal in the NetworkBlueprint. If you have not assigned a name to the terminal, the field contains the default string“Terminal n” where “n” is an integer relating to the number of radios in the network. You canchange the name by selecting the field with the mouse, and typing in the new name.

Board DetailsThe Board Details section has two text fields:

• Type

• Board Name

The Type field contains a specific description of the board type, usually “DXR 100 NMSBoard”. This information is embedded in DXR NET, and you cannot change it.

The Board Name field is used to hold the name assigned to the board. If you have notassigned a name to the board, the field contains the default string “NMS n” where “n” is aninteger relating to the number of boards in the network. You can change the name by selectingthe field with the mouse, and typing in the new name.

SMA DetailsThe SMA Details section has two text fields:

• Type

• SMA Name

The Type field contains a specific description of the board type, usually “DXR 100 NMSBoard”. It is read from the NMS, and you cannot change it.

The SMA Name field is used to hold the name assigned to the SMA. If you have not assigneda name to the board, the field contains the default string “SMA n” where “n” is an integerrelating to the number of boards in the network. You can change the name by selecting thefield with the mouse, and typing in the new name.

Site InformationThe Site Information section has three text fields:

• Name

• Description

• Contact Details

The Name field is used to hold the name you assigned to the site in the Network Blueprint. Ifyou have not assigned a name, the field is assigned the default string “Site n” where “n” is aninteger relating to the number of radios in the network.

The Description field is used to hold any details of the site you feel should be noted. If you donot input any details, the field is left blank.

The Contact Details field is used to hold the details of the person responsible for the site. Ifyou do not input any details, the field is left blank.




Normally, you would have set the details in these fields when you created the networkblueprint. However, you can change the details by selecting the field with the mouse, andtyping in the new details.

Note: You can only change the Description and Contact Details fields when the Site iconis selected in the Explorer Tree, not the terminal icon.

��'�#) ��

The Port and EOW Settings page is divided into the following sections:

• Local Terminals

• NMS In Connected

• NMS Out Connected

• Baud Rates

• Engineering Order Wire (EOW)

• Clock SourcesLocal Terminals

Figure 10: Port and EOW Settings Page

This contains four list boxes, designated Port A to Port D respectively, one for each for eachof the four possible DXR 200 and DXR 700 radio links the SMA can support. The list boxescontain the name of the local terminal connected to this port on the SMA.




NMS In ConnectedThis has two list boxes, designated Site and NMS Unit respectively, used to define whichremote NMS units the NMS In port on the SMA communicates with. The Site list boxcontains the name of the remote site. The NMS Unit list box contains the name of the actualNMS unit at the remote site.

NMS Out ConnectedThis has two list boxes (designated Site and NMS Unit respectively) that are used to definethe remote NMS units the NMS Out port on the SMA communicates with. The Site list boxcontains the name of the remote site. The NMS Unit list box contains the name of the actualNMS unit at the remote site.

Baud RatesThis has two list boxes (designated NMS In and NMS Out respectively) that are used to setthe baud rates the SMA uses to communicate over the NMS In and NMS Out ports. Forfurther details, refer to Appendix F: Using DXR NET with Different Data Rates.

Engineering Order Wire (EOW)The SMA EOW provides an “all-station” calling facility. This has two uses:

• ring-tones can be sent over the network to check IP routing

• messages can be broadcast over the network

The SMA uses DXR 700 auxiliary or overhead channel to carry the EOW signals. The ring-tones are generated by pressing the push-button on the SMA front panel, and are output eithervia the EOW handset or the speaker in the SMA. Messages are broadcast by inserting theEOW handset into the jack on the SMA front panel, and holding down the push-button. Themessages can then be picked up by any other handsets.

The Engineering Order Wire (EOW) section has four fields:

• Ear Piece Volume

• PCM Coding Law

• Ring Modes

• Transmit High Pass Filter

The Ear Piece Volume field is used to set the volume of the earpiece in the EOW handset.Select the volume from the drop-down list displayed when you click on the field with themouse. You can choose between Normal or Loud.

The PCM Coding field is used to select the coding law used to transmit voice over the EOWinterface. The coding law governs the relationship between the analog voice signal and thedigital pulses used to transmit the signal over the network. You select the law from the drop-down list displayed when you click on the field with the mouse. You can choose betweenµLaw or A-law.

Note: All the SMAs on your network should be set to the same coding law, and this shouldmatch the law used by your country.

The Ring Modes field is used to set the type of ringing tone generated by the SMA when itringing signals over the EOW interface. Select the tone from the drop-down list displayedwhen you click on the field with the mouse. You can choose between the tone for a DXR 100,a DXR 200, or a DXR 700.




The Transmit High Pass Filter field is used to select whether the analog voice signal from theEOW handset is passed through a high pass filter or not. Set the option you require byclicking on the check box field with the mouse. The option is selected when there is a tick inthe check box.

Clock SourcesThe Clock Sources section has two fields:

• Primary

• Secondary

To ensure its components are synchronized, the SMA is provided with two possible clocksignals, Primary and Secondary. The SMA switches to the Secondary clock signal if thePrimary fails. Either signal can be generated internally, or input to the SMA via a port on thefront panel.

The Primary and Secondary fields are used to select the source for the associated clock signal.Select the option you require from the drop-down list displayed when you click on the fieldwith the mouse. The choices are:

Free-running (generated internally),

One of the four AUX ports (AUX A to D),

The NMS In port, the NMS Out port, or

one of Option 1 or Option 2, i.e. input via one of the optional daughter boards.

Note: For either of the last two choices to be valid, the relevant slot in the SMA must beoccupied by an appropriate board.




%��

The Routing Table fields are contained within a three-column table for a NMS board, and afour-column table for a SMA. The columns are:

• Destination IP Address

• Mask IP Address

• Interface

• Gateway/Next Hop (SMA only)

Figure 11: Routing Table Page – SMA

You use the Routing Table to set-up the IP routes by which the NMS unit communicates withother IP devices on the network, including any PC attached to the SMA Setup port. Each rowof the table defines one IP route. You create a new row by pressing the Insert key. For theNMS unit to communicate with another IP device, you must set up a valid route in the IPAddress table.

Note: Each IP device on the network must have a unique IP address.

Destination IP AddressThe Destination IP address is the IP address on the network of the device you wish the NMSunit to communicate with. You input the required address by double-clicking the next emptyfield in the Destination IP address column, and typing in the address.




Mask IP AddressTo save you having to define a route for every single IP address, you can use a subnet mask toroute a range of IP addresses to a single destination. A subnet mask allows you to definewhich part of the IP address you want to match for routing. The Mask IP address allows youto set the subnet mask for the range of IP addresses you want the NMS unit to use the samedefined route for. You input the required subnet mask by selecting the next empty field in theMask IP address column, and typing in the mask.

InterfaceThe Interface is the port that the NMS unit uses to send messages to the given IP address. Youselect the port from the drop-down list displayed when you double click on the field.

Gateway/Next HopThe SMA routing table also has a “Gateway/Next Hop” field, which should be left at 0.0.0.0unless the interface is Ethernet, and the destination host or network is indirectly connected tothe SMA via a router or gateway. The next-hop address is then the address of the router. Inputthe required address by double-clicking the next empty field in the Destination IP addresscolumn, and typing in the address.

�� ) ��

The Interface Setup page is divided into the following sections:

• Interface

• Tributary

• Wayside Tributary (DXR 700 terminal only)

InterfaceDepending on the type of line interface you select, the Interface section has either one or twodrop-down list fields. The fields are:

• Interface Type (always present)

• Interface Capacity (present if selected interface type uses more than one signal channel)




Figure 12: Interface Setup Page – DXR 700

SETTING THE INTERFACE TYPE. The terminal interface type is set by the terminalhardware. You should therefore only select an interface type that matches the terminalhardware.

The Interface Type drop-down list allows you to choose the terminal line interface. Theavailable interface types are shown in the following table.

Note: At present, the DXR 100 only supports E1 and DS1.

��

'� Default setting. Data rate 2.048 Mbs. Can carry up to thirtyvoice channels, with two control and synchronizationchannels.

'� Supported by DXR 700 only. Data rate 34.368 Mbs.Equivalent to 16 E1 circuits.

&5� Data rate 1.544 Mbs. Can carry up to twenty-four voicechannels.

&5� Supported by DXR 700 only. Data rate 44.736 Mbs. Cancarry up to 672 64 kbs channels, each channel capable ofcarrying one analog telephone conversation (after analog-to-digital conversion). Equivalent to 28 DS1 circuits.

56/�� Supported by DXR 700 only. Data rate 51.840 Mbs.




SETTING THE INTERFACE CAPACITY. The terminal interface capacity is set by theterminal hardware. You should therefore only select an interface capacity that matches theterminal hardware.

The Interface Capacity drop-down list is only displayed when you have selected a terminalline interface that can support more than one signal channel. The following table shows thesupported interface capacities.

Note 1: At present, the DXR 100 only supports 1xE1, 2xE1, 4xE1, 1xDS1, 2xDS1 and4xDS1.

Note 2: STM-0 does not have selectable interface capacities.

��

'� Both terminals support 1xE1, 2xE1, and 4xE1. DXR 700 alsosupports 8xE1 and 16xE1.

'� DXR 700 supports 1xE3 and 2xE3.

&5� Both terminals support 1xDS1, 2xDS1, and 4xDS1.DXR 700 also supports 8xDS1 and 16xDS1.

&5� DXR 700 supports 1xDS3.

TributaryThe Tributary section is only active when you have selected a terminal line interface that cansupport more than one channel. The section normally contains a table, and sometimes a listbox for selecting Line Encoding.




The number of columns in the table depends on the Interface Type, and the number of rowsdepends on the Interface Capacity. The columns are:

• Tributary

• Line Impedance (E1 interface type)

• Rx Sensitivity (E3, DS3, or STM-0 interface type)

• Tx Level Boost (DS3 or STM-0 interface type)

• Line Build-out (DS1 interface type)

• Equalizer Bypass (E3, DS3 or STM-0 interface type)

• Commissioned

There is also a Line Encoding list box available with the DS1 interface type.

The Tributary column is used to identify the tributary whose configuration is defined in theother table columns. The column entries are “Trib n” where “n” is the number of the tributary.The range of “n” depends on the capacity selected. The fields are input automatically, and youwill not be able to change them.

SETTING THE LINE IMPEDANCE. The line impedance depends on the cabling attachedto the line interface of the terminal. Therefore, any changes you make to the line impedancemust reflect the impedance of the cabling attached to your terminal line interface.

The Line Impedance column is used to set the impedance of the tributary to either 120 ohm(default) or 75 ohm. You select the line impedance from the drop-down list displayed whenyou double click on the field.

SETTING THE LINE BUILD-OUT. The Line Build-out depends upon the cabling attachedto the line interface of the terminal. Therefore, any changes you make to the line impedancein the software must reflect the cabling attached to your terminal line interface.

The Line Build-out column is used to set the line build-out. Select the line build-out from thedrop-down list displayed when you double click on the field. The values range from 0-133 ft(default), 133-266 ft, 266-399 ft, 399-533 ft, 533-655 ft.

The Rx Sensitivity column is used to set the sensitivity of the terminal receiver to Low,Medium (default) or High. Select one of these sensitivities from the drop-down list displayedby when you double-click on the field.

The Tx Level Boost column is used to increase the amplitude of signals transmitted from theline interface. Enable Tx level boost by selecting True (enabled) or False (disabled) in thecolumn.

The Equalizer Bypass column is used to take the equalizer circuitry on the line interface outof the signal path. Enable equalizer bypass by selecting True (enabled) or False (disabled) inthe column.

The Commissioned column is used to enable the tributary to carry traffic. It can be either True(tributary can carry traffic) or False (tributary cannot carry traffic). Select these from thedrop-down list displayed when you double click on the field.

Note: The commissioned state of a tributary affects the alarms raised, as traffic on anuncommissioned tributary is an alarm condition (Uncommissioned Traffic. SeeAppendix A, NPR Unit Alarm, Traffic).




The Line Encoding list box is available when the DS1 interface type is selected. It allows youto select the type of coding used by DS1. You select the coding from the list displayed whenyou click on the arrow in the box and selecting from the displayed menu.

Wayside TributaryThe Wayside Tributary section is available with DXR 700 terminals. The Wayside Tributaryis an extra control channel supported for the 16xE1 or 16xDS1 interface capacities, or the E3,DS3, or STM-0 interface types. The section contains either a table for configuring thetributary, or “No Wayside Available” if you selected an interface capacity or type that doesnot support the tributary.

The table has two columns, each of which corresponds to columns in the Tributary sectiontable. The Wayside column corresponds to the Tributary column, and is followed by either aLine Impedance column (16xE1, E3, or STM-0), or a Line Build-Out column (16xDS1 orDS3). The function of these columns is the same as for those described for the main table.

�� 6%��-) ��

The appearance of this page depends on configuration of the terminal. If the terminal is anunprotected terminal, the Radio Settings sub-section appears at the top of the page. If theterminal is a protected terminal, the Protected & Diversity Options sub-section appears at thetop of the page, with the Radio sub-section directly underneath it.

Figure 13: Modem/RF Link Setup Page – DXR 700

The RF Link and Link Parameters section is divided into the following sub-sections:

• Protected & Diversity Options (protected terminals only)

• Radio Settings/Radio (title dependent upon terminal configuration)




• Remote Terminal

Protected & Diversity OptionsThe Protected & Diversity Options sub-section will only be displayed for protected terminals.It contains the following fields:

• Protected

• Space Diversity

• Frequency Diversity

Protected and Non-protectedMicrowave terminals are available in non-protected and protected configurations. The basicunprotected DXR 700 radio terminal comprises three functional modules. These are theProtection Multiplex Adaptor (PMA) and the Radio Modem Adaptor (RMA), both locatedindoors, and the RF Outdoor Unit (ODU). Typically, the Services Management Adaptor(SMA) is also installed. The figure below displays an unprotected terminal block diagram.

ODUThe ODU consists of a light-weight, compact, integrated RF electronics enclosure attached toan antenna. The millimetre wave technology employed permits the complete integration of allmillimetre wave functions into a single, small, rugged subassembly.This technology yields a significant increase in reliability when compared to conventionalapproaches. Typically, the ODU is installed outdoors on tower or rooftop.

IDUThe IDU is an indoor mounted assembly that contains all of the baseband electronicsincluding the functions of line interface, digital multiplexing, modulation and frequencygeneration. It also includes the alarm and diagnostic, service channel and networkmanagement interfaces. Furthermore, within the IDU is the capability to set the systemcapacity, frequency synthesizer and power output of the radio; NO access to the Outdoor Unitis required.




IRUThe IRU contains the same light-weight, compact integrated RF electronics as the ODU but ispackaged for fitting in an indoor rack. You would typically use an IRU where the output ofthe IRU goes to the antenna via a waveguide. This gives you the flexibility of mounting all thecomponents indoors. It also enables hot standby, where required.

Protection OptionsThere are a number of protection options available for the DXR 700 range of products. Theseoptions use two RMAs and two RF Units to provide 100% redundancy of the RF and modemfunctions. The same RF Units and RMA modules are used in both protected and unprotectedsystems, minimizing spares requirements.

In a typical protected configuration, the transmit RF signals are combined using a powersplitter/combiner into a single antenna, and the receive RF signals are split with the samesplitter/combiner to the two receivers. In this configuration, the two RF Units can be on thesame frequency with one of the transmitters being disabled in software, or both transmittersmay be operated simultaneously on different frequencies for frequency diversity operation.

Upgrading an unprotected system to a protected one is as simple as adding additional RMA,ODU and power/splitter combiner and re-configuring the terminal for protected operation.

Both receive paths are continuously monitored for receive signal integrity while the protectionswitch selects the highest quality data. FEC controlled block selection enables errorlessreceive path switching.




A further configuration is available with two RF Units connected to two separate antennas toprovide space diversity or frequency diversity. In this configuration, the system gain is highersince it does not have the additional loss of the powersplitter/combiner.

Space DiversitySpace diversity is usually applied to overcome the effects of multipath fading. With spacediversity only one frequency pair is used. Both transmitters operate at the same time usingdifferent antennas. Only one transmitter needs to be operating, however, in order to haveequipment protection as well as path protection. The transmit branching is often the same asthe hot standby arrangement.

Frequency DiversityIn some cases, when fading activity occurs over the hop, the effect on one frequency isdifferent from an adjacent frequency due to the electrical path differential between the two.Therefore, to meet specified performance objectives in a route, a protection channel is usedduring fading the traffic channel, traffic loss can be avoided. With frequency diversity, tworadios are transmitting to the same antenna using different frequencies. The greater thedifference between the two frequencies, the better the performance improvement againstfading.

Hot StandbyIn a hotstandby arrangement both sets of RF (main and standby) are operational the wholetime. This means that there is a guaranteed backup transmitter in the event of failure. Onlyone frequency pair is used for the two-radio system. It is thus not possible to transmit bothsignals simultaneously. Both transmitters actually transmit a signal. But only one is switchedonto the antenna. The other signal is transmitted to a dummy load.

In the event of system failure, DXR NET will report a fault and switch transmission to theback-up RF, guaranteeing a secure system.

DXR NET supports the protected IRU variant when configuring hot or warm standby for theprotected DXR 700 radio.




Monitored HotstandbyMonitored hot standby (MHSB) is offered with all frequency bands of protected system asstandard. Switching on receive is fully automatic and is based on detection of uncorrectableerrors by the forward error correction (FEC) circuit. Manual mode may be selected to allowone protected radio to be replaced while maintaining normal operation via the other radio.

The protected option can be configured to switch from the main to the standby transmitter byselecting any one of the following alarm conditions:

Low transmitter forward power

Temperature too high

Local oscillator out of lock

Major alarm (triggered by failure of any sub-module)

Manual switch-over commands for testing and maintenance

Note: Transmitter switches are disruptive to traffic only in the cases listed above. They arenever disruptive due to path performance.

SETTING THE TERMINAL DIVERSITY OPTION. The diversity option you can select isdependent on the terminal hardware, and you must not make any changes that do not reflectthe terminal hardware.

Note 1: If you select either of the Space or Frequency Diversity options, you will have to setthe terminal power and AGC alarm limits for each radio. If you select the FrequencyDiversity option, you will also have to set the frequencies and transmitter power foreach radio.

Note 2: You can only select one of the three configurations at any one time.

Note 3: The DXR 200 has no access to AGC data.

You select a configuration option by clicking on the appropriate radio button with the mouse.If you select Frequency Diversity, the additional fields are displayed in the following Radiosub-section for Radio A and Radio B.

Radio SettingsThe Radio Settings sub-section contain the following fields:

• Tx Frequency (MHz)

• Rx Frequency (MHz)

• Tx Power (dBm)

• Preferred A




Preferred TransmitterPreferred TX gives the user the option of having a protected radio use the preferredtransmitter whenever possible, unless there is a hardware alarm on the preferred transmitter.

This option may be used if there is an un-equal loss splitter, or a space diversity configurationwith unequal gain. The preferred transmitter is always TX A.

If there are no outstanding alarms on TX A, the PMA will attempt to switch to TX A. In thecase of switch-causing alarms on TX B, the radio must wait the minimum guard time (5 secs)before it can switch back to TX B, and once it does, the guard time will be doubled. Theradio will not switch back to TX A until the guard time has elapsed. If there are no alarms onTX A at this time, it will switch to TX A. After successfully running for twice the currentguard time on TX A, the guard time is halved.

The minimum guard time is 5 seconds. The switch from A to B always has the minimumguard time. The maximum guard time is around 20,000 seconds, which is 5 ½ hours.

It is not recommended to use Preferred Transmitter unless the path engineering requires it,due to the possibility if increased TX switches.

Note: Preferred transmitter is only supported by DXR 700 system software V2 and above.

SETTING THE TERMINAL FREQUENCIES AND TRANSMITTER RF POWER. Thefrequency range and transmitter power of your terminal depends on the duplexer of theterminal. Therefore, any changes you make to the frequency parameters must reflect theduplexer tuning, and any changes to the output power must reflect the capacity of theduplexer.

You can change the values in any of these fields using the up/down arrows. The Tx Power canbe varied in 0.1 dB steps from +10 dBm to the maximum for the terminal.

Appendix D shows the following relationships for a DXR 100 terminal:

The relationship between the modulation, the capacity, and the maximum transmitter poweroutput at the Tx port. .

The relationship between the frequency range and the frequency step size.

Appendix D shows the following relationships for a DXR 700 terminal::

The relationship between the modulation, the capacity, and the maximum transmitter poweroutput at the Tx port. .

The relationship between the frequency range and the frequency step size,




Note: If you make any changes to the frequency values, these will be reflected in theremote terminal settings only after you have committed the changes, and if theremote terminal is selected in the Remote Terminal field (see below).

Remote TerminalThe Remote Terminal sub-section only becomes active when you select the check box in thetop left-hand corner, and a remote terminal has been selected in the Remote Terminal field.

Note: You can only select a remote terminal of the same type and configuration as thelocal terminal.

This allows DXR NET to check the Tx/Rx pairs for the link, and to move between the pairs ateither end of the link using the “Right-click, Go to” option. It contains the following fields:

• Site Name

• Terminal Name

• Tx Frequency (MHz)

• Rx Frequency (MHz)

You can select the Site Name and Terminal Name for the remote terminal from the drop-downlist displayed when you click on the down arrow in the relevant field. You cannot select orchange the values in the frequency fields. However, if you have made changes to the relevantsettings in the Radio Settings sub-section, the values will be updated in line with the valuesyou have selected for the local terminal after you have committed the changes.

Note 1: Any changes you make to the frequency values will be reflected in the remoteterminal settings after you have committed the changes.

Note 2: If Frequency Diversity is selected in the Protected & Diversity Options sub-section,there are Tx Frequency (MHz) and Rx Frequency (MHz) fields for Radio A andRadio B. If the configuration is not selected, there are only fields for one radio.




Modem ParametersThe Modem Parameters section is only supported by the DXR 700. It contains the Modulationfield, which you use to set the type of modulation used by the terminal modem. You select themodulation type from the drop-down list displayed when you double click on the field. Thesupported types are 16 QAM (default), 32 QAM, 64 QAM or DQPSK.

SETTING THE MODULATION. The modem modulation you can select is dependent onthe modem in the DXR 700 RMA. Any changes you make must match the modulation typeof the modem of the RMA that is installed.

!��

Figure 14: Alarm I/O PageThe Alarm IO page is only supported by the DXR 100. The Parameters section in the page isdivided into the following sub-sections:

• Alarm Inputs

• Alarm Outputs

The DXR 100 can have up to two alarm inputs or outputs. An alarm input is an external signalthat can be fed into the terminal, eg site door open, where it is used to generate an event in theAction Table (see Action Table). This enables the alarms at remote sites to be monitored overthe radio link. The alarm inputs are fed into the terminal via DB15 connector on the DXR 100front panel, and are set-up in the Alarm Inputs sub-section Alarm IO page.




An alarm output is a signal fed out from the terminal, eg to operate a buzzer, in response tothe occurrence of an event listed in the Action Table.

Alarm InputsThe Alarm Inputs sub-section contain the following fields:

• Input 1 Identifier

• Input 2 Identifier

• Normal State

There is one normal state field for each of the identifier fields. This field determines whetherthe alarm event is triggered when input signal is present or absent. The field is set to thenormal condition of the input, ie. The input state that indicates no alarm is present.

You can assign names to the alarm inputs by selecting the relevant field and typing in thename. After you have committed the changes, the names will appear in the Event Tree in theAction Table page.

You select “No Current” or “Current” from the drop-down list displayed when you click onthe Normal State field.

Alarm OutputsThe Alarm Outputs sub-section contain the following fields:

• Output 1 Identifier

• Output 2 Identifier

• Normal State

• Rate

There is a Normal State field and a Rate field for each of the identifier fields. The NormalState field determines whether the normal (ie, no alarm is present) condition is open-circuit orclosed-circuit. You can select either “Open” or “Closed” from the drop-down list displayedwhen you click-on the field. The Rate field determines the maximum number of changes theassociated alarm signal can make per second. You can select a rate from 0 to 20 using theup/down arrows in the field.

Note: Selecting 0 will mean that no alarms are output at all.

You can assign names to the alarm outputs by selecting the relevant field and typing in thename. After you have committed the changes, this is the name that will be displayed in theAction Table.




!��

You use the Action Table page to select the actions you wish the terminal or SMA to takewhen a particular event occurs. This is known as mapping an action to an event. The ActionTable page is divided into the following three panes:

• Events

• Mapped Actions

• Inherited Actions

Figure 15: Action Table Page

EventsThe Events pane lists the events that you can set an action for. The events are listed in theWindows Explorer tree format.

You set or “map” an action to an event by selecting the event, and then clicking on the EditActions button. This displays the Edit Actions window with drop-down lists of availablelocations (the network elements where the action can be raised) and available actions. Youselect the location where the action will occur, and the action from the lists.

Note 1: The events you can set actions for are all alarm conditions.

Note 2: DXR NET can see all alarm conditions not just the alarms you have set actions for.

Note 3: Actions enabled on remote elements are followed by the name of the element inparenthesis.




Note 4: A SMA can have up to thirty remote actions.

Mapped ActionsThe Mapped Actions pane lists any actions that you have mapped to the alarm presentlyselected in the Events pane. You can also remove an action from an alarm by selecting theaction in the Mapped Actions pane, then clicking on the Delete button

Inherited ActionsThe Inherited Actions pane lists any actions mapped to an alarm higher up in the treehierarchy than the alarm you have currently selected.

Note: An inherited action must be deleted by selecting the alarm causing the action.

'/� ��6�5)�!

The External I/O page is only supported by the SMA. The SMA can have one of the followingalarm boards:

• Alarm Board Mk I

• Alarm Board Mk II

The alarms for these boards are available on the DB15 connector on the SMA front panel.The alarm states are configured both by software, and by switches and links on the boards.Each board can have up to six alarm input and output pairs, handling a total of twelve alarmsignals.

Note: DXR NET will only write the configuration to an alarm board if it finds that theboard type in the SMA matches the type set in the blueprint.

The External I/O page contains the Alarm Board I/O Channel Settings section. This has a fivecolumn table displaying the following fields:

• Channel

• Identifier

• Type

• Electrical State

• Rate




Figure 16: External I/O Page

ChannelThe Channel field displays the channel designation. This is the channel number, followed by“a” or “b” to indicate which of the channel pairs the signal is assigned to.

IdentifierThe Identifier field displays the name of the signal. You assign a name to the signal bydouble-clicking on the field with the mouse, and typing the name in.

TypeThe Type field defines the signal is an input or an output. In the MK I board, you can assign astate to the signal by double-clicking on the field with the mouse, and selecting the state fromthe drop-down list. The signal state is “hard-coded”, ie, not selectable, in the Mark II board.

Electrical StateThe Electrical State field entry defines the electrical state of the channel when the signal ispresent. You assign a state to the signal by double-clicking on the field with the mouse, andselecting the state from the drop-down list. You can select between no current and current.

Note: For either signal, changing from the default setting requires you to alter switchsettings in the SMA, and also links in the SMA for output signal changes.

RateThe Rate field defines the maximum number of changes to the alarm signal that the SMA candetect per second. It can vary from zero (no alarms detected) to a maximum of twenty. Thisfield is used to prevent a recurring alarm swamping the alarm monitoring function, preventingother alarms on the system being detected.




You select the rate by double-clicking on the Rate field, and typing in the value.

Note: You must select a number within the given range, and you must select an integervalue.

��

The Thresholds page is divided into the following sections:

• General

• Transmit Path

• Receive Path

Figure 17: Thresholds Page – DXR 700

GeneralThe General section contains the Correctable Bytes per Second field. This field is used to setthe number of correctable bytes that can be received over the radio link before triggering theCorrectable Error Limit alarm (see Appendix A for details). If the number exceeds the setlimit, the alarm is triggered. You can set this number by using the up/down arrows in the field.You can also select the default value by clicking on the Defaults button.The following tablesshow recommended values of Correctable Bytes per Second for each radio type and capacityto obtain an error rate of 1 x 10-6.




DXR 100 Radio Capacity Link Data Rate

Mbit/S Bit Error Rate

1E-6 4 x E1 9.728 10 2 x E1 4.864 5 1 x E1 2.432 2

4 x DS1 7.926 8 2 x DS1 3.648 4 1 x DS1 1.824 2

DXR 700 Radio Capacity Link Data Rate

Mbit/S Bit Error Rate

1E-6 1 x STM-0 60.441 60

2 x E3 79.836 80 1 x E3 40.769 41

16 x E1 40.762 41 8 x E1 19.747 20 4 x E1 9.792 10 2 x E1 5.01 5

1 x DS3 51.875 52

16 x DS1 30.731 31 8 x DS1 14.887 15 4 x DS1 7.382 7 2 x DS1 3.867 4

Note: The correctable bit error rate is not a true BER, as multiple bit errors per byte are

not detected. The correction algorithms employed allow a significant error rate to bemasked from the customer traffic.




Transmit PathThe Transmit Path section contains the fields used to set the limits for the following:

• Forward Power (dBm)

• Reflected Power (dBm)

The appearance of this page depends on whether the terminal selected in the Explorer Paneuses frequency diversity, and also the terminal type. Terminals using frequency diversity havefields for Radio A and Radio B.

The Forward Power fields, Low limit and High limit, are used to set the values of RF outputpower from the terminal transmitter that will trigger the Forward Power alarm (see AppendixE for details). Set the limits by either selecting the fields and typing in the values, or by usingthe up/down arrows in the fields. You can set the fields to their default values by clicking theDefaults button.

The Reflected Power is used to set the value of the RF power being reflected back to theterminal from the antenna that will trigger the Reflected Power alarm (see Appendix E fordetails). Set the maximum acceptable value by either selecting the field and typing in thevalue you require, or by using the up/down arrow in the field. You can set the fields to theirdefault values by clicking the Defaults button.

Receive PathThe appearance of this page depends on the terminal type.

For a DXR 100 terminal, the page contains the fields used to set the limits for the AutomaticGain Control (AGC) alarm. The AGC is a voltage applied in the DXR 100 circuitry thatcontrols the gain applied to the received RF signal to ensure that the information it carries canbe recovered. The two fields, Low limit and High limit, set the range over which it can varywithout triggering the alarm. Set the values by either selecting the field and typing in thevalue you require, or by using the up/down arrows in the fields. You can set the fields to theirdefault values by clicking the Defaults button.

The DXR 200 radio has no access to AGC data.

For a DXR 700 terminal, the page contains the fields used to set the Received Signal StrengthIndicator (RSSI) limits for the Rx Path Warning alarm. Refer to Appendix A for details of thealarms. The RSSI is the strength of the received RF signal in dBm. The two fields, Low limitand High limit, set the range over which it can vary without triggering the alarm. Set thevalues by either selecting the field and typing in the value you require, or by using theup/down arrows in the fields. You can set the fields to their default values by clicking theDefaults button.

The DXR 100 and 200 radios have no access to RSSI data.

��

The Option 1 and Option 2 pages are only supported by the SMA. The Option pages are usedto configure any SDM board fitted into the corresponding option slot of the SMA. Theappearance of the pages depends on the type of board that has been fitted to the slot.

Note: In the following, “n” represents either “1” or “2”.




Figure 18: Option page with no board selected

Low Speed Daughter BoardWhen a Low Speed Daughter Board is fitted to an option slot, the associated option page hasthe following sections:

• Option Slot n (n depends on which slot the board is inserted into)

• Circuit 1

• Circuit 2




Figure 19: Option page with Low Speed Daughter Board selectedThe Option Slot n section has the following fields:

• Option Board Type. Use this field to select the type of board inserted into the slot. Thedefault is “Not Installed”. In this case, select “Low Speed Daughter Board” from the drop-down menu displayed by clicking on the arrow in the right hand side of the field.

• Cross connect to. Use this field to select the AUX port on the SMA the board uses tocommunicate with the SDM board at the other end of the circuit. This in turn selects theDXR 700 terminal by which the board data is sent and received. The default is “AUX A”.Select any one of the four AUX ports on the SMA from the drop-down menu displayed byclicking on the arrow in the right-hand side of the field.

• Channel. Use this field to select the first channel used for the board data on the AUXchannel. Default is “2”. Select either “2” or “3” from the drop-down menu displayed byclicking on the arrow in the right-hand side of the field.

• Channels required. This field shows the number of channels on the AUX channel theboard requires to transmit and receive data. It is generated automatically, and depends onthe board you selected and the values you input to the Data Rate fields in the Circuitsections.

• Option Board Active. Use this checkbox field to enable all other fields in the section. Ifthe checkbox is not selected (default), ie, not ticked, all other fields will be greyed out anddisabled.

Note: When an Option Board is inactive, the SMA will expect the board to be present, but will notallocate any bandwidth to it. In this case, the board will not carry any data.




The Circuit sections contain the following fields:

• Mode. You use this field to select the mode of operation of the board, either “Async” or“Sync”. Select the mode from the drop-down menu displayed by clicking on the arrow inthe right-hand side of the field.

Note: Your selection in this field determines the other fields displayed in the Circuitsection.

• Data Rate. Use this field to select the speed at which the board transmits and receivesdata. The values you select are dependent on the selection you made in the Mode field. Ifyou selected “Async” Mode, you can select one of 150 (default), 300, 600, 1200, 2400,4800, 9600, 14400, or 19200 bits per second. If you selected “Sync” Mode, you can selectone of 2400 (default), 3600, 4800, 7200 or 9600 bits per second. In both cases, you selectthe rate from the drop-down menu displayed when you click on the arrow in the right-hand side of the field.

• Data Bits. This field is only available when you have selected Async mode. Use this fieldto set the number of bits needed to represent a character. You can choose between 7 or 8bits (default). Select the number of bits from the drop-down menu displayed when youclick on the arrow in the right-hand side of the field.

• Stop Bits. This field is only available when you have selected Async mode. Use this fieldto set the number of bits needed to represent a stop bit. You can choose between 1(default) or 2 bits. Select the number of bits from the drop-down menu displayed whenyou click on the arrow in the right-hand side of the field.

• Bit Shave. This field is only available when you have selected Async mode. Use this fieldto shorten or “shave” the length of the stop bit(s). You would do this to reduce loss of bitsynchronization due to transmission between stations in multi-hop situations. You canchoose between 1/16th (default) to 7/16th. Select the bit shave bits from the drop-downmenu displayed when you click on the arrow in the right-hand side of the field.

• Parity. This field is only available when you have selected Async mode. Use this field toset up a parity bit used for error checking. The status of the parity bit (0 or 1) isdetermined by the other bits in the data bit. You can choose between “None” (default),“Odd” or “Even”. “None” means that the parity bit is not used. “Odd” means that thestatus of the parity bit is set so that there is an odd number of ones in the data bit.Similarly, “Even” means that the status of the parity bit is set so that there is an evennumber of ones in the data bit. Select the parity from the drop-down menu displayed whenyou click on the arrow in the right-hand side of the field.

• Break length. This field is only available when you have selected Async mode. Use thisfield to set the number of characters that will represent a line break. You can enter aninteger from 1 to 65535, representing the break length in characters. The default is 4.

High Speed Daughter BoardWhen a High Speed Daughter Board is fitted to an option slot, the associated option page hasthe following sections:


• Circuit 1




Figure 20: Option page with High Speed Daughter Board selectedThe Option Slot n section has the following fields:

• Option Board Type. Use this field to select the type of board inserted into the slot. Thedefault is “Not Installed”. In this case, select “High Speed Daughter Board” from thedrop-down menu displayed when you click on the arrow in the right-hand side of thefield.

• Cross connect to. Use this field to select the AUX port on the SMA the board uses tocommunicate with the SDM board at the other end of the circuit. This in turn selects theDXR 700 terminal by which the board data is sent and received. The default is “AUX A”.Select any one of the four AUX ports on the SMA from the drop-down menu displayedwhen you click on the arrow in the right-hand side of the field.

• Channel. Use this field to select the first channel used for the board data on the AUXchannel. The default is “2”. Select either channel “2”, “3”, or “2 and 3” from the drop-down menu displayed when you click on the arrow in the right-hand side of the field.

Note: If the SMA high speed daughter board circuit has a data rate of 128 KBPS, bothchannels are required, and you will only be able to select channel “2 and 3”. Ifthe circuit has a rate of 64 KBPS or less, then either “2” or “3” can be selected.

• Channels required. This field shows the number of AUX channels that the board requiresto send and receive data. It is generated automatically, and depends on the board youselected, and the values you input to the Data Rate fields in the Circuit section.

The Circuit 1 section contains the following fields:




• Active. Use this checkbox field to enable the other fields in the section. If the checkbox isnot selected (default), ie, not ticked, all other fields will be greyed out and disabled.

Note: When an Option Board is inactive, the SMA will treat it as present, but will notallocate any bandwidth to it. The board will not carry data.

• Data Rate. Use this field to select the speed at which the board transmits and receivesdata. You can select one of 8, 16, 24, 32, 48, 56, 64 (default), or 128 KBPS. Select therate from the drop-down menu displayed when you click on the arrow in the right-handside of the field.

Co-directional Daughter BoardWhen a Co-directional Daughter Board is fitted to an option slot, the associated option pagehas the following sections:


• Circuit 1

Figure 21: Option page with Co-directional Daughter Board selected




The Option Slot n section has the following fields:

• Option Board Type. Use this field to select the type of board inserted into the slot. Thedefault is “Not Installed”. In this case, select “Co-directional Daughter Board” from thedrop-down menu displayed when you click on the arrow in the right-hand side of thefield.

• Cross connect to. Use this field to select the AUX port on the SMA the board uses totransmit and receive data. This in turn selects the DXR 700 terminal by which the boarddata is sent and received. The default is “AUX A”. Select any one of the four AUX portson the SMA from the drop-down menu displayed when you click on the arrow in theright-hand side of the field.

Note: You must select an AUX port connected to a terminal.

• Channel. Use this field to select the first channel used for the board data on the AUXchannel. Default is “2”. Select either “2” or “3” from the drop-down menu displayedwhen you click on the arrow in the right-hand side of the field.

• Channels required. This field shows the number of channels on the AUX channel theboard requires to transmit and receive data. It is generated automatically from the board.

The Circuit 1 section contains only the message “No circuit configuration is required for aCo-directional Daughter Board.”

��5��

The Cross-connects page is only supported by the SMA. The Cross-connects page is used toshow the relationship, or cross-connection, between the SDM board data stream channels andthe channels available on the SMA AUX ports. Cross-connections are required for the datastreams of any SDM boards in the actual SMA, and also for any data streams the SMA isrelaying.

Note: In the latter case, the SDM boards are in other SMA, and the SMA is relaying themas part of a multi-hop link.




Figure 22: Cross Connect Page with grid shown

The relationship between the channels is shown on the grid. The vertical and horizontal axesshows the AUX port channels. There are two channels for each port. Cross-connects betweenchannels are shown shaded on the grid, i.e. if the second channel of Option board 2 is cross-connected to the third channel of AUX B, the column under OPTION 2 (2) is shaded, alongwith the row from AUX B (3). This is to indicate the channels are unavailable for otherconnections.

Cross-connections are made on the grid in two ways:

• Automatically, using the details you input for the boards in the option pages.

• Manually, using the mouse.

Automatic cross-connections are made for the SDM boards you have configured in the optionpages. You therefore need to take no further action to enable cross-connections for the boards.Manual cross-connections are made for the data streams for SDM boards outside the presentSMA. In this case, the SMA is being used as a relay, and the cross-connects are betweenavailable AUX port channels.

To set a manual cross-connection, you move the mouse to select the appropriate row andcolumn, then click the left mouse button. The selected row and column are then shaded in toshow they are in use. As you move the mouse cursor through the grid, the row and the columnit is situated on are highlighted, showing the current cross-connection that would be made ifyou pressed the left mouse button.




Note: You cannot select rows and columns already in use by an automatic cross-connection.

To remove a manual cross-connection, move the mouse to select the appropriate row andcolumn, then click the left mouse button.

Note: You cannot remove an automatic cross-connection.

��#��-�� You can use the Commissioning Workspace to install and commission a DXR NETworkelement. The Commissioning Workspace provides the following information and functions:

• Site details, RSSI and alarm information.

• Terminal details to sub-unit level.

• Line and radio facing loopback functions for the terminal tributaries, and digital and IFloopback functions for the terminal RF/Modem links.

• Manual protection switching (for protected terminals only).

You can access the above information and functions via the tabbed pages in the workspacearea.

Note 1: For the details associated with a particular type of element, refer to the relevantsection in this manual.

Note 2: The Commissioning workspace cannot be used offline, as its pages use real-timedata generated by the network. If you attempt to access the workspace while offline,DXR NET will display a warning message.

Note 3: You can only access remote terminal details if the radio link is operational.

The Commissioning Workspace is used to monitor and test the operation of a networkelement after it has been brought into service, especially during commissioning. Theworkspace has the following tabbed pages:

• Commissioning (DXR 100 and DXR 700 terminals).

• Terminal Details (DXR 100 and DXR 700 terminals).

• NMS Details (NMS board only).

• SMA Details (SMA only).

• Controls (DXR 100 and DXR 700 terminals).

��

The Commissioning page is divided into Local (Selected) and Remote sections. The detailsfor the terminal that you have currently selected in the Explorer Tree are given in the Local(Selected) section, and those for the terminal at the other end of the link are given in theRemote section.




Note: The Remote section details are only valid if the link is operational.

Figure 23: Commissioning Page – DXR 700Each section contains the following sub-sections:

• Site Details.

• AGC (DXR 100 terminals only).

• RSSI (DXR 700 terminals only).

• Alarm Information.

Note: You will not be able to change any of the details in the fields of this page, as theyare all read directly from the terminal. Because of this, they may not match thedetails for the unit in the blueprint.

The page also has the Commissioning Report button, which you can use to produce a reportcontaining details relevant to the terminal when it is commissioned.

Site DetailsThe Site Details sub-section contains the following fields:

• Site

• Terminal

• TX Frequency (MHz)

• TX Power (dBm)




Note: Terminals using frequency diversity will have TX Frequency and TX Power fieldsfor Radio A and Radio B.

AGCThe AGC sub-section contains a bar-graph and a Reset AGC button. The bar graph shows thecurrent AGC value, continually updated. The Reset AGC button resets the maximum andminimum lines on the bar graph to the maximum and minimum AGC values (+5V and 0V).

Note: Protected terminals will have bar graphs for Radio A and Radio B.

RSSIThe RSSI sub-section contains a bar-graph and a Reset RSSI button. The bar graph shows thecurrent RSSI value, continually updated. The Reset RSSI button resets the maximum andminimum lines on the bar graph to the maximum and minimum RSSI values measured sincethe monitoring began, or since the last time the button was selected.

Note: Protected terminals will have bar graphs for Radio A and Radio B.

Alarm InformationThe Alarm information section has two items, an Alarm Status LED icon, and a View Alarmsbutton. The icon is used to indicate whether any alarms are present on the terminal. Thecolours it can take and their meanings are listed in the table below.

��

$TKIJV )TGGP Indicates that no alarm is present. &WNN 4GF Indicates that the alarm status is not known. 4GF Indicates that an alarm has been triggered.

Note: A “dull red” icon is usually due to DXR NET being unable to communicate with the

terminal.

If you click on the View Alarms button, the Alarms page is displayed. The Alarms page isdivided into two panes. The left-hand pane, Alarm Status and Related Information, lists allpossible alarms in the Windows Explorer tree format. This has the alarms grouped inhierarchical levels under the units currently present in the link or terminal.




Figure 24: Alarms PageYou can move through the levels by double clicking on a unit listing to display the sub-unitand alarm listing under it. Each unit or alarm listing has an LED icon next to it. The iconindicates whether there are any alarms present in the unit or any sub-units under it. For analarm listing, the icon indicates the alarm status, as described in the previous table. Units“inherit” alarms from levels under them in the hierarchy. You can therefore use the AlarmStatus and Related Information pane to detect when an alarm is present on a unit, and then totrack the alarm to a particular component.

Note: The status indicated by the icons is given in the previous table.

The right-hand pane, Alarm Information, displays the details of any alarm selected in the left-hand pane. The right-hand pane contains the following fields:

• Alarm Name

• Alarm Description

• Alarm Type

• Alarm Severity

The Alarm Name field contains the name of the alarm as shown in the left-hand pane. TheAlarm Description contains the probable cause of the alarm.




The Alarm Type field entries are described in the following table.

�� 'SWKROGPV Indicates an alarm associated with an equipment fault or

external alarm input. 'PXKTQPOGPVCN Indicates an alarm associated with the enclosure that contains

the terminal equipment. 2TQEGUUKPI GTTQT Indicates an alarm associated with a software or processing

fault. %QOOWPKECVKQPU Indicates an alarm associated with the procedures and/or

processes required to carry information. 3WCNKV[ QH UGTXKEG Indicates an alarm associated with the degradation of quality

of service.

The Alarm Severity field entries are described in the following table.

Note: The entries are listed in order of increasing severity.

�� 9CTPKPI Indicates a condition with the potential to cause a fault that

affects service has occurred. /KPQT Indicates a condition that does not affect user traffic, but

which requires corrective action before a more serious faultoccurs.

/CLQT Indicates a condition affecting user traffic that requirescorrective action.

%TKVKECN Indicates a condition affecting user traffic that requiresimmediate corrective action.

For full descriptions of the alarms that can be generated by a DXR NETwork element, refer toAppendix B.

� �� $% 44��744

The Terminal Details page is divided into the following sections:

• General Information

• Pedigree Information (non-protected DXR 100 terminal only)

• Daughter Board Information (non-protected DXR 100 terminal only)

• PSW (protected DXR 100 terminal only)

• PRA A (protected DXR 100 terminal only)

• PRA B (protected DXR 100 terminal only)

• PMA Information (DXR 700 terminal only)

• RMA (non-protected DXR 700 terminal only)

• ODU (non-protected DXR 700 terminal only)

• RMA A (protected DXR 700 terminal only)

• RMA B (protected DXR 700 terminal only)




• ODU A (protected DXR 700 terminal only)

• ODU B (protected DXR 700 terminal only)

The page also has the following buttons:

• Local (Selected)

• Remote

• Refresh

• Inventory Report

The Local (Selected) button is used to display the details of the terminal you have selected inthe Explorer Tree. The Remote button will display the details of the remote terminal, ie, theterminal that the terminal you have selected is linked to. The Refresh button will re-displaythe Terminal Details page to take into account any changes since the page was first selected.The Inventory Report button will produce a report containing relevant terminal details.

Note: Remote terminal details can only be displayed if the link is operational.

Figure 25: Terminal Details Page




General InformationThe General Information section contains the following fields:

• Site Name

• Terminal Name

• Terminal Type

• Modulation Type

• Capacity

• Occupied Bandwidth

The Site Name and Terminal Name fields are both read from the terminal.

The Terminal Type field contains the equipment description of the terminal. The field isgenerated automatically from embedded information in DXR NET.

The Modulation Type field contains the type of modulation the terminal applies to the RFsignal. The field value is read from the terminal, and you cannot change it.

Note: The type of modulation is set at the factory, so you specify the type you requirewhen you order the terminal.

The Capacity field is only displayed when the terminal line interface type can support morethan one channel. The field value is read from the terminal, and you cannot change it.

Note: The capacity is set at the factory, so you specify it when you order the terminal. Youcan select the capacity in the Interface Setup page of the Configuration Workspace,but the capacity you select must match the terminal hardware.

The Occupied Bandwidth field contains the RF bandwidth that the signal from the terminaltakes up. The field value is read from the terminal, and you cannot change it.

Pedigree InformationFor a DXR 100 terminal, the Pedigree Information section contains the following fields:

• Part Number

• Serial Number

• Software Type

• Software Version

The details contained within these fields are self-explanatory. The section also contains aDetails button, which you can use to display the Pedigree Details box. This lists the PartNumber, Serial Number and Build Level for the Terminal Hardware, the Version and Typefor the Terminal Software, and the factory set duplexer TX and RX frequencies.




Daughter Board InformationFor a DXR 100 terminal, the Daughter Board Information section contains the followingfields:

• Option Board 1

• Option Board 2

These two fields display the names of any optional daughter boards that have been fitted intothe DXR 100. The entries are automatically generated depending upon whether/which boardsare fitted, and you will not be able to change them.

Note: The boards are normally factory fitted, which means you have to specify them whenyou order the terminal. They should only be fitted in the field by an accredited DMCStratex Networks representative.

PSWFor a protected DXR 100 terminal, the PSW section contains the following fields for thePSW:

• Part Number

• Serial Number


• Option Board 1

• Option Board 2

The details contained within these fields are self-explanatory. The section also contains aPSW Details button, which you can use to display the Pedigree Details box. This lists the PartNumber, Serial Number and Build Level for the PSW Hardware, the Version and Type for thePSW Software, and the interface capacity for the PSW Build Type.

PRA AFor a protected DXR 100 terminal, the PRA A section contains the following fields for RadioA:

• Part Number

• Serial Number


The details contained within these fields are self-explanatory. The section also contains aPRA A Details button, which you can use to display the Pedigree Details box. This lists thePart Number, Serial Number and Build Level for the PRA Hardware, the Version and Typefor the PRA Software, the occupied bandwidth and modulation for the PRA Build Type, andthe factory set duplexer TX and RX frequencies.




PRA BFor a protected DXR 100 terminal, the PRA B section contains the following fields for RadioB:

• Part Number

• Serial Number


The details contained within these fields are self-explanatory. The section also contains aPRA B Details button, which you can use to display the Pedigree Details box. This lists thePart Number, Serial Number and Build Level for the PRA Hardware, the Version and Typefor the PRA Software, the occupied bandwidth and modulation for the PRA Build Type, andthe factory set duplexer TX and RX frequencies.

PMA InformationFor a DXR 700 terminal, the PMA Information section contains the following fields:

• Part Number

• Serial Number


The details contained within these fields are self-explanatory. The section also contains aPMA Details button, which you can use to display the PMA Details box. This lists the PartNumber, Serial Number and Build Level for the PMA Hardware, the Build Type for the PMAInterface capacity, and the Version and Type for the PMA Software.

RMA InformationFor a non-protected DXR 700 terminal, the RMA Information section contains the followingfields:

• Part Number

• Serial Number


The details contained within these fields are self-explanatory. The section also contains aRMA Details button, which you can use to display the RMA Details box. This lists the PartNumber, Serial Number and Build Level for the RMA Hardware, the Occupied Bandwidth(MHz) and Modulation for the RMA Build Type, and the Version and Type for the RMASoftware.

ODU InformationFor a non-protected DXR 700 terminal, the ODU Information section contains the followingfields:

• Part Number

• Serial Number





The details contained within these fields are self-explanatory. The section also contains aDetails button, which you can use to display the ODU Details box. This lists the Part Number,Serial Number and Build Level for the ODU Hardware, the Version and Type for the ODUSoftware, and the TX and RX frequencies the duplexer was set to at the factory.

RMA A InformationFor a protected DXR 700 terminal, the RMA A section contains the following fields:

• Part Number

• Serial Number



RMA B InformationFor a protected DXR 700 terminal, the RMA B section contains the following fields:

• Part Number

• Serial Number



ODU A InformationFor a protected DXR 700 terminal, the ODU A section contains the following fields:

• Part Number

• Serial Number






ODU B InformationFor a protected DXR 700 terminal, the ODU B section contains the following fields:

• Part Number

• Serial Number






� �� $%344

The Terminal Details page is divided into the following sections:


• Hardware

• Software

Figure 26: Terminal Details Page - DXR 200

The Refresh button will re-display the Terminal Details page to take into account any changessince the page was first selected. The Inventory Report button will produce a reportcontaining relevant terminal details.

Note: Remote terminal details can only be displayed if the link is operational.


• Terminal Name

• Terminal Number

• Terminal Type


• Software Type




• Band

The details contained within these fields are read from the DXR 200 terminal.

HardwareThe Hardware section contains the following fields:

Slot

Module Type

PartNumber

Serial Number

Revision

HSC (Hardware Software Compatability)

The details contained within these fields are read from the DXR 200 terminal.

SoftwareThe Software section contains the following fields:

Slot

Module

Status

Version

The details contained within these fields are self-explanatory.




&�)� ��

The NMS Details page is divided into the following sections:


• Pedigree Information


• Site Name

• Element Name

• Element Type

The information contained in all these fields is read directly from the NMS.

The Site Name field contains the name assigned to the site. If you have not assigned a name tothe site, the field is assigned the default string “Site n” where “n” is an integer relating to thenumber of sites in the network.

The Element Name field contains the name assigned to NMS. If you not assigned a name tothe NMS, the field contains the default string “NMS n” where “n” is an integer relating to thenumber of NMS boards in the network.

The Element Type field contains a detailed description of the NMS board, usually “DXR 100NMS board.”

Pedigree InformationThe Pedigree Information section contains the following fields:

• Part Number

• Serial Number

• Software Type


The details contained within these fields are self-explanatory. The section also contains aDetails button, which you can use to display the Pedigree Details box. This lists the PartNumber, Serial Number and Build Level for the NMS Board Hardware, and the Version andType for the NMS Board Software.




)�!� ��

The SMA Details page is divided into the following sections:


• SMA

• Option Slot 1 (SDM equipped SMA only)

• Option Slot 2 (SDM equipped SMA only)

Figure 27: SMA Details Page


• Site Name

• SMA Name

The Site Name and the SMA Name fields contain the names read out from the SMA. Thesemay not be the names assigned in the blueprint.

SMAThe SMA section contains the following fields:

• Part Number

• Serial Number

• Software Type





The details contained within these fields are self-explanatory. The section also contains aDetails button, which you can use to display the Pedigree Details window. This lists the PartNumber, Serial Number and Build Level for the SMA Hardware, and the Version and Typefor the SMA Software.

Option Slot SectionsDepending on the type of board inserted into their associated slot, the Option Slot sectionscan contain the following fields:

Note: The Board ID text field will always be present, but the other three fields are onlypresent when either a low speed or high speed daughter board has been inserted intothe appropriate slot.

• Board ID text

• Part Number

• Serial Number


The Board ID text will contain one of the following:

• High speed daughter board installed

• Low speed daughter board installed

• Co-directional daughter board installed

• Unknown daughter board installed

• Option board not installed

The details contained within the Part Number, Serial Number and Software Version fields areself-explanatory.

��

The Controls page is divided into the Tributary Loopbacks, RF/Modem, Protection Switchingand Script File sections.

Note: The Protection Switching section is only available with a terminal in the protectedconfiguration.




Figure 28: Controls Page

Tributary LoopbacksThe Tributary Loopbacks section allows you to select the following types of loopbacks:

• No Tributary Loopback (default)

• Line Facing

• Radio Facing

Select an option by clicking on the appropriate radio button with the mouse. The centre of theselected button is filled to show that it has been selected.

Note: You can select only one of the three options at any one time.

LOOPBACK FUNCTIONS. Loopback functions interrupt network traffic.

TRIBUTARY LOOPBACKS. Tributary loopbacks affect all tributaries at once.

You can use the loopback functions to test the signal integrity of the link, and to help locatewhere any integrity problems are occurring. When you select a loopback function, theterminal will feed back any received input signal to the signal source. Normally, you wouldenable a loopback function, input a known bit-stream, and check the bit-stream output fromthe terminal for errors.




When you select the Line Facing loopback function, the loopback is made in the localterminal line interface. Any bit-stream fed into a line input channel to the terminal is fed backout again on the appropriate line output channels. You can then compare the output streamwith the input stream, identifying any errors. From this, you will be able to deduce the qualityof service and the error-rate of the terminal line interface.

When you select the Radio Facing loopback function, the loopback is made in the localterminal radio interface. Any signals received from the remote terminal will be re-transmittedback to the remote terminal over the radio link. You can then compare the output stream at theremote terminal with the input stream, identifying any errors. From this, you will be able todeduce the quality of service and the error-rate of the radio link.

RF/ModemThe RF/Modem section allows you to select the following:

• Digital Loopbacks

• IF Loopback

• FEC Disable

You select an option by clicking on the appropriate check box with the mouse. The box youhave selected is “checked”.


FEC DISABLE. FEC disable turns off the forward error correction function, and thereforeincreases the number of errors output from the terminal.

Note: You can only select these functions for the local terminal.

You can use these functions to test the data integrity of the terminal, and to help locate whereany integrity problems are occurring. When you enable a loopback, the terminal feeds anyreceived input data back to the source. You can then input a known bit-stream, check the bit-stream output from the terminal, and compare the output stream with the input stream,identifying any errors.

When you select the Digital Loopbacks option, the loopback is made between the compositedigital transmit and receive streams inside the radio modem, before the streams are passed todigital-to-analog conversion. From this, you will be able to deduce the error-rate in themodem circuitry.

When you select the IF Loopbacks option, the loopback is made between the transmit andreceive IF signals, just before they are output from the terminal. From this, you will be able todeduce the error-rate in the IF circuitry.

You would select the FEC Disable option in conjunction with one of the other RF modemloopbacks to determine the true transmission error-rate. You must disable FEC for this, asFEC automatically corrects any errored bytes in the received data, and this would mean thatany errors would be corrected before you could detect them.

Protection SwitchingThe Protection Switching section is only displayed when the terminal is in one of theprotected configurations. It allows you to test the ability of the terminal to switch between theavailable transmitters and receivers.




The Protection Switching section has the following sub-sections:

• Transmitter

• Receiver

• TX Switch Counter

The Transmitter sub-section allows you to change the following settings:

• Operation

• Radio

You can select either Automatic (default) or Manual operation of the protection switching byclicking on the appropriate radio button with the mouse. The centre of the button you haveselected is filled in to show it has been selected.

Note: You must select Manual operation before you can select a radio.

You can select either the A-Side (default) or B-Side radio by clicking on the appropriate radiobutton with the mouse. The centre of the button you have selected is filled to show it has beenselected.

The Receiver sub-section allows you to change the following settings:

• Operation

• Radio

You can select either Automatic (default) or Manual operation of the protection switching byclicking on the appropriate radio button with the mouse. The centre of the button you haveselected is filled to show it has been selected.

Note: You must select Manual operation before the Radio listing and radio buttons aredisplayed, i.e. before you can select a radio.

You can select either the A-Side (default) or B-Side radio by clicking on the appropriate radiobutton with the mouse. The centre of the button you have selected is filled to show it has beenselected.

Script File

SCRIPT FILES. You should only run script files under the supervision of accredited DMCservice personnel.

You can click the Script File button to open the window that allows you to select and run anyavailable test script files.




�� #��-�� You can use the Maintenance Workspace to diagnose any faults in a DXR NETwork element.The monitoring and diagnostic functions available include:

• Alarm information

• Constellation diagrams

• Equalizer Graphs

• AGC/RSSI graphs

• SNR readings

• line and radio facing loopback functions for the terminal tributaries, and digital and IFloopback functions for the terminal RF/Modem links

• manual protection switching (for protected terminals only)

You can access the above information and functions via the tabbed pages in the workspacearea.

Note 1: For the details associated with a particular type of element, refer to the relevantsection in this manual.

Note 2: The Maintenance workspace cannot be used offline, as it relies on real-time datagenerated by the network. If you attempt to access the workspace while offline,DXR NET will display a warning message.

Note 3: You can only access remote terminal details if the radio link is operational.

Note 4: DXR NET will always try to use the combination of SMA IP address and Terminalnumber to communicate with any DXR 200 terminal in the blueprint.

The Maintenance Workspace has the following tabbed pages:

• Alarms

• Constellation (DXR 100 and DXR 700)

• AGC (DXR 100 only)

• Equalizer Graph (DXR 100 and DXR 200 only)

• RSSI (DXR 700 only)

• Controls (DXR 100, DXR 200 and DXR 700)

• Terminal Details (DXR 100, DXR 200 and DXR 700)

• NMS Details (NMS board only)

• SMA Details (SMA only)

• File System (NMS Board and SMA)




The Alarms, Controls, Terminal Details, SMA Details and NMS Details pages are identical tothose described under the Commissioning Workspace heading, and therefore will not bedetailed here.

��

SELECTING OTHER OPERATIONS. Except for the AGC page operations (DXR 100terminal), or RSSI page operations (DXR 700 terminal), you cannot select other operationswhile Constellation Diagram monitoring is in progress.

STOPPING MONITORING. You must remember that just because a constellation diagramis not shown for a terminal or carrier does NOT mean the terminal or carrier is not beingmonitored.

A constellation diagram is a polar graph showing the plots obtained from monitoring aselected signal. The plots consist of groups of points, each point representing many samplesof the phase and amplitude of the signal. For error-free operation, the points should be tightlygrouped together. You can therefore use the plots in the diagram to monitor signalperformance.

DXR NET provides 24-hour constellation monitoring. Every point is shown from the time thesignal was sent out. This historical view of data points is valuable for analysing and trackinginterference and its possible causes. Previously, only the first 10,000 points were displayed.Now an unlimited number of data points can be displayed over time (limited only by displayresolution).

The Constellation page is divided into the Select Terminal and the Constellation Diagramsections.

Figure 29: Constellation Diagram – Single View Selected




For a DXR 700, the appearance of these two sections is dependent upon whether the Single orMulti-carrier view has been selected in the Advanced option of the DXR NET Maintenancemenu (refer to Section 2, DXR NET GUI). If the Single view has been selected, DXR NET

produces constellation diagrams by monitoring the baseband signals from each availableterminal. If the Multi-carrier view has been selected, DXR NET produces constellationdiagrams by monitoring the individual carriers on the local terminal.

Note: The multi-carrier option is not supported by the DXR 100.

Select TerminalFor a DXR 100, or a DXR 700 with the Single view selected, the Select Terminal section willcontain the following buttons:

• Local (for an unprotected terminal), or Local Radio A, Local Radio B (for a protectedterminal)

• Remote (for an unprotected terminal) or Remote Radio A, Remote Radio B (for aprotected terminal)

• Monitor All

• Reset All

By selecting from the Local and Remote buttons, you choose the terminals for whichconstellation diagrams will be displayed in the Constellation Diagram section.

Note: The diagrams for the Remote terminal(s) can only be produced when the link isoperational.

When you select the Monitor All button, DXR NET will start monitoring all the basebandsignals from all available terminals. When you select the Reset All button, DXR NET willclear the plots obtained up to that time.

For a DXR 700 with the Multi-carrier view selected, the Select Terminal section will containthe following buttons:

• Carrier n (where n varies from 1 to the total number of available signal channels)

• Monitor All

• Reset All

By selecting from the Carrier n buttons, you choose the carriers for which constellationdiagrams will be displayed in the Constellation Diagram section.

Note: Only the carriers to the local DXR 700 terminal can be monitored.

When you select the Monitor All button, DXR NET will start monitoring all available carrierson the local DXR 700 terminal. When you select the Reset All button, DXR NET will clear theplots obtained up to that time.




Constellation DiagramThe Constellation Diagram section will display the following items for each of the terminalsor carriers that were chosen using the Local, Remote or Carrier buttons in the Select Terminalsection:

• Constellation Diagram

• AGC (V) field (DXR 100 terminal only)

• RSSI (dBm) field (DXR 700 terminal only)

• SNR (dBm) field

• Monitor button

• Reset button

As already stated, each Constellation Diagram is a polar graph showing the plots obtainedfrom monitoring the selected terminal or carrier. You can therefore use the diagram monitorsignal performance.

Note: The number of sections the diagram is divided into depends on the type ofmodulation being used, eg. for DQPSK, the diagram is divided into four sections,for 16QAM, it is divided into sixteen sections.

Note: DXR 200 provides no access to constellation data.

The AGC (V) and SNR (dBm) fields allow you to view the current values of these twoparameters for the selected terminal or carrier.

When you select the Monitor button, DXR NET will start monitoring the selected terminal orcarrier. When you select the Reset button, DXR NET clear all the plots obtained up to thatpoint in time.

Note: Unlike the Monitor All and Reset All buttons in the Select Terminal section, thesebuttons only control the monitoring of the terminal or carrier related to this specificdiagram.

!+�

SELECTING OTHER OPERATIONS. Except for the Constellation page operations, youcannot select other operations while AGC monitoring is in progress.

STOPPING MONITORING. You must remember that just because an AGC graph is notshown for a terminal or carrier does NOT mean the terminal or carrier is not beingmonitored.

The AGC (Automatic Gain Control) is a voltage, which is used to control the amount of gainapplied by the DXR 100 terminal to a received signal. It is derived automatically by theterminal, based upon the strength of the received signal, compared with that required toproduce a recognisable output signal. The AGC variation with respect to time is plotted on anAGC graph, and this plot can then be used to monitor the terminal performance.




Figure 30: AGC Graph

The AGC page is divided into the Select Terminal and the AGC graph sections.

Select TerminalThe Select Terminal section contains the following buttons:

• Local (for an unprotected DXR 100), or Local A, Local B (for a protected DXR 100)

• Remote (for an unprotected DXR 100) or Remote A, Remote B (for a protectedDXR 100)

• Monitor All

• Reset All

By selecting from the Local and Remote buttons, you choose the terminals for which graphswill be displayed in the AGC Graph section.

Note: The graphs for the Remote terminal(s) can only be produced when the link isoperational.

When you select the Monitor All button, DXR NET will start monitoring all the AGC voltagesapplied to the baseband signals from all available terminals. When you select the Reset Allbutton, DXR NET will clear all the plots obtained up to that time.

AGC Graph

Except for the Constellation page operations, you cannot select other operations while AGCmonitoring is in progress.

The AGC Graph section will display the following items for each of the terminals that werechosen using the Local or Remote buttons in the Select Terminal section:




• AGC Graph

• Monitor button

• Reset button

As already stated, the AGC Graph section contains a continuous display of the AGC voltagefor the selected terminal plotted on a graph. The graph shows sampled AGC voltage valueplotted between the maximum and minimum values detected during the monitoring period.You can therefore monitor the variation of the AGC voltage with time.

When you select the Monitor button, DXR NET will start monitoring all the selectedterminals. When you select the Reset button, DXR NET will reset the Max and Min bars onthe AGC graph to the maximum and minimum AGC values (+5V and 0V).


'8��9 �+��

SELECTING OTHER OPERATIONS. You cannot select other operations while EqualizerGraph monitoring is in progress.

STOPPING MONITORING. You must remember that just because an Equalizer Graph isnot shown for a terminal or carrier does NOT mean the terminal or carrier is not beingmonitored.

The Equalizer Graph page is used to give an indication of any multi-path fading over theDXR 100 link. The page has two bar-graphs, one for FFE (Feed-Forward Equalization), andone for DFE (Decision Feedback Equalization).

The Equalizer Graph page is divided into the Select Terminal and Terminal sections.




Figure 31: Equalizer Graph

Select TerminalThe Select Terminal section contains the following buttons:

• Local (for an unprotected DXR 100), or Local A, Local B (for a protected DXR 100)

• Remote (for an unprotected DXR 100) or Remote A, Remote B (for a protectedDXR 100)

• Monitor All

• Reset All

By selecting from the Local and Remote buttons, you choose the terminals for which graphswill be displayed in the Terminal section.

Note: The graphs for the Remote terminal(s) can only be produced when the link isoperational.

When you select the Monitor All button, DXR NET will start monitoring all the DFE and FFEfrom all available terminals. When you select the Reset All button, DXR NET will clear all theplots obtained up to that time.




TerminalThe Terminal section will display the following items for each of the terminals that werechosen using the Local or Remote buttons in the Select Terminal section:

• DFE Graph

• FFE Graph

• Monitor button

• Reset button

As already stated, the Terminal section contains a continuous bar-graph display of the DFEand FFE for the selected terminals.

When you select the Monitor button, DXR NET will start monitoring all the selectedterminals. When you select the Reset button, DXR NET will clear the graphs.


%))�

SELECTING OTHER OPERATIONS. Except for the Constellation page operations, youcannot select other operations while RSSI graph monitoring is in progress.


The RSSI page is divided into the Select Terminal and the RSSI graph sections.




Figure 32: RSSI PageThe RSSI (Received Signal Strength Indication) is a measure of the strength of the radiosignal being received by the DXR 700. An RSSI Graph is a dynamic display of the RSSIplotted with respect to time. The graph shows sampled RSSI value plotted between themaximum and minimum RSSI values obtained since monitoring began. You can therefore usethis monitoring of the RSSI to check how the link performance varies with time.

The RSSI page is divided into the Select Terminal and the RSSI graph sections. Theappearance of these two sections is dependent upon whether the Single or Multi-carrier viewhas been selected in the Advanced option of the DXR NET Maintenance menu (refer toSection 2, DXR NET GUI). If the Single view has been selected, DXR NET produces RSSIgraphs by monitoring the baseband signals from each available terminal. If the Multi-carrierview has been selected, DXR NET produces graphs by monitoring the individual carriers onthe local terminal.

Select TerminalIf you have selected the Single view in the Maintenance menu, the Select Terminal sectionwill contain the following buttons:

• Local (for an unprotected DXR 700), or Local Radio A, Local Radio B (for a protectedDXR 700)

• Remote (for an unprotected DXR 700) or Remote Radio A, Remote Radio B (for aprotected DXR 700)

• Monitor All

• Reset All

By selecting from the Local and Remote buttons, you choose the terminals for which RSSIgraphs will be displayed in the RSSI Graph section.




Note: The diagrams for the Remote terminal(s) can only be produced when the link isoperational.

When you select the Monitor All button, DXR NET will start monitoring all the basebandsignals from all available terminals. When you select the Reset All button, DXR NET willclear all the plots obtained up to that point in time.

If the Multi-carrier option is selected in the Maintenance menu, the Select Terminal sectionwill contain the following buttons:

• Carrier n (where n varies from 1 to the total number of available signal channels)

• Monitor All

• Reset All

By selecting from the Carrier n buttons, you choose the carriers for which graphs will bedisplayed in the RSSI Graph section.

Note: Only the carriers to the local terminal can be monitored.

When you select the Monitor All button, DXR NET will start monitoring all available carrierson the local terminal. When you select the Reset All button, DXR NET will clear all the plotsobtained up to that point in time.

RSSI GraphThe RSSI Graph section will display the following items for each of the terminals or carriersthat were chosen using the Local, Remote or Carrier buttons in the Select Terminal section:

• RSSI Graph

• Monitor button

• Reset button

As already stated, each RSSI graph shows the variation of the RSSI monitored for the selectedterminal or carrier with time. You can therefore use the diagram monitor signal performance.

When you select the Monitor button, DXR NET will start monitoring the selected terminal orcarrier. When you select the Reset button, DXR NET will reset the Max and Min bars on thegraph to 0 dBm and -100dBm respectively.

Note: Unlike the Monitor All and Reset All buttons in the Select Terminal section, thesebuttons only control the monitoring of the terminal or carrier related to this specificgraph.




�� )"��

The File System page is used to view, and if necessary, delete, BIN files stored on SMA andNMS boards. These files are used when loading software to the elements under the control ofthe SMA or NMS board, and should be removed when loading new software.

Figure 33: File System Page

Installing DXR NET



: ��$%&'�

��This section covers the following:

• Requirements (ie, what a PC needs to run DXR NET)

• Installing DXR NET on your PC

Note: Before installing DXR NET, you must check that your PC fulfils the requirementslisted below. We also advise that the person carrying out the installation is familiarwith the features and terminology of your PC operating system.

% 8�� The requirements for a PC to be able to run DXR NET can be divided into the following:

• Software

• Hardware

Note: The above requirements will vary depending on your PC operating system, and thelevel of the tool you are installing.

)��*�� % 8��

To run the DXR NET Network Maintenance Tool (NMT), a PC must have one of:

• Microsoft Windows 95 OEM Service Release (OSR) 2 operating system (or later)installed,

• Microsoft Windows 98

• Microsoft Windows NT 4.0 (or later)

Note: Windows 95 users should check that they are running a “B” version of the operatingsystem. The operating system version is detailed in the System Properties window,which can be accessed via the System icon in the Control Panel window.

2��*�� % 8��

Note: The hardware requirements listed below are for the DXR NET NMT only, and do nottake into account any requirements of any other software. Before installingDXR NET, you should check that your PC has the capacity to operate both the tool,and any other required software.

Installing DXR NET



The minimum hardware requirements for DXR NET NMT are as follows:

• 133 MHz Pentium Processor

• 64 MB RAM

• 200 MB free hard disk space

• 3.5” floppy drive

• Serial COM port (COM1 or COM2)

• 800 x 600 resolution, 256 colour display (16 bit colour recommended)

• SVGA Display Adaptor Card

• 2 or 3-button Mouse

• 101-key US keyboard

��$%&'��#��*�;<After ensuring that you have fulfilled all the conditions for Windows 95 detailed underRequirements, you are now ready to prepare your PC to use DXR NET. This entails:

• Removing earlier versions of DXR NET from your PC (optional).

• Ensuring your PC has TCP/IP networking enabled.

• Loading DXR NET onto your PC.

• Ensuring your PC has Windows “Dial-up” Networking installed.

• Installing the DMC DXR driver utility.

• Starting-up Windows “Dial-up” Networking for the first time with the DMC DXRdriver utility.

• Ensuring your PC has W95ws2se.exe installed.

Installing DXR NET



% ��$%&'��"��

You can use this procedure if you want to:

• Remove earlier versions of DXR NET from your PC before loading your current version.

• Remove DXR NET from your PC altogether.

It is not necessary to remove earlier versions of DXR NET from your PC before loading yourcurrent version. However, keeping the earlier versions could lead to confusion betweenprogram files (especially when installing the DMC DXR Driver utility), and will take upmemory space.

If you do wish to remove any versions of DXR NET from your PC, proceed as follows:

WINDOWS 95 PROMPTS. When using this procedure in Windows 95, you will beprompted if "sif.ini" should be removed or not. If there is another installation of DXR NET

on the PC hard drive, always select NO in response to this prompt, as the other installationwill be reliant on the "sif.ini" file being present.

BLUEPRINTS AND CONFIGURATION FILES. If you wish to remove an earlier versionof DXR NET but keep any network blueprint files or element configuration files created bythe earlier version, make sure you save these files outside the DMC folder before removingthe earlier version of DXR NET.

Procedure

Step 1: On the desktop, click Start to display the Start menu, then select Settings, ControlPanel.

Step 2: Double-click on the Add/Remove Programs icon in the Control Panel window.

Step 3: Select the version of DXR NET you wish to remove in the window of theInstall/Uninstall page, then click the Add/Remove button, then the OK button.

Step 4: Confirm you wish to delete the version of DXR NET by clicking the Yes button inthe Confirm Delete box. The Uninstall utility will now remove DXR NET from yourPC.

Step 5: Uninstall will display a message if it cannot remove certain folders or files. If thishappens, click the Details button, and record the file details to remove themmanually later.

Step 6: Click the OK button to return to the Control Panel window, then close the ControlPanel window.

Step 7: Use Windows Explorer to manually delete any folders or files noted in Step 5.

You have now removed the selected version of DXR NET from your PC. You can repeat theprocedure for any other versions, or until DXR NET is completely removed from your PC

Installing DXR NET



��6��"��

TCP/IP NETWORKING. Your PC must have TCP/IP networking installed to use DXR NET

You will need to install TCP/IP on your PC to let it use the NMS connection. This requiresyou to:

• Install the TCP/IP protocol, and bind it to the Dial-Up Networking adaptor.

• Enter TCP/IP information. Installing the TCP/IP protocol

Step 1: On the desktop, click Start to display the Start menu, select Settings, click ControlPanel, and then double-click Network to display the Network dialog box.

Step 2: Click Add, then Protocol.

Step 3: Click Add, Microsoft in the Manufacturers column, and then click MicrosoftTCP/IP.

Step 4: Click the adapter you want to bind to the TCP/IP protocol, and then click Properties.

Step 5: On the Bindings tab, make sure the checkbox for the appropriate protocol ischecked.

If prompted, restart your computer. Then, go to the following Entering TCP/IP Informationprocedure.

Note: When you install TCP/IP, it is bound to all of your adaptors by default. If you have anetwork card and don't use TCP/IP with it, in the Network dialog box, select thenetwork card, click Properties, click the Bindings tab, and then click to clear theTCP/IP check box.

Entering TCP/IP Information


Step 2: Click TCP/IP (if there is more than one TCP/IP entry, click TCP/IP -> Dial-UpAdapter), then click Properties.

Step 3: Select the IP Address page, and type your PC IP address and subnet mask

Note: On the Bindings tab, it is recommended that you click to clear the File and printersharing check box.

Installing DXR NET



��$%&'�

The installation is carried out using DXR NET InstallShield utility. The procedure is asfollows:

Note: DMC Stratex Networks advises that you use the default locations and folders set byInstallShield, but take careful note of the destination drive for the DMC programfolder and the COM port selected on your PC.

Procedure

Step 1: From the desktop, insert the CD into the CD drive.

Step 2: Run the setup.exe file on the CD. This will run InstallShield, which will install thetool on your PC.

Step 3: Follow the screen prompts. These will be requests as to whether you wish to acceptor change the InstallShield default settings.

Step 4: Click on the Next button to move to the next screen, until the installation procedureis complete.

Step 5: Remove the CD from your PC, and store in a safe place.

��#��*�=��5��& �*��-��

DXR NET uses Windows® “Dial-up” Networking to make an NMS connection to a SMA orNMS board, either directly, or via a modem. From the user perspective, both types ofconnection appear to be via a “Dial-up” modem.

Note: To set-up Windows® “Dial-up” Networking for modem connections, consult theinstructions that came with your modem.

To install Windows® “Dial-up” Networking on your PC, boot-up your PC and proceed asfollows:

Procedure

Step 1: Select the Start button.

Step 2: Select Settings, Control Panel from the Start button menu.

Step 3: Select the Add/Remove Programs icon from the Control Panel window.

Step 4: Select the Windows Setup Tab from the Add/Remove Programs Properties box.

Step 5: On the Windows Setup page, select Communications from the Components list.

Step 6: Select Details, then select Dial-up Networking and Phone Dialler, then the OKbutton.

Step 7: Select the OK button in the Windows Setup page.

Step 8: Select the OK button in the Add/Remove Programs Properties box.

Step 9: Select File, Close in the Control Panel window.

Installing DXR NET



��$%�� ,��"

For the direct NMS connection to a SMA or NMS board the DMCDXR driver utility isinstalled in place of the modem driver:

Procedure



Step 3: Select the Modems icon from the Control Panel window.

Step 4: Select the Add button on the General page.

Step 5: Select Other Type Modem, then Next.

Step 6: Select Don’t Detect, then Next.

Step 7: Select Have Disk, and use Browse Program Files to find nmsmodem.inf then selectOK. This driver should be in the drivers directory, under the directory whereDXR NET was installed.

Step 8: Select "DMC Direct Connection (38400 bps)", and the COM port you will be using,then OK, then Next.

Step 9: Wait while the driver is installed.

Step 10: Select Finish, Close.


)��#��*�=��5��& �*��-��

After installation, you will need to go through the following procedure to start up Windows®“Dial-up” Networking:

Procedure


Step 2: For Windows '95, select Programs, Accessories, Dial up Networking, from the Startbutton menu.

For Windows '98, select Programs, Accessories, Communications, Dial upNetworking, from the Start button menu.

Step 3: Select Make New Connection.

Step 4: Type a name, such as "DMC DXR Connection".

Step 5: Select device called "DMC Direct Connection (38400bps)", and select "Configure".

Step 6: Select the required COM port, then OK, then Next.

Step 7: Type any number in the area code and telephone number.

Installing DXR NET



Step 8: Select the correct Country Code, then select Next, Finish.

Step 9: Right click on your new connection (named in Step 4), then select Properties.

Step 10: Select Server Type button. If required, set the defaults to PPP (Point-to-PointProtocol) and Windows 95.

Step 11: If required, set the Advanced Options Group settings Logon to Network and RequireEncrypted to Off, and the Enable SW Comp setting to On.

Step 12: If required, set the Allowed Protocols Group to TCP/IP only.

Step 13: Select the "TCP/IP settings" button and select Server Supplied IP address.

Step 14: Select OK until returned to the Dial-up Networking screen, then File, Close.

��#��)��-3

To complete the installation procedure for Windows 95, proceed as follows:

Procedure

Step 1: Go to Windows Explorer, and use this to find "W95ws2se.exe".

Step 2: Run "W95ws2se.exe" from Windows Explorer.

Step 3: When prompted, reboot the PC.

The installation procedure is now complete for Windows 95.

��$%&'��#��*�;>After ensuring that you have fulfilled all the conditions detailed under WorkstationRequirements, you are now ready to prepare your PC to use DXR NET. This entails:


• Ensuring your PC has TCP/IP networking enabled.

• Loading DXR NET onto your PC.

• Ensuring your PC has Windows “Dial-up” Networking installed.

• Installing the DMC DXR driver utility.

• Starting-up Windows “Dial-up” Networking for the first time with the DMC DXRdriver utility.

Installing DXR NET



% ��$%&'��"��







Procedure









Installing DXR NET



��6��"��



• Install the Windows 98 TCP/IP protocol, and bind it to the Dial-Up Networking adaptor.

• Enter TCP/IP information.

Installing the Windows 98 TCP/IP protocol


Step 2: Click the Add button, and check the protocols displayed in the window. If theWindows 98 TCP/IP protocol is already installed, you can skip the rest of thisprocedure, and the following Entering TCP/IP Information procedure.

Step 3: Click Protocol, then the Add button.

Step 4: Click Microsoft, and then click TCP/IP, OK.

Step 5: Click Dial-Up Adapter, and then Properties.

Step 6: Click the Bindings tab, and then make sure the TCP/IP check box is selected.

If prompted, restart your computer. Then, go to the following Entering TCP/IP Informationprocedure.

Note: When you install TCP/IP, it is bound to all of your adaptors by default. If you have anetwork card and don't use TCP/IP with it, in the Network dialog box, select thenetwork card, click Properties, click the Bindings tab, and then click to clear theTCP/IP check box.

Entering TCP/IP Information


Step 2: Click TCP/IP (if there is more than one TCP/IP entry, click TCP/IP -> Dial-UpAdapter), then click Properties.

Step 3: Type your PC IP address and subnet mask

Note: On the Bindings tab, it is recommended that you click to clear the File and printersharing check box.

Installing DXR NET



��$%&'�

DXR NET is installed from CD. The installation is carried out using DXR NET InstallShieldutility. The procedure is as follows:


Procedure






��#��*�=��5��& �*��-��

DXR NET uses Windows® “Dial-up” Networking to make an NMS connection to a SMA orNMS board, either directly, or via a modem. From the user perspective, both types ofconnection appear to be via a “Dial-up” modem.

Note: To set-up Windows® “Dial-up” Networking for modem connections, consult theinstructions that came with your modem.

To install Windows® “Dial-up” Networking on your PC, boot-up your PC and proceed asfollows:

Procedure



Step 3: Select the Add/Remove Programs icon from the Control Panel window.

Step 4: Select the Windows Setup Tab from the Add/Remove Programs Properties box.

Step 5: On the Windows Setup page, select Communications from the Components list.

Step 6: Select Details, then select Dial-up Networking and Phone Dialler, then the OKbutton.

Step 7: Select the OK button in the Windows Setup page.

Step 8: Select the OK button in the Add/Remove Programs Properties box.


Installing DXR NET



��$%�� ,��"


Procedure





Step 5: Select Other Type Modem, then Next.


Step 7: Select Have Disk, and use Browse Program Files to find nmsmodem.inf, then selectOK. This driver should be in the drivers directory, under the directory whereDXR NET was installed.

Step 8: Select "DMC Direct Connection (38400 bps)", and the COM port you will be using,then OK, then Next.




)��#��*�=��5��& �*��-��

Procedure


Step 2: Select Programs, Accessories, Dial up Networking, from the Start button menu.

Step 3: Select Make New Connection.

Step 4: Type a name, such as "DMC DXR Connection".

Step 5: Select device called "DMC Direct Connection (38400bps)", and select "Configure".

Step 6: Select the required COM port, then OK, then Next.

Step 7: Type any number in the area code and telephone number.

Step 8: Select the correct Country Code, then select Next, Finish.

Step 9: Right click on your new connection (named in Step 4), then select Properties.

Installing DXR NET



Step 10: Select Server Type button. If required, set the defaults to PPP (Point-to-PointProtocol) and your operating system (Windows 95, 98 or NT 3.5, etc).

Step 11: If required, set the Advanced Options Group settings Logon to Network and RequireEncrypted to Off, and the Enable SW Comp setting to On.

Step 12: If required, set the Allowed Protocols Group to TCP/IP only.

Step 13: Select the "TCP/IP settings" button and select Server Supplied IP address.

Step 14: Select OK until returned to the Dial-up Networking screen, then File, Close.

��$%&'��#��*�&�After ensuring that you have fulfilled all the conditions detailed under WorkstationRequirements, you are now ready to prepare your PC to use DXR NET. This entails:

WINDOWS NT ADMINISTRATION RIGHTS. As per other Windows applications, youmust have logged onto NT with administration rights in order to install the DXR NET

application.


• Installing the IP protocol.

• Installing the DMC DXR Driver.

• Installing RAS (Remote Access Service).

• Dial-up networking configuration.

• Testing dial-up networking.

% ��$%&'��"��







Procedure


Installing DXR NET










��6��"��



• Install the TCP/IP protocol, and bind it to the Dial-Up Networking adaptor.

• Enter TCP/IP information.

Installing the TCP/IP protocol


Step 2: Go to the Protocols page, and click the Add button.

Step 3: Click TCP/IP Protocol, then OK.

Step 4: Click No in the TCP/IP dialog box asking if you want to use DHCP.

Step 5: Enter the location of the “I386” files into the Windows NT Setup dialog box, thenclick Continue.

Step 6: Click Close to start the binding process.

Step 7: Click Yes when prompted to restart your PC.

��$%&'�

DXR NET is installed from CD. The installation is carried out using DXR NET InstallShieldutility. The procedure is as follows:

Installing DXR NET




Procedure






��$%�� ,��"


Procedure






Step 6: Select Have Disk, and use Browse Program Files to find nmsmodem.inf, then selectOK. This driver should be in the drivers directory, under the directory whereDXR NET was installed.

Step 7: Select "DMC Direct Connection (38400 bps)", then Next.

Step 8: Select COM1, then Next.



Step 11: Select the Modems icon from the Control Panel window, and check that the systemhas registered your installation.


Installing DXR NET



��%!)?% �� !�� ) �� @

RAS enables you to use dial-up networking and other NT features. DXR NET uses Windows®“Dial-up” Networking to make an NMS connection to a SMA or NMS board.

To install RAS on your PC, boot-up your PC and proceed as follows:

Procedure



Step 3: Select the Network icon from the Control Panel window.

Step 4: Select the Services Tab from the Network dialog box, and click Add.

Step 5: Select the Remote Access Service, then OK.

Step 6: Locate and select the “I386” files on your PC, then Continue.

Step 7: In the Add RAS Device box, select the DMC DXR Driver Utility you installed onyour PC, then OK.

Step 8: In the Remote Access Setup box, select the DMC DXR Driver Utility, thenConfigure.

Step 9: In the Configure Port Usage box, select Dial out only, then OK.

Step 10: Click Continue, then select File, Close in the Control Panel window.ConfiguringDial-up Networking

To configure dial-up networking for use, proceed as follows:

Procedure

Step 1: On the desktop, double-click My Computer.

Step 2: Double-click Dial-up Networking.

Step 3: If the Location Information box appears, fill-in the required information, clickClose, then double-click Dial-up Networking.

Step 4: If the Dial-up Networking message box appears, click OK.

Step 5: Enter the name you want to give to the DXR NET NMS connection into the NewPhonebox Entry Wizard box, select the “I know all about…” check box, then clickFinish.

Step 6: Double-click Dial-up Networking to display the New Phonebook Entry box.

Step 7: In the Basic page, select the DMC DXR Driver Utility in the Dial using scroll box,the name you gave to the NMS connection in the Entry name text box, and enter asuitable number in the Phone Number box.

Installing DXR NET



Step 8: In the Server page, select “PPP:Windows NT, Windows 95 Plus, Internet…” in theDial-up server type scroll box, ensure that the Enable software compression andEnable PPP LCP extensions check boxes are selected, and that only the TCP/IPcheck box is selected in the Network protocols section, then click TCP/IP Settings....

Step 9: In the PPP TCP/IP Settings box, ensure that Server assigned IP address, Serverassigned name server address, Use IP header compression, and Use default gatewayon remote network are all selected, then click OK.

Step 10: In the Security page, click “Accept any authentication…”, then OK.

Step 11: Close in the Dial-up Networking window.

Using DXR NET NMT



A ,��$%&'�&��

+ � ��This section describes how to use DXR NET. You can use this tool in four main ways:

• To design a network blueprint.

• To work with a DXR NETwork with a network blueprint loaded.

• To work with a DXR NETwork without a network blueprint loaded.

• To configure, commission, and carry out diagnostics on individual network elements.

� ��& �*��-.�� *�� $%&'� DXR NET enable you to view the entire connected network.

& �*��-.�� *

The network blueprint is a software representation of the actual DXR NETwork. It is used toensure the network and its elements are configured, commissioned, and maintained in anorderly manner. Refer to Section 2 for more details.

There are two types of network:

• Networks without NMS units (ie, made up of terminals only).

• Networks with NMS units (ie, containing both NMS units and terminals).

The type of network defines the way in which you design your blueprint.

Adding Sites to a Network BlueprintTo add a site to a network, either right-click on the network icon and select Add Site, or selectthe network icon and select Add Site from the Configuration menu.

Adding Network Elements to a Site in a Network BlueprintThe way in which you add a network element to a site in the blueprint depends on the type ofelement, and its relationship to the other elements at the site:

• To add either a DXR 100 without a NMS board, a DXR 700 not under SMA control, or aSMA, select the required element from the Add Network Element window, then click theOK button.

• To add either a DXR 100 with a NMS board, select the required DXR 100 terminal fromthe Add Network Element window, click the NMS Option check box, then click the OKbutton.

Using DXR NET NMT



• To add a DXR 200 under SMA control, first add the SMA, select the SMA in theDXR NET Explorer Tree pane, select the required DXR 200 from the Add NetworkElement window, then click the OK button. Refer to Appendix G: "Using DXR NET withDXR 200" for full instructions.

• To add a DXR 700 under SMA control, first add the SMA as described above, select theSMA in the DXR NET Explorer Tree pane, select the required DXR 700 from the AddNetwork Element window, then click the OK button.

�� & �*��-.�� 5&�)& �*��-Before you can create a blueprint for a non-NMS network, you must have carried out thefollowing tasks:

• Given the network a name.

• Identified and named all the sites on the network.

• Identified and named all the terminals at each site .

�� 5&�).��

You can create a blueprint for a non-NMS network using the following procedure:

Note: We advise you create the blueprint while working offline.

Procedure

Step 1: From the desktop, run DXR NET.

Step 2: Click on the Configuration Workspace button from the Workspace Selection screen.

Step 3: The Explorer Tree pane will have the Network icon followed by “Network” at thetop of the column. Click on “Network”, type in the name you have given to thenetwork, then press <Enter>.

Step 4: To add a site to the blueprint, right-click on the Network icon in the Explorer Treepane, then select Add Site from the drop-down menu. The Site icon will appear inthe pane, followed by “Site n”, where “n” relates to the number of sites already inthe blueprint.

Step 5: Select the Site icon for the site you have just added in the Explorer Tree pane. TheSite Information page appears in the workspace. Enter the name you have given thesite into the Site Name field. You can also add the Description and Contact Details(for the person responsible for the site) into the relevant fields in the page. Whenyou are satisfied with the details, click on the Commit button in the Toolbar.

Step 6: Repeat Steps 4 and 5 until you have added all the other sites to the blueprint.

Step 7: To add terminals to a site, right-click on the Site icon in the Explorer Tree pane,then select Add Network Element from the drop-down menu. Select the type ofterminal you want to add to the site from the Add Network Element window asdescribed in Adding Network Elements. The icon for the terminal will appear in theExplorer Tree pane, followed by the default name. Click on the default name, typein the name you have given to the terminal, then press <Enter>.

Using DXR NET NMT



Note: The right-click menu for the DXR 200 icon contains the following elements: ExportNetwork Element, Rename and Delete.

Step 8: To import an already saved configuration file for a terminal to a site, right-click onthe Site icon in the Explorer Tree pane, then select Import Network Element fromthe drop-down menu. In the Import Configuration window, select the previouslysaved configuration file for the terminal, then click Open. The icon for the terminalwill appear listed under the site in the Explorer Tree pane, followed by the filename. If you want to give the terminal a new name, click on the current name, typein the name of your choice, then press <Enter>.

Step 9: Select the terminal you have just added or imported, then go through each of theavailable tabbed pages in the Configuration workspace. Either accept the defaultsettings, or enter the values you require. Refer to the section in this manual thatdescribes the terminal for details. Select the Commit button from the DXR NET

toolbar to save any changes you make to the blueprint.

Step 10: Repeat Steps 7 to 9 as required for the other sites on the network.

Step 11: When you have completed your design, select File from the menu bar, and then Savefrom the drop-down menu to save the blueprint for future reference.

Step 12: When you have finished using DXR NET, select File from the menu bar, and thenExit.

You are now returned to the PC desktop.

Using DXR NET NMT



'/�� &��5&�).��

In this example, you have set-up a simple network servicing the hospitals in three towns,Newtown, Oldtown, and Seatown. The network comprises two links, one from Newton toSeatown, and the other from Newtown to Oldtown. You have selected protected DXR 103terminals to make the links; there will be two of these at the Newton site, and one each at theother sites.

Before you start to design the network blueprint, you should decide what names you are goingto use in the blueprint. You should therefore try and select names that are meaningful to youand to anyone else who may have cause to use the blueprint. At the same time, the namesshould be short enough to be viewed without difficulty in the Explorer Tree pane.

Your first task is to give the network a name. The main reason for this is to enable you toeasily identify the blueprint file. As the network is to service three hospitals, you decide tocall it MEDICAL.

Your next task is to select the names for the sites. As there is only one site at each location,you decide to name each site after the town it is located in, ie. NEWTOWN, OLDTOWN andSEATOWN. If there was more than one site at each location, you could distinguish them byincluding either a letter or a number in the name, eg. NEWTON-A, NEWTON-B, orNEWTON-1, NEWTON-2, etc.

You can now select the terminal names. The most useful information these can contain iswhich link the terminal belongs to, and which end of the link it is at. You can achieve this byincluding the names of the local and remote sites in the terminal name, with the local sitename first. The names should be separated with a hyphen, and can be shortened to be viewedin the Explorer Pane. For example, the terminal at Seatown could be namedSEATOWN-NEWTOWN, or SEA-NEW. You should ensure that any shortened names retainenough detail to be clearly identified by anyone who will use the blueprint.

Note: If you use a Terminal Number in the Terminal Name field, ensure that it is the correctTerminal Number.

MEDICAL

NEWTOWN

DXR 103 DXR 103DXR 103 DXR 103

OLDTOWN SEATOWN

Figure 34: Non-NMS Blueprint Example – Network Diagram

You can now begin to design the blueprint:

Procedure



Step 3: The Explorer Tree pane will have the Network icon followed by “Network” at thetop of the column. Click on “Network”, type in MEDICAL, then press <Enter>.

Using DXR NET NMT



Step 4: Right-click on the Network icon in the Explorer Tree pane, then select Add Sitefrom the drop-down menu. The Site icon will appear in the pane, followed by “Siten”, where “n” relates to the number of sites already in the blueprint.

Step 5: Select the Site icon for the site you have just added in the Explorer Tree pane. TheSite Information page appears in the workspace. Enter NEWTOWN into the SiteName field. You can also add the Description and Contact Details (for the personresponsible for the site) into the relevant fields in the page. When you are satisfiedwith the details, click on the Commit button in the Toolbar.

Step 6: Repeat Steps 4 and 5 to add the Seatown and Oldtown sites to the blueprint.

Step 7: Right-click on the NEWTOWN site icon in the Explorer Tree pane, then select AddNetwork Element from the drop-down menu. Select the DXR 103 ProtectedTerminal from the Add Network Element window. The icon for the terminal willappear in the Explorer Tree pane, followed by the default name. Click on the defaultname, and type in NEWTOWN-SEATOWN, then press <Enter>.

Step 8: Select the NEWTOWN-SEATOWN terminal in the Explorer Pane, then go througheach of the available tabbed pages in the Configuration workspace. Either accept thedefault settings, or enter the values you require. Select the Commit button from theDXR NET toolbar to save any changes you make to the blueprint.

Step 9: Right-click on the NEWTOWN site icon in the Explorer Tree pane, then select AddNetwork Element from the drop-down menu. Select the DXR 103 ProtectedTerminal from the Add Network Element window. The icon for the terminal willappear in the Explorer Tree pane, followed by the default name. Click on the defaultname, and type in NEWTOWN-OLDTOWN, then press <Enter>.

Step 10: Select the NEWTOWN-OLDTOWN terminal in the Explorer Pane, then go througheach of the available tabbed pages in the Configuration workspace. Either accept thedefault settings, or enter the values you require. Select the Commit button from theDXR NET toolbar to save any changes you make to the blueprint.

Step 11: Right-click on the OLDTOWN site icon in the Explorer Tree pane, then select AddNetwork Element from the drop-down menu. Select the DXR 103 ProtectedTerminal from the Add Network Element window. The icon for the terminal willappear in the Explorer Tree pane, followed by the default name. Click on the defaultname, and type in OLDTOWN-NEWTOWN, then press <Enter>.

Step 12: Select the OLDTOWN-NEWTOWN terminal in the Explorer Pane, then go througheach of the available tabbed pages in the Configuration workspace. Either accept thedefault settings, or enter the values you require. As the NEWTON-OLDTOWNterminal already exists in the blueprint, you should select it as the remote terminalfor OLDTOWN-NEWTOWN. Select the Commit button from the DXR NET toolbarto save any changes you make to the blueprint.

Step 13: Right-click on the SEATOWN site icon in the Explorer Tree pane, then select AddNetwork Element from the drop-down menu. Select the DXR 103 ProtectedTerminal from the Add Network Element window. The icon for the terminal willappear in the Explorer Tree pane, followed by the default name. Click on the defaultname, and type in SEATOWN-NEWTOWN, then press <Enter>.

Using DXR NET NMT



Step 14: Select the SEATOWN-NEWTOWN terminal in the Explorer Pane, then go througheach of the available tabbed pages in the Configuration workspace. Either accept thedefault settings, or enter the values you require. As the NEWTON-SEATOWNterminal already exists in the blueprint, you should select it as the remote terminalfor SEATOWN-NEWTOWN. Select the Commit button from the DXR NET toolbarto save any changes you make to the blueprint.

Step 15: You have now completed the blueprint. Select File from the menu bar, and thenSave from the drop-down menu to save the blueprint for future reference.

Step 16: If you are finished using DXR NET, select File from the menu bar, and then Exit.

You are now returned to the PC desktop. You can now use the blueprint to connect to thenetwork as described in “Connecting to the Network with a Network Blueprint”.

�� & �*��-.�� &�)& �*��-Before you can create a blueprint for a NMS network, you must have carried out thefollowing tasks:

• created the IP addresses for all the NMS elements on the network

• created the Routing Table entries for all the NMS elements on the network

• identified the correct terminal numbers for all DXR 200s

• given the network a name

• identified and named all the sites on the network

• identified and named all the network elements at each site

The last three tasks are as already described for the non-NMS network blueprint.

�$%&�)& �*��-��!�� % 8�� ?�$% 44��744

��"@

For a NMS network to function, the NMS elements must be able to communicate with oneanother. In DXR NMS networks, NMS element communication is carried out using IP(Internet Protocol) Addressing. Each message sent over the network will contain theDestination IP address it is to be sent to. A NMS element looks at the Destination IP addressof the messages it receives to determine if they match the element IP address. If not, theelement sends the message to its destination via the port associated with the messageDestination IP address. Hence, each NMS element on a DXR NETwork requires three things:

• its own IP address

• the IP addresses of the NMS elements it is to communicate with

• the ports on the NMS element associated with the IP addresses

In the blueprint, the IP addresses of all the NMS elements are set using the IP Address Table.The IP addresses an element it can communicate with, and the ports it uses to communicatewith them are set in the Routing Table associated with the NMS element.

Using DXR NET NMT



��!��

An IP address is divided into four eight-digit binary numbers known as octets. Forconvenience, the numbers in the address are normally displayed as decimals, eg255.255.255.255, not 11111111.11111111.11111111.11111111. However, you shouldremember that the decimals are representations of binary numbers, and any operations carriedout on the addresses are binary operations. This is especially important when the topic of IPmasking is considered.

��-��!��

A Mask IP Address is used to determine which of the octets in an IP address are required byan NMS element to determine the port to a Destination IP Address. Like the Destination IPaddress, the Mask IP Address is divided into four octets, however, mask octets usually onlytake the values 255 or 0. When the NMS element looks at a message IP address, it compares itwith the Destination IP Addresses associated with the element ports to determine the port towhich the message should be routed. If an octet is set to 0, the corresponding octet of theDestination IP Address will be ignored in the comparison. If the mask octet is set to 255, thecorresponding octet of the Destination IP Address is used in the comparison. This is bestshown by an example.

ExampleThe Destination and Mask IP Addresses for the ports of a NMS element are set as follows:

Port Destination IP Address Mask IP Address

Port 1 128.132.96.25 255.255.255.255

Port 2 128.132.96.17 255.255.255.0

Port 3 128.132.21.48 255.255.0.0

For IP masking, a binary AND is carried out on the Mask IP Address and the associatedDestination IP Address. For Port 1:

Destination IP Address = 128.132.96.25 Decimal = 10000000.10000100.01100000.00011001

Mask IP Address = 255.255.255.255 Decimal = 11111111.11111111.11111111.11111111

Binary AND Result = 10000000.10000100.01100000.00011001

= 128.132.96.25

For Port 2:




= 128.132.96.0

For Port 3:




= 128.132.0.0

Using DXR NET NMT



When the NMS element matches the octets of the IP Address message with the results of IPmasking, it ignores any octets in the result that are zero. This means that:

• for a message to use Port 1, all four message IP octets must match the corresponding octetof the result IP address, ie. 128, 132, 96 and 25

• for a message to use Port 2, the first three message IP octets must match thecorresponding octet of the result IP address, ie. 128, 132 and 96.

• for a message to use Port 3, the first two message IP octets must match the correspondingoctet of the result IP address, ie. 128 and 132.

Consider the following three messages:

• Message 1, going to the IP address 128.132.96.52



As a result of IP masking, Message 1 can be routed via Ports 2 and 3, Message 2 can berouted via Port 1, and Message 3 can only be routed via Port 3.

�$%&�)'� � ��!��

DMC recommend that DXR NMS elements take IP addresses in the range 10.0.0.1 to10.255.255.255. The first octet, 10, is standard for all DXR IP addresses. You can set all thethree other octets from to any value between 0 to 255 inclusive. The second octet is used toset the sub-net address of the NMS element. This can be used to divide the NMS elements onthe network into smaller sub-nets. The third octet identifies the particular NMS element onthe sub-net, and the fourth octet is used to identify the connections (ports) on the element usedto connect to the addresses.

Note: You should not use 0 as an octet value, except as the last entry in the IP address in aNMS element routing table, or as part of a Mask IP Address and its correspondingoctet in the Destination IP Address.

&�)'� � ��

The NMS element ports are the actual connections by which the element communicates withthe outside world. Each IP address needs to be associated with the port that actually connectsthe local element to the element or sub-net that uses the IP address.

Note: Each port can be associated with more than one IP address.

A DXR 100 with NMS can use the following ports:

• V.24. Used to connect the DXR 100 to the PC running DXR NET.

• NMS In. Used to make NMS connections to other DXR 100 terminals, or to SMA. Connections are made by cable.

• NMS Out. As for NMS In.

• Radio. Used to make any connections made via the radio link.

Note: NMS In and NMS Out are functionally identical, In and Out refers only to the polarity of the physical connectors on the DXR 100.

Using DXR NET NMT



A SMA can use the following ports:

• Setup. Used to connect the SMA to the PC running DXR NET.

• NMS In. Used to make NMS connections to other SMA, or to DXR 100 terminals. Connections are made by cable.

• NMS Out. As for NMS In.

• AUX A to AUX D. Used to connect the SMA to the AUX port on a DXR 700.

• V.24 A to V.24 D. Used to connect the SMA to the V.24 port on a DXR 200 andDXR 700.

• Ethernet. Used to make any connections made via a LAN or a Router.

Note 1: NMS In and NMS Out are functionally identical, In and Out refers only to thepolarity of the physical connectors on the SMA.

The V.24 entry in a routing table refers to the DXR 100 V.24 port, the DXR 200V.24 port, and the SMA Setup port.

,��)��5� ��

Sub-nets are used to make the DXR NMS network more manageable by dividing the NMSelements into groups. They reduce the number of IP addresses a NMS element needs to know,and also make it easier to add new NMS elements to the network.

As already recommended, the second octet in the IP address is used to set the sub-net addressof the NMS element. By using an IP mask, you can set up a NMS element to route allmessages with the same second octet via a specific port. Therefore, an element only needs oneIP address to communicate with the elements of another sub-net, not the specific IP addressesof all the elements.

Since a NMS element can communicate with all the NMS elements in another sub-net using ageneral address for the sub-net, the only specific IP addresses it needs to know are thosebelonging to the elements in its own sub-net. This means that when new NMS elements areadded to a sub-net, only the elements in that sub-net need to have the new IP addresses added.Elements outside the sub-net do not need any additions, as they only require the sub-netaddress to communicate with the sub-net members, and any new members will have the samesub-net address as the existing members.

Sub-net Design GuidelinesThe only major restriction on the sub-net design is that each NMS element can only hold up tofifty IP addresses, i.e the sum of the number of NMS elements in a sub-net; and the number ofsub-nets it connects to cannot exceed fifty. The following guidelines apply:

• The sub-nets should match the network topology.

• If possible, there should be no more than ten NMS element per sub-net.

• The design should take into account any potential increase in the size of the network.

Using DXR NET NMT



A quick method for determining the number and size of any sub-nets on your network is tocalculate the root of the number of NMS elements (or the likely number after any expansion),then round this off to the nearest whole number to get the number of sub-nets. You can thendivide the NMS elements between the sub-nets, trying to keep the same number of elements ineach sub-net. For example, for a network with 17 elements, the number of sub-nets would befour (root 17 = 4.123), and you would have three sub-nets with four NMS elements, and onewith five.

�� .��

You can use DXR NET to create a blueprint for a NMS network using the followingprocedure:

Note: We advise you create the blueprint while working offline.

Procedure



Step 3: The Explorer Tree pane will have the Network icon followed by “Network” at thetop of the column. Click on “Network”, type in the name you have given to thenetwork, then press <Enter>.

Step 4: To add a site to the blueprint, right-click on the Network icon in the Explorer Treepane, then select Add Site from the drop-down menu. The Site icon will appear inthe pane, followed by “Site n”, where “n” relates to the number of sites already inthe blueprint.

Step 5: Select the Site icon for the site you have just added in the Explorer Tree pane. TheSite Information page appears in the workspace. Enter the name you have given thesite into the Site Name field. You can also add the Description and Contact Details(for the person responsible for the site) into the relevant fields in the page. Whenyou are satisfied with the details, click on the Commit button in the Toolbar.

Step 6: Repeat Steps 4 and 5 until you have added all the other sites to the blueprint.

Step 7: To add network elements to a site, right-click on the Site icon in the Explorer Treepane, then select Add Network Element from the drop-down menu. Select the typeof element you want to add to the site from the Add Network Element window asdescribed in Adding Network Elements. The icon for the terminal will appear in theExplorer Tree pane, followed by the default name. Click on the default name, typein the name you have given to the terminal, then press <Enter>.

Step 8: To import an already saved configuration file for a network element to a site,right-click on the Site icon in the Explorer Tree pane, then select Import NetworkElement from the drop-down menu. In the Import Configuration window, select thepreviously saved configuration file for the terminal, then click Open. The icon forthe element will appear listed under the site in the Explorer Tree pane, followed bythe file name. If you want to give the terminal a new name, click on the currentname, type in the name of your choice, then press <Enter>.

Using DXR NET NMT



Step 9: Select the element you have just added or imported, then go through each of theavailable tabbed pages in the Configuration workspace. Either accept the defaultsettings, or enter the values you require. For NMS elements, you should set the IPaddress of the element in the IP Address Table, and also set up the element routingtable. Select the Commit button from the DXR NET toolbar to save any changes youmake to the blueprint.

Step 10: Repeat Steps 7 to 9 as required for the other sites on the network.

Step 11: When you have completed your design, select File from the menu bar, and then Savefrom the drop-down menu to save the blueprint for future reference.



'/�� 3�&�).��

In this example, you have set-up a simple network servicing a set of coast guard stations. Thecurrent requirement is for a single link between the regional control station and the branchstation in the local port, and a single link between the regional control station and awatchtower at the local beach. More such towers are to be installed in the immediate future,so you have decided to use a DXR 700 under SMA control for this link, making it easier toadd links later. The link to the port is well-established and unlikely to change and can becovered by a DXR 124 link. You want to be able to monitor the whole network while attachedto any NMS element, so both the DXR 124 terminals have an NMS board, and there is anNMS connection running between one of the SMAs and one of the DXR 124 terminals.

DXR 770 DXR 770

DXR 124 DXR 124SMA SMA

Figure 35: NMS Blueprint Example – Network Diagram

NMS Network Naming ConventionsThe first stage in designing the network blueprint is to decide which names you are going touse in the blueprint. As with the non-NMS network, you should try and select names that aremeaningful to you and to anyone else who may have cause to use the blueprint. At the sametime, the names should be short enough to be viewed without difficulty in the Explorer Treepane. The network and site names are similar to the non-NMS network, but the SMA andNMS boards have a slightly different convention, and the DXR 700 terminal names nowcontain a reference to the SMA AUX port they are connected to.

Your first task is to give the network a name. The main reason for this is to enable you toeasily identify the blueprint file. As the network is to service three coastguard stations, youdecide to call it COASTGUARD.

Your next task is to select the names for the sites. As there is only one site at each location,you decide to name the sites TOWN, PORT and BEACH.

Using DXR NET NMT



You can now select the NMS element names. The most useful information you can use is thelocation of the element, the type of element, and the IP address of the element. You caninclude these details in the names, site first, then element type, followed by IP address. Thesite name can be shortened to be viewed in the Explorer Pane, but you should ensure that anyshortened names retain enough detail to be clearly identified by anyone who will use theblueprint. At the moment, you have not created the IP addresses, so these will be added to theNMS element names later. In this case, the names are:

• TOWN SMA

• BEACH SMA

• TOWN NMS

• PORT NMS

You can now select the terminal names. The most useful information you can use is the linkthe terminal belongs to, and the end of the link the terminal is situated. Also, the names for theterminals under SMA control should indicate which AUX port they are attached to on theSMA. You can achieve this by including the names of the local and remote sites in theterminal name, giving the local site name first. The names should be separated with a hyphen,and can be shortened to be viewed in the Explorer Pane. For example, the DXR 124 terminalat the TOWN site could be named TOWN-PORT, or TWN-PRT. You should ensure that anyshortened names retain enough detail to be clearly identified by anyone who will use theblueprint. The terminals under SMA control end in a letter, which designates the AUX portthey are connected to.

The terminal names are therefore:

• TOWN-BEACH-A

• BEACH-TOWN-A

• TOWN-PORT

• PORT-TOWN

BEACH-TOWN-A

TOWN-BEACH-A

TOWN NMS

BEACH SMA

TOWN SMA

TOWN-PORT

PORT NMS

PORT-TOWN

Figure 36: NMS Blueprint Example – Element Names

Creating the NMS Element IP AddressesThe next part of designing the network blueprint is to create IP addresses for the NMSelements. As part of this, you should decide if you are going to use sub-nets. In this case,since the network uses different terminal types, you decide to separate the DXR 124 link fromthe link under SMA control.

Using DXR NET NMT



There are two SMAs and two DXR 124 terminals, so the total number of NMS elements isfour. Using the rule given previously gives two sub-nets of two NMS elements. Place theSMAs and the DXR 700 terminals they control in one sub-net, and the two DXR 124terminals in the other. Give the first sub-net an address of 1, and the second an address of 2.

From the sub-net addresses, you know that the SMA IP address will begin with 10.1, and theDXR 124 terminal IP addresses will begin with 10.2. You decide to designate the SMAconnected to the DXR 124 as Element 1 of its sub-net, and the other as Element 2. Similarly,you designate the DXR 124 attached to the SMA as Element 1 of its sub-net, and the other asElement 2. The last octet of the addresses identifies the port the NMS element uses tocommunicate with an attached PC. By convention, this is normally set to 1.

AUX A AUX A

BEACH-TOWN-A

TOWN-BEACH-A

TOWN NMS 10.2.1.1

BEACH SMA

10.1.2.1

TOWN SMA

10.1.1.1

TOWN-PORT

PORT NMS 10.2.2.1

PORT-TOWN

Figure 37: NMS Blueprint Example – NMS Element IP Addresses

You have now created IP addresses for all the NMS elements on the network, and can addthese to the NMS element names, and then create the routing table entries.

Creating the Routing Table EntriesThe routing table for each NMS element sets up the ports the element uses to communicatewith the IP addresses. Each table row comprises:

• The Destination IP Address.

• The Mask IP Address.

• The port on the NMS element connected to the Destination IP Address.

Each table must contain the element's IP address, and the IP addresses it uses to communicatewith the other NMS elements on the network.

Consider the TOWN SMA whose IP address is 10.1.1.1. It is connected to any attached PC byits V.24 (Setup) port. It is also connected to the BEACH SMA via a DXR 700 radio link on itsAUX A port, and to the DXR 124 terminals via its NMS In port. The IP address of theBEACH SMA is 10.1.2.1, and the addresses of the NMS boards in the TOWN-PORT andPORT-TOWN DXR 124 terminals are 10.2.1.1 and 10.2.2.1 respectively. Because there isonly one IP address per element, the last octet is not required to designate a route in the table.The last octets of the Destination and Mask IP addresses are set to 0. Finally, only one route isrequired for the NMS connection to the DXR 124 terminals. The routing table is therefore:

Destination IP Address Mask IP Address Port

10.1.1.0 255.255.255.0 V.24

10.1.2.0 255.255.255.0 AUX A

10.2.0.0 255.255.0.0 NMS In

Using DXR NET NMT



V.24

10.2.1.0 10.2.2.0

NMS In

AUX A

TOWN-BEACH-A

10.1.2.0

TOWN SMA

10.1.1.1 10.1.1.0

(PC)

Radio

Figure 38: NMS Blueprint Example – TOWN SMA Routing

The routing table for the BEACH SMA is:


10.1.2.0 255.255.255.0 V.24

10.1.1.0 255.255.255.0 AUX A

10.2.0.0 255.255.0.0 AUX A

Note that this SMA “sees” the DXR 124 terminals via the radio link, so the connection to the10.2.0.0. address is through AUX A.

Radio

BEACH-TOWN-A

10.1.1.0 10.2.1.0 10.2.2.0

BEACH SMA

10.1.2.1

10.1.2.0 (PC)

V.24

AUX A

Figure 39: NMS Blueprint Example – BEACH SMA Routing

The routing table for the TOWN NMS is:


10.2.1.0 255.255.255.0 V.24

10.2.2.0 255.255.255.0 Radio

10.1.0.0 255.255.0.0 NMS Out

NMS Out

10.1.1.0 10.1.2.0

V.24

TOWN NMS

10.2.1.1

10.2.2.0

10.2.1.0 (PC)

Figure 40: NMS Blueprint Example – TOWN NMS Routing

The routing table for the PORT NMS is:

Using DXR NET NMT




10.2.2.0 255.255.255.0 V.24

10.2.1.0 255.255.255.0 Radio

10.1.0.0 255.255.0.0 Radio

Note that this NMS board “sees” the SMAs via the radio link, so the connection to the10.1.0.0 address is through the Radio port.

V.24

Radio

PORT NMS

10.2.2.1

10.1.1.0 10.1.2.0 10.2.1.0

10.2.2.0

Figure 41: NMS Blueprint Example – PORT NMS Routing

You can now begin to create the blueprint.

Creating the Blueprint



Step 3: The Explorer Tree pane will have the Network icon followed by “Network” at thetop of the column. Click on “Network”, type in COASTGUARD, then press<Enter>.

Step 4: Right-click on the Network icon in the Explorer Tree pane, then select Add Sitefrom the drop-down menu. The Site icon will appear in the pane, followed by “Siten”, where “n” relates to the number of sites already in the blueprint.

Step 5: Select the Site icon for the site you have just added in the Explorer Tree pane. TheSite Information page appears in the workspace. Enter TOWN into the Site Namefield. You can also add the Description and Contact Details (for the personresponsible for the site) into the relevant fields in the page. When you are satisfiedwith the details, click on the Commit button in the Toolbar.

Step 6: Repeat Steps 4 and 5 to add the PORT and BEACH sites to the blueprint.

Step 7: Right-click on the TOWN site icon in the Explorer Tree pane, then select AddNetwork Element from the drop-down menu. Select an SMA from the Add NetworkElement window. The icon for the SMA will appear in the Explorer Tree pane,followed by the default name. Click on the default name, and type in TOWN SMA10.1.1.1., then press <Enter>.

Step 8: Select TOWN SMA 10.1.1.1. icon in the Explorer Pane, then go through each of theavailable tabbed pages in the Configuration workspace. Either accept the defaultsettings, or enter the values you require. Select the Commit button from theDXR NET toolbar to save any changes you make to the blueprint.

Using DXR NET NMT



Step 9: Right-click on the TOWN SMA 10.1.1.1. icon in the Explorer Pane, then select AddNetwork Element from the drop-down menu. Select a DXR 770 from the AddNetwork Element window. The icon for the DXR 770 will appear in the ExplorerTree pane, followed by the default name. Click on the default name, and type inTOWN-BEACH-A, then press <Enter>.

Step 10: Select TOWN-BEACH-A icon in the Explorer Pane, then go through each of theavailable tabbed pages in the Configuration workspace. Either accept the defaultsettings, or enter the values you require. Select the Commit button from theDXR NET toolbar to save any changes you make to the blueprint.

Step 11: Right-click on the TOWN site icon in the Explorer Tree pane, then select AddNetwork Element from the drop-down menu. Select the DXR 124 UnprotectedTerminal from the Add Network Element window. Ensure the NMS Option checkbox is selected in the window. The icon for the terminal will appear in the ExplorerTree pane, followed by the default name. Click on the default name, and type inTOWN-PORT, then press <Enter>.

Step 12: Select the TOWN-PORT terminal in the Explorer Pane, then go through each of theavailable tabbed pages in the Configuration workspace. Either accept the defaultsettings, or enter the values you require. Select the Commit button from theDXR NET toolbar to save any changes you make to the blueprint.

Step 13: Double click the TOWN-PORT terminal in the Explorer Pane to display the NMSboard icon, and name the board TOWN NMS 10.2.1.1. Then go through each of theavailable tabbed pages in the Configuration workspace. Either accept the defaultsettings, or enter the values you require. Select the Commit button from theDXR NET toolbar to save any changes you make to the blueprint.

Step 14: Right-click on the PORT site icon in the Explorer Tree pane, then select AddNetwork Element from the drop-down menu. Select the DXR 124 UnprotectedTerminal from the Add Network Element window. Ensure the NMS Option checkbox is selected in the window. The icon for the terminal will appear in the ExplorerTree pane, followed by the default name. Click on the default name, and type inPORT-TOWN, then press <Enter>.

Step 15: Select the PORT-TOWN terminal in the Explorer Pane, then go through each of theavailable tabbed pages in the Configuration workspace. Either accept the defaultsettings, or enter the values you require. As the TOWN-PORT terminal alreadyexists in the blueprint, you should select it as the remote terminal for PORT-TOWN.Select the Commit button from the DXR NET toolbar to save any changes you maketo the blueprint.

Step 16: Double click the PORT-TOWN terminal in the Explorer Pane to display the NMSboard icon, and name the board PORT NMS 10.2.2.1. Then go through each of theavailable tabbed pages in the Configuration workspace. Either accept the defaultsettings, or enter the values you require. Select the Commit button from theDXR NET toolbar to save any changes you make to the blueprint.

Step 17: Right-click on the BEACH site icon in the Explorer Tree. Select an SMA from theAdd Network Element window. The icon for the SMA will appear in the ExplorerTree pane, followed by the default name. Click on the default name, and type inBEACH SMA 10.1.2.1, then press <Enter>.

Using DXR NET NMT



Step 18: Select BEACH SMA 10.1.2.1 icon in the Explorer Pane, then go through each of theavailable tabbed pages in the Configuration workspace. Either accept the defaultsettings, or enter the values you require. Select the Commit button from theDXR NET toolbar to save any changes you make to the blueprint.

Step 19: Right-click on the BEACH SMA 10.1.2.1 icon in the Explorer Pane, then select AddNetwork Element from the drop-down menu. Select a DXR 770 from the AddNetwork Element window. The icon for the DXR 770 will appear in the ExplorerTree pane, followed by the default name. Click on the default name, and type inBEACH-TOWN-A, then press <Enter>.

Step 20: Select BEACH-TOWN-A icon in the Explorer Pane, then go through each of theavailable tabbed pages in the Configuration workspace. Either accept the defaultsettings, or enter the values you require. As the TOWN-BEACH-A terminal alreadyexists in the blueprint, you should select it as the remote terminal for BEACH-TOWN-A. Select the Commit button from the DXR NET toolbar to save any changesyou make to the blueprint.

Step 21: Select IP Address Table from the Configuration menu, and enter the IP addresses forall the NMS elements in the network.

Step 22: You have now completed the blueprint. Select File from the menu bar, and thenSave from the drop-down menu to save the blueprint for future reference.


You are now returned to the PC desktop. You can now use the blueprint to connect to thenetwork as described in “Connecting to the Network with a Network Blueprint”.

Using DXR NET NMT



) ��& �*��-.�� '5��

You can send blueprints as e-mail attachments provided:

• You send both the .net file and the .dxr folder associated with the blueprint.

• You send the files as a ZIP file.

You should also ensure both the files are saved to the same location on the receiving PC. Asuitable procedure is as follows:

Procedure

Step 1: Using Windows Explorer, locate the .net file and the .dxr folder associated with theblueprint (these will both have the name you saved the blueprint under).

Step 2: Use WinZip to compress the file and folder to the same ZIP file.

Step 3: Attach the ZIP file to an e-mail sent to the receiving PC.

Step 4: At the receiving PC, extract the attached ZIP file to a location on the PC hard drive.

Step 5: Start up DXR NET on the receiving PC, and check that you can open the blueprint.

#��-��*��$%&'�*��-��& �*��-'� � ��Although you can use DXR NET to design a network blueprint while your PC is offline, youwill need to connect your PC to a DXR 100, a DXR 700 or a SMA to view or modify theconfiguration data of an existing network.

& �*��-B��"

Even with a full blueprint loaded, your ability to view a site or network element on thenetwork depends on two things:

• The type of network element your PC is connected to.

• For remote elements (ie, elements accessed via a radio link), whether the radio link isoperational.

• When the connection is to a DXR 100 without a NMS board, or a DXR 700, you will beable to access only the data stored in the local and terminal remote terminals.

• When the connection is to a SMA, or a DXR 100 with the NMS option, you will be ableto access the data from any DXR 100s, DXR 700s or SMAs on the network.

Note: You will only be able to access data from network elements at the remote end of anylink when the link is operational.

Using DXR NET NMT



� ��

Terminal connections are used to connect to a DXR 700, or DXR 100 without NMS board.

Note: DXR NET will not allow you to use a Terminal connection to connect to a DXR 700under SMA control. You should use a NMS connection to the SMA instead.

Terminal Connection to a DXR 700To make a terminal connection from your PC to a DXR 700, connect the supplied cablebetween the selected COM port on your PC and the V.24 connector on the DXR 700 PMA.

Figure 42: DXR 700 PMA Front Panel Layout - location of connector V.24

Terminal Connection to a DXR 100 (without NMS board)To make a terminal connection from your PC to a DXR 100 without NMS option, connect thesupplied cable between the selected COM port on your PC and the V.24 connector on thefront panel of the DXR 100.

Figure 43: DXR 100 Front Panel Layout - location of connector V.24

Using DXR NET NMT



&�)��

NMS connections are used connect to a SMA, or to a DXR 100 or DXR 200 with NMSoption.

Note: Your PC must have Windows® “Dial-Up” Networking enabled for NMSconnections. Refer to Section 3 for details.

NMS Connection to a SMANMS connections behave like a modem connection using Windows® “Dial-Up” Networking.They can be made directly to the SMA, or via the telephone network using a modem.

For a direct connection, you select the NMS connection driver in place of a modem driver.

Note: The name of the driver for the NMS connection is set when you install Windows®“Dial-Up” Networking, and when the DMC Direct Connection driverNMSMODEM.INF is installed.

Direct NMS connections to a SMA are made with the supplied cable. To connect to a SMA,connect the supplied cable to between the selected COM port on your PC and the Setupconnector on the SMA.

Figure 44: SMA Front Panel Layout - location of Setup connector

The procedure for modem connections is the same as for the direct NMS connection, exceptthat you select the modem driver instead of the NMS connection driver. The modem at theSMA end of the connection should be attached to the SMA Setup port using the cablesupplied for this purpose by DMC. Consult the instructions that were supplied with yourmodem for further details.

Note: Connections via a modem are slower than direct connections.

NMS Connection to DXR 100 with NMS boardThese are the same as SMA connections, except for the following cable connection details:

• For a direct NMS connection, the supplied cable is connected to the V.24 port on theDXR 100.

• For a connection via a telephone network, the modem at the DXR 100 end is connected tothe V.24 port on the DXR 100 via the cable supplied by DMC for this purpose.

Using DXR NET NMT



Connection to DXR 200These are the same as SMA connections, except for the following cable connection details:

• For a direct NMS connection, the supplied cable is connected to the V.24 port on theDXR 200.

For a connection via a telephone network, the modem at the DXR 200 end is connected to theV.24 port on the DXR 200 via the cable supplied by DMC for this purpose.

Connect to the SMA as described above. Connect a V.24 cable from a V.24 connector on theDXR 2-00 CTC module, or via a null modem to the DTI connector on the neon of the DXR200 module.

'��

Ethernet connections are used connect to a SMA.

To use the Ethernet connection:

• Your PC must have an Ethernet port set up.

• You must have a hub or cross-over cable.

• The SMA LAN connection (direct or via a router) must be via the LAN port on the SMA,not the SMA Setup port.

• You must have set the IP address of the SMA.

A successful Ethernet connection is indicated by the network icon in the lower right-handcorner of the DXR NET GUI.

) � �� $%&'�� "� ��0��

You can choose three types of DXR net interface:

• Terminal Connection Used for direct connection between the PC and a DXR 700, or aDXR 100 without the NMS option.

• NMS Connection Used for a direct or modem connection to a SMA or a DXR 100 withNMS option.

• Ethernet Used for connection to a SMA over an Ethernet LAN.

SELECTING THE CONNECTION. You must select the right type of connection for thenetwork element you are trying to connect to. If you select the wrong type, DXR NET willnot be able to connect to the network, and will tell you it cannot find a valid networkelement.

ProcedureTo select a DXR NET connection type, proceed as follows:

Note: DXR NET will not allow you to select the connection type while you are connectedto a DXR NETwork.

Step 1: Run DXR NET.

Step 2: Select the Communication Setup option from the Tools menu.

Using DXR NET NMT



Step 3: To connect to a DXR 700, or a DXR 100 without NMS board, select the TerminalConnection button. If required, you can then select the COM port that DXR NET

uses on your PC in the Options section.

Step 4: To connect to a SMA, or a DXR 100 with NMS board, select the NMS Connectionbutton. If required, you can then select the driver (NMS DMC Direct Connection ormodem driver) that DXR NET uses in the Options section. As a connection via adial-up modem will be slower, select the Dial-up Modem Delay check box if you areusing a modem. This will increase the time DXR NET waits for a response beforedeciding the connection has failed.

Step 5: Select the Ethernet button to connect to a SMA via a LAN (directly, or via a router).

Step 6: Click the Save Settings button if you wish to make the selected connection type thedefault setting,

Step 7: Click the OK button to change the connection type to the connection type.

DXR NET will now use the connection type you have selected.

�� %��& �*��-*��.��

To connect DXR NET to the radio network with a blueprint loaded, first ensure you are usingthe right type of connection for the element your PC is attached to, then proceed as follows:

Note: This procedure is for an already existing network. To configure a brand newnetwork element, refer to the section in this manual that details the element.

Procedure


Step 2: Select the Configuration workspace from the Workspace Selection screen.

Step 3: Select File, Open from the menu bar, and load the blueprint for the network you areconnected to into DXR NET.

Step 4: Select the Connect button from the DXR NET toolbar. When the connection issuccessfully completed, the icon for the network element you are connected to willhave a plug symbol in the Explorer Pane. You can now use the Configuration,Commissioning and Maintenance Workspace functions with any element you canaccess. Any elements that you cannot access will be shown greyed-out in theblueprint.

Step 5: When you are finished using the functions, click on the Disconnect button in theDXR NET toolbar, then click on File in the menu bar, and select Exit from the Filemenu.


�� %��& �*��-*��.�� ?!�� "@

You can use the Autodiscovery feature to automatically create a blueprint for the link you areconnected to in the Explorer Pane.

Using DXR NET NMT



Note 1: The Autodiscovery feature only reads site and network element names. You mustread the configuration from a network element before carrying out any operations onit.

Note 2: The blueprint created by the Autodiscovery feature will only contain remoteelements, ie, the elements at the other end of the link, if the link is operational.

Note 3: The Autodiscovery feature cannot be used if you are connected to the network viaEthernet.

Note 4: If the Autodiscovery feature detects unsupported software in an element, it will setthe element in the blueprint to a supported software version. This will enableDXR NET to communicate with the element.

To use the Autodiscovery feature, first ensure you are using the right type of connection forthe element you are connecting to, then proceed as follows:

Procedure



Step 3: Select the Connect button from the DXR NET toolbar. The Autodiscovery featurewill create a blueprint of the link you are connected to, and display this in theExplorer Tree pane. You can now read the configuration from any element you cansee in the blueprint, and use the Configuration, Commissioning and MaintenanceWorkspace functions as required.

Step 4: When you are finished using the functions, click on the Disconnect button in theDXR NET toolbar, then click on File in the menu bar, and select Exit from the Filemenu.


Note: DXR NET does not auto-discover with DXR 200.

Using DXR NET NMT



,��$%&'��

��

This section covers the operations you should take to configure a terminal. You can do this inone of two ways:

Note: The terminal should have the correct frequency loaded, and that the networkblueprint (if used) should contains the complete and correct configuration data.

• using a master blueprint (preferred method). The network designer uses DXR NET tocreate a master network blueprint or Design blueprint containing all the informationrequired to configure the terminals. This blueprint is then used at the time of installationto load the terminal configurations. Any changes made in the field can be saved in theblueprint, which now becomes the Field blueprint. This should then be sent to the networkoperations centre (NOC), allowing them to have an accurate blueprint that can be used forfuture visits to the site, or from the central office. The blueprint constructed from all thefield blueprints is called a Commissioned blueprint, as it reflects the unique, real, networkthat is installed.

• using configuration sheets. The network installation teams install the terminal, then usethe Autodiscovery feature to build a blueprint containing the installed terminal. They thenwork through the tabbed pages in the Configuration Workspace, making any changesrequired to bring the terminal into line with the values given in the configuration sheets.The installed configuration should then be saved to a blueprint, which now becomes theField blueprint. The procedure is then the same as for a Field blueprint created using amaster network blueprint.

ABORT BUTTON. Whenever you use DXR NET to make changes to a DXR terminal, youcan stop the change action by selecting the Abort button in the displayed dialog box.However, if you do this, DXR NET will simply stop sending commands to the terminal. Thiscan leave the terminal and any associated link(s) in an undesired state, with the terminalsoftware not reflecting the correct settings for the link. You will then need to set the correctvalues in DXR NET and re-send them to the element. For these reasons, we recommend thatbefore you start making changes you save the current terminal configuration, and that youhave a hard copy of the desired settings available.

WRITING CONFIGURATION CHANGES TO A TERMINAL. Whenever you writeconfiguration changes and data to a terminal, there is a momentary loss of traffic on thelink. We advise therefore that you carry out any changes to the configuration when the linkis either out of service, or at times when link traffic is at a minimum.

REMOTE TERMINAL CHANGES. Some actions can cause the loss of communication tothe remote terminal in a link, requiring manual intervention at the remote terminal to re-establish the link. We therefore advise you take great care when making any changes thatcould impact communication with the remote terminal.

DMC Stratex Networks advises that when checking or modifying the data, you have hardcopy of the expected values available to refer to before beginning the procedure.

Using DXR NET NMT



DMC Stratex Networks advises that you save the configuration data of all your terminalsafter initial setup and after any changes are made.

�� ,�� .��

This procedure covers configuring either a DXR 700 or a DXR 100 without NMS from amaster blueprint. You will use DXR NET to:

• check the terminal name

• load the master blueprint

• make any required changes to the terminal configuration

• save any changes that are made to the terminal configuration for later use

• save the modified Field blueprint for later use in a Commissioned blueprint

• for the second terminal of a link, confirm that the link is operational by connecting to thefar end terminal and checking for alarms

The following assumptions have been made:

The terminal has been installed, connected to power and the antenna, and has beensuccessfully powered up.

The DXR NET PC is connected to the V.24 connector on the terminal front panel, except whenthe terminal is a DXR 700 under the control of a SMA. In this case, the PC is connected to theSetup connector on the controlling SMA.

You know what the name of the terminal is in the master blueprint.

Note 1: Great care should be taken that the parameters are correct before writing anychanges to a terminal. For example, writing incorrect frequencies back to theterminal will result in the loss of the operational link, which could require on-siteactions to recover.

Note 2: If you attempt to write blueprint default values to a terminal, DXR NET will ask youto confirm the action.

Procedure


Step 2: Select the Configuration Workspace from the Workspace Selection window.

Step 3: Select the Connect button from the DXR NET toolbar. After autodiscovery issuccessfully completed, a blueprint containing the terminal will appear in theExplorer Tree. Select the terminal, and click the Read Configuration button to readthe terminal configuration.

Step 4: Check that the name of the terminal matches the name in the master blueprint. If not,right-click on the terminal icon in the Explorer Tree, select Rename from the drop-down menu, then change the name to match the blueprint.

Step 5: Select the Disconnect button, then click File in the DXR NET menu bar, and selectOpen from the drop-down menu. Load the master blueprint by selecting theblueprint file, then click the OK button.

Using DXR NET NMT



Step 6: Select the Connect button from the DXR NET toolbar. After connection issuccessfully completed, select the terminal in the Explorer Tree, then click the ReadConfiguration button.

Step 7: Go through the Configuration workspace pages, making any changes as required.Refer to the specific operations detailed later in this section for details. Select theCommit button after making any changes to ensure you save them to the blueprint.

Step 8: When you are satisfied with the details in the Configuration workspace pages, clickthe Write Configuration button in the DXR NET toolbar to load the configuration tothe terminal. DXR NET will open a window asking to proceed. Ensure that you havethe correct terminal selected in the Explorer Tree, and select Start to write to theterminal.

Step 9: After any changes have been written to the terminal, right-click on the terminal inthe Explorer Tree, and select Export Configuration. Select the destination for the filecontaining terminal settings, then the OK button.

Step 10: Select Save or Save As from the File menu to save the blueprint. This blueprint isknown as the "field blueprint".

Step 11: If this is the second terminal of a link, the link should now be operational. Toconfirm this, check that you can access the far end terminal by clicking on its icon inthe Explorer Tree, and then select the Commissioning Workspace to check if anyalarms are present.

Step 12: When you are finished viewing or modifying the terminal configuration, click on theDisconnect button in the DXR NET toolbar, then select Exit from the File menu.

��

This procedure covers configuring a DXR 700 terminal working from configuration sheets.You will use DXR NET to:

• use the autodiscovery feature to connect to the terminal

• make any required changes to the terminal configuration

• save any changes that are made to the terminal configuration for later use


• for the second terminal of a link, confirm that the link is operational by connecting to thefar end terminal and checking for alarms


the terminal has been installed, connected to power and the antenna, and has beensuccessfully powered up

the DXR NET PC is connected to the V.24 connector on the terminal front panel, except whenthe terminal is a DXR 700 under the control of a SMA. In this case, the PC is connected to theSetup connector on the controlling SMA

you know what the name of the terminal should be

Using DXR NET NMT



Note 1: Great care should be taken that the parameters are correct before writing anychanges to a terminal. For example, writing incorrect frequencies back to theterminal will result in the loss of the operational link, which could require on-siteactions to recover.

Note 2: If you attempt to write default values to a terminal, DXR NET will ask you toconfirm the action.

Procedure



Step 3: Selecting the Connect button from the DXR NET toolbar. After autodiscovery issuccessfully completed, a blueprint containing the terminal will appear in theExplorer Tree.

Step 4: Click the Read Configuration button from the DXR NET toolbar to read the terminalsettings into the Configuration workspace.

Step 5: Go through the Configuration workspace pages, making any changes as required.Refer to the specific operations detailed later in this section for details. Select theCommit button after making any changes to ensure you save them to the blueprint.

Step 6: When you are satisfied with the details in the Configuration workspace pages, clickthe Write Configuration button in the DXR NET toolbar to load the configuration tothe terminal. DXR NET will open a window asking to proceed. Ensure that you havethe correct terminal selected in the Explorer Tree, and select Start to write to theterminal.

Step 7: After any changes have been written to the terminal, right-click on the terminal inthe Explorer Tree, and select Export Configuration. Select the destination for the filecontaining terminal settings, then the OK button.

Step 8: Select Save or Save As from the File menu to save the blueprint. This blueprint isknown as the "field blueprint".

Step 9: If this is the second terminal of a link, the link should now be operational. Toconfirm this, check that you can access the far end terminal by clicking on its icon inthe Explorer Tree, and then select the Commissioning Workspace to check if anyalarms are present.

Step 10: When you are finished viewing or modifying the network, click on the Disconnectbutton in the DXR NET toolbar, then select Exit from the File menu.


�$%344� ��"� ��

Refer to Appendix G

Using DXR NET NMT



.�� *��-��

As terminals are installed and become operational, it is useful to have an updated blueprint atthe central office and in the operations centre. This blueprint should reflect the latestconfiguration data, and any operational data about the network. Engineers travelling to sitesshould have this blueprint with them , in case a terminal needs to be replaced. This blueprintis known as the "custom" blueprint, and should be created by importing configuration files,created from the "field" blueprints.

The network operations centre can discover the terminal configurations if the terminal type,physical connections and IP address are known, and create a "custom" blueprint by readingthe data directly from the terminals.

Note: Great care should be taken that the parameters are correct before writing anychanges to a terminal. For example, writing incorrect frequencies back to theterminal will result in the loss of the operational link, which could require on-siteactions to recover.

,��$%&'�� &�),��

��

This section covers the operations you should take to configure a NMS unit (SMA orDXR 100 with NMS board) using a master blueprint. The network designer uses DXR NET tocreate a master network blueprint or Design blueprint, containing all the information requiredto configure the unit. This blueprint is then used at the time of installation to load the unitconfiguration. Any changes made in the field can be saved in the blueprint, which nowbecomes the Field blueprint. This should then be sent to the network operations centre (NOC),allowing them to have an accurate blueprint that can be used for future visits to the site, orfrom the central office. The blueprint constructed from all the field blueprints is called aCommissioned blueprint, as it reflects the unique, real, network that is installed.

ABORT BUTTON. Whenever you use DXR NET to make changes to a network element,you can stop the change action by selecting the Abort button in the displayed dialog box.However, if you do this, DXR NET will simply stop sending commands to the element. Thiscan leave the element and any associated link(s) in an undesired state, with the elementsoftware not reflecting the correct settings for the link. You will then need to set the correctvalues in DXR NET and re-send them to the affected elements. For these reasons, werecommend that before you start making changes you save the current elementconfiguration, and that you have a hard copy of the desired settings available.

DMC Stratex Networks advises that when checking or modifying the data, you have hardcopy of the expected values available to refer to before beginning the procedure.

DMC Stratex Networks advises that you save the configuration data of all your networkelements after initial setup and after any changes are made.

��&�),��

This procedure covers configuring a NMS unit from a master blueprint. You will useDXR NET to:

• connect to the unit using autodiscovery

Using DXR NET NMT



• set the unit IP address

• load the master blueprint

• connect to the unit in the blueprint

• make any required changes to the unit configuration

• save any changes that are made to the unit configurations for later use



• the unit has been installed, connected to power, and has been successfully powered up

• the DXR NET PC is connected to either the Setup connector on the SMA front panel or theV.24 port on the DXR 100 front panel

• you know what the IP address of the unit is in the master blueprint

Note 1: Great care should be taken that the parameters are correct before writing anychanges to an unit.

Note 2: If you attempt to write default routing table values to a NMS unit, DXR NET will askyou to confirm the action.

Procedure



Step 3: Select the Connect button from the DXR NET toolbar. DXR NET will performautodiscovery, and a blueprint containing the NMS unit you are attached to willappear in the Explorer Tree window. The NMS unit you are attached to will have asmall red plug symbol.

Step 4: Select the NMS unit in the Explorer Tree, and set the unit Real Time Clock and IPaddress (refer to Setting the Real Time Clock and Setting the IP Address proceduresin this section).

Step 5: Once the new address has been written, the NMS unit will drop the networkconnection to your PC, and DXR NET will ask if you want to reconnect. Select No,

Step 6: Open the "master" blueprint.

Step 7: Select the Connect button from the DXR NET toolbar. DXR NET will mark the NMSunit you are connected to on the Explorer tree with a small red plug symbol. Ensurethat the correct unit is selected in the tree before attempting to load the configurationfrom the blueprint. If the correct unit is not selected, check the unit IP address in theblueprint, click the Disconnect button in the DXR NET toolbar, close the blueprint,then go back to Step 3.

Using DXR NET NMT



Step 8: After you have ensured the correct NMS unit is selected, go through each of thetabbed pages in the Configuration Workspace, making any required changes (referto the procedures given later in this section for details). After you have completedany required changes, click on the Commit button to save them to the blueprint.

Step 9: Select the Write Configuration button from the DXR NET toolbar, then select Startto load the configuration details to the SMA. When the configuration has loaded,press OK. If you made any changes in Step 7, right-click on the NMS unit icon inthe Explorer Tree, then select Write Configuration from the drop-down menu andsave the unit configuration to file.

Step 10: When you are finished viewing or modifying the network, save the blueprint, clickon the Disconnect button in the DXR NET toolbar, then select Exit from the Filemenu.

) �� !�� &�),��NMS units (SMAs or NMS boards) use IP to communicate with other equipment, eitherdirectly connected, or connected via a network. Because of this, each NMS unit must have itsown unique IP address.

Note: See earlier in this section for a simple IP address selection procedure.

To set the IP address for an NMS unit, connect to the unit (either using the Autodiscoveryfeature or with the network blueprint loaded), then proceed as follows:

Procedure

Step 1: Select the NMS unit in the Explorer Tree.

Step 2: Select Configuration in the menu bar.

Step 3: Select IP Address Table from the drop-down Configuration menu.

Step 4: Double-click on IP address column entry for the NMS unit, and then type in the newaddress.

Step 5: If the field in the IP Address Mask column for the NMS unit IP address is not255.255.255.255, then double-click on the field and type in 255.255.255.255.

Step 6: Click OK, then click on the Write Configuration button

Step 7: If the Target IP address is correct in the displayed window, select the check box nextto the address, then Start. If the address is incorrect, type in the correct IP address ofthe NMS unit you are trying to connect to.

Step 8: When the address has been updated, click Finish.

Step 9: After you have written the new IP address to the NMS unit, the connection to thenetwork will be dropped. DXR NET will then ask you if you wish to reconnect.Select No. The changes you have made will now be reflected in the networkblueprint.

Using DXR NET NMT



) �� 8� �� * �You can change the transmit and receive frequencies and RF output power of a terminal usingthe following procedure.

SETTING THE TERMINAL FREQUENCIES AND TRANSMITTER POWER. Theterminal frequencies and transmitter output power are dependent on the duplexer. Anysoftware changes you make to these settings must reflect the duplexer type and tuning.

Note: In a protected terminal, there will be a set of fields for each radio.

Procedure

Step 1: Select the terminal in the Explorer Tree.

Step 2: Select the Configuration Workspace.

Step 3: Select the Modem/RF Link Setup page.

Step 4: In the Radio section, change the transmit and receive frequencies, or the transmitterpower by using the up/down arrows in the relevant field, or by selecting the relevantfield and typing in the value.

Step 5: After you have finished making your changes, select the Commit button in theToolbar. The changes you have made will be reflected in the network blueprint.

Step 6: If you are not going to make any further changes to the terminal configuration, selectthe Write Configuration button in the Toolbar. The terminal configuration will nowchange to reflect the values set in the blueprint.

) �� &�),��% �� -Both the SMA and the NMS board have an internal clock to synchronize their operations. Toset this clock, proceed as follows:

Note: If the Real Time Clock is not set, an alarm (Real Time Clock not set) is generatedfor the NMS unit. See Appendix A for details.

Procedure


Step 2: Select Configuration in the menu bar.

Step 3: Select Set Real Time Clock from the drop-down menu.

The NMS unit Real Time Clock is now set.

) �� %�� &�),��You can use the following procedure to set up a route by which the NMS unit cancommunicate with any attached PC. For a SMA, the PC will be connected to the Setup port,for a DXR 100 with NMS board, the PC will be connected to the V.24 port.

Using DXR NET NMT



Note 1: The following assumes that you have already changed the NMS unit IP address fromthe default factory setting. If this is not the case, refer to Setting the IP Address for aNMS Unit, then return to this procedure.

Note 2: We advise you set the route to the PC before setting up the routes to any otherequipment.

Procedure



Step 2: Select the Routing Table tabbed page.

Step 3: Press the Insert key on the PC to add a new row to the table.

Step 3: Take the NMS unit IP address, make the last field in the address zero, then enter thisinto the Destination IP Address field of the new row.

Step 4: For the IP address in Step 3, enter 255.255.255.0 in the Mask Address IP column,

Step 5: For the IP address in Step 3, double-click in the Interface column and select V.24from the drop-down list.


Step 7: If you are not going to make any further changes to the terminal configuration, selectthe Write Configuration button in the Toolbar. The NMS unit configuration willnow change to reflect the values set in the blueprint.

) ��,�� %�� &�),��NMS units (SMAs or NMS boards) use IP to communicate with other equipment, eitherdirectly connected, or connected via a network. Each device on the network has a unique IPaddress, and all messages sent using IP will contain the address of the device the message isintended for (i.e. the destination IP address). When a NMS unit receives a message, it looks atthe destination IP address, and uses this to try and route the message to its intendeddestination. The NMS unit therefore needs two sets of information:

• the IP addresses of all the other devices on the network

• the interface it uses to communicate with any specific IP address

This information is contained within the NMS unit Routing Table. You use the Routing Tableto associate each of the IP address the NMS unit needs to know with the interface the unituses to communicate with that address. You can also use masking, so that the unit only needsto use part of an address to determine the message destination.

You can set up the Routing Table for a NMS unit using the following procedure.

Note: The following procedure assumes that you have already selected IP addresses for allthe devices on the network. Refer to earlier in this section for a simple IP addressselection procedure.

Using DXR NET NMT



Procedure



Step 3: Select the Routing Table tabbed page.

Step 4: Press the Insert key on the PC to add a new row to the table.

Step 5: Take the address of one of the IP devices on the network, make the last field in thisaddress zero (e.g. for an IP address of 123.123.123.123 the new address would be123.123.123.0), then enter this new address into the Destination IP Address column.

Step 6: For the IP address entered in Step 5, enter 255.255.255.0 in the Mask Address IPcolumn

Step 7: For the IP address entered in Step 5, double-click the Interface column, and selectthe port you want the SMA to use for devices on this address from the drop-downmenu.

Step 8: Repeat Steps 4 to 7 until you have entered routes to all the other IP devices on thenetwork into the Routing Table


Step 10: If you are not going to make any further changes to the SMA configuration, selectthe Write Configuration button in the Toolbar. The SMA configuration will nowchange to reflect the values set in the blueprint.

) �� )�!��

) �� %��-��

You can set up the radio link ports (AUX and V.24) on an SMA front panel using thefollowing method.

Procedure


Step 2: Select the SMA in the Explorer Tree.

Step 3: Select the Port and EOW Settings tabbed page.

Step 4: In the Port section associated with the connectors you are to configure, click on theLocal Terminal field, and select the name of the terminal the port is connected to.


Using DXR NET NMT




�� '�#�� )�!

You can configure the following:

• Volume in the EOW handset ear piece.

• The PCM Coding Law used to translate analog voice signals into digital pulses fortransmission over DXR 700 auxiliary channel.

• The ringing tones produced by the SMA.

• Whether the analog voice signal from the handset is high pass filtered or not.

You can configure the EOW interface using the following method.

Procedure




Step 4: In the Engineering Order Wire (EOW) section, click on the Ear Piece Volume field,and select the volume from the drop-down list. You can choose between Normal andLoud.

Step 5: In the Engineering Order Wire (EOW) section, click on the PCM Coding Law field,and select the coding law from the drop-down list. You can choose between Lawand A-Law.

Step 6: In the Engineering Order Wire (EOW) section, click on the Ring Modes field, andselect the ringing tone to be generated by the SMA from the drop-down list. You canchoose DXR 700 (default), DXR 200 and DXR 100 tones.

Step 7: In the Engineering Order Wire (EOW) section, enable or disable the Transmit HighPass Filter by clicking on the check box. The function is disabled when the box isempty, and enabled when the box is ticked.



) �� -)�� )�!You can set up the SMA clock source using the following method.

Using DXR NET NMT



Note 1: You would normally set the clock source to build a Clocking Hierarchy for SMAusing SDM boards. See Appendix D for details.

Note 2: For either of the Option 1 or Option 2 selections to be valid, ie, synchronizationsignal coming in via optional daughter board, the relevant slot in the SMA must beoccupied by an appropriate board.

Procedure




Step 4: In the Clock Sources section, click on the Primary field, and select the signal sourcefrom the drop-down list. You can choose between Free-running (default, generatedinternally), one of the four AUX ports (AUX A to D), the NMS In port, the NMSOut port, or one of Option 1 or Option 2.

Step 5: In the Clock Sources section, click on the Secondary field, and select the signalsource from the drop-down list. You can choose between Free-running (default,generated internally), one of the four AUX ports (AUX A to D), the NMS In port,the NMS Out port, or one of Option 1 or Option 2.



) ��,�� )�!!��.��You can set up an alarm board in a SMA using the following procedure:

Note 1: DXR NET will only write the configuration to an alarm board if it finds that theboard type in the SMA matches the type set in the blueprint. You should thereforecheck the type of board in the SMA before attempting set-up. You can check theboard type in the SMA Details page of the Commissioning Workspace.

Note 2: If you change the Electrical State field, you will also need to alter switch settings onthe alarm board, and also links on the board, to match the new signal setting.

Note 3: You must select a number between zero and twenty in the Rate field, and you mustselect an integer value.

Note 4: You can only select the signal state (input/output) for a Mk I alarm board.

Procedure



Using DXR NET NMT



Step 3: Select the External Inputs/Outputs page.

Step 4: Double-click on the Identifier field, and type in the name of the alarm.

Step 5: If you are setting up a Mk I alarm board, double-click on the Type field, and selectInput or Output from the drop-down list.

Step 6: Double-click on the Electrical State field, and choose the appropriate setting fromthe drop-down list. You can choose between current and no current for inputs, andclosed or open for outputs.

Step 7: Select the maximum number of changes to the signal that can be detected per secondby clicking on the Rate field, and either using the up/down arrows, or typing in thevalue.


Step 9: If you are not going to make any further changes to the terminal configuration, selectthe Write Configuration button in the Toolbar. The alarm board configuration willnow change to reflect the values set in the blueprint, as long as the board type in theSMA matches the type in the blueprint.

) �� * �!��You can set the values of forward and reverse power which trigger the terminal ForwardPower Warning, and the Reflected Power Warning (see Appendix B for details). Theprocedure is as follows:

Note 1: You can set the limits to their default values by clicking the Default button.

Note 2: In a protected terminal, there will be a set of fields for each radio.

Procedure



Step 3: Select the Thresholds page.

Step 4: In the Transmit Path section, set the high and low limits for the forward power byusing the up/down arrows in the relevant fields, or by selecting the relevant fieldsand typing in the values.

Step 5: In the Transmit Path section, set the high limit for the reverse power by using theup/down arrows in the relevant field, or by selecting the relevant field and typing inthe value.


Using DXR NET NMT




) �� !+�!��$% 44� ��The AGC Alarm limits are used to define the range over which the AGC voltage can varywithout triggering the AGC Alarm. Refer to Appendix B for details. You can change the AGClow and high limits of a terminal using the following procedure.

Note: You can set the limits to their default values by clicking the Default button.

Procedure




Step 4: In the Receive Path section, set the high and low limits for the AGC by using theup/down arrows in the relevant fields, or by selecting the relevant fields and typingin the values.



) �� %))�!��$%744� ��You can set the range over which the RSSI can vary without triggering the Rx Path Warningalarm (see Appendix B for details). You set the low and high RSSI limits of a terminal usingthe following procedure.

Note 1: You can set the limits to their default values by clicking the Default button.

Note 2: In a protected terminal, there will be a set of fields for each radio.

Procedure




Step 4: In the Receive Path section, set the high and low limits for the RSSI by using theup/down arrows in the relevant fields, or by selecting the relevant fields and typingin the values.

Using DXR NET NMT





) �� %��$%744� ��You can set the modulation a terminal applies to the RF signal using the following procedure.

SETTING THE MODULATION. The modem modulation you can select is dependent onthe modem in the DXR 700 RMA. Any changes you make must match the modulation typeof the modem of the RMA that is installed.

Procedure




Step 4: In the Modem Parameters section, select the modulation you require from drop-down list displayed when you click-on the Modulation field.



) �� /�� ."� �� ) �� The Maximum Correctable Bytes per Second Threshold is used to set the number ofcorrectable bytes that can be received over the radio link before triggering the CorrectableError Limit alarm (see Appendix B for details).

Note: Refer to Appendix C for values of Correctable Bytes per Second.

You can change the Maximum Correctable Bytes per Second Threshold of a terminal usingthe following procedure.

Note: You can set the limit to a default value by clicking the Default button.

Procedure




Using DXR NET NMT



Step 4: In the General section, set the Correctable Bytes per Second by using the up/downarrows in the fields, or by selecting the field and typing in the value.



) �� "��You can change the diversity option of a protected terminal using the following procedure.

SETTING THE TERMINAL DIVERSITY OPTION. The diversity you can select isdependent on the terminal hardware. You must ensure that any changes you make in thesoftware reflect your terminal hardware.

Note: If you select the Frequency Diversity option, you will have to set the frequencies forthe second radio.

Procedure




Step 4: In the Protected & Diversity Options section, select the option you require byclicking the relevant radio button. You can choose between Protected, SpaceDiversity or Frequency Diversity.

Step 5: If you have selected the Frequency Diversity option, select the frequencies yourequire for the two radios in the Radio A and Radio B fields. Refer to Changing theTerminal Frequencies and RF Power for details.



��'� ��!��You can set a network element to create a pre-set alarm action when a specific event occurs.This is known as mapping an event to an action, and is set up in the Action Table page.

Note: The same actions can be set for more than one event.

Using DXR NET NMT



The Action Table page is divided into the Events, Mapped Actions and Inherited Actionspanes. The Events pane lists the events that you can set an action for. The events are listed inthe Windows Explorer tree format. The Mapped Actions pane lists any actions that you havemapped to the alarm presently selected in the Events pane. The Inherited Actions pane listsany actions that are mapped to an alarm higher up in the tree hierarchy than the alarm youhave currently selected.

You can set an event to generate an action using the following procedure:

Procedure


Step 2: Select the network element in the Explorer Tree.

Step 3: Select the Action Table page. The events you can select actions for are displayed ina hierarchical tree in the Windows Explorer format in the Events pane.

Step 4: Move down the levels of the tree in the Events pane, until you can select the eventfor which you want to generate an action.

Step 5: Select the Edit Actions button.

Step 6: In the Edit Actions window, select the Location (i.e. where you want the alarmaction to be produced) and the Action (i.e. what you want to happen when the eventoccurs) from the drop-down list, then click on the Add Action button next to the list.The action will appear in the lower pane of the window. If you decide to remove anaction after selection, select the action in the lower pane, then click on the DeleteAction button next to the drop-down list.

Step 7: Select the OK button in the Add Actions window. The window will close and theaction should now be displayed in the Mapped Actions pane of the Actions Tablepage.



Using DXR NET NMT



% ��!��'� ��You can remove an action that you have enabled on a network element (see Mapping anEvent to an Action) using the following procedure:

Procedure



Step 3: Select the Action Table page. The events you have selected actions for are displayedin a hierarchical tree in the Windows Explorer format in the Events pane.

Step 4: Move down the levels of the tree in the Events pane, until you can select the eventfrom which you want to remove an action. Any actions mapped to the event will bedisplayed in the Mapped Actions pane.

Step 5: Select the action you want to remove in the Mapped Actions pane and click theDelete Actions button. If the action is mapped to a single event, it will disappearfrom the pane. If it is mapped to more than one event, a dialog box will appearallowing you to choose between removing the action from just the selected event, orfrom all the events it has been mapped to.



) ��

) �� "�

You can set the terminal line interface type using the following procedure:

CHANGING THE INTERFACE TYPE. The interface type is dependent on the interfacehardware in the terminal. Any changes you make to the software must reflect the hardware.

Procedure



Step 2: Select the Interface Setup page.

Step 3: Click on the Interface Type field in the Interface section and select the interface typefrom the displayed drop-down list.


Using DXR NET NMT




) �� ' ��

SETTING THE LINE INTERFACE PARAMETERS. The interface capacity and thetributary impedance are both dependent on the hardware in the terminal and the cablingattached to it. Any changes you make to the software must reflect the terminal hardwareand the cabling attached to the terminal line interface.

Note: DMC Stratex Networks supplies cabling matched to the line impedance for the

interface connectors on the terminals.

You can change the terminal line parameters using the following procedure:

Procedure




Step 4: If you wish to change the interface capacity, select the new capacity from the drop-down list displayed when you click on the Interface Capacity field in the Interfacesection.

Step 5: If you wish to change the impedance of a particular tributary, select the relevantentry in the Impedance column of the table in the Tributary section, then use thearrow to display the drop-down list. Select the new impedance from the list.

Step 6: If you wish to change the impedance of all the tributaries to the same value, changethe value of the first tributary as described in Step 4, then click on the Impedancecolumn heading.

Step 7: If you wish to change the commissioned state of a particular tributary, select theTrue or False in the Commissioned column of the table in the Tributary section.Tributaries set to True are commissioned, tributaries set to False areuncommissioned.

Step 8: If you wish to change the commissioned state of all the tributaries to the same value,change the state of the first tributary as described in Step 6, then click on theCommissioned column heading.

Step 9: For interface capacities of 16xE1, if you wish to change the impedance of theWayside Tributary, change the state of the tributary in the Wayside Tributarysection as described in Step 4.


Using DXR NET NMT




) �� ':��

SETTING THE LINE INTERFACE PARAMETERS. The receiver sensitivity and thetributary wayside line build-out are both dependent on the hardware in the terminal and thecabling attached to it. Any changes you make to the software must reflect the terminalhardware and the cabling attached to the terminal line interface.


tributary wayside connector on the PMA front panel.

You can change the terminal line interface parameters using the following procedure:

Procedure




Step 4: If you wish to change the interface receiver sensitivity, select the Rx Sensitivitycolumn of the table in the Tributary section, then double-click to display the drop-down list. Select the new sensitivity from the list. You can choose from Low,Medium (default), or High.

Step 5: If you wish to enable or disable the transmitter level boost function in the lineinterface, select the Tx Level Boost column of the table in the Tributary section,then double-click to display the drop-down list. Select True (enabled) or False(disabled) as required.

Step 6: If you wish to enable or disable the equalizer bypass function in the line interface,select the Equalizer Bypass column of the table in the Tributary section, thendouble-click to display the drop-down list. Select True (enabled) or False (disabled)as required.

Step 7: If you wish to change the commissioned state of the line interface, select theCommissioned column of the table in the Tributary section, then double-click todisplay the drop-down list. Select True (enabled) or False (disabled) as required.

Step 8: If you wish to change the impedance of the Wayside Tributary, change the state ofthe tributary in the Wayside Tributary section as described in Step 7.



Using DXR NET NMT



) �� ) ��

You can change the terminal line interface parameters for a DS1 type interface using thefollowing procedure.



tributary wayside connector on the PMA front panel.

Procedure




Step 4: If you wish to change the line build out of a tributary, select the Line Build Outcolumn of the table in the Tributary section, then double-click to display the drop-down list. Select the new build-out from the drop-down menu. You can choosebetween lengths of 0-133 feet (default), 133-266 feet, 266-399 feet, 399-533 feetand 533-655 ft.

Step 5: If you wish to change the commissioned state of a tributary, select the check box inthe Commissioned column of the table in the Tributary section, then double-click todisplay the drop-down list. Select True (enabled) or False (disabled) as required.

Step 6: If you wish to change the coding used on the line interfaces, select the LineEncoding field in the Tributary section, then double-click to display the drop-downlist. Select the encoding from the list.

Step 7: If you wish to change the impedance of the Wayside Tributary, select the column inthe Wayside Tributary section, and select the new build-out from the drop-down list.You can choose between lengths of 0-133 feet (default), 133-266 feet, 266-399 feet,399-533 feet and 533-655 ft.



Using DXR NET NMT



) �� ):��

You can change the terminal line interface parameters for a DS3 type interface using thefollowing procedure.



tributary wayside connector on the DXR 700 PMA front panel.

Procedure




Step 4: If you wish to change the interface receiver sensitivity, select the Rx Sensitivitycolumn of the top table in the Tributary section, then double-click to display thedrop-down list. Select the new sensitivity from the list. You can choose from Low,Medium (default), or High.


Step 6: If you wish to enable or disable the equalizer bypass function in the line interface,select the Equalizer Bypass column of the table in the Tributary section, thendouble-click to display the drop-down list. Select True (enabled) or False (disabled)as required.

Step 7: If you wish to change the commissioned state of the line interface, select the checkbox in the Commissioned column of the table in the Tributary section, then double-click to display the drop-down list. Select True (enabled) or False (disabled) asrequired.

Step 8: If you wish to change the line build out of the wayside tributary, select the LineBuild Out column of the table in the Wayside Tributary section, then double-click todisplay the drop-down list. Select the new build-out from the drop-down menu. Youcan choose between lengths of 0-133 feet (default), 133-266 feet, 266-399 feet,399-533 feet and 533-655 ft.



Using DXR NET NMT



) �� )��54��

You can change the terminal line interface parameters for a STM-0 type interface using thefollowing procedure.



tributary wayside connector on the DXR 700 PMA front panel.

Procedure




Step 4: If you wish to change the interface receiver sensitivity, select the Rx Sensitivitycolumn of the top table in the Tributary section, then double-click to display thedrop-down list. Select the new sensitivity from the list. You can choose from Low,Medium (default), or High.


Step 6: If you wish to enable or disable the equalizer bypass function in the line interface,select the check box in the Equalizer Bypass column of the table in the Tributarysection, then double-click to display the drop-down list. Select True (enabled) orFalse (disabled) as required.

Step 7: If you wish to change the commissioned state of the line interface, select the checkbox in the Commissioned column of the table in the Tributary section, then double-click to display the drop-down list. Select True (enabled) or False (disabled) asrequired.

Step 8: If you wish to change the line impedance of the wayside tributary, select theImpedance column of the table in the Wayside Tributary section, then double-clickto display the drop-down list. Select the new impedance from the list. You canchoose between impedances of 120 ohm (default) and 75 ohm.



Using DXR NET NMT



) ��,�!��$% 44� ��You can set up an alarm input to the DXR 100 using the following procedure:

Procedure



Step 3: Select the Alarm I/O page.

Step 4: If you wish to assign a name to the alarm input, then select the relevant inputidentifier field and type in the name.

Step 5: If you wish to set the normal condition of the input, i.e. the input state that indicatesno alarm is present, click on the Normal State field, and select the appropriate statefrom the displayed scroll-down menu. You can choose between “Current” and “NoCurrent”.



) ��,�!��$% 44� ��You can set up an alarm output from the DXR 100 using the following procedure:

Procedure



Step 3: Select the Alarm IO page.

Step 4: If you wish to assign a name to the alarm output, then select the relevant outputidentifier field, and type in the name.

Step 5: If you wish to set the normal condition of the output, i.e. the output state thatindicates no alarm is present, click on the Normal State field, and select theappropriate state from the drop-down list. You can choose between “Open” and“Closed”.

Step 6: Select the maximum number of changes the alarm signal can make per second byclicking on the Rate field, and either using the up/down arrows, or typing in thevalue.


Using DXR NET NMT




�� -��!��You can check to see if there are any alarms present on a network element by viewing theAlarms page.

Procedure 1

Step 1: Select the Commissioning Workspace.


Step 3: Select the Commissioning page.

Step 4: If the LED icon in the Alarm Status section is red, click on the View Alarms buttonto display the Alarms page.

Step 5: If the icon in the Alarm Status and Related Information pane is red, click on the iconto move down the hierarchical alarm levels until the alarm is reached. The alarmname and a description of the most likely causes will be displayed in the right hand-panes.

Step 6: When you have identified an active alarm, take the required action to correct it, i.e.clear the alarm condition yourself, or if this is not possible, alert the appropriatenetwork personnel.

Procedure 2

Step 1: Select the Maintenance Workspace.


Step 3: Select the Alarms page.

Step 4: If the icon in the Alarm Status and Related Information pane is red, click on the iconto move down the hierarchical alarm levels until the alarm is reached. The alarmname and a description of the most likely causes will be displayed in the right hand-panes.

Step 5: When you have identified an active alarm, take the required action to correct it, i.e.clear the alarm condition yourself, or if this is not possible, alert the appropriatenetwork personnel.

Using DXR NET NMT



,��-�� -��-You would use the loopback functions after commissioning the link, to check the link hasbeen set up properly, or during maintenance, when you are investigating problems with thelink.

You will require test equipment capable of generating and monitoring a Pseudo Random BitStream (PRBS), eg BERL tester or similar. You should also be familiar with the remedialactions to be carried out when you have traced a fault to a particular piece of equipment.These will be laid down in your servicing policy.



RF/MODEM FUNCTIONS. You should select the functions in the RF/Modem section forthe local terminal (the terminal selected in the Explorer Tree) only, as selecting them in aremote terminal could cause you to lose communication with the terminal.

Loopbacks are used to:

• Check that a link is functioning within the desired parameters.

• Locate where any problems are occurring.

You can use DXR NET to apply loopback functions to a selected terminal. When you select aloopback function, the terminal will feed back any received input signal to the signal source.Normally, you would enable a loopback function, input a known bit-stream, and check the bit-stream output from the terminal for errors.

Loopback functions are available from the Controls page, which can be selected from eitherthe Commissioning or Maintenance Workspace. The functions are selected from the TributaryLoopbacks and the RF/Modem sections in the page.

Tributary LoopbacksThe Tributary Loopbacks section allows you to select the following:

Note: You can select the functions in the Tributary Loopbacks section for both the localterminal (the terminal selected in the Explorer Tree), and its remote terminal (theterminal at the other end of the link).

• No Tributary Loopback (default).

• Line Facing

• Radio Facing

You select a function by clicking its radio button.


Using DXR NET NMT




When you select No Tributary Loopback, there are no loopbacks enabled, and the lineinterface operates as normal.

When you select the Line Facing loopback function, the line interface will connect theterminal line inputs and outputs. Any inputs to the local line interface are therefore fedstraight back out again without going through the rest of the terminal circuitry. You wouldnormally enable this on the local terminal to check the operation of your test equipmentbefore using it to test the actual link.

Figure 45: Line Facing Loopback

When you select the Radio Facing loopback function, the line interface will connect the inputand output streams to the terminal radio circuitry. Any signals received from the remoteterminal are therefore re-transmitted back to the remote terminal over the radio link, afterpassing through all the local terminal circuitry. You would normally enable this on the remoteterminal to see if there are any problems with the link.

Figure 46: Radio Facing Loopback

RF/ModemThe RF/Modem section allows you to select the following:


RF/MODEM FUNCTIONS. You should select the functions in the RF/Modem section forthe local terminal (the terminal selected in the Explorer Tree) only, as selecting them in aremote terminal could cause you to lose communication with the terminal.

• Digital Loopback

• IF Loopback

• FEC Disable (DXR 100 only)

You select an option by clicking on the appropriate check box with the mouse.

When you select the Digital Loopback option, the loopback is made between the compositedigital transmit and receive streams inside the radio modem, before the streams are passed todigital-to-analog conversion.

Using DXR NET NMT



Figure 47: Digital Loopback

When you select the IF Loopbacks option, the loopback is made between the transmit andreceive IF signals, just before they are output from the terminal.

Figure 48: IF Loopback

You can carry out a RF loopback by changing the receive and transmit frequencies to thesame frequency.

When you select the FEC Disable option (DXR 100 only), you can obtain a true reading of theactual errors received over the link. You need to disable FEC for this, as FEC automaticallycorrects any errored bytes in the received data, i.e. errors are corrected before you can detectthem.

) 8� ��

Normally, you would use loopback functions on two occasions:

• During commissioning, to check the link has been set-up properly.

• When problems have occurred on the link.

In either case, the sequence of operations is as follows:

• Connect your test equipment to one of the terminals of the link.

• Check the test equipment and the connection to the local terminal by carrying out a line-facing loopback on the local terminal.

• Check the link by carrying out a radio-facing loopback in the remote terminal.

If the results of the radio-facing loopback are satisfactory, the link is operational, and youneed take no further action. If the results are not satisfactory, there is a fault somewhere onthe link, and you should proceed as follows:

• If the radio-facing loopback results are unsatisfactory, try to localise the fault by carryingout Digital, IF and RF loopbacks on the local terminal.

• If the fault cannot be found on the local terminal, carry out Digital, IF and RF loopbackson the remote terminal

Using DXR NET NMT



,��-�� -�� '8��

��

Before you can use your test equipment to monitor the performance of a link, it is a good ideato check both the test equipment, and the connection between it and the terminal. Proceed asfollows:

Procedure

Step 1: Attach your test equipment to the line interface of the local terminal.

Step 2: Select the local terminal in the DXR NET Explorer Pane.

Step 3: Select the Commissioning or the Maintenance Workspace (as appropriate).

Step 4: Select the Controls page.

Step 5: Select the Line Facing loopback function from the Tributary Loopback section, clickthe Apply button, then the OK button in the displayed Warning box.

Step 6: Compare the bit-stream output from the terminal against the input stream from yourtest equipment.

Step 7: After you are finished comparing the bit-streams, select the No Tributary Loopbackradio button, then click the Apply button.

If any differences between the bit-streams are within the desired limits, go to “UsingLoopbacks to Check the Link”. If the differences are outside the limits, check:

• The connection between the test equipment and the terminal.

• The test equipment.

When you have rectified the problem, return to Step 1 and repeat the procedure.

,��-�� -�� -

After you have carried out the procedure in “Using Loopbacks to Check the Test Equipmentand the Terminal Connection”, you can then use a radio-facing loopback to monitor theperformance of a link. Proceed as follows:

Step 1: Select the remote terminal in the DXR NET Explorer Pane.

Step 2: Select the Radio Facing loopback function from the Tributary Loopback section,click the Apply button, then the OK button in the displayed Warning box.

Step 3: Check the bit-stream output from the local terminal against the input stream fromyour test equipment.

Step 4: When you have finished comparing the bit-streams, select the No TributaryLoopback radio button, then click the Apply button.

If the errors are within the desired range, the link is functioning properly, and you need takeno further action. If the errors are outside the set range, there is a problem with the link, andyou should use loopbacks to check the terminals at either end of the link.

Using DXR NET NMT



,��-�� -�� -� ��

If you have identified a problem with a link, you should try and localise the problem bycarrying out Digital, IF and RF loopbacks on first the local, then the remote terminal. Connectyour test equipment to the terminal, then proceed as follows:

Note 1: When you have located a fault using a loopback, you should disable any loopbackspresent, then quit the procedure. You should not proceed with any following steps.

Note 2: If you are checking a DXR 100 terminal, you should select the FEC Disablefunction after Step 1 of the procedure. Remember to deselect the function beforequitting the procedure. Refer to “Using FEC Disable While Checking DXR 100Terminals” for details.

Step 1: Select the terminal in the DXR NET Explorer Pane.

Step 2: Select the Digital loopback function from the RF/Modem section, than click theApply button, then the OK button in the displayed Warning box.


Step 4: When you are finished comparing the bit-streams, deselect the Digital loopbackfunction by clicking again on the selected check box.

Step 5: If the errors are outside the desired range, the problem is in the circuitry between theG.703 interface and the Modulation and Demodulation circuitry. Quit thisprocedure, and carry out any remedial action set out for this type of fault in yourservicing policy. If the errors are within the desired range, the problem is not in thiscircuitry, and you should proceed to Step 6.

Step 6: Select the IF loopback function from the RF/Modem section, than click the Applybutton, then the OK button in the displayed Warning box.


Step 8: When you are finished comparing the bit-streams, deselect the IF loopback functionby clicking again on the selected check box.

Step 9: If the errors are outside the set range, there is a problem in the circuitry between theModulation and Demodulation circuitry and the Splitter/Combiner. Quit thisprocedure, and carry out any remedial action set out for this type of fault in yourservicing policy. If the errors are within the desired range, the problem is not in thiscircuitry, and you should proceed to Step 10.

Step 10: Set up a RF loopback by going to the Modem/RF Link Setup page in theConfiguration Workspace, and setting the transmit and receive frequencies to thesame frequency.


Step 12: When you have finished comparing the bit-streams, deselect the RF loopbackfunction by restoring the transmit and receive frequencies to their original settings.

Using DXR NET NMT



Step 13: If the errors are outside the set range, there is a problem in the ODU. Quit thisprocedure, and carry out any remedial action set out for this type of fault in yourservicing policy. If the errors are within the desired range, there are no faults in thisterminal.

Step 14: If you have not already investigated the terminal at the other end of the link,disconnect the test equipment from the local terminal, go to the remote site, connectthe test equipment to the terminal at that site, then go through Steps 1 to 13 for thisterminal.

If you have gone through all the above steps at both terminals without being able to localisethe problem, this indicates one of the following:

• There is an antenna problem (eg, misalignment, matching).

• There is a radio path problem (eg, obstacles, multi-path).

You should investigate and identify what the problem is, then take suitable remedial action.

,��'�� *�� -��$% 44� ��

The DXR 100 uses Forward Error Correction (FEC) to correct any errored bytes receivedover the radio link. Although this adds to the performance of the link during normal operation,it can cause a problem when you are trying to identify faults using loopbacks. Since errors canbe corrected before reaching the output, you may therefore not obtain a true picture of theterminal error-rate when comparing the input and output streams. This will make it moredifficult to track errors to a particular piece of circuitry in the terminal.

To combat this, DXR NET has a FEC Disable function for DXR 100 terminals. You can selectthis from RF/Modem section in the Controls page. You click on the FEC Disable check box toselect the function, then click the box again when you wish to deselect it.

� �� )*�� Note: You can only enable protection switching in a protected terminal.

You can test protection switching using the following procedure.

Switching the transmitter will cause an interruption of up to 50 ms in the network traffic.

Procedure

Step 1: Select the Commissioning or Maintenance Workspace.


Step 3: Select the Controls page.

Step 4: Select the Manual switching option you require from the Protection Switchingsection by clicking on the associated radio button.

Step 5: Select the transmitter or receiver you wish DXR 700 to switch to.

Step 6: Click the Apply button in the displayed dialog box, then the OK button in theWarning box.

Using DXR NET NMT



Step 7: When you have completed your tests, reselect the Automatic switching option byclicking again on the associated radio button.

B� *�� You can view the Constellation Diagram for a terminal using the following procedure.

Except for the RSSI Graph (DXR 700) or AGC Graph (DXR 100) page operations, youcannot select other operations while Constellation Diagram monitoring is in progress.


Note: For a DXR 700, if the Single Carrier option is selected in the Advanced option inthe Tools menu, DXR NET monitors the baseband signal from each availableDXR 700 terminal to produce the diagrams. If the Multi-Carrier option is selected,DXR NET monitors the individual carriers of the local DXR 700 terminal to producethe diagrams.

Procedure



Step 3: Select the Constellation Diagram page.

Step 4: Select the terminals or carriers you wish to monitor by clicking the relevant buttonin the Select Terminal section.

Step 5: You can start monitoring for all terminals or carriers by clicking the Monitor Allbutton in the Select Terminal section, or you can start monitoring for an individualterminal or carrier by clicking the Monitor button in the particular ConstellationDiagram for the terminal or carrier.

Step 6: If you wish to clear all the diagrams, click on the Reset All button in the SelectTerminal section. If you wish to clear a particular diagram, click on the Reset buttonin the diagram.

Step 7: After you have finished monitoring the constellation diagrams, stop monitoring byclicking on any indented monitoring buttons. Ensure that all the monitoring buttonsare raised before leaving the page.

B� *�� %))�+��$%744� ��You can view the RSSI graph using the following procedure.

Except for the Constellation page operations, you cannot select other operations while RSSImonitoring is in progress.

Using DXR NET NMT




Note: If the Single Carrier option is selected in the Advanced option in the Tools menu,

DXR NET monitors the baseband signal from each available terminal to produce thegraphs. If the Multi-Carrier option is selected in the Advanced option in the Toolsmenu, DXR NET monitors the individual carriers of the local terminal to produce thegraphs.

Procedure


Step 2: Select the local terminal in the Explorer Tree.

Step 3: Select the RSSI Graph page.

Step 4: Select the terminals or carriers you wish to monitor by clicking on the relevantbutton.

Step 5: You can start monitoring for all terminals or carriers by clicking the Monitor Allbutton in the Select Terminal section, or you can start monitoring for an individualterminal or carrier by clicking the Monitor button in the particular RSSI Graph forthe terminal or carrier.

Step 6: If you wish to clear all the graphs, click on the Reset All button in the SelectTerminal section. If you wish to clear a particular graph, click on the Reset button inthe graph.

Step 7: If you wish to reset the Max and Min bars for a particular graph, click on the Resetbutton in the graph. This will reset the bars to the maximum and minimum RSSIvalues (0 dBm and –100 dBm respectively).

Step 8: After you have finished monitoring the RSSI graphs, stop monitoring by clicking onany indented monitoring buttons. Ensure that all the monitoring buttons are raisedbefore leaving the page.

Using DXR NET NMT



B� *��!+�+��$% 44� ��You can view the AGC graph for a DXR 100 terminal using the following procedure.

Except for the Constellation page operations, you cannot select other operations while AGCmonitoring is in progress.

STOPPING MONITORING. You must remember that just because an AGC graph is notshown for a terminal does NOT mean the terminal is not being monitored.

Procedure



Step 3: Select the AGC Graph page.

Step 4: Select the terminals you wish to monitor by clicking on the relevant button.

Step 5: You can start monitoring for all terminals by clicking the Monitor All button in theSelect Terminal section, or you can start monitoring for an individual terminal byclicking the Monitor button in the particular AGC Graph for the terminal.

Step 6: If you wish to clear all the graphs, click on the Reset All button in the SelectTerminal section.

Step 7: If you wish to reset the Max and Min bars for a particular graph, click on the Resetbutton in the graph. This will reset the bars to the maximum and minimum AGCvalues (+5V and 0V), and clear all the data.

Step 8: After you have finished monitoring the AGC graphs, stop monitoring by clicking onany indented monitoring buttons. Ensure that all the monitoring buttons are raisedbefore leaving the page.

B� *��'8��9 �+��$% 44� ��You can view the Equalizer graph for a DXR 100 terminal using the following procedure.

STOPPING MONITORING. You must remember that just because an equalizer graph isnot shown for a terminal does NOT mean the terminal is not being monitored.

Procedure



Step 3: Select the Equalizer Graph page.

Step 4: Select the terminals you wish to monitor by clicking on the relevant button.

Using DXR NET NMT



Step 5: You can start monitoring for all terminals by clicking the Monitor All button in theSelect Terminal section, or you can start monitoring for an individual terminal byclicking the Monitor button in the particular Equalizer Graph for the terminal.

Step 6: If you wish to clear all the graphs click on the Reset All button in the SelectTerminal section.

Step 7: After you have finished monitoring the Equalizer graphs, stop monitoring byclicking on any indented monitoring buttons. Ensure that all the monitoring buttonsare raised before leaving the page.

��)��*�� & �*��-'� � ��

LOADING SOFTWARE. Software can only be loaded to terminals via a NMS element(NMS board or SMA). If you do not have an NMS element, you will require DXRloader.Please contact DMC for information on using DXRloader.

You can use DXR NET to load both terminals and NMS elements with updated software. Theprocedure has the following three steps:

• Installing the system software (ie, the available versions of terminal and NMS unitsoftware) on your PC.

• Removing any old software files from the NMS element you are using to load thesoftware.

• Loading the software to the network elements.

You can abort a software load at any time during the loading process. If DXR NET is unable tocommunicate with certain element components, it will display a dialog box so that you canselect the available components for software loading. However, DXR NET detects that theelement is not compatible with the software you are trying to load, it will abort the loadingprocess.

��)"�� )��*�� 0��

Before you can load software to a network element, you must have first install the SystemSoftware containing the network element software into the DXR NET folder on your PC.

Step 1: Insert the System Software disk (CD or floppy) into your PC.

Step 2: Use Windows Explorer to find SETUP.EXE on the disk.

Step 3: Click "Next" in the Welcome screen.

Step 4: If required, change the desired location specified for the System Software files.

Step 5: Click Next.

Step 6: When the Setup Completed message appears, click Finish.

Using DXR NET NMT



� � ��)��*�� &�),��

After you have loaded new software to any network elements, the BIN files remain stored inthe NMS element. Before you load any new software, you should delete these files. You maydelete all files that are marked as read/write. DXR NET will not allow you to delete filesrequired by the NMS element.

The procedure is as follows:

Note: You must be connected to the network via a NMS unit (a SMA or a NMS board).

Step 1: Run DXR NET from the PC desktop.

Step 2: Select Maintenance from the Workspace Selection window.

Step 3: Either click on the Connect button on the toolbar to autodiscover the attachednetwork, or load the network blueprint and then click on the Connect button.


Step 5: Select the File System page in the Maintenance workspace.

Step 6: Select and delete the BIN files in the File System window.

You can now proceed with loading the new software.

��)��*�� & �*��-'� � ��

Note 1: You must be connected to the network via a NMS unit (a SMA or a NMS board). Ifyou do not have an NMS unit, contact DMC on using other software loading tools.

Note 2: We recommend that software is loaded to remote elements first (see Note 3).

Note 3: Following the SW load into the NMS unit, the link will drop while the terminal isloaded. This may happen any time in the 5 mins after the load completed,depending on the terminal type. Do not attempt to perform software loads over thelink during this time.

Note 4: You can abort a software load at any time during the loading process. If DXR NET isunable to communicate with certain element components, it will display a dialogbox so that you can select the available components for software loading. However,if DXR NET detects that the element is not compatible with the software you aretrying to load, it will abort the loading process.

To load software to a network element, proceed as follows:


Step 2: Select Configuration from the Workspace Selection window.

Step 3: Either click on the Connect button on the toolbar to autodiscover the attachednetwork, or load the network blueprint and then click on the Connect button.


Step 5: Read the configuration from the element.

Using DXR NET NMT



Step 6: Select Software Table from the drop-down Configuration menu.

Step 7: Click the ellipsis (“…”) button in Software Version Table window to get the foldercontaining the System Software.

Step 8: Double click on the Version field in Software Version Table window, select theversion of the element software you wish to load, then click OK.

Step 9: Select Load Software from the drop-down Configuration menu, then Start.

Step 10: When the Complete message appears, click the OK button.

Step 11: Write the configuration into the element.

Note: If you have any problems with this basic procedure contact customer support asshown in the dialog box below. You can open this dialog box by choosing theCustomer Support option in the Help menu of DXR NET NMT.

)��*�� "��

When you connect to a NMS unit with a network blueprint loaded, DXR NET checks that theversion of software it detects in the unit matches the version set in the blueprint. This isknown as SSC compatibility checking. If the versions do not match, a warning message willappear in the Status Bar of the DXR NET GUI, and you will not be able to read or write to theunit.

To overcome this, amend the blueprint to reflect the version of software in the NMS unit.

To amend the blueprint, proceed as follows:

Step 1: Connect to the NMS unit without having the blueprint loaded. This willautodiscover the link.

Step 1: Read the configuration from the unit.


Step 3: Note the version of software listed for the NMS unit in the Version field of theSoftware Table.

Using DXR NET NMT



Step 4: Disconnect from the NMS unit, and load the blueprint.



Step 7: For the NMS unit you are interested in, double click on the Version field inSoftware Version Table window, select the version of software actually present inthe unit, then click OK.

The blueprint should now reflect the software version in the actual unit. To confirm this, tryto connect to the unit again with the blueprint loaded.

!��.��.��"��

When you connect to an SMA, DXR NET checks that the version of alarm board and optionboards it detects in the unit matches the version set in the blueprint. If the versions do notmatch, a warning message will appear in the Status Bar of the DXR NET GUI, and you willnot be able to read or write to the unit.

To overcome this, amend the blueprint to reflect the version of board in the unit.

To amend the blueprint, proceed as follows:

Step 1: Connect to the NMS unit without having the blueprint loaded.


Step 3: Select "Configuration" menu.

Step 4: Note the version of option board listed.

Step 5: Disconnect from the NMS unit, and load the blueprint.


Step 7: Select Configuration menu.

Step 8: For the NMS unit you are interested in, change the alarm board type, or the optionboard type to that which is actually present in the unit, then click OK.

The blueprint should now reflect the option board type in the actual unit. To confirm this, tryto connect to the unit again with the blueprint loaded.

%��)�� DXR NET allows you to load and run script files to carry out test procedures.

SCRIPT FILES. Script files should only be used under the direction of DMC.

The procedure for running a script file is as follows:

Note: Make sure that the network element you want to run the script file on is selected inthe Explorer Tree, as this sets up the target for SNMP messages.


Using DXR NET NMT



Step 2: Select Maintenance from the Workspace Selection window.


Step 4: Select Load Script File from the drop-down Maintenance menu.

Step 5: Select the script you want to run in the Execute Script File box, then Start.

��% ��You can use DXR NET Report facility to produce reports for network elements. The reportsare of two main kinds:

• Commissioning Reports – these contain details of network element status after theelement has been brought into service.

• Inventory Reports – these contain details of network element status during normaloperation.

The reports can be viewed on your PC, saved for later reference, or printed out to providehard copy. They are produced from stored templates, which can themselves be customized tosuit your requirements. The templates are stored in the Templates folder, and any reportsproduced can be stored, for later reference and printing, in the Reports folder.

Note: The default location for these folders is off the DMC folder, but you can select otherlocations for them. You would normally do this when you install DXR NET on yourPC.

��% ��

You can produce Commissioning reports for the following network elements:

• DXR 100 terminals (protected and unprotected).

• DXR 700 terminals (protected and unprotected).

The reports are produced by clicking the Report button in the Commissioning page of theCommissioning Workspace.

ProcedureTo produce a Commissioning report for a terminal, proceed as follows:

Note: A report can only be successfully produced if there is a valid template available forthe terminal.

Step 1: Select the element in the DXR NET Explorer Tree.

Step 2: If required, select either the Commissioning Workspace, and go to the TerminalDetails page.

Step 3: Click the Commissioning Report button in the Terminal Details page.

Step 4: If you decide not to continue with producing the report, click the Abort button in thedisplayed dialog box.

Using DXR NET NMT



Step 5: If the report has been successfully produced, the Report Dialog window isdisplayed. You can then select the template used by the report from the TemplateSelection combo box. This contains all the available templates for the element.

Step 6: After displaying the report, you can add any required additional information to theComments section. You can then save the report to the Reports folder, for storage orprinting, by clicking the Save button in the window.

Step 7: If the report has not been successfully produced, or you are finished using it, clickthe Close button in the Report Dialog window to return to the main DXR NET

window.

�� "% ��

You can produce Inventory reports for all DXR NETwork elements. The reports are producedby clicking the Report button in the Details page for the element. These pages appear in boththe Commissioning and the Maintenance Workspaces.

ProcedureTo produce an Inventory report for a network element, proceed as follows:

Note: A report can only be successfully produced if there is a valid template available forthe element.

Step 1: Select the element in the DXR NET Explorer Tree.

Step 2: If required, select either the Commissioning or Maintenance Workspace, and go tothe details page for the element.

Step 3: Click the Report button in the element details page.

Step 4: If you decide not to continue with producing the report, click the Abort button in thedisplayed dialog box.

Step 5: If the report has been successfully produced, the Report Dialog window isdisplayed. You can then select the template used by the report from the TemplateSelection combo box. This contains all the available templates for the element.

Step 6: After displaying the report, you can add any required additional information to theComments section. You can then save the report to the Reports folder, for storage orprinting, by clicking the Save button in the window.

Step 7: If the report has not been successfully produced, or you are finished using it, clickthe Close button in the Report Dialog window to return to the main DXR NET

window.

Appendix A: Problems Using DXR NET



!�� /!�� ,��$%&'�

+ � ��Problems encountered using DXR NET might include:

• The network cannot be accessed.

• Changes to the configuration are not accepted.

�� !�� & �*��-

Check you have the right type of interface for your connection by selecting theCommunication Setup option from the Tool menu in the menu bar. If you have selected thewrong interface, change it to the correct one (see Selecting DXR NET interface on your PC inthe Installing DXR NET section).

Check that the cable is connected to the correct COM port of your PC by selectingCommunication Setup option from the Tools menu. If it has been inserted into the wrong port,either connect it to the correct port, or change the selected COM port (see Selecting DXR NET

interface on your PC in the Installing DXR NET section).

Check that the cable connections are secure.

Check that the cable pins and wiring are undamaged.

�� & �*��-'� � ��

Check the original setup details to ensure that you are not trying to load changes that cannotbe supported by your variant of the element.

�$%&'�#��

The most common warning messages you will encounter using DXR NET, and their likeliestcauses, are listed below.

Note: The warnings are not listed in full for reasons of space.

Unable to launch dial-up adaptor …This usually indicates problems trying to connect to a DXR NETwork. Most common causesare:

• There is something wrong with the connection between your PC and the network.

• You are trying to connect to an NMS element before it has completed an action that hascaused it to drop its NMS connection (eg. resetting the element IP address).

• You are trying to connect using the wrong dial-up adaptor.

Appendix A: Problems Using DXR NET



• You have not properly enabled your dial-up adaptor for NMS connections.

No valid network elements…This usually indicates problems trying to connect to a DXR NETwork. Most common causesare:

• There is something wrong with the connection between your PC and the network.

• You are using the wrong type of connection for the element to which you are connected.

An IP compliant device could not be found…This usually indicates problems trying to connect to a DXR NMS network with the blueprintloaded in DXR NET. Most common causes are:

• You are trying to connect to a terminal instead of a NMS element.

• The IP address of the NMS element you are trying to connect to does not match theaddress given in the blueprint.

Loss of linkThis usually indicates problems with frequency settings or cable connections. Most commoncauses are:

The transmitter (TX) and receiver (RX) frequencies are different at each end of the link.

The transmitter (TX) and receiver (RX) frequencies do not match the ODU duplexer settingsmade at the factory. Check the correct factory settings by viewing the ODU details asdescribed on page 60 in this manual.

There is a faulty cable connection or you have loaded invalid software. Check for any alarmsin the radio. If none are present you may have lost contact with the ODU due to a cableproblem.

��)�� /& �*��-�

Selecting Help and then Customer Support will display the methods you can use to contact theproduct support staff at DMC Stratex Networks.

Appendix B: Alarms



!�� /.�!��

+ � ��This appendix contains descriptions of the alarms that can be generated in DXR NET by thefollowing network elements:

• DXR 100

• DXR 200

• NMS board

• DXR 700

• SMA

B� *��!��

+ � ��

DXR NET alarms are viewed in the Alarms page, which is divided into two panes. The left-hand pane, Alarm Status and Related Information, lists all possible alarms in the WindowsExplorer tree format. This has the alarms grouped in hierarchical levels under the unitscurrently present in the link or terminal.

You can move through the levels by double clicking on a unit listing to display the sub-unitand alarm listing under it. Each unit or alarm listing has an LED icon next to it. For a unitlisting, the icon indicates whether there are any alarms present in the unit or any sub-unitsunder it. For an alarm listing, the icon indicates the alarm status, as described in the previoustable. Units “inherit” alarms from levels under them in the hierarchy. You can therefore usethe Alarm Status and Related Information pane to detect when an alarm is present on a unit,and then to track the alarm to a particular component.

The alarm status indicated by the icons is given in the following table.

��

$TKIJV )TGGP Indicates that no alarm is present. &WNN 4GF Indicates that the alarm status is not known. 4GF Indicates that an alarm has been triggered.

Note: A “dull red” icon is usually due to DXR NET being unable to communicate with the

terminal.

Appendix B: Alarms




• Alarm Name


• Alarm Type

• Alarm Severity


The Alarm Type field entries are described in the following table.

�� 'SWKROGPV Indicates an alarm associated with an equipment fault or an

external alarm input. 'PXKTQPOGPVCN Indicates an alarm associated with the enclosure that contains

the equipment. 2TQEGUUKPI GTTQT Indicates an alarm associated with a software or processing

fault. %QOOWPKECVKQPU Indicates an alarm associated with the procedures and/or

processes required to carry information. 3WCNKV[ QH UGTXKEG Indicates an alarm associated with the degradation of quality

of service.

The Alarm Severity field entries are described in the following table.

Note: The entries are listed in order of increasing severity.

�� %NGCTGF Indicates that no alarm is present. +PFGVGTOKPCVG Indicates that the alarm status is not known. 9CTPKPI Indicates a condition with the potential to cause a fault that

affects service has occurred. /KPQT Indicates a condition that does not affect user traffic, but

which requires corrective action before a more serious faultoccurs.

/CLQT Indicates a condition affecting user traffic that requirescorrective action.

%TKVKECN Indicates a condition affecting user traffic that requiresimmediate corrective action.

Appendix B: Alarms



�$% 44!��

&�%,��!��

When the NPR Unit Alarm is active, it indicates an alarm is present on an unprotectedDXR 100. The alarms that can trigger the NPR Unit Alarm can be grouped into the followingtypes:

• Hardware

• Software

• Maintenance

• Traffic

• Modem

• Radio link

2��*��

This indicates that a hardware alarm is present on the DXR 100. The alarms that can triggerthe hardware alarm can be grouped into the following types:

• Component failure

• Power supply

• Internal temperature

• Alarm inputs

Component FailureThis indicates a component failure has occurred in the DXR 100. It is classed as a minoralarm, of the equipment type.

Power SupplyThis indicates one or more of the three power supplies used in the DXR 100 is operatingoutside of the normal threshold limits. The three possible power supply alarms are shown inthe following table.

��

��

��

��

��

+5V digitalsupply

Warning Equipment The +5V digital supply is outside ofthe normal operating upper and lowerthresholds.

+5V analogsupply

Warning Equipment The +5V analog supply is outside ofthe normal operating upper and lowerthresholds.

10V supply Warning Equipment The 10V supply is outside of thenormal operating upper and lowerthresholds.

Internal TemperatureThis indicates the temperature inside the DXR 100 chassis is outside the normal operatingupper and lower thresholds. It is classed as a warning alarm, of the environmental type.

Appendix B: Alarms



Alarm InputsThis indicates one or both of the two external alarm inputs to the DXR 100 is active. The twopossible alarms are shown in the following table.

Note: The perceived severity of alarm board input alarms will be user-configurable in thefuture.

��

��

��

��

��

Alarm Inputs 1 Warning Equipment External alarm input 1 is present.


)��*��

This indicates that one or more software alarms are present on the DXR 100. The possiblealarms are shown in the following table.

��

��

��

��

��

Configurationcorrupt

Major Processingerror

Corruption of the configuration datahas been detected.

Settings not valid Major Processingerror

The configuration does not match thehardware capability.

Software/hardwareincompatible


The software is not fully compatiblewith the hardware.

Software resourceslow

Minor Processingerror

Insufficient memory for the softwareto operate correctly.

��

This indicates that one or more maintenance alarms are present on the DXR 100. Theycomprise:

• Traffic

• Modulation

• RF

Appendix B: Alarms



TrafficThis indicates that one or more traffic related alarms are present on the DXR 100. Thepossible alarms are shown in the following table.

��

��

��

AIS outputenabled

Warning Communications AIS is enabled on all outgoingtributaries.

Trib radiofacing loopbackactive

Warning Communications The radio facing loopback isenabled for one or more tributaries.

Trib line facingloopback active

Warning Communications The line facing loopback is enabledfor one or more tributaries.

ModulationThis indicates that one or more modulation alarms are present on the DXR 100. The possiblealarms are shown in the following table.

��

��

��

IF loopbackactive

Warning Communications The IF loopback is enabled.

Digital loopbackactive

Warning Communications The digital loopback is enabled.

FEC disabled Warning Communications Forward Error Correction isdisabled

RFThis indicates that one or both RF related alarms are present on the DXR 100. The possiblealarms are shown in the following table.

��

��

��

RF loopbackactive

Warning Communications The RF loopback is enabled.

TX PA muted Warning Communications The TX PA is muted.

��

This indicates that one or more traffic related alarm conditions are present on the DXR 100.They comprise:

• Trib port

• Trib n

Trib PortThis indicates that a traffic-related alarm is present on one of the DXR 100 Tributary ports.

Appendix B: Alarms



Trib nThis indicates one of the three possible alarms is present on the Tributary port n of theDXR 100. The three possible alarms are shown in the following table.

��

��

��

LOS Critical Communications Loss of signal has occurred. Theprobable cause is a disconnectedTributary cable.

AIS Warning Communications AIS is being detected. Uncommissionedtraffic

Warning Communications Traffic is being received on thisuncommissioned Tributary port.

��

This indicates that one or more modem related alarm conditions are present on the DXR 100.They comprise:

• RX path failure

• RX path warning

RX Path FailureThis indicates that a modem related alarm is present, due to the loss of the DXR 100 RX path.It has a single alarm under it, De-modulator not locked, which is present when the modem de-modulator is out of lock. This is classed as a critical alarm, of the communications type.

RX Path WarningThis indicates one of two possible modem-related alarms, due to the detection of errors in thereceived data, is present on the DXR 100. The two possible alarms are shown in the followingtable.

��

��

��

��

� � � ��

Correctableerror limit

Warning Quality ofservice

The number of correctable bytes detected in thelast second exceeds the user configured upperthreshold.

Uncorrectableerrors


Uncorrectable blocks are being detected.

%��-

This indicates that a radio link related alarm is present on the DXR 100.

Link failureThis indicates one or more of the radio link failure alarms is present on the DXR 100. Thesecomprise:

• TX Path Failure

• RX Path Failure

Appendix B: Alarms



The TX Path Failure alarm indicates that a TX path failure alarm is present on the DXR 100.It has a single alarm under it, TX Synthesizer not locked. This is classed as a critical alarm, ofthe equipment type. The two most probable causes of this alarm are:

• An invalid TX frequency has been configured.

• The upconverter module in the DXR 100 is faulty.

The RX Path Failure alarm indicates that a RX path failure alarm is present on the DXR 100.It has a single alarm under it, RX Synthesizer not locked. This is classed as a critical alarm, ofthe equipment type. The two most probable causes of this alarm are:

• An invalid RX frequency has been configured.

• The upconverter module in the DXR 100 is faulty.

Link WarningThis indicates one or more of the radio link warning alarms is present on the DXR 100. Thesecomprise:

• TX Path Warning

• RX Path Warning

The TX Path Warning alarm indicates that one or both of the following alarms are present onthe DXR 100.

��

��

��

Forwardpower

Warning Equipment The TX forward power is outside the userconfigured upper and lower thresholds.

Reflectedpower

Warning Equipment The TX reflected power is above the userconfigured upper threshold. The probablecause is a faulty antenna.

The RX Path Warning alarm indicates that the AGC alarm is present on the DXR 100. Thisindicates that the AGC is outside the user configured upper and lower thresholds. It is classedas a Warning, of the Communications type.

�)#!��

When the PSW Unit Alarm is active, it indicates an alarm is present on the Protection Switchunit of a protected DXR 100. The alarms that can trigger the PSW Unit Alarm can be groupedinto the following types:

• Hardware

• Software

• Maintenance

• Traffic

• Tx Switch

Appendix B: Alarms



2��*��

This indicates that a hardware alarm is present on the PSW. The alarms that can trigger thehardware alarm can be grouped into the following types:


• Power supply


• Alarm inputs

Component FailureThis indicates a component failure has occurred in the PSW. It is classed as a minor alarm, ofthe equipment type.

Power SupplyThis indicates one or more of the three power supplies used in the PSW are operating outsideof the normal threshold limits. The three possible power supply alarms are shown in thefollowing table.

��

��

��

��

��

+5V digitalsupply


+5V analogsupply



Internal TemperatureThis indicates the temperature inside the PSW chassis is outside the normal operating upperand lower thresholds. It is classed as a warning alarm, of the environmental type.

Alarm InputsThis indicates one or both of the two external alarm inputs to the PSW is active. The twopossible alarms are shown in the following table.

Note: The perceived severity of alarm board input alarms will be user-configurable in thefuture.

��

��

��

��

��



Appendix B: Alarms



)��*��

This indicates that one or more software alarms are present on the PSW. The possible alarmsare shown in the following table.

��

��

��

��

��












��

This indicates that one or more maintenance alarms are present on the PSW. They comprise:

• AIS output enabled

• Trib radio facing loopback active

• Trib line facing loopback active

AIS output enabledThis indicates that AIS is enabled on all outgoing tributaries on the PSW. It is classed as aWarning alarm, of the Communications type.

Trib radio facing loopback activeThis indicates that radio facing loopback is enabled for one or more tributaries on the PSW. Itis classed as a Warning alarm, of the Communications type.

Trib line facing loopback activeThis indicates that line facing loopback is enabled for one or more tributaries on the PSW. It isclassed as a Warning alarm, of the Communications type.

Manual TX path enabledThis indicates that TX protection switching is locked on manual on the PSW. It is classed as aWarning alarm, of the Communications type.

Manual RX path enabledThis indicates that RX protection switching is locked on manual on the PSW. It is classed as aWarning alarm, of the Communications type.

Appendix B: Alarms



��

This indicates that one or more traffic related alarm conditions are present on the PSW. Theycomprise:

• Trib port

• Radio Link

Trib PortThis indicates that a traffic-related alarm is present on one of the PSW Tributary ports (Tribn). Each tributary port listing can have one or all of the three possible alarms in the followingtable.

��

��

��


AIS Warning Communications AIS is being detected. Uncommissionedtraffic


%��-

This indicates that a radio link related alarm is present on the PSW.

Link failureThis indicates one or more of the radio link failure alarms is present on the PSW. Thesecomprise:

• TX Path Failure

• RX Path Failure

The RX Path Failure alarm indicates that the RX path has failed, i.e. the radio link is down.. Itis classed as a critical alarm, of the communications type.

Received Bitstream ErrorsThis indicates that data from the remote DXR 100 contains errors that cannot be corrected.This is classed as a warning alarm, of the quality of service type.

�$)*��

This indicates that one or more TX path protection switching alarms are present on the PSW.These comprise:

• Switch oscillation limit

• Cannot switch

Switch Oscillation LimitThe Switch Oscillation Limit alarm indicates that the maximum number of protectionswitches within a given time period has occurred. This is classed as a minor alarm, of theequipment type.

Appendix B: Alarms



Cannot SwitchThe Cannot Switch alarm indicates that the TX path cannot switch to the standby PSW. Thisis classed as a minor alarm, of the equipment type. The most probable cause is that an alarmcondition is active on the standby PSW.

�%!!��

When the PRA Alarm is active, it indicates an alarm is present on the Protected RadioAssembly of a protected DXR 100. The alarms that can trigger the PRA Alarm can begrouped into the following types:

• Hardware

• Software

• Maintenance

• Modem

• Radio link

2��*��

This indicates that a hardware alarm is present on the PRA. The alarms that can trigger thehardware alarm can be grouped into the following types:


• Power supply


• Alarm inputs

Component FailureThis indicates a component failure has occurred in the PRA. It is classed as a minor alarm, ofthe equipment type.

Appendix B: Alarms



Power SupplyThis indicates one or more of the three power supplies used in the PRA are operating outsideof the normal threshold limits. The three possible power supply alarms are shown in thefollowing table.

��

��

��

��

��

+5V digitalsupply


+5V analogsupply



Internal TemperatureThis indicates the temperature inside the PRA chassis is outside the normal operating upperand lower thresholds. It is classed as a warning alarm, of the environmental type.

)��*��

This indicates that one or more software alarms are present on the PRA. The possible alarmsare shown in the following table.

��

��

��

��

��












��

This indicates that one or more maintenance alarms are present on the PRA. They comprise:

• Modulation

• RF

Appendix B: Alarms



ModulationThis indicates that one or more modulation alarms are present on the PRA. The possiblealarms are shown in the following table.

��

��

��

IF loopbackactive

Warning Communications The IF loopback is enabled.


Warning Communications The digital loopback is enabled.

FEC disabled Warning Communications Forward Error Correction isdisabled

RFThis indicates that one or both RF related alarms are present on the PRA. The possible alarmsare shown in the following table.

��

��

��

RF loopbackactive



��

This indicates that one or more modem related alarm conditions are present on the PRA. Theycomprise:

• RX path failure

• RX path warning

RX Path FailureThis indicates that a modem related alarm is present, due to the loss of the PRA RX path. Ithas a single alarm under it, De-modulator not locked, which is present when the modem de-modulator is out of lock. This is classed as a critical alarm, of the communications type.

RX Path WarningThis indicates one of two possible modem related alarms, due to the detection of errors in thereceived data, is present on the PRA. The two possible alarms are shown in the followingtable.

��

��

��

��

� � � ��




Uncorrectableerrors



Appendix B: Alarms



%��-

This indicates that a radio link related alarm is present on the PRA.

Link failureThis indicates one or more of the radio link failure alarms is present on the PRA. Thesecomprise:

• TX Path Failure

• RX Path Failure

The TX Path Failure alarm indicates that a TX path failure alarm is present on the PRA. It hasa single alarm under it. The TX Synthesizer is not locked. This is classed as a critical alarm,of the equipment type. The two most probable causes of this alarm are:


• The upconverter module in the PRA is faulty.

The RX Path Failure alarm indicates that an RX path failure alarm is present on the PRA. Ithas a single alarm under it. The RX Synthesizer is not locked. This is classed as a criticalalarm, of the equipment type. The two most probable causes of this alarm are:


• The upconverter module in the PRA is faulty.

Link WarningThis indicates one or more of the radio link warning alarms is present on the PRA. Thesecomprise:

• TX Path Warning

• RX Path Warning

The TX Path Warning alarm indicates that one or both of the following alarms are present onthe PRA.

��

��

��

Forwardpower


Reflectedpower


The RX Path Warning alarm indicates that the AGC alarm is present on the PRA. Thisindicates that the AGC is outside the user configured upper and lower thresholds. It is classedas a Warning, of the Communications type.

Appendix B: Alarms



&�).��!��

The NMS (Network Management Systems) Board Alarm is the top-most alarm in the NMSBoard Alarm tree hierarchy. When it is present, it indicates an alarm is present on the NMSboard. The alarms that can trigger the NMS Board Alarm can be grouped into the followingtypes:

• Hardware

• Software

• Maintenance

• Radio communication

2��*��

The Hardware alarm indicates that the Component failure alarm is present on the NMS board.

Component FailureThis is present when the UART Failure alarm has been detected. This alarm is classed as aminor alarm, of the equipment type, and is present when a fault has been detected on the NMSboard UART.

)��*��

This indicates that one or more software alarms are present on the NMS board. The possiblealarms are shown in the following table.

��

��

��

��

��












Date and time notset


The software clock date and time hasnot been set.

��

This indicates that NMS Radio Loopback alarm is present on the NMS Board. It is classed asa Warning alarm, of the communications type, and is present when a loopback is enabled on aradio port NMS channel.

Appendix B: Alarms



%��

This is present when the Local Radio alarm is detected. This in turn indicates a NPR, PRA orPSW alarm could be present, which means that NMS board communications with the localradio have been lost. This is classed as a major alarm, of the communications type.

�$%744%�!!��

%�!,��!��

The RMA (Radio Modem Adaptor) Unit Alarm is the top-most alarm in the DXR 700 RMAAlarm tree hierarchy. When the RMA Unit Alarm is active, it indicates an alarm is present onthe RMA. The alarms that can trigger the RMA Unit Alarm can be grouped into the followingtypes:

• Hardware

• Software

• Maintenance

• Modem

2��*��

This indicates that a hardware alarm is present on the DXR 700 RMA. The alarms that cantrigger the hardware alarm can be grouped into the following types:


• Power supply


• Alarm inputs

Component FailureThis indicates that a component failure has occurred in the DXR 700. It is classed as a minoralarm, of the equipment type.

Appendix B: Alarms



Power SupplyThis indicates one or more of the three RMA power supplies is operating outside of thenormal threshold limits. The three possible power supply alarms are shown in the followingtable.

��

��

��

��

��

+5V supply Warning Equipment The +5V supply is outside of thenormal operating upper and lowerthresholds.


-48V ODUsupply

Warning Equipment The -48V supply to the ODU isoutside of the normal operating upperand lower thresholds.

TemperatureThis indicates the temperature inside the RMA chassis is outside the normal operating upperand lower thresholds. It is classed as a warning alarm, of the environmental type.

)��*��

This indicates that one or more software alarms are present on the DXR 700 RMA. Thepossible alarms are shown in the following table.

��

��

��

��

��



Corruption of the RMA configurationdata has been detected.


The RMA configuration does notmatch the hardware capability.



The RMA software is not fullycompatible with the hardware.



Insufficient memory for the RMAsoftware to operate correctly.

ODUcommunicationslost

Major Equipment The RMA has lost communicationswith the ODU.

Appendix B: Alarms



��

This indicates that one or more maintenance alarms are present on the DXR 700 RMA. Thepossible alarms are shown in the following table.

��

��

��

��

��

IF loopback active Warning Communications The IF loopback is enabled on theRMA.


Warning Communications The digital loopback is enabled onthe RMA.

Modulationdisabled

Warning Communications The modulation is disabled on one ormore of the installed modemmodules on the RMA.

��

This indicates that one or more modem related alarm conditions are present on the DXR 700RMA. They comprise:

• TX path failure

• RX path failure

• RX path warning

TX Path WarningThis indicates that one or more modem alarm conditions, resulting in loss of the TX path, arepresent on the RMA. The two possible alarms are shown in the following table.

��

��

��

Modulator notlocked

Major Communications One or more of the RMA modulators isout of lock.

TX alignmentmultiplexerlost sync

Major Communications The RMA TX alignment multiplexercannot synchronize to incoming data fromthe PMA.

RX Path FailureThis indicates that one or more alarm conditions, resulting in the loss of the RX path, arepresent on the RMA. The two possible alarms are shown in the following table.

��

��

��

Demodulatornot locked

Major Communications One or more of the RMA demodulators isout of lock.

RX alignmentmultiplexerlost sync

Major Communications The RX alignment multiplexer cannotsynchronize to incoming data from thedemodulators.

RX Path WarningThis indicates one of two possible modem related alarms, due to the detection of errors in thereceived data, is present on the RMA. The two possible alarms are shown in the followingtable.

Appendix B: Alarms



��

��

��

��

� � � ��




Uncorrectableerrors



�$%744��!!��

��!,��!��

The PMA (Protection Multiplex Adaptor) Unit Alarm is the top-most alarm in the DXR 700PMA Alarm tree hierarchy. When the PMA Unit Alarm is active, it indicates an alarm ispresent on the PMA. The alarms that can trigger the PMA Unit Alarm can be grouped into thefollowing types:

• Hardware

• Software

• Maintenance

• Traffic

• Radio link

• Tx switch

2��*��

This indicates that a hardware alarm is present on the PMA. The alarms that can trigger thehardware alarm can be grouped into the following types:


• Power supply

Component FailureThis indicates a component failure has occurred in the PMA. It is classed as a minor alarm, ofthe equipment type.

Appendix B: Alarms



Power SupplyThis indicates one or both of the PMA power supplies is operating outside of the normalthreshold limits. The possible power supply alarms are shown in the following table.

��

��

��

��

��



)��*��


��

��

��

��

��



Corruption of the RMA configurationdata has been detected.


The RMA configuration does notmatch the hardware capability.



The RMA software is not fullycompatible with the hardware.



Insufficient memory for the RMAsoftware to operate correctly.

��

This indicates that one or more maintenance alarms are present on the PMA. The possiblealarms are shown in the following table.

��

��

��

AIS outputenabled

Warning Communications AIS is enabled on all outgoingtributaries.

Trib radiofacing loopbackactive

Warning Communications The radio facing loopback isenabled for one or more tributaries.

Trib line facingloopback active

Warning Communications The line facing loopback is enabledfor one or more tributaries.

Manual TX pathenabled

Warning Communications TX protection switching is lockedon manual.

Manual RX pathenabled

Warning Communications RX protection switching is lockedon manual.

��

This indicates that one or more traffic related alarm conditions are present on the PMA. Theycomprise:

Appendix B: Alarms



• Trib port

• Trib n

Trib PortThis indicates that a traffic-related alarm is present on one of the PMA Tributary ports.

Trib nThis indicates one of the three possible alarms is present on the Tributary port n of the PMA.The three possible alarms are shown in the following table.

��

��

��


AIS Warning Communications AIS is being detected.

Note: That there is no AIS for somevariants.

Uncommissionedtraffic


%��-

This indicates that a radio link related alarm is present on the PMA. These comprise:

• Link failure

• Received bitstream errors

Link failureThis indicates one or more of the radio link failure alarms is present on the PMA. Thesecomprise:

• TX Path Failure

• RX Path Failure

Note: Either of these errors indicates that the DXR 700 link has failed.

The TX Path Failure alarm indicates that a TX path failure alarm is present on the PMA. Thisis classed as a critical alarm, of the equipment type.

The RX Path Failure alarm indicates that a RX path failure alarm is present on the PMA. Thisis classed as a critical alarm, of the equipment type.

Received Bitstream ErrorsThis indicates that data from the remote DXR 700 contains errors that cannot be corrected.This is classed as a warning alarm, of the quality of service type.

�$)*��

This indicates that one or more TX path protection switching alarms are present on the PMA.These comprise:

Appendix B: Alarms



• Switch oscillation limit

• Cannot switch

Switch Oscillation LimitThe Switch Oscillation Limit alarm indicates that the maximum number of protectionswitches within a given time period has occurred. This is classed as a minor alarm, of theequipment type.

Cannot SwitchThe Cannot Switch alarm indicates that the TX path cannot switch to the standby RMA/ODUchain. This is classed as a minor alarm, of the equipment type. The most probable cause isthat an alarm condition is active on the standby chain.

�$%744��,!��

��,,��!��

The ODU (Outdoor Unit) Unit Alarm is the top-most alarm in the DXR 700 ODU Alarm treehierarchy. When the ODU Unit Alarm is active, it indicates an alarm is present on the ODU.The alarms that can trigger the ODU Unit Alarm can be grouped into the following types:

• Hardware

• Software

• Maintenance

• Radio link

2��*��

This indicates that a hardware alarm is present on the ODU. The alarms that can trigger thehardware alarm can be grouped into the following types:


• Power supply

• Temperature

Appendix B: Alarms



Component FailureThis indicates a component failure has occurred in the ODU. It is classed as a minor alarm, ofthe equipment type.

Power SupplyThis indicates one or both of the ODU power supplies is operating outside of the normalthreshold limits. The possible power supply alarms are shown in the following table.

��

��

��

��

��



TemperatureThis indicates that one or both of the temperature alarms is present on the ODU. The possiblealarms are shown in the following table.

��

��

��

��

��

InternalTemperature

Warning Environmental The ODU internal temperature isoutside of the normal operating upperand lower thresholds.

PATemperature

Warning Environmental The ODU PA heat sink temperature isoutside of the normal operating upperand lower thresholds.

)��*��


��

��

��

��

��



Corruption of the ODU configurationdata has been detected.


The ODU configuration does notmatch the hardware capability.



The ODU software is not fullycompatible with the hardware.



Insufficient memory for the ODUsoftware to operate correctly.

Appendix B: Alarms



��

This indicates that one or more maintenance alarms are present on the ODU. The possiblealarms are shown in the following table.

��

��

��

RF loopbackactive



%��-

This indicates that a radio link related alarm is present on the ODU. These comprise:

• Link failure

• Link warning

Link failureThis indicates one or more of the radio link failure alarms is present on the ODU. Thesecomprise:

• TX Path Failure

• RX Path Failure

The TX Path Failure alarm indicates that a TX path failure alarm is present on the ODU. Ithas a single alarm under it, TX Synthesizer not locked. This is classed as a major alarm, of theequipment type. The two most probable causes of this alarm are:


• The upconverter module is faulty.

The RX Path Failure alarm indicates that a RX path failure alarm is present on the DXR 700.It has a single alarm under it. The RX Synthesizer is not locked. This is classed as a majoralarm, of the equipment type. The two most probable causes of this alarm are:


• The downconverter module is faulty.

Link Warning

• This indicates one or more of the radio link warning alarms is present on the ODU. Thesecomprise:

• TX Path Warning

• RX Path Warning

Appendix B: Alarms



The TX Path Warning alarm indicates that one or both of the following alarms is present onthe ODU.

��

��

��

Forwardpower


Reflectedpower


IF Cable ALC Minor Equipment The TX IF Cable ALC is outside of the normaloperating upper and lower thresholds. Theprobable cause is the RMA/ODU cable isdamaged.

The RX Path Warning alarm indicates that the RSSI alarm is present on the ODU. Thisindicates that the RSSI is outside the user configured upper and lower thresholds. It is classedas a Warning, of the Communications type.

)�!!�� Note: that in Phase 2 there is no support for Local Radio n and Remote Radio n alarms. Thesemay be supported in a future release of DXR NET, DXRproxy and SMA system software.

)�!,��!��

The SMA (Services Management Adaptor) Unit Alarm is the top-most alarm in the SMAAlarm tree hierarchy. When the SMA Unit Alarm is active, it indicates an alarm is present onthe SMA. The alarms that can trigger the SMA Unit Alarm can be grouped into the followingtypes:

• Hardware

• Alarm Board

• Software

• Maintenance

• Traffic

• Terminal Communication

Appendix B: Alarms



2��*��

The Hardware alarm indicates that the Component failure alarm is present on the SMA.

Component FailureThis indicates that one or more of the following alarms is present.

��

��

��

EOW board Minor Equipment A fault has been detected on the SMA EOWBoard.

Ethernet Minor Equipment A fault has been detected on the SMAEthernet hardware.

UART Minor Equipment A fault has been detected in the SMA UART. Alarm boardnot installed

Warning Equipment The SMA Alarm Board is expected but cannotbe detected.

SDM AlarmsIn addition, when the SMA uses one of the SDM Option Boards, the following three alarmscan be present:

Note: In the alarm hierarchy, the Option board not installed alarm appears under theComponent Failure alarm, and the Option slot 1 and Option slot 2 alarm appearunder the Option board not installed alarm.

��

��

��

Option boardnot installed

Warning Equipment An Option Board is expected but cannot bedetected.

Option slot 1 Warning Equipment Indicates either a component failure in anOption Board inserted into option slot 1 in theSMA, or that slot 1 has been configured for aboard that is not present in the SMA.

Option slot 2 Warning Equipment Indicates either a component failure in anOption Board inserted into option slot 2 in theSMA, or that slot 2 has been configured for aboard that is not present in the SMA.

!��.��-�

The Mark I Alarm Board alarm indicates that one or more of the alarms displayed in thefollowing table is present. The Mark I board has 12 input/output alarms. The alarms can beconfigured via DXR NET as either:

Inputs, activated by grounding the pin alarm

Outputs, when activated the alarm pin is grounded (maximum current capacity 120mA, maxvoltage 100V).

Dip switches are set to IN or OUT on the alarm circuit board to cut tracks that choose groundreference or isolated. These settings are made by the DMC engineer or in the factory when theSMA is assembled. The software must be set to match this configuration.

Appendix B: Alarms



!��.��-��

The Mark II Alarm Board has 6 input alarms and 6 output alarms. Input alarms are activatedwhen the alarm pin is grounded. When activated, the output alarms will ground the alarm pin(maximum carrying capacity 120mA, maximum voltage 100V).

A SMA output alarm, when raised, will connect the appropriate pin to ground, and normallyhas high impedance. Therefore, any alarm monitoring equipment must recognise thegrounding of the SMA alarm output as an active alarm. Output ports can withstand amaximum voltage of 100V, and can carry a maximum current of 120 mA.

Note: The SMA must reflect that a Mark II board is installed.

#NCTO 0COG 2GTEGKXGF5GXGTKV[

#NCTO 6[RG 2TQDCDNG %CWUG &GUETKRVKQP

Ground referencedinput 1a

Warning Equipment Alarm Board ground referenced input 1a isactive.

Ground referencedinput 1b

Warning Equipment Alarm Board ground referenced input 1b isactive.

��

��

��





















Appendix B: Alarms



)��*��

This indicates that one or more software alarms are present on the SMA. The possible alarmsare shown in the following table.

��

��

��

��

��

Configuration corrupt Major Processingerror










Date and time not set Minor Processingerror

The software clock date and time hasnot been set.

SDM AlarmsIn addition, when the SMA uses one of the SDM Option Boards, the following three softwarealarms can be present:

Note: In the alarm hierarchy, the Option 1 parameter fail and Option 2 parameter failappear under the Option board configuration alarm.

��

��

��

Option boardconfiguration


An optional SDM Board has been configuredwith invalid information by the SMA.

Option 1parameter fail


The Option Board inserted into option slot 1has been configured with invalid informationby the SMA.

Option 2parameter fail


The Option Board inserted into option slot 2has been configured with invalid informationby the SMA.

Appendix B: Alarms



��

This indicates that one or both of the maintenance alarms are present on the SMA. Thepossible alarms are shown in the following table.

��

��

��

��

��

AUX loopbackactive

Warning Communications An AUX port loopback is enabledfor one or more AUX ports on theSMA.

Ethernet test modeactive

Warning Communications Ethernet test mode is active on theSMA.

��

This indicates that one or more traffic related alarm conditions are present on the SMA. Theycomprise:

• AUX port

• NMS port

• V.24 port

AUX PortThis indicates that one or more of the AUX n alarms are present on the SMA. ‘n’ is the AUXport identifier, either A, B, C, or D.

The AUX n alarm indicates the LOS (Loss of Signal) alarm is present on AUX port n of theSMA (n = A, B, C, or D). The LOS alarm is classed as a Critical alarm, of theCommunications type. The most common cause is that the cable to the port has becomedisconnected.

NMS PortThis indicates that one or more of the NMS n alarms are present on the SMA. ‘n’ is the portidentifier, either IN or OUT.

The NMS n alarm indicates the LOS (Loss of Signal) alarm is present on NMS n of the SMA(n = IN or OUT). The LOS alarm is classed as a Critical alarm, of the Communications type.The most common cause is that the cable to the port has become disconnected.

Appendix B: Alarms



V.24 PortThis indicates that one or more of the V.24 n alarms are present on the SMA. ‘n’ is the portidentifier, either A, B, C or D.

The V.24 n alarm indicates one or both of the following alarms are present.

��

��

��

��

��

Connection failure Major Communications NMS connection failure with thedevice on this V.24 port hasoccurred. The probable cause is adisconnected V.24 port cable.

Unexpected unit Warning Communications NMS traffic is being received froman unexpected unit on this V.24 port.

SDM AlarmsIn addition, when the SMA uses one of the SDM Option Boards, the following four trafficalarms can be present:

Note: In the alarm hierarchy, Option 1 and Option 2 appear under the Option port alarm,and each of the Option 1 and Option 2 alarms has an Errors alarm under it.

��

��

��

Option port Major Communications There is a communications problemwith a SDM Board in the SMA.

Option 1 Major Communications There is a communications problemwith the SDM Board installed in slot1 of the SMA.

Option 2 Major Communications There is a communications problemwith the SDM Board installed in slot2 of the SMA.

Errors Major Communications There is a communications problemassociated with the data stream fromthe SDM Board installed in theassociated slot.

%��

This indicates that one or both of the following is present:

• Local Radio n

• Remote Radio n

Appendix B: Alarms



Note: ‘n’ is the port identifier, either A, B, C or D.The Local Radio n alarm indicates thatone or more of the following alarms is present on the relevant local radio, and theRemote Radio n alarm indicates one or more of the following alarms is present onthe relevant remote radio.

��

��

��

��

��

PMA Major Communications SMA communications with thisPMA has been lost.

RMA A Major Communications SMA communications with thisRMA has been lost.

RMA B Major Communications SMA communications with thisRMA has been lost.

ODU A Major Communications SMA communications with thisODU has been lost.

ODU B Major Communications SMA communications with thisODU has been lost

344) �� & �*��-!�� )�!There are eight new SMA alarms for the DXR 200. These alarms reflect the highest alarmcondition on the indicated radio. This enables the SMA to map this condition to a SMA event.

��

��

��

��

��

Radio Alarms A monitored radio is reporting analarm condition.

Local radio n(n=A,B,C,D)

A local (near end) monitored radio isreporting an alarm condition.

Critical Critical A local (near end) monitored radio isreporting a critical alarm condition.

Major Major A local (near end) monitored radio isreporting a major alarm condition.

Minor Minor A local (near end) monitored radio isreporting a minor alarm condition.

Warning Warning A local (near end) monitored radio isreporting a warning alarm condition.

Remote radio n(n=A,B,C,D)

A remote (far end) monitored radiois reporting an alarm condition.

Critical Critical A remote (far end) monitored radiois reporting a critical alarmcondition.

Major Major A remote (far end) monitored radiois reporting a major alarm condition.

Minor Minor A remote (far end) monitored radiois reporting a minor alarm condition.

Warning Warning A remote (far end) monitored radiois reporting a warning alarmcondition.

Appendix B: Alarms



�$%344!��An alarm hierarchy is generated based on the flat alarm structure supplied by the DXR 200terminal. It is the responsibility of DXR NET to create and maintain this hierarchical structure.

DXR NET will only display the alarms that are appropriate for the terminal type and slotconfiguration of the DXR 200.

Shaded entries indicate alarms that are specific to a given DXR 200 terminal type (i.e. SCP,DCP Main, SCR, etc)

2��*��

This indicates that one or more hardware alarms are present on the DXR 200. The possiblealarms are shown in the table below.

��

��

��

Slot n module supply voltage(where n = 1..15)

Warning Equipment A monitored supply voltage of themodule in this chassis slot isoutside of the normal operatingupper and lower thresholds.

Slot n DSL power supply(where n = 2..8)

Warning Equipment The current limiter hasmalfunctioned in this DSL LTmodule, resulting in overloaddetection in the DC-DC converter.The line output power supply hastherefore shut down.

Slot n DSL line unbalanced(where n = 2..8)

Warning Equipment One of the output lines has beengrounded on this DSL LT module,resulting in line unbalance.

Slot n DSL line voltage(where n = 2..8)

Warning Equipment The line voltage for this DSL LTmodule is outside of the normaloperating upper (110V) or lower(90V) thresholds. This is likely tobe due to excessive current beingdrawn from the U-interface or afault on the DC-DC converter.

TX temperature Warning Environmental The internal temperature of thetransmitter module is outside of thenormal operating upper and lowerthresholds.

SCP TX n temperature (where n= 1..2)

Warning Environmental The internal temperature of thistransmitter module is outside of thenormal operating upper and lowerthresholds.

Digital input n (where n = 1..8) Warning Equipment This digital alarm input, on thepower supply module, is active.

Configuration card failure Critical Equipment The configuration card is notresponding correctly to requestsfrom the system control module.

Appendix B: Alarms



)��*��

This indicates that one or more software alarms are present on the DXR 200. The possiblealarms are shown in the table below.

��

��

��

Boot loader active Critical Processingerror

The terminal is executing the bootloader application, instead of themain application.

Software damaged Critical Processingerror

The software within the terminalhas been damaged and may not beoperating correctly.

Unknown chassis Major Processingerror

The user configured chassis type isnot supported by the systemsoftware executing in this terminal.

Signalling setup error Major Processingerror

The system control module isunable to perform the signallingrouting required by the userdefined configuration.

Signalling port setup error Major Processingerror

One or more ports have beenconfigured with a signallingprotocol that is not supported bythe system software executing inthis terminal.

Slot n module not ready(where n = 1..15)


This interface module in this slothas either not yet been verified bythe system control module, or hasfailed verification. Either theconfiguration data or the interfacemodule software is invalid for theinterface module installed in thisslot.

SCP TX n not configured(where n = 1..2)


This transmitter module has notbeen included in the user definedconfiguration.

SCP RX n not configured(where n = 1..2)


This receiver module has not beenincluded in the user definedconfiguration.

SCP modem n not configured(where n = 1..2)


This modem module has not beenincluded in the user definedconfiguration.

Appendix B: Alarms



��

This indicates that one or more maintenance alarms are present on the DXR 200. The possiblealarms are shown in the table below.

��

��

��

Loopback active Warning Communications Either one of the DTI ports hasa loopback enabled or themodem has a loopback enabled.

Slot n DSL loopback(where n = 2..8)

Warning Communications An exchange generated EOC(Embedded OperationsChannel) command is inprogress, resulting in aloopback being enabled on oneof the channels of this DSLmodule.

DCP manual mode Warning Communications Dual Chassis Protectionswitching is locked on manual.

SCP manual mode Warning Communications Single Chassis Protectionswitching is locked on manual.

��

This indicates that one or more traffic related conditions are present on the DXR 200. Thepossible alarms are shown in the table below.

��

��

��

DTI n no signal(where n = 1..2)

Critical Communications Loss of signal on this systemcontrol module DTI port hasoccurred. The probable causeis a disconnected tributary cableor an external equipment fault.

DTI n frame sync(where n = 1..2)

Critical Communications The system control modulecannot synchronise to the framealignment pattern in the databeing received on this DTI port.

DTI n multiframe sync(where n = 1..2)

Critical Communications The system control modulecannot synchronise to themultiframe alignment pattern inthe data being received on thisDTI port.

DTI n AIS(where n = 1..2)

Warning Communications AIS is being detected on alltimeslots on this system controlmodule DTI port.

DTI n AIS TS16(where n = 1..2)

Warning Communications AIS is being detected onTimeslot 16 on this systemcontrol module DTI port.

DTI n ALM (where n = 1..2) Warning Communications ALM remote alarm indication isbeing detected on this systemcontrol module DTI port.

Appendix B: Alarms



DTI n multiframe ALM(where n = 1..2)

Warning Communications Multiframe ALM remote alarmindication is being detected onthis system control module DTIport.

ADPCM m DTI n no signal(where m = 1..4, n = A or B)

Critical Communications Loss of signal on this ADPCMmodule DTI port has occurred.The probable cause is adisconnected tributary cable oran external equipment fault.

ADPCM m DTI n frame sync Critical Communications This ADPCM module cannotsynchronise to the framealignment pattern in the databeing received on this DTI port.

ADPCM m DTI n multiframesync

Critical Communications This ADPCM module cannotsynchronise to the multiframealignment pattern in the databeing received on this DTI port.

ADPCM m DTI n AIS Warning Communications AIS is being detected on alltimeslots on this ADPCMmodule DTI port.

ADPCM m DTI n AIS TS16 Warning Communications AIS is being detected onTimeslot 16 on this ADPCMmodule DTI port.

ADPCM m DTI n ALM Warning Communications ALM remote alarm indication isbeing detected on this ADPCMmodule DTI port.

ADPCM m DTI n multiframeALM

Warning Communications Multiframe ALM remote alarmindication is being detected onthis ADPCM module DTI port.

Radio signalling path lost Major Communications NMS and signalling traffic isnot being received from theterminal on the far end of theradio link.

DTI n signalling path lost(where n = 1..2)

Major Communications NMS and signalling traffic isnot being received from theadjacent terminal on this systemcontrol module DTI port.

Clock source failure Major Communications The user configured clocksource has failed or isunavailable. Automaticswitching to the internallygenerated clock source hastherefore occurred.

ISDN sync lost Major Communications The DSL modules cannotsynchronise to the clock signalin the selected DSL clocksource circuit.

Appendix B: Alarms



��

This indicates that one or more modem related alarm conditions are present on the DXR 200.The possible alarms are shown in the table below.

��

��

��

Modem frame sync Critical Communications The modem cannot synchroniseto the received radio signal.This could be due to ademodulator or downconverterfault, but most likely is due tothe absence of RF signal fromthe far end, incorrect frequencysettings, or an antenna fault.

SCP modem n sync loss(where n = 1..2)

Critical Communications This modem cannotsynchronize to the receivedradio signal. This could be dueto a demodulator ordownconverter fault, but mostlikely is due to the absence ofRF signal from the far end,incorrect frequency settings, oran antenna fault.

Modem E3 BER Minor Quality of service The Bit Error Rate on thereceived radio signal exceedsthe 1x10-3 threshold.

SCP modem n E3 BER(where n = 1..2)

Minor Quality of service The Bit Error Rate on thereceived radio signal exceedsthe 1x10-3 threshold.

Modem E6 BER Warning Quality of service The Bit Error Rate on thereceived radio signal exceedsthe 1x10-6 threshold.

SCP modem n E6 BER(where n = 1..2)

Warning Quality of service The Bit Error Rate on thereceived radio signal exceedsthe 1x10-6 threshold.

DCP standby terminal active Warning Communications The Dual Chassis Protectedterminal has switched tostandby operation.

Appendix B: Alarms



%��-

This indicates that a radio link related alarm is present on the DXR 200. The possible alarmsare shown in the table below.

��

��

��

TX shut down Critical Equipment The TX module has shut downbecause an exception has beenraised. The probable cause isan invalid user configured TXfrequency or the module isfaulty.

SCP TX n shut down(where n = 1..2)

Critical Equipment The TX module has shut downbecause an exception has beenraised. The probable cause isan invalid user configured TXfrequency or the module isfaulty.

RX shut down Critical Equipment The RX module has shut downbecause an exception has beenraised. The probable cause isan invalid user configured RXfrequency or the module isfaulty.

SCP RX n shut down(where n = 1..2)

Critical Equipment The RX module has shut downbecause an exception has beenraised. The probable cause isan invalid user configured RXfrequency or the module isfaulty.

TX SWR Warning Equipment The TX SWR is outside theuser configured upper andlower thresholds.

SCP TX n SWR(where n = 1..2)

Warning Equipment The TX SWR is outside theuser configured upper andlower thresholds.

TX forward power Warning Equipment The TX forward power isoutside the user configuredupper and lower thresholds.

SCP TX n forward power(where n = 1..2)

Warning Equipment The TX forward power isoutside the user configuredupper and lower thresholds.

TX relative forward power Warning Equipment The TX relative forward poweris outside the user configuredtransmit power by +/- 3dB.

SCP TX n relative forward power(where n = 1..2)

Warning Equipment The TX relative forward poweris outside the user configuredtransmit power by +/- 3dB.

TX reverse power Warning Equipment The TX reverse power is abovethe user configured upperthreshold. The probable causeis a faulty antenna.

SCP TX n reverse power(where n = 1..2)

Warning Equipment The TX reverse power is abovethe user configured upperthreshold. The probable causeis a faulty antenna.

Appendix B: Alarms



RX signal strength Warning Communications The RX signal strength (RSSI)is outside the user configuredupper and lower thresholds.

SCP RX n signal strength(where n = 1..2)

Warning Communications The RX signal strength (RSSI)is outside the user configuredupper and lower thresholds.

Appendix C: Constellation Diagrams



!�� /��

+ � ��In a digital radio, the information contained in the baseband signal is carried by the signal’samplitude and phase when sampled with reference to a precisely timed ‘recovered’ clocksignal. The phase and amplitude of the baseband signal at the instant of sampling can beplotted on a polar graph to provide a Constellation Diagram.

A normal Constellation Diagram will show 4 tightly grouped points for DQPSK or 16 pointsfor 16QAM as shown in the following diagrams.

Each point contains many samples of the baseband waveform.

Figure 49: Constellation Diagram (DQPSK)




Figure 50: Constellation Diagram (16 QAM)

Data is derived from the part of the graph an individual sample falls into. Where points aretightly grouped, the noise margin is large, reducing the probability of bit errors. If the RFsignal is noisy, the points will be more spread and the noise margin reduced. This increasesthe probability of bit errors because of the Gaussian shape of the points.

Transmitter, receiver or RF Path problems may affect the placement of points or distort theirshape, reducing the fade margin for a given signal to noise ratio. This will result in degradedradio BER performance.

Some examples of signal degradations and their causes are shown below.

Figure 51: Constellation Diagram (DQPSK) - Example 1

Cause: Tight points with some spread out samples caused by Pulse Noise or similarinterference.




Action: Check for sources of interference.

Figure 52: Constellation Diagram (16 QAM) - Signal Degradation Example 2

Cause: Transmitter over driving or non-linearity causes the outer or corner points whichtake the most power to transmit to be moved from the centre of their decisionboundaries.

Action: Check and adjust far end TX output power.

Contact DMC Stratex Networks Inc. for further information.

Figure 53: Constellation Diagram (16 QAM) - Signal Degradation Example 3

Cause: Excessive phase noise in the transmitter or receiver.

Action: Replace terminal if the BER performance is unsatisfactory.

Note: Before you can correct this fault you must first isolate the problem to either thereceiver at the monitoring end or the transmitter at the remote end of the link.

Appendix D: Data Tables



!�� /��

+ � ��This appendix contains tables that contain the parameters you have to refer to when usingDXR NET.

�� ."� �� ) ��The following table shows recommended values for each radio type and capacity. An errorrate of 1 x 10-6 is shown.

Radio Capacity Link Data Rate Mbit/S

Bit Error Rate 1E-6

For DXR 100 4 x E1 9.728 10 2 x E1 4.864 5 1 x E1 2.432 2

4 x DS1 7.926 8 2 x DS1 3.648 4 1 x DS1 1.824 2

For DXR 700

1 x STM-0 60.441 60

2 x E3 79.836 80 1 x E3 40.769 41

16 x E1 40.762 41 8 x E1 19.747 20 4 x E1 9.792 10 2 x E1 5.01 5

1 x DS3 51.875 52

16 x DS1 30.731 31 8 x DS1 14.887 15 4 x DS1 7.382 7 2 x DS1 3.867 4




�� 8� ��"%�� )� �)�9

�$% 44

The following table shows the relationship between the frequency range and the frequencystep size, for a DXR 100 terminal.

Terminal Type Frequency Range Step Size

DXR 103 330-470 MHz 25 kHz

DXR 109 890-960 MHz 125 kHz

DXR 114 1350-1550 MHz 125 kHz

DXR 121 2000-2300 MHz 125 kHz

DXR 122 2100-2300 MHz 125 kHz

DXR 124 2300-2500 MHz 125 kHz

DXR 126 2500-2700 MHz 125 kHz

The following table shows the relationship between the frequency range and the frequencystep size, for a DXR 700 terminal.

Terminal Type Frequency Range Step Size

DXR 710 10.0-10.7 GHz 5 kHz

DXR 711 10.7-11.7 GHz 5 kHz

DXR 726 2.5-2.7 GHz 250 kHz

DXR 730 3.4-3.6 GHz 250 kHz

DXR 737 3.6-3.8 GHz 250 kHz

DXR 762 5.9-6.4 GHz 5 kHz

DXR 768 6.4-7.1 GHz 5 kHz

DXR 770 7.1-7.75 GHz 5 kHz

DXR 785 7.7-8.5 GHz 5 kHz

DXR 740 3.8-4.2 GHz 5 kHz

�/��* �

�$% 44

The following table shows the relationship between the modulation, the capacity, and thetransmitter power output at the Tx port, for a DXR 100 terminal.

Terminal Type

Modulation

QPSK 16 QAM

1 x E1 2 x E1 4 x E1 1 x E1 2 x E1 4 x E1

DXR 103 37 dBm 37 dBm - 31 dBm 31 dBm 33 dBm

DXR 109 37 dBm 37 dBm 37 dBm - - 29 dBm

DXR 114 33/37 dBm 33/37 dBm 37 dBm 33 dBm 33 dBm 33 dBm

DXR 121 33 dBm 33 dBm 33 dBm - - 33 dBm

DXR 124 33 dBm - 33 dBm - - - DXR 126 - - 33 dBm - - -




�$%744

The following table shows the relationship between the modulation, the capacity, and thetransmitter power output at the Tx port, for a DXR 700 terminal.

Terminal Type

Modulation

16 QAM 64 QAM 32 QAM

2 x E1 4 x E1 8 x E1 16 x E1 E3 8 x E1 DS3 STM-0

DXR 710 +28dBm +28dBm +28dBm +28dBm +28dBm +26dBm +26dBm +26dBm


DXR 724 +28dBm +28dBm +28dBm +28dBm +28dBm - - 26 dBm

DXR 726 +28dBm +28dBm +28dBm +28dBm +28dBm - - +26dBm








Appendix E: Using DXR NET with SDM Boards



!�� /'�,��$%&'�*��)��

.��

+ � ��This section covers how to use DXR NET to set up a data circuit between SMAs using theoptional Serial Data Module (SDM) boards. Such a circuit would allow communicationbetween data monitoring equipment and a remote management workstation. The circuitcomprises the SMAs containing the boards and any SMAs required to connect them.

AUX AAUX AAUX BAUX B

DXR 700 DXR 700 DXR 700 DXR 700

SMA SMA SMASDM SDM

SDM DATA CIRCUITMANAGEMENTWORKSTATION

DATA MONITORINGEQUIPMENT

Figure 54: Example SDM Data Circuit – Block Diagram

To set up the circuit, you need to:

• Configure SMA at either end of the link to use the SDM boards.

• Set up the cross-connects in any SMA used to carry the circuit between the SMA with theSDM boards.

• Set up the clocking hierarchy.

)��.��

The SDM boards allows serial data communications over the AUX bearers channel of theSMA. There are three types of board:

• Low Speed Daughter Board

• High Speed Daughter Board




• Co-directional Daughter Board

The boards are inserted into the two optional board slots in the SMA, thus each SMA canhave up to two boards.

Note: A SMA can have any combination of boards.

SERIALDATA

SERIALDATA

AUXAUX

DXR 700 DXR 700

SMA SMASDM SDM

TRAFFIC TRAFFIC

Figure 55: SDM SMA to SMA Communication – Block Diagram

��5��

Unless the two SMAs at each end of the circuit are in direct communication with one another,ie. at the opposite ends of the same radio link (as in Figure 55), you will have to relay the datacircuit via another SMA. You do this by setting up an internal cross-connect in eachconnecting SMA.

AUXAUXAUXAUX

DXR 700 DXR 700 DXR 700 DXR 700

SMA SMA SMASDM SDM

CROSS-CONNECT SMA

Figure 56: SDM Cross-connect SMA – Block Diagram

��-��2� ��"

To synchronize communication between the SDM boards, each SMA on the data circuitshould be using the same timing signal. Ensure this by selecting one of the SMAs as theprimary clock source for the others (you can also select another SMA as the secondary clockas required). This is known as setting up a clocking hierarchy. The primary clock source ofthe selected SMA is set to free-running (clock generated internally), the other SMAs havetheir primary clock source set to the port (AUX port or NMS In or NMS Out port) by whichthey are connected to the selected SMA.




AUX A AUX A AUX B AUX A

DXR 700 DXR 700 DXR 700 DXR 700

SMA SMA SMA SDM SDM

PRIMARY: FREE-RUNNING SECONDARY: FREE-RUNNING

PRIMARY: AUX A SECONDARY: FREE-RUNNING

PRIMARY: AUX A SECONDARY: FREE-RUNNING

Figure 57: SDM SMA Clocking Hierarchy

��#��-��

)�!� ��

The SMA Details tabbed page in the Commissioning Workspace now has the followingadditional sections.

• Option Slot 1

• Option Slot 2

Option Slot SectionsDepending on the type of board inserted into their associated slot, the Option Slot sectionscan contain the following fields:

Note: The Board ID text field will always be present, but the other three fields are onlypresent when either a low speed or high speed daughter board has been inserted intothe appropriate slot.

• Board ID text

• Part Number

• Serial Number


The Board ID text will contain one of the following:

• High speed daughter board installed

• Low speed daughter board installed

• Co-directional daughter board installed

• Unknown daughter board installed

• Option board not installed




The details contained within the Part Number, Serial Number and Software Version fields areself-explanatory.

�� #��-�� The Maintenance Workspace has the following tabbed pages:

• Alarms

• SMA Details

!��

The Alarms page now has the additional alarms described under the Action Table heading inthe Configuration Workspace section.

)�!� ��

The changes to the SMA Details tabbed page are as described in the CommissioningWorkspace section.

) ��) ��*��)��To set up a serial data circuit using the SDM boards you need to:

• Configure the SMA containing the SDM boards.

• Set-up cross-connects in any SMA relaying the circuit between the SMA with the boards.

• Set-up the clocking hierarchy.

An outline of the procedure is as follows:

Step 1: Identify the data rate required by the equipment the circuit is to connect.

Step 2: Select the SDM boards that give the required performance.

Step 3: Check that the SMA that will contain the boards has both channels and free datacapacity to support the boards.

Step 4: Identify any SMA required to relay the data circuit, and check that they have portsavailable for the cross-connections.

Step 5: Configure the SMA at either end of the data circuit for the SDM boards.

Step 6: Set-up the required cross-connects in any relay SMA.

Step 7: Set-up the clocking hierarchy.

Step 8: Test the data circuit to see that it can carry the required data.




��*)� �� .��

You can use the following procedure to configure a Low Speed Daughter Board in an OptionPage.

Note: We advise that you have read and understood the material under the Option Pagesheadings in the Configuration Workspace before attempting to use this procedure.Pay special attention to any restrictions on the values you can select, both on thecurrent board, and any other board present.

Procedure


Step 2: Use the arrow keys to display the Option pages.

Step 3: Select the option page for the slot the board occupies.

Step 4: Click on the arrow in the Option Board Type field, and select “Low Speed DaughterBoard” from the drop-down menu.

Step 5: Click on the arrow in the Cross connect to field, and select the AUX port on theSMA that the board is to use from the drop-down menu.

Step 6: Click on the arrow in the Channel field, and select the channel on the AUX port youwant the board data stream to start at from the drop-down menu.

Step 7: For each circuit you want to enable on the board, select the Active check box in theappropriate Circuit section. Click on the arrow in the Mode field, and select thecircuit mode of operation from the drop-down menu.

Step 8: For a circuit operating in the Sync mode, click on the arrow in the Data Rate field,and select the number of bits per second from the drop-down menu. Ensure thisvalue does not contradict the values set in the Channel field, or the settings on anyother board.

Step 9: For a circuit operating in the Async mode, click on the arrow in the Data Rate field,and select the number of bits per second from the drop-down menu. Ensure thisvalue does not contradict the values set in the Channel field, or the settings on anyother board. You can also select values for the Data Bits, Stop bits, Bit shave andParity fields by clicking on the arrow in each field, and selecting from the drop-down menu, and input an integer value for the Break length field.

Step 10: Select one of the SMAs, and then select the Port and EOW Settings tabbed page inthe Configuration Workspace. In the Clock Sources section, click on the Primaryfield, and select Free-running. Then click on the Secondary field, and select theAUX port that the SDM uses to communicate with the remote SDM.

Step 11: Select the SMA at the opposite end of the data circuit from the SMA in Step 10, andthen select the Port and EOW Settings tabbed page in the Configuration Workspace.In the Clock Sources section, click on the Primary field, and select the AUX portthat the SDM uses to communicate with the remote SDM. Then click on theSecondary field, and select Free-running.




Step 12: When you have made your changes, select the Commit button in the Toolbar.

The changes you have made will be reflected in the network blueprint. If you are not going tomake any further changes to the SMA configuration, select the Write Configuration button inthe Toolbar. The configuration of the SDM daughter board in the SMA will now change toreflect the values set in the blueprint.

��2��)� �� .��

You can use the following procedure to configure a High Speed Daughter Board in an OptionPage.


Procedure




Step 4: Click on the arrow in the Option Board Type field, and select “High Speed DaughterBoard” from the drop-down menu.


Step 6: Click on the arrow in the Channel field, and select the channel on the AUX port youwant the board data stream to start at from the drop-down menu.

Step 7: Select the Active check box in the Circuit 1 section. Click on the arrow in the DataRate field, and select the number of kilobits per second from the drop-down menu.Ensure this value does not contradict the values set in the Start at channel field, orthe settings on any other board.



Step 10: When you have made your changes, select the Commit button in the Toolbar.




The changes you have made will be reflected in the network blueprint. If you require nofurther changes to the SMA configuration, select the Write Configuration button in theToolbar. The configuration of the SDM daughter board in the SMA will now change to reflectthe values set in the blueprint.

��5�� .��

You can use the following procedure to configure a Co-directional Daughter Board in anOption Page.


Procedure




Step 4: Click on the arrow in the Option Board Type field, and select “Co-directionalDaughter Board” from the drop-down menu.


Step 6: Click on the arrow in the Start at channel field, and select the channel on the AUXport from where you want the board data stream to start using the drop-down menu.



Step 9: After you have finished making your changes, select the Commit button in theToolbar.

The changes you have made will be reflected in the network blueprint. If you are not going tomake any further changes to the SMA configuration, select the Write Configuration button inthe Toolbar. The configuration of the SDM daughter board in the SMA will now change toreflect the values set in the blueprint.




) ��,��5�� 5��

You can use the following procedure to set up the cross-connects required to relay datastreams between SDM boards in other SMA. These cross-connects are made between any twoavailable AUX port channels.

Note: We advise that you have read and understood the material under the Cross-connectPages heading in the Configuration Workspace before attempting to use thisprocedure. Pay special attention to any restrictions on the connections you canselect.

Procedure


Step 2: Use the arrow keys to display the Cross-connect page.

Step 3: Select the Cross-connect page.

Step 4: To select a manual cross-connect, move the mouse on the cross-connect grid toselect the AUX port channels you wish to cross-connect, then click the left mousebutton.

Step 5: To remove a manual cross-connect, move the mouse on the cross-connect grid toselect the cross-connected channels, then click the left mouse button.

Step 6: After you have finished making your changes, select the Commit button in theToolbar.

The changes you have made will be reflected in the network blueprint. If you are not going tomake any further changes, select the Write Configuration button in the Toolbar. Theconfiguration of the SMA will now change to reflect the values set in the blueprint.

) ��,�� -��2� ��"

You can use the following procedure to set up the clocking hierarchy required to synchronizedata streams between SDM boards.

Note: We advise that you have read and understood “Setting up a Clock Source in a SMA”in Section 4.

Procedure

Step 1: Select the SMA you wish to use as the primary clock source for the data circuit.

Step 2: Set the primary clock source of this SMA to free-running (generated internally).

Step 3: Set the primary clock source of all the other SMAs in the circuit to the port they areconnected to by the clock source SMA.




!�� /��,��$%&'�*��!&

+ � ��You can connect the PC running DXR NET to a DXR NETwork in three ways:

Terminal connection, directly to a terminal (DXR 700, or DXR 100 without NMS board).

NMS connection, either directly, or via a modem, to a NMS unit (SMA or DXR 100 withNMS board).

Ethernet connection, with the connection made over a LAN.

Terminal and NMS connections have already been previously covered (see Section 4 fordetails). This document covers the ways in which you can use the Ethernet connection toaccess a DXR NETwork over a LAN.

Note: This document assumes that you are familiar with the concepts of IP addressing andDXR blueprint design, as covered in Section 4.

'�� % 8��

Before you can use the DXR NET Ethernet connection, you must fulfil the followingrequirements:

Your PC must have an Ethernet port set up.

You must have selected the Ethernet connection option for DXR NET (see Selecting theDXR NET Ethernet Interface On Your PC).

If you are connecting to the DXR NETwork via a SMA, you must have set the IP address ofthe SMA.

In addition, if you are using a router to connect your PC to the network, you must have asuitable router (eg, Cisco 2509) and any required hub cross-connect cabling.

Note: Before you can set up the SMA for Ethernet, you should have carried out all otherconfiguration operations using the Setup port.

'��

When using the Ethernet connection to either a Router or a SMA, DXR NET communicateswith the NMS Unit or the Router Software using SNMP and TFTP.




PC Running DXR NET

SMA

DXR NET

TCP/IP overEthernet

SMA

LAN

Figure 58: SMA Ethernet Connection

% �� $%&'�*��-��'��

There are two main advantages in your connecting to a DXR NETwork via the Ethernetconnection:

• You can connect to the network via a corporate LAN.

• You can connect to the network over the Ethernet, i.e. via an ISP.

With both methods, you can connect your PC to the network without having to attach it to anyparticular network element, or without having to be at any particular location (as long as youcan access the LAN). Ethernet connection therefore greatly increases your ability to access aDXR NETwork, although it does require slightly more planning and configuration to obtainthe full benefits.

�!&�� $%&'�*��-�There are three possible ways in which a DXR NETwork can be connected to a LAN:

Via a router directly connected to a piece of DXR equipment.

Via a SMA connected directly to a LAN.

Via a router connected to a LAN containing a SMA.

Note: The LAN may be a hub, or you may use a "cross-over" cable - see DXR 700installation for details.

�� %�� $%'8��

PC

Router DXR Equipment

V.24 Port V.24 Port

LAN

Ethernet protocol

PPP

Figure 59: Direct Router Connection to DXR Equipment




In this case, the router is directly connected to a piece of DXR equipment, via the router V.24port. The router communicates with the equipment using Point-to-Point Protocol (PPP), as fora Terminal or NMS connection between a PC running DXR NET and the equipment. Youwould connect your PC to the router over the LAN, using Ethernet protocol to communicatewith the router.

�� )�!�� !&

PC

SMA

LAN Ethernet protocol

Ethernet port

LAN port

Figure 60: Direct SMA Connection to LAN

In this case, the SMA is directly connected to the LAN, via the SMA LAN port. You wouldconnect your PC to the LAN using the Ethernet connection, which will enable you tocommunicate with the SMA using SNMP and TFTP.

�� )�!��%��

PC

Router

SMA

LAN Port

LAN

Ethernet protocol

LAN

Ethernet protocol

Figure 61: Connection to SMA via a Router

In this case, there are two LANs, the one your PC is connected to, and the one the SMA isdirectly connected to, via the SMA LAN port. The LANs are connected via a Router. Youwould connect your PC to the LAN using the Ethernet connection, then access the Router.You will then be able to communicate with the SMA using SNMP and TFTP.




��!&�� $%&'�*��-Connecting a DXR NETwork to a LAN (corporate or ISP) requires three things to be designed:

• the LAN

• the DXR NETwork

• the interface between them

The design of the LAN is outside the scope of this document, and DXR NETwork design hasalready been covered in Section 4. The main factor to be considered in connecting aDXR NETwork to a LAN is therefore the way the two networks are connected.

�!&6�$%&'�*��-��

Note: It is assumed that you are familiar with the concepts of IP addressing, as covered inSection 4.

Both the DXR NETwork and the LAN will use IP addressing to decide the routes networkmessages take to reach their destination. This means that the LAN will need an IP address forthe DXR NETwork, and any NMS units in the DXR NETwork will need an IP address for theLAN.

LAN RequirementsThe IP address that the LAN uses to talk to the DXR NETwork needs to fulfil two criteria:

• It must be a valid address.

• It must not conflict with any other address on the LAN.

This last condition is very important in LANs that use dynamic addressing to assign IPaddresses to PCs as they log-on.

Although the DXR NETwork uses IP addressing, the address range we advise you to use hasbeen specifically selected so as not to conflict with the addresses on other IP networks. Thismeans that it is very unlikely that DXR IP addresses will fit into the range of addressesrecognised by another LAN, and the LAN will not be able to “see” the DXR NETwork, as itwill not have a valid address.

Note: In a LAN using dynamic addressing, we advise you to select an address that is notgoing to ever be allocated by the address server.

DXR NETwork RequirementsThere are no address restrictions for the LAN/DXR NETwork interface that apply to theDXR NETwork. This is because the DXR NETwork address range is advised, not enforced, andthere are no checks on address validity. Any addressing conflicts between the DXR NETworkand the LAN should be dealt with at the design stage of the network blueprint. The onlyrequirement, therefore, is that any NMS units (SMA or DXR 100 with NMS) on theDXR NETwork must have a route set-up to the interface address.




) ��,�� %�� $%'8�� Consult the documentation that came with your router.

) �� )�!�� !&To set up a direct connection between a LAN and a SMA, you need to do the following:

• Set up the SMA LAN port.

• Change the network blueprint so that the DXR NETwork can communicate with the LAN.

• Manually set up the route to the SMA on your PC.

) �� )�!�!&��

To set up the LAN (Ethernet) port on a SMA, proceed as follows:

Note: We advise you carry out the following while directly connected to the SMA.

Procedure

Step 1: Obtain the network IP address for the SMA from your IT department.

Step 2: Run DXR NET, and select the Configuration Workspace.

Step 3: Select the IP Address Table from the Configuration Menu.

Step 4: Select the SMA in the IP Address Table.

Step 5: Click the Advanced button.




Figure 62: Advanced IP Address Dialog BoxStep 6: In the Advanced Address dialog box, select the Ethernet interface, enter the address

from Step 1 into the IP Address column, set the last octet of the IP mask to 0, select“None” in the Numbered column, then click the OK button.

Step 7: Double-click the SMA Ethernet interface in the IP Address Table. The red tick thatwas next to the V.24 will now appear next to Ethernet.




Figure 63: IP Address Table with Ethernet EntryStep 8: Select the Write Configuration button in the Toolbar to save the changes to the

SMA.

Step 9: If you wish to save the changes to the active blueprint, select the Commit button inthe Toolbar.

The LAN port on the SMA is now set up to use Ethernet. Quit DXR NET if it is no longerrequired.

& �*��-.��

The network blueprint changes consist of changing the routing tables of the SMA and all theother NMS units on the network so that they can use the SMA Ethernet port IP address tocommunicate with the LAN. The procedures for changing the routing tables are as alreadycovered, with one important exception. That is, if an octet of the SMA Network IP address iszero, the corresponding octet in the Mask IP Address must also be set to zero.




Example

A small DXR NETwork containing two SMAs is connected to a LAN via one of the SMA. TheSMA that is connected to the LAN is known as "SMA Bottom", and the other SMA is knownas "SMA Top". SMA Top communicates with SMA Bottom via the AUX A ports.

Note: We assume here that the network is already up and functioning, using DXR NET andthe V.24 interface.

The IP address of the SMA Bottom Ethernet port will be 192.192.0.41, mask 255.255.255.0.This is given by the LAN administrator and will be entered into the Advanced IP Addresstable for the SMA Bottom Ethernet interface, with the specified mask.




In the SMA Bottom Routing Table, the Destination IP Address for the Ethernet interface willbe 192.192.0.0., and the Mask IP Address will therefore be 255.255.255.0. In the SMA TopRouting Table, an entry will be added for the AUX A port with a Destination IP Address of192.192.0.0. and a Mask IP Address of 255.255.0.0.

) �� %�� )�!

You need to manually set the route your PC uses to communicate with the SMA network, asthe SMA IP addresses are not visible on the LAN. As a result, the PC will be unable toaddress a message to the SMA until you set the route. You set the route using the "route add"facility in DOS.

To add the route, you need the subnet address of the SMA network, and the IP address of theEthernet port on the SMA. You then use the DOS route add command.

You would normally obtain the network IP address in consultation with your LAN SystemAdministrator (your IT department, or whoever else is responsible for the LAN). Deriving theother two factors is slightly more complicated, as they depend on the degree of access youwant to have to the DXR NETwork. You must also take into account any possible addressingconflicts between the IP addresses used in the network, and those used on the LAN. Normally,we advise you set the Sub-net address to 10.0.0.0 and the mask to 255.0.0.0, as this willenable you to access the entire DXR NETwork.

To manually set the route your PC uses to communicate with the SMA, proceed as follows:

Step 1: Restart your PC and log-on to the LAN.

Step 2: Go to MS-DOS window, and at the DOS prompt, enter the following:

route add <Sub-net IP address> mask <Sub-net IP addressmask> <DXR NETwork IP address>

For this example, it would be:

route add 10.0.0.0 mask 255.0.0.0 192.192.0.41

This commands tells the PCs IP code to send messages for the 1.0 Network to the address192.192.0.41, which will know how to route the traffic.

You can check the routes on the PC using the command "route print".




Figure 64: Adding Route to PC at DOS prompt

Step 3: Return to the PC desktop, and run DXR NET.

Step 4: If required, select the Ethernet connection for DXR NET (see Selecting the DXR NET

Ethernet Interface), then open the blueprint for the DXR NETwork and select theConnect button.

You should now be able to access the network over the LAN.

) ��)�!�� !&��%�� Consult the documentation supplied with your router.

) � �� $%&'�'�� To select the Ethernet connection option for DXR NET network interface, proceed as follows:

SELECTING THE INTERFACE. You must select the right type of interface for yourconnection, or DXR NET will not be able to access the network.

Procedure

Step 1: Run DXR NET from the desktop.

Step 2: Select the Communication Setup option from the Tools menu.

Step 3: Select the Ethernet interface from the Scroll Box in the Communications Setupscreen.

Step 4: If you wish to make the Ethernet interface the default setting, click the Save Settingsbutton.

Step 5: Click the OK button to change the interface to the selected interface.

The DXR NET interface will now change to your selection.

Note: A successful Ethernet connection is indicated by the network icon in the lower right-hand corner of the DXR NET GUI.

Appendix G: Using DXR NET with DXR 200



!�� /+�,��$%&'�*��$%344

+ � ��This section covers how to use DXR NET to manage networks that incorporate DXR 200radios.

DXR NET allows for the monitoring of DXR 200 alarms, and viewing of system details suchas hardware and software types and versions .

DXR 200 is incorporated into the DXR NET Network Management environment by treatingthe SMA as a "proxy" for a DXR 200 network. The purpose of this functionality is to create abridge to the DXR 200 so that DXR NET and ProVision can monitor the DXR 200 radio.

Note: This appendix assumes that you are familiar with the concept of DXR blueprintdesign, as covered in Section 4 of this manual.

�� $%344The SMA creates an SNMP bridge between the manager and the DXR 200. The SMAconnects a V.24 port to the DTI or set-up connector on the DXR 200. The manager usesTCP/IP to communicate to the SMA, and the SMA communicates to the DXR 200 using theDXR 200 proprietary protocol. In this manual, the manager is DXR NET, although ProVisionmay also use the connection.

When the PC running DXR NET is connected to a DXR 200 radio via the SMA, DXR NET

identifies the DXR 200 terminal unit using the Terminal Number assigned to the DXR 200.The DXR NET software uses TCP/IP addressing to communicate with the SMA.

The DXR 200 software has not been modified to recognise the SMA, and communicates withit as if it is DXRsetup or DXRview. The SMA does not carry any DXR 200 signalling. As aresult, if a SMA is used between two DXR 200 networks, the networks are not aware of eachother due to the SMA.




PC Running DXR NET

SMA

DXR NET

TCP/IP overV.24

DXR 700

DXR 200

V.24 connector

ProVision

V.24 connector

Figure 65: SMA NMS V.24 Connection

�$%344& �*��-!�� % 8�� DXR NET communicates with the DXR 200 terminals via the SMA, identifying each DXR200 connected to the network with a combination of SMA IP address, SMA port the DXR 200is attached via, and the DXR 200 terminal number.

The address is considered as:

SMA IP address, PORT(A-D), TERMINA #

In a network with multiple networks of DXR 200s, each group of DXR 200s connected via aSMA port is considered to be a network. DXR 200s on other ports, or on other SMAs, areseparate networks, and can re-use the DXR 200 Terminal numbers.

� �� &��

DXR NET requires a terminal number field to be completed when a DXR 200 is added to theblueprint. This information is pre-set in the DXR 200 using DXRsetup. If a terminal numberis not correctly written to the blueprint (i.e. if it does not match the number defined byDXRsetup), DXR NET will be unable to communicate with the DXR 200.

� ��&�� ,��

The Terminal Number relates to the Control Module of the SMA. The SMA constantly pollsthe DXR 200 for its alarm structure and lists all standard DXR 200 alarms. All terminals ineach DXR 200 network are accessed via the DXR 200 that is attached to the SMA.




�$%344& �*��-.�� DXR NET writes the DXR 200 data from the blueprint to the configuration data that is sent tothe SMA.

DXR 200 terminals can be deployed at sites in the network blueprint, and then selected asbeing managed by a SMA. When a SMA becomes a manager, each DXR 200 is assigned to aparticular SMA port. This port is connected to the DXR 200, and all management informationwill use this port and DXR 200 connection.

�� /��

If a DXR 200 is a complex model, such as Single or Dual chassis protected, or a single chassisrepeater, it will contain multiple control modules. Each control module must be deployed onthe blueprint as a DXR 200, with it own terminal number. DXR NET does not work with thephysical representation, but communicates with each control module via its own terminalnumber.

��

A maximum of 500 DXR 200 terminals can be added to the blueprint. Each SMA can have upto 4 directly attached DXR 200 terminals. Each of these can be connected to a network of upto 255 terminals, to the maximum of 500 per SMA and 500 per blueprint.

The terminal number must be unique within a network, but, since each port on each SMA is aseparate network, terminal numbers can be re-used.

�!� �� ! �� "��#$$��"� %&

Figure 66: Deployment Option 1 - Direct ConnectionIf connected to the SMA - deploy the SMA then position the DXR 200 below the SMA.

Site

SMA

DXR 200Terminal 2

DXR 200Terminal 3




Figure 67: Deployment Option 2 - Indirect Connection.

Deploy the DXR 200 to a site and then set up indirect connection to a SMA at a later point.

Figure 68: Deployment Option 3 - Intermediate ConnectionThis figure shows an intermediate step. The DXR 200 terminal could later be connected to theSMA via the Port and EOW settings page, or it could be directly connected to the SMA viathe Terminal Management page; or, it could be indirectly connected to the SMA via theManagement Setup page.

��#��-�� $%344� ��You use the Configuration Workspace to write the pre-defined terminal numbers to theblueprint, to create terminal names, to configure the SMA to communicate with the DXR 200and to set up remote radio connections.

You cannot configure the DXR 200 terminal using DXR NET. Configuration must beperformed by a PC running DXRsetup that is directly connected to the DXR 200 network.

Configuration Workspace can work with saved data, so you can build a network blueprintoffline. i.e. you can deploy and configure the DXR 200 data when your PC is not actuallyconnected to an element.

Site

DXR 200

Terminal 1

SMA

Site

DXR 200Terminal 1




� ��"�� $%344& �*��-

Procedure

Step 1: First create all the sites within the blueprint.

Step 2: Add each DXR 200 at the site that it is located.

Note: For complex DXR 200 terminals, deploy one instance of a DXR 200 for eachcontrol module (these of course should be at the same site).

Step 3: Name each DXR 200 terminal, and assign the correct terminal number to eachterminal (see "Deploy the DXR 200 procedure" in this appendix).

Step 4: Where creating radio links, select the remote site and remote terminal on the RFLink Setup page. For non-radio DXR 200, this is not necessary.

Step 5: Deploy the SMAs in the blueprint at the correct sites, and implement the IP table,routing table and other items as described previously for the SMA.

Step 6: Enter an integer between 1 and 254 in the Terminal Number scrolling text box tomatch the terminal number previously defined in DXRsetup.

Step 7: On the “ports” page of SMA configuration, assign the correct port to the attachedDXR 200. This will change the Terminal Management page to reflect thisconnection. Perform this task for all DXR 200s that are connected to SMAs in theblueprint.

Step 8: On the Terminal Management page, it is possible to now add all DXR 200s that arenot directly connected to a SMA. This can be done by selecting the SMA that is thebridge to the DXR 200 network on the explorer tree, and them adding them to thecorrect port at terminal management time.

Step 9: Find the DXR 200 that is directly connected to the SMA by expanding the networkunder the SMA if required.

Note: Unmanaged DXR 200 terminals appear as light grey icons in the explorer tree pane,and, once managed, they become dark and solid.

��

When you select a DXR 200 terminal in the Explorer Tree Pane, the ConfigurationWorkspace displays the following tabbed pages:

• General Setup

• Management Setup

• RF Link Setup

Note: All tabbed pages for a SMA in the Configuration Workspace are documented indetail in Section 2 of this manual and will not be covered here.




+ � ��) ��

Figure 69: General Setup Page - DXR 200

Terminal DetailsThe Terminal Details section has two text fields:

• Type

• Terminal Name

The Type field contains the equipment description of the terminal. This is determined byDXR NET, depending on the unit selected in the Explorer pane and you cannot change it.

The Terminal Name field is used to hold the name assigned to the terminal in the NetworkBlueprint. If you have not assigned a name to the terminal, the field contains the default string"Terminal aaa" where "aaa" is a three letter sequence. You can change the name by selectingthe field with the mouse and typing in the new name.

The Terminal Name must be unique within the blueprint and can be between 1 and 16characters long. The Terminal Name is not the terminal number, but you may use a terminalname that relates to the terminal number, i.e. Terminal 2, if this does actually reflect thecorrect terminal number.




Site InformationThe Site Information section has three text fields:

• Name

• Description

• Contact Information

The Name field is used to hold the name you assigned to the site in the Network Blueprint. Ifyou have not assigned a name, the field is assigned the default string “Site n” where “n” is aninteger relating to the number of radios in the network.

The Description field is used to hold any details of the site you feel should be noted. If you donot input any details, the field is left blank.

The Contact Information field is used to hold the details of the person responsible for the site.If you do not input any details, the field is left blank.

Normally, you would have set the details in these fields when you created the networkblueprint. However, you can change the details by selecting the field with the mouse, andtyping in the new details.

Note: You can only change the Description and Contact Details fields when the Site icon(not the terminal icon) is selected in the Explorer Tree.

�� ) ��

DXR 200 terminals can be managed or un-managed. A managed terminal has a SMA gatewaydefined to it. This is achieved by adding a site, adding a SMA to a site, deploying DXR 200sto the SMA and saving the configuration to the network blueprint. Terminals that are un-managed by a SMA are displayed as greyed out icons in the Explorer Tree pane. Once a DXR200 terminal is managed, it ceases to be greyed out and can now receive alarm information orterminal details information.

Note: DXR 200 terminals cannot be monitored unless they have a managing SMA assigned.




Figure 70: Management Setup Page - DXR 200

Terminal DetailsThe Terminal Details section contains the Terminal Number list box. This scrolling list box isused to assign the Terminal Number previously defined in DXRsetup

ManagedThe Managed section has two scrolling list boxes:

• Managing SMA

• SMA AUX Port

These list boxes are greyed out if the terminal is un-managed by a SMA. To assign a SMA toa terminal, click the Managed check box and select the SMA name and V.24 port you requirefrom the options displayed when you click on the scrolling list box arrows.

%��-) ��

The RF Link Setup page allows you to pair radios at each end of a link. The terminal you wishto link to (from your currently selected terminal) is known as a remote terminal.




Figure 71: RF Link Setup Page - DXR 200The RF Link Setup tabbed page has two scrolling list boxes:

• Site Name

• Terminal Name

Note: The list boxes are greyed out if the Remote Terminal check box is unchecked.

To set up a remote terminal, click on the Remote Terminal check box field with the mouseand select the required Site Name and Terminal Name from the options displayed when youclick on the scrolling list box arrows.

Note: You can assign a radio to a remote link only where that radio has not already beenused as a remote link.

You can navigate from a terminal to the remote terminal by right clicking on the mouse andselecting "Go to Remote Link".




� ��"�� $%344

Procedure


Step 2: Add a network site by choosing the Add Site command from the ConfigurationMenu, or by right-clicking the mouse button and choosing "Add Site".

Step 3: Enter the Site Name in the Site Information screen.

Step 4: Click on the Commit button in the Toolbar to commit the change to the blueprint.

Step 5: Add a DXR 200 network element to the site by selecting the site icon in theExplorer Tree pane and choosing the Add Network Element command from theConfiguration menu, or by right-clicking the mouse button to display the dialog boxbelow.

Step 6: Select DXR 200 from the list to add this terminal element to the selected site.

Step 7: Select the DXR 200 terminal icon you have added in the Explorer Tree pane.

Step 8: Enter the Terminal Name in the General Setup page.


Step 10: Select the Management Setup settings tabbed page.




Step 11: Enter an integer between 1 and 254 in the Terminal Number scrolling text box tomatch the terminal number previously defined in DXRsetup


Step 13: Select the RF Link Setup settings tabbed page.

Step 14: Click on the Remote Terminal check box with the mouse.

Step 15: Select the name of the site containing the DXR 200 radio you wish to connect tofrom the Site Name drop-down list box.

Step 16: Select the name of the DXR 200 terminal you wish to connect to from the TerminalName drop-down list box.


Step 18: Right-click your mouse button on the DXR 200 terminal icon in the Explorer Treepane and choose Go to Remote Link to check the result.

!��$%344��)�!

A DXR 200 terminal can be assigned to a SMA in a variety of ways as illustrated in Figures65-67 in this appendix.

A direct connection to the SMA can be made via the Port and EOW screen. An indirectconnection to the SMA can be made via the Terminal Management screen. Alternatively, theDXR 200 terminal can be connected to a site and then later connected to the SMA via the Portand EOW settings page.

Setting up the Radio Link PortsThe Port and EOW screen in the Commissioning Workspace enables you to connect DXRradios to a SMA. Connections can be direct or indirect. If you use the Port and EOW screen tocreate a connection between a SMA and a DXR 200, you must select the SMA in the ExplorerTree pane first. Alternatively, if you use the Management Setup page to establish aconnection between a DXR 200 and a SMA, you must select the DXR 200 icon in theExplorer Tree pane.

Note: To do so, a direct connection between a DXR 200 and a SMA must already exist in thenetwork.

Direct ConnectionsYou must assign one DXR 200 to a SMA directly before you can assign further DXR 200s.See Figure 65 for an example of direct connection.

In the Port and EOW screen you tell the SMA which port it has a DXR 200 plugged into. Thescreen contains four list boxes, designated Port A to Port D respectively, one for each for eachof the four possible DXR 200 and DXR 700 radio links the SMA can support. The list boxescontain the name of the local terminal connected to this port on the SMA.

See "Port and EOW Settings" in Section 2 of this manual for a full explanation of the fields inthis screen.

Note: You cannot perform Terminal Management until you connect a SMA to a DXRradio via the Port and EOW page.




Procedure - Direct ConnectionA direct connection is a deployment of a DXR 200 plugged directly into the port of a SMA.All SMAs must be connected at the same site (See Figure 65 for an example of directconnection deployment).


Step 2: Select the SMA icon in the Explorer Tree pane.

Step 3: Select the Port and EOW settings tabbed page.

Figure 72: Port and EOW Settings Page - DXR 200Step 5: In the Port section associated with the connectors you are to configure, click on the

Local Terminal field and select the name of the terminal the port is connected to.

Step 6: After you have finished making your changes, select the Commit button in theToolbar. The changes you have made will be reflected in the Network blueprint.

Note: If you deploy a DXR 200 under a SMA (as opposed to at a site and then adding theDXR 200 to the SMA) the SMA will assume the first port as displayed in theTerminal Management page.




� �� )��

Indirect ConnectionsAn indirect connection is a deployment of a SMA communicating to a DXR 200 via anotherDXR 200. The Terminal Management screen enables you to add indirect DXR 200 terminals(already in the blueprint) to this list, as required. Figure 66. provides an illustration of anindirect connection.

Figure 73: Terminal Management Page - DXR 200

Procedure - Indirect ConnectionThe Add button in the Terminal Management tabbed page enables you to quickly associateDXR 200 terminals with their managing SMA.

Step 1: In the Explorer Tree pane select the managing SMA.

Step 2: Select the Configuration Workspace

Step 3: Select the Terminal Management settings tabbed page.

Step 4: Click the Add/Remove button.




Step 4: Select a group of terminals in the Unmanaged Terminals section of the dialog boxand choose OK to associate them with the desired V.24 Port of the SMA.

Procedure - View Managed terminalsThe Terminal Management tabbed page lists all terminals managed by the SMA by direct orremote connection. It also lists all the terminal numbers for the DXR 200s managed by theSMA.

Step 1: In the Explorer Tree pane select the SMA whose managed terminals you wish toview.

Step 2: Select the Configuration Workspace

Step 3: Select the Terminal Management settings tabbed page.

��#��-�� $%344The Commisioning Workspace displays the Terminal Details screen for a selected DXR 200terminal. Refer to "Terminal Details for DXR 200" in Section 2 of this manual.

��#��-�� )�!The Commissioning Workspace displays the SMA Details screen for a selected SMA. Referto "SMA Details" in Section 2 of this manual.

The SMA Details Screen also enables Report Printing. Refer to "Producing Reports in Section4 of this manual.

�� #��-�� $%344You can use the Maintenance Workspace to monitor the alarm data and terminal details ofany DXR 200 inside a DXR NETwork. This section discusses the alarms and report details forDXR 200 via the Maintenance Workspace.




B� *�$%344!��

The alarm settings tabbed page allows you to view the DXR 200 alarm status. The SMAconstantly polls the DXR 200 for its alarm structure and lists all standard DXR 200 alarms.DXR NET will only display the currently active alarms for a DXR 200 network element.Alarms are presented in a flat structure on the DXR 200 alarms screen. The flat structureshows the alarms for the selected terminal. DXR NET only displays alarms that are appropriatefor the terminal type and slot configuration of the DXR 200.

The refresh cycle period on each V.24 port depends on the number of DXR 200 terminals onthat port and on the round-trip to these terminals.

DXR NET will only display the current active alarms for a DXR 200 network element.

Refer to Appendix B in this manual for full details of DXR 200 alarms and descriptions.

Figure 74: Alarms Page - DXR 200

Procedure - View DXR 200 Alarms


Step 2: In the Explorer Tree pane select the DXR 200 terminal whose alarm state you wishto view.


Step 4: Select the name of the active alarm whose details you wish to view. The alarm nameand a description of the most likely causes will be displayed in the right hand-pane.




Step 5: Take the required action to correct the active alarm, i.e. clear the alarm conditionyourself or, if this is not possible, alert the appropriate network personnel.

B� *�$%344� ��

The Terminal Details screen allows you to monitor configuration data for the DXR 200. Theterminal details settings tabbed page is divided into three sections.


• Hardware

• Software

The General Information section is self-explanatory.

The Hardware section displays details for the selected DXR 200 terminal, including thephysical positioning of modules, the serial number of each module and the HSC(hardware/software compatibility number) for each module.

The Software section lists the software loaded into each module in the selected DXR 200terminal.

Figure 75: Terminal Details Page - DXR 200




Procedure - View DXR 200 Terminal Details


Step 2: In the Explorer Tree pane select the DXR 200 icon whose terminal details you wishto view.

Step 3: Select the Terminal Details page.

��$%344�� "% ��

You can produce Inventory Reports for all DXR NETwork elements. To produce a report forthe DXR 200 network element selected in the Explorer Tree Pane, click on the InventoryReport button in the Terminal Details page.

Figure 76: Inventory Report Page - DXR 200

You can save the terminal details report in Word format by clicking on the Save Reportbutton. This document can then be printed out and used to provide a list of details whencommissioning a system.




�� #��-�� )�!

You can use the Maintenance Workspace to diagnose any faults in a SMA in a DXR 200network. The monitoring and diagnostic functions available include:

• Alarms

• SMA Details

• File System

B� *)�!!��

DXR NET polls the SMA to locate the alarms that are active according to the SMA.

Figure 77: Alarms Page - SMA

The 200 Series Network A, B, C and D shows if there is a communication problem with theDXR 200 on that port.


• Alarm Name


• Alarm Type

• Alarm Severity





For Alarm Type field entries, see Section 2 of this manual.

Procedure - View Alarm Conditions for a SMA


Step 2: Select the SMA network element whose alarm conditions you wish to view.


Step 4: If the icon in the Alarm Status and Related Information pane is red, click on the iconto move down the hierarchical alarm levels until the alarm is reached. The alarmname and description of the most likely causes will be displayed in the right handpanes.

Step 5: When you have identified an active alarm, take the required action to correct it. i.e.clear the alarm condition yourself, or, if this is not possible, alert the appropriatenetwork personnel.

Step 6: Use the Alarm Status and Related Information pane to detect when an alarm ispresent on a unit, and then to track the alarm to a particular component.

)�!� ��

DXRNET provides the ability to view the hardware and software details of network elements.Refer to "SMA Details" in Section 2 of this manual for a description of the fields and buttonsin the SMA details tabbed page.

�� )"��

The File System page is used to view and, if necessary, delete BIN files stored on the SMA.These files are used when loading software to the elements under the control of the SMA, andshould be removed when loading new software.

Appendix H: Using DXR NET with Different Data Rates



!�� /2�,��$%&'�*��

��%��

�� *DXR NET communications have a standard data rate of 38k4 bps, but it is possible to carrythem out over channels that have a lower capacity. This section describes three methods ofdoing this.

AFFECTS ON PERFORMANCE. Using a lower port speed can affect performance, andthe size of the network you can monitor.

Note: This section does not contain full details of any required DXR NET functions andoperations already covered in the DXR NET IOM, or in the IOMs for theDXR NETwork elements.

+ � ��You can select the type of connection that DXR NET uses from the following three types:

• Terminal Connection – you use this when you want to connect your PC to a DXR 100(without NMS board) or a DXR 700

• NMS Connection – you use this when you want to connect your PC to a DXR 100 (withNMS board) or a SMA

• Ethernet Connection – you use this when you want to connect your PC to a SMA via aLAN

With all three types of connection, your PC port will use a standard data rate of 38k4 bps tocommunicate with the network. This corresponds to the rate used by the ports on the networkelements. You can therefore connect to a network element without having to worry about thedata rate, providing the actual channel you use has the capacity to support a rate 38k4 bps.

You can ensure this for terminal connections, and NMS connections where your PC is directlyconnected to a network element, by using the cables supplied for this purpose by DMCStratex Networks. These are designed to support the standard 38k4 bps data rate.

Data Rate = 38k4 bps PC

Direct Connection

DXR Network




Figure 78: DXR NET Direct Connection to Network

However, this will not necessarily be the case for connections where your PC is not directlyconnected to the element, i.e. NMS connections made via the PSTN, or Ethernet connections.In either of these cases, the connection data rate will be limited to the maximum capacity ofthe channel, or in the case of connections made via more than one channel, the maximumcapacity of the slowest channel.

DXR NET Connection

Data Rate = 38k4 bps

PC

DXR Network

Element Connection

Data Rate = 38k4 bps

Channel Connection

Data Rate = ?

Figure 79: DXR NET Connection to Network via Channel

For optimum performance, you should try to ensure that the maximum capacity of anychannel DXR NET uses to communicate with a DXR NETwork is no less than 38k4 bps.However, if this is not possible, you can use a lower capacity channel to carry DXR NET

information. There are three ways of achieving this:

• Set up a NMS In/Out connection between two SMA that runs at the channel data rate.

• Use data rate converters at either end channel.

• Connect your PC to a data rate converter on the channel, then connect DXR NET to thenetwork via Ethernet.

) ��&�)��6�� Although you cannot alter the data rate at which your PC port and the ports on the networkelements communicate, you can alter the rates of the NMS In and NMS Out ports on a SMA.You can therefore use two SMA to communicate DXR NET communication over a low-capacity channel by setting the data rate of these ports to less than the maximum capacity ofthe channel, then connecting the ports via the channel.

Note 1: The SMA software needs to be SSC 3 or higher.

Note 2: If you change a SSC3 SMA to an SSC2 SMA in your blueprint, then you will onlybe able to use the standard 38,400 bps baud rate.

SMA PC

DXR Network

NMS Connection (selectable Baud rate)

SMA or NMS Board

Low Capacity Channel

Data rate 38k4 bps

Figure 80: DXR NET Connection to Network via SMA NMS Connection




You can select baud rates of 2,400, 4,800, 9,600, 19,200, 38,400 or 57,600 bps.

Procedure

CHANGING BAUD RATES. If you make changes to the baud rate of a port that is alreadyin use, you can cause a loss of communication, requiring manual intervention at the remoteport to re-establish the link. We therefore advise you take great care when making anychanges to the baud rate of an existing link.

Note: This procedure assumes that you know how to configure SMAs using DXR NET.

Step 1: Obtain the maximum data rate of the channel, or the channel with the lowestcapacity in the circuit used to connect to the DXR NETwork.

Step 2: Select the Port/EOW page in the Configuration Workspace for one of the SMA.

Step 3: Select the port(s) you are going to use (NMS In Connected or NMS Out Connected)by clicking the related check box.

Step 4: For each selected port, select the Site and NMS Unit that the ports are to beconnected to from the related list boxes. This should automatically configure theports at the other end of the link in the blueprint.

Step 5: Set the rates for the selected port(s) in the Baud Rates section. If you are changingthe data rate of a port already in use, DXR NET will warn you, and allow you toAbort, Continue (make the change), or change the port baud rate to match the rate atthe other end of the link.

Step 6: For a new link, repeat Steps 2 to 5 at the SMA at the other end of the link.

Step 7: If required, connect the ports on the SMAs via the link.

You should now be able to communicate with the DXR NETwork by connecting your PC tothe Setup port of the SMA at your end of the link.

,��%�� You can use two Data Rate Converters at each end of a low-capacity channel to allow thechannel to carry communications between DXR NET and the DXR NETwork. The convertorstake in the 38k4 bps streams from the PC and the network, convert them to streams of a ratethe channel can carry, and then convert the rate of streams received over the channel back to38k4 bps.

Data Rate 38k4 bps

Data Rate 38k4 bps

Data Rate Converter

Data Rate Converter

PC

DXR Network

Low CapacityChannel

SMA or NMS Board

Figure 81: DXR NET Connection to Network using Data Rate Converters




You should refer to the manufacturer’s instructions on how to set up the converters to use thechannel.

,��#��*��5,�& �*��-��*��%�� You can connect the PC running DXR NET directly to a low speed channel, provided there is aData Rate Converter between the other end of the channel and the network. In this case, youmust connect the Ethernet port on your PC to the channel, use Dial-Up Networking to connectyour PC to the converter outside the DXR NET application, then start up DXR NET using theEthernet connection. DXR NET will use the “socket” already set up for the first connection,and you will be able to access the converter, and therefore the network, over the channel.

Data Rate 38k4 bps

Data Rate Converter

PC

DXR Network

Low Capacity Channel

SMA or NMS Board

Figure 82: DXR NET Connection to Network using Dial-Up Networking

Procedure

Step 1: Connect the V.24 port of your PC to the channel.

Step 2: Go to the Windows Dial-Up Networking, select the modem connection thatDXR NET normally uses, and use this to connect to the converter.

Step 3: Start up DXR NET, and select the Ethernet type of connection. DXR NET will nowuse the connection set up in Step 2, and you will therefore be able to access thenetwork via the low capacity channel.

Appendix I: DXR SOFTWARE SETS



!�� /��$%)��*�� ) ��

DXR software is released in sets. Each new release of any of the software in a set causes anew set to be released. This allows some software to be in many sets, but each set contains adifferent collection of DXR software.

Software for DXR 700 and SMA software is contained in different sets than DXR 100 andDXR 100 NMS software. Some components of these two product families are common.

Before July 2000, the set numbers were re-used, so set numbers before this data do notuniquely identify a collection of software.

Note: Details of the software sets for the latest release are supplied on the CD.

) �:4Release PendingDate 8 Feb 2001DXR NET 2.4c.2700 PMA 2.0c700 RMA 2.0c700 ODU 2.0cSMA 1.5aDXRloader 1.2a

) �3;Release Set 29Date 8 Feb 2001DXR NET 2.4c.2700 PMA 1.4f700 RMA 1.4f700 ODU 1.4fSMA 1.5aDXRloader 1.2a

Appendix I: DXR Software Sets



) �3ARelease Set 24Date 1 Nov 2000DXR NET 2.3k700 PMA 1.4f700 RMA 1.4f700 ODU 1.4fSMA 1.1bDXRloader 1.2a

) �3 Limited Release Set 21Date 25 Sep 2000DXR NET 2.3k700 PMA 1.3k700 RMA 1.3k700 ODU 1.3kSMA 1.1bDXR Loader 1.2a

445) � >Release 100-Set 18DateDXRTech 6.7dPR-Base 6.7dTrans.NMS 1.0g

445) � 7Release 100-Set 17DateDXRTech 6.7dNPR-Base 6.7dTrans.NMS 1.0g

445) � <Release 100-Set 15Date 14-Aug-00DXR NET 2.3k100 NMS 2.1b100PR 2.0bDXR Loader 1.0h

Appendix I: DXR SOFTWARE SETS



445) � ARelease 100-Set 14Date 14-Aug-00DXR NET 2.3k100 NMS 2.1b100NPR 2.0cDXR Loader 1.0h

) � 3

Release Set 12Date 9 Aug 2000DXR NET 2.3k700 PMA 1.3h700 RMA 1.3h700 ODU 1.3hSMA 1.1bDXR Loader 1.2a

445) � Release 100-Set 11DateDXR NET 2.2d100 NMS 1.3d100PR 1.3d

445) � 4Release 100-Set 10DateDXR NET 2.2d100 NMS 1.3d100 NPR 1.3d

) �CRelease Set 6Date 3-Aug-00DXR NET 2.2d700 PMA 1.3h700 RMA 1.3h700 ODU 1.3hSMA 1.0d

Appendix I: DXR Software Sets



) �<Limited Release Set 5Date 19-Jul-00DXR NET 2.2d700 PMA 1.3g700 RMA 1.3g700 ODU 1.3gSMA 1.0d

) �ALimited Release Set 4Date 12-Apr-00DXR NET 2.2d700 PMA 1.3d700 RMA 1.3d700 ODU 1.3dSMA 1.0d

) �3Release Set 2Date 1-Feb-00DXR NET 2.0c700 PMA 1.2e700 RMA 1.2e700 ODU 1.3dSMA 1.0d

A

ppen

dix

J: D

XR

NE

T S

oftw

are

Com

patib

ility

Tab

le

254

300D

XR

NE

T02

01A

5

2001

DM

C S

trat

ex N

etw

orks

��

��

��

DX

R70

0S

MA

DX

R10

0N

MS

Bo

ard

1.1b

1.1c

1.2e

1.3d

1.3g

1.3h

1.4f

0.9x

0.91

1.0d

1.1b

0.6b

2.0a

2.0b

2.0c

1.9l

1.9m

2.0a

2.0b

2.1b

1.9g

√√

√√

√√

2.0a

√√

√√

√√

√√

√

2.0b

√√

√√

√√

√√

√√

2.0c

√√

√√

√√

√√

√√

√

2.1h

√√

√√

√√

√√

√√

√√

√√

2.2b

√√

√√

√√

√√

√√

√√

√√

2.2c

??

?√

√√

√√

√√

√√

√√

√√

√

2.2d

??

√√

√√

√√

√√

√√

√√

√√

√

2.3k

??

?√

√√

√√

√√

√√

√√

√√

√√

√√

2.4c

??

?√

√√

√√

√√

√√

√√

√√

√√

√√

Appendix K: Abbreviations



��

AGC Automatic Gain Control

ANSI American National Standards Institute

AUI TBD

BER Bit Error Rate

bps Bits per second

CEPT TBD

dB Decibels

dBm Decibels given relative to RF power

DB15 15 pin connector type

DQPSKDifferential Quadrature Phase Shift Keying

DS1 Digital Signal Level 1 (NADH line interface type)

DS3 Digital Signal Level 3 (NADH line interface type)

DXR DMC Stratex Network's Digital Cross-Connect Radio Product

EOW Engineering Order Wire

FEC Forward Error Correction

ft feet

GHz Gigahertz

IF Intermediate Frequency

kbs Kilobits per second

LAN Local Area Network

LED Light Emitting Diode

Mbs Megabits per second

NADH North American Digital Hierarchy

ODU Outdoor Unit

PC Personal Computer

PCM Pulse Code Modulation

PMA Protection Multiplex Adaptor

PSTN Public Switched Telephone Network

QAM Quadrature Amplitude Modulation

Appendix K: Abbreviations



RAM Random Access Memory

RF Radio Frequency

RMA Radio Modem Adaptor

RX Receiver

SNMP Simple Network Management Protocol

STM-0 TBD

TTFP TBD

TX Transmitter

V.24 Serial data communications interface (Also called RS-232)

Index



��

A

Action Table, 41Advanced IP Table, 221AGC Alarm Limits, 136AGC Graph, 156Alarm Board

Mk I, 42Mk II, 42

Alarm Inputs for DXR 100, 146Alarm IO, 39Alarm Outputs for DXR 100, 146Alarms

Commissioning PageAlarm Information, 56View Alarms Button, 56

External on SMA, 134Forward and Reverse Power, 135SDM Board, 212Viewing Alarm Status, 147Viewing Alarms, 165

Alarms, Table of, 165Assign a DXR 200 to a SMA, 237AUX Ports, 132

B

Baud Rates, 24Blueprint, 12

C

Checking for Alarms, 147Clock Source, 133Clock Sources, 26Clocking Hierarchy, 210COMMISSIONING REPORTS, 161Commissioning Workspace, 2, 14, 20, 54, 211,

212Toolbar, 19Uses, 54

Commissioning Workspace for DXR 200, 240Commissioning Workspace for SMA, 240Commit Configuration, 18Compatability Problems

Alarm Boards, 160Complex Models, 229CONFIGURATION DATA, 13

Configuration Workspace, 2, 13, 21, 212, 213,214, 215, 216General Setup Page

Site Name Field, 60Terminal Name Field, 60

Interface Setup Page, 60Page Variation, 21Tabbed Pages, 21Toolbar, 19Working Offline, 21

CONNECTION PROTOCOL

DXR 100 WITH NMS, 8DXR 100 WITHOUT NMS, 8DXR 700, 9

Connection Protocol for DXR 100 with a NMSBoard, 8

Connection Protocol for DXR 100 without a NMSBoard, 8

Connection Protocol for DXR 200, 227Connection Protocol for DXR 700, 9Connection Protocol for SMA, 9CONNECTION PROTOCOLS, 7CONNECTION TYPE SELECTION, 8Connections to a DXR 200, 10Constellation, 74Constellation Diagram, 154, 203constellation monitoring

24 hour, 74Contacting Digital Microwave Corporation, 164Correctable Bytes per Second, 44Correctable Bytes per Second Calculation, 206Correctable Bytes per Second Threshold, 137Cross-connects, 210customer support

details, 159Customer Support, 164CUSTOMIZATION

LANGUAGESUPPORT, 3

D

DB15, 42Define Terminal Numbers, 228DELETING OLD SOFTWARE FILES, 158Deploy the DXR 200, 236Deploying the DXR 200 Network, 231Direct Connections, 237DS1 Line Interface Parameters, 143

Index



DS3 Line Interface Parameters, 144Duplexor frequencies, 63DXR 100, 77, 79

AGC Page, 55, 76Alarm Inputs and Outputs, 39Correctable Bytes per Second, 45Daughter Board Information, 61DXR 100 with NMS

Adding to Blueprint, 100DXR 100 without NMS

Adding to Blueprint, 100DXR 100 without NMS Board

Terminal Connection, 118Equalizer Graph Page, 78Interface Capacities, 30Non-protected Alarms

Hardware, 167Maintenance, 168Modem, 170Radio Link, 170Software, 168Traffic, 169

Pedigree Information, 60PRA A Section, 61PRA Alarms

Hardware, 175Maintenance, 176Modem, 177Radio Link, 178Software, 176

PRA B Section, 62PSW Alarms

Hardware, 172Maintenance, 173Radio Link, 174Software, 173Traffic, 174TX Switch, 174

PSW Section, 61Receive Path, 46

DXR 200 Alarms, 196, 241DXR 200 Hardware Alarms, 196DXR 200 Maintenance Alarms, 198DXR 200 Modem Alarms, 200DXR 200 Network Addressing Requirements,

228DXR 200 Network Blueprint, 229DXR 200 Radio Link Alarms, 201DXR 200 Software Alarms, 197DXR 200 Traffic Alarms, 198DXR 700, 32

ConfiguringFrom Configuration Sheets, 125From Master Blueprint, 124

Correctable Bytes per Second, 45Modem Paramaters, 39Not under SMA Control

Adding to Blueprint, 100ODU A Information, 63ODU B Information, 64ODU Information Section, 62ODU Unit Alarms, 186

Hardware, 186Maintenance, 188Radio Link, 188Software, 187

PMA Information Section, 62PMA Unit Alarm, 183PMA Unit Alarms

Hardware, 183Maintenance, 184Radio Link, 185Software, 184Traffic, 184TX Switch, 185

Receive Path, 46RMA A Information, 63RMA B Information, 63RMA Section Information, 62RMA Unit Alarms, 180

Hardware, 180Maintenance, 182Modem, 182Software, 181

RSSI Page, 55, 81Terminal Connection, 118Under SMA Control

Adding to Blueprint, 101DXR NET, 77, 79, 84, 104, 105

ADVANCED OPTION

SELECTIONS, 75, 81ADVANCED OPTIONS, 154, 155AGC PAGE

MONITOR ALL/RESET ALL BUTTONS, 78ALARMS, 165CONNECTING TO THE RADIO NETWORK

WITH BLUEPRINT, 121WITHOUT A BLUEPRINT, 121

CONNECTION PROTOCOL

SMA, 9Connection Type

Selecting, 120CONNECTION TYPE RESTRICTIONS, 120CONSTELLATION PAGE

MONITOR ALL/RESET ALL BUTTONS, 75, 76CREATING BLUEPRINT

NMS NETWORK, 109DESCRIPTION, 1, 2EQUALIZER GRAPH PAGE

MONITOR ALL/RESET ALL BUTTONS, 80INSTALLATION

WINDOWS 95REMOVING EARLIER VERSIONS, 86

DIAL-UP NETWORKING

Index



WINDOWS 98, 93WINDOWS 95, 85

DIAL-UP NETWORKING, 88INSTALLING DMC DXR DRIVER UTILITY, 89INSTALLING DXRNET, 88INSTALLING WINSOCK2, 90STARTING WINDOWS® DIAL-UP

NETWORKING, 89WINDOWS 98

REMOVING EARLIER VERSIONS, 91, 95WINDOWS 98, 90

FROM CD, 93, 96WINDOWS NT, 95

Configuring Dial-up Networking, 98INSTALLING RAS, 98

INSTALLATION REQUIREMENTS, 84HARDWARE, 84

NMT, 85NMT, 84

REMOTE TERMINAL, 38RSSI PAGE

MONITOR ALL/RESET ALL BUTTONS, 82TOOL LEVEL, 1UNABLE TO COMMUNICATE, 56WARNING MESSAGE, 54WARNING MESSAGES, 163

DXR NET GUI, 3DXR NETwork, 100

Element Configuration, 21Network Blueprint, 100Network Element, 54Network Element Alarms, 58NMS Element

IP Addressing, 105

E

E1 Line Interface Parameters, 141E3 Line Interface Parameters, 142Element Manager, 1EM, 1E-mailing blueprints, 117EOW, 25

SMA, 133EOW Interface, 133EOW Ring Tones, 25Equalizer Graph, 156ERROR MESSAGES, 20Ethernet, 8, 9, 120

Description, 120Ethernet Interface, 226Ethernet, Connection Requirements, 217Event

Mapping an Event to an Action, 138Removing an Event from an Action, 140

Explorer Tree Pane, 20External Alarms on a SMA, 134External I/O - SMA, 42

F

Factory set duplexer freqency, 63Frequency Diversity, 35Frequency Range, 207Frequency Step Size, 207

G

General Setup, 232GUI

Explorer Window, 12GUI, 2, 15

H

Hardware Supported, 6HELP MENU

ABOUT DXR NET, 19High Speed Daughter Board, 214Hot Standby, 35

I

IDU, 33Indirect Connections, 239INSTALLING SYSTEM SOFTWARE, 157Interface Setup, 28INVENTORY REPORTS, 162IRU, 34

L

LAN, 218Line Interface Type, 140LOADING SOFTWARE TO NETWORK ELEMENTS, 157,

158Loopbacks

Checking terminals, 152FEC disable, 153

Checking test equipment and terminalconnection, 151

Checking the link, 151RF/Modem Loopbacks, 149Tributary Loopbacks, 148Types of, 148

Low Speed Daughter Board, 213

M

Maintenance Workspace, 2, 14, 21, 73, 212Advanced Options, 18Tabbed Pages, 73Toolbar, 19

Maintenance Workspace for DXR 200, 240Maintenance Workspace for SMA, 244MANAGEMENT DOMAIN:, 7Management Setup, 233MANAGING NETWORK ELEMENTS, 13Mask IP Address, 28

Index



Menu Bar, 16Modem Parameters, 39Modem/RF Link Setup, 32modulation, 37Monitored Hotstandby, 36Mouse Overs, 20

N

Network BlueprintsCreating, Saving and Retrieving, 15

Network ElementsAdding to Blueprint, 100

Network Maintenance Tool, 1Software Requirements, 84

Network Management Solution, 4NMS, 4

Network IP Addressing Requirements, 105NMS Board

BIN Files, 83General Information Section, 67

Element Name Field, 67Element Type Field, 67

NMS ConnectionDial-up Networking

Windows 98, 93Windows NT, 98

DirectWindows 98, 94, 97

DXR 100 with NMS Board, 119, 120SMA, 119

Direct Connection, 119Modem Connection, 119

Windows 95Installing TCP/IP, 87

Windows 98Installing TCP/IP, 92, 96

NMS Details Page, 67NMS Element

Mask IP Address, 106Ports, 107

NMS elementsIP Addressing, 105Routing Table, 105

NMS ElementsIP Address Range, 107Subnets, 108

Design Guidelines, 108NMS network

Creating a Blueprint, 105NMS Unit Communication, 27

Destination IP Address, 27Interface, 28Mask IP Address, 28

Windows 95NMS Connection

Dial-up Networking, 88

Direct, 89NMS board

Default String, 67NMS Board Alarm, 179

Hardware, 179Maintenance, 179Radio Communication, 180Software, 179

NMS ConnectionDirect

Windows 98, 94, 97Windows 98, 93Windows NT, 98

Windows 95NMS Connection, 88

Direct, 89NMS Connection, 8, 9

Description, 120NMS unit

ConfigurationFrom Master Blueprint, 127

Setting the IP Address, 129NMT, 1, 100

Hardware Requirements, 85Software Requirements, 84

O

ODU, 33Option Pages, 46Output Power, 207

P

PCM Coding Law, 25Port and EOW Settings, 24Port speed, 246Preferred A, 36Preferred Transmitter, 37Procedure - Direct Connection, 238Protected & Diversity Options, 33Protected and Non-protected

configurations, 33Protection Options, 34Protection Switching Testing, 153

R

R9109, [5], 196, 197, 198, 200, 201R9309, [5], 196, 197, 198, 200, 201R9409, [5], 196, 197, 198, 200, 201R9509, [5], 196, 197, 198, 200, 201Radio Settings, 36Real Time Clock, 130RELATIONSHIP TO DXR SOFTWARE PRODUCT

SUITE:, 7Remote Terminal, 38Reports, 161

Index



RF Link Setup, 234RF Modulation for DXR 700, Setting, 137Ring Modes, 25Route add, 225Route to the SMA, (Ethernet), 225Router, 226Routing Table, 27

Setting up, 131RSSI Alarm on DXR 700, 136RSSI Graph, 154RUNNING SCRIPT FILES, 160

S

SDM. See Serial Data ModuleSDM board, 46

Automatic Cross-connects, 53Clocking hierarchy, 216Configuring, 212Configuring a Co-directional Daughter Board,

215Configuring a High Speed Daughter Board, 214Configuring a Low Speed Daughter Board, 213Cross-connections, 52Description, 209High Speed Daughter Board, 50Low Speed Daughter Board, 48Manual Cross-connects, 53, 216

Serial Data Circuit, 212Serial Data Module, 209Services Management Adaptor, 189Sets. See Software,setsSetting Real Time Clock, 130Setting the Terminal Frequencies and Transmitter

Power, 130Setting up the Radio Link Ports, 237Setting up the Routing Table, 131SMA, 9, 216

Adding to Blueprint, 100BIN Files, 83Clocking hierarchy, 210Cross-connects, 210Cross-connects Page, 52Daughter Board, 50EOW, 25Ethernet Connection, 120NMS Connection, 119

DirectWindows 98, 94, 97

Windows 98, 93Windows NT, 98

Option Board Slots, 210Option Page

Co-directional Daughter BoardCross connect to field, 52

High Speed Daughter BoardCross connect to field, 50

Low Speed Daughter Board

Cross connect to field, 48Option Pages, 46SDM Boards, 209SMA Details Page, 68

Name field, 68SDM Board, 211, 212SMA Section, 68

SMA Unit Alarms, 189Alarm Board, 190Hardware, 190Maintenance, 193Radio Communication, 194Software, 192Traffic, 193

Synchronisation, 26Windows 95

NMS Connection, 88Direct, 89

SoftwareDeleting Software from NMS Unit, 158Loading to Element, 158Sets, 250

SOLVING ALARM BOARD COMPATABILITY

PROBLEMS, 160SOLVING SOFTWARE COMPATABILITY PROBLEMS,

159Space Diversity, 35Status Bar, 21STM-0 Line Interface Parameters, 145STORING AND RETREIVING DATA, 15Storing and Retrieving DXR NET Data, 15Supported Interface Types

DXR 100, 29

T

Terminal Connection, 8Description, 120

Terminal Details for DXR 100 and 700, 58Terminal Details for DXR 200, 65Terminal Diversity Option, 138Terminal Frequencies, 130Terminal Number Usage, 228The DXR NET GUI, 15The Network Blueprint Concept, 12Thresholds, 44Title Bar, 16TOOLBAR

CONNECT, 19DISCONNECT, 20

Toolbar, 19TOOLS MENU

CONNECT, 18ERROR MESSAGES, 19

DISCONNECT, 18Topologies of DXR 200-SMA Networks, 10Training courses, 5Transmitter Power, 130

Index



Transmitter Power OutputDXR 100, 37DXR 700, 37

Tx Output Power. See Output Power

U

Using DXR NET to Manage Network Elements, 13

Using the Network Blueprint, 13

W

Wayside Tributary, 28Workspace Pane, 20WORKSPACE SELECTION, 21WORKSPACES, 2

Documents

DXR NET NMT ION-NMS 2-2.5