DXRNETI&O 5.c

&:40'6
+PUVCNNCVKQP1RGTCVKQP/CPWCN

Copyright 1999 Digital Microwave Corporation
All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into
any language or computer language, in any form or by any means, electronic, magnetic, optical, chemical, manual or otherwise, without the
prior written permission of Digital Microwave Corporation.
DISCLAIMER
Digital Microwave Corporation makes no representation or warranties with respect to the contents hereof and specifically disclaims any
implied warranties or merchantability or fitness for any particular purpose. Further, Digital Microwave Corporation reserves the right to
revise this publication and to make changes from time to time in the content hereof without obligation of Digital Microwave Corporation to
notify any person or 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
in its electromagnetic environment without introducing intolerable electromagnetic disturbances.
TRADEMARKS AND REGISTERED TRADEMARKS
The DXR name and logo is a registered Trademark of Digital Microwave Corporation.
Parts of the DXR product design are protected under Patent Cooperation Treaty Application No: PCT/NZ93/00046.
Corporate Headquarters Europe/Africa/Middle East Headquarters Asia Pacific Headquarters

Americas Headquarters Digital Microwave Corporate Digital Microwave Corporate
Broadband Division Headquarters Siskin Drive 10 Ang Mo Kio Street 65
Digital Microwave Corporate Middlemarch Business Park #03-13 Techpoint
170 Rose Orchard Way Coventry CV3 4JA Singapore 569059
San Jose, CA 95134 United Kingdom
USA Tel: +65-484-7780
Tel: +44-1203-863838 Fax: +65-484-7768
Tel: +1-408-943-0777 Fax: +44-1203-530126
Fax: +1-408-944-1801
Narrowband Headquarters Long Haul Division Headquarters

3325 South 116th Street 24 Bridge Street
Seattle, Washington 98168 Lower Hutt
USA New Zealand
Tel: +1 206 439 9121 Tel: +64 4 569 2170

Fax: +1 206 439 2701 Fax: +64 4 5666 1247
Note: The DXR NET Help menu gives full details on how to contact Digital Microwave
Corporation Customer Support personnel, under the Customer Support heading.
6JKUOCPWCNEQXGTU DXR NET V2.0

2TQFWEV&CVG March 2000
2TQFWEV%QFG IOM-NMS-1/05C
Table of Contents
6CDNGQH%QPVGPVU
TABLE OF CONTENTS I
LIST OF FIGURES IV
1 INTRODUCTION 6
About this Manual 6
Welcome to DXR NET 6
Licensing 8
Language Support 8
Digital Microwave Corporation Network Management Solutions 8
What You Will Find In This Manual 8
What You Need To Know 9
2 INTRODUCTION TO DXR NET 10

Overview 10
The DXR NET Management Domain 10
Using DXR NET 13
The DXR NET GUI 15
Configuration Workspace 21
Commissioning Workspace 47
Maintenance Workspace 61
3 INSTALLING DXR NET 70

Introduction 70
Requirements 70
Installing DXR NET on your PC 72
4 USING DXR NET LMT AND NMT 78

General 78
Designing Network Blueprints with the DXR NET LMT and NMT 78
Creating a Network Blueprint for a non-NMS Network 79
Creating a Network Blueprint for a NMS Network 82
Working with a DXR Network 92
Additional DXR NET Functions 99
Problems Using DXR NET 101
5 USING DXR NET ELEMENT MANAGER 103

General 103
Requirements for EM 104
Event Monitoring 105
Workstation Requirements 114
Preparing your PC to use EM 115
DIGITAL MICROWAVE CORPORATION i
MARCH 2000
IOM-NMS-1/05C
Table of Contents
Using the EM with Event Browser Windows 118

Using the EM with Event Notification Functions 123
EM Example 124
6 USING DXR NET WITH DXR 100 129

General 129
About This Section 129
Using DXR NET to configure a DXR 100 131
Setting the Terminal Frequencies and Transmitter RF Power 135
Setting the Forward and Reflected Power Alarm Limits 137
Setting the AGC Alarm Limits 138
Setting the Correctable Bytes per Second Threshold 139
Setting the Terminal Diversity Option 139
Mapping an Event to an Action 140
Removing an Action from an Event 141
Selecting the Terminal Line Interface Type 142
Selecting the Line Interface Parameters for the E1 Interface Type 143
Selecting the Line Interface Parameters for the DS1 Interface Type 143
Setting Up Alarm Inputs 144
Setting Up Alarm Outputs 145
Viewing the Alarm Status 146
Enabling the Tributary Loopbacks 147
Enabling Digital/IF/FEC Loopbacks 148
Testing Protection Switching 149
Viewing the Constellation Diagram 149
Viewing AGC Graph 151
7 USING DXR NET WITH THE NMS BOARD 153

General 153
Using DXR NET to install a DXR 100 with NMS Board 153
Setting the NMS Board Real Time Clock 158
Setting the NMS Board IP Address 159
Setting Up the IP Addresses in the NMS Board Routing Table 161
Viewing the Alarm Status 162
8 USING DXR NET WITH DXR 700 164

General 164
Using DXR NET to install a DXR 700 165
Setting the Terminal Frequencies and Transmitter Power 169
Setting the Terminal Power Alarm Limits 170
Setting the RSSI Alarm Limits 172
Setting the Terminal RF Modulation 172
Setting the Maximum Correctable Bytes per Second Threshold 173
Setting the Terminal Diversity Option 173
Setting the Terminal Line Interface Type 176
Setting E1 Type Line Interface Parameters 177
Setting the E3 Type Line Interface Parameters 179
Setting the DS1 Type Line Interface Parameters 181
Setting the DS3 Type Line Interface Parameters 182
Setting the STM-0 Type Line Interface Parameters 184
Setting the STS-1 Type Line Interface Parameters 185
Viewing the Alarms Page 187
ii DIGITAL MICROWAVE CORPORATION
MARCH 2000
IOM-NMS-1/05C
Table of Contents
Enabling the Tributary Loopbacks 189

Enabling the RF/Modem Loopbacks 190
Testing Protection Switching 190
Viewing the Constellation Diagram 191
Viewing the RSSI Graph 192
9 USING DXR NET WITH THE SERVICES MANAGEMENT ADAPTOR (SMA) 194
General 194
Using DXR NET to install a SMA 195
Setting the SMA Real Time Clock 199
Setting the SMA Board IP Address 199
Configuring the IP Address for the SMA Setup Port 200
Setting Up the IP Addresses in the SMA Board Routing Table 201
Configuring the SMA Radio Link Ports 202
Configuring the EOW Interface 203
Setting up the SMA Clock Source 203
Setting Up External Alarms 206
Viewing Alarms 208
10 USING DXR NET WITH SDM BOARDS 209

General 209
Commissioning Workspace 210
Maintenance Workspace 211
Setting up a Serial Data Circuit with SDM boards 211
APPENDIX A: ALARMS 216

General 216
Non Protected DXR 100 Alarm Descriptions 216
DXR 100 NMS Board Alarm Descriptions 222
DXR 700 RMA Alarm Descriptions 223
DXR 700 PMA Alarm Descriptions 226
DXR 700 ODU Alarm Descriptions 229
SMA Alarm Descriptions 232
APPENDIX B: CONSTELLATION DIAGRAM 236

General 236
APPENDIX C: DATA TABLES 240

General 240
Correctable Bytes per Second Calculation 240
DXR 100 Frequency Relationships 240
DXR 700 Frequency Relationships 241
APPENDIX D: ABBREVIATIONS 242
INDEX 244
DIGITAL MICROWAVE CORPORATION iii

MARCH 2000
IOM-NMS-1/05C
List of Figures
.KUVQH(KIWTGU
Page
FIGURE 1: DXR NET GUI 7
FIGURE 2: CONNECTION TO DXR 100 11
FIGURE 3: CONNECTION TO DXR 100 WITH NMS BOARD 12
FIGURE 4: CONNECTION TO A DXR 700 12
FIGURE 5: SMA NMS CONNECTION 12
FIGURE 6: SMA ETHERNET CONNECTION 12
FIGURE 7: BLUEPRINT SEQUENCE OF USE 13
FIGURE 8: DXR NET GUI 15
FIGURE 9: PORT AND EOW SETTINGS PAGE 23
FIGURE 10: INTERFACE SETUP PAGE DXR 100 WITH DS1 LINE INTERFACE 27
FIGURE 11: MODEM/RF LINK SETUP PAGE UNPROTECTED DXR100 30
FIGURE 12: MODEM/RF LINK SETUP PAGE PROTECTED DXR 100 31
FIGURE 13: ALARM I/O PAGE 34
FIGURE 14: ACTION TABLE PAGE 36
FIGURE 15: EXTERNAL I/O PAGE 37
FIGURE 16: THRESHOLDS PAGE 39
FIGURE 17: OPTION PAGE WITH NO BOARD SELECTED 41
FIGURE 18: OPTION PAGE WITH LOW SPEED DAUGHTER BOARD SELECTED 42
FIGURE 19: OPTION PAGE WITH CO-DIRECTIONAL DAUGHTER BOARD SELECTED 45
FIGURE 20: CROSS CONNECT PAGE WITH GRID SHOWN 46
FIGURE 21: ALARMS PAGE 49
FIGURE 22: SMA DETAILS PAGE 57
FIGURE 23: CONTROLS PAGE 59
FIGURE 24: CONSTELLATION DIAGRAM SINGLE VIEW SELECTED 63
FIGURE 25: AGC GRAPH SINGLE VIEW SELECTED 65
FIGURE 26: RSSI PAGE 67
FIGURE 27: DXR 700 PMA FRONT PANEL LAYOUT - LOCATION OF CONNECTOR V.24 93
FIGURE 28: DXR 100 FRONT PANEL LAYOUT - LOCATION OF CONNECTOR V.24 94
FIGURE 29: SMA FRONT PANEL LAYOUT - LOCATION OF SETUP CONNECTOR 94
FIGURE 30: EVENT MONITORING DROP-DOWN MENU 105
FIGURE 31: NETWORK WIDE ALARM MONITORING CONFIGURATION WINDOW 106
FIGURE 32: EVENT BROWSER WINDOW 107
FIGURE 33: EVENT BROWSER WINDOW ACKNOWLEDGED ALARMS 109
FIGURE 34: DETAILS WINDOW 110
FIGURE 35: SEVERITY FILTER WINDOW 111
FIGURE 36: CLEARED/RAISED FILTER WINDOW 111
FIGURE 37: ACKNOWLEDGE FILTER WINDOW 112
FIGURE 38: DATE AND TIME FILTER WINDOW 112
FIGURE 39: GENERIC FILTER WINDOW 113
FIGURE 40: LABEL BROWSER WINDOW 113
FIGURE 41: POP-UP NOTIFICATION WINDOW 114
FIGURE 42: ALL EVENTS WINDOW 125
FIGURE 43: ACTIVE/UNACKNOWLEDGED WINDOW 126
FIGURE 44: LINK WINDOW 127
FIGURE 45: TIMES WINDOW 128
FIGURE 46: MODEM/RF LINK SETUP PAGE UNPROTECTED DXR100 136
iv DIGITAL MICROWAVE CORPORATION
MARCH 2000
IOM-NMS-1/05C
List of Figures
FIGURE 47: MODEM/RF LINK SETUP PAGE PROTECTED DXR 100 136
FIGURE 50: INTERFACE SETUP PAGE FOR DS1 LINE INTERFACE 142
FIGURE 51: ALARM I/O PAGE 145
FIGURE 54: CONSTELLATION DIAGRAM SINGLE VIEW SELECTED 150
FIGURE 55: AGC GRAPH SINGLE VIEW SELECTED 152
FIGURE 56: SETTING THE REAL TIME CLOCK 159
FIGURE 57: SETTING THE NMS IP ADDRESS 160
FIGURE 58: SETTING THE IP ADDRESSES 161
FIGURE 60: MODEM/RF LINK PAGE 170
FIGURE 63: INTERFACE SETUP PAGE 177
FIGURE 64: INTERFACE SETUP PAGE FOR E1 INTERFACE 178
FIGURE 65: INTERFACE SETUP PAGE FOR E3 INTERFACE 180
FIGURE 66: INTERFACE SETUP PAGE FOR DS1 INTERFACE 182
FIGURE 67: INTERFACE SETUP PAGE FOR DS3 INTERFACE 183
FIGURE 68: INTERFACE SETUP PAGE FOR STM-0 INTERFACE 185
FIGURE 69: INTERFACE SETUP PAGE FOR STS-1 INTERFACE 186
FIGURE 70: COMMISSIONING WORKSPACE 187
FIGURE 73: CONSTELLATION PAGE 191
FIGURE 74: RSSI PAGE 193
FIGURE 75: ROUTING TABLE PAGE 200
FIGURE 76: PORT AND EOW SETTINGS PAGE 202
FIGURE 78: EXTERNAL I/O PAGE 207
FIGURE 80: SDM DATA CIRCUIT BLOCK DIAGRAM 209
FIGURE 81: SDM SMA TO SMA COMMUNICATION BLOCK DIAGRAM 210
FIGURE 82: SDM CROSS-CONNECT SMA BLOCK DIAGRAM 210
FIGURE 83: CONSTELLATION DIAGRAM (DQPSK) 236
FIGURE 84: CONSTELLATION DIAGRAM (16 QAM) 237
FIGURE 85: NOISY CONSTELLATION DIAGRAM (16 QAM) 237
FIGURE 86: CONSTELLATION DIAGRAM (DQPSK) - EXAMPLE 1 238
FIGURE 87: CONSTELLATION DIAGRAM (16 QAM) - SIGNAL DEGRADATION EXAMPLE 2 238
FIGURE 88: CONSTELLATION DIAGRAM (16 QAM) - SIGNAL DEGRADATION EXAMPLE 3 239
DIGITAL MICROWAVE CORPORATION v

MARCH 2000
IOM-NMS-1/05C
Introduction
+PVTQFWEVKQP
#DQWVVJKU/CPWCN
This manual describes how to use the DXR NET product with the following Digital
Microwave Corporation network elements:
DXR 100 digital radio terminals (with and without optional NMS board)
DXR 700 digital radio terminals
Services Management Adaptor (SMA)
Note: DXR NET only works with the DXR radios and associated equipment supplied by
Digital Microwave Corporation.
9GNEQOGVQ&:40'6
9JCVKU&:40'6!
DXR NET is a software package supplied by Digital Microwave Corporation for use with the
DXR product family. You can use DXR NET to configure, commission, and carry out
diagnostics on the individual DXR network elements, and also to monitor the performance of
DXR networks.
After loading DXR NET on your PC, you can connect the PC to the network, and use
DXR NET to manage the radios and other network elements in the network.
DXR NET is offered in three levels:
Local Maintenance Tool (LMT), for use in the configuring, commissioning and
maintenance of individual radio links
Network Maintenance Tool (NMT), for use in the configuring, commissioning and
maintenance of DXR radio networks containing up to 200 network elements
Element Manager (EM), for use in administering DXR radio networks from Network
Operation Centres (NOC)
You interface with DXR NET via the DXR NET GUI.
6JG&:40'6)7+
The DXR NET GUI is divided into a left-hand and a right-hand pane. The Explorer Pane (the
left-hand pane) shows a hierarchical tree view of the network in the Windows Explorer
format. The Workspace (the right-hand pane) displays one of the following:
6 DIGITAL MICROWAVE CORPORATION

MARCH 2000
IOM-NMS-1/05C
Introduction
Configuration Workspace. This is used to view and modify the configuration of the
network elements
Commissioning Workspace. This contains basic fault and performance monitoring
features useful during the network commissioning
Maintenance Workspace. This contains detailed fault and performance monitoring
features used to carry out network diagnostics
The current workspace is selected:
at DXR NET start-up, from the Workspace Selection box

by clicking an icon in the DXR NET toolbar
by clicking the View heading in the DXR NET menu bar, and selecting the workspace
from the drop-down menu
Note: In the Explorer Pane, the icon for the element directly connected to the PC running
DXR NET is shown with a plug to distinguish it from any other shown elements.
Figure 1: DXR NET GUI

In addition to the above, when the EM is enabled, the events it detects are listed in an Event
Browser window. The EM also uses Event Notification windows to draw your attention to
selected events.
DIGITAL MICROWAVE CORPORATION 7

MARCH 2000
IOM-NMS-1/05C
Introduction
.KEGPUKPI
The LMT is supplied at no cost with orders for DXR radios. You can upgrade the LMT to the
NMT with a hardware licence key. An additional software key is then required to upgrade the
NMT to the EM. This key sets the size of the network the EM can monitor, and is also tied to
the hardware key. Both keys can be obtained from your Digital Microwave Corporation agent.
Note 1: The EM network size set in the software key can be altered.
Note 2: New versions of DXR NET will support your current licence keys.
Note 3: New versions of DXR NET are available from your Digital Microwave Corporation
agent, or can be down-loaded from the Digital Microwave Corporation web site.
.CPIWCIG5WRRQTV
Digital Microwave Corporation can supply you with a customised version of DXR NET to
support your language requirements.
Note: This customisation is only available on request from Digital Microwave

Corporation, who will supply a quotation.
&KIKVCN/KETQYCXG%QTRQTCVKQP0GVYQTM/CPCIGOGPV5QNWVKQPU
DXR NET can only be used:
with individual DXR radio links (networks with no SMA, or no DXR 100 equipped with
NMS board)
with SMA, or DXR 100 equipped with NMS board. With the NMT, this allows you to
manage networks whose radios are all DXR radios, and whose total number of radios is
less than 200
If you require a Network Management Solution (NMS), and DXR NET is not suitable due to
network size, or the presence of other radio types on the network, we recommend ProVision
as your NMS solution. ProVision is a Digital Microwave Corporation product to provide
management of all our radios.
9JCV;QW9KNN(KPF+P6JKU/CPWCN
This manual is split-up into the following sections:
About This Manual (this section). This gives an introduction to the manual, including a
brief overview of DXR NET
Introduction to DXR NET. This contains a description of DXR NET Management Domain,
and how you can use DXR NET to manage a radio link
Installation of DXR NET. This tells you all you need to know to install DXR NET on your
PC, and how to get started using it

MARCH 2000
IOM-NMS-1/05C
Introduction
Using DXR NET with the LMT and NMT. This contains a description of how you can use
DXR NET LMT and NMT to design and modify network blueprints, and to configure,
commission and maintain network elements
Using DXR NET Element Manager. This contains a description of how to use the DXR
NET Element Manager to monitor a DXR network
Using DXR NET with DXR 100. This contains a description of how you can use DXR NET
to configure, commission and maintain a DXR 100 terminal
Using DXR NET with NMS board. This contains a description of how you can use DXR
NET to configure, commission and maintain the optional NMS board used with the DXR
100
Using DXR NET with DXR 700. This contains a description of how you can use DXR NET
to configure, commission and maintain a DXR 700 terminal
Using DXR NET with SMA. This contains a description of how you can use DXR NET to
configure, commission and maintain a SMA, and a DXR 700/SMA network
Using DXR NET with SDM boards. This contains a description of how you can use DXR
NET to set up a data service channel using the SDM boards
There are also appendices detailing:
Alarms
Constellation Diagrams
9JCV;QW0GGF6Q-PQY
To obtain the full benefit of DXR NET features, and to use this document, you must be
familiar with the features and terminology of the Microsoft Windows 95 operating system (or
later). This should include installing software from 3.5 floppy disks or CD. You must also be
familiar with the Digital Microwave Corporation equipment you are planning to use DXR NET
with. Ideally, you should have completed any Digital Microwave Corporation training courses
for the equipment, and have access to the training and installation manuals for the equipment
and any other relevant documentation
Note: The Digital Microwave Corporation training courses cover the installation,
configuration, operation and maintenance of DXR products. Please contact your
local Digital Microwave Corporation representative for details.

MARCH 2000
IOM-NMS-1/05C
Introduction to DXR NET
+PVTQFWEVKQPVQ&:40'6
1XGTXKGY
This section covers:
The DXR NET Management Domain (ie, how DXR NET fits in with the other DXR
product software)
Using DXR NET
The DXR NET GUI
6JG&:40'6/CPCIGOGPV&QOCKP
&:45QHVYCTG.C[GTKPI
DXR NET is a component of the DXR Software Product suite. The other components of the
suite comprise:
Terminal Unit Software - the software in the DXR 100 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 of
software the element contains.
%QPPGEVKQP2TQVQEQNU
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 700 terminals
SMA (Services Management Adaptor)
The type of connection you select for DXR NET depends on the network element you are
trying to connect to.
Note: For details on the actual physical connections to the elements, and how these affect
the level of access you have to the DXR network, refer to Section 4.

MARCH 2000
IOM-NMS-1/05C
Selecting the DXR NET Connection

Due to interface differences between Terminal Unit and NMS Unit software, you need to tell
DXR NET the type of unit (terminal or NMS unit) it is going to connect to before DXR NET
can make the connection. You do this by selecting the DXR NET connection type to match the
type of network element.
You can select three types of connection:
Terminal Connection. You select this type of connection when you are connecting to a
terminal (DXR 100 without NMS board, or a DXR 700). Your PC is directly connected to
the terminal, and DXR NET interfaces with the terminal unit software.
NMS Connection. You 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
the NMS unit, or connected to the unit via a modem. In either case, DXR NET interfaces
with the NMS unit software, which also handles any communications required between
DXR NET and any other network elements.
Ethernet. You 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 to the LAN. In either case, DXR NET interfaces with the SMA software, which
also handles any communications required between DXR NET and any other network
elements.
Note 1: DXR NET will not allow you to connect to a terminal if the terminal is part of a
network containing NMS units. Instead, you will have to connect to one of the NMS
units.
Note 2: The DXR NET LMT does not support the Ethernet connection.
Connection Protocol for DXR 100 without a NMS Board

When 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 is
made directly to the V.24 port on the terminal front panel.
PC Running DXR NET Proprietary
DXR NET over V.24
Internal
TCP/IP
DXRproxy DXR 100
Figure 2: Connection to DXR 100
Connection Protocol for DXR 100 with a NMS Board

When 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 a
modem.

MARCH 2000
IOM-NMS-1/05C
PC Running DXR NET TCP/IP over

DXR NET V.24
DXR 100
with NMS
Board
Figure 3: Connection to DXR 100 with NMS Board
Connection Protocol for DXR 700

When the PC running DXR NET is connected to a DXR 700, DXR NET communicates with the
terminal unit software using a proprietary protocol. The connection is made directly to the
V.24 port on the terminal front panel.
PC Running DXR NET Proprietary
DXR NET over V.24
Internal
TCP/IP
DXRproxy DXR 700
Figure 4: Connection to a DXR 700
Connection Protocol for SMA

The PC running DXR NET can connect to a SMA using either the NMS Connection or
Ethernet. When using a NMS Connection, DXR NET communicates with the SMA Unit
Software using SNMP and TFTP. The connection is made via the Setup port on the SMA
front panel, either directly, or via a modem. Direct connections are made over
UDP/IP/PPP/V.24.
DXR NET V.24
SMA
Figure 5: SMA NMS Connection

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

MARCH 2000
IOM-NMS-1/05C
7UKPI&:40'6
6JG0GVYQTM$NWGRTKPV%QPEGRV
The Network Blueprint concept is the heart of the Software Functional Architecture for any
DXR 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 be
modified 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 as
possible. Each blueprint will support one network, displaying the network as a collection of
sites. The sites in turn are represented as a collection of network elements (DXR 100 and 700
terminals, SMAs, or NMS boards). It is this hierarchical view which is displayed in the
Explorer Window of DXR NET GUI.
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
7UKPIVJG0GVYQTM$NWGRTKPV
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 of
the network
all the Field blueprints are sent to the NOC, and used to update the original Design
blueprint, which now becomes the Commissioned blueprint
NOC Site
To On-site
Design Installers Changes
Blueprint
Field
To Blueprint
Commissioned NOC
Blueprint
Figure 7: Blueprint Sequence of Use

MARCH 2000
IOM-NMS-1/05C
7UKPI&:40'6VQ/CPCIG0GVYQTM'NGOGPVU
DXR NET has been developed to assist you in the configuration, installation, commissioning
and maintenance of the DXR series of radios and their associated network management
hardware.
Configuration
Using the DXR NET Configuration Workspace, you can either carry out the configuration of
network elements while connected to the element, or create the configurations in the blueprint
for down-loading to the elements later. You can also read details from existing elements for
modifying, saving and re-writing. The details comprise:
Element details (name, description, type, etc)

Interface setup details
Link setup details
Alarm actions, and
Performance thresholds
Commissioning
Using the DXR NET Commissioning Workspace, you can view all the details required to
correctly 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 and
Manual protection switching for test purposes.
Maintenance
Using the DXR NET Maintenance Workspace, you can carry out troubleshooting and fault
diagnosis on a network. The features provided include numerical readings and graphical
displays of:
Alarms (similar to that provided in the Commissioning Workspace)

Constellation diagrams
Equaliser graphs
RSSI graphs, and
Signal to Noise Ratio (SNR)
As in the Commissioning Workspace, the Maintenance Workspace also includes a control
panel that allows you to carry out Loopbacks and Manual protection switching for test
purposes.

MARCH 2000
IOM-NMS-1/05C
5VQTKPICPF4GVTKGXKPI&:40'6&CVC
In accordance with the concept of the Network Blueprint, it is very important to be able to
store 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
6JG&:40'6)7+
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.

MARCH 2000
IOM-NMS-1/05C
6KVNG$CT
The left-hand side of the title bar lists the name of the active network blueprint (ie. the
blueprint 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 no
active 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.
/GPW$CT
The menu bar contains the following pull-down menus:
File
View
Configuration
Maintenance
Event Manager (only when you have the EM level of DXR NET)
Tools
Help
The availability of a pull-down menu depends on the level of tool you are using, and the
current state 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 pull-down menus can be displayed by
selecting their item with the mouse, or by holding down the <Alt> key and typing the
underlined letter in the menu name in the toolbar.
Note 1: The Configuration and Maintenance menus are only available if you have selected
the corresponding workspace.
Note 2: The Event Manager menu is only available if you are using the DXR NET EM.
File
The 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 network
element configuration file (.cfg)
Export Network Element - allows you to save the configuration file of the currently
selected network element for future reference
Save - allows you to save the active network blueprint, overwriting any previously saved
version
Save As - allows you to save the active network blueprint under a different name, thus
keeping any previously saved version
MARCH 2000
IOM-NMS-1/05C
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 listed
names 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 letter
or 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 after
their listing in the menu bar.
View
The 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 for
display in DXR NET Workspace Area
Configuration Workspace - allows you to select the Configuration Workspace for display
in DXR NET Workspace Area
Maintenance Workspace - allows you to select the Maintenance Workspace for display in
DXR NET Workspace Area
You can select any of the items in the View menu using the mouse, or by typing the
underlined letter in the item listing.
Note: Currently selected items are identified by having a tick at the start of their name.
Configuration
The Configuration menu contains listings for the following functions:
Note: The Configuration menu is only available if you have selected the Configuration
workspace.
Add Network Element - allows you to add network elements to the site currently selected
in the active network blueprint. You select the elements from a dialog box that contains a
list 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 selected
network element in the active network blueprint into the corresponding element of a
connected network
Read Configuration - allows you to download the configuration and settings of the
selected network element in the active network blueprint from the corresponding element
of a connected network
Load Software - available when a SMA or a DXR 100 with a NMS board is selected in
the Explorer Tree pane. Allows you to download the unit software to the SMA or NMS
board, or to units under their control

MARCH 2000
IOM-NMS-1/05C
IP Address Table - empty unless a SMA or NMS board is selected in the Explorer Tree
pane. Contains all the IP addresses that the SMA or NMS board needs to communicate
with other IP devices on the network, also used to set up the SMA or NMS IP address
Software Table - lists the versions of the Terminal and NMS unit software of all the
network elements
Set Real Time Clock - available when a SMA or NMS board is selected in the Explorer
Pane. Used to set the clock used to synchronise operations in the SMA or NMS board
You can select any of the functions listed in the Configuration menu using the mouse, or by
typing the underlined letter in the function listing. The Add Network Element and Add Site
functions can be used while working off-line. The Write Configuration and Read
Configuration functions can only be used when DXR NET is connected to a network.
Note: DXR NET will display an error message if you attempt to read or write a network
element configuration while your PC is not connected to a network.
Maintenance
The Maintenance menu contains listings for the following functions:
You should only use these functions under direct instructions from Digital
Microwave Corporation, or under the supervision of an accredited Digital
Microwave Corporation representative.
Note: The Maintenance menu is only available if you have selected the Maintenance
workspace.
Load Script File - allows you to display the Execute Script File dialog box. This box
enables 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 box
enables you to select either the single or the multi-carrier views for the monitoring
functions in the Maintenance workspace. Single means the baseband signal is monitored,
multi-carrier means the individual signal channels are monitored. See the Maintenance
Workspace descriptions is Sections 6 and 8 for further details
You can select any of the functions listed in the Maintenance menu using the mouse, or by
typing the underlined letter in the function listing, but we advise you only to do so under the
conditions set out in the above warning.
Event Monitoring
The Event Monitoring menu contains listings for the following functions:
Enable Network Event Monitoring - allows you to enable or disable the EM.
Configuration - allows you to select which parts of the network the EM will monitor.
Event Browser - allows you to open Event Browser windows, which you can then use to
view the events detected by the EM
Event Notification allows you to set up the EM to notify you of events while you are
carrying out other tasks on your PC
For further descriptions of the Event Monitoring functions, refer to Section 5.

MARCH 2000
IOM-NMS-1/05C
Tools
The 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 type
of connection you are using
Communications Setup - allows you to select the type connection by which your PC
communicates with any attached network
You can select any of the functions listed in the Tools menu using the mouse, or by typing the
underlined letter in the function listing.
Note: DXR NET displays an error message if you select the Connect function while your
PC is not connected to a network.
Help
The Help menu contains listings for the following functions:
Customer Support - displays a dialog box listing the contact details for the Long Haul
Division of Digital Microwave Corporation
About DXR NET - displays a dialog box listing DXR NET software version the PC is
running, the Product level, and the currently available memory
You can select either of these items using the mouse, or by typing the underlined letter in the
item name.
6QQNDCT
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 current
name (overwriting any previously saved version), or under a different name (keeping any
previously saved version)
Commissioning Workspace - allows you to select the Commissioning Workspace for
display in the workspace area
Configuration Workspace - allows you to select the Configuration Workspace for display
in the workspace area
Maintenance Workspace - allows you to select the Maintenance Workspace for display in
the workspace area
Commit - allows you to commit or save any changes that have been made to the
configuration of the currently selected network element to the active blueprint
Write Configuration - allows you to upload the configuration and settings of the selected
network element in the active blueprint into the corresponding element of the network
your PC is connected to

MARCH 2000
IOM-NMS-1/05C
Read Configuration - allows you to download the configuration and settings of the
selected network element in the active blueprint from the corresponding element of the
network 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 Configuration
or Write Configuration, while your PC is not connected to a network element.
'ZRNQTGT6TGG2CPG
The Explorer Tree pane displays a representation of the active network blueprint in a
hierarchical tree format.
In this hierarchy, networks are made up of collections of sites, which are in turn made up of
collections of network elements, ie. DXR 100s, DXR 700s, or SMAs. The tree view uses the
standard Windows format.
You can use the tree view to add, edit and delete site and network elements, and to assign and
modify the network, site and the network element names. When you use it with the
Workspace Pane, you can view and modify the configuration of a network element, monitor
the 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 under
SMA control displayed under the controlling SMA, and any NMS boards displayed under the
DXR 100s that contain them.
9QTMURCEG2CPG
The Workspace pane displays the currently selected workspace. The workspaces are used to
display, modify and monitor the settings of the network element that is currently selected in
the 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 box displayed when you start-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.

MARCH 2000
IOM-NMS-1/05C
5VCVWU$CT
The Status Bar can be divided into two sections:
text field. This displays information on the current operations of DXR NET, and
descriptions of tools in the GUI
network icon. This indicates both the type and status of the network connection
%QPHKIWTCVKQP9QTMURCEG
You use the Configuration Workspace to manage the configuration data for DXR network
elements. 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 are
contained in the tabbed pages in the workspace area.
Note: The pages displayed in the Configuration Workspace can vary, depending on the
network element selected in the Explorer Tree.
As Configuration Workspace can work with saved data, you can work with it offline, ie, you
can create and modify element configuration data while your PC is not actually connected to a
element.
Note: The Configuration Workspace is the only workspace that can be used offline, as the
pages 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 and DXR 700 terminals)
Modem/RF Link Setup (for DXR 100 and DXR 700 terminals)
Alarm IO (for DXR 100 terminals only)
Action Tables (for DXR 100 terminal, DXR 700 terminal and SMA)
Thresholds (for DXR 100 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)
)GPGTCN5GVWR
The General Setup page is divided into the following sections:
Terminal Details (for DXR 100 and DXR 700 terminals)

Board Details (for NMS boards only)
SMA Details (for SMA only)
MARCH 2000
IOM-NMS-1/05C
Site Information
Terminal Details
The Terminal Details section has two text fields:
Type
Terminal Name
The Type field contains the equipment description of the terminal. It is determined
automatically from the terminal 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 Network
Blueprint. If you not assigned a name to the terminal, the field is contains the default string
Terminal n where n is an integer relating to the number of radios in the network. You can
change the name by selecting the field with the mouse, and typing in the new name.
Board Details
The Board Details section has two text fields:
Type
Board Name
The Type field contains a specific description of the board type, usually DXR 100 NMS
Board. It is read from the NMS, and you cannot change it.
The Board Name field is used to hold the name of assigned to the board. If you have not
assigned a name to the board, the field is contains the default string NMS n where n is an
integer relating to the number of boards in the network. You can change the name by selecting
the field with the mouse, and typing in the new name.
SMA Details
The SMA Details section has two text fields:
Type
SMA Name
The Type field contains a specific description of the board type, usually DXR 100 NMS
Board. It is read from the NMS, and you cannot change it.
The SMA Name field is used to hold the name of assigned to the SMA. If you have not
assigned a name to the board, the field is contains the default string SMA n where n is an
integer relating to the number of boards in the network. You can change the name by selecting
the field with the mouse, and typing in the new name.
Site Information
The Site Information section has three text fields:
Name
Description
Contact Details

MARCH 2000
IOM-NMS-1/05C
The Name field is used to hold the name you assigned to the site in the Network Blueprint. If
you have not assigned a name, the field is assigned the default string Site n where n is an
integer relating to the number of radios in the network.
The Description field is used to hold the any details of the site you feel should be noted. If
you do not 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. 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 network
blueprint. However, you can change the details by selecting the field with the mouse, and
typing in the new details.
Note: You can only change the Description and Contact Details fields when the Site icon
is selected in the Explorer Tree, not the terminal icon.
2QTVCPF'195GVVKPIU
The Port and EOW Settings page is divided into the following sections:
Port Details
Engineering Order Wire (EOW)
Clock Sources
Figure 9: Port and EOW Settings Page

MARCH 2000
IOM-NMS-1/05C
Port Details
There are four sections, designated Port A to Port D respectively, one for each for each of the
four possible DXR 700 radio links the SMA can support. There are two connectors on the
SMA front panel for each link:
the AUX ports (AUX A to AUX D). The SMA uses these to communicate with other
SMAs on the part of the network to which it is connected via the radio link. The actual
physical connection is to the AUX port on the PMA of the local terminal. The SMA
communications are carried by the DXR 700 auxiliary channel.
the V.24 ports (V.24 A to V.24 D). The SMA uses these to control the local DXR 700
terminal of the radio link. The actual physical connection is to the V.24 port on the PMA
of the terminal.
Each port section has two fields:
Local Terminal
Baud Rate
The Local Terminal field contains the name of the local terminal connected to this V.24 port
on the SMA.
The Baud Rate field is used to set the Baud rate, (ie, the signalling rate), over DXR 700
auxiliary channel. This should be 38400 baud.
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 the push-button on the SMA front panel, and are output either via the
EOW handset or the speaker in the SMA. Messages are broadcast by inserting the EOW
handset into the jack on the SMA front panel, and holding down the push-button. They can be
received either via the handset or the SMA internal speaker.
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.
You select the volume from the drop-down menu displayed when you click on the field with
the mouse. You can choose between Normal or Loud.
The PCM Coding field is used to select the coding law used to transmit voice over the EOW
interface. The coding law governs the relationship between the analogue voice signal and the
digital pulses used to transmit the signal over the network. You select the law from the drop-
down menu displayed when you click on the field with the mouse. You can choose between
Law or A-law.

MARCH 2000
IOM-NMS-1/05C
The Ring Modes field is used to set the type of ringing tone generated by the SMA when it
ringing signals over the EOW interface. You select the tone from the drop-down menu
displayed when 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 analogue voice signal from
the EOW handset is passed through a high pass filter or not. You set the option you require by
clicking on the check box field with the mouse. The option is selected when there is a tick in
the check box.
Clock Sources
The Clock Sources section has two fields:
Primary
Secondary
To ensure the synchronisation of its components the SMA is provided with two possible clock
signals, Primary and Secondary. This enables it to switch to the Secondary clock signal if the
Primary fails. Either signal can be generated internally, or input to the SMA via a port on the
front panel.
The Primary and Secondary fields are used to select the source for the associated clock signal.
You select the option you require from the drop-down menu displayed when you click on the
field with 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, ie, 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 be
occupied by an appropriate board.
4QWVKPI6CDNG
The Routing Table fields are contained within a three-column table. The columns are:
Destination IP Address
Mask IP Address
Interface
You use the Routing Table to set-up the IP routes by which the NMS unit communicates with
other IP devices on the network. Each row of the table defines one IP route. You create a new
row by pressing the Insert key. For the NMS unit to communicate with another IP device, you
must set up a valid route in the IP Address table.
Note: Each IP device on the network must have an unique IP address.
Destination IP Address
The Destination IP address is the IP address on the network of the device you wish the NMS
unit to communicate with. You input the required address by double-clicking the next empty
field in the Destination IP address column, and typing in the address.

MARCH 2000
IOM-NMS-1/05C
Mask IP Address
To save you having to define a route for every single IP address, you can use a subnet mask to
route a range of IP addresses to a single destination. A subnet mask allows you to define
which part of the IP address you want to match for routing. The Mask IP address allows you
to set the subnet mask for a range of IP addresses you want the NMS unit to use the same
defined route for. You input the required subnet mask by selecting the next empty field in the
Mask IP address column, and typing in the mask.
Interface
The Interface is the port that the NMS unit will use to send messages to the given IP address.
You select the port from the drop-down list displayed when you double click on the field.
+PVGTHCEG5GVWR
The Interface Setup page is divided into the following sections:
Interface
Tributary
Wayside Tributary (DXR 700 terminal only)
Interface
Depending on the type of line interface you select, the Interface section has either one or two
pull-down menu fields. The fields are:
Interface Type (always present)

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

MARCH 2000
IOM-NMS-1/05C
Figure 10: Interface Setup Page DXR 100 with DS1 Line Interface
SETTING THE INTERFACE TYPE. The terminal interface type is set by the terminal
hardware. You should therefore only select an interface type that matches the terminal
hardware.
The Interface Type pull-down menu allows you to choose the terminal line interface. The
available interface types are shown in the following table.
Note: At present, the DXR 100 only supports E1 and DS1.

MARCH 2000
IOM-NMS-1/05C
+PVGTHCEG6[RG &GUETKRVKQP
' Default setting. Defined as part of the European Digital
Hierarchy. Data rate 2.048 Mbs. Can carry up to thirty voice
channels, with two control and synchronisation channels.
' Supported by DXR 700 only. Defined as part of the

European Digital Hierarchy. Data rate 34.368 Mbs.
Equivalent to 16 E1 circuits.
&5 Defined as part of the NADH. Data rate 1.544 Mbs. Can
carry up to twenty-four voice channels.
&5 Supported by DXR 700 only. Digital Signal Level 3. Defined

as part of the North American Digital Hierarchy (NADH).
Data rate 44.736 Mbs. Can carry up to 672 64 kbs channels,
each channel capable of carrying one analogue telephone
conversation (after analogue-to-digital conversion). T-carrier
equivalent T3.
56/ Supported by DXR 700 only. To be defined.
565 Supported by DXR 700 only. To be defined.
SETTING THE INTERFACE CAPACITY. The terminal interface capacity is set by the
terminal hardware. You should therefore only select an interface capacity that matches the
terminal hardware.
The Interface Capacity pull-down menu is only displayed when you have selected a terminal
line interface that can support more than one signal channel. The following table shows the
supported interface capacities.
Note 1: At present, the DXR 100 only supports 1xE1, 2xE1, 4xE1, 1xDS1, 2xDS1 and
4xDS1.
Note 2: STM-0 and STS-1 do not have selectable interface capacities.
+PVGTHCEG6[RG +PVGTHCEG%CRCEKV[
' Both terminals support 1xE1, 2xE1, and 4xE1. DXR 700 also
supports 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.
Tributary
The Tributary section is only active when you have selected a terminal line interface that can
support more than one channel. The section normally contains a table, and sometimes a list
box for selecting Line Encoding.
MARCH 2000
IOM-NMS-1/05C
The number of columns in the table depends on the Interface Type, and the number of rows
depends on the Interface Capacity. The columns are:
Tributary
Line Impedance (E1 interface type)
Rx Sensitivity (E3, DS3, STM-0 or STS-1 interface type)
Tx Level Boost (DS3, STM-0 or STS-1 interface type)
Line Build-out (DS1 interface type)
Equaliser Bypass (E3, DS3, STM-0 or STS-1 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 the
other table columns. The column entries are Trib n where n is the number of the tributary.
The range of n depending on the capacity selected. The fields are input automatically, and
you will not be able to change them.
SETTING THE LINE IMPEDANCE. The line impedance depends on the cabling attached
to the line interface of the terminal. Therefore, any changes you make to the line impedance
must 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 when
you double click on the field.
SETTING THE LINE BUILD-OUT. The Line Build-out is dependant upon the cabling
attached to the line interface of the terminal. Therefore, any changes you make to the line
impedance in the software must reflect the cabling attached to your terminal line interface.
The Line Build-out column is used to set the length of line from the tributary to the connected
equipment. You select the length from the drop-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. You select one of these sensitivities from the drop-down list
displayed when you double click on the field
The Tx Level Boost column is used to increase the amplitude of signals transmitted from the
line interface. You enable Tx level boost by selecting True (enabled) or False (disabled) in the
column.
The Equaliser Bypass column is used to take the equaliser circuitry on the line interface out of
the signal path. You enable equaliser bypass by selecting the check-box in the column.
Selected check boxes display a tick (default is not ticked)
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). You select these
from the drop-down list displayed when you double click on the field.

MARCH 2000
IOM-NMS-1/05C
Note: The commissioned state of a tributary affects the alarms raised, as traffic on an
uncommissioned tributary is an alarm condition (Uncommissioned Traffic. See
Appendix A, NPR Unit Alarm, Traffic)
The Line Encoding list box is available when the DS1 interface type is selected. It allows you
to select the type of coding used by DS1. You select the coding from the list displayed when
you click on the arrow in the box and selecting from the displayed menu.
Wayside Tributary
The Wayside Tributary section is available with DXR 700 terminals. The Wayside Tributary
is an extra control channel supported for the 16xE1 or 16xDS1 interface capacities, or the E3,
DS3, STM-0 or STS-1 interface types. The section contains either a table you can use to
configure the tributary, or No Wayside Available if you have selected an interface capacity
or type that does not support the tributary.
The table has two columns, both of which correspond to columns in the Tributary section
table. The Wayside column corresponds to the Tributary column, and is followed by either a
Line Impedance column (16xE1, E3, or STM-0), or a Line Build-Out column (16xDS1, DS3,
or STS-1). The functions of these columns is as for the columns described for the main table.
/QFGO4(.KPM5GVWR
The appearance of this page depends on configuration of the terminal. If the terminal is an
unprotected terminal, the Radio Settings sub-section appears at the top of the page. If the
terminal is a protected terminal, the Protected & Diversity Options sub-section appears at the
top of the page, with the Radio sub-section directly underneath it.
Figure 11: Modem/RF Link Setup Page Unprotected DXR100

MARCH 2000
IOM-NMS-1/05C
Figure 12: Modem/RF Link Setup Page Protected DXR 100

The RF Link and Link Parameters section is divided into the following sub-sections:
Protected & Diversity Options (protected terminals only)

Radio Settings/Radio (title dependant upon terminal configuration)
Remote Terminal
Protected & Diversity Options

The Protected & Diversity Options sub-section will only be displayed for protected terminals.
It contains the following fields:
Protected
Space Diversity
Frequency Diversity
SETTING THE TERMINAL DIVERSITY OPTION. The diversity option you can select is
dependent on the terminal hardware, and you must not make any changes that do not reflect
the terminal hardware.
Note 1: If you select either of the Space or Frequency Diversity options, you will have to set
the terminal power and AGC alarm limits for each radio. If you select the Frequency
Diversity option, you will also have to set the frequencies and transmitter power for
each radio.
Note 2: You can only select one of the three configurations at any one time.

MARCH 2000
IOM-NMS-1/05C
You select a configuration option by clicking on the appropriate radio button with the mouse.
If you select the Frequency Diversity, the additional fields are displayed in the following
Radio sub-section for Radio A and Radio B.
Radio Settings
The Radio Settings sub-section contain the following fields:
Tx Frequency (MHz)
Rx Frequency (MHz)
Tx Power (dBm)
SETTING THE TERMINAL FREQUENCIES AND TRANSMITTER RF POWER. The
frequency range and transmitter power of your terminal depends on the duplexer of the
terminal. Therefore, any changes you make to the frequency parameters must reflect the
duplexer tuning, and any changes to the output power must reflect the capacity of the
duplexer.
You can change the values in any of these fields using the up/down arrows. The Tx Power can
be varied in 0.1 dB steps from +10 dBm to the maximum for the terminal. For a DXR 100
terminal, the relationship between the frequency range, the modulation, the capacity, and the
maximum transmitter power output at the Tx port, is shown in the following table.
Modulation
QPSK 16 QAM
1 x E1 2 x E1 4 x E1 1 x E1 2 x E1 4 x E1
DXR 103 330-470 MHz 37 dBm 37 dBm - 31 dBm 31 dBm 33 dBm
DXR 109 890-960 MHz 37 dBm 37 dBm 37 dBm - - 29 dBm
DXR 114 1350-1550 MHz 33/37 dBm 33/37 dBm 37 dBm 33 dBm 33 dBm 33 dBm
DXR 124 2300-2500 MHz 33 dBm - 33 dBm - - -
DXR 126 2500-2700 MHz - - 33 dBm - - -
For a DXR 700 terminal, the relationship between the frequency range, the modulation, the
capacity, and the maximum transmitter power output at the Tx port, is shown in the following
table.
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 10.5-10.7 GHz +28dBm +28dBm +28dBm +28dBm +28dBm +26dBm +26dBm +26dBm
DXR 724 2.3-2.5 GHz +28dBm +28dBm +28dBm +28dBm +28dBm - - 26 dBm
DXR 726 2.5-2.7 GHz +28dBm +28dBm +28dBm +28dBm +28dBm - - +26dBm

MARCH 2000
IOM-NMS-1/05C
Note: If you make any changes to the frequency values, these will be reflected in the
remote terminal settings only after you have committed the changes, and if the
remote terminal is selected in the Remote Terminal field (see below).
Remote Terminal
The Remote Terminal sub-section only becomes active when you select the check box in the
top 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 the
local terminal.
This allows DXR NET to check the Tx/Rx pairs for the link, and to move between the pairs at
either 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-down
menu displayed when you click on the down arrow in the relevant field. You cannot select or
change the values in the frequency fields. However, if you have made changes to the relevant
settings in the Radio Settings sub-section, the values will be updated in line with the values
you have selected for the local terminal after you have committed the changes.
Note 1: If you make any changes to the frequency values, these will be reflected in the
remote terminal settings after you have committed the changes.
Note 2: If the Frequency Diversity configuration is selected in the Protected & Diversity
Options sub-section, there are Tx Frequency (MHz) and Rx Frequency (MHz) fields
for Radio A and Radio B. If the configuration is not selected, there are only fields
for one radio.
Modem Parameters
The Modem Parameters section is only supported by the DXR 700. It contains the Modulation
field, which you use to set the type of modulation used by the terminal modem. You select the
modulation type from the drop-down list displayed when you double click on the field. The
supported types are 16 QAM (default), 32 QAM, 64 QAM or DQPSK.
SETTING THE MODULATION. The modem modulation you can select is dependent on
the modem in the DXR 700 RMA. Any changes you make must match the modulation type
of the modem of the RMA that is installed.
#NCTO+1
The Alarm IO page is only supported by the DXR 100. The Parameters section in the page is
divided into the following sub-sections:
Alarm Inputs
Alarm Outputs

MARCH 2000
IOM-NMS-1/05C
Figure 13: Alarm I/O Page

The DXR 100 can have up to two alarm inputs or outputs. An alarm input is an external signal
that can be fed into the terminal, eg site door open, where it is used to generate an event in the
Action Table (see Action Table). This enables the alarms at remote sites to be monitored over
the radio link. The alarm inputs are fed into the terminal via DB15 connector on the DXR 100
front 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 to
the occurrence of an event listed in the Action Table.
Alarm Inputs
The 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 whether
the alarm event is triggered when input signal is present or absent. The field is set to the
normal 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 the
name. After you have committed the changes, the names will appear in the Event Tree in the
Action Table page.

MARCH 2000
IOM-NMS-1/05C
You select No Current or Current from the drop-down menu displayed when you double
click on the Normal State field.
Alarm Outputs
The 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 Normal
State field determines whether the normal (ie, no alarm is present) condition is open-circuit or
closed-circuit. You can select either Open or Closed from the drop-down list displayed
when you click-on the field. The Rate field determines the maximum number of changes the
associated alarm signal can make per second. You can select a rate from 0 to 20 using the
up/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 the
name. After you have committed the changes, this is the name that will be displayed in the
Action Table.
#EVKQP6CDNG
You use the Action Table page to select the actions you wish the terminal or SMA to take
when a particular event occurs. This is known as mapping an action to an event. The Action
Table page is divided into the following three panes:
Events
Mapped Actions
Inherited Actions

MARCH 2000
IOM-NMS-1/05C
Figure 14: Action Table Page
Events
The Events pane lists the events that you can set an action for. The events are listed in the
Windows Explorer tree format.
You set or map an action to an event by selecting the event, and then clicking on the Edit
Actions button. This displays the Add Actions window with drop-down lists of available
locations (the terminals where the action can be raised) and available actions. You select 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: Any actions that you have enabled on remote terminals are shown with their location
in parenthesis after the action name.
Mapped Actions
The Mapped Actions pane lists any actions that you have mapped to the alarm presently
selected in the Events pane. You can also remove an action from an alarm by selecting the
action in the Mapped Actions pane, then clicking on the Delete button
Inherited Actions
The Inherited Actions pane lists any actions mapped to an alarm higher up in the tree
hierarchy than the alarm you have currently selected.
Note: An inherited action must be deleted by selecting the alarm causing the action.
MARCH 2000
IOM-NMS-1/05C
'ZVGTPCN+1
The External I/O page is only supported by the SMA. The SMA has a DB15 connector on its
front panel for inputting and outputting external alarms. These are configured both by
software, and by switches and links in the SMA. The SMA can have up to twelve alarm inputs
and outputs, or, if output isolation is applied, up to six outputs.
The External I/O page contains the Alarm Board I/O Channel section. This has a five column
table displaying the following fields:
Channel
Identifier
Type
Electrical State
Rate
The section also an Isolated check-box for each channel pair. This is used to select whether
the input or output signals on the associated channel are isolated or not. When the check box
is empty, there are two full rows in the table rows for each channel (a and b). When the check
box is selected, the lower row of each channel pair is blank apart from the Channel field.
Figure 15: External I/O Page
Channel
The 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.

MARCH 2000
IOM-NMS-1/05C
Identifier
The Identifier field displays the name of the signal. You assign a name to the signal by
double-clicking on the field with the mouse, and typing the name in.
Type
The Type field defines the signal is an input or an output. You assign a state to the signal by
double-clicking on the field with the mouse, and selecting the state from the drop-down menu.
Electrical State
The Electrical State field entry defines the electrical state of the channel when the signal is
present. You assign a state to the signal by double-clicking on the field with the mouse, and
selecting the state from the drop-down menu. You can select between no current and current.
Note: For either signal, changing from the default setting requires you to alter switch
settings in the SMA, and also links in the SMA for output signal changes.
Rate
The Rate field defines the maximum number of changes to the alarm signal that the SMA can
detect per second. It can vary from zero (no alarms detected) to a maximum of twenty. This
field is used to prevent a recurring alarm swamping the alarm monitoring function, preventing
other alarms on the system being detected.
You select the rate by clicking on the Rate field, and either using the up/down arrows, or
typing in the value.
Note: You must select a number within the given range, and you must select an integer
value.
6JTGUJQNFU
The Thresholds page is divided into the following sections:
General
Transmit Path
Receive Path

MARCH 2000
IOM-NMS-1/05C
Figure 16: Thresholds Page
General
The General section contains the Correctable Bytes per Second field. This field is used to set
the number of correctable bytes that can be received over the radio link before triggering the
Correctable Error Limit alarm (see Appendix A for details). If the number exceeds the set
limit, 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 tables show recommended values of Correctable Bytes per Second for each
radio type and capacity to obtain an error rate of 1 x 10-6.
DXR 100
Radio Capacity Link Data Rate Bit Error Rate
Mbit/S 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
Mbit/S 1E-6
1 x STM-0 60.441 60
1 x DS3 51.875 52
MARCH 2000
IOM-NMS-1/05C
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
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 be
masked from the customer traffic.
Transmit Path
The 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 Pane
uses frequency diversity, and also the terminal type. Terminals using frequency diversity have
fields for Radio A and Radio B.
The Forward Power fields, Low limit and High limit, are used to set the values of RF output
power from the terminal transmitter that will trigger the Forward Power alarm (see Appendix
E for details). You can set the limits by either selecting the fields and typing in the value, or
using the up/down arrows in the fields. You can set the fields to their default values by
clicking the Defaults button.
The Reflected Power is used to set the value of the RF power being reflected back to the
terminal from the antenna that will trigger the Reflected Power alarm (see Appendix E for
details). You set the maximum acceptable value by either selecting the field and typing in the
value you require, or using the up/down arrow in the field. You can set the fields to their
default values by clicking the Defaults button.
Receive Path
The appearance of this page depends on whether the terminal selected in the Explorer Pane
uses frequency diversity, and also the terminal type. Terminals using frequency diversity have
fields for Radio A and Radio B.
For a DXR 100 terminal, the page contains the fields used to set the limits for the Automatic
Gain Control (AGC) alarm. The AGC is a voltage applied in the DXR 100 circuitry that
controls the gain applied to the received RF signal to ensure that the information it carries can
be recovered. The two fields, Low limit and High limit, set the range over which it can vary
without triggering the alarm. You can set the values by either selecting the field and typing in
the value you require, or using the up/down arrows in the fields. You can set the fields to their
default values by clicking the Defaults button.

MARCH 2000
IOM-NMS-1/05C
For a DXR 700 terminal, the page contains the fields used to set the Received Signal Strength
Indicator (RSSI) limits for the Rx Path Warning alarm. Refer to Appendix A for details of the
alarms. The RSSI is the strength of the received RF signal in dBm. The two fields, Low limit
and High limit, set the range over which it can vary without triggering the alarm. You can set
the values by either selecting the field and typing in the value you require, or using the
up/down arrows in the fields. You can set the fields to their default values by clicking the
Defaults button.
1RVKQP2CIGU
The Option 1 and Option 2 pages are only supported by the SMA. The Option pages are used
to configure any SDM board fitted into the corresponding option slot of the SMA. The
appearance of the pages depends on type of board that has been fitted to the slot.
Note: In the following, n represents either 1 or 2.
Figure 17: Option page with no board selected
Low Speed Daughter Board

When a Low Speed Daughter Board is fitted to an option slot, the associated option page has
the following sections:
Option Slot n (n depends on which slot the board is inserted into)

Circuit 1
Circuit 2

MARCH 2000
IOM-NMS-1/05C
Figure 18: Option page with Low Speed Daughter Board selected
The Option Slot n section has the following fields:
Option Board Type. You use this field to select the type of board inserted into the slot.
Default is Not Installed. In this case, you select Low Speed Daughter Board from the
drop-down menu displayed when you click on the arrow in the right-hand side of the field.
Cross connect to. You use this field to select the AUX port on the SMA the board uses to
communicate with the SDM board at the other end of the circuit. This in turn selects the
DXR 700 terminal by which the board data is sent and received. Default is AUX A. You
select any one of the four AUX ports on the SMA from the drop-down menu displayed
when you click on the arrow in the right-hand side of the field.
Channel. You use this field to select the first timeslot used for the board data on the AUX
channel. Default is 2. You select either 2 or 3 from the drop-down menu displayed
Note: Channels cannot be shared, and boards always occupy the whole channel,
irrespective of the actual number of bits needed to carry their data. If the SMA
has another daughter board you will only be able to select channel 2.
Channels required. This field shows the number of timeslots on the AUX channel that the
board requires to send and receive data. It is generated automatically, and depends on the
board you selected, and the values you input to the Data Rate fields in the Circuit sections.
Option Board Active. You use this checkbox field to enable the other fields in the section.
If the checkbox is not selected (default), ie, not ticked, all the other fields will be greyed
out and disabled.

MARCH 2000
IOM-NMS-1/05C
Note: Even if the Option Board Active checkbox is not selected, DXR NET will still
configure the low speed daughter board for the required bandwidth parameters
and cross-connects. This is to save you confusion when looking at the Cross-
connect page.
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. You select the mode from the drop-down menu displayed when you click on the
arrow in the right-hand side of the field.
Note: Your selection in this field determines the other fields displayed in the Circuit
section.
Data Rate. You use this field to select the speed at which the board transmits and receives
data. The values you can select are dependant on your selection in the Mode field. If you
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 select one of
2400 (default), 3600, 4800, 7200 or 9600 bits per second. In both cases, you select the 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. You use this
field to set the number of bits needed to represent a character in the board data. You can
choose between 7 or 8 bits (default). You select the number of bits from the drop-down
menu displayed when you click on the arrow in the right-hand side of the field.
Stop Bits. This field is only available when you have selected Async mode. You use this
field to set the number of bits needed to represent a stop bit in the board data. You can
choose between 1 (default) or 2 bits. You select the number of bits from the drop-down
menu displayed when you 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. You use this
field to shorten or shave the length the stop bit(s) in the board data. You would do this to
reduce loss of bit synchronisation due to transmission between stations in multi-hop
situations. You can choose between 1/16th (default) to 7/16th. You select the bit shave bits
from the drop-down menu 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. You use this field
to set up a parity bit used for error checking. The status of the parity bit (0 or 1) is
determined 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 the
status 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 even
number of ones in the data bit. You select the parity from the drop-down menu displayed
Break length. This field is only available when you have selected Async mode. You use
this field to set the number of characters that will represent a line break in the board data.
You can enter an integer from 1 to 65535, representing the break length in characters. The
default is 4.
High Speed Daughter Board

When a High Speed Daughter Board is fitted to an option slot, the associated option page has
the following sections:
MARCH 2000
IOM-NMS-1/05C

Circuit 1
Option Board Type. You use this field to select the type of board inserted into the slot.
Default is Not Installed. In this case, you select High Speed Daughter Board from the
drop-down menu displayed when you click on the arrow in the right-hand side of the field.
communicate with the SDM board at the other end of the circuit. This in turn selects the
DXR 700 terminal by which the board data is sent and received. Default is AUX A. You
select any one of the four AUX ports on the SMA from the drop-down menu displayed
Channel. You use this field to select the first channel used for the board data on the AUX
channel. Default is 2. You select either timeslot 2 or 3 from the drop-down menu
displayed when you click on the arrow in the right-hand side of the field.
has another daughter board, or the high speed daughter board circuits has a data
rate of 128 KBPS, both channels will be required, and you will only be able to
select channel 2.
Channels required. This field shows the number of AUX channels that the board requires
to send and receive data. It is generated automatically, and depends on the board you
selected, and the values you input to the Data Rate fields in the Circuit section.
The Circuit 1 section contains the following fields:
Active. You use this checkbox field to enable the other fields in the section. If the
checkbox is not selected (default), ie, not ticked, all the other fields will be greyed out and
disabled.
Note: Even if the Active checkbox is not selected, DXR NET will still configure the
high speed daughter board for the required bandwidth parameters and cross-
connects. This is to save you confusion when looking at the Cross-connect page.
Data Rate. You use this field to select the speed at which the board transmits and receives
data. You can select one of 8, 16, 24, 32, 48, 56, 64 (default), or 128 KBPS. You select the
rate from the drop-down menu displayed when you click on the arrow in the right-hand
side of the field.
Co-directional Daughter Board

When a Co-directional Daughter Board is fitted to an option slot, the associated option page
has the following sections:

Circuit 1

MARCH 2000
IOM-NMS-1/05C
Figure 19: Option page with Co-directional Daughter Board selected

Option Board Type. You use this field to select the type of board inserted into slot.
Default is Not Installed. In this case, you select Co-directional Daughter Board from
the drop-down menu displayed when you click on the arrow in the right-hand side of the
field.
transmit and receive data. This in turn selects the DXR 700 terminal by which the board
data is sent and received. Default is AUX A. You select any one of the four AUX ports
on the SMA from the drop-down menu displayed when you click on the arrow in the right-
hand side of the field.
Note: You must select an AUX port connected to a terminal.
Channel. You use this field to select the first channel used for the board data on the AUX
channel. Default is 2. You select either 2 or 3 from the drop-down menu displayed
has another daughter board you will only be able to select channel 2.
Channels required. This field shows the number of channels on the AUX channel that the
board requires to send and receive data. It is generated automatically from the board
The Circuit 1 section contains only the message No circuit configuration is required for a
Co-directional Daughter Board.

MARCH 2000
IOM-NMS-1/05C
%TQUUEQPPGEVU2CIG
The Cross-connects page is only supported by the SMA. The Cross-connects page is used to
show the relationship, or cross-connection, between the SDM board data stream timeslots and
the timeslots available on the SMA AUX ports. Cross-connections are required for the data
streams of any SDM boards in the actual SMA, and also for any data streams the SMA is
relaying.
Note: In the latter case, the SDM boards are in other SMA, and the SMA is relaying them
as part of a multi-hop link.
Figure 20: Cross Connect Page with grid shown

The relationship between the timeslots is shown on the grid. The vertical and horizontal axes
shows the AUX port channels, two channels for each port. Cross-connects between channels
are shown shaded on the grid, ie, 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 in, along with the
row from AUX B (3). This is to indicate the channels are unavailable for other connections.
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 option
pages. 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 present
SMA. In this case, the SMA is being used as a relay, and the cross-connects are between
available AUX port timeslots.
MARCH 2000
IOM-NMS-1/05C
Note: The two types of cross-connection are distinguished in the grid by different shading.
To set a manual cross-connection, you move the mouse to select the appropriate row and
column, then click the left mouse button. The selected row and column is then shaded in to
show they are in use. As you move the mouse cursor through the grid, the row directly
underneath it and the column directly to the right of the cursor are shaded red, showing the
current cross-connection that would be made if you 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, you move the mouse to select the appropriate row and
column, then click the left mouse button.
Note: You cannot remove an automatic cross-connection.
%QOOKUUKQPKPI9QTMURCEG
You can use the Commissioning Workspace to install and commission a DXR network
element. It 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 IF
loopback 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 workspace
area.
Note 1: For the details associated with a particular type of element, refer to the relevant
section in this manual.
Note 2: The Commissioning workspace cannot be used offline, as its pages use real-time
data 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 network
element after it has been brought into service, especially during commissioning. The
workspace has the following tabbed pages:
Commissioning 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)

MARCH 2000
IOM-NMS-1/05C
%QOOKUUKQPKPI
The Commissioning page is divided into Local (Selected) and Remote sections. The details
for 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 the
Remote section.
Note: The Remote section details are only valid if the link is operational.
Each 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.
Site Details
The Site Details sub-section contains the following fields:
Site
Terminal
TX Frequency (MHz)
TX Power (dBm)
Each of these fields should contain the names or values that you have assigned to their
associated parameter. If you have not assigned a name or value, the field contains the default
name or value for that parameter.
Note: Terminals using frequency diversity will have TX Frequency and TX Power fields
for Radio A and Radio B.
AGC
The AGC sub-section contains a bar-graph and a Reset AGC button. The bar graph shows the
current AGC value, continually updated. The Reset AGC button resets the maximum and
minimum lines on the bar graph to the maximum and minimum AGC values measured since
the monitoring began, or since the last time the button was selected.
Note: Terminals using frequency diversity will have bar graphs for Radio A and Radio B.
RSSI
The RSSI sub-section contains a bar-graph and a Reset RSSI button. The bar graph shows the
current RSSI value, continually updated. The Reset RSSI button resets the maximum and
minimum lines on the bar graph to the maximum and minimum RSSI values measured since
the monitoring began, or since the last time the button was selected.
Note: Terminals using frequency diversity will have bar graphs for Radio A and Radio B.

MARCH 2000
IOM-NMS-1/05C
Alarm Information
The Alarm information section has two items, an Alarm Status LED icon, and a View Alarms
button. The icon is used to indicate whether any alarms are present on the terminal. The
colours it can take and their meanings are listed in the table below.
%QNQWT /GCPKPI
$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 is
divided into two panes. The left-hand pane, Alarm Status and Related Information, lists all
possible alarms in the Windows Explorer tree format. This has the alarms grouped in
hierarchical levels under the units currently present in the link or terminal. You can also
update the display at any time by clicking on the Refresh button.
Figure 21: Alarms Page

You can move through the levels by double clicking on a unit listing to display the sub-unit
and alarm listing under it. Each unit or alarm listing has an LED icon next to it. The icon
indicates whether there are any alarms present in the unit or any sub-units under it. For an
alarm 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 Alarm
Status and Related Information pane to detect when an alarm is present on an unit, and then to
track the alarm to a particular component.

MARCH 2000
IOM-NMS-1/05C
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. The
Alarm Description contains the probable cause of the alarm.
The Alarm Type field entries are described in the following table.
#NCTO6[RG &GUETKRVKQP
'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.
#NCTO5GXGTKV[ &GUETKRVKQP
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 fault
occurs.
/CLQT Indicates a condition affecting user traffic that requires
corrective action.
%TKVKECN Indicates a condition affecting user traffic that requires
immediate corrective action.
For full descriptions of the alarms that can be generated by a DXR network element, refer to
Appendix E.
6GTOKPCN&GVCKNU
The Terminal Details page is divided into the following sections:
General Information
Pedigree Information (non-protected DXR 100 terminal only)

MARCH 2000
IOM-NMS-1/05C
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
The Local (Selected) button is used to display the details of the terminal you have selected in
the Explorer Tree. The Remote button will display the details of the remote terminal, ie, the
terminal that the terminal you have selected is linked to. The Refresh button will re-display
the Terminal Details page to take into account any changes since the page was first selected.
Note: Remote terminal details can only be displayed if the link is operational.
General Information
The General Information section contains the following fields:
Site Name
Terminal Name
Terminal Type
Modulation Type
Capacity
Occupied Bandwidth
The Site Name field contains the name that you gave the site when you created the network
blueprint, or, alternatively, in the General Setup page in the Configuration Workspace.
Note: If you have not given a name to the site, the field has the default string Site n
where n is an integer relating to the number of radios in the network.
The Terminal Name field contains the name you gave the terminal when you created the
network blueprint, or, alternatively, in the General Setup page in the Configuration
Workspace.

MARCH 2000
IOM-NMS-1/05C
Note: If you not given a name to the terminal, the field has the default string Terminal n
where n is an integer relating to the number of radios in the network.
The Terminal Type field contains the equipment description of the terminal. You set the
Terminal Type when you assigned the terminal to the network blueprint. The field is
generated automatically from your selection, and you cannot change it except by deleting the
terminal from the blueprint and selecting another terminal.
The Modulation Type field contains the type of modulation the terminal applies to the RF
signal.
Note: The type of modulation is set at the factory, so you specify the type you require
when you order the terminal.
The Capacity field is only displayed when the terminal line interface type can support more
than one channel.
Note: The capacity is set at the factory, so you specify it when you order the terminal. You
can 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 terminal
takes up. The field is generated automatically from the frequency range and modulation type
you specified when you ordered the terminal, and you cannot change it.
Pedigree Information
For 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 a
Details button, which you can use to display the Pedigree Details box. This lists the Part
Number, Serial Number and Build Level for the Terminal Hardware, and the Version and
Type for the Terminal Software.
Daughter Board Information

For a DXR 100 terminal, the Daughter Board Information section contains the following
fields:
Option Board 1
Option Board 2
These two fields display the names of any optional daughter boards that have been fitted into
the DXR 100. The entries are automatically generated depending upon whether/which boards
are fitted, and you will not be able to change them.
Note: The boards are normally factory fitted, which means you have to specify them when
you order the terminal. They should only be fitted in the field by an accredited
Digital Microwave Corporation representative.

MARCH 2000
IOM-NMS-1/05C
PSW
For a protected DXR 100 terminal, the PSW section contains the following fields for the
PSW:
Part Number
Serial Number
Software Version
Option Board 1
Option Board 2
PSW Details button, which you can use to display further details.
PRA A
For a protected DXR 100 terminal, the PRA A section contains the following fields for Radio
A:
Part Number
Serial Number
Software Version
PRA A Details button, which you can use to display further details.
PRA B
For a protected DXR 100 terminal, the PRA B section contains the following fields for Radio
B:
Part Number
Serial Number
Software Version
PRA B Details button, which you can use to display further details.
PMA Information
For a DXR 700 terminal, the PMA Information section contains the following fields:
Part Number
Serial Number
Software Version
PMA Details button, which you can use to display the PMA Details box. This lists the Part
Number, Serial Number and Build Level for the PMA Hardware, the Build Type for the PMA
Interface capacity, and the Version and Type for the PMA Software.

MARCH 2000
IOM-NMS-1/05C
RMA Information
For a non-protected DXR 700 terminal, the RMA Information section contains the following
fields:
Part Number
Serial Number
Software Version
RMA Details button, which you can use to display the RMA Details box. This lists the Part
Number, 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 RMA
Software.
ODU Information
For a non-protected DXR 700 terminal, the ODU Information section contains the following
fields:
Part Number
Serial Number
Software Version
Details 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, and the Version and Type for the
ODU Software.
RMA A Information
For a protected DXR 700 terminal, the RMA A section contains the following fields:
Part Number
Serial Number
Software Version
Software.
RMA B Information
For a protected DXR 700 terminal, the RMA B section contains the following fields:
Part Number
Serial Number
Software Version

MARCH 2000
IOM-NMS-1/05C
Software.
ODU A Information
For a protected DXR 700 terminal, the ODU A section contains the following fields:
Part Number
Serial Number
Software Version
ODU Software.
ODU B Information
For a protected DXR 700 terminal, the ODU B section contains the following fields:
Part Number
Serial Number
Software Version
ODU Software.
0/5&GVCKNU
The NMS Details page is divided into the following sections:
General Information
General 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 to
the site, the field is assigned the default string Site n where n is an integer relating to the
number of sites in the network.

MARCH 2000
IOM-NMS-1/05C
The Element Name field contains the name assigned to NMS. If you not assigned a name to
the NMS, the field contains the default string NMS n where n is an integer relating to the
number of NMS boards in the network.
The Element Type field contains a detailed description of the NMS board, usually DXR 100
NMS board.
The Pedigree Information section contains the following fields:
Part Number
Serial Number
Software Type
Software Version
Number, Serial Number and Build Level for the Board Hardware, and the Version and Type
for the Board Software.
5/#&GVCKNU
The SMA Details page is divided into the following sections:
General Information
SMA
Option Slot 1 (SDM equipped SMA only)
Option Slot 2 (SDM equipped SMA only)

MARCH 2000
IOM-NMS-1/05C
Figure 22: SMA Details Page
General Information
Site Name
SMA Name
The Site Name field contains the names that you have assigned to the site in the network
blueprint. You set the Site Name either when you create the network blueprint, or,
alternatively, in the General Setup page in the Configuration Workspace. If you have not
assigned a name to the site, the field is assigned the default string Site n where n is an
integer relating to the number of radios in the network.
The SMA Name field contains the name you have assigned to the terminal in the network
blueprint. You set the SMA Name either when you create the network blueprint, or,
alternatively, in the General Setup page in the Configuration Workspace. If you not assigned a
name to the SMA, the field contains the default string Undefined SMA n where n is an
integer relating to the number of SMAs in the network.
SMA
The SMA section contains the following fields:
Part Number
Serial Number
Software Type

MARCH 2000
IOM-NMS-1/05C
Software Version
Number, Serial Number and Build Level for the SMA Hardware, and the Version and Type
for the SMA Software.
Option Slot Sections

Depending on the type of board inserted into their associated slot, the Option Slot sections
can contain the following fields:
Note: The Board ID text field will always be present, but the other three fields are only
present when either a low speed or high speed daughter board has been inserted into
the appropriate slot.
Board ID text
Part Number
Serial Number
Software Version
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 are
self-explanatory.
%QPVTQNU
The Controls page is divided into the Tributary Loopbacks, RF/Modem, Protection Switching
and Script File sections.
Note: The Protection Switching section is only available with a terminal in the protected
configuration.

MARCH 2000
IOM-NMS-1/05C
Figure 23: Controls Page
Tributary Loopbacks
The Tributary Loopbacks section allows you to select the following types of loopbacks:
No Tributary Loopback (default)

Line Facing
Radio Facing
You select an option by clicking on the appropriate radio button with the mouse. The centre of
the button you have selected is filled in to show it has been selected.
Note: You can only select 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 locate
where any integrity problems are occurring. When you select a loopback 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.

MARCH 2000
IOM-NMS-1/05C
When you select the Line Facing loopback function, the loopback is made in the local
terminal line interface. Any bit-stream fed into a line input channel to the terminal is fed back
out again on the appropriate line output channels. You can then compare the output stream
with the input stream, identifying any errors. From this, you will be able to deduce the quality
of service and the error-rate of the terminal line interface.
When you select the Radio Facing loopback function, the loopback is made in the local
terminal radio interface. Any signals received from the remote terminal will be re-transmitted
back to the remote terminal over the radio link. You can then compare the output stream at the
remote terminal with the input stream, identifying any errors. From this, you will be able to
deduce the quality of service and the error-rate of the radio link.
RF/Modem
The RF/Modem section allows you to select the following types of loopbacks:
Digital Loopbacks
IF Loopback
FEC Disable
You select an option by clicking on the appropriate check box with the mouse. The box you
have selected is checked.
LOOPBACK FUNCTIONS. Loopback functions interrupt network traffic.
Note: You can only select these loopbacks for the local terminal.
You can use the loopback functions to test the data integrity of the terminal, and to help locate
where any integrity problems are occurring. When you select a loopback function, the
terminal feeds any received input data back to the source. Normally, you would enable a
loopback function, input a known bit-stream, and check the bit-stream output from the
terminal. You can then compare the output stream with the input stream, identifying any
errors.
When you select the Digital Loopbacks option, the loopback is made between the composite
digital transmit and receive streams inside the radio modem, before the streams are passed to
digital-to-analogue conversion. From this, you will be able to deduce the error-rate in the
modem circuitry.
When you select the IF Loopbacks option, the loopback is made between the transmit and
receive IF signals, just before they are output from the terminal. From this, you will be able to
deduce the error-rate in the IF circuitry.
When you select the FEC Disable option, the loopback is made between the transmit and
receive RF channels by setting them both to the same frequency. From this, you will be able
to deduce the transmission error-rate. You need to disable FEC for this, as FEC automatically
corrects any errored bytes in the received data, and this would mean that any errors would be
corrected before you could detect them.
Protection Switching
The Protection Switching section is only displayed when the terminal is in one of the
protected configurations. It allows you to test the ability of the terminal to switch between the
available transmitters and receivers.

MARCH 2000
IOM-NMS-1/05C
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 by
clicking on the appropriate radio button with the mouse. The centre of the button you have
selected 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 radio
button with the mouse. The centre of the button you have selected is filled in to show it has
been selected.
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 by
clicking on the appropriate radio button with the mouse. The centre of the button you have
selected is filled in to show it has been selected.
Note: You must select Manual operation before the Radio listing and radio buttons are
displayed, ie, before you can select a radio.
You can select either the A Side (default) or B Side radio by clicking on the appropriate radio
button with the mouse. The centre of the button you have selected is filled in to show it has
been selected.
Script File
SCRIPT FILES. You should only run script files under the supervision of accredited DMC
service personnel.
You can click the Script File button to open the window that will allow you to select and run
any available test script files.
/CKPVGPCPEG9QTMURCEG
You can use the Maintenance Workspace diagnose any faults in a DXR network element. The
available monitoring and diagnostic functions include:
Alarm information
Constellation diagrams
AGC/RSSI graphs

MARCH 2000
IOM-NMS-1/05C
SNR readings
line and radio facing loopback functions for the terminal tributaries, and digital and IF
loopback 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 workspace
area.
Note 1: For the details associated with a particular type of element, refer to the relevant
section in this manual.
Note 2: The Maintenance workspace cannot be used offline, as it relies on real-time data
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 Maintenance Workspace has the following tabbed pages:
Alarms
Constellation (DXR 100 and DXR 700)
AGC (DXR 100 only)
RSSI (DXR 700 only)
Controls (DXR 100 and DXR 700)
Terminal Details (DXR 100 and DXR 700)
NMS Details (NMS board only)
The Alarms, Controls, Terminal Details and NMS Details pages are identical to those
described under the Commissioning Workspace heading, and therefore will not be detailed
here.
%QPUVGNNCVKQP
SELECTING OTHER OPERATIONS. Except for the AGC page operations (DXR 100
terminal), or RSSI page operations (DXR 700 terminal), you cannot select other operations
while Constellation Diagram monitoring is in progress.
STOPPING MONITORING. You must remember that just because a constellation diagram
is not shown for a terminal or carrier does NOT mean the terminal or carrier is not being
monitored. When you are finished using the Constellation page, do not leave monitoring
running, or DXR NET performance will be affected.
A constellation diagram is a polar graph showing the plots obtained from monitoring a
selected signal. The plots consist of groups of points, each point representing many samples
of the phase and amplitude of the signal. For error-free operation, the points should be tightly
grouped together. You can therefore use the plots in the diagram monitor signal performance.
The Constellation page is divided into the Select Terminal and the Constellation Diagram
sections.

MARCH 2000
IOM-NMS-1/05C
Figure 24: Constellation Diagram Single View Selected

The appearance of these two sections is dependant upon whether the Single or Multi-carrier
view has been selected in the Advanced option of the DXR NET Maintenance menu (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 available terminal. If the
Multi-carrier view has been selected, DXR NET produces constellation diagrams by
monitoring the individual carriers on the local terminal.
Select Terminal
If you have selected the Single view in the Maintenance menu, the Select Terminal section
will contain the following buttons:
Local (for an unprotected terminal), or Local A, Local B (for a protected terminal)

Remote (for an unprotected terminal) or Remote A, Remote B (for a protected terminal)
Monitor All
Reset All
By selecting from the Local and Remote buttons, you choose the terminals for which
constellation diagrams will be displayed in the Constellation Diagram section.
Note: The diagrams for the Remote terminal(s) can only be produced when the link is
operational.
When you select the Monitor All button, DXR NET will start monitoring all the baseband
signals from all available terminals. When you select the Reset All button, DXR NET will start
re-monitoring all the baseband signals from all available terminals from that point in time.
MARCH 2000
IOM-NMS-1/05C
If the Multi-carrier option is selected in the Maintenance menu, the Select Terminal section
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 constellation
diagrams will be displayed in the Constellation Diagram 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 carriers
on the local terminal. When you select the Reset All button, DXR NET will start re-monitoring
all the carriers from that point in time.
Constellation Diagram
The Constellation Diagram section will display the following items for each of the terminals
or carriers that were chosen using the Local, Remote or Carrier buttons in the Select Terminal
section:
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 obtained
from monitoring the selected terminal or carrier. You can therefore use the diagram monitor
signal performance.
Note: The number of sections the diagram is divided into depends on the type of
modulation being used, eg. for DQPSK, the diagram is divided into four sections,
for 16QAM, it is divided into sixteen sections.
The AGC (V) and SNR (dBm) fields allow you to view the current values of these two
parameters for the selected terminal or carrier.
When you select the Monitor button, DXR NET will start monitoring the selected terminal or
carrier. When you select the Reset button, DXR NET will start re-monitoring the selected
terminal or carrier from that point in time.
Note: Unlike the Monitor All and Reset All buttons in the Select Terminal section, these
buttons only control the monitoring of the terminal or carrier related to this specific
diagram.
#)%
SELECTING OTHER OPERATIONS. Except for the Constellation page operations, you

MARCH 2000
IOM-NMS-1/05C
cannot select other operations while AGC monitoring is in progress.
STOPPING MONITORING. You must remember that just because an AGC graph is not
shown for a terminal or carrier does NOT mean the terminal or carrier is not being
monitored. When you are finished using the AGC page, do not leave monitoring running, or
DXR NET performance will be affected.
The AGC (Automatic Gain Control) is a voltage, which is used to control the amount of gain
applied by the DXR 100 terminal to a received signal. It is derived automatically by the
terminal, based upon the strength of the received signal, compared with that required to
produce a recognisable output signal. The AGC variation with respect to time is plotted on an
AGC graph, and this plot can then be used to monitor the terminal performance.
The AGC page is divided into the Select Terminal and the AGC graph sections.
Figure 25: AGC Graph Single View Selected

The appearance of these two sections is dependant upon whether the Single or Multi-carrier
view has been selected in the Advanced option of the DXR NET Maintenance menu (refer to
Section 2, DXR NET GUI). If the Single view has been selected, DXR NET produces graphs
by monitoring the AGC applied to the baseband signals from each available terminal. If the
Multi-carrier view has been selected, DXR NET produces constellation diagrams by
monitoring the AGC applied to the individual carriers on the local terminal.
Select Terminal
MARCH 2000
IOM-NMS-1/05C
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 protected DXR
100)
Monitor All
Reset All
By selecting from the Local and Remote buttons, you choose the terminals for which graphs
will be displayed in the AGC Graph section.
Note: The graphs for the Remote terminal(s) can only be produced when the link is
operational.
When you select the Monitor All button, DXR NET will start monitoring all the AGC voltages
applied to the baseband signals from all available terminals. When you select the Reset All
button, DXR NET will start re-monitoring all the AGC voltages from all available terminals
from that point in time.
Monitor All
Reset All
By selecting from the Carrier n buttons, you choose the carriers for which graphs will be
displayed in the AGC Graph section.
When you select the Monitor All button, DXR NET will start monitoring the AGC voltages
applied to all available carriers on the local terminal. When you select the Reset All button,
DXR NET will start re-monitoring all the carriers from that point in time.
AGC Graph
Except for the Constellation page operations, you cannot select other operations while AGC
monitoring is in progress.
The AGC Graph section will display the following items for each of the terminals or carriers
that were chosen using the Local, Remote or Carrier 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 voltage
for the selected terminal or carrier plotted on a graph. The graph shows sampled AGC voltage
value plotted between the maximum and minimum values detected during the monitoring
period. You can therefore monitor the variation of the AGC voltage with time.

MARCH 2000
IOM-NMS-1/05C
When you select the Monitor button, DXR NET NET will start monitoring all the selected
terminal or carrier. When you select the Reset button, DXR NET will reset the Max and Min
bars on the AGC graph to the maximum and minimum AGC values recorded since either
monitoring began, or since the last time the Rest button was selected.
diagram.
455+
SELECTING OTHER OPERATIONS. Except for the Constellation page operations, you
cannot 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 26: RSSI Page

MARCH 2000
IOM-NMS-1/05C
The RSSI (Received Signal Strength Indication) is a measure of the strength of the radio
signal being received by the DXR 700. An RSSI Graph is a dynamic display of the RSSI
plotted with respect to time. The graph shows sampled RSSI value plotted between the
maximum and minimum RSSI values you selected in the Thresholds page of the Configuring
Workspace. You can therefore use this 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. The
appearance of these two sections is dependant upon whether the Single or Multi-carrier view
has been selected in the Advanced option of the DXR NET Maintenance menu (refer to
Section 2, DXR NET GUI). If the Single view has been selected, DXR NET produces RSSI
graphs by monitoring the baseband signals from each available terminal. If the Multi-carrier
view has been selected, DXR NET produces graphs by monitoring the individual carriers on
the local terminal.
Select Terminal
Local (for an unprotected DXR 700), or Local A, Local B (for a protected DXR 700)
Remote (for an unprotected DXR 700) or Remote A, Remote B (for a protected DXR
700)
Monitor All
Reset All
By selecting from the Local and Remote buttons, you choose the terminals for which RSSI
graphs will be displayed in the RSSI Graph section.
Note: The diagrams for the Remote terminal(s) can only be produced when the link is
operational.
When you select the Monitor All button, DXR NET NET will start monitoring all the baseband
signals from all available terminals. When you select the Reset All button, DXR NET will start
re-monitoring all the baseband signals from all available terminals from that point in time.
Monitor All
Reset All
By selecting from the Carrier n buttons, you choose the carriers for which graphs will be
displayed in the RSSI Graph section.
When you select the Monitor All button, DXR NET NET will start monitoring all available
carriers on the local terminal. When you select the Reset All button, DXR NET will start re-
monitoring all the carriers from that point in time.

MARCH 2000
IOM-NMS-1/05C
RSSI Graph
The RSSI Graph section will display the following items for each of the terminals or carriers
that 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 selected
terminal or carrier with time. You can therefore use the diagram monitor signal performance.
When you select the Monitor button, DXR NET NET will start monitoring the selected terminal
or carrier. When you select the Reset button, DXR NET will reset the Max and Min bars on
the graph to the maximum and minimum RSSI values detected since the start of monitoring,
or since the Rest button was last pressed.
graph.
(KNG5[UVGO
The File System page is used to view, and if necessary, delete, BIN files stored on SMA and
NMS boards. These files are used when loading software to the elements under the control of
the SMA or NMS board, and should be removed when loading new software.

MARCH 2000
IOM-NMS-1/05C
Installing DXR NET
+PUVCNNKPI&:40'6
+PVTQFWEVKQP
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 requirements
listed below. We also advise that the person carrying out the installation is familiar
with the features and terminology of your PC operating system.
4GSWKTGOGPVU
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 the
level of the tool you are installing.
5QHVYCTG4GSWKTGOGPVU
Local Maintenance Tool
To run the DXR NET Local Maintenance Tool (LMT), a PC must have one of:
Microsoft Windows 95 OEM Service Release (OSR) 2 operating system (or later),
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 operating
system. The operating system version is detailed in the System Properties window,
which can be accessed via the System icon in the Control Panel window.
Network Maintenance Tool

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

MARCH 2000
IOM-NMS-1/05C
Installing DXR NET
Microsoft Windows NT 4.0 (or later)

Note: Windows 95 users should check that they are running a B version of the operating
system. The operating system version is detailed in the System Properties window,
which can be accessed via the System icon in the Control Panel window.
Event Manager
To run the DXR NET Event Manager (EM), a PC must have Microsoft Windows NT 4.0 (or
later).
Note: The EM will run on earlier versions, but there is no support for any of its functions.
*CTFYCTG4GSWKTGOGPVU
Note: The hardware requirements listed below are for the DXR NET tools only, and do not
take into account any requirements of any other software. Before installing DXR
NET, you should check that your PC has the capacity to operate both the tool, and
any other required software.
Local Maintenance Tool

The minimum hardware requirements for DXR NET Local Maintenance Tool (LMT) are as
follows:
100 MHz Pentium Processor

64 MB RAM
100 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
Network Maintenance Tool

The minimum hardware requirements for DXR NET Network Maintenance Tool (NMT) are as
follows:

64 MB RAM
3.5 floppy drive

MARCH 2000
IOM-NMS-1/05C
Installing DXR NET
2 or 3-button Mouse
101-key US keyboard
Event Manager
The minimum hardware configuration for DXR NET Event Manager (EM) is as follows:

128 MB RAM
3.5 floppy drive
Ethernet port
2 or 3-button Mouse
101-key US keyboard
+PUVCNNKPI&:40'6QP[QWT2%
After ensuring that you have fulfilled all the conditions detailed under Workstation
Requirements, 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 (for Windows 98)
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 DXR driver
utility
ensuring your PC has W95ws2se.exe installed (for Windows 95)
4GOQXKPI&:4 0'6HTQO[QWT2%
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 your
current version. However, keeping the earlier versions could lead to confusion between
program files (especially when installing the DMC DXR Driver utility), and will take up
memory space.
If you do wish to remove any versions of DXR NET from your PC, proceed as follows:

MARCH 2000
IOM-NMS-1/05C
Installing DXR NET
WINDOWS 95 PROMPTS. When using this procedure in Windows 95, you will be
prompted 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 installation
will be reliant on the "sif.ini" file being present.
BLUEPRINTS AND CONFIGURATION FILES. If you wish to remove an earlier version

of DXR NET but keep any network blueprint files or element configuration files created by
the earlier version, make sure you save these files outside the DMC folder before removing
the earlier version of DXR NET.
Procedure
Step 1: On the desktop, click Start to display the Start menu, then select Settings, Control
Panel.
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 the
Install/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 in
the Confirm Delete box. The Uninstall utility will now remove DXR NET from your
PC.
Step 5: Uninstall will display a message if it cannot remove certain folders or files. If this
happens, click the Details button, and record the file details to remove them
manually later.
Step 6: Click the OK button to return to the Control Panel window, then close the Control
Panel 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 the
procedure for any other versions, or until DXR NET is completely removed from your PC
+PUVCNNKPI6%2+2QP[QWT2%
HQT9KPFQYU
TCP/IP NETWORKING. Your PC must have TCP/IP networking installed to use DXR NET
If your PC uses the Windows 98 operating system, you need to check that it has TCP/IP
networking is installed. You will need to install TCP/IP on your PC to let it use the NMS
connection. This requires you to:
1. Install the Windows 98 TCP/IP protocol, and bind it to the Dial-Up Networking adaptor.
2. Enter TCP/IP information.
Installing the Windows 98 TCP/IP protocol

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

MARCH 2000
IOM-NMS-1/05C
Installing DXR NET
Step 2: Click the Add button, and check the protocols displayed in the window. If the
Windows 98 TCP/IP protocol is already installed, you can skip the rest of this
procedure, 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 Information
procedure.
Note: When you install TCP/IP, it is bound to all of your adaptors by default. If you have a
network card and don't use TCP/IP with it, in the Network dialog box, select the
network card, click Properties, click the Bindings tab, and then click to clear the
TCP/IP check box.
Entering TCP/IP Information

Step 1: On the desktop, click Start to display the Start menu, select Settings, click Control
Panel, and then double-click Network to display the Network dialog box.
Step 2: Click TCP/IP (if there is more than one TCP/IP entry, click TCP/IP -> Dial-Up
Adapter), 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 printer
sharing check box.
+PUVCNNKPI&:40'6HTQOHNQRR[FKUM
DXR NET is installed from either 3.5-inch floppy disks or CD.
Note: If you received DXR NET on CD, and require floppy disks, or vice-versa, please
contact your local Digital Microwave Corporation agent, or the Customer Services
Department of the Digital Microwave Corporation Long Haul Division (refer to the
copyright page in the front of this manual).
WINDOWS NT ADMINISTRATION RIGHTS. As per other Windows applications, you

must have logged onto NT with administration rights in order to install the DXR NET
application. Also, when using DXR NET with Windows NT, you must log on as the user
who installed the DXR NET application.
The installation is carried out using DXR NET InstallShield utility. The procedure is as
follows:
Note: Digital Microwave Corporation advises that you use the default locations and
folders set by InstallShield, but take careful note of the destination drive for the
DMC program folder and the COM port selected on your PC.

MARCH 2000
IOM-NMS-1/05C
Installing DXR NET
Procedure
Step 1: From the desktop, insert Disk 1 of the installation disks into the 3.5 floppy drive.
Step 2: Run the setup.exe file on Disk 1. This will run InstallShield, which will install the
tool on your PC.
Step 3: Follow the screen prompts. These will be either requests to insert disks, or whether
you wish to accept or change the InstallShield default settings.
Step 4: Click on the Next button to move to the next screen, until the installation procedure
is complete.
Step 5: Remove the last installation disk from your PC, and store the disks in a safe place.
The installation procedure is now complete.
+PUVCNNKPI&:40'6HTQO%&
The installation is carried out using DXR NET InstallShield utility. The procedure is as
follows:
Note: Digital Microwave Corporation advises that you use the default locations and
folders set by InstallShield, but take careful note of the destination drive for the
DMC program folder 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 the
tool on your PC.
Step 3: Follow the screen prompts. These will be requests as to whether you wish to accept
or change the InstallShield default settings.
Step 4: Click on the Next button to move to the next screen, until the installation procedure
is complete.
Step 5: Remove the CD from your PC, and store in a safe place.
The installation procedure is now complete for Windows 98 or later. Windows 95 requires
WinSock2 to be installed.
+PUVCNNKPI9KPFQYUsK&KCNWRL0GVYQTMKPI
DXR NET uses Windows Dial-up Networking to make an NMS connection to a SMA or
NMS board, either directly, or via a modem. From the user perspective, both types of
connection appear to be via a Dial-up modem.
Note: To set-up Windows Dial-up Networking for modem connections, consult the
instructions that came with your modem.
To install Windows Dial-up Networking on your PC, boot-up your PC and proceed as
follows:
MARCH 2000
IOM-NMS-1/05C
Installing DXR NET
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 OK
button.
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.
+PUVCNNKPI&/%&:4&TKXGT7VKNKV[
For the direct NMS connection to a SMA or NMS board the DMCDXR driver utility is
installed in place of the modem driver:
Procedure
Step 2: Select Settings, Control Panel from the Start button menu.
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 Dont Detect, then Next.
Step 7: Select Have Disk, and use Browse Program Files to find dmcdxr.inf, then select OK.
This driver should be in the drivers directory, under the directory where DXR 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.
Step 11: Select File, Close in the Control Panel window.

MARCH 2000
IOM-NMS-1/05C
Installing DXR NET
5VCTVKPI9KPFQYUsK&KCNWRL0GVYQTMKPIHQTVJG(KTUV6KOG
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.
Step 10: Select Server Type button. If required, set the defaults to PPP (Point-to-Point
Protocol) 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 Require
Encrypted 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.
+PUVCNNKPI9KP5QEM
HQT9KPFQYU
This is not required in Windows 98 or later.
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.

MARCH 2000
IOM-NMS-1/05C
Using DXR NET LMT and NMT
7UKPI&:40'6./6CPF0/6
)GPGTCN
This section describes how to use DXR NET LMT and NMT. You can use these tools in three
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
&GUKIPKPI0GVYQTM$NWGRTKPVUYKVJVJG&:40'6./6CPF0/6
0GVYQTM$NWGRTKPV1XGTXKGY
The network blueprint is a software representation of the actual DXR network. It is used to
ensure the network and its elements are configured, commissioned, and maintained in an
orderly 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 Blueprint

To add a site to a network, either right-click on the network icon and select Add Site, or select
the network icon and select Add Site from the Configuration menu.
Adding Network Elements to a Site in a Network Blueprint

The way in which you add a network element to a site in the blueprint depends on the type of
element, 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 a
SMA, select the required element from the Add Network Element window, then click the
OK button
to add either a DXR 100 with a NMS board, select the required DXR 100 terminal from
the Add Network Element window, click the NMS Option check box, then click the OK
button

MARCH 2000
IOM-NMS-1/05C
to add a DXR 700 under SMA control, first add the SMA as described above, select the
SMA in the DXR NET Explorer Tree pane, select the required DXR 700 from the Add
Network Element window, then click the OK button
%TGCVKPIC0GVYQTM$NWGRTKPVHQTCPQP0/50GVYQTM
Before you can create a blueprint for a non-NMS network, you must have carried out the
following tasks:
given the network a name

identified and named all the sites on the network
identified and named all the terminals at each site
%TGCVKPICPQP0/5$NWGRTKPV
You can create a blueprint for a non-NMS network using the following procedure:
Note 1: Unless your network is very simple, we advise you to use the Network Maintenance
Tool.
Note 2: 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 the
top of the column. Click on Network, type in the name you have given to the
network, then press <Enter>.
Step 4: To add a site to the blueprint, right-click on the Network icon in the Explorer Tree
pane, then select Add Site from the drop-down menu. The Site icon will appear in
the pane, followed by Site n, 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. The
Site Information page appears in the workspace. Enter the name you have given the
site 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. When
you 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 of
terminal you want to add to the site from the Add Network Element window as
described in Adding Network Elements. The icon for the terminal will appear in the
Explorer Tree pane, followed by the default name. Click on the default name, type
in the name you have given to the terminal, then press <Enter>.

MARCH 2000
IOM-NMS-1/05C
Step 8: To import an already saved configuration file for a terminal to a site, right-click on
the Site icon in the Explorer Tree pane, then select Import Network Element from
the drop-down menu. In the Import Configuration window, select the previously
saved configuration file for the terminal, then click Open. The icon for the terminal
will appear listed under the site in the Explorer Tree pane, followed by the file
name. If you want to give the terminal a new name, click on the current name, type
in the name of your choice, then press <Enter>.
Step 9: Select the terminal you have just added or imported, then go through each of the
available tabbed pages in the Configuration workspace. Either accept the default
settings, or enter the values you require. Refer to the section in this manual that
describes 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 Save
from the drop-down menu to save the blueprint for future reference.
Step 12: If you are finished using DXR NET, select File from the menu bar, and then Exit.
You are now returned to the PC desktop.
'ZCORNG0QP0/5$NWGRTKPV
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 to
Seatown, and the other from Newtown to Oldtown. You have selected protected DXR 103
terminals to make the links; there will be two of these at the Newton site, and one each at the
other sites.
Before you start to design the network blueprint, you should decide what names you are going
to use in the blueprint. You should therefore try and select names that are meaningful to you
and to anyone else who may have cause to use the blueprint. At the same time, the names
should 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 to
easily identify the blueprint file. As the network is to service three hospitals, you decide to
call 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 and
SEATOWN. If there was more than one site at each location, you could distinguish them by
including either a letter or a number in the name, eg. NEWTON-A, NEWTON-B, or
NEWTON-1, NEWTON-2, etc.
You can now select the terminal names. The most useful information these can contain is
which link the terminal belongs to, and which end of the link it is at. You can achieve this by
including the names of the local and remote sites in the terminal name, with 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 terminal at Seatown could be named
SEATOWN-NEWTOWN, or SEA-NEW. You should ensure that any shortened names retain
enough detail to be clearly identified by anyone who will use the blueprint.

MARCH 2000
IOM-NMS-1/05C
You can now begin to design the blueprint:
Procedure
top of the column. Click on Network, type in MEDICAL, then press <Enter>.
Step 4: Right-click on the Network icon in the Explorer Tree pane, then select Add Site
from the drop-down menu. The Site icon will appear in the pane, followed by Site
n, where n relates to the number of sites already in the blueprint.
Site Information page appears in the workspace. Enter NEWTOWN 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. When you are satisfied
with 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 Add
Network Element from the drop-down menu. Select the DXR 103 Protected
Terminal from the Add Network Element window. The icon for the terminal will
appear in the Explorer Tree pane, followed by the default name. Click on the default
name, and type in NEWTOWN-SEATOWN, then press <Enter>.
Step 8: Select the NEWTOWN-SEATOWN terminal in the Explorer Pane, then go through
each of the available tabbed pages in the Configuration workspace. Either accept the
default settings, or enter the values you require. Refer to the section in this manual
that describes the terminal for details. Select the Commit button from the DXR NET
Step 9: Right-click on the NEWTOWN site icon in the Explorer Tree pane, then select Add
name, and type in NEWTOWN-OLDTOWN, then press <Enter>.
Step 10: Select the NEWTOWN-OLDTOWN terminal in the Explorer Pane, then go through
default settings, or enter the values you require. Refer to the section in this manual
that describes the terminal for details. Select the Commit button from the DXR NET
Step 11: Right-click on the OLDTOWN site icon in the Explorer Tree pane, then select Add
name, and type in OLDTOWN-NEWTOWN, then press <Enter>.

MARCH 2000
IOM-NMS-1/05C
Step 12: Select the OLDTOWN-NEWTOWN terminal in the Explorer Pane, then go through
default settings, or enter the values you require. As the NEWTON-OLDTOWN
terminal already exists in the blueprint, you should select it as the remote terminal
for OLDTOWN-NEWTOWN. Refer to the section in this manual that describes the
terminal for details. Select the Commit button from the DXR NET toolbar to save
any changes you make to the blueprint.
Step 13: Right-click on the SEATOWN site icon in the Explorer Tree pane, then select Add
name, and type in SEATOWN-NEWTOWN, then press <Enter>.
Step 14: Select the SEATOWN-NEWTOWN terminal in the Explorer Pane, then go through
default settings, or enter the values you require. As the NEWTON-SEATOWN
terminal already exists in the blueprint, you should select it as the remote terminal
for SEATOWN-NEWTOWN. Refer to the section in this manual that describes the
terminal for details. Select the Commit button from the DXR NET toolbar to save
any changes you make to the blueprint.
Step 15: You have now completed the blueprint. Select File from the menu bar, and then
Save 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 the
network as described in Connecting to the Network with a Network Blueprint.
%TGCVKPIC0GVYQTM$NWGRTKPVHQTC0/50GVYQTM
Before you can create a blueprint for a NMS network, you must have carried out the
following 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
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.

MARCH 2000
IOM-NMS-1/05C
&:40/50GVYQTM+2#FFTGUUKPI4GSWKTGOGPVU
For a NMS network to function, the NMS elements must be able to communicate with one
another. In DXR NMS networks, NMS element communication is carried out using IP
(Internet Protocol) Addressing. Each message sent over the network will contain the
Destination IP address it is to be sent to. A NMS element looks at the Destination IP address
of the messages it receives to determine if they match the element IP address. If not, the
element sends the message on to its destination, via the port associated with the message
Destination IP address. Therefore, 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 can communicate with, and the ports it uses to communicate with
them, are set in the Routing Table associated with the NMS element.
+2#FFTGUUGU
An IP address is divided into four eight-digit binary numbers known as octets. For
convenience, the numbers in the address are normally displayed as decimals, eg
255.255.255.255, not 11111111.11111111.11111111.11111111. However, you should
remember that the decimals are representations of binary numbers, and any operations carried
out on the addresses are binary operations. This is especially important when the topic of IP
masking is considered.
/CUM+2#FFTGUUGU
A Mask IP Address is used to determine which of the octets in an IP address are required by
an NMS element to determine the port to a Destination IP Address. Like the Destination IP
address, the Mask IP Address is divided into four octets, however, mask octets usually only
take the values 255 or 0. When the NMS element looks at a message IP address, it compares it
with the Destination IP Addresses associated with the element ports to determine the port to
which the message should be routed. If an octet is set to 0, the corresponding octet of the
Destination IP Address will be ignored in the comparison. If the mask octet is set to 255, the
corresponding octet of the Destination IP Address is used in the comparison. This is best
shown by an example.
Example
The 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 associated
Destination IP Address. For Port 1:

MARCH 2000
IOM-NMS-1/05C
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
When the NMS element matches the octets of the IP Address message with the results of IP
masking, 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 octet
of 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 the
corresponding 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 corresponding
octet 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 be
routed via Port 1, and Message 3 can only be routed via Port 3.
&:40/5'NGOGPV+2#FFTGUUKPI
DXR NMS elements can take IP addresses in the range 10.0.0.1 to 10.255.255.255. The first
octet, 10, is standard for all DXR IP addresses. You can set all the three other octets from to
any value between 0 to 255 inclusive. The second octet is used to set the sub-net address of
the NMS element. This can be used to divide the NMS elements on the network into smaller
sub-nets. The third octet identifies the particular NMS element on the sub-net, and the fourth
octet is used to identify the connections (ports) on the element used to connect to the
addresses.

MARCH 2000
IOM-NMS-1/05C
Note: You should not use 0 as an octet value, except as the last entry in the IP address in a
NMS element routing table, or as part of a Mask IP Address and its corresponding
octet in the Destination IP Address.
0/5'NGOGPV2QTVU
The NMS element ports are the actual connections by which the element communicates with
the outside world. Each IP address needs to be associated with the port that actually connects
the 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.
A SMA can use the following ports:
V.24. 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 ports (AUX A to AUX D). Used to make any connections made via the DXR 700
radio links controlled by the SMA.
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 the
polarity of the physical connectors on the SMA.
Note 2: The V.24 port is designated the Setup port on the SMA front panel.
7UKPI5WDPGVU
Sub-nets are used to make the DXR NMS network more manageable by dividing the NMS
elements 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 stated, the second octet in the IP address is used to set the sub-net address of the
NMS element. By using an IP mask, you can set up a NMS element to route all messages with
the same second octet via a specific port. Therefore, an element only needs one IP address to
communicate with the elements of another sub-net, instead of the specific IP addresses of all
the elements.

MARCH 2000
IOM-NMS-1/05C
Since a NMS element can communicate with all the NMS elements in another sub-net using a
general address for the sub-net, the only specific IP addresses it needs to know are those
belonging to the elements in its own sub-net. This means that when new NMS elements are
added 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-net
address to communicate with the sub-net members, and any new members will have the same
sub-net address as the existing members.
Sub-net Design Guidelines

The only major restriction on the sub-net design is that each NMS element can only hold up to
fifty IP addresses, ie, the sum of the number of NMS elements in an sub-net and the number
of sub-nets it connects to cannot exceed fifty. However, the following guidelines are of use:
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
A quick method for determining the number and size of any sub-nets on your network is to
calculate 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 then
divide the NMS elements between the sub-nets, trying to keep the same number of elements in
each sub-net. For example, for a network with 17 elements, the number of sub-nets would be
four (root 17 = 4.123), and you would have three sub-nets with four NMS elements, and one
with five.
%TGCVKPIVJG$NWGRTKPV
You can use DXR NET to create a blueprint for a NMS network using the following
procedure:
Note 1: Unless your network is very simple, we advise you to use the Network Maintenance
Tool.
Note 2: We advise you create the blueprint while working offline.
Procedure
top of the column. Click on Network, type in the name you have given to the
network, then press <Enter>.
Step 4: To add a site to the blueprint, right-click on the Network icon in the Explorer Tree
pane, then select Add Site from the drop-down menu. The Site icon will appear in
the pane, followed by Site n, where n relates to the number of sites already in
the blueprint.

MARCH 2000
IOM-NMS-1/05C
Site Information page appears in the workspace. Enter the name you have given the
site 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. When
you 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 Tree
pane, then select Add Network Element from the drop-down menu. Select the type
of element you want to add to the site from the Add Network Element window as
described in Adding Network Elements. The icon for the terminal will appear in the
Explorer Tree pane, followed by the default name. Click on the default name, type
in 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 Network
Element from the drop-down menu. In the Import Configuration window, select the
previously saved configuration file for the terminal, then click Open. The icon for
the element will appear listed under the site in the Explorer Tree pane, followed by
the file name. If you want to give the terminal a new name, click on the current
name, type in the name of your choice, then press <Enter>.
Step 9: Select the element you have just added or imported, then go through each of the
describes the element for details. For NMS elements, you should set the IP address
of the element in the IP Address Table, and also set up the element routing table.
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 Save
from the drop-down menu to save the blueprint for future reference.
'ZCORNG0/5$NWGRTKPV
In this example, you have set-up a simple network servicing a set of coast guard stations. The
current requirement is for a single link between the regional control station and the branch
station in the local port, and a single link between the regional control station and a
watchtower at the local beach. It is planned to install more such towers in the immediate
future, so you have decided to use a DXR 700 under SMA control for this link, making it
easier to add links later. The link to the port is well established and unlikely to change, so that
can be covered by a DXR 124 link. You want to be able to monitor the whole network while
attached to any NMS element, so both the DXR 124 terminals have an NMS board, and there
is an NMS connection going between one of the SMA and one of the DXR 124 terminals.

MARCH 2000
IOM-NMS-1/05C
Creating the NMS Element IP Addresses

The first part of designing the network blueprint is to create IP addresses for the NMS
elements. 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 from
the link under SMA control.
There are two SMAs and two DXR 124 terminals, so the total number of NMS elements is
four. Using the rule given previously gives two sub-nets of two NMS elements. You put the
SMAs and the DXR 700 terminals they control in one sub-net, and the two DXR 124
terminals in the other. You 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 the
DXR 124 terminal IP addresses will begin with 10.2. You decide to designate the SMA
connected 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 as
Element 2. The last octet of the addresses identifies the port the NMS element uses to
communicate with an attached PC, by convention, this is usually set to 1.
You now have created IP addresses for all the NMS elements on the network, and can now
create the routing table entries.
Creating the Routing Table Entries

The routing table for each NMS element sets up the ports the element uses to communicate
with 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 elements own IP address, and the IP addresses it uses to
communicate with the other NMS elements on the network.
Consider the SMA whose IP address is 10.1.1.1. It is connected to any attached PC by its
V.24 (Setup) port. It is also connected to the other SMA via a DXR 700 radio link on its AUX
A port, and to the DXR 124 terminals via its NMS In port. The IP address of the other SMA is
10.1.2.1, and the addresses of the DXR 124 terminals are 10.2.1.1. and 10.2.2.1. respectively.
Because there is only 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 is required 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
The routing table for the second SMA is:

10.1.2.0. 255.255.255.0. V.24

MARCH 2000
IOM-NMS-1/05C
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 the
10.2.0.0. address is through AUX A.
The routing table for the DXR 124 connected to the first SMA 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
The routing table for the second DXR 124 is:

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 DXR 124 terminal sees the SMAs via the radio link, so the connection to the
10.1.0.0. address is through the Radio port.
NMS Network Naming Conventions

You now have to decide what names you are going to use in the blueprint. Like in the
non-NMS network, you should try and select names that are meaningful to you and to anyone
else who may have cause to use the blueprint. At the same time, the names should be short
enough to be viewed without difficulty in the Explorer Tree pane. The network and site names
are similar to the non-NMS network, but the SMA and NMS boards have a slightly different
convention, and the DXR 700 terminal names now contain 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 to
easily identify the blueprint file. As the network is to service three coastguard stations, you
decide 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.
You can now select the NMS element names. The most useful information these can contain
is the site the element is at, the type of element, and the IP address of the element. You can
include these details in the names, site first, then element type, followed by IP address. The
site name can be shortened to be viewed in the Explorer Pane, but you should ensure that any
shortened names retain enough detail to be clearly identified by anyone who will use the
blueprint. In this case, the names are:
TOWN SMA 10.1.1.1.

BEACH SMA 10.1.2.1.
TOWN NMS 10.2.1.1

MARCH 2000
IOM-NMS-1/05C
PORT NMS 10.2.2.1.

You can now select the terminal names. The most useful information these can contain is
which link the terminal belongs to, and which end of the link it is at. Also, the names for the
terminals under SMA control should indicate which AUX port they are attached to on the
SMA. You can achieve this by including the names of the local and remote sites in the
terminal name, with 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 terminal
at the TOWN site could be named TOWN-PORT, or TWN-PRT. You should ensure that any
shortened names retain enough detail to be clearly identified by anyone who will use the
blueprint. The terminals under SMA control end in a letter, which designates the AUX port
they are connected to. The terminal names are therefore:
TOWN-BEACH-A
BEACH-TOWN-A
TOWN-PORT
PORT-TOWN
You can now begin to create the blueprint in DXR NET.
Creating the Blueprint

top 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 Site
from the drop-down menu. The Site icon will appear in the pane, followed by Site
n, where n relates to the number of sites already in the blueprint.
Site Information page appears in the workspace. Enter TOWN 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. When you are satisfied
with 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 Add
Network Element from the drop-down menu. Select an SMA from the Add Network
Element 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 SMA
10.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 the
describes the SMA for details. Select the Commit button from the DXR NET toolbar
to save any changes you make to the blueprint.

MARCH 2000
IOM-NMS-1/05C
Step 9: Right-click on the TOWN SMA 10.1.1.1. icon in the Explorer Pane, then select Add
Network Element from the drop-down menu. Select a DXR 770 from the Add
Network Element window. The icon for the DXR 770 will appear in the Explorer
Tree pane, followed by the default name. Click on the default name, and type in
TOWN-BEACH, then press <Enter>.
Step 10: Select TOWN-BEACH icon in the Explorer Pane, then go through each of the
Step 11: Right-click on the TOWN site icon in the Explorer Tree pane, then select Add
Network Element from the drop-down menu. Select the DXR 124 Unprotected
Terminal from the Add Network Element window. Ensure the NMS Option check
box is selected in the window. The icon for the terminal will appear in the Explorer
TOWN-PORT, then press <Enter>.
Step 12: Select the TOWN-PORT terminal in the Explorer Pane, then go through each of the
Step 13: Double click the TOWN-PORT terminal in the Explorer Pane to display the NMS
board icon, then go through each of the available tabbed pages in the Configuration
workspace. Either accept the default settings, or enter the values you require. Refer
to the section in this manual that describes the NMS board for details. Select the
Commit button from the DXR 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 Add
Network Element from the drop-down menu. Select the DXR 124 Unprotected
Terminal from the Add Network Element window. Ensure the NMS Option check
box is selected in the window. The icon for the terminal will appear in the Explorer
PORT-TOWN, then press <Enter>.
Step 15: Select the PORT-TOWN terminal in the Explorer Pane, then go through each of the
settings, or enter the values you require. As the TOWN-PORT terminal already
exists in the blueprint, you should select it as the remote terminal for PORT-TOWN.
Refer to the section in this manual that describes the terminal for details. Select the
blueprint.
Step 16: Double click the PORT-TOWN terminal in the Explorer Pane to display the NMS
board icon, then go through each of the available tabbed pages in the Configuration
workspace. Either accept the default settings, or enter the values you require. Refer
to the section in this manual that describes the NMS board for details. Select the
blueprint.
MARCH 2000
IOM-NMS-1/05C
Step 17: Right-click on the BEACH site icon in the Explorer Tree. Select an SMA from the
Add Network Element window. The icon for the SMA will appear in the Explorer
BEACH SMA 10.1.2.1., then press <Enter>.
Step 18: Select BEACH SMA 10.1.2.1. icon in the Explorer Pane, then go through each of
the available tabbed pages in the Configuration workspace. Either accept the default
describes the SMA for details. Select the Commit button from the DXR 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
Add Network Element from the drop-down menu. Select a DXR 770 from the Add
Network Element window. The icon for the DXR 770 will appear in the Explorer
BEACH-TOWN, then press <Enter>.
Step 20: Select BEACH-TOWN icon in the Explorer Pane, then go through each of the
settings, or enter the values you require. As the TOWN-BEACH terminal already
exists in the blueprint, you should select it as the remote terminal for BEACH-
TOWN. Refer to the section in this manual that describes the terminal for details.
Select the Commit button from the DXR NET toolbar to save any changes you make
to the blueprint.
Step 21: Select IP Address Table from the Configuration menu, and enter the IP addresses for
all the NMS elements in the network.
Step 22: You have now completed the blueprint. Select File from the menu bar, and then
Save 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 the
network as described in Connecting to the Network with a Network Blueprint.
9QTMKPIYKVJC&:40GVYQTM
Although you can use DXR NET to design a network blueprint while your PC is offline, you
will need to connect your PC to a DXR 100, a DXR 700 or a SMA to view or modify the
configuration data of an existing network.
.GXGNUQH#EEGUU
Your ability to access a site or network element on the network depends on. three things:
whether you are using the Local Maintenance Tool or the Network Maintenance Tool
the type of network element your PC is connected to
for remote elements (ie, elements accessed via a radio link), whether the radio link is
operational

MARCH 2000
IOM-NMS-1/05C
Note: The icon for a site or element that cannot currently be accessed is shown
greyed-out in the tree view.
Local Maintenance Tool Access

When you are using the Local Maintenance Tool (LMT), your access to the network is limited
as follows:
when your PC is connected to a terminal (DXR 100 or DXR 700), you can only access
this link (ie, the local and remote terminals)
when your PC is connected to an SMA, you can access this local SMA, any links under
the control of this SMA, and any SMA connected to a terminal at the remote end of one of
these links. However, your access to any remote SMA is restricted to details relating to
the remote terminal connecting the remote SMA to the link.
Note: Each SMA can control up to four links.
Network Maintenance Tool Access

Using the Network Maintenance Tool (NMT), your PC can be connected to either a DXR 100
(with or without a NMS board), a DXR 700, or a SMA:
When the connection is to a DXR 100 without a NMS board, or a DXR 700, you will be
able to access 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 able
to 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 any
link when the link is operational.
6GTOKPCN%QPPGEVKQPU
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 700
under SMA control. You should use a NMS connection to the SMA instead.
Terminal Connection to a DXR 700

To make a terminal connection to your PC to a DXR 700, connect the supplied cable to
between the selected COM port on your PC and the V.24 connector on the DXR 700 PMA.
V24 Connector
Figure 27: DXR 700 PMA Front Panel Layout - location of connector V.24

MARCH 2000
IOM-NMS-1/05C
Terminal Connection to a DXR 100 (without NMS board)

To make a terminal connection to your PC to a DXR 100 without NMS option, connect the
supplied cable to between the selected COM port on your PC and the V.24 connector on the
front panel of the DXR 100.
V.24 Connector
Figure 28: DXR 100 Front Panel Layout - location of connector V.24
0/5%QPPGEVKQPU
NMS connections are used connect to a SMA, or DXR 100 with NMS option.
Note: Your PC must have Windows Dial-Up Networking enabled for NMS
connections. Refer to Section 3 for details.
NMS Connection to a SMA

NMS connections behave like a modem connection made 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.
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 Setup
connector on the SMA.
Setup Connector
Figure 29: SMA Front Panel Layout - location of Setup connector

The procedure for modem connections is the same as for the direct NMS connection, except
that you select the modem driver instead of the NMS connection driver. The modem at the
SMA end of the connection should be attached to the SMA Setup port. Consult the
instructions that were supplied with your modem for further details.

MARCH 2000
IOM-NMS-1/05C
Note: Connections via a modem are slower than direct connections.
NMS Connection to DXR 100 with NMS board

These 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 the DXR
100
for a connection via a telephone network, the modem at the DXR 100 end is connected to
the V.24 port on the DXR 100
'VJGTPGV%QPPGEVKQP
Ethernet connections are used connect to a SMA.
Note: The LMT does not support Ethernet connections.
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
you must have set the IP address of the SMA or NMS board
the UDP port must be set to 161
Note: The UDP port should only be changed by accredited Digital Microwave Corporation
representatives, or under direct instructions from Digital Microwave Corporation.
A successful Ethernet connection is indicated by the network icon in the lower right-hand
corner of the DXR NET GUI.
5GNGEVKPIVJG&:40'6%QPPGEVKQP6[RG1P;QWT2%
You can choose three types of DXR NET interface:
Terminal Connection Used for direct connection between the PC and a DXR 700, or a
DXR 100 without the NMS option
NMS Connection Used for a direct or modem connection to a SMA or a DXR 100 with
NMS option
Ethernet Used for connection to a SMA over an Ethernet LAN
SELECTING THE CONNECTION. You must select the right type of connection for the
network element you are trying to connect to. If you select the wrong type, DXR NET will
not be able to connect to the network, and will tell you it cannot find a valid network
element.
Procedure
To select DXR NET connection type , proceed as follows:
Note: DXR NET will not allow you to select the connection type while you are connected
to a DXR network.
MARCH 2000
IOM-NMS-1/05C
Step 1: Run DXR NET.
Step 2: Select the Communication Setup option from the Tools menu.
Step 3: To connect to a DXR 700, or a DXR 100 without NMS board, select the Terminal
Connection 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 Connection
button. If required, you can then select the driver (NMS connection or modem
driver) that DXR NET uses in the Options section. As a connection via a dial-up
modem will be slower, we advise you select the Dial-up Modem Delay check box if
you are using a modem. This will increase the time DXR NET wait for a response
before deciding the connection has failed.
Step 5: To connect to a SMA via a LAN (directly, or via a router), select the Ethernet
button.
Step 6: If you wish to make the selected interface the default setting, click the Save Settings
button.
Step 7: Click the OK button to change the interface to the selected interface.
DXR NET will now use the connection type you have selected.
%QPPGEVKPIVQVJG4CFKQ0GVYQTMYKVJC$NWGRTKPV
To connect DXR NET to the radio network with a blueprint loaded, first ensure you are using
the 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 new
network element, refer to the section in this manual that details the element.
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. This
can leave the element and any associated link(s) in an undesired state, with the element
software not reflecting the correct settings for the link. You will then need to set the correct
values in DXR NET and re-send them to the element. For these reasons, we recommend that
before you start making changes you save the current element configuration, and that you
have a hard copy of the desired settings available.
WRITING CONFIGURATION CHANGES TO A NETWORK ELEMENT. Whenever you

write configuration changes and data to a terminal, there is a momentary loss of traffic on
the link. We advise therefore that you carry out any changes to the configuration when the
link is 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 to
the 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 that
could impact communication with the remote terminal.

MARCH 2000
IOM-NMS-1/05C
Digital Microwave Corporation advises that when checking or modifying the data, you have
hard copy of the expected values available to refer to before beginning the procedure.
Digital Microwave Corporation advises that you save the configuration data of all your
terminals after initial setup and after any changes are made.
Note 1: We advise that if there are significant changes to the configuration data, these
should be done by loading a new file created offline, rather than making the changes
manually.
Note 2: If you change any parameters in a workspace tabbed-page, you must select the
Commit button from the toolbar before leaving the page, otherwise the changes will
not take effect. You will be prompted to select the button if you try to leave a
changed page without using the button.
Note 3: In the Explorer Window, the icon for the terminal you are connected to will show a
red plug symbol.
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 are
connected to into DXR NET.
Step 4: Select the Connect button from the DXR NET toolbar. When the connection is
successfully completed, the icon for the network element you are connected to will
have a plug symbol in the Explorer Pane. You can now use the Configuration,
Commissioning and Maintenance Workspace functions with any element you can
access. Any elements that you cannot access will be shown greyed-out in the
blueprint.
Step 5: When you are finished using the functions, click on the Disconnect button in the
DXR NET toolbar, then click on File in the menu bar, and select Exit from the File
menu.
%QPPGEVKPIVQC4CFKQ0GVYQTMYKVJQWVC$NWGRTKPV
You can use the Autodiscovery feature to automatically create a blueprint for the link you are
connected to in the Explorer Pane.
Note 1: The blueprint created by the Autodiscovery feature will only contain remote
elements, ie, the elements at the other end of the link, if the link is operational.
Note 2: The Autodiscovery feature cannot be used if you are connected to the network via
Ethernet.

MARCH 2000
IOM-NMS-1/05C
To use the Autodiscovery feature, first ensure you are using the right type of connection for
the element you are connecting to, then proceed as follows:
before you start making changes you save the current element configuration, and that you
WRITING CONFIGURATION CHANGES TO A TERMINAL. Whenever you write

configuration changes and data to a terminal, there is a momentary loss of traffic on the
link. We advise therefore that you carry out any changes to the configuration when the link
is either out of service, or at times when link traffic is at a minimum.
Note 1: We advise that if there are significant changes to the configuration data, these
should be done by loading a new file created offline, rather than making the changes
manually.
Note 2: If you change any parameters in a workspace tabbed-page, you must select the
Commit button from the toolbar before leaving the page, otherwise the changes will
not take effect. You will be prompted to select the button if you try to leave a
Note 3: In the Explorer Window, the icon for the terminal you are connected to will show a
red plug symbol.
Procedure
Step 3: Select the Connect button from the DXR NET toolbar. The Autodiscovery feature
will create a blueprint of the link you are connected to, and display this in the
Explorer Tree pane. You can now use the Configuration, Commissioning and
Maintenance Workspace functions with any element you can see in the blueprint.

MARCH 2000
IOM-NMS-1/05C
Step 4: When you are finished using the functions, click on the Disconnect button in the
DXR NET toolbar, then click on File in the menu bar, and select Exit from the File
menu.
#FFKVKQPCN&:40'6(WPEVKQPU
Apart from the functions in the Configuration, Commissioning and Maintenance Workspaces,
you can also use DXR NET LMT and NMT to:
run test script files

load new software to terminals and NMS elements
Note: Refer to Section 2 for a description of the functions available (the tabbed pages) in
the Configuration, Commissioning and Maintenance Workspaces, and to the section
in this manual that describes the network element for how to use the workspaces
with the specific element.
4WPPKPI6GUV5ETKRV(KNGU
DXR NET allows you to load and run test script files to carry out test procedures.
SCRIPT FILES. Script files should only be used under the supervision of accredited DMC
service personnel.
The procedure for running a script file is as follows:
Note: If the file does not designate the network element it is to be run on, it will be run on
the element selected in the Explorer Tree.
Step 1: Run DXR NET from the PC desktop.
Step 2: Select Maintenance from the Workspace Selection box.
Step 3: Select Load Script File from the drop-down Maintenance menu.
Step 4: Select the test script you want to run in the Execute Script File box, then Start.
.QCFKPI5QHVYCTG
DXR NET allows you to load software to network elements.
LOADING SOFTWARE. Software can only be loaded to terminals via a NMS element
(NMS board or SMA.
Loading System Software to DXR NET

Before you can load software to a network element, you must have first loaded the System
Software containing the element software into the DXR NET folder on your PC.
Note: DMC advises that in Step 4 you use the default location for the System Software.
Step 1: Insert the System Software CD into your PC.

MARCH 2000
IOM-NMS-1/05C
Step 2: Use Windows Explorer to find SETUP.EXE on the CD.
Step 3: Click Next in the Welcome screen.
Step 4: If required, change the desired location for the System Software files.
Step 5: Click Next.
Step 6: When the Setup Completed message appears, click Finish.
Deleting Old Software Files on a NMS Element

After you have loaded new software to any network elements, the BIN files that are used to
set the elements up will remain stored in the NMS element. Before you load any new
software, you should delete these files. The procedure is as follows:
Note: You must be connected to the network via a NMS element (a SMA or a NMS
board).
Step 2: Select Maintenance from the Workspace Selection box.
Step 3: Either click on the Connect button on the toolbar to autodiscover the attached
network, or load the network blueprint and then click on the Connect button.
Step 4: Select the File System page in the Maintenance workspace.
Step 5: Select and delete the old BIN files in the File System window.
You can now proceed with loading the new software.
Loading Software to a Network Element

To load software to a network element, proceed as follows:
Note 1: You must be connected to the network via a NMS element (a SMA or a NMS
board).
Note 2: We advise that you load any software to remote elements first (see Note 3).
Note 3: When loading to a terminal, the link will drop for ten minutes while the software is
loaded from the NMS unit to the terminal. Do not try to carry out any other software
loading until after this time has elapsed.
Step 2: Select Configuration from the Workspace Selection box.
Step 3: Either click on the Connect button on the toolbar to autodiscover the attached
network, or load the network blueprint and then click on the Connect button.
Step 4: Select Software Table from the drop-down Configuration menu.

MARCH 2000
IOM-NMS-1/05C
Step 5: Click the ellipsis () button in Software Version Table window to get the folder
containing the System Software.
Step 6: Double click on the Version field in Software Version Table window, select the
version of the element software you wish to load, then click OK.
Step 7: Select Load Software from the drop-down Configuration menu, then Start.
Step 8: When the Complete message appears, click the OK button.
2TQDNGOU7UKPI&:40'6
Problems encountered using DXR NET might include:
The network cannot be accessed

Changes to the configuration are not accepted
2TQDNGOU#EEGUUKPIVJG0GVYQTM
Check that the right type of interface for your connection by selecting Communication
Setup option from the Tool menu in the menu bar. If you have selected the wrong
interface, change it to the correct one (see Selecting DXR NET interface on your PC in the
Installing DXR NET section)
Note: The LMT does not support the Ethernet connection.
If you are using an Ethernet connection, check that you are using the correct IP address
for the element you are trying to connect to, and that the UDP port address is set to 161
Check that the cable is connected to the correct COM port of your PC by selecting
Communication 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
2TQDNGOU%JCPIKPIVJG%QPHKIWTCVKQPQHC0GVYQTM'NGOGPV
Check the original setup details to ensure that you are not trying to load changes that cannot
be supported by your variant of the element.
&:40'69CTPKPI/GUUCIGU
The most common warning messages you will encounter using DXR NET, and there likeliest
causes, 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 causes
are:

MARCH 2000
IOM-NMS-1/05C
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 has
caused it to drop its NMS connection (eg. resetting the element IP address)
you are trying to connect using the wrong dial-up adaptor
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 causes
are:
there is something wrong with the connection between your PC and the network
you are using the wrong type of connection for the element you are connected to
An IP compliant device could not be found

This usually indicates problems trying to connect to a DXR NMS network with the blueprint
loaded 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 the
address given in the blueprint
%QPVCEVKPI&KIKVCN/KETQYCXG%QTRQTCVKQP
Selecting Help and then Customer Support will display the methods you can use to contact the
product support staff at Digital Microwave Corporation.

MARCH 2000
IOM-NMS-1/05C
Using DXR NET Element Manager
7UKPI&:40'6'NGOGPV/CPCIGT
)GPGTCN
The DXR NET Element Manager (EM) is used to monitor the performance of DXR radio
networks. Each NMS element (SMA or NMS board) maintains its own event log. The EM
uses polling to access each NMS element in turn, and reads the event details from the
element. It then allows you to view the events using display windows, or create notifications
(either audio, or pop-up windows).
Note: DXR NET EM only works with the DXR radios and associated equipment supplied
by Digital Microwave Corporation.
You can apply filtering to both the windows and the notifications, so that you can display all
events, high impact events, uncleared events, unacknowledged events, events for selected
resources, or events occurring within a certain date or time span. Refer to EM Example in
this section for details.
5QHVYCTGCPF*CTFYCTG-G[U
To enable the EM functions with DXR NET, you must have both the required software and
hardware keys. The keys can be easily moved between PC, enabling the EM to be enabled on
any PC running DXR NET. The software key is related to the serial number on the hardware
key, and also contains the Maximum Network Size Licence. This determines the number of
the network elements you can monitor at any one time.
/CZKOWO0GVYQTM5K\G.KEGPEG
The number of the network elements you can monitor with the EM at any one time is
determined by the Maximum Network Size Licence (MNSL). This is included in the code of
the software key that enables the EM functions. The MNSL limits the number of NMS
elements that can be activated by the EM, and hence the total number of network elements
that can be monitored. The MNSL is available in sizes of 10, 20, 50, 100 and 200. A DXR
100 NMS board counts as one element, a SMA counts as two (each SMA can support up to
four DXR terminals, so two is taken as the average).
'/2QNNKPI
The EM polls each monitored NMS element (SMA or NMS board) to obtain their event logs.
It then uses these logs to produce its own log of all the events on the monitored areas of the
network. The polling frequency depends on the size of the network and the number of events
that occur on it. All events are displayed in the order their elements are polled by the EM, not
the order in which they occur. Because of this, events may not be displayed immediately in
the EM event log.

MARCH 2000
IOM-NMS-1/05C
9KPFQYUCPF0QVKHKECVKQPU
The EM can display events in up to 16 Event Browser windows. It can also be set to inform
(notify) you when events occur, using either audio or pop-up windows.
Note: You can choose the events which trigger pop-up windows using the pop-up
notification filters.
4GSWKTGOGPVUHQT'/
The EM functions are accessed through the Event Monitoring item in the DXR NET menu bar.
This only appears when DXR NET detects that your PC has both the valid hardware and
software keys. Both keys are supplied when you order DXR NET with the EM option.
Note: Your current licence keys will be supported by later versions of the software. These
will be available from your Digital Microwave Corporation agent, or can be
downloaded from the Digital Microwave Corporation web site.
The keys enable the EM as follows:
the hardware key converts the DXR NET LMT to the NMT
the software key enables you to access the EM functions, and also sets the size of the
network you can monitor
Note: The network size can be increased by ordering a new software key with a larger
MNSL from Digital Microwave Corporation.
*CTFYCTG-G[
When DXR NET starts, it checks for the licence keys. If the hardware key is present, DXR NET
starts up in the NMT operation.
5QHVYCTG-G[
When DXR NET starts, it checks for the licence keys. If the software key is present as well as
the matching hardware key, DXR NET starts up in the NMT operation, and the Event
Monitoring item appears in the menu bar. You can then use this item to select EM functions.
The software key is loaded onto your computer hard-drive. It not only gives you access to EM
functions, and also governs the maximum number of network elements that you can select for
network wide element monitoring at any one time. This is derived from the Maximum
Network Size License (MNSL). The relationship between the MNSL and the number of NMS
elements (ie, SMA or DXR 100 with NMS boards) that you can use the EM to monitor is
governed by the following rules:
The number of DXR 100s with NMS boards must not exceed the MNSL.
As each SMA typically manages 2 DXR 700 radios in a simple bus topology network, the
number of SMA's will not exceed the MNSL / 2, eg, if the MNSL is 400, the maximum
number of SMA's will be 200.
The following equation defines the maximum numbers of SMA's and DXR 100 radios with
NMS boards that will be supported by the network wide event monitoring :

MARCH 2000
IOM-NMS-1/05C
DXR_100_NMS + (SMA * 2) <= MNSL
Note: If you require, you can apply to Digital Microwave Corporation to increase the
number of elements you can monitor.
'XGPV/QPKVQTKPI
When you select the Event Monitoring item in the DXR NET menu bar, a drop-down menu is
displayed with the following items:
Enable Network Event Monitoring

Configuration
Event Browser
Event Notification
Figure 30: Event Monitoring Drop-down Menu

The EM needs to know the IP addresses for all the NMS elements on the network. You must
therefore load the network blueprint, with the correct IP addresses of all the NMS elements,
into DXR NET before connecting to the network.
'PCDNG0GVYQTM'XGPV/QPKVQTKPI
You select Enable Event Monitoring to enable and disable the EM.

MARCH 2000
IOM-NMS-1/05C
%QPHKIWTCVKQP
You select this item to display the Network Wide Event Monitoring Configuration window.
You use this window to select the NMS elements, and any other network elements under their
control, that the EM will monitor.
Figure 31: Network Wide Alarm Monitoring Configuration Window

The window has two panes, Unmonitored and Monitored, and two arrowed buttons (>> and
<<). The panes contain all the NMS elements in the active network blueprint. You can move
an element between the panes by selecting the element, and then clicking on the appropriate
arrow button.
Note: You must ensure that the total number of network elements to be monitored does not
exceed the MNSL. Refer to Requirements for EM in this section for details on
how the MNSL affects the number of elements you can monitor.
'XGPV$TQYUGT
When you select the Event Browser item, you open an Event Browser window. You can have
up to 16 Event Browser windows open at any one time. You can select which events are
displayed in a window, acknowledge events, and remove events from the window using the
Event Browser Window functions. These are obtained from the menu displayed when you
right-click within the window.

MARCH 2000
IOM-NMS-1/05C
Figure 32: Event Browser Window

Each row in a window refers to a specific event detected by the EM. The severity and current
status of the event is indicated by the coloured symbol at the start of the row. The meanings of
the symbols are as follows:
Green square cleared, ie, the alarm is no longer active

Cyan triangle warning, ie, a condition has occurred with the potential to cause a fault
affecting the service.
Red triangle with exclamation mark critical, ie, a condition has occurred that affects
user traffic, and requires immediate corrective action
Orange triangle with exclamation mark major, ie, a condition has occurred that affects
user traffic, and requires corrective action
Yellow triangle with exclamation mark minor, ie, a condition has occurred that does not
affect user traffic, but requires corrective action to prevent a more serious fault developing
Note: If you have acknowledged an alarm, the symbol will have a tick superimposed
over it. See Event Browser, Window Functions, Acknowledge for details.
The rows list further information on their event under the following four columns:
Object
Time
Severity
Event

MARCH 2000
IOM-NMS-1/05C
Note: Some of the entries in the columns will be longer than the column width. To view
these entries, use your mouse to adjust the column width by dragging the right-hand
side of the column heading.
Object
The Object column contains the location where the event has been raised. For example,
BEACH SMA 10.4.1.1, SMA indicates the alarm is being raised on the SMA named BEACH
SMA 10.4.1.1., TOWN-PORT-NMS 10.2.1.1, Unprotected DXR 100 indicates the alarm is
being raised on the unprotected DXR 100 that contains the NMS board TOWN-PORT-NMS
10.2.1.1.
Note: The name of the NMS element will be the one assigned to it in the blueprint.
Time
The Time column contains the date and time that the alarm became active, as read directly
from the network element Event Log. Because the EM uses polling to read the alarm details
from the elements it monitors, the alarms are listed in the order in which they were read from
their elements by the EM, not the order in which they occurred.
Note: If the Date and Time have not been set in the NMS elements, the Time column lists
the time the event was detected by the EM. These times will be followed by an
asterisk to distinguish them from the times from the actual elements.
Severity
The Severity column indicates the severity of the event, and the current state of the event. The
severity can be one of:
Warning, ie, a condition has occurred with the potential to cause a fault affecting the
service
Critical, ie, a condition that affects user traffic has occurred and requires immediate
corrective action
Major, ie, a condition that affects user traffic has occurred and requires corrective action
Minor, ie, a condition that does not affects user traffic has occurred and requires
corrective action to prevent a more serious fault developing
If the column only contains the severity, the event is for a condition still present on the
network. If the severity is followed by (DOWN), the event is for a condition that is no longer
present on the network. If the severity is followed by (CLEARED), the event is a clearing
event, ie an event raised when a condition that had been present on the network is cleared.
This is classed as a separate event from the raising of the initial event.
Event
The Event column contains a description of the alarm.
'XGPV$TQYUGT9KPFQY(WPEVKQPU
When you right-click on an Event Browser window, you display the menu containing the
functions you can apply to the entries in the window. You can then select the following
functions:

MARCH 2000
IOM-NMS-1/05C
Acknowledge
Details
Delete
Purge Acknowledge
Purge Cleared
Filter Settings
Acknowledge
You use the Acknowledge function to add a tick to the symbol of selected event. You would
do this to indicate that you have already looked at the event.
Note: You can also acknowledge an alarm by double-clicking on the symbol.
Figure 33: Event Browser Window Acknowledged Alarms
Details
You use the Details function to obtain more details on the selected event. The details appear
in a separate Details Window.

MARCH 2000
IOM-NMS-1/05C
Figure 34: Details Window
Delete
You use the Delete function to delete selected events from the Event Browser window.
DELETING AN ALARM. You cannot retrieve an event after you have deleted it.
Purge Acknowledge
You apply the Purge Acknowledge function to delete all the events you have acknowledged
from the Event Browser window.
PURGE ACKNOWLEDGE. You cannot retrieve any acknowledged events after they have
been purged.
Purge Cleared
You apply the Purge Cleared function to delete all the cleared events from the Event Browser
window.
PURGE CLEARED. You cannot retrieve any cleared events after they have been purged.
Filter Settings
You use the Filter Settings to select the events in the EM log that are shown in the Event
Browser window.
You can select events on the basis of their:
Severity

MARCH 2000
IOM-NMS-1/05C
Cleared Status
Acknowledgement
Type
Date and Time
Generic
Note: You can select more than one type of filtering at once.
If you select Severity, the Severity Filter window will be displayed. This contains check boxes
for the Critical, Major, Minor and Warning severities, and Activate Severity Filtering. You
select the boxes for the severities you are interested in, and then select the Activate Severity
Filtering box to turn on the filter.
Figure 35: Severity Filter Window

If you select Cleared Status, the Cleared/Raised Filter window will be displayed. This
contains check boxes for Show Active Alarms, Show Cleared Alarms, and Activate
Cleared/Raised Filtering. You would select the boxes for the alarm status you are interested
in, and then select the Activate Cleared/Raised Filtering box to turn on the filter.
Figure 36: Cleared/Raised Filter Window

MARCH 2000
IOM-NMS-1/05C
If you select Acknowledge, the Acknowledge Filter window will be displayed. This contains
check boxes for Show Acknowledged Events, Show Unacknowledged Events, and Activate
Acknowledge Filtering. You would select the boxes to show the events you are interested in,
and then select the Activate Acknowledge Filtering box to turn on the filter.
Figure 37: Acknowledge Filter Window

If you select Date and Time, the Date and Time Filter window will be displayed. You would
input the times or dates you are interested in into the relevant fields. You use the arrow
buttons to select whether you wish to display events before (<<), after (>>), or between (<>)
the input date/time(s), select the Time or Date check box (or both if required), and then select
the Activate Time/Date Filtering box to turn on the filter.
Note: You only need to input dates and times into the second set of fields when you are
interested in events between specific times and dates. When filtering for events
before or after a time or date, you only need to fill the first set of fields.
Figure 38: Date and Time Filter Window

If you select Generic, the Generic Filter window will be displayed. You would use this to
select any alarms containing specific text, eg. the name of a network element. You type the
text into the window, and then select the Activate Generic Filtering box to turn on the filter.

MARCH 2000
IOM-NMS-1/05C
Note: You use the * at the beginning and end of single word, and as a separator when
you are searching for multiple text strings.
Figure 39: Generic Filter Window
Label Browser
You use the Label Browser function to name the Event Browser window. Giving the window
a distinct names is useful when you are using more than one window at once, eg, when you
are using windows with different filter settings. You select Label Browser, and then type the
name you want to give the window into the Label Browser window.
Figure 40: Label Browser Window
New Event Table

You use the New Event Table function when you need to create more Event Browser
windows. A new window is produced each time the function is selected.
Note: You have to set-up any filtering for each window individually, using the right-click
menu.
'XGPV0QVKHKECVKQPU
You select the Event Notifications functions to enable you to keep track of any events while
carrying out other tasks on your PC. You can choose the type of notification you receive when
an event occurs, and also apply filtering to select the events you wish to be notified about.
When you select Event Notifications, the following drop-down menu appears:
MARCH 2000
IOM-NMS-1/05C
Enable Audio Notification

Enable Pop-up Notification
Filter by Severity
Filter by Cleared Status
Filter by Type
Generic Filter
You select the type of notification you receive using Enable Audio Notification and/or Enable
Pop-up Notification.
When you select Enable Audio Notification your PC will emit a signal tone every time a new
event occurs.
When you select Pop-up Notification, a window will appear on the PC desktop every time a
new event occurs. The window will contain a detailed description of the event, including the
network element that has raised the event, the event name, the severity and the date and time
the event was raised.
Figure 41: Pop-up Notification Window

The windows appear cascaded on the desktop, with the window detailing the most recent
event at the front. There can be a maximum of fifteen cascaded windows on the desktop at
any one time. As more events occur, the windows relating to earlier events are deleted to keep
the number of windows to fifteen. You remove windows by selecting their Dismiss button.
You prevent a window from being overwritten by selecting it and moving it away from the
other cascaded windows.
Note: Such a window is still counted among the cascaded windows, so the maximum
number of pop-up windows on display remains fifteen.
The four filter options (Filter by Severity, Filter by Cleared Status, Filter by Type, and
Generic Filter) allow you to select the events that cause pop-up notifications.
Note: These four filters only apply to the pop-up notification windows, not the audio
notification, or the Event Browser windows.
9QTMUVCVKQP4GSWKTGOGPVU
The Workstation Requirements for EM can be divided into the following:
Software
Hardware
MARCH 2000
IOM-NMS-1/05C
Software
To run DXR NET EM, a PC must have Microsoft Windows NT 4.0 (or later).
Note: The EM will run on earlier versions of windows, but there is no support for any of
its functions.
Hardware
The minimum hardware configuration for DXR NET EM is as follows:
Note: The hardware requirements listed below are for the tool only, and do not take into
account any requirements of any other software. You should check that your PC has
the capacity to operate both the required tool, and any other required software
before installing the tool.

128 MB RAM
3.5 floppy drive
Ethernet port
2 or 3-button Mouse
101-key US keyboard
2TGRCTKPI[QWT2%VQWUG'/
After ensuring your PC meets the criteria specified in the Workstation Requirements section,
you must carry out the following actions:
fit the hardware licence key to your PC

load the software key
use DXR NET to connect to the network
+PUGTVKPIVJG*CTFYCTG-G[
The hardware key:
must be installed before you start up DXR NET

must match the software key
must not be removed while DXR NET is running
You install the hardware key into the parallel port on your PC.
Note: The parallel port on your PC is the port you would normally use to attach to your
printer.

MARCH 2000
IOM-NMS-1/05C
.QCFKPIVJG5QHVYCTG-G[
The software key must match the hardware key in the PC parallel port. You can load the
software key either from a registry file (extension .REG), or manually. The registry file name
contains the hardware key serial number, and the MNSL size.
Loading the Software Key from a Registry File

To load the software key from a registry file, proceed as follows:
Note: The registry file can be supplied either on disk, or as an e-mail attachment.
Step 3: Select Tools from the DXR NET menu bar.
Step 4: Select Upgrade NMSL from the drop-down Tools menu. The NMSL Software Key
Change window will appear.
Step 5: If required, select the Retrieve software key from registry radio button, then select
Run REG.file button to load the file.
Step 6: Use the displayed window to select the registry file, then select the Open button.
Step 7: Select the Retrieve software key from registry radio button, then click OK.
Step 8: A window is now displayed, telling you that you need to close down and restart
DXR NET for the file to be loaded. Select Yes.
When you run DXR NET again, the Event Monitoring item will now be shown in the DXR
NET menu bar.
Note: If you get the NMSL Cleared message, refer to the ReadMe file in the DXR NET
folder for further details.
Loading the Software Key Manually

To load the software key manually, proceed as follows:
Step 3: Select Tools from the DXR NET menu bar.
Step 4: Select Upgrade NMSL from the drop-down Tools menu. The NMSL Software Key
Change window will appear.
Step 5: Select the Manually enter software key radio button.
Step 6: Type the key numbers into each of the fields provided.

MARCH 2000
IOM-NMS-1/05C
Step 7: After entering numbers into all the fields, click the Check button. Lines with errors
will be indicated for re-entering.
Step 8: After you have entered the key correctly, click the OK button.
Step 9: A window is now displayed, telling you that you need to close down and restart
DXR NET for the file to be loaded. Select Yes.
When you run DXR NET again, the Event Monitoring item will now be shown in the DXR
NET menubar.
&:40'60GVYQTM%QPPGEVKQP
To use EM:
you must use select either the NMS or the Ethernet connection for DXR NET. Refer to
Section 4 for details.
You must have the network NMS blueprint loaded with the correct IP addresses of all the
NMS elements you wish to monitor
5GNGEVKPIVJG0/5'NGOGPVUHQTVJG'/
You need to do this every time you monitor the network. You must have the relevant
blueprint, with the correct IP addresses for all the NMS elements, loaded or created in DXR
NET.
Note: NMS elements without the correct addresses will not be listed in the Network Wide
Alarm Monitoring Configuration window.
To select the network elements the EM is to monitor, proceed as follows:
Step 1: Load the network blueprint into DXR NET, and connect to the network containing
the elements you are going to monitor.
Step 2: Select Event Monitoring from the DXR NET menu bar.
Step 3: Select Configure from the drop-down Event Monitoring menu.
Step 4: In the Network Wide Alarm Monitoring Configure window, check the NMS
elements shown in the Unmonitored and Monitored panes.
Step 5: To select a NMS element for monitoring, select the element in the Unmonitored
pane, then click the >> button. The element will appear in the Monitored pane.
Step 6: To remove NMS element from monitoring, select the NMS element in the
Monitored pane, then click the << button. The element will appear in the
Unmonitored pane.
Step 7: When you are satisfied with your selections, close the Network Wide Alarm
Monitoring Configuration window.

MARCH 2000
IOM-NMS-1/05C
7UKPIVJG'/YKVJ'XGPV$TQYUGT9KPFQYU
You can use the Event Browser window(s), to:
create a log of events (alarms) that occur on the network you are monitoring
filter this log to produce listings of the specific types of alarms you are interested in
To use the EM to create and filter Event Browser windows, ensure the required hardware and
software keys are present on your PC, start up DXR NET, and proceed as follows:
Step 1: Load the network blueprint into DXR NET, and then connect to the network
containing the elements you are going to monitor.
Step 2: Select the network elements you wish to monitor, as detailed in Selecting the NMS
Elements for the EM.
Step 3: Start the EM by selecting Enable Network Event Monitoring from the Event
Monitoring menu.
Step 4: Display the first Event Browser window by selecting Event Table from the Event
Monitoring menu.
Step 5: To apply filtering to the window, right-click on the window, select Filter Settings
from the displayed menu, and then enable the required filtering, as detailed in the
following sections.
Step 6: To give the window a name, right-click on the window, select Label Browser from
the displayed menu, and then type in the name.
Step 7: If you wish to display more Event Browser windows, right-click on the window, and
select New Event Table from the displayed menu. You can then apply filtering or
name any new window by selecting the window, then following Steps 5 and 6.
Step 8: When you want to stop event monitoring, select Enable Event Monitoring again.
You can still carry out functions such as filtering or re-naming on any open
windows, but no further events will be added to their contents. Close the windows
after you are finished viewing their details.
#EMPQYNGFIKPICP#NCTOKPCP'XGPV$TQYUGT9KPFQY
You can acknowledge an alarm in an Event Browser Window, (ie, give it a visual indication
that you have looked at it) as follows:
Step 1: Select the alarm in the window.
Step 2: Right-click on the window.
Step 3: Select Acknowledge from the displayed menu. A check mark will now appear in the
Object column of the alarm.
Alternatively, you can acknowledge an alarm by simply double-clicking on the alarm Object
column in the window.

MARCH 2000
IOM-NMS-1/05C
&KURNC[KPIVJG&GVCKNU9KPFQYHQTCP#NCTOKPCP'XGPV$TQYUGT
9KPFQY
You can obtain more details on an alarm in an Event Browser Window by displaying the
Details Window. Proceed as follows:
Step 3: Select Details from the displayed menu to display the Details Window.
Step 4: When you have finished viewing the alarm details, close the Details Window.
&GNGVKPICP#NCTOKPVJG'XGPV$TQYUGT9KPFQY
DELETING AN ALARM. You cannot retrieve an alarm after you have deleted it from the
Event Browser Window.
You can delete an alarm from the Event Browser Window by using the following procedure:
Step 3: Select Delete from the displayed menu. The alarm will be deleted from the window.
2WTIKPI#EMPQYNGFIGF#NCTOUHTQOCP'XGPV$TQYUGT9KPFQY
PURGING ACKNOWLEDGED ALARMS. You cannot retrieve acknowledged alarms
after you have purged them from an Event Browser Window.
You can delete any alarms you have acknowledged from an Event Browser Window by using
the following procedure:
Note: Refer to Acknowledging an Alarm in an Event Browser Window for details on how
to acknowledge an alarm.
Step 2: Select Purge Acknowledge from the displayed menu. The acknowledged alarms will
be deleted from the window.
2WTIKPI%NGCTGF#NCTOUHTQOCP'XGPV$TQYUGT9KPFQY
PURGING CLEARED ALARMS. You cannot retrieve cleared alarms after you have
purged them from an Event Browser Window.
You can delete any cleared alarms from an Event Browser Window by using the following
procedure:

MARCH 2000
IOM-NMS-1/05C
Step 2: Select Purge Cleared from the displayed menu. The cleared alarms will be removed
from the window.
5GVVKPIVJG5GXGTKV[(KNVGTHQT#NCTOUKPCP'XGPV$TQYUGT9KPFQY
You can set an Event Browser Window to display only alarms that have specific severities by
using the following procedure:
Step 2: Select Filter Settings from the displayed menu.
Step 3: Select Severity from the Filter Settings menu. The Severity Filter window is now
displayed.
Step 4: Select the check boxes for the alarm severities you wish to see displayed in the
Event Browser Window.
Step 5: Select the Activate Severity Filtering check box, and then close the Severity Filter
window.
The Event Browser Window will now only display alarms with the severities you have
selected.
5GVVKPIVJG%NGCTGF5VCVWU(KNVGTHQT#NCTOUKPCP'XGPV$TQYUGT
9KPFQY
You can an Event Browser Window to display only either alarms that have been cleared, or
alarms that are currently active, by using the following procedure:
Step 3: Select Cleared Status from the Filter Settings menu. The Cleared/Raised Filter
window is now displayed.
Step 4: Select the Show Active Alarms check box if you wish to see only active alarms
displayed in the Event Browser Window.
Step 5: Select the Show Cleared Alarms check box if you wish to see only active alarms
displayed in the Event Browser Window.
Step 6: Select the Activate Cleared/Raised Filtering check box, and then close the
Cleared/Raised Filter window.
The Event Browser Window will now only display alarms with the status you have selected.

MARCH 2000
IOM-NMS-1/05C
5GVVKPIVJG#EMPQYNGFIG(KNVGTHQT#NCTOUKPCP'XGPV$TQYUGT
9KPFQY
You can set an Event Browser Window to display only either alarms that you have
acknowledged, or alarms that you have not acknowledged, by using the following procedure:
Step 3: Select Acknowledgement from the Filter Settings menu. The Acknowledge Filter
Step 4: Select the Show Acknowledged Alarms check box if you wish to see only
acknowledged alarms displayed in the Event Browser Window.
Step 5: Select the Show Unacknowledged Alarms check box if you wish to see only
unacknowledged alarms displayed in the Event Browser Window.
Step 6: Select the Activate Acknowledge Filtering check box, then close the Acknowledge
Filter window.
The Event Browser Window will now only display the alarms you have selected.
5GVVKPIVJG6[RG(KNVGTHQT#NCTOUKPCP'XGPV$TQYUGT9KPFQY
You can set an Event Browser Window to display only alarms of specific types by using the
following procedure:
Step 3: Select Type from the Filter Settings menu. The Type Filter window is now
displayed.
Step 4: Select the check boxes for the alarm types you wish to see displayed in the Event
Browser Window.
Step 5: Select the Activate Type Filtering check box, then close the Type Filter window.
The Event Browser Window will now only display alarms of the types you have selected.
5GVVKPIVJG&CVGCPF6KOG(KNVGTUHQT#NCTOUKPCP'XGPV$TQYUGT
9KPFQY
You can set the Event Browser Window to display only alarms occurring before, after or
between specific times of day or dates, by using the following procedure:
Note: You can use both filters at the same time to display alarms occurring at a specific
time of day on the days between specific dates.

MARCH 2000
IOM-NMS-1/05C
Step 3: Select Date and Time from the Filter Settings drop-down menu. The Time/Date
Filter window is now displayed.
Step 4: If you wish to see only alarms that occur before or after a specific time of day, select
the Time check box, enter the time in hours, minutes, and seconds into the From
fields, and then select the << button for alarms that occur before the entered time, or
the >> button for alarms that occur after the entered time.
Step 5: If you wish to see only alarms that occur between specific times of day, select the
Time check box, enter the times in hours, minutes, and seconds into the From and
To fields, and then select the <> button.
Step 6: If you wish to see only alarms that occur before or after a specific date, select the
Date check box, enter the date in days, months, and years into the From fields, and
then select the << button for alarms that occur before the entered date, or the >>
button for alarms that occur after the entered date.
Step 7: If you wish to see only alarms that occur between specific dates, select the Date
check box, enter the dates in days, months, and years into the From and To fields,
and then select the <> button.
Step 8: After you have set-up your required filters, select the Activate Date and Time
Filtering check box, then close the Date/Time Filter window.
The Event Browser Window will now only display alarms that have occurred between the
times and dates you have selected.
5GVVKPI)GPGTKE(KNVGTKPIHQT#NCTOUKPCP'XGPV$TQYUGT9KPFQY
You use generic filtering when you only want an Event Browser Window to display alarms
that contain specific pieces of text, eg, the name of a network element. The procedure is as
follows:
Note: Generic filtering is case-sensitive.
Step 3: Select Generic from the Filter Settings menu. The Generic Filter window is now
displayed.
Step 4: Type in the text you are interested in. Words to be searched for should begin and
end with *, eg, SMA will find all events containing the word SMA. When you are
searching for multiple text strings, the * should be used as a separator between the
words. The filter will then find all occurrences of each word, and AND them all
together.
Step 5: Select the Activate Generic Filtering check box, then close the Generic Filter
window.

MARCH 2000
IOM-NMS-1/05C
The Event Browser Window will now only display alarms that contain the text you are
interested in.
7UKPIVJG'/YKVJ'XGPV0QVKHKECVKQP(WPEVKQPU
To use the EM to notify you of events while you are performing other tasks on your PC, start
up the EM, and select Event Notifications from the Event Monitoring menu. If you wish to
receive an audio notification every time a new event occurs, select Enable Pop-up
Notification. If you wish to use the pop-up window notification, proceed as follows:
Step 1: Select Enable Pop-up Notification from the Event Notification menu.
Step 2: Apply any required filtering to the events to the pop-up notification (see the
references in the following text for setting event notification filters).
Step 3: If you wish to keep one of the cascaded windows on your desktop, select the
window, and then move it away from the other windows.
Step 4: After you are finished viewing the details in a window, click the Dismiss button.
5GVVKPIVJG5GXGTKV[(KNVGTHQT2QRWR0QVKHKECVKQPU
You can filter pop-up notification so that you are only notified of alarms that have specific
severities. The procedure is as follows:
Step 1: Select Filter by Severity from the Event Notifications menu. The Severity Filter
Step 2: Select the check boxes for the alarm severities you wish to be notified of.
Step 3: Select the Activate Severity Filtering check box, then close the Severity Filter
window.
You will now only be notified of alarms with the severities you have selected.
5GVVKPIVJG%NGCTGF5VCVWU(KNVGTHQT2QRWR0QVKHKECVKQPU
You can filter pop-up notification so that you are notified of when an alarm is cleared, or
when an alarm becomes active. The procedure is as follows:
Step 1: Select Filter by Cleared Status from the Event Notifications menu. The
Cleared/Raised Filter window is now displayed.
Step 2: Select the Show Active Alarms check box if you wish to be notified when an alarm
becomes active.
Step 3: Select the Show Cleared Alarms check box if you wish to be notified when an alarm
is cleared.
Step 4: Select the Activate Cleared/Raised Filtering check box, then close the
Cleared/Raised Filter window.
You will now only be notified of alarms of the status you have selected.
MARCH 2000
IOM-NMS-1/05C
5GVVKPIVJG6[RG(KNVGTHQT2QRWR0QVKHKECVKQPU
You can filter pop-up notification so that you are only notified of alarms of specific types.
The procedure is as follows:
Step 1: Select Filter by Type from the Event Notifications menu. The Type Filter window is
now displayed.
Step 2: Select the check boxes for the alarm types you wish to be notified of.
Step 3: Select the Activate Type Filtering check box, then close the Type Filter window.
You will now only be notified of alarms of the types you have selected.
5GVVKPI)GPGTKE(KNVGTKPIHQT2QRWR0QVKHKECVKQPU
You can filter pop-up notification so that you are only notified of alarms that contain specific
pieces of text, eg, the name of a network element. The procedure is as follows:
Note: The Generic Filter is case-sensitive.
Step 1: Select Generic Filtering from the Event Notifications menu. The Generic Filter
Step 2: Type in the text you are interested in. Words to be searched for should begin and
end with *, eg, SMA will find all events containing the word SMA. When you are
searching for multiple text strings, the * should be used as a separator between the
words. The filter will then find all occurrences of each word, and AND them all
together.
Step 3: Select the Activate Generic Filtering check box, then close the Generic Filter
window.
You will now only be notified of alarms that contain the text you are interested in.
'/'ZCORNG
In the following example, you have decided to enable the following Event Browser windows:
a window showing all events

a window showing all active events that are not acknowledged
a window monitoring a specific link
a window reviewing activity between 2am and 4am on several links to study a reported
fault
Procedure
Step 1: Load the network blueprint into DXR NET, and then connect to the network
containing the elements you are going to monitor.
Step 2: Select the network elements you wish to monitor, as detailed in Selecting the NMS
Elements for the EM.

MARCH 2000
IOM-NMS-1/05C
Step 3: Start the EM by selecting Enable Network Event Monitoring from the Event
Monitoring menu.
Step 4: Display the first Event Browser window by selecting Event Browser from the Event
Monitoring menu. This will be the window containing all events. Right-click on this
window, select Label Browser from the displayed menu, type in All Events into
the Label Browser window, then click the OK button. The name All Events is
now shown in the window title bar.
Figure 42: All Events Window

Step 5: To display the next Event Browser window, right-click on the All Events window,
and select New Event Table from the displayed menu. This window will show all
active events that are not acknowledged. Right-click on this window, select Label
Browser from the displayed menu, type in Active/Unacknowledged into the Label
Browser window, then click the OK button. The name Active/Unacknowledged is
now shown in the window title bar.
Step 6: Right-click in the Active/Unacknowledged window, and select Filter Settings,

then Cleared Status from the Filter Settings menu. Select the Show Active Alarms
check box in the Cleared/Raised Filter window, then the Activate Cleared/Raised
Filtering check box, and then close the Cleared/Raised Filter window. The window
will now only show active alarms.
Step 7: Right-click in the Active/Unacknowledged window, and select Filter Settings,

then Acknowledgement from the Filter Settings menu. Select the Show
Unacknowledged Alarms check box in the Acknowledge Filter window, then the
Activate Acknowledge Filtering check box, and then close the Acknowledge Filter
window. The Active/Unacknowledged window will now only show active alarms
that have not been acknowledged.
MARCH 2000
IOM-NMS-1/05C
Figure 43: Active/Unacknowledged Window

active events on a specific link. Right-click on this window, select Label Browser
from the displayed menu, and type in Link into the Label Browser window, then
click the OK button. The name Link is now shown in the window title bar.
Step 9: Right-click on the Link window, and select Filter Settings, then Generic from the
Filter Settings menu. Type in the names of the SMAs connected to the terminals at
either end of the link into Generic Filter window, using the * at the beginning and
end, and as a separator between the words. Include the AUX port to which the
terminals are connected. Remember that the Generic Filter is case-sensitive, so type
in the names to match the case of the names in the blueprint. Select the Activate
Generic Filtering check box, and then close the Generic Filter window. The Link
window will now only display the events associated with the link.

MARCH 2000
IOM-NMS-1/05C
Figure 44: Link Window

active events that occur between 2am and 4am on specific links. Right-click on this
window, select Label Browser from the displayed menu, and type Times into the
Label Browser window, then click the OK button. The name Times now shown in
the window title bar.
Step 11: Right-click on the Times window, and select Filter Settings, then Date and Time
from the Filter Settings menu. Select the Time check box, and enter 2, 0, and 0 into
the hours, minutes and seconds fields in the From fields, then 4, 0, and 0 into the
hours, minutes and seconds fields in the To fields. Select the <> button, and then
the Activate Date and Time Filtering check box, then close the Date/Time Filter
window.
Step 12: Right-click on the Times window, and select Filter Settings, then Generic from
the Filter Settings menu. Type in the names of the terminals at either end of the links
you are interested in into Generic Filter window, using the * at the beginning and
end, and as a separator between the words. Remember that the Generic Filter is
case-sensitive, so type in the names to match the case of the names in the blueprint.
Select the Activate Generic Filtering check box, then close the Generic Filter
window. The Times window will now only display the events that occur between
2am and 4am associated with the specified links.

MARCH 2000
IOM-NMS-1/05C
Figure 45: Times Window

You have now created Event Browser Windows for all the events you are interested in.

MARCH 2000
IOM-NMS-1/05C
Using DXR NET with DXR 100
7UKPI&:40'6YKVJ&:4
)GPGTCN
DXR 100 is a point-to-point digital microwave radio system designed primarily for medium to
long haul, thin route telecommunications networks. It is available in three different
configurations:
Unprotected - this comprises a radio modem RF unit packaged in a standard 19 inch 3U

horizontal rack shelf or 120 mm slim rack
Protected - this comprises a main radio modem RF unit, a standby radio modem RF unit,
and a protection switch interface (supports space and frequency diversity options)
Upgradeable - this comprises a single radio modem RF unit and a protection switch
interface
For a more detailed description of the DXR 100, refer to the DXR 100 Installation and
Maintenance manual, Technical Manual, and Product Descriptions.
Note: Digital Microwave Corporation also provides technical training programs for DXR
100 users. Refer to your local Digital Microwave Corporation representative for
details.
#DQWV6JKU5GEVKQP
This section describes the DXR 100 terminal information and functions that are available to
you when you use DXR NET. The NMS board information and functions are described in
Section 6.
Note: Before consulting this section, you should have read and understood the material in
Section 4, particularly the material relating to the Network Blueprint concept.
ABORT BUTTON. Whenever you use DXR NET to make changes to a DXR 100 terminal,
However, if you do this, DXR NET will simply stop sending commands to the terminal. This
can leave the terminal and any associated link(s) in an undesired state, with the terminal
values in DXR NET and re-send them to the terminal. For these reasons, we recommend that
before you start making changes you save the current terminal configuration, and that you
WRITING CONFIGURATION CHANGES TO A DXR 100 TERMINAL. Whenever you

write configuration changes and data to a DXR 100 terminal, there is a momentary loss of
traffic on the link. We advise therefore that you carry out any changes to the configuration

MARCH 2000
IOM-NMS-1/05C
when the link is either out of service, or at times when link traffic is at a minimum.
Note 1: We advise that if there are significant changes to the DXR 100 terminal
configuration data, these should be done by loading a new file created offline, rather
than making the changes manually.
Note 2: If you change any terminal parameters in a workspace tabbed page, you must select
the Commit button from the toolbar before leaving the page, otherwise the changes
will not take effect. You will be prompted to select the button if you try to leave a
Note 3: When using the LMT, you will only be able to access the DXR 100 terminals that
make up the local link. Elements you cannot access will be shown greyed-out.
Note 4: In the Explorer Window, the icon for the DXR 100 terminal you are connected to
will show a red plug symbol.
Note 5: Blueprints created using the Autodiscovery feature only contain the terminals in the
link you are connected to, and only contain the remote terminals if the link is
operational.
The DXR NET functions are divided between the Configuration, Commissioning and
Maintenance Workspaces (see Section 2 for details). You use the Configuration Workspace to
setup and modify the following DXR 100 terminal parameters:
Terminal frequencies (MHz) and transmitter RF power (dBm)

Forward and reflected power alarm limits (dBm)
AGC alarm limits (V)
Correctable bytes per second alarm upper limit
Diversity
Mapping of alarms in the action table
Commissioning and impedance of tributaries
Alarm inputs and outputs
You use the Commissioning Workspace to check and monitor the DXR 100 while it is being
installed, and after it has been brought into operation. The workspace enables you to view site
and terminal details, the alarm status, and enable the loopback functions.

MARCH 2000
IOM-NMS-1/05C
You can use the Maintenance Workspace to carry out detailed diagnostics on the DXR 100.
Like the Commissioning Workspace, it enables you to view site and terminal details, the
alarm status, and enable the loopback functions. In addition, it uses real-time information to
produce Constellation Diagrams and AGC Graphs that enable you to monitor DXR 100
performance in detail.
7UKPI&:40'6VQEQPHKIWTGC&:4
+PVTQFWEVKQP
This section covers the operations you should take to configure a new DXR 100 terminal as
part of a network. You can do this in one of two ways:
Note: The terminal should have the correct frequency loaded, and that the network
blueprint (if used) should contains the complete and correct configuration data.
using a master network blueprint (preferred method). The network designer uses
DXR NET to create a master network blueprint or Design blueprint, containing all the
information required to configure the DXR 100 terminals. This blueprint is then used at
the time of installation to load the terminal configurations. Any changes made in the field
can be saved in the blueprint, which now becomes 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, or from the central office. The blueprint
constructed from all the field blueprints is called a Commissioned blueprint, as it reflects
the unique, real, network that is installed.
using configuration sheets. The network installation teams install the terminal, then use
the DXR NET Autodiscovery feature to build a blueprint containing the installed terminal.
They then work through the tabbed pages in the Configuration Workspace, making any
changes required 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 the Field blueprint. The procedure is then the same as for a Field blueprint
created using a master network blueprint.
ABORT BUTTON. Whenever you use DXR NET to make changes to a terminal, 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 terminal. This can leave
the terminal and any associated link(s) in an undesired state, with the terminal software not
reflecting the correct settings for the link. You will then need to set the correct values in
DXR NET and re-send them to the element. For these reasons, we recommend that before
you start making changes you save the current terminal configuration, and that you have a
hard copy of the desired settings available.


MARCH 2000
IOM-NMS-1/05C
%QPHKIWTKPIC&:4VGTOKPCNHTQOPGYYKVJCOCUVGTDNWGRTKPV
This procedure covers configuring a DXR 100 terminal from a master blueprint. You will use
DXR NET to:
load the master blueprint

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
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 the
far 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 been
successfully powered up
the DXR NET PC is connected to the V.24 connector on the terminal front panel
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 any
changes to a terminal. For example, writing incorrect frequencies back to the
terminal will result in the loss of the operational link, which could require on-site
actions to recover.
Note 2: If you attempt to write default values to a terminal, DXR NET will ask you to
confirm the action.
Note 3: You cannot use the autodiscovery feature when connected to the DXR 100 via
Ethernet.
Procedure

MARCH 2000
IOM-NMS-1/05C
Step 3: Enable the autodiscovery feature by selecting the Connect button from the DXR NET
toolbar. After autodiscovery is successfully completed, the terminal you are
attached to will appear in the Explorer Tree window with a small plug symbol.
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. Also note the terminal
frequencies.
Step 4: Select the Disconnect button, then click File in the DXR NET menu bar, and select
Open from the drop-down menu. Load the master blueprint by selecting the
blueprint file, then click the OK button. Check that the frequencies in the blueprint
match the ones read from the terminal. If this is not the case, you should change the
blueprint frequencies to match the terminal.
Step 5: Select the Connect button again from the DXR NET toolbar. If the connection is
successful, the icon for the terminal you are attached in the active blueprint will
appear in the Explorer Tree window with a small plug symbol.
Step 6: Make any changes that are required to the terminal configuration in the workspace
pages. Refer to the specific operations detailed in this section for details. Ensure you
save any changes made to the blueprint using the Commit button.
Step 7: After you have made and saved any required changes to the blueprint, click the
Write Configuration button in the DXR NET toolbar to load the configuration to the
terminal. DXR NET will open a window asking to proceed. Ensure that you have the
correct terminal selected in the Explorer Tree, and select Start to write to the
terminal.
Step 8: After any changes have been written to the terminal, right-click on the terminal in
the Explorer Tree, and select Export Configuration. Select the destination for the file
containing terminal settings, then the OK button.
Step 9: Select Save or Save As from the File menu to save the blueprint. This blueprint is
known as the "field blueprint".
Step 10: If this is the second terminal of a link, the link should now be operational. To
confirm this, check that you can use autodiscovery to connect to the far end
terminal, and the select the Commissioning Workspace to check if any alarms are
present.
Step 11: When you are finished viewing or modifying the terminal configuration, click on the
Disconnect button in the DXR NET toolbar, then select Exit from the File menu.
%QPHKIWTKPIC&:4VGTOKPCNHTQOPGYYQTMKPIHTQOEQPHKIWTCVKQP
UJGGVU
This procedure covers configuring a DXR 100 terminal working from configuration sheets.
You will use DXR NET to:


MARCH 2000
IOM-NMS-1/05C
you know what the name of the terminal should be
actions to recover.
confirm the action.
Ethernet.
Procedure
toolbar. After autodiscovery is successfully completed, the terminal you are attached
to will appear in the Explorer Tree window with a small plug symbol.
Step 4: Click the Read Configuration button from the DXR NET toolbar to read the terminal
settings into the Configuration workspace.
Step 6: After you have made and saved any changes to the blueprint, click on the Write
Configuration button in the DXR NET toolbar to save the changes to the terminal.
DXR NET will open a window asking to proceed. Ensure that you have the correct
terminal selected in the Explorer Tree, and select Start to write to the terminal.

MARCH 2000
IOM-NMS-1/05C
terminal, and check for alarms to confirm correct operation
Step 10: When you are finished viewing or modifying the network, click on the Disconnect
button in the DXR NET toolbar, then select Exit from the File menu.
$WKNFKPIC%QOOKUUKQPGFPGVYQTMDNWGRTKPV
As terminals are installed and become operational, it is useful to have an updated blueprint at
the central office and in the operations centre. This blueprint should reflect the latest
configuration data, and any operational data about the network. Engineers travelling to sites
should have this blueprint with them , in case a terminal needs to be replaced. This blueprint
is 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 reading
the data directly from the terminals.
Note: Great care should be taken that the parameters are correct before writing any
actions to recover.
5GVVKPIVJG6GTOKPCN(TGSWGPEKGUCPF6TCPUOKVVGT4(2QYGT
For a DXR 100 terminal, the relationship between the frequency range, the modulation, the
capacity, and the maximum transmitter power output at the Tx port, is shown in the following
table.
Modulation
QPSK 16 QAM
1 x E1 2 x E1 4 x E1 1 x E1 2 x E1 4 x E1
DXR 124 2300-2500 MHz 33 dBm - 33 dBm - - -
DXR 126 2500-2700 MHz - - 33 dBm - - -
You can set the transmit and receive frequencies and RF output power of a terminal using the
following procedure.
SETTING THE TERMINAL FREQUENCIES AND TRANSMITTER RF POWER. The

frequency range and transmitter power of your terminal depends on the duplexer of the
terminal. Therefore, any changes you make to the frequency parameters must reflect the
duplexer tuning, and any changes to the output power must reflect the capacity of the
duplexer.

MARCH 2000
IOM-NMS-1/05C
Figure 46: Modem/RF Link Setup Page Unprotected DXR100
Figure 47: Modem/RF Link Setup Page Protected DXR 100

MARCH 2000
IOM-NMS-1/05C
Procedure
Step 1: Select the Configuration Workspace.
Step 2: Select the Modem/RF Link Setup page.
Step 3: In the Radio section, change the transmit and receive frequencies, or the transmitter
power by using the up/down arrows in the relevant field, or by selecting the relevant
field and typing in the value.
Step 4: After you have finished making 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 to
make any further changes to the terminal configuration, select the Write Configuration button
in the Toolbar. The terminal configuration will now change to reflect the values set in the
blueprint.
5GVVKPIVJG(QTYCTFCPF4GHNGEVGF2QYGT#NCTO.KOKVU
The Forward and Reflected Power Alarm limits are used to define the input and output RF
power levels that trigger the Forward and Reflected Power Alarms. Refer to Appendix A for
details. You can set the limits using the following procedure.
Note: You can set the limits to their default values by clicking the Default button.

MARCH 2000
IOM-NMS-1/05C
Procedure
Step 2: Select the Thresholds page.
Step 3: In the Transmit Path section, set the high and low limits for the forward power by
using the up/down arrows in the relevant fields, or by selecting the relevant fields
and typing in the values.
Step 4: In the Transmit Path section, set the high limit for the reflected power by using the
up/down arrows in the relevant field, or by selecting the relevant field and typing in
the value.
Toolbar.
blueprint.
5GVVKPIVJG#)%#NCTO.KOKVU
The AGC Alarm limits are used to define the range over which the AGC voltage can vary
without triggering the AGC Alarm. Refer to Appendix A for details. You can change the AGC
low 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 3: In the Receive Path section, set the high and low limits for the AGC by using the
up/down arrows in the relevant fields, or by selecting the relevant fields and typing
in the values.
Toolbar.
blueprint.

MARCH 2000
IOM-NMS-1/05C
5GVVKPIVJG%QTTGEVCDNG$[VGURGT5GEQPF6JTGUJQNF
The Correctable Bytes per Second Threshold is used to set the maximum number of bytes
received over the link that need error correction before triggering the Correctable Error Limit
alarm. Refer to Appendix A for details. You can change the Correctable Bytes per Second
Threshold of a terminal using the following procedure.
Note 1: You can set the limit to a default value by clicking the Default button.
Note 2: Section 4 gives a procedure for calculating the Correctable Bytes per Second for
your link.
Procedure
Step 3: In the General section, set the Correctable Bytes per Second by using the up/down
arrows in the fields, or by selecting the field and typing in the value.
Toolbar.
blueprint.
5GVVKPIVJG6GTOKPCN&KXGTUKV[1RVKQP
You can change the diversity option of a protected DXR 100terminal using the following
procedure.
SETTING THE TERMINAL DIVERSITY OPTION. The diversity you can select is
dependent on the terminal hardware. You must not make any changes in the software that
do not comply with your terminal hardware.
Note: If you select either of the Space or Frequency Diversity options, you will have to set
the terminal power and AGC alarm limits for each radio. If you select the Frequency
Diversity option, you will also have to set the frequencies and transmitter power for
each radio.
Procedure
Step 3: In the Protected & Diversity Options section, select the option you require by
clicking the relevant radio button. You can choose between Protected, Space
Diversity or Frequency Diversity.

MARCH 2000
IOM-NMS-1/05C
Step 4: If you have selected the Frequency Diversity option, select the frequencies you
require for the two radios in the Radio A and Radio B fields. Refer to Changing the
Terminal Frequencies and RF Power for details.
Step 5: If you have selected either of the Frequency or Space Diversity options, select the
terminal power and AGC alarm limits for each radio. Refer to Changing the
Terminal Power Alarm Limits and Changing the AGC Limits for details.
Toolbar.
blueprint.
/CRRKPICP'XGPVVQCP#EVKQP
You can set the DXR 100 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.
The Action Table page is divided into the Events, Mapped Actions and Inherited Actions
panes. The Events pane lists the events that you can set an action for. The events are listed in
the Windows Explorer tree format. The Mapped Actions pane lists any actions that you have
mapped to the alarm presently selected in the Events pane. The Inherited Actions pane lists
any actions mapped to an alarm higher up in the tree hierarchy than the alarm you have
currently selected.
You can set an event to generate an action using the following procedure:

MARCH 2000
IOM-NMS-1/05C
Procedure
Step 2: Select the Action Table page. The events you can select actions for are displayed in
a hierarchical tree in the Windows Explorer format in the Events pane.
Step 3: Move down the levels of the tree in the Events pane, until you can select the event
for which you want to generate an action.
Step 4: Select the Edit Actions button.
Step 5: In the Edit Actions window, select the Location (i.e., where you want the alarm
action to be produced) and the Action (i.e., what you want to happen when the event
occurs) from the scroll-bars, then click on the Add Action button next to the menu
window. The action will appear in the lower pane of the window. If you decide to
remove an action after selection, select the action in the lower pane, then click on
the Delete Action button next to the menu window.
Step 6: Select the OK button in the Add Actions window. The window will close and the
action should now be displayed in the Mapped Actions pane of the Actions Table
page.
Toolbar.
blueprint.
4GOQXKPICP#EVKQPHTQOCP'XGPV
You can remove an action you have mapped to an event (see Mapping an Event to an Action)
Procedure
Step 2: Select the Action Table page. The events you have selected actions for are displayed
in a hierarchical tree in the Windows Explorer format in the Events pane.
from which you want to remove an action. Any actions mapped to the event will be
displayed in the Mapped Actions pane.
Step 4: Select the action you want to remove in the Mapped Actions pane and click the
Delete Actions button. If the action is mapped to a single event, it will disappear
from the pane. If it is mapped to more than one event, a dialog box will appear
allowing you to choose between removing the action from just the selected event, or
from all the events it has been mapped to.
MARCH 2000
IOM-NMS-1/05C
Toolbar.
blueprint.
5GNGEVKPIVJG6GTOKPCN.KPG+PVGTHCEG6[RG
You can select the DXR 100 terminal line interface using the following procedure:
SELECTING THE INTERFACE TYPE. The interface type you can select is dependant
upon the hardware in your DXR 100 terminal. You should therefore only use this procedure
to ensure that the interface type is the correct one for the terminal.
Figure 50: Interface Setup Page for DS1 Line Interface
Procedure
Step 2: Select the Interface Setup page.
Step 3: Click on the Interface Type field in the Interface section and select the interface type
from the displayed drop-down menu.
Toolbar.

MARCH 2000
IOM-NMS-1/05C
blueprint.
5GNGEVKPIVJG.KPG+PVGTHCEG2CTCOGVGTUHQTVJG'+PVGTHCEG6[RG
You can select the line parameters for a DXR 100 terminal with the E1 Interface Type using
the following procedure:
SETTING THE INTERFACE CAPACITY. The interface capacity is dependant upon the
hardware in your DXR 100 terminal. You should therefore only use this procedure to
ensure that the interface capacity is the correct one for the terminal.
SETTING THE LINE IMPEDANCE. The line impedance is dependant upon the cabling
attached to the line interface of your DXR 100 terminal. You should therefore only use this
procedure to ensure that the line impedance matches the cabling.
Procedure
Step 3: If you wish to change the interface capacity, select the new capacity from the drop-
down menu displayed when you click on the Interface Capacity field in the Interface
section.
Step 4: If you wish to change the impedance of a particular tributary, double-click the
relevant entry in the Line Impedance column of the table in the Tributary section,
then select the new impedance from the displayed scroll-down menu.
Step 5: If you wish to change the commissioned state of a particular tributary, double-click
the relevant entry in the Commissioned column of the table in the Tributary section,
then select the new state from the displayed scroll-down menu. The entry is True for
commissioned tributaries, and False for uncommissioned tributaries.
Toolbar.
blueprint.
5GNGEVKPIVJG.KPG+PVGTHCEG2CTCOGVGTUHQTVJG&5+PVGTHCEG6[RG
You can select the line parameters for a DXR 100 terminal with the DS1 Interface Type

MARCH 2000
IOM-NMS-1/05C
SETTING THE INTERFACE CAPACITY. The interface capacity is dependant upon the
hardware in your DXR 100 terminal. You should therefore only use this procedure to
ensure that the interface capacity is the correct one for the terminal.
SETTING THE LINE IMPEDANCE. The line impedance is dependant upon the cabling
attached to the line interface of your DXR 100 terminal. You should therefore only use this
procedure to ensure that the line impedance matches the cabling.
Procedure
section.
Step 4: If you wish to change the line build-out of a particular tributary, double-click the
relevant entry in the Line Build-out column of the table in the Tributary section,
then select the new value from the displayed scroll-down menu.
Step 5: If you wish to change the commissioned state of a particular tributary, double-click
the relevant entry in the Commissioned column of the table in the Tributary section,
then select the new state from the displayed scroll-down menu. The entry is True for
commissioned tributaries, and False for uncommissioned tributaries.
Toolbar.
blueprint.
5GVVKPI7R#NCTO+PRWVU
You can setup an alarm input to the DXR 100 using the following procedure:

MARCH 2000
IOM-NMS-1/05C
Figure 51: Alarm I/O Page
Procedure
Step 2: Select the Alarm I/O page.
Step 3: If you wish to assign a name to the alarm input, then select the relevant input
identifier field and type in the name.
Step 4: If you wish to set the normal condition of the input, i.e. the input state that indicates
no alarm is present, click on the Normal State field, and select the appropriate state
from the displayed scroll-down menu. You can choose between Current and No
Current.
Toolbar.
blueprint.
5GVVKPI7R#NCTO1WVRWVU
You can setup an alarm output from the DXR 100 using the following procedure:

MARCH 2000
IOM-NMS-1/05C
Procedure
Step 2: Select the Alarm IO page.
Step 3: If you wish to assign a name to the alarm output, then select the relevant output
identifier field, and type in the name.
Step 4: If you wish to set the normal condition of the output, i.e. the output state that
indicates no alarm is present, click on the Normal State field, and select the
appropriate state from the drop-down list. You can choose between Open and
Closed.
Step 5: Select the maximum number of changes the alarm signal can make per second by
clicking on the Rate field, and either using the up/down arrows, or typing in the
value.
Toolbar.
blueprint.
8KGYKPIVJG#NCTO5VCVWU
You can view the Alarms page using the following procedure.
Note 1: The first three steps of this procedure can be replaced by selecting the Maintenance
Workspace, then the Alarms page. You would do this if you were already sure that
alarms were present.
Note 2: If the LED icon in Step 2 is a dull red, it indicates that DXR NET cannot
communicate with the selected terminal.

MARCH 2000
IOM-NMS-1/05C
Procedure
Step 1: Select the Commissioning Workspace.
Step 2: Select the Commissioning page. If the LED icon in the Alarm Status section is not
green, alarms are present on the link.
Step 3: To identify any current alarms, click on the View Alarms button to display the
Alarms page. The Alarm Status and Related Information pane displays all possible
alarms in a hierarchical Explorer Tree format.
Step 4: If an alarm icon in the Alarm Status and Related Information pane is red, double-
click on the icon to move down the levels until the alarm is reached. The alarm
name 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 appropriate
network personnel.
'PCDNKPIVJG6TKDWVCT[.QQRDCEMU
You can enable the DXR 100 tributary loopback functions on the Controls page using the

MARCH 2000
IOM-NMS-1/05C
Loopback functions interrupt network traffic.
Tributary loopbacks affect all tributaries at once.
Procedure
Step 1: Select the Commissioning or the Maintenance Workspace.
Step 2: Select the Controls page.
Step 3: Select the tributary loopback function from the Tributary Loopback section by
clicking on the associated radio button
Step 4: Click the Apply button in the displayed dialog box, then the OK button in the
Warning box.
Step 5: When you have completed your tests, select the No Tributary Loopback radio
button, then Click the Apply button.
'PCDNKPI&KIKVCN+(('%.QQRDCEMU
You can enable the DXR 100 Digital/IF/FEC loopback functions using the following
procedure.

MARCH 2000
IOM-NMS-1/05C
Procedure
Step 1: Select the Commissioning or Maintenance Workspace.
Step 3: Select the RF/Modem loopback function from the RF/Modem section by clicking on
the associated check box.
Warning box.
Step 5: When you have completed your tests, deselect the loopback function by clicking
again on the selected check box.
6GUVKPI2TQVGEVKQP5YKVEJKPI
Note: You can only enable protection switching in a protected DXR 100.
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 3: Select the Manual switching option you require from the Protection Switching
section by clicking on the associated radio button.
Step 4: Select the transmitter or receiver you wish DXR 100 to switch to.
Warning box.
Step 6: When you have completed your tests, reselect the Automatic switching option by
clicking again on the associated radio button.
8KGYKPIVJG%QPUVGNNCVKQP&KCITCO
You can view the Constellation Diagram for a DXR 100 terminal using the following
procedure.
Except for the AGC page operations, you cannot select other operations while Constellation
Diagram monitoring is in progress.

MARCH 2000
IOM-NMS-1/05C
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 the
diagrams. If the Multi-Carrier option is selected in the Advanced option in the Tools
menu, DXR NET monitors the individual carriers of the local terminal to produce the
diagrams.
Figure 54: Constellation Diagram Single View Selected
Procedure
Step 1: Select the Maintenance Workspace.
Step 2: Select the Constellation Diagram page.
Step 3: Select the terminals or carriers you wish to monitor by clicking the relevant button
in the Select Terminal section.
Step 4: You can start monitoring for all terminals or carriers by clicking the Monitor All
button in the Select Terminal section, or you can start monitoring for an individual
terminal or carrier by clicking the Monitor button in the particular Constellation
Diagram for the terminal or carrier.

MARCH 2000
IOM-NMS-1/05C
Step 5: If you wish to clear all the diagrams and restart monitoring click on the Reset All
button in the Select Terminal section. If you wish to clear and restart monitoring for
a particular diagram, click on the Reset button in the diagram.
Step 6: After you have finished monitoring the constellation diagrams, stop monitoring by
clicking on any indented monitoring buttons. Ensure that all the monitoring buttons
are raised before leaving the page.
8KGYKPI#)%)TCRJ
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 AGC
graphs. If the Multi-Carrier option is selected in the Advanced option in the Tools
graphs.

MARCH 2000
IOM-NMS-1/05C
Figure 55: AGC Graph Single View Selected
Procedure
Step 2: Select the AGC Graph page.
Step 3: Select the terminals or carriers you wish to monitor by clicking on the relevant
button.
terminal or carrier by clicking the Monitor button in the particular AGC Graph for
the terminal or carrier.
Step 5: If you wish to clear all the graphs and restart monitoring click on the Reset All
button in the Select Terminal section.
Step 6: If you wish to reset the Max and Min bars for a particular graph, click on the Reset
button in the graph. This will reset the bars to the maximum and minimum AGC
values recorded since monitoring began, or since the last time you selected the graph
Reset button.
Step 7: After you have finished monitoring the AGC graphs, stop monitoring by clicking on
any indented monitoring buttons. Ensure that all the monitoring buttons are raised
before leaving the page.

MARCH 2000
IOM-NMS-1/05C
Using DXR NET with the NMS Board
7UKPI&:40'6YKVJVJG0/5$QCTF
)GPGTCN
The NMS board is an optional network management interface board, which can be fitted to
the DXR 100. It provides the SNMP agent and transport for DXR NET NMS. You must
specify this option when you order the DXR 100, since it is not possible to upgrade a DXR
100 in the field without void of warranty (except by a DMC Customer Services
Representative).
Note: DXR 100 terminals fitted with the NMS option cannot be operated in the same link
with DXR 100 terminals not fitted with the NMS option.
When the NMS board has been fitted to all network terminals, any terminal in the network
can be managed using either DXR NET or ProVision. Depending on terminal capacity, the
NMS board uses 32 or 64 kbps of wayside capacity as an inter-terminal communication
channel.
For a more detailed description of DXR 100, refer to DXR 100 Installation and Operation
Manual and Product Description.
Note: Digital Microwave Corporation provides technical training programs for NMS board
users. Refer to your local Digital Microwave Corporation representative for details.
#DQWV6JKU5GEVKQP
This section describes the information and functions that are available to you when you use
DXR NET to access the NMS board within a DXR 100 with the NMS option. Any DXR 100
parameters that are the same as for the DXR 100 without the NMS option, and you should
refer to Section 5.
Sections 4, particularly the material relating to the Network Blueprint concept.
You can use DXR NET to access and modify the following NMS board parameters:
IP addressing (routes, masks and interfaces)

View Alarm Status
7UKPI&:40'6VQKPUVCNNC&:4YKVJ0/5$QCTF
This section covers the operations you should take to configure a new DXR 100 with NMS
board as part of a network. You can do this in one of two ways:

MARCH 2000
IOM-NMS-1/05C
Note: The network blueprint (if used) should contain the complete and correct
configuration data.
information required to configure the DXR 100 terminal and the NMS boards. This
blueprint is then used at the time of installation to load the terminal and board
configurations. Any changes made in the field can be saved in the blueprint, which now
becomes 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, or from the central office. The blueprint constructed from all the field blueprints is
called a Commissioned blueprint, as it reflects the unique, real, network that is installed.
using configuration sheets. The network installation teams install the terminal with the
board, then use the DXR NET Autodiscovery feature to build a blueprint containing the
installed terminal. They then work through the tabbed pages in the Configuration
Workspace, making any changes required to bring the terminal and board into line with the
values given in the configuration sheets. The installed configuration should then be saved
to a blueprint, which now becomes the Field blueprint. The procedure is then the same as
for a Field blueprint created using a master network blueprint.
values in DXR NET and re-send them to the affected elements. For these reasons, we
recommend that before you start making changes you save the current element
configuration, and that you have a hard copy of the desired settings available.
WRITING CONFIGURATION CHANGES TO A ELEMENT. Whenever you write

configuration changes and data to a element, there is a momentary loss of traffic on the
network elements after initial setup and after any changes are made.

MARCH 2000
IOM-NMS-1/05C
%QPHKIWTKPIC&:4VGTOKPCNYKVJ0/5DQCTFHTQOPGYYKVJC
OCUVGTDNWGRTKPV
This procedure covers configuring a DXR 100 terminal with NMS board from a master
blueprint. You will use DXR NET to:

make any required changes to the terminal and board configurations
save any changes that are made to the terminal or board configurations for later use
the terminal containing the NMS board has been installed, connected to power and the
antenna, and has been successfully powered up
you know what the IP address of the board is in the master blueprint
actions to recover.
confirm the action.
Ethernet.
Procedure
Step 3: Select the Connect button from the DXR NET toolbar. DXR NET will perform
autodiscovery, and a blueprint of the network containing the terminal you are
attached to will appear in the Explorer Tree window. The terminal you are attached
to will have a small red plug symbol.
Step 4: Set the board IP address to match the master blueprint (refer to the Setting the
NMS board IP Address procedure).
Step 5: Once the new address has been written, the terminal will drop the connection to the
DXR NET PC, and will ask if you want to reconnect. Select No, then open the
"master" blueprint.

MARCH 2000
IOM-NMS-1/05C
Step 6: Select the Connect button from the DXR NET toolbar. DXR NET will mark the
terminal you are connected to on the Explorer tree with a small red plug symbol.
Ensure that the correct terminal is selected in the tree before attempting to load the
configuration from the blueprint, as loading the configuration to the wrong terminal
will have serious consequences. If the correct terminal is not selected, check the
board IP address in the blueprint, click the Disconnect button in the DXR NET
toolbar, then go back to Step 3.
Step 7: After you have ensured the correct terminal is selected, double-click on the terminal
icon to display the NMS board. Go through each of the tabbed pages in the
Configuration Workspace, making any required changes (refer to the procedures
given later in this section for details). After you have completed any required
changes, click on the Commit button to save them to the blueprint.
Step 8: Select the Write Configuration button from the DXR NET toolbar, then select Start
to load the configuration details to the NMS board. When the configuration has
loaded, press OK. If you made any changes in Step 7, right-click on the board icon
in the Explorer Tree, then select Write Configuration from the drop-down menu and
save the NMS board configuration to file.
Step 9: Select the DXR 100 terminal that contains the NMS board in the Explorer Tree then
go through each of the tabbed pages in the Configuration Workspace, making any
required changes (refer to the procedures given in Section 5 for details). After you
have completed any required changes, click on the Commit button to save them to
the blueprint.
to load the configuration details to the terminal. When the configuration has loaded,
press OK. If you made any changes in Step 9, right-click on the terminal icon in the
Explorer Tree, then select Write Configuration from the drop-down menu and save
the terminal configuration to file.
+PUVCNNKPIHTQOPGYHTQOEQPHKIWTCVKQPUJGGVU
This procedure covers configuring a DXR 100 terminal with NMS board from configuration
sheets. You will use DXR NET to:

make any required changes to the terminal and board configurations
the terminal containing the NMS board has been installed, connected to power and the
antenna, and has been successfully powered up

MARCH 2000
IOM-NMS-1/05C
you know what the IP address of the board should be
actions to recover.
confirm the action.
Ethernet.
Procedure
attached to will appear in the Explorer Tree window. The terminal you are attached
to will have a small red plug symbol.
Step 4: Set the NMS board real time clock and IP address (refer to Setting the Real Time
Clock and Setting the NMS board IP Address procedures in this section).
Step 5: Once the new IP address has been written, the board will drop the network
connection to the DXR NET PC. DXR NET will then ask if you want to reconnect.
Wait 15 seconds, and then select Yes. DXR NET will perform autodiscovery, and a
blueprint of the network containing the terminal you are attached to will appear in
the Explorer Tree window.
Step 6: Double-click on the terminal to display the NMS board, then select the NMS board
in the Explorer Tree. Select the Read Configuration button from the DXR NET
toolbar to read the terminal configuration details into the blueprint. This will ensure
that the that you are working on the correct parameters when you make changes.
Step 7: Go through each of the tabbed pages in the Configuration Workspace, making any
required changes (refer to the procedures given later in this section for details).
After you have completed any required changes, click on the Commit button to save
them to the blueprint.
to load the configuration details to the NMS board. When the configuration has
loaded, press OK. If you made any changes in Step 7, right-click on the board icon
in the Explorer Tree, then select Write Configuration from the drop-down menu and
save the NMS board configuration to file.

MARCH 2000
IOM-NMS-1/05C
Step 9: Select the DXR 100 terminal that contains the NMS board in the Explorer Tree then
go through each of the tabbed pages in the Configuration Workspace, making any
required changes (refer to the procedures given in Section 5 for details). After you
have completed any required changes, click on the Commit button to save them to
the blueprint.
to load the configuration details to the terminal. When the configuration has loaded,
press OK. If you made any changes in Step 9, right-click on the terminal icon in the
the terminal configuration to file.
should have this blueprint with them, in case a terminal needs to be replaced. This blueprint
Great care should be taken before writing any changes to a terminal, that the parameters are
correct. Writing incorrect frequencies or capacities back to the terminal will result in the loss
of the operational link, which could require on-site actions to recover.
5GVVKPIVJG0/5$QCTF4GCN6KOG%NQEM
The NMS board has an internal clock to synchronise its operations. You can use the following
procedure to set the Real Time Clock for a directly connected NMS board:
Note: If the Real Time Clock is not set, an alarm (Real Time Clock not set) is generated.
See Appendix A for details.

MARCH 2000
IOM-NMS-1/05C
Figure 56: Setting the Real Time Clock
Procedure
Step 1: Select the NMS board in the Explorer Tree.
Step 2: Select Configuration in the menu bar.
Step 3: Select Set Real Time Clock from the drop-down menu.
The NMS board clock is now set.
5GVVKPIVJG0/5$QCTF+2#FFTGUU
The NMS board uses PPP to communicate with other equipment, either directly connected, or
connected via a network. Because of this, each NMS board on the network must have its own
unique IP address.
You can use the following procedure to set the IP address for a directly connected NMS
board:
Note: The following procedure assumes that you know the current IP address of the NMS
board, and the IP addresses for all the other NMS boards on the network. Refer to
Section 4 for a simple IP address selection procedure.

MARCH 2000
IOM-NMS-1/05C
Figure 57: Setting the NMS IP Address
Procedure
Step 3: Select IP Address Table from the drop-down menu.
Step 4: Double-click on IP address column entry for the V.24 port listed under the NMS
board, then type in the new address.
Step 5: If the field in the IP Address Mask column for the NMS board IP address is not
255.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 next
to the address, then Start. If the address is incorrect, return to Step 3.
Step 8: When the address has been updated, click Finish.
Step 9: After you have written the new IP address to the NMS board, the connection to the
network will be dropped. DXR NET will then ask you if you wish to reconnect. If
you do wish to reconnect, wait 15 seconds, then select Yes.
Step 10: Select the Commit button in the DXR NET toolbar to save the changes you have
made to the NMS board to the network blueprint.

MARCH 2000
IOM-NMS-1/05C
5GVVKPI7RVJG+2#FFTGUUGUKPVJG0/5$QCTF4QWVKPI6CDNG
You use the Routing Table to set-up the IP routes by which the NMS Board communicates
with other IP devices on the network. You must set-up these routes, otherwise the NMS Board
will not be able to communicate with the network.
You can set the IP addresses of the other devices on the network in the Routing Table using
the following procedure.
Note: The following procedure assumes that you have already selected IP addresses for all
the IP devices on the network. Refer to Section 4 for a simple IP address selection
procedure.
Figure 58: Setting the IP Addresses
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.

MARCH 2000
IOM-NMS-1/05C
Step 5: Take the address of one of the IP devices on the network, make the last field in this
address 1 (eg. for an IP address of 123.123.123.123 the new address would be
123.123.123.1), 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 IP
column
Step 7: For the IP address entered in Step 5, double-click the Interface column, and select
the port you want the NMS board to use for devices on this address from the drop-
down menu.
Step 8: Repeat Steps 4 to 7 until you have entered routes to all the other IP devices on the
network into the Routing Table
Toolbar.
make any further changes to the NMS board configuration, select the Write Configuration
button in the Toolbar. The terminal configuration will now change to reflect the values set in
the blueprint.
8KGYKPIVJG#NCTO5VCVWU
You can view the Alarms page for the NMS Board using the following procedure.

MARCH 2000
IOM-NMS-1/05C
Procedure
Step 2: Select the Alarms page.
Step 3: If the icon in the Alarm Status and Related Information pane is red, click on the icon
to move down the hierarchical alarm levels until the alarm is reached. The alarm
panes.
network personnel.

MARCH 2000
IOM-NMS-1/05C
7UKPI&:40'6YKVJ&:4
)GPGTCN
DXR 700 is a point-to-point digital microwave radio system designed primarily for medium to
long haul, thin route telecommunications networks. It is available in three different
configurations:
Unprotected - this comprises a Radio Modem Adaptor (RMA), a Protection Multiplex

Adaptor (PMA), and a Outdoor Unit (ODU)
Protected & Diversity, Single Antenna - this comprises two RMAs, a PMA, and an ODU
Protected & Diversity, Dual Antenna - this comprises two RMAs, a PMA, and two ODUs
For a more detailed description of DXR 700, refer to DXR 700 Product Description.
Note: Digital Microwave Corporation provides technical training programs for DXR 700
users. Refer to your local Digital Microwave Corporation representative for details.
#DQWV6JKU5GEVKQP
DXR NET to access a DXR 700. It is assumed that before consulting this section, you have
read and understood the material in Sections 2 and 4, particularly the material relating to the
Network Blueprint concept. We also advise that before attempting any of the operations listed
in this section, you have gone through the workspace descriptions contained in the front of
this section.
You can use DXR NET to access and modify the following DXR 700 parameters:
Radio Name
Tx Frequency (MHz)
Rx Frequency (MHz)
Tx Power (dBm)
Forward power upper and lower limits (dBm)
Reverse power lower limits (dBm)
RSSI upper and lower limits (dBm)
Modulation type
Maximum correctable bytes per second threshold
Diversity
Alarm actions
MARCH 2000
IOM-NMS-1/05C
Line interface
7UKPI&:40'6VQKPUVCNNC&:4
+PVTQFWEVKQP
This section covers the operations you should take to configure a new DXR 700 terminal as
part of a network. You can do this in one of two ways:
Note: The terminal should have the correct frequency loaded, and that the network
blueprint (if used) should contains the complete and correct configuration data.
information required to configure the DXR 700 terminals. This blueprint is then used at
the time of installation to load the terminal configurations. Any changes made in the field
can be saved in the blueprint, which now becomes 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, or from the central office. The blueprint
constructed from all the field blueprints is called a Commissioned blueprint, as it reflects
the unique, real, network that is installed.
using configuration sheets. The network installation teams install the terminal, then use
the DXR NET Autodiscovery feature to build a blueprint containing the installed terminal.
They then work through the tabbed pages in the Configuration Workspace, making any
changes required 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 the Field blueprint. The procedure is then the same as for a Field blueprint
created using a master network blueprint.
ABORT BUTTON. Whenever you use DXR NET to make changes to a DXR 700 terminal,
However, if you do this, DXR NET will simply stop sending commands to the terminal. This
can leave the terminal and any associated link(s) in an undesired state, with the terminal
before you start making changes you save the current terminal configuration, and that you


MARCH 2000
IOM-NMS-1/05C
%QPHKIWTKPIC&:4VGTOKPCNHTQOPGYYKVJCOCUVGTDNWGRTKPV
This procedure covers configuring a DXR 700 terminal from a master blueprint. You will use
DXR NET to:

you know what the name of the terminal is in the master blueprint
changes to a DXR 700. For example, writing incorrect frequencies back to the DXR
700 will result in the loss of the operational link, which could require on-site actions
to recover.
Note 2: If you attempt to write default values to a DXR 700, DXR NET will ask you to
confirm the action.
Ethernet.
Procedure
toolbar. After autodiscovery is successfully completed, the terminal you are
attached to will appear in the Explorer Tree window with a small plug symbol.
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. Also note the terminal
frequencies.

MARCH 2000
IOM-NMS-1/05C
Step 4: Select the Disconnect button, then click File in the DXR NET menu bar, and select
Open from the drop-down menu. Load the master blueprint by selecting the
blueprint file, then click the OK button. Check the frequencies given in the
blueprint, and if required, change them to match the ones in the terminal.
Step 5: Enable the autodiscovery feature again by selecting the Connect button from the
DXR NET toolbar. After autodiscovery is successfully completed, the terminal you
are attached to will appear in the Explorer Tree window with a small plug symbol.
Step 7: After you have made and saved any required changes to the blueprint, click the
Write Configuration button in the DXR NET toolbar to load the configuration to the
terminal. DXR NET will open a window asking to proceed. Ensure that you have the
correct terminal selected in the Explorer Tree, and select Start to write to the
terminal.
terminal, and the select the Commissioning Workspace to check if any alarms are
present.
Step 11: When you are finished viewing or modifying the terminal configuration, click on the
Disconnect button in the DXR NET toolbar, then select Exit from the File menu.
%QPHKIWTKPIC&:4VGTOKPCNHTQOPGYYQTMKPIHTQOEQPHKIWTCVKQP
UJGGVU
This procedure covers configuring a DXR 700 terminal working from configuration sheets.
You will use DXR NET to:


MARCH 2000
IOM-NMS-1/05C
you know what the name of the terminal should be
changes to a DXR 700. For example, writing incorrect frequencies back to the DXR
700 will result in the loss of the operational link, which could require on-site actions
to recover.
Note 2: If you attempt to write default values to a DXR 700, DXR NET will ask you to
confirm the action.
Ethernet.
Procedure
toolbar. After autodiscovery is successfully completed, the terminal you are attached
to will appear in the Explorer Tree window with a small plug symbol.
Step 4: Click the Read Configuration button from the DXR NET toolbar to read the terminal
settings into the Configuration workspace.
Step 6: After you have made and saved any changes to the blueprint, click on the Write
Configuration button in the DXR NET toolbar to save the changes to the terminal.
DXR NET will open a window asking to proceed. Ensure that you have the correct
terminal selected in the Explorer Tree, and select Start to write to the terminal.
terminal, and check for alarms to confirm correct operation

MARCH 2000
IOM-NMS-1/05C
should have this blueprint with them , in case a terminal needs to be replaced. This blueprint
Note: Great care should be taken that the parameters are correct before writing any
actions to recover.
5GVVKPIVJG6GTOKPCN(TGSWGPEKGUCPF6TCPUOKVVGT2QYGT
You can change the transmit and receive frequencies and RF output power of a DXR 700
terminal using the following procedure.
SETTING THE TERMINAL FREQUENCIES AND TRANSMITTER POWER. The

terminal frequencies and transmitter output power are dependent on the duplexer in the
DXR 700 ODU. Any software 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.

MARCH 2000
IOM-NMS-1/05C
Figure 60: Modem/RF Link Page
Procedure
Step 3: In the Radio section, change the transmit and receive frequencies, or the transmitter
power by using the up/down arrows in the relevant field, or by selecting the relevant
field and typing in the value.
Toolbar.
blueprint.
5GVVKPIVJG6GTOKPCN2QYGT#NCTO.KOKVU
You can set the values of forward and reverse power which trigger the DXR 700 Forward
Power Warning, and the Reflected Power Warning (see Appendix A for details). The
procedure is as follows:
Note 1: You can set the limits to their default values by clicking the Default button.

MARCH 2000
IOM-NMS-1/05C
Note 2: In a protected terminal, there will be a set of fields for each radio.
Procedure
Step 3: In the Transmit Path section, set the high and low limits for the forward power by
using the up/down arrows in the relevant fields, or by selecting the relevant fields
and typing in the values.
Step 4: In the Transmit Path section, set the high limit for the reverse power by using the
up/down arrows in the relevant field, or by selecting the relevant field and typing in
the value.
Toolbar.
blueprint.

MARCH 2000
IOM-NMS-1/05C
5GVVKPIVJG455+#NCTO.KOKVU
You can set the range over which the RSSI can vary without triggering the Rx Path Warning
alarm (see Appendix A for details). You set the low and high RSSI limits of a terminal using
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: In the Receive Path section, set the high and low limits for the RSSI by using the
up/down arrows in the relevant fields, or by selecting the relevant fields and typing
in the values.
Toolbar.
blueprint.
5GVVKPIVJG6GTOKPCN4(/QFWNCVKQP
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 on
the modem in the DXR 700 RMA. Any changes you make must match the modulation type
of the modem of the RMA that is installed.
Procedure
Step 3: In the Modem Parameters section, select the modulation you require from drop-
down menu displayed when you click-on the Modulation field.
Toolbar.
blueprint.

MARCH 2000
IOM-NMS-1/05C
5GVVKPIVJG/CZKOWO%QTTGEVCDNG$[VGURGT5GEQPF6JTGUJQNF
The Maximum Correctable Bytes per Second Threshold is used to set the number of
correctable bytes that can be received over the radio link before triggering the Correctable
Error Limit alarm (see Appendix A for details).
Note: Refer to Section 4 for a procedure to calculate the number of Correctable Bytes per
Second.
You can change the Maximum Correctable Bytes per Second Threshold of a terminal using
Note: You can set the limit to a default value by clicking the Default button.
Procedure
Step 3: In the General section, set the Correctable Bytes per Second by using the up/down
arrows in the fields, or by selecting the field and typing in the value.
Toolbar.
blueprint.
5GVVKPIVJG6GTOKPCN&KXGTUKV[1RVKQP
You can change the diversity option of a protected terminal using the following procedure.
SETTING THE TERMINAL DIVERSITY OPTION. The diversity you can select is
dependent on the DXR 700 hardware. You must ensure that any changes you make in the
software reflect your terminal hardware.
Note: If you select the Frequency Diversity option, you will have to set the frequencies for
the second radio.
Procedure
Step 3: In the Protected & Diversity Options section, select the option you require by
clicking the relevant radio button. You can choose between Protected, Space
Diversity or Frequency Diversity.

MARCH 2000
IOM-NMS-1/05C
Step 4: If you have selected the Frequency Diversity option, select the frequencies you
require for the two radios in the Radio A and Radio B fields. Refer to Changing the
Terminal Frequencies and RF Power for details.
Toolbar.
blueprint.
You can set the DXR 700 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 1: You can set remote actions that occur on the DXR 700 at the other end of the link.
Note 2: The same actions can be set to more than one event.
The Action Table page is divided into the Events, Mapped Actions and Inherited Actions
panes. The Events pane lists the events that you can set an action for. The events are listed in
the Windows Explorer tree format. The Mapped Actions pane lists any actions that you have
mapped to the alarm presently selected in the Events pane. The Inherited Actions pane lists
any actions which are mapped to an alarm higher up in the tree hierarchy than the alarm you
have currently selected.

MARCH 2000
IOM-NMS-1/05C
Procedure
Step 5: In the Edit Actions window, select the Location (i.e., where you want the alarm
action to be produced) and the Action (i.e., what you want to happen when the event
occurs) from the scroll-bars, then click on the Add Action button next to the menu
window. The action will appear in the lower pane of the window. If you decide to
remove an action after selection, select the action in the lower pane, then click on
the Delete Action button next to the menu window.
Step 6: Select the OK button in the Add Actions window. The window will close and the
action should now be displayed in the Mapped Actions pane of the Actions Table
page.
Toolbar.

MARCH 2000
IOM-NMS-1/05C
blueprint.
You can remove an action you have mapped to an event (see Mapping an Event to an Action)
Procedure
Toolbar.
blueprint.
5GVVKPIVJG6GTOKPCN.KPG+PVGTHCEG6[RG
You can change the terminal type using the following procedure:
CHANGING THE INTERFACE TYPE. The interface type is dependent on the interface
hardware in the DXR 700 Any changes you make to the software must reflect the hardware.

MARCH 2000
IOM-NMS-1/05C
Figure 63: Interface Setup Page
Procedure
Step 3: Click on the Interface Type field in the Interface section and select the interface type
from the displayed drop-down menu.
Toolbar.
blueprint.
5GVVKPI'6[RG.KPG+PVGTHCEG2CTCOGVGTU
SETTING THE LINE INTERFACE PARAMETERS. The interface capacity and the
tributary impedance are both dependent on the hardware in the DXR 700 and the cabling
attached to it. Any changes you make to the software must reflect the terminal hardware
and the cabling attached to the terminal line interface.

MARCH 2000
IOM-NMS-1/05C
Note: Digital Microwave Corporation supplies cabling matched to the line impedance for
the interface connectors on the PMA front panel.
You can change the terminal line parameters using the following procedure:
Figure 64: Interface Setup Page for E1 Interface
Procedure
section.
Step 4: If you wish to change the impedance of a particular tributary, select the relevant
entry in the Impedance column of the table in the Tributary section, then use the
arrow to display the drop-down menu. Select the new impedance from the drop-
down menu.
Step 5: If you wish to change the impedance of all the tributaries to the same value, change
the value of the first tributary as described in Step 4, then click on the Impedance
column heading.

MARCH 2000
IOM-NMS-1/05C
Step 6: If you wish to change the commissioned state of a particular tributary, select the
True or False in the Commissioned column of the table in the Tributary section.
Tributaries set to True are commissioned, tributaries set to False are
uncommissioned.
Step 7: 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 the
Commissioned column heading.
Step 8: For interface capacities of 16xE1, if you wish to change the impedance of the
Wayside Tributary, change the state of the tributary in the Wayside Tributary
section as described in Step 4.
Toolbar.
blueprint.
5GVVKPIVJG'6[RG.KPG+PVGTHCEG2CTCOGVGTU
SETTING THE LINE INTERFACE PARAMETERS. The receiver sensitivity and the
tributary wayside line build-out are both dependent on the hardware in the DXR 700 and
the cabling attached to it. Any changes you make to the software must reflect the terminal
hardware and the cabling attached to the terminal line interface.
the tributary wayside connector on the PMA front panel.
You can change the terminal line interface parameters using the following procedure:

MARCH 2000
IOM-NMS-1/05C
Figure 65: Interface Setup Page for E3 Interface
Procedure
Step 3: If you wish to change the interface receiver sensitivity, select the Rx Sensitivity
column of the table in the Tributary section, then use the arrow to display the drop-
down menu. Select the new sensitivity from the drop-down menu. You can choose
from Low, Medium (default), or High.
Step 4: If you wish to enable or disable the transmitter level boost function in the line
interface, select the Tx Level Boost column of the table in the Tributary section,
then use the arrow to display the drop-down menu. Select True (enabled) or False
(disabled) as required.
Step 5: If you wish to enable or disable the equaliser bypass function in the line interface,
select the Equaliser Bypass column of the table in the Tributary section, then use the
arrow to display the drop-down menu. Select True (enabled) or False (disabled) as
required.
Step 6: If you wish to change the commissioned state of the line interface, select the
Commissioned column of the table in the Tributary section, then use the arrow to
display the drop-down menu. Select True (enabled) or False (disabled) as required.

MARCH 2000
IOM-NMS-1/05C
Step 7: If you wish to change the impedance of the Wayside Tributary, change the state of
the tributary in the Wayside Tributary section as described in Step 7.
Toolbar.
blueprint.
5GVVKPIVJG&56[RG.KPG+PVGTHCEG2CTCOGVGTU
You can change the terminal line interface parameters for a DS1 type interface using the

MARCH 2000
IOM-NMS-1/05C
Figure 66: Interface Setup Page for DS1 Interface
Procedure
Step 3: If you wish to change the line build out of a tributary, select the Line Build Out
column of the table in the Tributary section, then use the arrow to display the drop-
down menu. Select the new build-out from the drop-down menu. You can choose
between lengths of 0-133 feet (default), 133-266 feet, 266-399 feet, 399-533 feet
and 533-655 ft.
Step 4: If you wish to change the commissioned state of a tributary, select the check box in
the Commissioned column of the table in the Tributary section, then use the arrow
to display the drop-down menu. Select True (enabled) or False (disabled) as
required.
Step 5: If you wish to change the coding used on the line interfaces, select the Line
Encoding field in the Tributary section, then use the arrow to display the drop-down
menu. Select the encoding from the drop-down menu.
Step 6: If you wish to change the impedance of the Wayside Tributary, select the column in
the Wayside Tributary section, and select the new build-out from the drop-down
menu. You can choose between lengths of 0-133 feet (default), 133-266 feet, 266-
399 feet, 399-533 feet and 533-655 ft.
Toolbar.
blueprint.
5GVVKPIVJG&56[RG.KPG+PVGTHCEG2CTCOGVGTU
You can change the terminal line interface parameters for a DS3 type interface using the

MARCH 2000
IOM-NMS-1/05C
Figure 67: Interface Setup Page for DS3 Interface
Procedure
column of the top table in the Tributary section, then use the arrow to display the
drop-down menu. Select the new sensitivity from the drop-down menu. You can
choose from Low, Medium (default), or High.
select the Equaliser Bypass column of the table in the Tributary section, then use the
required.
Step 6: If you wish to change the commissioned state of the line interface, select the check
box in the Commissioned column of the table in the Tributary section, then use the
required.

MARCH 2000
IOM-NMS-1/05C
Step 7: If you wish to change the line build out of the wayside tributary, select the Line
Build Out column of the table in the Wayside Tributary section, then use the arrow
to display the drop-down menu. Select the new build-out from the drop-down menu.
You can choose between lengths of 0-133 feet (default), 133-266 feet, 266-399 feet,
399-533 feet and 533-655 ft.
Toolbar.
blueprint.
5GVVKPIVJG56/6[RG.KPG+PVGTHCEG2CTCOGVGTU
You can change the terminal line interface parameters for a STM-0 type interface using the

MARCH 2000
IOM-NMS-1/05C
Figure 68: Interface Setup Page for STM-0 Interface
Procedure
select the check box in the Equaliser Bypass column of the table in the Tributary
section, then use the arrow to display the drop-down menu. Select True (enabled) or
False (disabled) as required.
required.
Step 7: If you wish to change the line impedance of the wayside tributary, select the
Impedance column of the table in the Wayside Tributary section, then use the arrow
to display the drop-down menu. Select the new impedance from the drop-down
menu. You can choose between impedances of 120 ohm (default) and 75 ohm.
Toolbar.
blueprint.
5GVVKPIVJG5656[RG.KPG+PVGTHCEG2CTCOGVGTU
You can change the terminal line interface parameters for a STM-1 type interface using the

MARCH 2000
IOM-NMS-1/05C
Figure 69: Interface Setup Page for STS-1 Interface
Procedure
select the check box in the Equaliser Bypass column of the table in the Tributary
section, then use the arrow to display the drop-down menu. Select True (enabled) or
False (disabled) as required.
required.

MARCH 2000
IOM-NMS-1/05C
Step 7: If you wish to change the line build out of the wayside tributary, select the Line
Build Out column of the table in the Wayside Tributary section, then use the arrow
to display the drop-down menu. Select the new build-out from the drop-down menu.
You can choose between lengths of 0-133 feet (default), 133-266 feet, 266-399 feet,
399-533 feet and 533-655 ft.
Toolbar.
blueprint.
8KGYKPIVJG#NCTOU2CIG
You can view the alarms on the Alarms page using one of the following procedures.
Note: It is assumed that you know what action to take in response to a given alarm.
Figure 70: Commissioning Workspace

MARCH 2000
IOM-NMS-1/05C
Procedure 1
Step 1: Select the Commissioning Workspace.
Step 2: Select the Commissioning page.
Step 3: If the LED icon in the Alarm Status section is red, click on the View Alarms button
to display the Alarms page.
panes.
network personnel.
Procedure 2

MARCH 2000
IOM-NMS-1/05C
panes.
network personnel.
'PCDNKPIVJG6TKDWVCT[.QQRDCEMU
You can enable the tributary loopback functions using the following procedure.
Tributary loopbacks affect all tributaries at once.
Procedure

MARCH 2000
IOM-NMS-1/05C
Step 3: Select the tributary loopback function from the Tributary Loopback section by
clicking on the associated radio button
Warning box.
Step 5: When you have completed your tests, select the No Tributary Loopback radio
button, then Click the Apply button.
'PCDNKPIVJG4(/QFGO.QQRDCEMU
You can enable the RF/Modem loopback functions using the following procedure.
Procedure
Step 3: Select the RF/modem loopback function from the RF/Modem section by clicking on
the associated check box.
Warning box.
Step 5: Compare the input and output bit-streams.
Step 6: When you have completed your tests, deselect the function by clicking the selected
check box.
6GUVKPI2TQVGEVKQP5YKVEJKPI
Note: You can only enable protection switching in a protected DXR 700.
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 3: Select the Manual switching option you require from the Protection Switching
section by clicking on the associated radio button.
Step 4: Select the transmitter or receiver you wish DXR 700 to switch to.

MARCH 2000
IOM-NMS-1/05C
Warning box.
Step 6: When you have completed your tests, reselect the Automatic switching option by
clicking again on the associated radio button.
8KGYKPIVJG%QPUVGNNCVKQP&KCITCO
You can view the Constellation Diagram using the following procedure.
Except for the RSSI Graph page operations, you cannot select other operations while
Constellation Diagram monitoring is in progress.
diagrams. If the Multi-Carrier option is selected in the Advanced option in the Tools
diagrams.
Figure 73: Constellation Page

MARCH 2000
IOM-NMS-1/05C
Procedure
Step 2: Select the Constellation Diagram page.
Step 3: Select the terminals or carriers you wish to monitor by clicking the relevant button
in the Select Terminal section.
terminal or carrier by clicking the Monitor button in the particular Constellation
Diagram for the terminal or carrier.
Step 5: If you wish to clear all the diagrams and restart monitoring click on the Reset All
button in the Select Terminal section. If you wish to clear and restart monitoring for
a particular diagram, click on the Reset button in the diagram.
Step 6: After you have finished monitoring the constellation diagrams, stop monitoring by
clicking on any indented monitoring buttons. Ensure that all the monitoring buttons
are raised before leaving the page.
8KGYKPIVJG455+)TCRJ
You can view the RSSI graph using the following procedure.
Except for the Constellation page operations, you cannot select other operations while RSSI
graphs. If the Multi-Carrier option is selected in the Advanced option in the Tools
graphs.

MARCH 2000
IOM-NMS-1/05C
Figure 74: RSSI Page
Procedure
Step 2: Select the RSSI Graph page.
Step 3: Select the terminals or carriers you wish to monitor by clicking on the relevant
button.
terminal or carrier by clicking the Monitor button in the particular RSSI Graph for
the terminal or carrier.
Step 5: If you wish to clear all the graphs and restart monitoring click on the Reset All
button in the Select Terminal section.
Step 6: If you wish to reset the Max and Min bars for a particular graph, click on the Reset
button in the graph. This will reset the bars to the maximum and minimum RSSI
values recorded since monitoring began, or since the last time you selected the graph
Reset button.
Step 7: After you have finished monitoring the RSSI graphs, stop monitoring by clicking on
any indented monitoring buttons. Ensure that all the monitoring buttons are raised
before leaving the page.

MARCH 2000
IOM-NMS-1/05C
Using DXR NET with the Services Management Adaptor (SMA)
7UKPI&:40'6YKVJVJG5GTXKEGU
/CPCIGOGPV#FCRVQT
5/#
)GPGTCN
The Services Management Adaptor (SMA) provides an interface between DXR NET, the
network management software, and DXR 700 terminals.
The SMA has the following features:
Management and co-ordination of service channels for up to four radios at one location
(can be increased by connecting SMAs together)
Engineering orderwire, complete with handset, providing All station calling omnibus
Industry standard Internet (SNMP, TCP/IP) based interfaces
User programmable external alarm inputs, and/or outputs (alarms can be configured as
ground referenced or isolated)
Ethernet 10 base-T capability, allowing direct connection to a LAN
Two option slots, for data service cards (Alarm or Ethernet AUI options)
Note: Ethernet and data service card options still under development.
For more details on the SMA, refer to DXR 700 Product Description. For details on the
physical and electrical installation and setup procedures for an SMA, refer to DXR 700
Installation, Operation and Maintenance manual.
#DQWV6JKU5GEVKQP
DXR NET to access an SMA.
Sections 2 and 4, particularly the material relating to the Network Blueprint concept.
You can use DXR NET to access and modify the following SMA parameters:
SMA board name

SMA IP address
Routing table for IP network addresses
Primary and secondary clock source
Alarm board inputs and outputs
MARCH 2000
IOM-NMS-1/05C
Remote Alarm actions

EOW earpiece volume, ring mode, TX high pass filter, and PCM law
SMA port configuration
7UKPI&:40'6VQKPUVCNNC5/#
This section covers the operations you should take to configure a new SMA as part of a
network. You can do this in one of two ways:
Note: The network blueprint (if used) should contains the complete and correct
configuration data.
information required to configure the SMA. This blueprint is then used at the time of
installation to load the SMA configuration. Any changes made in the field can be saved
in the blueprint, which now becomes 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, or from the central office. The blueprint constructed
from all the field blueprints is called a Commissioned blueprint, as it reflects the unique,
real, network that is installed.
using configuration sheets. The network installation teams install the terminal with the
board, then use the DXR NET Autodiscovery feature to build a blueprint containing the
installed SMA. They then work through the tabbed pages in the Configuration
Workspace, making any changes required to bring the SMA into line with the values
given in the configuration sheets. The installed configuration should then be saved to a
blueprint, which now becomes the Field blueprint. The procedure is then the same as for a
Field blueprint created using a master network blueprint.
values in DXR NET and re-send them to the affected elements. For these reasons, we
recommend that before you start making changes you save the current element
configuration, and that you have a hard copy of the desired settings available.
REMOTE SMA CHANGES. Some actions can cause the loss of communication to the
remote terminal in a link, requiring manual intervention at the remote terminal to re-
network elements after initial setup and after any changes are made.

MARCH 2000
IOM-NMS-1/05C
%QPHKIWTKPIC5/#HTQOPGYYKVJCOCUVGTDNWGRTKPV
This procedure covers configuring a SMA from a master blueprint. You will use DXR NET to:

use the autodiscovery feature to connect to the SMA
make any required changes to the SMA configuration
the SMA has been installed, connected to power and the antenna, and has been
the DXR NET PC is connected to the Setup connector on the SMA front panel
you know what the IP address of the SMA is in the master blueprint
changes to a SMA.
Note 2: If you attempt to write default values to a SMA, DXR NET will ask you to confirm
the action.
Note 3: You cannot use the autodiscovery feature when connected to the SMA via Ethernet.
Procedure
autodiscovery, and a blueprint of the network containing the SMA you are attached
to will appear in the Explorer Tree window. The SMA you are attached to will have
a small red plug symbol.
Step 4: Set the SMA real time clock and IP address (refer to Setting the Real Time Clock
and Setting the SMA IP Address procedures in this section).
Step 5: Once the new address has been written, the SAM will drop the network connection
to your PC, and DXR NET will ask if you want to reconnect. Select No, then open
the "master" blueprint.

MARCH 2000
IOM-NMS-1/05C
Step 6: Select the Connect button from the DXR NET toolbar. DXR NET will mark the SMA
you are connected to on the Explorer tree with a small red plug symbol. Ensure that
the correct SMA is selected in the tree before attempting to load the configuration
from the blueprint, as loading the configuration to the wrong SMA will have serious
consequences. If the correct SMA is not selected, check the board IP address in the
blueprint, click the Disconnect button in the DXR NET toolbar, then go back to Step
3.
Step 7: After you have ensured the correct SMA is selected, go through each of the tabbed
pages in the Configuration Workspace, making any required changes (refer to the
procedures given later in this section for details). After you have completed any
required changes, click on the Commit button to save them to the blueprint.
to 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 SMA icon in the
the SMA configuration to file.
+PUVCNNKPIHTQOPGYHTQOEQPHKIWTCVKQPUJGGVU
This procedure covers configuring a SMA from configuration sheets. You will use DXR NET
to:

make any required changes to the SMA configuration
save any changes that are made to the SMA configuration for later use
the SMA has been installed, connected to power and the antenna, and has been
the DXR NET PC is connected to the Setup connector on the SMA front panel
you know what the IP address of the SMA should be
changes to a SMA.
Note 2: If you attempt to write default values to a SMA, DXR NET will ask you to confirm
the action.
Note 3: You cannot use the autodiscovery feature when connected to the SMA via Ethernet.

MARCH 2000
IOM-NMS-1/05C
Procedure
attached to will appear in the Explorer Tree window. The SMA you are attached to
will have a small red plug symbol.
Step 4: Set the SMA board real time clock and IP address (refer to Setting the Real Time
Clock and Setting the SMA board IP Address procedures in this section).
Step 5: Once the new IP address has been written, the SMA will drop the network
connection to your PC. DXR NET will then ask if you want to reconnect. Wait 15
seconds, and then select Yes. DXR NET will perform autodiscovery, and a blueprint
of the network containing the SMA you are attached to will appear in the Explorer
Tree window.
Step 6: Select the Read Configuration button from the DXR NET toolbar to read the SMA
configuration details into the blueprint. This will ensure that you are working on the
correct parameters when you make changes.
Step 7: Go through each of the tabbed pages in the Configuration Workspace, making any
required changes (refer to the procedures given later in this section for details).
After you have completed any required changes, click on the Commit button to save
them to the blueprint.
to 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 board icon in the
the SMA configuration to file.
As SMAs are installed and become operational, it is useful to have an updated blueprint at the
central office and in the operations centre. This blueprint should reflect the latest
should have this blueprint with them , in case a SMA needs to be replaced. This blueprint is
known as the "custom" blueprint, and should be created by importing configuration files,
The network operations centre can discover the SMA configurations if the SMA type,
the data directly from the SMAs.
Great care should be taken that the parameters are correct before writing any changes to a
SMA. Writing incorrect parameters back to the SMA could result in the loss of the
operational link, which could require on-site actions to recover.
MARCH 2000
IOM-NMS-1/05C
5GVVKPIVJG5/#4GCN6KOG%NQEM
The SMA has an internal clock to synchronise its operations. You can use the following
procedure to set the Real Time Clock for a directly connected SMA:
Note: If the Real Time Clock is not set, an alarm (Real Time Clock not set) is generated.
See Appendix A for details.
Procedure
Step 1: Select the SMA in the Explorer Tree.
Step 3: Select Set Real Time Clock from the drop-down menu.
The SMA clock is now set.
5GVVKPIVJG5/#$QCTF+2#FFTGUU
The SMA board uses PPP to communicate with other equipment, either directly connected, or
connected via a network. Because of this, each SMA board on the network must have its own
unique IP address.
You can use the following procedure to set the IP address for a directly connected SMA:
Note: The following procedure assumes that you know the current IP address of the SMA.
Refer to Section 4 for a simple IP address selection procedure.
Procedure
Step 1: Select the SMA board in the Explorer Tree.
Step 3: Select IP Address Table from the drop-down menu.
Step 4: Double-click on IP address column entry for the SMA, then type in the new address.
Step 5: If the field in the IP Address Mask column for the SMA IP address is not
255.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 next
to the address, then Start. If the address is incorrect, return to Step 3.
Step 8: When the address has been updated, click Finish.
Step 9: After you have written the new IP address to the SMA, the connection to the
network will be dropped. DXR NET will then ask you if you wish to reconnect. If
you do wish to reconnect, wait 15 seconds, then select Yes.

MARCH 2000
IOM-NMS-1/05C
Step 10: Select the Commit button in the DXR NET toolbar to save the changes you have
made to the SMA to the network blueprint.
The changes you have made will now be reflected in the network blueprint.
%QPHKIWTKPIVJG+2#FFTGUUHQTVJG5/#5GVWR2QTV
You can use the following procedure to set the IP address the SMA Setup Port (the port the
SMA uses to communicate with the PC):
Note 1: The following assumes that you have already changed the SMA IP address from the
default factory setting. If this is not the case, refer to Setting the IP Address for the
SMA, then return to this procedure.
Note 2: We advise you set the IP address for the PC before setting up the routes to any other
equipment.
Figure 75: Routing Table Page
Procedure

MARCH 2000
IOM-NMS-1/05C
Step 3: Take the SMA IP address, make the last field in the address one, then enter this into
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 Setup
from the drop-down menu.
Toolbar.
blueprint.
5GVVKPI7RVJG+2#FFTGUUGUKPVJG5/#$QCTF4QWVKPI6CDNG
You use the Routing Table to set-up the IP routes by which the SMA communicates with
other IP devices on the network. You must set-up these routes, otherwise the SMA will not be
able to communicate with the network.
You can set the IP addresses of the other devices on the network in the Routing Table using
Note: The following procedure assumes that you have already selected IP addresses for all
the IP devices on the network. Refer to Section 4 for a simple IP address selection
procedure.
Procedure
Step 1: Select the SMA in the Explorer Tree.
Step 5: Take the address of one of the IP devices on the network, make the last field in this
address 1 (eg. for an IP address of 123.123.123.123 the new address would be
123.123.123.1), 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 IP
column
Step 7: For the IP address entered in Step 5, double-click the Interface column, and select
the port you want the SMA to use for devices on this address from the drop-down
menu.
Step 8: Repeat Steps 4 to 7 until you have entered routes to all the other IP devices on the
network into the Routing Table
MARCH 2000
IOM-NMS-1/05C
Toolbar.
make any further changes to the SMA configuration, select the Write Configuration button in
the Toolbar. The SMA configuration will now change to reflect the values set in the blueprint.
%QPHKIWTKPIVJG5/#4CFKQ.KPM2QTVU
You can configure the radio link connectors (AUX and V.24) on an SMA front panel using
the following method.
Figure 76: Port and EOW Settings Page
Procedure
Step 2: Select the Port and EOW Settings tabbed page.
Step 3: 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.
Toolbar.

MARCH 2000
IOM-NMS-1/05C
blueprint.
%QPHKIWTKPIVJG'19+PVGTHCEG
You can configure the following:
volume in the EOW handset ear piece

the PCM Coding Law used to translate analogue voice signals into digital pulses for
transmission over DXR 700 auxiliary channel
the ringing tones produced by the SMA, and
whether the analogue voice signal from the handset is high pass filtered or not
You can configure the EOW interface using the following method.
Procedure
Step 3: In the Engineering Order Wire (EOW) section, click on the Ear Piece Volume field,
and select the volume from the drop-down menu. You can choose between Normal
and Loud.
Step 4: In the Engineering Order Wire (EOW) section, click on the PCM Coding Law field,
and select the coding law from the drop-down menu. You can choose between Law
and A-Law.
Step 5: In the Engineering Order Wire (EOW) section, click on the Ring Modes field, and
select the ringing tone to be generated by the SMA from the drop-down menu. You
can choose DXR 700 (default), DXR 200 and DXR 100 tones.
Step 6: In the Engineering Order Wire (EOW) section, enable or disable the Transmit High
Pass Filter by clicking on the check box. The function is disabled when the box is
empty, and enabled when the box is ticked.
Toolbar.
blueprint.
5GVVKPIWRVJG5/#%NQEM5QWTEG
You can set up the SMA clock source using the following method.

MARCH 2000
IOM-NMS-1/05C
Note: For either of the Option 1 or Option 2 selections to be valid, ie, synchronisation
signal coming in via optional daughter board, the relevant slot in the SMA must be
occupied by an appropriate board.
Procedure
Step 3: In the Clock Sources section, click on the Primary field, and select the signal source
from the drop-down menu. 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.
Step 4: In the Clock Sources section, click on the Secondary field, and select the signal
source from the drop-down menu. 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.
Toolbar.
Note: You can set local SMA events to trigger alarms at a remote SMA, but the maximum
number of remote alarms is limited to 30.

MARCH 2000
IOM-NMS-1/05C
Procedure
Step 5: In the Edit Actions window, select the action and the location you want it to occur
from the drop-down menu, then click on the Add Action button. The action will
appear in the lower pane of the window.
Step 6: If you decide not to proceed with adding this action, select the action in the lower
pane, and click the Delete button. If you are happy with your selection, select the
OK button in the Add Actions window. The window will close and the action
should now be displayed in the Mapped Actions pane of the Actions Table page.
Toolbar.

MARCH 2000
IOM-NMS-1/05C
blueprint.
You can remove an action from a specific event using the following procedure:
Procedure
Toolbar.
blueprint.
5GVVKPI7R'ZVGTPCN#NCTOU
You can setup an external alarm on the SMA using the following procedure:
Note 1: For an output signal with isolated outputs selected (see Step 3), the Type field is set
automatically to output.
Note 2: For either signal, changing from the default setting in the Electrical Status field
requires you to alter switch settings in the SMA, and also links in the SMA for
output signal changes.
Note 3: You must select a number between zero and twenty in the Rate field, and you must
select an integer value.

MARCH 2000
IOM-NMS-1/05C
Figure 78: External I/O Page
Procedure
Step 2: Select the External Inputs/Outputs page.
Step 3: If the alarm signal is to be isolated, select the Isolated check box associated with the
alarm channel at the far right of the page.
Step 4: Double-click on the Identifier field, and type in the name of the alarm.
Step 5: Double-click on the Type field, and select Input or Output from the drop-down list.
Step 6: Double-click on the Electrical State field, and select the appropriate setting from the
drop-down list. You can choose between current and no current.
Step 7 Select the maximum number of changes to the signal that can be detected per second
by clicking on the Rate field, and either using the up/down arrows, or typing in the
value.
Toolbar.
blueprint.
MARCH 2000
IOM-NMS-1/05C
8KGYKPI#NCTOU
You can view the alarms on the Alarms page using the following procedures.
Note: It is assumed that you know what action to take in response to a given alarm.
Procedure
panes.
network personnel.

MARCH 2000
IOM-NMS-1/05C
Using DXR NET with SDM Boards
7UKPI&:40'6YKVJ5&/$QCTFU
)GPGTCN
This section covers how to use DXR NET to set up a data circuit between SMA using the
optional Serial Data Modem (SDM) boards. Such a circuit would be to allow communication
between data monitoring equipment and a remote management workstation. The circuit
comprises the SMAs containing the boards and any SMAs required to connect them.
DXR 700 DXR 700 DXR 700 DXR 700
AUX B AUX B AUX A AUX A
SMA SMA SMA

SDM SDM
SDM DATA CIRCUIT

MANAGEMENT DATA MONITORING
WORKSTATION EQUIPMENT
Figure 80: SDM Data Circuit Block Diagram

To set up the circuit, you need to:
configure SMA at either end of the link to use the boards

set-up the cross-connects in any SMA used to carry the circuit between the SMA with the
SDM boards
5&/$QCTFU
The SDM boards allow serial data communications over the NMS Overhead channel of the
SMA. 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, therefore each SMA can
have up to two boards.
MARCH 2000
IOM-NMS-1/05C
Note: A SMA can have any combination of boards.
SERIAL SERIAL
DATA SMA SMA DATA
SDM SDM
AUX AUX
TRAFFIC DXR 700 DXR 700 TRAFFIC
Figure 81: SDM SMA to SMA Communication Block Diagram
%TQUUEQPPGEVU
Unless the two SMA at each end of the circuit are in direct communication with one another,
ie. at the opposite ends of the same radio link, you will have to connect the data circuit via
other SMA. You do this by setting up an internal cross-connects in each of the connecting
SMA. This governs which ports on the SMA are used to connect the circuit.
Note: The ports you can use will depend on what other functions the SMA is providing.
DXR 700 DXR 700 DXR 700 DXR 700
AUX AUX AUX AUX
SMA SMA SMA

SDM SDM
CROSS-CONNECT SMA
Figure 82: SDM Cross-connect SMA Block Diagram
%QOOKUUKQPKPI9QTMURCEG
5/#&GVCKNU
The SMA Details tabbed page in the Commissioning Workspace now has the following
additional sections.
Option Slot 1
Option Slot 2

MARCH 2000
IOM-NMS-1/05C
Option Slot Sections

Depending on the type of board inserted into their associated slot, the Option Slot sections
can contain the following fields:
Note: The Board ID text field will always be present, but the other three fields are only
present when either a low speed or high speed daughter board has been inserted into
the appropriate slot.
Board ID text
Part Number
Serial Number
Software Version
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 are
self-explanatory.
/CKPVGPCPEG9QTMURCEG
The Maintenance Workspace has the following tabbed pages:
Alarms
SMA Details
#NCTOU
The Alarms page now has the additional alarms described under the Action Table heading in
the Configuration Workspace section.
5/#&GVCKNU
The changes to the SMA Details tabbed page are as described in the Commissioning
Workspace section.
5GVVKPIWRC5GTKCN&CVC%KTEWKVYKVJ5&/DQCTFU
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
An outline of the procedure is as follows:
MARCH 2000
IOM-NMS-1/05C
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 have both timeslots and free data
capacity to support the boards.
Step 4: Identify any SMA required to relay the data circuit, and check that they have ports
available 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 SMAs.
Step 7: Test the data circuit to see that it can carry the required data.
%QPHKIWTKPIC.QY5RGGF&CWIJVGT$QCTFKPCP1RVKQP2CIG
You can use the following procedure to configure a Low Speed Daughter Board in an Option
Page.
Note: We advise that you have read and understood the material under the Option Pages
headings in the Configuration Workspace before attempting to use this procedure.
Pay special attention to any restrictions on the values you can select, both on the
current 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 Daughter
Board from the drop-down menu.
Step 5: Click on the arrow in the Cross connect to field, and select the AUX port on the
SMA 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 you
want 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 the
appropriate Circuit section. Click on the arrow in the Mode field, and select the
circuit 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 this
value does not contradict the values set in the Channel field, or the settings on any
other board.

MARCH 2000
IOM-NMS-1/05C
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 this
value does not contradict the values set in the Channel field, or the settings on any
other board. You can also select values for the Data Bits, Stop bits, Bit shave and
Parity 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 SMA, and then select the Port and EOW Settings tabbed page in
the Configuration Workspace. In the Clock Sources section, click on the Primary
field, and select Free-running. Then click on the Secondary field, and select the
AUX 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, and
then 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 port
that the SDM uses to communicate with the remote SDM. Then click on the
Secondary field, and select Free-running.
Toolbar.
the Toolbar. The configuration of the SDM daughter board in the SMA will now change to
reflect the values set in the blueprint.
%QPHKIWTKPIC*KIJ5RGGF&CWIJVGT$QCTFKPCP1RVKQP2CIG
You can use the following procedure to configure a High Speed Daughter Board in an Option
Page.
Procedure
Step 4: Click on the arrow in the Option Board Type field, and select High Speed Daughter
Board from the drop-down menu.
Step 6: Click on the arrow in the Channel field, and select the channel on the AUX port you
want the board data stream to start at from the drop-down menu.

MARCH 2000
IOM-NMS-1/05C
Step 7: Select the Active check box in the Circuit 1 section. Click on the arrow in the Data
Rate 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 timeslot field, or
the settings on any other board.
Toolbar.
%QPHKIWTKPIC%QFKTGEVKQPCN&CWIJVGT$QCTFKPCP1RVKQP2CIG
You can use the following procedure to configure a Co-directional Daughter Board in an
Option Page.
Procedure
Step 4: Click on the arrow in the Option Board Type field, and select Co-directional
Daughter Board from the drop-down menu.
Step 6: Click on the arrow in the Start at timeslot field, and select the timeslot on the AUX
port you want the board data stream to start at from the drop-down menu.

MARCH 2000
IOM-NMS-1/05C
Toolbar.
5GVVKPI7R/CPWCN%TQUUEQPPGEVUKPVJG%TQUUEQPPGEVU2CIG
You can use the following procedure to set up the cross-connects required to relay data
streams between SDM boards in other SMA. These cross-connects are made between any two
available AUX port channels.
Note: We advise that you have read and understood the material under the Cross-connect
Pages heading in the Configuration Workspace before attempting to use this
procedure. Pay special attention to any restrictions on the connections you can
select.
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 to
select the AUX port channels you wish to cross-connect, then click the left mouse
button.
Step 5: To remove a manual cross-connect, move the mouse on the cross-connect grid to
select the cross-connected channels, then click the left mouse button.
Toolbar.
make any further changes, select the Write Configuration button in the Toolbar. The
configuration of the SMA will now change to reflect the values set in the blueprint.

MARCH 2000
IOM-NMS-1/05C
Appendix A: Alarms
#RRGPFKZ##NCTOU
)GPGTCN
This appendix contains descriptions of the alarms that can be generated in DXR NET by the
following network elements:
DXR 100
NMS board
DXR 700
SMA
0QP2TQVGEVGF&:4#NCTO&GUETKRVKQPU
)GPGTCN
DXR 100 alarms are viewed in the Alarms page. This is divided into two panes. The left-hand
pane, Alarm Status and Related Information, lists all possible alarms in the Windows Explorer
tree format. This has the alarms grouped in hierarchical levels under the units currently
present in the link or terminal.
You can move through the levels by double clicking on a unit listing to display the sub-unit
and alarm listing under it. Each unit or alarm listing has an LED icon next to it. For an unit
listing, the icon indicates whether there are any alarms present in the unit or any sub-units
under it. For an alarm 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 Alarm Status and Related Information pane to detect when an alarm is present on an unit,
and then to track the alarm to a particular component.
The alarm status indicated by the icons is given in the following table.
%QNQWT /GCPKPI
$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.
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

MARCH 2000
IOM-NMS-1/05C
Appendix A: Alarms
Alarm Description
Alarm Type
Alarm Severity
The Alarm Name field contains the name of the alarm as shown in the left-hand pane. The
Alarm Description contains the probable cause of the alarm.
The Alarm Type field entries are described in the following table.
#NCTO6[RG &GUETKRVKQP
'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 DXR 100 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.
#NCTO5GXGTKV[ &GUETKRVKQP
%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 fault
occurs.
/CLQT Indicates a condition affecting user traffic that requires
corrective action.
%TKVKECN Indicates a condition affecting user traffic that requires
immediate corrective action.
0247PKV#NCTO
The NPR (Non-protected Radio) Unit Alarm is the top-most alarm in the DXR 100 Alarm tree
hierarchy. When the NPR Unit Alarm is active, it indicates an alarm is present on the DXR
100. The alarms that can trigger the NPR Unit Alarm can be grouped into the following types:
Hardware
Software
Maintenance
Traffic
Modem
Radio link

MARCH 2000
IOM-NMS-1/05C
Appendix A: Alarms
*CTFYCTG
This indicates that a hardware alarm is present on the DXR 100. The alarms that can trigger
the hardware alarm can be grouped into the following types:
Component failure
Power supply
Internal temperature
Alarm inputs
Component Failure
This indicates a component failure has occurred in the DXR 100. It is classed as a minor
alarm, of the equipment type.
Power Supply
This indicates one or more of the three power supplies used in the DXR 100 is operating
outside of the normal threshold limits. The three possible power supply alarms are shown in
the following table.
#NCTO 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP

0COG 5GXGTKV[
+5V digital Warning Equipment The +5V digital supply is outside of
supply the normal operating upper and lower
thresholds.
+5V analog Warning Equipment The +5V analog supply is outside of
supply the normal operating upper and lower
thresholds.
10V supply Warning Equipment The 10V supply is outside of the
normal operating upper and lower
thresholds.
Internal Temperature
This indicates the temperature inside the DXR 100 chassis is outside the normal operating
upper and lower thresholds. It is classed as a warning alarm, of the environmental type.
Alarm Inputs
This indicates one or both of the two external alarm inputs to the DXR 100 is active. The two
possible alarms are shown in the following table.
Note: The perceived severity of alarm board input alarms will be user configurable in the
future.

0COG 5GXGTKV[
Alarm Inputs 1 Warning Equipment External alarm input 1 is present.
Alarm Inputs 2 Warning Equipment External alarm input 2 is present.

MARCH 2000
IOM-NMS-1/05C
Appendix A: Alarms
5QHVYCTG
This indicates that one or more software alarms are present on the DXR 100. The possible
alarms are shown in the following table.

0COG 5GXGTKV[
Configuration Major Processing Corruption of the configuration data
corrupt error has been detected.
Settings not valid Major Processing The configuration does not match the
error hardware capability.
Software/hardware Major Processing The software is not fully compatible

incompatible error with the hardware.
Software resources Minor Processing Insufficient memory for the software

low error to operate correctly.
/CKPVGPCPEG
This indicates that one or more maintenance alarms are present on the DXR 100. They
comprise:
Traffic
Modulation
RF
Traffic
This indicates that one or more traffic related alarms are present on the DXR 100. The
#NCTO0COG 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP

5GXGTKV[
AIS output Warning Communication AIS is enabled on all outgoing
enabled s tributaries.
Trib radio Warning Communication The radio facing loopback is
facing loopback s enabled for one or more tributaries.
active
Trib line facing Warning Communication The line facing loopback is enabled
loopback active s for one or more tributaries.
Modulation
This indicates that one or more modulation alarms are present on the DXR 100. The possible

5GXGTKV[
IF loopback Warning Communication The IF loopback is enabled.
active s
Digital loopback Warning Communication The digital loopback is enabled.
active s

MARCH 2000
IOM-NMS-1/05C
Appendix A: Alarms
FEC disabled Warning Communication Forward Error Correction is

s disabled
RF
This indicates that one or both RF related alarms are present on the DXR 100. The possible

5GXGTKV[
RF loopback Warning Communication The RF loopback is enabled.
active s
TX PA muted Warning Communication The TX PA is muted.
s
6TCHHKE
This indicates that one or more traffic related alarm conditions are present on the DXR 100.
They comprise:
Trib port
Trib n
Trib Port
This indicates that a traffic related alarm is present on one of the DXR 100 Tributary ports.
Trib n
This indicates one of the three possible alarms is present on the Tributary port n of the DXR
100. The three possible alarms are shown in the following table.

5GXGTKV[
LOS Critical Communication Loss of signal has occurred. The
s probable cause is a disconnected
Tributary cable.
AIS Warning Communication AIS is being detected.
s
Uncommissione Warning Communication Traffic is being received on this
d traffic s uncommissioned Tributary port.
/QFGO
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 Failure
This 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, Demodulator not locked, which is present when the modem
demodulator is out of lock. This is classed as a critical alarm, of the communications type.

MARCH 2000
IOM-NMS-1/05C
Appendix A: Alarms
RX Path Warning
This indicates one of two possible modem related alarms, due to the detection of errors in the
received data, is present on the DXR 100. The two possible alarms are shown in the following
table.
#NCTO0COG 2GTEGKXGF #NCTO 2TQDCDNG%CWUG&GUETKRVKQP

5GXGTKV[ 6[RG
Correctable Warning Quality of The number of correctable bytes detected in the
error limit service last second exceeds the user configured upper
threshold.
Uncorrectable Warning Quality of Uncorrectable blocks are being detected.
errors service
4CFKQNKPM
This indicates that a radio link related alarm is present on the DXR 100.
Link failure
This indicates one or more of the radio link failure alarms is present on the DXR 100. These
comprise:
TX Path Failure
RX Path Failure
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 Synthesiser not locked. This is classed as a critical alarm, of
the 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 Synthesiser not locked. This is classed as a critical alarm, of
an invalid RX frequency has been configured

the upconverter module in the DXR 100 is faulty
Link Warning
This indicates one or more of the radio link warning alarms is present on the DXR 100. These
comprise:
TX Path Warning
RX Path Warning
The TX Path Warning alarm indicates that one or both of the following alarm is present on
the DXR 100.

5GXGTKV[
Forward Warning Equipment The TX forward power is outside the user
power configured upper and lower thresholds.

MARCH 2000
IOM-NMS-1/05C
Appendix A: Alarms
Reflected Warning Equipment The TX reflected power is above the user

power configured upper threshold. The probable
cause is a faulty antenna.
The RX Path Warning alarm indicates that the AGC alarm is present on the DXR 100. This
indicates that the AGC is outside the user configured upper and lower thresholds. It is classed
as a Warning, of the Communications type.
&:40/5$QCTF#NCTO&GUETKRVKQPU
)GPGTCN
When a DXR 100 is equipped with the NMS board, the following additional alarms can be
present.
Note: The procedure for viewing the NMS board alarms and determining their status is as
described under the previous Non Protected DXR 100 Alarm Descriptions heading.
0/5$QCTF#NCTO
The NMS (Network Management Systems) Board Alarm is the top-most alarm in the NMS
Board Alarm tree hierarchy. When it is present, it indicates an alarm is present on the NMS
board. The alarms that can trigger the NMS Board Alarm can be grouped into the following
types:
Hardware
Software
Maintenance
Radio communication
*CTFYCTG
The Hardware alarm indicates that the Component failure alarm is present on the NMS board.
Component Failure
This is present when the UART Failure alarm has been detected. This alarm is classed as a
minor alarm, of the equipment type, and is present when a fault has been detected on the NMS
board UART.
5QHVYCTG
This indicates that one or more software alarms are present on the NMS board. The possible

0COG 5GXGTKV[

MARCH 2000
IOM-NMS-1/05C
Appendix A: Alarms


Date and time not Minor Processing The software clock date and time has
set error not been set.
/CKPVGPCPEG
This indicates that NMS Radio Loopback alarm is present on the NMS Board. This is classed
as a minor alarm, of the equipment type. It is classed as a Warning alarm, of the
communications type, and is present when a loopback is enabled on a radio port NMS
channel.
4CFKQ%QOOWPKECVKQP
This is present when the Local Radio alarm is detected. This in turn indicates the NPR alarm
is present, which means that NMS board communications with the local radio have been lost.
This is classed as a major alarm, of the communications type.
&:44/##NCTO&GUETKRVKQPU
)GPGTCN
The procedure for viewing the DXR 700 alarms and determining their status is as described
under the previous Non Protected DXR 100 Alarm Descriptions heading.
4/#7PKV#NCTO
The RMA (Radio Modem Adaptor) Unit Alarm is the top-most alarm in the DXR 700 RMA
Alarm tree hierarchy. When the RMA Unit Alarm is active, it indicates an alarm is present on
the RMA. The alarms that can trigger the RMA Unit Alarm can be grouped into the following
types:
Hardware
Software
Maintenance
Modem
*CTFYCTG
This indicates that a hardware alarm is present on the DXR 700. The alarms that can trigger
the hardware alarm can be grouped into the following types:
Component failure

MARCH 2000
IOM-NMS-1/05C
Appendix A: Alarms
Power supply
Internal temperature
Alarm inputs
Component Failure
This indicates a component failure has occurred in the DXR 700. It is classed as a minor
alarm, of the equipment type.
Power Supply
This indicates one or more of the three RMA power supplies is operating outside of the
normal threshold limits. The three possible power supply alarms are shown in the following
table.

0COG 5GXGTKV[
+5V supply Warning Equipment The +5V supply is outside of the
thresholds.
thresholds.
-48V ODU Warning Equipment The -48V supply to the ODU is
supply outside of the normal operating upper
and lower thresholds.
Temperature
This indicates the temperature inside the RMA chassis is outside the normal operating upper
and lower thresholds. It is classed as a warning alarm, of the environmental type.
5QHVYCTG

0COG 5GXGTKV[
Configuration Major Processing Corruption of the RMA configuration
corrupt error data has been detected.
Settings not valid Major Processing The RMA configuration does not
error match the hardware capability.
Software/hardware Major Processing The RMA software is not fully

incompatible error compatible with the hardware.
Software resources Minor Processing Insufficient memory for the RMA

low error software to operate correctly.
ODU Major Equipment The RMA has lost communications

communications with the ODU.
lost

MARCH 2000
IOM-NMS-1/05C
Appendix A: Alarms
/CKPVGPCPEG
This indicates that one or more maintenance alarms are present on the RMA. The possible

0COG 5GXGTKV[
IF loopback active Warning Communication The IF loopback is enabled on the
s RMA.
Digital loopback Warning Communication The digital loopback is enabled on
active s the RMA.
Modulation Warning Communication The modulation is disabled on one or
disabled s more of the installed modem
modules on the RMA.
/QFGO
This indicates that one or more modem related alarm conditions are present on the RMA.
They comprise:
TX path failure
RX path failure
RX path warning
TX Path Warning
This indicates that one or more modem alarm conditions, resulting in loss of the TX path, are
present on the RMA. The two possible alarms are shown in the following table.

5GXGTKV[
Modulator not Major Communications One or more of the RMA modulators is
locked out of lock.
TX alignment Major Communications The RMA TX alignment multiplexer
multiplexer cannot synchronise to incoming data from
lost sync the PMA.
RX Path Failure
This indicates that one or more alarm conditions, resulting in the loss of the RX path, are
present on the RMA. The two possible alarms are shown in the following table.

5GXGTKV[
Demodulator Major Communications One or more of the RMA demodulators is
not locked out of lock.
RX alignment Major Communications The RX alignment multiplexer cannot

multiplexer synchronise to incoming data from the
lost sync demodulators.

MARCH 2000
IOM-NMS-1/05C
Appendix A: Alarms
RX Path Warning
This indicates one of two possible modem related alarms, due to the detection of errors in the
received data, is present on the RMA. The two possible alarms are shown in the following
table.
#NCTO0COG 2GTEGKXGF #NCTO 2TQDCDNG%CWUG&GUETKRVKQP

5GXGTKV[ 6[RG
Correctable Warning Quality of The number of correctable bytes detected in the
error limit service last second exceeds the user configured upper
threshold.
Uncorrectable Warning Quality of Uncorrectable blocks are being detected.
errors service
&:42/##NCTO&GUETKRVKQPU
)GPGTCN
The procedure for viewing the DXR 700 PMA alarms and determining their status is as
2/#7PKV#NCTO
The PMA (Protection Multiplex Adaptor) Unit Alarm is the top-most alarm in the DXR 700
PMA Alarm tree hierarchy. When the PMA Unit Alarm is active, it indicates an alarm is
present on the PMA. The alarms that can trigger the PMA Unit Alarm can be grouped into the
following types:
Hardware
Software
Maintenance
Traffic
Radio link
Tx switch
*CTFYCTG
This indicates that a hardware alarm is present on the PMA. The alarms that can trigger the
hardware alarm can be grouped into the following types:
Component failure
Power supply
Component Failure
This indicates a component failure has occurred in the PMA. It is classed as a minor alarm, of
the equipment type.
Power Supply
This indicates one or both of the PMA power supplies is operating outside of the normal
threshold limits. The possible power supply alarms are shown in the following table.
MARCH 2000
IOM-NMS-1/05C
Appendix A: Alarms

0COG 5GXGTKV[
thresholds.
thresholds.
5QHVYCTG

0COG 5GXGTKV[
Configuration Major Processing Corruption of the RMA configuration
Settings not valid Major Processing The RMA configuration does not
Software/hardware Major Processing The RMA software is not fully

Software resources Minor Processing Insufficient memory for the RMA

/CKPVGPCPEG
This indicates that one or more maintenance alarms are present on the PMA. The possible

5GXGTKV[
AIS output Warning Communication AIS is enabled on all outgoing
enabled s tributaries.
Trib radio Warning Communication The radio facing loopback is
facing loopback s enabled for one or more tributaries.
active
Trib line facing Warning Communication The line facing loopback is enabled
loopback active s for one or more tributaries.
Manual TX path Warning Communication TX protection switching is locked
enabled s on manual
Manual RX path Warning Communication RX protection switching is locked
enabled s on manual
6TCHHKE
This indicates that one or more traffic related alarm conditions are present on the PMA. They
comprise:
Trib port

MARCH 2000
IOM-NMS-1/05C
Appendix A: Alarms
Trib n
Trib Port
This indicates that a traffic related alarm is present on one of the PMA Tributary ports.
Trib n
This 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.

5GXGTKV[
LOS Critical Communication Loss of signal has occurred. The
s probable cause is a disconnected
Tributary cable.
AIS Warning Communication AIS is being detected.
s
Uncommissione Warning Communication Traffic is being received on this
d traffic s uncommissioned Tributary port.
4CFKQNKPM
This indicates that a radio link related alarm is present on the PMA. These comprise:
Link failure
Received bitstream errors
Link failure
This indicates one or more of the radio link failure alarms is present on the PMA. These
comprise:
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. This
is 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. This
is classed as a critical alarm, of the equipment type.
Received Bitstream Errors

This 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.
6:5YKVEJ
This indicates that one or more TX path protection switching alarms is present on the PMA.
These comprise:
Switch oscillation limit

Cannot switch
MARCH 2000
IOM-NMS-1/05C
Appendix A: Alarms
Switch Oscillation Limit

The Switch Oscillation Limit alarm indicates that the maximum number of protection
switches within a given time period has occurred.. This is classed as a minor alarm, of the
equipment type.
Cannot Switch
The Cannot Switch alarm indicates that the TX path cannot switch to the standby RMA/ODU
chain. This is classed as a minor alarm, of the equipment type. The most probable cause is
that an alarm condition is active on the standby chain.
&:41&7#NCTO&GUETKRVKQPU
)GPGTCN
The procedure for viewing the DXR 700 ODU alarms and determining their status is as
1&77PKV#NCTO
The ODU (Outdoor Unit) Unit Alarm is the top-most alarm in the DXR 700 ODU Alarm tree
hierarchy. 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
Radio link
*CTFYCTG
This indicates that a hardware alarm is present on the ODU. The alarms that can trigger the
hardware alarm can be grouped into the following types:
Component failure
Power supply
Component Failure
This indicates a component failure has occurred in the ODU. It is classed as a minor alarm, of
the equipment type.
Power Supply
This indicates one or both of the ODU power supplies is operating outside of the normal
threshold limits. The possible power supply alarms are shown in the following table.

0COG 5GXGTKV[
thresholds.

MARCH 2000
IOM-NMS-1/05C
Appendix A: Alarms

thresholds.
Temperature
This indicates that one or both of the temperature alarms is present on the ODU. The possible

0COG 5GXGTKV[
Internal Warning Environmental The ODU internal temperature is
Temperature outside of the normal operating upper
PA Warning Environmental The ODU PA heat sink temperature is
Temperature outside of the normal operating upper
5QHVYCTG

0COG 5GXGTKV[
Configuration Major Processing Corruption of the ODU configuration
Settings not valid Major Processing The ODU configuration does not
Software/hardware Major Processing The ODU software is not fully

Software resources Minor Processing Insufficient memory for the ODU

/CKPVGPCPEG
This indicates that one or more maintenance alarms are present on the PMA. The possible

5GXGTKV[
RF loopback Warning Communication The RF loopback is enabled.
active s
TX PA muted Warning Communication The TX PA is muted.
s
4CFKQ.KPM
This indicates that a radio link related alarm is present on the ODU. These comprise:
Link failure
Link warning

MARCH 2000
IOM-NMS-1/05C
Appendix A: Alarms
Link failure
This indicates one or more of the radio link failure alarms is present on the ODU. These
comprise:
TX Path Failure
RX Path Failure
The TX Path Failure alarm indicates that a TX path failure alarm is present on the ODU. It
has a single alarm under it, TX Synthesiser not locked. This is classed as a major alarm, of the
equipment type. The two most probable causes of this alarm are:
an invalid TX frequency has been configured

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, RX Synthesiser not locked. This is classed as a major alarm, of
an invalid RX frequency has been configured

the downconverter module is faulty
Link Warning
This indicates one or more of the radio link warning alarms is present on the DXR 700. These
comprise:
TX Path Warning
RX Path Warning
The TX Path Warning alarm indicates that one or both of the following alarm is present on
the DXR 700.

5GXGTKV[
Forward Warning Equipment The TX forward power is outside the user
power configured upper and lower thresholds.
Reflected Warning Equipment The TX reflected power is above the user

power configured upper threshold. The probable
cause is a faulty antenna.
IF Cable ALC Minor Equipment The TX IF Cable ALC is outside of the normal
operating upper and lower thresholds. The
probable cause is the RMA/ODU cable is
damaged.
The RX Path Warning alarm indicates that the RSSI alarm is present on the DXR 700. This
indicates that the RSSI is outside the user configured upper and lower thresholds. It is classed
as a Warning, of the Communications type.

MARCH 2000
IOM-NMS-1/05C
Appendix A: Alarms
5/##NCTO&GUETKRVKQPU
)GPGTCN
The procedure for viewing the SMA alarms and determining their status is as described under
the previous Non Protected DXR 100 Alarm Descriptions heading.
5/#7PKV#NCTO
The SMA (Services Management Adaptor) Unit Alarm is the top-most alarm in the SMA
Alarm tree hierarchy. When the SMA Unit Alarm is active, it indicates an alarm is present on
the SMA. The alarms that can trigger the SMA Unit Alarm can be grouped into the following
types:
Hardware
Alarm Board
Software
Maintenance
Traffic
Radio Communication
*CTFYCTG
The Hardware alarm indicates that the Component failure alarm is present on the SMA.
Component Failure
This indicates that one or more of the following alarms is present.

5GXGTKV[
EOW board Minor Equipment A fault has been detected on the SMA EOW
Board.
Ethernet Minor Equipment A fault has been detected on the SMA
Ethernet hardware.
UART Minor Equipment A fault has been detected in the SMA UART.
Alarm board Warning Equipment The SMA Alarm Board is expected but cannot
not installed be detected.
#NCTO$QCTF
The Alarm Board alarm indicates that one or more of the following alarms is present.
Note: At present, there is no support for Local Radio n and Remote Radio n alarms. These
may be supported in a future release of DXR NET, DXRproxy and SMA system
software.

5GXGTKV[
Ground Warning Equipment Alarm Board ground referenced input 1a is
referenced active.
MARCH 2000
IOM-NMS-1/05C
Appendix A: Alarms
input 1a
Ground Warning Equipment Alarm Board ground referenced input 1b is
referenced active.
input 1b
referenced active.
input 2a
referenced active.
input 2b
referenced active.
input 3a
referenced active.
input 3b
referenced active.
input 4a
referenced active.
input 4b
referenced active.
input 5a
referenced active.
input 5b
referenced active.
input 6a
referenced active.
input 6b
Isolated input Warning Equipment Alarm Board isolated input 1 is active.
1
2
3
4
5
6
5QHVYCTG
This indicates that one or more software alarms are present on the SMA. The possible alarms
are shown in the following table.

MARCH 2000
IOM-NMS-1/05C
Appendix A: Alarms

0COG 5GXGTKV[


Date and time not Minor Processing The software clock date and time has
set error not been set.
/CKPVGPCPEG
This indicates that one or both of the maintenance alarms are present on the SMA. The

0COG 5GXGTKV[
AUX loopback Warning Communication An AUX port loopback is enabled
active s for one or more AUX ports on the
SMA
Ethernet test mode Warning Communication Ethernet test mode is active on the
active s SMA
6TCHHKE
This indicates that one or more traffic related alarm conditions are present on the SMA. They
comprise:
AUX port
NMS port
V.24 port
AUX Port
This indicates that one or more of the AUX n alarms is present on the SMA. n is the AUX
port 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 the
SMA (n = A, B, C, or D). 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.
NMS Port
This indicates that one or more of the NMS n alarms is present on the SMA. n is the port
identifier, either IN or OUT.

MARCH 2000
IOM-NMS-1/05C
Appendix A: Alarms
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.
V.24 Port
This indicates that one or more of the V.24 n alarms is present on the SMA. n is the port
identifier, either A, B, C or D.
The V.24 n alarm indicates one or both of the following alarms is present.

0COG 5GXGTKV[
Connection failure Major Communication NMS connection failure with the
s device on this V.24 port has
occurred. The probable cause is a
disconnected V.24 port cable.
Unexpected unit Warning Communication NMS traffic is being received from
s an unexpected unit on this V.24 port.
4CFKQ%QOOWPKECVKQP
This indicates that one or both of the following is present:
Local Radio n
Remote Radio n
Note: n is the port identifier, either A, B, C or D.
The Local Radio n alarm indicates one or more of the following alarms is present on the
relevant local radio, and the Remote Radio n alarm indicates one or more of the following
alarms is present on the relevant remote radio.

0COG 5GXGTKV[
PMA Major Communication SMA communications with this
s PMA has been lost.
RMA A Major Communication SMA communications with this
s RMA has been lost.
RMA B Major Communication SMA communications with this
s RMA has been lost.
ODU A Major Communication SMA communications with this
s ODU has been lost.
ODU B Major Communication SMA communications with this
s ODU has been lost

MARCH 2000
IOM-NMS-1/05C
Appendix B: Constellation Diagrams
#RRGPFKZ$%QPUVGNNCVKQP&KCITCO
)GPGTCN
In a digital radio, the information contained in the baseband signal is carried by the signals
amplitude and phase when sampled with reference to a precisely timed recovered clock
signal. The phase and amplitude of the baseband signal at the instant of sampling can be
plotted on a polar graph to provide a Constellation Diagram.
A normal Constellation Diagram will show 4 tightly grouped points for DQPSK or 16 points
for 16QAM as shown in the following diagrams.
Each point contains many samples of the baseband waveform.
Figure 83: Constellation Diagram (DQPSK)

MARCH 2000
IOM-NMS-1/05C
Figure 84: Constellation Diagram (16 QAM)

Data is derived from the part of the graph an individual sample falls into. Where points are
tightly grouped the noise margin is large, reducing the probability of bit errors. If the RF
signal is noisy, the points will be more spread and the noise margin reduced. This increases
the probability of bit errors because of the Gaussian shape of the points.
Figure 85: Noisy Constellation Diagram (16 QAM)

MARCH 2000
IOM-NMS-1/05C
Transmitter, receiver or RF Path problems may affect the placement of points or distort their
shape, reducing the fade margin for a given signal to noise ratio. This will result in degraded
radio BER performance.
Some examples of signal degradations and their causes are shown below.
Figure 86: Constellation Diagram (DQPSK) - Example 1

Cause: Tight points with some spread out samples caused by Pulse Noise or similar
interference.
Action: Check for sources of interference.
Figure 87: Constellation Diagram (16 QAM) - Signal Degradation Example 2

Cause: Transmitter over driving or non-linearity causes the outer or corner points which
take the most power to transmit to be moved from the centre of their decision
boundaries.
Action: Check and adjust far end TX output power.
Contact Digital Microwave Corporation. for further information.

MARCH 2000
IOM-NMS-1/05C
Figure 88: 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 the
receiver at the monitoring end or the transmitter at the remote end of the link.

MARCH 2000
IOM-NMS-1/05C
Appendix C: Data Tables
#RRGPFKZ%&CVC6CDNGU
)GPGTCN
This appendix contains tables that contain the parameters you have to refer to when using
DXR NET.
%QTTGEVCDNG$[VGURGT5GEQPF%CNEWNCVKQP
The following table shows recommended values for each radio type and capacity. An error
rate of 1 x 10-6 is shown.

Mbit/S 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
1 x DS3 51.875 52
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
16 x DS1 30.731 31
8 x DS1 14.887 15
4 x DS1 7.382 7
2 x DS1 3.867 4
&:4(TGSWGPE[4GNCVKQPUJKRU
The following table shows the relationship between the frequency range, the modulation, the
capacity, and the transmitter power output at the Tx port, for a DXR 100 terminal.

MARCH 2000
IOM-NMS-1/05C
Appendix C: Data Tables
Modulation
QPSK 16 QAM
1 x E1 2 x E1 4 x E1 1 x E1 2 x E1 4 x E1
DXR 124 2300-2500 MHz 33 dBm - 33 dBm - - -
DXR 126 2500-2700 MHz - - 33 dBm - - -
&:4(TGSWGPE[4GNCVKQPUJKRU
The following table shows the relationship between the frequency range, the modulation, the
capacity, and the transmitter power output at the Tx port, for a DXR 700 terminal.
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 724 2.3-2.5 GHz +28dBm +28dBm +28dBm +28dBm +28dBm - - 26 dBm

MARCH 2000
IOM-NMS-1/05C
Appendix D: Abbreviations
#RRGPFKZ&#DDTGXKCVKQPU
AGC Automatic Gain Control
AUI TBD
BER Bit Error Rate
bps Bits per second
dB Decibels
dBm Decibels given relative to RFpower
DB15 15 pin connector type
DQPSK Differential Quadrature Phase Shift Keying
DS1 Digital Signal Level 1 (NADH line interface type)
DS3 Digital Signal Level 3 (NADH line interface type)
DXR The Digital Microwave Corporation 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

MARCH 2000
IOM-NMS-1/05C
Appendix D: Abbreviations
QAM Quadrature Amplitude Modulation
RAM Random Access Memory
RF Radio Frequency
RMA Radio Modem Adaptor
RX Receiver
SNMP Simple Network Management Protocol
STM-0 TBD
TX Transmitter
V.24 Serial data communications interface (Also called RS-232)

MARCH 2000
IOM-NMS-1/05C
Index
+PFGZ
Interface Capacities...................................................28
Mapping an Event to an Action ..............................140
A Non-protected Alarms.............................................217
Alarms Hardware ............................................................218
Commissioning Page Maintenance .......................................................219
Alarm Information ................................................49 Modem ...............................................................220
View Alarms Button .............................................49 Radio Link..........................................................221
DXR 100 Software..............................................................219
Forward and Reflected Power.............................137 Traffic.................................................................220
DXR 100 Alarms.....................................................216 Pedigree Information ................................................52
NMS Board Alarm Page..........................................162 PRA A Section..........................................................53
SDM Board .............................................................211 PRA B Section..........................................................53
Viewing Alarm Status .............................146, 187, 208 PSW Section .............................................................53
Receive Path .............................................................40
Removing an Event from an Action........................141
C Selecting Terminal Frequencies and Transmitter
Commissioning Workspace ...7, 14, 20, 47, 131, 210, 211 Power..................................................................135
DXR 100 .................................................................130 Setting the Line Interface........................................142
Toolbar ......................................................................19 Setting the Line Interface Parameters .....................143
Uses...........................................................................47 Setting the Terminal Diversity ................................139
Configuration Workspace7, 14, 20, 21, 211, 212, 213, Setting Up Alarm Inputs .........................................144
214, 215 Setting Up Alarm Outputs.......................................145
DXR 100 .................................................................130 Supported Interface Types ........................................27
General Setup Page Testing Protection Switching..................................149
Site Name Field ....................................................51 Transmitter Power Output.........................................32
Terminal Name Field ............................................51 Viewing Alarm Status.............................................146
Interface Setup Page..................................................52 Viewing the AGC Graph.........................................151
Page Variation...........................................................21 Viewing the Constellation Diagram........................149
Tabbed Pages ............................................................21 DXR 700 .......................................................................30
Toolbar ......................................................................19 Alarms.....................................................................223
Working Offline ........................................................21 Auxiliary Channel.....................................................24
Constellation Diagrams ...............................................131 Configuring.............................................................165
From Configuration Sheets.................................167
From Master Blueprint .......................................166
D Correctable Bytes per Second ...................................39
Description..............................................................164
DXR 100 .......................66, 131, 136, 217, 223, 226, 229
Enabling the RF/Modem Loopbacks ......................190
AGC Page............................................................48, 65
Enabling the Tributary Loopbacks..........................189
Alarm Descriptions..................................................216
EOW Ring Tones......................................................25
Alarm Inputs and Outputs .........................................34
Mapping an Event to an Action ..............................174
Configuration ..........................................................131
Modem Paramaters ...................................................33
From Configuration Sheets .................................133
Not under SMA Control
From Master Blueprint........................................132
Adding to Blueprint..............................................78
Correctable Bytes per Second ...................................39
ODU A Information ..................................................55
Daughter Board Information .....................................52
ODU B Information ..................................................55
Description ..............................................................129
ODU Information Section.........................................54
DXR 100 with NMS
ODU Unit Alarm.....................................................229
Adding to Blueprint ..............................................78
Hardware ............................................................229
DXR 100 without NMS
Maintenance .......................................................230
Adding to Blueprint ..............................................78
Radio Link..........................................................230
DXR 100 without NMS Board
Software..............................................................230
Terminal Connection ............................................94
PMA Information Section.........................................53
Enabling the Digital/IF/FEC Loopbacks .................148
PMA Unit Alarm.....................................................226
Enabling the Tributary Loopbacks ..........................147
Hardware ............................................................226
EOW Ring Tones ......................................................25
MARCH 2000
IOM-NMS-1/05C
Index
Maintenance........................................................227 Selecting ...............................................................95

Radio Link ..........................................................228 Connection Type Restrictions...................................95
Software..............................................................227 Connection Type Selection .......................................11
Traffic .................................................................227 Constellation Page
TX Switch...........................................................228 Monitor All/Reset All Buttons .......................63, 64
Receive Path..............................................................41 Creating Blueprint
Removing an Event from an Action ........................176 NMS Network ......................................................86
RMA A Information..................................................54 Customisation
RMA B Information ..................................................54 Language Support...................................................8
RMA Section Information.........................................54 Daughter Board Configuration..................................43
RMA Unit Alarm.....................................................223 Description..................................................................6
Hardware.............................................................223 DXR 700 Parameters ..............................................164
Maintenance........................................................225 Error Messages .........................................................20
Modem................................................................225 Hardware Key .........................................................104
Software..............................................................224 Insertion..............................................................115
RSSI Page ...........................................................48, 68 Help Menu
Setting DS1 Parameters...........................................181 About DXR NET....................................................19
Setting DS3 Parameters...........................................182 Installation ................................................................72
Setting E1 Parameters .............................................178 Dial-up Networking..............................................75
Setting E3 Parameters .............................................179 From CD...............................................................75
Setting Forward and Reverse Power Alarms ...........170 From floppy disk ..................................................74
Setting Line Interface ..............................................176 Removing Earlier Versions ..................................72
Setting Maximum Correctable Bytes per Second Installation Requirements .........................................70
Threshold ............................................................173 EM........................................................................71
Setting RF Modulation............................................172 Hardware ..............................................................71
Setting RSSI Alarms ...............................................172 EM ...................................................................72
Setting STM-0 Parameters ......................................184 LMT .................................................................71
Setting STS-1 Parameters........................................185 NMT.................................................................71
Setting Terminal Diversity Option ..........................173 NMT.....................................................................70
Setting the Terminal Frequencies and Transmitter Software
Power ..................................................................169 LMT .................................................................70
Terminal Connection.................................................93 Management Domain:...............................................10
Testing Protection Switching ..................................190 Managing Network Elements....................................14
Transmitter Power Output .........................................32 New Versions
Under SMA Control Licence Keys: .........................................................8
Adding to Blueprint ..............................................79 New Versions:.............................................................8
Viewing the Alarms Page........................................187 Relationship to DXR Software Product suite: ..........10
Viewing the Constellation Diagram ........................191 Remote Terminal.......................................................33
Viewing the RSSI Graph.........................................192 Restrictions on use:.....................................................8
Wayside Tributary.....................................................26 RSSI Page
DXR NET........................65, 66, 70, 81, 82, 117, 118, 151 Monitor All/Reset All Buttons .......................68, 69
Active Checkbox .......................................................44 SMA Parameters .....................................................194
Additional Functions.................................................99 Software Folder.........................................................99
Loading Software..................................................99 Software Key ..........................................................104
Running Test Script Files .....................................99 Storing and retreiving data........................................15
Advanced Option Tool Level...................................................................6
Selections........................................................63, 68 Toolbar
Advanced Options ...........................150, 151, 191, 192 Connect ................................................................20
AGC Page Disconnect............................................................20
Monitor All/Reset All Buttons..............................67 Tools Menu
Alarms .....................................................................216 Connect ................................................................19
Configuration Data....................................................13 Error Messages.................................................19
Configuring a NMS Board Disconnect............................................................19
From Configuration Sheets .................................156 Unable to Communicate............................................49
From Master Blueprint........................................155 Using with a DXR 100 terminal .............................129
Connecting to the Radio Network Using with a NMS Board........................................153
With Blueprint ......................................................96 Using with DXR 700 ..............................................164
Without a Blueprint ..............................................97 Using with NMS Board ..........................................153
Connection Protocol Using with the SMA ...............................................194
DXR 100 with NMS .............................................11 Warning Message......................................................47
DXR 100 without NMS ........................................11 Warning Messages ..................................................101
DXR 700...............................................................12 Workspace Selection.................................................20
SMA......................................................................12 Workspaces.........................................................7, 130
Connection Protocols ................................................10 DXR net GUI ..................................................6, 7, 15, 65
Connection Type Explorer Window......................................................13
MARCH 2000
IOM-NMS-1/05C
Index
DXR network.................................................................78 Filter Settings..........................................................110

Blueprint ...................................................................13 Label Browser.........................................................113
Element Configuration ..............................................21 New Event Table.....................................................113
Network Blueprint.....................................................78 Number of Windows...............................................104
Network Element.......................................................47 Pop-up Notification
Network Element Alarms ..........................................50 Filters..................................................................114
NMS Element Purge Acknowledge ................................................110
IP Addressing........................................................83 Purge Cleared..........................................................110
Right-click Menu ....................................................108
Using the Event Browser Windows ........................118
E Event Notification
Element Manager.............................................................6 Description........................................................18, 113
Description ..............................................................103 Drop-down Menu....................................................113
EM...................................................................6, 104, 117 Event Monitoring Menu..........................................105
Availability................................................................16 Pop-up Notifications
Configuration ....................................................18, 106 Setting the Cleared Status Filter .........................123
Description ..............................................................103 Setting the Generic Filter....................................124
EM log ....................................................................110 Setting the Severity Filter ...................................123
EM polling Setting the Type Filter ........................................124
Time....................................................................108 Selecting .................................................................123
Enabling and Disabling .....................................18, 105
Event Browser ...........................................................18 L
Events .................................................................107
Event Notification .....................................................18 LMT ..........................................................................6, 78
Event Notifications..................................................123 Additional Functions ................................................99
Hardware Requirements ....................................72, 115 Ethernet.....................................................................11
Licencing.....................................................................8 Hardware Requirements............................................71
Maximum Network Size Licence ............................103 Level of Access to Network ......................................93
Network Size ...............................................................8 Licencing ....................................................................8
Polling .....................................................................103 Software Requirements .............................................70
Requirements...........................................................103 Local Maintenance Tool............................................6, 70
Hardware and Software Keys..............................104 Hardware Requirements............................................71
Selecting NMS Elements to Monitor ......................117 Level of Access to Network ......................................93
Software Requirements .....................................71, 115 Software Requirements .............................................70
Windows and Notifications .....................................104
Workstation Requirements ......................................114
Ethernet .......................................11, 12, 72, 95, 115, 117
M
Autodiscovery Restricitons .....................................196 Maintenance Workspace .......................7, 14, 20, 61, 211
Autodiscovery Restrictions132, 134, 155, 157, 166, Advanced Options.....................................................18
168, 197 DXR 100.................................................................131
Description ................................................................95 Tabbed Pages ............................................................62
LMT ..........................................................................11 Toolbar......................................................................19
LMT Restriction........................................................95
SMA
Card Options.......................................................194 N
SMA AUI Options ..................................................194 Network Blueprints
SMA Capability.......................................................194 Creating, Saving and Retrieving ...............................15
Event Browser Network Elements
Delete Function .......................................................110 Adding to Blueprint ..................................................78
Description ........................................................18, 106 Network Maintenance Tool.......................................6, 70
Details .....................................................................109 Creating Blueprints ...................................................86
Event Browser Window Hardware Requirements............................................71
Acknowledging an Alarm ...................................118 Level of Access to Network ......................................93
Deleting an Alarm...............................................119 Software Requirements .............................................70
Displaying the Details Window ..........................119 Using to Create a Blueprint.......................................79
Purging Acknowledged Alarms ..........................119 Network Management Solution.......................................8
Purging Cleared Alarms......................................119 NMS........................................................................8, 117
Setting the Acknowledge Filter...........................121 Network IP Addressing Requirements ......................83
Setting the Cleared Status Filter .........................120 NMS Board
Setting the Date and Time Filters........................121 BIN Files ..............................................................69
Setting the Generic Filter ....................................122 General Information Section.................................55
Setting the Severity Filter ...................................120 Element Name Field.........................................56
Setting the Type Filter ........................................121 Element Type Field ..........................................56
Event Browser Window Example ...........................124 NMS Connection
Event Monitoring Menu ..........................................105
MARCH 2000
IOM-NMS-1/05C
Index
Dial-up Networking ..............................................75 Configuring a Low Speed Daughter Board.............212

Direct ....................................................................76 Cross-connections.....................................................46
DXR 100 with NMS Board ..................................95 Description..............................................................209
Installing TCP/IP ..................................................73 High Speed Daughter Board .....................................44
SMA......................................................................94 Low Speed Daughter Board......................................42
Direct Connection.............................................94 Manual Cross-connects.....................................46, 215
Modem Connection ..........................................94 Services Management Adaptor....................................232
NMS Details Page .....................................................55 Description..............................................................194
NMS Element SMA................................................................12, 25, 215
Mask IP Address...................................................83 Adding to Blueprint ..................................................78
Ports......................................................................85 Alarms.....................................................................232
NMS elements Aux Ports ..................................................................24
IP Addressing........................................................82 BIN Files...................................................................69
Routing Table .......................................................82 Configuration..........................................................195
NMS Elements From Configuration Sheets.................................197
Configuration Window .......................................106 From Master Blueprint .......................................196
Effect of MNSL ..................................................103 Configuring EOW Interface....................................203
IP Address Range..................................................84 Configuring Radio Link Ports.................................202
MNSL Restriction...............................................104 Cross-connects ........................................................210
Selection for Event Monitoring ..........................106 Cross-connects Page .................................................46
Subnets .................................................................85 Daughter Baord.........................................................44
Design Guidelines ............................................86 Daughter Board.........................................................45
NMS network Description..............................................................194
Creating a Blueprint..............................................82 EOW .........................................................................24
NMS Unit Communication .......................................25 Ethernet Connection .................................................95
Destination IP Address .........................................25 Mapping an Event to an Action ..............................204
Interface ................................................................26 NMS Connection ................................................75, 94
Mask IP Address...................................................26 Direct....................................................................76
SMA Option Board Slots .................................................209
NMS Overhead Channel .....................................209 Option Page
NMS board Co-directional Daughter Board
Alarms .....................................................................222 Cross connect to field.......................................45
Configuration ..........................................................153 High Speed Daughter Board
Default String ............................................................56 Cross connect to field.......................................44
Description ..............................................................153 Low Speed Daughter Board
NMS Board Alarm ..................................................222 Cross connect to field.......................................42
Hardware.............................................................222 Option Pages.............................................................41
Maintenance........................................................223 Removing an Action from an Event........................206
Radio Communication ........................................223 SDM Boards ...........................................................209
Software..............................................................222 Setting Real Time Clock .........................................199
NMS Connection.......................................................75 Setting the Clock Source.........................................203
Direct ....................................................................76 Setting the IP Address.............................................199
Setting the IP Addresses..........................................161 Setting up External Alarms .....................................206
Setting the NMS Board IP Address.........................159 SMA Details Page.....................................................56
Setting the Real Time Clock....................................158 Name field ............................................................57
Viewing Alarm Status .............................................162 SDM Board ................................................210, 211
NMS Connection .....................................................11, 12 SMA Section ........................................................57
Description ................................................................95 SMA Unit Alarm.....................................................232
NMT ..........................................................................6, 78 Alarm Board .......................................................232
Additional Functions.................................................99 Hardware ............................................................232
Hardware Requirements ............................................71 Maintenance .......................................................234
Level of Access to Network ......................................93 Radio Communication........................................235
Licencing.....................................................................8 Software..............................................................233
Software Requirements .............................................70 Traffic.................................................................234
Synchronisation ........................................................25
V.24 Ports .................................................................24
S
SDM board ....................................................................41 T
Automatic Cross-connects.........................................46
Configuring .............................................................211 Terminal Connection.....................................................11
Configuring a Co-directional Daughter Board ........214 Description................................................................95
Configuring a High Speed Daughter Board ............213

MARCH 2000
IOM-NMS-1/05C

DXRNETI&amp;O 5.c

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

DXRNETI&amp;O 5.c

Caricato da

Copyright:

Formati disponibili

&:40'6

TRADEMARKS AND REGISTERED TRADEMARKS

Corporate Headquarters Europe/Africa/Middle East Headquarters Asia Pacific Headquarters

Narrowband Headquarters Long Haul Division Headquarters

Tel: +1 206 439 9121 Tel: +64 4 569 2170

6JKUOCPWCNEQXGTU DXR NET V2.0

2 INTRODUCTION TO DXR NET 10

3 INSTALLING DXR NET 70

4 USING DXR NET LMT AND NMT 78

5 USING DXR NET ELEMENT MANAGER 103

Using the EM with Event Browser Windows 118

6 USING DXR NET WITH DXR 100 129

7 USING DXR NET WITH THE NMS BOARD 153

8 USING DXR NET WITH DXR 700 164

Enabling the Tributary Loopbacks 189

10 USING DXR NET WITH SDM BOARDS 209

APPENDIX A: ALARMS 216

APPENDIX B: CONSTELLATION DIAGRAM 236

APPENDIX C: DATA TABLES 240

APPENDIX D: ABBREVIATIONS 242

DIGITAL MICROWAVE CORPORATION iii

DIGITAL MICROWAVE CORPORATION v

6 DIGITAL MICROWAVE CORPORATION

at DXR NET start-up, from the Workspace Selection box

Figure 1: DXR NET GUI

DIGITAL MICROWAVE CORPORATION 7

Note: This customisation is only available on request from Digital Microwave

8 DIGITAL MICROWAVE CORPORATION

There are also appendices detailing:

DIGITAL MICROWAVE CORPORATION 9

DXR 100 terminals without the optional NMS Board

10 DIGITAL MICROWAVE CORPORATION

Selecting the DXR NET Connection

Connection Protocol for DXR 100 without a NMS Board

Figure 2: Connection to DXR 100

Connection Protocol for DXR 100 with a NMS Board

DIGITAL MICROWAVE CORPORATION 11

PC Running DXR NET TCP/IP over

Figure 3: Connection to DXR 100 with NMS Board

Connection Protocol for DXR 700

Figure 4: Connection to a DXR 700

Connection Protocol for SMA

Figure 5: SMA NMS Connection

Figure 6: SMA Ethernet Connection

12 DIGITAL MICROWAVE CORPORATION

how a DXR network will be built

the DXR network

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

Figure 7: Blueprint Sequence of Use

DIGITAL MICROWAVE CORPORATION 13

Element details (name, description, type, etc)

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

Alarms (similar to that provided in the Commissioning Workspace)

14 DIGITAL MICROWAVE CORPORATION

create, save and retrieve Network Blueprints to and from disk

Figure 8: DXR NET GUI

the Title bar

DIGITAL MICROWAVE CORPORATION 15

Toolbar - allows you to show or hide DXR NET toolbar

DIGITAL MICROWAVE CORPORATION 17

18 DIGITAL MICROWAVE CORPORATION

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

DIGITAL MICROWAVE CORPORATION 19

the Configuration Workspace

DXRNETI&O 5.c

DXRNETI&O 5.c

6JKUOCPWCNEQXGTU DXR NET V2.0

' Supported by DXR 700 only. Defined as part of the

&5 Supported by DXR 700 only. Digital Signal Level 3. Defined

56/ Supported by DXR 700 only. To be defined.

565 Supported by DXR 700 only. To be defined.

' DXR 700 supports 1xE3 and 2xE3.

&5 Both terminals support 1xDS1, 2xDS1, and 4xDS1. DXR

&5 DXR 700 supports 1xDS3.