Documente Academic
Documente Profesional
Documente Cultură
+PUVCNNCVKQP1RGTCVKQP/CPWCN
Copyright © 2001 DMC Stratex Networks
All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated 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 DMC Stratex Networks.
DISCLAIMER
DMC Stratex Networks 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, DMC Stratex Networks reserves the right to revise this
publication and to make changes from time to time in the content hereof without obligation of DMC Stratex Networks 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.
The DXR name and logo is a registered Trademark of DMC Stratex Networks.
Parts of the DXR product design are protected under Patent Cooperation Treaty Application No: PCT/NZ93/00046.
Seattle Wellington
DMC Stratex Networks DMC Stratex Networks Ltd
3325 South 116th Street 24 Bridge Street
Seattle, Washington 98168 Lower Hutt
USA New Zealand
Note: The DXR NET Help menu gives full details on how to contact
DMC Stratex Networks Customer Support personnel, under the Customer Support
heading.
6CDNGQH%QPVGPVU
TABLE OF CONTENTS I
Interface Setup 28
Modem/RF Link Setup 32
Alarm IO 39
Action Table 41
External I/O - SMA 42
Thresholds 44
Option Pages 46
Cross-connects Page 52
Commissioning Workspace 54
Commissioning 54
Terminal Details for DXR 100 and 700 58
Terminal Details for DXR 200 65
NMS Details 67
SMA Details 68
Controls 69
Maintenance Workspace 73
Constellation 74
AGC 76
Equalizer Graph 78
RSSI 80
File System 83
DXR NMS Network IP Addressing Requirements (DXR 100 and 700 only) 105
IP Addresses 106
Mask IP Addresses 106
DXR NMS Element IP Addressing 107
NMS Element Ports 107
Using Sub-nets 108
Creating the Blueprint 109
Example 2: NMS Blueprint 110
Sending Network Blueprints via E-mail 117
Working with a DXR NETwork and Network Elements 117
Network Visibility 117
Terminal Connections 118
NMS Connections 119
Ethernet Connection 120
Selecting the DXR NET Connection Type On Your PC 120
Connecting to the Radio Network with a Blueprint 121
Connecting to a Radio Network without a Blueprint (Autodiscovery) 121
Using DXR NET to Configure a Terminal 123
Introduction 123
Configuring a Terminal Using a Master Blueprint 124
Configuring a terminal from configuration sheets 125
DXR 200 Deployment 126
Building a Commissioned network blueprint 127
Using DXR NET to Configure a NMS Unit 127
Introduction 127
Configuring a NMS Unit 127
Setting the IP Address for a NMS Unit 129
Setting the Terminal Frequencies and Transmitter Power 130
Setting the NMS Unit Real Time Clock 130
Setting up the Route to a PC for a NMS Unit 130
Setting Up the Routing Tablefor a NMS Unit 131
Setting up the SMA Interfaces 132
Setting up the Radio Link Ports 132
Configuring the EOW Interface on a SMA 133
Setting up the Clock Source on a SMA 133
Setting Up the SMA Alarm Board 134
Setting the Terminal Power Alarm Limits 135
Setting the AGC Alarm Limits for a DXR 100 Terminal 136
Setting the RSSI Alarm Limits for a DXR 700 Terminal 136
Setting the RF Modulation for a DXR 700 Terminal 137
Setting the Maximum Correctable Bytes per Second Threshold 137
Setting the Terminal Diversity Option 138
Mapping an Event to an Action 138
Removing an Action from an Event 140
Setting the Terminal Line Interface 140
Setting the Terminal Line Interface Type 140
Setting the Parameters for an E1 Line Interface 141
Setting the Parameters for an E3 Line Interface 142
Setting the Parameters for a DS1 Line Interface 143
Setting the Parameters for a DS3 Line Interface 144
Setting the Parameters for a STM-0 Line Interface 145
Setting Up Alarm Inputs for a DXR 100 Terminal 146
Setting Up Alarm Outputs for a DXR 100 Terminal 146
Checking for Alarms 147
Using Loopbacks to Check a Link 148
Sequence of Operations 150
Using Loopbacks to Check the Test Equipment and the Terminal Connection 151
Using Loopbacks to Check the Link 151
Using Loopbacks To Check the Link Terminals 152
iii DMC STRATEX NETWORKS
APRIL 2001
IOM-NMS-2/2.5
Table of Contents
Software 181
Maintenance 182
Modem 182
DXR 700 PMA Alarm Descriptions 183
PMA Unit Alarm 183
Hardware 183
Software 184
Maintenance 184
Traffic 184
Radio link 185
TX Switch 185
DXR 700 ODU Alarm Descriptions 186
ODU Unit Alarm 186
Hardware 186
Software 187
Maintenance 188
Radio Link 188
SMA Alarm Descriptions 189
SMA Unit Alarm 189
Hardware 190
Alarm Board Mark I 190
Alarm Board Mark II 191
Software 192
Maintenance 193
Traffic 193
Radio Communication 194
200 Series Network Alarms for Terminals on the SMA 195
DXR 200 Alarms 196
Hardware 196
Software 197
Maintenance 198
Traffic 198
Modem 200
Radio Link 201
Overview 246
General 246
Setting up a NMS In/Out Connection 247
Using Data Rate Converters 248
Using Windows “Dial-Up Networking” with a Data Rate Converter 249
INDEX 257
.KUVQH(KIWTGU
Page
FIGURE 1: DXR NET GUI 3
FIGURE 2: CONNECTION TO DXR 100 8
FIGURE 3: CONNECTION TO DXR 100 WITH NMS BOARD 9
FIGURE 4: CONNECTION TO A DXR 700 9
FIGURE 5: SMA NMS V.24 CONNECTION 9
FIGURE 6: CONNECTION TO A DXR 200 - SMA ETHERNET CONNECTION 10
FIGURE 7: BLUEPRINT SEQUENCE OF USE 13
FIGURE 8: DXR NET GUI 15
FIGURE 9: GENERAL SETUP PAGE – DXR 700 22
FIGURE 10: PORT AND EOW SETTINGS PAGE 24
FIGURE 11: ROUTING TABLE PAGE – SMA 27
FIGURE 12: INTERFACE SETUP PAGE – DXR 700 29
FIGURE 13: MODEM/RF LINK SETUP PAGE – DXR 700 32
FIGURE 14: ALARM I/O PAGE 39
FIGURE 15: ACTION TABLE PAGE 41
FIGURE 16: EXTERNAL I/O PAGE 43
FIGURE 17: THRESHOLDS PAGE – DXR 700 44
FIGURE 18: OPTION PAGE WITH NO BOARD SELECTED 47
FIGURE 19: OPTION PAGE WITH LOW SPEED DAUGHTER BOARD SELECTED 48
FIGURE 20: OPTION PAGE WITH HIGH SPEED DAUGHTER BOARD SELECTED 50
FIGURE 21: OPTION PAGE WITH CO-DIRECTIONAL DAUGHTER BOARD SELECTED 51
FIGURE 22: CROSS CONNECT PAGE WITH GRID SHOWN 53
FIGURE 23: COMMISSIONING PAGE – DXR 700 55
FIGURE 24: ALARMS PAGE 57
FIGURE 25: TERMINAL DETAILS PAGE 59
FIGURE 26: TERMINAL DETAILS PAGE - DXR 200 65
FIGURE 27: SMA DETAILS PAGE 68
FIGURE 28: CONTROLS PAGE 70
FIGURE 29: CONSTELLATION DIAGRAM – SINGLE VIEW SELECTED 74
FIGURE 30: AGC GRAPH 77
FIGURE 31: EQUALIZER GRAPH 79
FIGURE 32: RSSI PAGE 81
FIGURE 33: FILE SYSTEM PAGE 83
FIGURE 34: NON-NMS BLUEPRINT EXAMPLE – NETWORK DIAGRAM 103
FIGURE 35: NMS BLUEPRINT EXAMPLE – NETWORK DIAGRAM 110
FIGURE 36: NMS BLUEPRINT EXAMPLE – ELEMENT NAMES 111
FIGURE 37: NMS BLUEPRINT EXAMPLE – NMS ELEMENT IP ADDRESSES 112
FIGURE 38: NMS BLUEPRINT EXAMPLE – TOWN SMA ROUTING 113
FIGURE 39: NMS BLUEPRINT EXAMPLE – BEACH SMA ROUTING 113
FIGURE 40: NMS BLUEPRINT EXAMPLE – TOWN NMS ROUTING 113
FIGURE 41: NMS BLUEPRINT EXAMPLE – PORT NMS ROUTING 114
FIGURE 42: DXR 700 PMA FRONT PANEL LAYOUT - LOCATION OF CONNECTOR V.24 118
FIGURE 43: DXR 100 FRONT PANEL LAYOUT - LOCATION OF CONNECTOR V.24 118
FIGURE 44: SMA FRONT PANEL LAYOUT - LOCATION OF SETUP CONNECTOR 119
FIGURE 45: LINE FACING LOOPBACK 149
FIGURE 46: RADIO FACING LOOPBACK 149
FIGURE 47: DIGITAL LOOPBACK 150
viii DMC STRATEX NETWORKS
APRIL 2001
IOM-NMS-2/2.5
List of Figures
#DQWV6JKU/CPWCN
+PVTQFWEVKQP
This manual describes how to use the DXR NET Network Maintenance Tool (NMT) product
with the following DMC Stratex network elements:
• DXR 100 digital radio terminals (with and without optional NMS board)
6GTOKPQNQI[
In this manual, we use the terms Terminal, Element and Unit to describe the hardware
involved.
The terms general are used as follows:
The radio terminals and SMA devices in a network are called elements
A radio, such as a DXR 100, DXR 200 or a DXR 700 is a terminal
The SMA and DXR 100 NMS boards are NMS units
One exception to this terminology is the license size count for DXR NET Element manager
(described below). This counts only NMS units, but refers to them as elements - a SMA is
counted as two elements, the DXR 100 NMS unit counts as one element. The DXR 200 is
counted as two elements in this case.
9JCVKUVJG&:40'6!
DXR NET is a software package supplied by DMC Stratex Networks. It is offered in two
levels:
• Network Maintenance Tool (NMT), for configuring, commissioning, and carrying out
diagnostics on the network elements on a radio network
Note: For information on the DXR NET Element Manager, refer to the “DXR NET EM
Installation and Operation Manual”, Product Code IOM-NMS-3.
&:40'65QHVYCTG
DXR NET is supplied as one program, and uses a hardware key and software key to enable the
NMT and EM levels. These keys will work with all releases of DXR NET, to enable users to
upgrade to a later version, and make use of the level of function they have access to using the
keys.
6JG&:40'6)7+
You interface with DXR NET via the DXR NET GUI.
The DXR NET GUI is divided into a left-hand and a right-hand pane. The Explorer Pane (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:
• Configuration Workspace. This is used to view and modify the configuration of the
network elements
• 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 sometimes shown with a “plug” to distinguish it from any other shown
elements.
&:40'60/6.KEGPUKPI
DXR NET NMT requires a hardware key to activate it. If the key is connected to the PC when
DXR NET starts, the extra function provided in NMT will be available. The current level of
DXR NET is shown on the Help- About screen.
&:40'6.CPIWCIG5WRRQTV
DMC Stratex Networks can supply you with a customized version of DXR NET to support
your language requirements.
Note: This customization is available on request from DMC Stratex Networks who will
supply a quotation.
&:40'60GVYQTM4GUVTKEVKQPU
0GVYQTM'NGOGPV6[RGU
DXR NET operates with DXR 700 terminals, DXR 200 terminals DXR 100 terminals, and
SMAs.
0GY(GCVWTGU
DXR NET software provides a solution for the management of DXR networks that incorporate
DXR 100, DXR 200 and DXR 700 radios.
DXR 200 is incorporated into the DXR NET Network Management environment for the first
time by treating the SMA as a "proxy" for a DXR 200 network. The purpose of this new
functionality is to create a SNMP bridge to the DXR 200 so that ProVision and DXR NET can
monitor the DXR 200 radio.
$GPGHKVU
Previously, it was necessary to use DXRview or DXRsetup to configure and monitor a 200
network. Now, the DXR 200 can be part of a DXR NETwork and DXR NET can be used to
monitor DXR 200 units and display the results in a GUI interface.
Network management facilities incorporated into DXR NET for the DXR 200 series include:
Viewing DXR 200 alarms
Ability to configure DXR 200 terminals and alarms
Ability to monitor DXR 200 terminals and alarms
1VJGT&/%5VTCVGZ0GVYQTM/CPCIGOGPV5QNWVKQPU
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 DMC Stratex Networks product providing management
of all DMC 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 the DXR NET to manage a radio link
• Installation of DXR NET. This tells you all you need to know to install DXR NET on your
PC, and how to get started using it
• Using the DXR NET. This contains a description of how you can use DXR NET to design
and modify network blueprints, and to configure, commission and maintain network
elements
• Constellation Diagrams
• Data Tables
• Abbreviations
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 CD. You must also be familiar with DMC
Stratex Networks equipment you are planning to use the DXR NET with. Ideally, you should
have completed any DMC Stratex Networks training courses for the equipment, and have
access to the training and installation manuals for the equipment and any other relevant
documentation
Note: The DMC Stratex Networks training courses cover the installation, configuration,
operation and maintenance of DXR products. Please contact your local DMC
Stratex Networks representative for details.
*CTFYCTG5WRRQTVGF
LINK. An entire link must be made up of either RMA-V or original RMAs.
DXR 100
• Protected and non-protected configurations and upgradeables
DXR 200
• All protection and repeater variants
Note: The SMA works as a bridge to the DXR 200 network, and does not carry DXR 200
traffic or signalling. There is no communication between DXR 200s on different
SMA ports.
DXR 700
Protected and unprotected
IRU and ODU variants
With and without SMA
Note: Without an SMA, some functions are not available with DXR NET (i.e. software
loading). For these situations, the engineering tool DXRloader is required.
+PVTQFWEVKQPVQ&:40'6
+PVTQFWEVKQP
This section covers:
• The DXR NET Management Domain (ie, how DXR NET fits in with the other DXR
product software)
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, DXR 200 or DXR 700 terminals
• NMS Unit Software – the software in the NMS boards or the SMAs
The way in which DXR NET communicates with a network element depends on the type of
software the element contains.
DXR NET software is a single package that has three levels available. The NMT and EM
levels require a hardware and software key to "unlock" the additional function.
%QPPGEVKQP2TQVQEQNU
At present, you can use DXR NET to connect to the following DXR NETwork elements:
• DXR 100 terminals without the optional NMS Board
• NMS Connection. Select this type of connection when you are connecting to a NMS unit
(DXR 100 with NMS board, or a SMA). Your PC can be either directly connected to 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. 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: DXR NET will not allow you to connect to a terminal directly if the terminal is part
of a network containing NMS units. Instead, you will have to connect to one of the
NMS units.
DXR 100
with NMS
Board
ProVision
V.24 connector
DXR 200
LAN
SMA SMA
6QRQNQIKGUQH&:45/#0GVYQTMU
Scenario A - 1:many relationship
DXR NET
SMA All DXR 200s can talk to each other using their
Terminal Numbers.
ProVision
DXR 200
Terminal 2
DTI connection
DXR 200
Terminal 3
Radio Link
DXR 200
Terminal 4
DXR NET
SMA SMA
ProVision
DXR NET
SMA DXR 200
Terminal 1 DXR 200
ProVision
Terminal 2 DXR 200
Terminal 3
V24l
DXR 200
Terminal 1
DXR 200
Terminal 1
DXR 200
Terminal 1
DXR 200
Terminal 2 RdiLik DXR 200
Terminal 2
DXR 200
Terminal 2 DXR 200
Terminal 3
D TI i
DXR SETUP
DXR 200
Terminal 4
RdiLik
DXR VIEW
&:45QHVYCTG5GVU
DXR software, both terminal software and the DXR NET software, are released in "sets". A
set contains all the software that will work together for a specific release. Each set supersedes
the earlier sets. Software that is not contained in a single set is not supported. Many sets will
contain similar levels of software, as a new set is released if any component in the set is
updated.
Details of released sets are contained in Appendix I: DXR Software Sets.
DXR 200 software is not covered. Refer to the DXR 200 library.
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
Using DXR NET, you can edit the configuration data held in the blueprint for:
• the DXR NETwork
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
7UKPI&:40'6VQ/CPCIG0GVYQTM'NGOGPVU
DXR NET has been developed to assist you to install, configure, commission and maintain the
DXR series of radios and their associated network management hardware.
DXR 200 configuration is achieved via DXRsetup.
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)
• Performance thresholds
Note: You use DXR NET to configure the SMA to communicate with the DXR 200. You
cannot configure the DXR 200 radio using DXR NET. Configuration must be
performed by a PC running DXRsetup that is directly connected to the DXR 200
network.
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
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)
• Receive Signal Strength Indicator (RSSI) graphs, (DXR 100 and DXR 700 only) and
• Signal to Noise Ratio (SNR) (DXR 100 and DXR 700 only)
As in the Commissioning Workspace, the Maintenance Workspace also includes a control
panel that allows you to carry out Loopbacks and Manual protection switching for test
purposes.
For the DXR 200, the Maintenance Workspace is used to view alarms. Other functions must
be performed via DXRsetup and DXRview.
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+
The DXR NET GUI contains the following:
• the Title bar
• the Toolbar
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 drop-down lists:
• File
• View
• Configuration
• Maintenance
• Tools
• Help
The availability of a drop-down list depends on the level of tool you are using, and the 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 drop-down lists 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: The Configuration and Maintenance menus are only available if you have selected
the corresponding workspace.
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
• 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 own 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
• 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 there is a NMS unit (SMA or a DXR 100 with a NMS
board) in the blueprint. Allows you to download the unit software to the SMA or NMS
board, or to units under their control. DXR 200 cannot be software loaded through DXR
NET.
• IP Address Table - available when there is a NMS unit (SMA or a DXR 100 with a NMS
board) in the blueprint. Contains all the IP addresses of all the NMS units in the blueprint,
also used to set up the SMA or NMS IP address.
• Software Table - available when there is a NMS unit (SMA or a DXR 100 with a NMS
board) in the blueprint. Lists the versions of the unit software of all the NMS units and the
terminals under their control. For DXR 200 this information can be seen on the Terminal
Details page accessed from the Commissioning or Maintenance workspace.
• Set Real Time Clock - available when a SMA or NMS board is selected in the Explorer
Pane. Sets the clock used to synchronize operations in the SMA or NMS board
• Commit Configuration - writes the changes made on the screen to the configuration.
You can select any of the functions listed in the Configuration menu with the mouse, or 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 other 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 use any functions other
than Add Network Element or Add Site while your PC is not physically connected
to a network.
Maintenance
The Maintenance menu contains listings for the following functions:
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 description is Section 4 for further details.
You can select any of the functions listed in the Maintenance menu with 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.
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 DMC Stratex Networks.
• 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 with 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.
• 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).
• 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.
• 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 physically 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 200s, 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
/QWUG1XGTU
You can view the specification of a radio or NUS (SMA, NMS board) by moving the mouse
over the relevant icon in the explorer tree pane, A pop up window displays the following
information for the selected element from the network blueprint:
SMA, NMS board - IP address
700 radio - Protected/Non-protected, capacity, modulation
200 radio - Protected/Non-protected, capacity, modulation
100 radio - Protected/Non-protected, capacity
Each DXR 200 on a blueprint represents a single control card (CTL-2). Therefore, the mouse
over may not accurately describe the entire DXR 200.
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
5VCVWU$CT
The Status Bar can be divided into three 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
• SSC compatibility checking. This indicates any incompatibility between what the
software version of an NMS unit has been set to in the blueprint, and the version
DXR NET detects in the actual unit
%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.
You can only change the terminal name and number for the DXR 200 radio in the
configuration workspace. For more advanced configuration options, use DXRview
and DXRsetup - two PC based programs that enables users to configure terminals to
form a network, change the way a terminal operates or load new software.
As Configuration Workspace can work with saved data, you can work with it offline, ie, you
can create and modify element configuration data while your PC is not actually connected to
abelement.
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.
• Action Tables (for DXR 100 terminal, DXR 200 terminal and DXR 700 terminal and
SMA)
• Thresholds (for DXR 100, DXR 200 and DXR 700 terminals)
• External I/O (for SMA only)
• Option 1 and 2 (for SMA only)
• Cross-connects (for SMA only)
• Notifications (for NMS board and SMA only)
)GPGTCN5GVWR
The General Setup page is divided into the following sections:
• Terminal Details (for DXR 100, DXR 200 and DXR 700 terminals)
• Board Details (for NMS boards only)
• SMA Details (for SMA only)
• Site Information
Terminal Details
The Terminal Details section has two text fields:
• Type
• Terminal Name
The Type field contains the equipment description of the terminal. This is determined by
DXR NET, depending on the unit selected in the Explorer Pane, and you cannot change it.
The Terminal Name field is used to hold the name of assigned to the terminal in the Network
Blueprint. If you have not assigned a name to the terminal, the field contains the default string
“Terminal n” where “n” is an integer relating to the number of radios in the network. You 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”. This information is embedded in DXR NET, and you cannot change it.
The Board Name field is used to hold the name assigned to the board. If you have not
assigned a name to the board, the field 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 assigned to the SMA. If you have not assigned
a name to the board, the field 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
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 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:
• Local Terminals
• NMS In Connected
• Baud Rates
NMS In Connected
This has two list boxes, designated Site and NMS Unit respectively, used to define which
remote NMS units the NMS In port on the SMA communicates with. The Site list box
contains the name of the remote site. The NMS Unit list box contains the name of the actual
NMS unit at the remote site.
Baud Rates
This has two list boxes (designated NMS In and NMS Out respectively) that are used to set
the baud rates the SMA uses to communicate over the NMS In and NMS Out ports. For
further details, refer to Appendix F: Using DXR NET with Different Data Rates.
• Ring Modes
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. Select the tone from the drop-down list 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.
25 DMC STRATEX NETWORKS
APRIL 2001
IOM-NMS-2/2.5
Introduction to DXR NET
The Transmit High Pass Filter field is used to select whether the analog voice signal from the
EOW handset is passed through a high pass filter or not. 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 its components are synchronized, the SMA is provided with two possible clock
signals, Primary and Secondary. The SMA switches 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.
Select the option you require from the drop-down list 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, i.e. input via one of the optional daughter boards.
Note: For either of the last two choices to be valid, the relevant slot in the SMA must be
occupied by an appropriate board.
4QWVKPI6CDNG
The Routing Table fields are contained within a three-column table for a NMS board, and a
four-column table for a SMA. The columns are:
• Destination IP Address
• Mask IP Address
• Interface
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.
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 the 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 uses 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.
Gateway/Next Hop
The SMA routing table also has a “Gateway/Next Hop” field, which should be left at 0.0.0.0
unless the interface is Ethernet, and the destination host or network is indirectly connected to
the SMA via a router or gateway. The next-hop address is then the address of the router. Input
the required address by double-clicking the next empty field in the Destination IP address
column, and typing in the address.
+PVGTHCEG5GVWR
The Interface Setup page is divided into the following sections:
• Interface
• Tributary
Interface
Depending on the type of line interface you select, the Interface section has either one or two
drop-down list fields. The fields are:
• Interface Type (always present)
• Interface Capacity (present if selected interface type uses more than one signal channel)
+PVGTHCEG6[RG &GUETKRVKQP
' Default setting. Data rate 2.048 Mbs. Can carry up to thirty
voice channels, with two control and synchronization
channels.
&5 Supported by DXR 700 only. Data rate 44.736 Mbs. Can
carry up to 672 64 kbs channels, each channel capable of
carrying one analog telephone conversation (after analog-to-
digital conversion). Equivalent to 28 DS1 circuits.
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 drop-down list 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.
+PVGTHCEG6[RG +PVGTHCEG%CRCEKV[
' Both terminals support 1xE1, 2xE1, and 4xE1. DXR 700 also
supports 8xE1 and 16xE1.
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.
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
• 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” depends 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 depends 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 line build-out. Select the line build-out 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. Select one of these sensitivities from the drop-down list displayed
by 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. Enable Tx level boost by selecting True (enabled) or False (disabled) in the
column.
The Equalizer Bypass column is used to take the equalizer circuitry on the line interface out
of the signal path. Enable equalizer bypass by selecting True (enabled) or False (disabled) in
the column.
The Commissioned column is used to enable the tributary to carry traffic. It can be either True
(tributary can carry traffic) or False (tributary cannot carry traffic). Select these from the
drop-down list displayed when you double click on the field.
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).
31 DMC STRATEX NETWORKS
APRIL 2001
IOM-NMS-2/2.5
Introduction to DXR NET
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, or STM-0 interface types. The section contains either a table for configuring the
tributary, or “No Wayside Available” if you selected an interface capacity or type that does
not support the tributary.
The table has two columns, each of which corresponds 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 or
DS3). The function of these columns is the same as for those 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.
• Remote Terminal
• Space Diversity
• Frequency Diversity
ODU
The ODU consists of a light-weight, compact, integrated RF electronics enclosure attached to
an antenna. The millimetre wave technology employed permits the complete integration of all
millimetre wave functions into a single, small, rugged subassembly.
This technology yields a significant increase in reliability when compared to conventional
approaches. Typically, the ODU is installed outdoors on tower or rooftop.
IDU
The IDU is an indoor mounted assembly that contains all of the baseband electronics
including the functions of line interface, digital multiplexing, modulation and frequency
generation. It also includes the alarm and diagnostic, service channel and network
management interfaces. Furthermore, within the IDU is the capability to set the system
capacity, frequency synthesizer and power output of the radio; NO access to the Outdoor Unit
is required.
IRU
The IRU contains the same light-weight, compact integrated RF electronics as the ODU but is
packaged for fitting in an indoor rack. You would typically use an IRU where the output of
the IRU goes to the antenna via a waveguide. This gives you the flexibility of mounting all the
components indoors. It also enables hot standby, where required.
Protection Options
There are a number of protection options available for the DXR 700 range of products. These
options use two RMAs and two RF Units to provide 100% redundancy of the RF and modem
functions. The same RF Units and RMA modules are used in both protected and unprotected
systems, minimizing spares requirements.
In a typical protected configuration, the transmit RF signals are combined using a power
splitter/combiner into a single antenna, and the receive RF signals are split with the same
splitter/combiner to the two receivers. In this configuration, the two RF Units can be on the
same frequency with one of the transmitters being disabled in software, or both transmitters
may be operated simultaneously on different frequencies for frequency diversity operation.
Upgrading an unprotected system to a protected one is as simple as adding additional RMA,
ODU and power/splitter combiner and re-configuring the terminal for protected operation.
Both receive paths are continuously monitored for receive signal integrity while the protection
switch selects the highest quality data. FEC controlled block selection enables errorless
receive path switching.
A further configuration is available with two RF Units connected to two separate antennas to
provide space diversity or frequency diversity. In this configuration, the system gain is higher
since it does not have the additional loss of the power
splitter/combiner.
Space Diversity
Space diversity is usually applied to overcome the effects of multipath fading. With space
diversity only one frequency pair is used. Both transmitters operate at the same time using
different antennas. Only one transmitter needs to be operating, however, in order to have
equipment protection as well as path protection. The transmit branching is often the same as
the hot standby arrangement.
Frequency Diversity
In some cases, when fading activity occurs over the hop, the effect on one frequency is
different from an adjacent frequency due to the electrical path differential between the two.
Therefore, to meet specified performance objectives in a route, a protection channel is used
during fading the traffic channel, traffic loss can be avoided. With frequency diversity, two
radios are transmitting to the same antenna using different frequencies. The greater the
difference between the two frequencies, the better the performance improvement against
fading.
Hot Standby
In a hotstandby arrangement both sets of RF (main and standby) are operational the whole
time. This means that there is a guaranteed backup transmitter in the event of failure. Only
one frequency pair is used for the two-radio system. It is thus not possible to transmit both
signals simultaneously. Both transmitters actually transmit a signal. But only one is switched
onto the antenna. The other signal is transmitted to a dummy load.
In the event of system failure, DXR NET will report a fault and switch transmission to the
back-up RF, guaranteeing a secure system.
DXR NET supports the protected IRU variant when configuring hot or warm standby for the
protected DXR 700 radio.
35 DMC STRATEX NETWORKS
APRIL 2001
IOM-NMS-2/2.5
Introduction to DXR NET
Monitored Hotstandby
Monitored hot standby (MHSB) is offered with all frequency bands of protected system as
standard. Switching on receive is fully automatic and is based on detection of uncorrectable
errors by the forward error correction (FEC) circuit. Manual mode may be selected to allow
one protected radio to be replaced while maintaining normal operation via the other radio.
The protected option can be configured to switch from the main to the standby transmitter by
selecting any one of the following alarm conditions:
Low transmitter forward power
Temperature too high
Local oscillator out of lock
Major alarm (triggered by failure of any sub-module)
Manual switch-over commands for testing and maintenance
Note: Transmitter switches are disruptive to traffic only in the cases listed above. They are
never disruptive due to path performance.
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.
You select a configuration option by clicking on the appropriate radio button with the mouse.
If you select Frequency Diversity, the additional fields are displayed in the following 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)
• Preferred A
Preferred Transmitter
Preferred TX gives the user the option of having a protected radio use the preferred
transmitter whenever possible, unless there is a hardware alarm on the preferred transmitter.
This option may be used if there is an un-equal loss splitter, or a space diversity configuration
with unequal gain. The preferred transmitter is always TX A.
If there are no outstanding alarms on TX A, the PMA will attempt to switch to TX A. In the
case of switch-causing alarms on TX B, the radio must wait the minimum guard time (5 secs)
before it can switch back to TX B, and once it does, the guard time will be doubled. The
radio will not switch back to TX A until the guard time has elapsed. If there are no alarms on
TX A at this time, it will switch to TX A. After successfully running for twice the current
guard time on TX A, the guard time is halved.
The minimum guard time is 5 seconds. The switch from A to B always has the minimum
guard time. The maximum guard time is around 20,000 seconds, which is 5 ½ hours.
It is not recommended to use Preferred Transmitter unless the path engineering requires it,
due to the possibility if increased TX switches.
Note: Preferred transmitter is only supported by DXR 700 system software V2 and above.
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
list 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: Any changes you make to the frequency values will be reflected in the remote
terminal settings after you have committed the changes.
Note 2: If Frequency Diversity is selected in the Protected & Diversity Options sub-section,
there are Tx Frequency (MHz) and Rx Frequency (MHz) fields for Radio A 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
• Alarm Outputs
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.
You select “No Current” or “Current” from the drop-down list displayed when you 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
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 Edit Actions window with drop-down lists of available
locations (the network elements 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: Actions enabled on remote elements are followed by the name of the element in
parenthesis.
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.
'ZVGTPCN+15/#
The External I/O page is only supported by the SMA. The SMA can have one of the following
alarm boards:
• Alarm Board Mk I
• Alarm Board Mk II
The alarms for these boards are available on the DB15 connector on the SMA front panel.
The alarm states are configured both by software, and by switches and links on the boards.
Each board can have up to six alarm input and output pairs, handling a total of twelve alarm
signals.
Note: DXR NET will only write the configuration to an alarm board if it finds that the
board type in the SMA matches the type set in the blueprint.
The External I/O page contains the Alarm Board I/O Channel Settings section. This has a five
column table displaying the following fields:
• Channel
• Identifier
• Type
• Electrical State
• Rate
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.
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. In the MK I board, you can assign a
state to the signal by double-clicking on the field with the mouse, and selecting the state from
the drop-down list. The signal state is “hard-coded”, ie, not selectable, in the Mark II board.
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 list. 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 double-clicking on the Rate field, and typing in the value.
Note: You must select a number within the given range, and you must select an integer
value.
6JTGUJQNFU
The Thresholds page is divided into the following sections:
• General
• Transmit Path
• Receive Path
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
Radio Capacity Link Data Rate Bit Error Rate
Mbit/S 1E-6
1 x STM-0 60.441 60
2 x E3 79.836 80
1 x E3 40.769 41
16 x E1 40.762 41
8 x E1 19.747 20
4 x E1 9.792 10
2 x E1 5.01 5
1 x DS3 51.875 52
16 x DS1 30.731 31
8 x DS1 14.887 15
4 x DS1 7.382 7
2 x DS1 3.867 4
Note: The correctable bit error rate is not a true BER, as multiple bit errors per byte are
not detected. The correction algorithms employed allow a significant error rate to 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)
Receive Path
The appearance of this page depends on the terminal type.
For a DXR 100 terminal, the page contains the fields used to set the limits for the 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. Set the values by either selecting the field and typing in the
value you require, or by using the up/down arrows in the fields. You can set the fields to their
default values by clicking the Defaults button.
The DXR 200 radio has no access to AGC data.
For a DXR 700 terminal, the page contains the fields used to set the Received Signal 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. Set the
values by either selecting the field and typing in the value you require, or by using the
up/down arrows in the fields. You can set the fields to their default values by clicking the
Defaults button.
The DXR 100 and 200 radios have no access to RSSI data.
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 the type of board that has been fitted to the slot.
Note: In the following, “n” represents either “1” or “2”.
• Circuit 1
• Circuit 2
Figure 19: Option page with Low Speed Daughter Board selected
The Option Slot n section has the following fields:
• Option Board Type. Use this field to select the type of board inserted into the slot. The
default is “Not Installed”. In this case, select “Low Speed Daughter Board” from the drop-
down menu displayed by clicking on the arrow in the right hand side of the field.
• Cross connect to. Use this field to select the AUX port on the SMA the board uses 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. The default is “AUX A”.
Select any one of the four AUX ports on the SMA from the drop-down menu displayed by
clicking on the arrow in the right-hand side of the field.
• Channel. Use this field to select the first channel used for the board data on the AUX
channel. Default is “2”. Select either “2” or “3” from the drop-down menu displayed by
clicking on the arrow in the right-hand side of the field.
• Channels required. This field shows the number of channels on the AUX channel the
board requires to transmit 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. Use this checkbox field to enable all other fields in the section. If
the checkbox is not selected (default), ie, not ticked, all other fields will be greyed out and
disabled.
Note: When an Option Board is inactive, the SMA will expect the board to be present, but will not
allocate any bandwidth to it. In this case, the board will not carry any data.
Note: Your selection in this field determines the other fields displayed in the Circuit
section.
• Data Rate. Use this field to select the speed at which the board transmits and receives
data. The values you select are dependent on the selection you made 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. Use this field
to set the number of bits needed to represent a character. You can choose between 7 or 8
bits (default). 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. Use this field
to set the number of bits needed to represent a stop bit. You can choose between 1
(default) or 2 bits. Select the number of bits from the drop-down menu displayed 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. Use this field
to shorten or “shave” the length of the stop bit(s). You would do this to reduce loss of bit
synchronization due to transmission between stations in multi-hop situations. You can
choose between 1/16th (default) to 7/16th. 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. 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. Select the parity from the drop-down menu displayed when
you click on the arrow in the right-hand side of the field.
• Break length. This field is only available when you have selected Async mode. Use this
field to set the number of characters that will represent a line break. You can enter an
integer from 1 to 65535, representing the break length in characters. The default is 4.
• Circuit 1
Figure 20: Option page with High Speed Daughter Board selected
The Option Slot n section has the following fields:
• Option Board Type. Use this field to select the type of board inserted into the slot. The
default is “Not Installed”. In this case, 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.
• Cross connect to. 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. The default is “AUX A”.
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. Use this field to select the first channel used for the board data on the AUX
channel. The default is “2”. Select either channel “2”, “3”, or “2 and 3” from the drop-
down menu displayed when you click on the arrow in the right-hand side of the field.
Note: If the SMA high speed daughter board circuit has a data rate of 128 KBPS, both
channels are required, and you will only be able to select channel “2 and 3”. If
the circuit has a rate of 64 KBPS or less, then either “2” or “3” can be selected.
• Channels required. This field shows the number of AUX channels that the board 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. Use this checkbox field to enable the other fields in the section. If the checkbox is
not selected (default), ie, not ticked, all other fields will be greyed out and disabled.
Note: When an Option Board is inactive, the SMA will treat it as present, but will not
allocate any bandwidth to it. The board will not carry data.
• Data Rate. Use this field to select the speed at which the board transmits and receives
data. You can select one of 8, 16, 24, 32, 48, 56, 64 (default), or 128 KBPS. Select the
rate from the drop-down menu displayed when you click on the arrow in the right-hand
side of the field.
• Circuit 1
• Cross connect to. Use this field to select the AUX port on the SMA the board uses to
transmit and receive data. This in turn selects the DXR 700 terminal by which the board
data is sent and received. The default is “AUX A”. Select any one of the four AUX ports
on the SMA from the drop-down menu displayed when you click on the arrow in the
right-hand side of the field.
• Channel. Use this field to select the first channel used for the board data on the AUX
channel. Default is “2”. Select either “2” or “3” from the drop-down menu displayed
when you click on the arrow in the right-hand side of the field.
• Channels required. This field shows the number of channels on the AUX channel the
board requires to transmit and receive data. It is generated automatically from the board.
The Circuit 1 section contains only the message “No circuit configuration is required for a
Co-directional Daughter Board.”
%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 channels and
the channels 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.
Note: You cannot select rows and columns already in use by an automatic cross-
connection.
To remove a manual cross-connection, move the mouse to select the appropriate row 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. The Commissioning Workspace provides the following information and functions:
• Site details, RSSI and alarm information.
• Line and radio facing loopback functions for the terminal tributaries, and digital and IF
loopback functions for the terminal RF/Modem links.
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 (DXR 100 and DXR 700 terminals).
%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.
• Alarm Information.
Note: You will not be able to change any of the details in the fields of this page, as they
are all read directly from the terminal. Because of this, they may not match the
details for the unit in the blueprint.
The page also has the Commissioning Report button, which you can use to produce a report
containing details relevant to the terminal when it is commissioned.
Site Details
The Site Details sub-section contains the following fields:
• Site
• Terminal
• TX Frequency (MHz)
• TX Power (dBm)
Note: Terminals using frequency diversity will have TX Frequency and TX Power 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 (+5V and 0V).
Note: Protected terminals 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: Protected terminals will have bar graphs for Radio A and Radio B.
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.
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 B.
6GTOKPCN&GVCKNUHQT&:4CPF
The Terminal Details page is divided into the following sections:
• General Information
• Remote
• Refresh
• Inventory Report
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.
The Inventory Report button will produce a report containing relevant terminal details.
Note: Remote terminal details can only be displayed if the link is operational.
General Information
The General Information section contains the following fields:
• Site Name
• Terminal Name
• Terminal Type
• Modulation Type
• Capacity
• Occupied Bandwidth
The Site Name and Terminal Name fields are both read from the terminal.
The Terminal Type field contains the equipment description of the terminal. The field is
generated automatically from embedded information in DXR NET.
The Modulation Type field contains the type of modulation the terminal applies to the RF
signal. The field value is read from the terminal, and you cannot change it.
Note: The type of modulation is set at the factory, so you specify the type you require
when you order the terminal.
The Capacity field is only displayed when the terminal line interface type can support more
than one channel. The field value is read from the terminal, and you cannot change it.
Note: The capacity is set at the factory, so you specify it when you order the terminal. 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 value is read from 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, the Version and Type
for the Terminal Software, and the factory set duplexer TX and RX frequencies.
• 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 DMC
Stratex Networks representative.
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
The details contained within these fields are self-explanatory. The section also contains a
PSW Details button, which you can use to display the Pedigree Details box. This lists the Part
Number, Serial Number and Build Level for the PSW Hardware, the Version and Type for the
PSW Software, and the interface capacity for the PSW Build Type.
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
The details contained within these fields are self-explanatory. The section also contains a
PRA 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 PRA Hardware, the Version and Type
for the PRA Software, the occupied bandwidth and modulation for the PRA Build Type, and
the factory set duplexer TX and RX frequencies.
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
The details contained within these fields are self-explanatory. The section also contains a
PRA B Details button, which you can use to display the Pedigree Details box. This lists the
Part Number, Serial Number and Build Level for the PRA Hardware, the Version and Type
for the PRA Software, the occupied bandwidth and modulation for the PRA Build Type, and
the factory set duplexer TX and RX frequencies.
PMA Information
For a DXR 700 terminal, the PMA Information section contains the following fields:
• Part Number
• Serial Number
• Software Version
The details contained within these fields are self-explanatory. The section also contains a
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.
RMA Information
For a non-protected DXR 700 terminal, the RMA Information section contains the following
fields:
• Part Number
• Serial Number
• Software Version
The details contained within these fields are self-explanatory. The section also contains a
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
The details contained within these fields are self-explanatory. The section also contains a
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, the Version and Type for the ODU
Software, and the TX and RX frequencies the duplexer was set to at the factory.
RMA A Information
For a protected DXR 700 terminal, the RMA A section contains the following fields:
• Part Number
• Serial Number
• Software Version
The details contained within these fields are self-explanatory. The section also contains a
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.
RMA B Information
For a protected DXR 700 terminal, the RMA B section contains the following fields:
• Part Number
• Serial Number
• Software Version
The details contained within these fields are self-explanatory. The section also contains a
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 A Information
For a protected DXR 700 terminal, the ODU A section contains the following fields:
• Part Number
• Serial Number
• 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 ODU Details box. This lists the Part Number,
Serial Number and Build Level for the ODU Hardware, the Version and Type for the ODU
Software, and the TX and RX frequencies the duplexer was set to at the factory.
ODU B Information
For a protected DXR 700 terminal, the ODU B section contains the following fields:
• Part Number
• Serial Number
• 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 ODU Details box. This lists the Part Number,
Serial Number and Build Level for the ODU Hardware, the Version and Type for the ODU
Software, and the TX and RX frequencies the duplexer was set to at the factory.
6GTOKPCN&GVCKNUHQT&:4
The Terminal Details page is divided into the following sections:
• General Information
• Hardware
• Software
General Information
The General Information section contains the following fields:
• Terminal Name
• Terminal Number
• Terminal Type
• Software Version
• Software Type
• Band
The details contained within these fields are read from the DXR 200 terminal.
Hardware
The Hardware section contains the following fields:
Slot
Module Type
PartNumber
Serial Number
Revision
HSC (Hardware Software Compatability)
The details contained within these fields are read from the DXR 200 terminal.
Software
The Software section contains the following fields:
Slot
Module
Status
Version
The details contained within these fields are self-explanatory.
0/5&GVCKNU
The NMS Details page is divided into the following sections:
• General Information
• Pedigree Information
General Information
The General Information section contains the following fields:
• 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.
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.”
Pedigree Information
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 NMS Board Hardware, and the Version and
Type for the NMS Board Software.
5/#&GVCKNU
The SMA Details page is divided into the following sections:
• General Information
• SMA
• SMA Name
The Site Name and the SMA Name fields contain the names read out from the SMA. These
may not be the names assigned in the blueprint.
SMA
The SMA 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 window. This lists the Part
Number, Serial Number and Build Level for the SMA Hardware, and the Version and Type
for the SMA Software.
• Board ID text
• Part Number
• Serial Number
• Software Version
The Board ID text will contain one of the following:
• High speed daughter board installed
%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.
Tributary Loopbacks
The Tributary Loopbacks section allows you to select the following types of loopbacks:
• No Tributary Loopback (default)
• Line Facing
• Radio Facing
Select an option by clicking on the appropriate radio button with the mouse. The centre of the
selected button is filled to show that it has been selected.
Note: You can select only one of the three options at any one time.
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.
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:
• 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.
FEC DISABLE. FEC disable turns off the forward error correction function, and therefore
increases the number of errors output from the terminal.
Note: You can only select these functions for the local terminal.
You can use these functions to test the data integrity of the terminal, and to help locate where
any integrity problems are occurring. When you enable a loopback, the terminal feeds any
received input data back to the source. You can then input a known bit-stream, check the bit-
stream output from the terminal, and compare the output stream with the input stream,
identifying any errors.
When you select the Digital Loopbacks option, the loopback is made between the composite
digital transmit and receive streams inside the radio modem, before the streams are passed to
digital-to-analog 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.
You would select the FEC Disable option in conjunction with one of the other RF modem
loopbacks to determine the true transmission error-rate. You must 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.
• 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 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 to show it has been selected.
Note: You must select Manual operation before the Radio listing and radio buttons are
displayed, i.e. before you can select a radio.
You can select either the A-Side (default) or B-Side radio by clicking on the appropriate radio
button with the mouse. The centre of the button you have selected is filled 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 allows you to select and run any
available test script files.
/CKPVGPCPEG9QTMURCEG
You can use the Maintenance Workspace to diagnose any faults in a DXR NETwork element.
The monitoring and diagnostic functions available include:
• Alarm information
• Constellation diagrams
• Equalizer Graphs
• AGC/RSSI graphs
• SNR readings
• line and radio facing loopback functions for the terminal tributaries, and digital and IF
loopback functions for the terminal RF/Modem links
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.
Note 4: DXR NET will always try to use the combination of SMA IP address and Terminal
number to communicate with any DXR 200 terminal in the blueprint.
The Alarms, Controls, Terminal Details, SMA 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.
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 to monitor signal
performance.
DXR NET provides 24-hour constellation monitoring. Every point is shown from the time the
signal was sent out. This historical view of data points is valuable for analysing and tracking
interference and its possible causes. Previously, only the first 10,000 points were displayed.
Now an unlimited number of data points can be displayed over time (limited only by display
resolution).
The Constellation page is divided into the Select Terminal and the Constellation Diagram
sections.
For a DXR 700, the appearance of these two sections is dependent 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.
Note: The multi-carrier option is not supported by the DXR 100.
Select Terminal
For a DXR 100, or a DXR 700 with the Single view selected, the Select Terminal section will
contain the following buttons:
• Local (for an unprotected terminal), or Local Radio A, Local Radio 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
clear the plots obtained up to that time.
For a DXR 700 with the Multi-carrier view selected, the Select Terminal section will contain
the following buttons:
• Carrier n (where n varies from 1 to the total number of available signal channels)
• Monitor All
• Reset All
By selecting from the Carrier n buttons, you choose the carriers for which constellation
diagrams will be displayed in the Constellation Diagram section.
Note: Only the carriers to the local DXR 700 terminal can be monitored.
When you select the Monitor All button, DXR NET will start monitoring all available carriers
on the local DXR 700 terminal. When you select the Reset All button, DXR NET will clear the
plots obtained up to that 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
• 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 clear all the plots obtained up to 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
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.
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.
Select Terminal
The Select Terminal section contains the following buttons:
• Local (for an unprotected DXR 100), or Local A, Local 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 clear all the plots obtained up to that 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 that were
chosen using the Local or Remote buttons in the Select Terminal section:
77 DMC STRATEX NETWORKS
APRIL 2001
IOM-NMS-2/2.5
Introduction to DXR NET
• 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 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.
When you select the Monitor button, DXR NET will start monitoring all the selected
terminals. 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 (+5V and 0V).
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.
'SWCNK\GT)TCRJ
SELECTING OTHER OPERATIONS. You cannot select other operations while Equalizer
Graph monitoring is in progress.
STOPPING MONITORING. You must remember that just because an Equalizer Graph is
not shown for a terminal or carrier does NOT mean the terminal or carrier is not being
monitored.
The Equalizer Graph page is used to give an indication of any multi-path fading over the
DXR 100 link. The page has two bar-graphs, one for FFE (Feed-Forward Equalization), and
one for DFE (Decision Feedback Equalization).
The Equalizer Graph page is divided into the Select Terminal and Terminal sections.
Select Terminal
The Select Terminal section contains the following buttons:
• Local (for an unprotected DXR 100), or Local A, Local 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 Terminal 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 DFE and FFE
from all available terminals. When you select the Reset All button, DXR NET will clear all the
plots obtained up to that time.
Terminal
The Terminal section will display the following items for each of the terminals that were
chosen using the Local or Remote buttons in the Select Terminal section:
• DFE Graph
• FFE Graph
• Monitor button
• Reset button
As already stated, the Terminal section contains a continuous bar-graph display of the DFE
and FFE for the selected terminals.
When you select the Monitor button, DXR NET will start monitoring all the selected
terminals. When you select the Reset button, DXR NET will clear the graphs.
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.
455+
SELECTING OTHER OPERATIONS. Except for the Constellation page operations, you
cannot select other operations while RSSI graph 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.
The RSSI page is divided into the Select Terminal and the RSSI graph sections.
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 DXR 700), or Local Radio A, Local Radio B (for a protected
DXR 700)
• Remote (for an unprotected DXR 700) or Remote Radio A, Remote Radio 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 will start monitoring all the baseband
signals from all available terminals. When you select the Reset All button, DXR NET will
clear all the plots obtained up to that point in time.
If the Multi-carrier option is selected in the Maintenance menu, the Select Terminal section
will contain the following buttons:
• Carrier n (where n varies from 1 to the total number of available signal channels)
• Monitor All
• Reset All
By selecting from the Carrier n buttons, you choose the carriers for which graphs will be
displayed in the RSSI Graph section.
Note: Only the carriers to the local terminal can be monitored.
When you select the Monitor All button, DXR NET will start monitoring all available carriers
on the local terminal. When you select the Reset All button, DXR NET will clear all the plots
obtained up to that point in time.
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 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 0 dBm and -100dBm respectively.
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
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.
+PUVCNNKPI&:40'6
+PVTQFWEVKQP
This section covers the following:
• Requirements (ie, what a PC needs to run DXR NET)
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
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
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.
*CTFYCTG4GSWKTGOGPVU
Note: The hardware requirements listed below are for the DXR NET NMT 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.
The minimum hardware requirements for DXR NET NMT are as follows:
• 133 MHz Pentium Processor
• 64 MB RAM
• 800 x 600 resolution, 256 colour display (16 bit colour recommended)
• 2 or 3-button Mouse
• 101-key US keyboard
+PUVCNNKPI&:40'6KP9KPFQYU
After ensuring that you have fulfilled all the conditions for Windows 95 detailed under
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).
• Starting-up Windows “Dial-up” Networking for the first time with the DMC DXR
driver utility.
4GOQXKPI&:40'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.
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%
TCP/IP NETWORKING. Your PC must have TCP/IP networking installed to use DXR NET
You will need to install TCP/IP on your PC to let it use the NMS connection. This requires
you to:
• Install the TCP/IP protocol, and bind it to the Dial-Up Networking adaptor.
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 3: Click Add, Microsoft in the Manufacturers column, and then click Microsoft
TCP/IP.
Step 4: Click the adapter you want to bind to the TCP/IP protocol, and then click Properties.
Step 5: On the Bindings tab, make sure the checkbox for the appropriate protocol is
checked.
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.
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: Select the IP Address page, and type your PC IP address and subnet mask
Note: On the Bindings tab, it is recommended that you click to clear the File and printer
sharing check box.
+PUVCNNKPI&:40'6
The installation is carried out using DXR NET InstallShield utility. The procedure is as
follows:
Note: DMC Stratex Networks 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.
+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:
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.
+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 1: Select the Start button.
Step 2: Select Settings, Control Panel from the Start button menu.
Step 3: Select the Modems icon from the Control Panel window.
Step 7: Select Have Disk, and use Browse Program Files to find nmsmodem.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.
5VCTVKPI9KPFQYUsK&KCNWRL0GVYQTMKPIHQTVJG(KTUV6KOG
After installation, you will need to go through the following procedure to start up Windows®
“Dial-up” Networking:
Procedure
Step 1: Select the Start button.
Step 2: For Windows '95, select Programs, Accessories, Dial up Networking, from the Start
button menu.
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.
89 DMC STRATEX NETWORKS
APRIL 2001
IOM-NMS-2/2.5
Installing DXR NET
Step 8: Select the correct Country Code, then select Next, Finish.
Step 9: Right click on your new connection (named in Step 4), then select Properties.
Step 10: Select Server Type button. If required, set the defaults to PPP (Point-to-Point
Protocol) and Windows 95.
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
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".
+PUVCNNKPI&:40'6KP9KPFQYU
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).
• Starting-up Windows “Dial-up” Networking for the first time with the DMC DXR
driver utility.
4GOQXKPI&:40'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.
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%
TCP/IP NETWORKING. Your PC must have TCP/IP networking installed to use DXR NET
You will need to install TCP/IP on your PC to let it use the NMS connection. This requires
you to:
• Install the Windows 98 TCP/IP protocol, and bind it to the Dial-Up Networking adaptor.
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 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.
Step 2: Click TCP/IP (if there is more than one TCP/IP entry, click TCP/IP -> Dial-Up
Adapter), then click Properties.
Note: On the Bindings tab, it is recommended that you click to clear the File and printer
sharing check box.
+PUVCNNKPI&:40'6
DXR NET is installed from CD. The installation is carried out using DXR NET InstallShield
utility. The procedure is as follows:
Note: DMC Stratex Networks 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.
+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:
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.
+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 1: Select the Start button.
Step 2: Select Settings, Control Panel from the Start button menu.
Step 3: Select the Modems icon from the Control Panel window.
Step 7: Select Have Disk, and use Browse Program Files to find nmsmodem.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.
5VCTVKPI9KPFQYUsK&KCNWRL0GVYQTMKPIHQTVJG(KTUV6KOG
Procedure
Step 1: Select the Start button.
Step 2: Select Programs, Accessories, Dial up Networking, from the Start button menu.
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.
+PUVCNNKPI&:40'6KP9KPFQYU06
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:
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.
• Removing earlier versions of DXR NET from your PC (optional).
4GOQXKPI&:40'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.
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%
TCP/IP NETWORKING. Your PC must have TCP/IP networking installed to use DXR NET
You will need to install TCP/IP on your PC to let it use the NMS connection. This requires
you to:
• Install the TCP/IP protocol, and bind it to the Dial-Up Networking adaptor.
Step 4: Click No in the TCP/IP dialog box asking if you want to use DHCP.
Step 5: Enter the location of the “I386” files into the Windows NT Setup dialog box, then
click Continue.
+PUVCNNKPI&:40'6
DXR NET is installed from CD. The installation is carried out using DXR NET InstallShield
utility. The procedure is as follows:
Note: DMC Stratex Networks 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.
+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 1: Select the Start button.
Step 2: Select Settings, Control Panel from the Start button menu.
Step 3: Select the Modems icon from the Control Panel window.
Step 6: Select Have Disk, and use Browse Program Files to find nmsmodem.inf, then select
OK. This driver should be in the drivers directory, under the directory where
DXR NET was installed.
Step 11: Select the Modems icon from the Control Panel window, and check that the system
has registered your installation.
+PUVCNNKPI4#5
4GOQVG#EEGUU5GTXKEG
RAS enables you to use dial-up networking and other NT features. DXR NET uses Windows®
“Dial-up” Networking to make an NMS connection to a SMA or NMS board.
To install RAS on your PC, boot-up your PC and proceed as follows:
Procedure
Step 1: Select the Start button.
Step 2: Select Settings, Control Panel from the Start button menu.
Step 3: Select the Network icon from the Control Panel window.
Step 4: Select the Services Tab from the Network dialog box, and click Add.
Step 6: Locate and select the “I386” files on your PC, then Continue.
Step 7: In the Add RAS Device box, select the DMC DXR Driver Utility you installed on
your PC, then OK.
Step 8: In the Remote Access Setup box, select the DMC DXR Driver Utility, then
Configure.
Step 9: In the Configure Port Usage box, select Dial out only, then OK.
Step 10: Click Continue, then select File, Close in the Control Panel window.Configuring
Dial-up Networking
Procedure
Step 1: On the desktop, double-click My Computer.
Step 3: If the Location Information box appears, fill-in the required information, click
Close, then double-click Dial-up Networking.
Step 5: Enter the name you want to give to the DXR NET NMS connection into the New
Phonebox Entry Wizard box, select the “I know all about…” check box, then click
Finish.
Step 6: Double-click Dial-up Networking to display the New Phonebook Entry box.
Step 7: In the Basic page, select the DMC DXR Driver Utility in the Dial using scroll box,
the name you gave to the NMS connection in the Entry name text box, and enter a
suitable number in the Phone Number box.
Step 8: In the Server page, select “PPP:Windows NT, Windows 95 Plus, Internet…” in the
Dial-up server type scroll box, ensure that the Enable software compression and
Enable PPP LCP extensions check boxes are selected, and that only the TCP/IP
check box is selected in the Network protocols section, then click TCP/IP Settings....
Step 9: In the PPP TCP/IP Settings box, ensure that Server assigned IP address, Server
assigned name server address, Use IP header compression, and Use default gateway
on remote network are all selected, then click OK.
Step 10: In the Security page, click “Accept any authentication…”, then OK.
7UKPI&:40'60/6
)GPGTCN
This section describes how to use DXR NET. You can use this tool in four main ways:
• To design a network blueprint.
&GUKIPKPI0GVYQTM$NWGRTKPVUYKVJVJG&:40'6
DXR NET enable you to view the entire connected network.
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.
• 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.
• To add a DXR 200 under SMA control, first add the SMA, select the SMA in the
DXR NET Explorer Tree pane, select the required DXR 200 from the Add Network
Element window, then click the OK button. Refer to Appendix G: "Using DXR NET with
DXR 200" for full instructions.
• 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.
%TGCVKPICPQP0/5$NWGRTKPV
You can create a blueprint for a non-NMS network using the following procedure:
Note: We advise you create the blueprint while working offline.
Procedure
Step 1: From the desktop, run DXR NET.
Step 2: Click on the Configuration Workspace button from the Workspace Selection screen.
Step 3: The Explorer Tree pane will have the Network icon followed by “Network” at 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>.
101 DMC STRATEX NETWORKS
APRIL 2001
IOM-NMS-2/2.5
Using DXR NET NMT
Note: The right-click menu for the DXR 200 icon contains the following elements: Export
Network Element, Rename and Delete.
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: When you have finished using DXR NET, select File from the menu bar, and then
Exit.
'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.
Note: If you use a Terminal Number in the Terminal Name field, ensure that it is the correct
Terminal Number.
MEDICAL
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 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.
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 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. Select the Commit button from the
DXR NET toolbar to save any changes you make to the blueprint.
Step 9: Right-click on the NEWTOWN site icon in the Explorer Tree pane, then select 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-OLDTOWN, then press <Enter>.
Step 10: Select the NEWTOWN-OLDTOWN 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. Select the Commit button from the
DXR NET toolbar to save any changes you make to the blueprint.
Step 11: Right-click on the OLDTOWN site icon in the Explorer Tree pane, then select 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 OLDTOWN-NEWTOWN, then press <Enter>.
Step 12: Select the OLDTOWN-NEWTOWN 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. As the NEWTON-OLDTOWN
terminal already exists in the blueprint, you should select it as the remote terminal
for OLDTOWN-NEWTOWN. 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
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 SEATOWN-NEWTOWN, then press <Enter>.
Step 14: Select the SEATOWN-NEWTOWN 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. As the NEWTON-SEATOWN
terminal already exists in the blueprint, you should select it as the remote terminal
for SEATOWN-NEWTOWN. 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.
Step 16: If you are finished using DXR NET, select File from the menu bar, and then Exit.
You are now returned to the PC desktop. You can now use the blueprint to connect to 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
&:40/50GVYQTM+2#FFTGUUKPI4GSWKTGOGPVU
&:4CPF
QPN[
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 to its destination via the port associated with the message
Destination IP address. Hence, each NMS element on a DXR NETwork requires three things:
• its own IP address
+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:
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:
Destination IP Address = 128.132.96.17 Decimal = 10000000.10000100.01100000.00010001
Mask IP Address = 255.255.255.0 Decimal = 11111111.11111111.11111111.00000000
Binary AND Result = 10000000.10000100.01100000.00000000
= 128.132.96.0
For Port 3:
Destination IP Address = 128.132.21.48 Decimal = 10000000.10000100.00010101.00110000
Mask IP Address = 255.255.0.0 Decimal = 11111111.11111111.00000000.00000000
Binary AND Result = 10000000.10000100.00000000.00000000
= 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
&:40/5'NGOGPV+2#FFTGUUKPI
DMC recommend that DXR NMS elements 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.
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.
• NMS In. Used to make NMS connections to other DXR 100 terminals, or to
SMA. Connections are made by cable.
• 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.
• NMS In. Used to make NMS connections to other SMA, or to DXR 100
terminals. Connections are made by cable.
• AUX A to AUX D. Used to connect the SMA to the AUX port on a DXR 700.
• V.24 A to V.24 D. Used to connect the SMA to the V.24 port on a DXR 200 and
DXR 700.
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.
The V.24 entry in a routing table refers to the DXR 100 V.24 port, the DXR 200
V.24 port, and the SMA Setup port.
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 recommended, 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, not the specific IP addresses
of all the elements.
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.
• 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: 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 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
available tabbed pages in the Configuration workspace. Either accept the default
settings, or enter the values you require. 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.
Step 12: If you are finished using DXR NET, select File from the menu bar, and then Exit.
'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. More such towers are to be installed in the immediate future,
so you have decided to use a DXR 700 under SMA control for this link, making it easier to
add links later. The link to the port is well-established and unlikely to change and 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 running between one of the SMAs and one of the DXR 124 terminals.
You can now select the NMS element names. The most useful information you can use is the
location of the element, 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. At the moment, you have not created the IP addresses, so these will be added to the
NMS element names later. In this case, the names are:
• TOWN SMA
• BEACH SMA
• TOWN NMS
• PORT NMS
You can now select the terminal names. The most useful information you can use is the link
the terminal belongs to, and the end of the link the terminal is situated. 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, giving the local site name first. The names should be separated with a hyphen,
and can be shortened to be viewed in the Explorer Pane. For example, the DXR 124 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
BEACH- TOWN-
TOWN-A BEACH-A
TOWN NMS PORT NMS
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. Place the
SMAs and the DXR 700 terminals they control in one sub-net, and the two DXR 124
terminals in the other. Give the first sub-net an address of 1, and the second an address of 2.
From the sub-net addresses, you know that the SMA IP address will begin with 10.1, and 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 normally set to 1.
BEACH- TOWN-
TOWN-A BEACH-A
TOWN NMS PORT NMS
AUX A AUX A 10.2.1.1 10.2.2.1
BEACH TOWN TOWN- PORT-
SMA SMA PORT TOWN
10.1.2.1 10.1.1.1
10.1.2.0 TOWN-
BEACH-A
Radio
AUX A
TOWN 10.2.1.0
10.1.1.0 SMA 10.2.2.0
(PC) V.24 10.1.1.1 NMS
In
10.1.2.0 (PC)
V.24
10.2.1.0 (PC)
V.24
10.1.1.0 TOWN
10.1.2.0 NMS 10.2.2.0
NMS
10.2.1.1
Out
10.2.2.0
V.24
10.1.1.0 PORT
10.1.2.0 NMS
10.2.1.0 Radio 10.2.2.1
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 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.
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 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
available tabbed pages in the Configuration workspace. Either accept the default
settings, or enter the values you require. Select the Commit button from the
DXR NET toolbar to save any changes you make to the blueprint.
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-A, then press <Enter>.
Step 10: Select TOWN-BEACH-A icon 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. Select the Commit button from the
DXR NET toolbar to save any changes you make to the blueprint.
Step 11: Right-click on the TOWN site icon in the Explorer Tree pane, then select 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
Tree pane, followed by the default name. Click on the default name, and type in
TOWN-PORT, then press <Enter>.
Step 12: Select the TOWN-PORT 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. Select the Commit button from the
DXR NET toolbar to save any changes you make to the blueprint.
Step 13: Double click the TOWN-PORT terminal in the Explorer Pane to display the NMS
board icon, and name the board TOWN NMS 10.2.1.1. Then go through each of the
available tabbed pages in the Configuration workspace. Either accept the default
settings, or enter the values you require. 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
Tree pane, followed by the default name. Click on the default name, and type in
PORT-TOWN, then press <Enter>.
Step 15: Select the PORT-TOWN 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. As the TOWN-PORT terminal already
exists in the blueprint, you should select it as the remote terminal for PORT-TOWN.
Select the Commit button from the DXR NET toolbar to save any changes you make
to the blueprint.
Step 16: Double click the PORT-TOWN terminal in the Explorer Pane to display the NMS
board icon, and name the board PORT NMS 10.2.2.1. Then go through each of the
available tabbed pages in the Configuration workspace. Either accept the default
settings, or enter the values you require. Select the Commit button from the
DXR NET toolbar to save any changes you make to the blueprint.
Step 17: Right-click on the BEACH site icon in the Explorer Tree. Select an SMA from 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
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
settings, or enter the values you require. 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
Tree pane, followed by the default name. Click on the default name, and type in
BEACH-TOWN-A, then press <Enter>.
Step 20: Select BEACH-TOWN-A icon 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. As the TOWN-BEACH-A terminal already
exists in the blueprint, you should select it as the remote terminal for BEACH-
TOWN-A. Select the Commit button from the DXR NET toolbar to save any 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.
Step 23: If you are finished using DXR NET, select File from the menu bar, and then Exit.
You are now returned to the PC desktop. You can now use the blueprint to connect to the
network as described in “Connecting to the Network with a Network Blueprint”.
5GPFKPI0GVYQTM$NWGRTKPVUXKC'OCKN
You can send blueprints as e-mail attachments provided:
• You send both the .net file and the .dxr folder associated with the blueprint.
Procedure
Step 1: Using Windows Explorer, locate the .net file and the .dxr folder associated with the
blueprint (these will both have the name you saved the blueprint under).
Step 2: Use WinZip to compress the file and folder to the same ZIP file.
Step 3: Attach the ZIP file to an e-mail sent to the receiving PC.
Step 4: At the receiving PC, extract the attached ZIP file to a location on the PC hard drive.
Step 5: Start up DXR NET on the receiving PC, and check that you can open the blueprint.
9QTMKPIYKVJC&:40'6YQTMCPF0GVYQTM'NGOGPVU
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.
0GVYQTM8KUKDKNKV[
Even with a full blueprint loaded, your ability to view a site or network element on the
network depends on two things:
• The type of network element your PC is connected to.
• For remote elements (ie, elements accessed via a radio link), whether the radio link is
operational.
• When the connection is to a DXR 100 without a NMS board, or a DXR 700, you will be
able to access only the data stored in the local and terminal remote terminals.
• When the connection is to a SMA, or a DXR 100 with the NMS option, you will be 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.
Figure 42: DXR 700 PMA Front Panel Layout - location of connector V.24
Figure 43: DXR 100 Front Panel Layout - location of connector V.24
0/5%QPPGEVKQPU
NMS connections are used connect to a SMA, or to a DXR 100 or DXR 200 with NMS
option.
Note: Your PC must have Windows® “Dial-Up” Networking enabled for NMS
connections. Refer to Section 3 for details.
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.
• 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 via the cable supplied by DMC for this purpose.
Connect to the SMA as described above. Connect a V.24 cable from a V.24 connector on the
DXR 2-00 CTC module, or via a null modem to the DTI connector on the neon of the DXR
200 module.
'VJGTPGV%QPPGEVKQP
Ethernet connections are used connect to a SMA.
To use the Ethernet connection:
• Your PC must have an Ethernet port set up.
• The SMA LAN connection (direct or via a router) must be via the LAN port on the SMA,
not the SMA Setup port.
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.
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 a 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.
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 DMC Direct Connection or
modem driver) that DXR NET uses in the Options section. As a connection via a
dial-up modem will be slower, select the Dial-up Modem Delay check box if you are
using a modem. This will increase the time DXR NET waits for a response before
deciding the connection has failed.
Step 5: Select the Ethernet button to connect to a SMA via a LAN (directly, or via a router).
Step 6: Click the Save Settings button if you wish to make the selected connection type the
default setting,
Step 7: Click the OK button to change the connection type to the connection type.
DXR NET will now use the connection type you have selected.
%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.
Procedure
Step 1: From the desktop, run DXR NET.
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
#WVQFKUEQXGT[
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 Autodiscovery feature only reads site and network element names. You must
read the configuration from a network element before carrying out any operations on
it.
Note 2: 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 3: The Autodiscovery feature cannot be used if you are connected to the network via
Ethernet.
Note 4: If the Autodiscovery feature detects unsupported software in an element, it will set
the element in the blueprint to a supported software version. This will enable
DXR NET to communicate with the element.
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:
Procedure
Step 1: From the desktop, run DXR NET.
Step 2: Select the Configuration workspace from the Workspace Selection screen.
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 read the configuration from any element you can
see in the blueprint, and use the Configuration, Commissioning and Maintenance
Workspace functions as required.
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.
7UKPI&:40'6VQ%QPHKIWTGC6GTOKPCN
+PVTQFWEVKQP
This section covers the operations you should take to configure a terminal. 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 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 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 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 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.
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.
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.
DMC Stratex Networks advises that when checking or modifying the data, you have hard
copy of the expected values available to refer to before beginning the procedure.
DMC Stratex Networks advises that you save the configuration data of all your terminals
after initial setup and after any changes are made.
%QPHKIWTKPIC6GTOKPCN7UKPIC/CUVGT$NWGRTKPV
This procedure covers configuring either a DXR 700 or a DXR 100 without NMS from a
master blueprint. You will use DXR NET to:
• check the terminal name
• 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, except when
the terminal is a DXR 700 under the control of a SMA. In this case, the PC is connected to the
Setup connector on the controlling SMA.
You know what the name of the terminal is in the master blueprint.
Note 1: Great care should be taken that the parameters are correct before writing 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 blueprint default values to a terminal, DXR NET will ask you
to confirm the action.
Procedure
Step 1: From the desktop, run DXR NET.
Step 2: Select the Configuration Workspace from the Workspace Selection window.
Step 3: Select the Connect button from the DXR NET toolbar. After autodiscovery is
successfully completed, a blueprint containing the terminal will appear in the
Explorer Tree. Select the terminal, and click the Read Configuration button to read
the terminal configuration.
Step 4: Check that the name of the terminal matches the name in the master blueprint. If not,
right-click on the terminal icon in the Explorer Tree, select Rename from the drop-
down menu, then change the name to match the blueprint.
Step 5: Select the Disconnect button, then click File in the DXR NET menu bar, and select
Open from the drop-down menu. Load the master blueprint by selecting the
blueprint file, then click the OK button.
124 DMC STRATEX NETWORKS
APRIL 2001
IOM-NMS-2/2.5
Using DXR NET NMT
Step 6: Select the Connect button from the DXR NET toolbar. After connection is
successfully completed, select the terminal in the Explorer Tree, then click the Read
Configuration button.
Step 7: Go through the Configuration workspace pages, making any changes as required.
Refer to the specific operations detailed later in this section for details. Select the
Commit button after making any changes to ensure you save them to the blueprint.
Step 8: When you are satisfied with the details in the Configuration workspace pages, 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 9: 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 10: Select Save or Save As from the File menu to save the blueprint. This blueprint is
known as the "field blueprint".
Step 11: If this is the second terminal of a link, the link should now be operational. To
confirm this, check that you can access the far end terminal by clicking on its icon in
the Explorer Tree, and then select the Commissioning Workspace to check if any
alarms are present.
Step 12: 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.
%QPHKIWTKPICVGTOKPCNHTQOEQPHKIWTCVKQPUJGGVU
This procedure covers configuring a DXR 700 terminal working from configuration sheets.
You will use DXR NET to:
• use the autodiscovery feature to connect to the terminal
• 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, except when
the terminal is a DXR 700 under the control of a SMA. In this case, the PC is connected to the
Setup connector on the controlling SMA
you know what the name of the terminal should be
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.
Procedure
Step 1: From the desktop, run DXR NET.
Step 2: Select the Configuration workspace from the Workspace Selection screen.
Step 3: Selecting the Connect button from the DXR NET toolbar. After autodiscovery is
successfully completed, a blueprint containing the terminal will appear in the
Explorer Tree.
Step 4: Click the Read Configuration button from the DXR NET toolbar to read the terminal
settings into the Configuration workspace.
Step 5: Go through the Configuration workspace pages, making any changes as required.
Refer to the specific operations detailed later in this section for details. Select the
Commit button after making any changes to ensure you save them to the blueprint.
Step 6: When you are satisfied with the details in the Configuration workspace pages, 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 7: 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 8: Select Save or Save As from the File menu to save the blueprint. This blueprint is
known as the "field blueprint".
Step 9: If this is the second terminal of a link, the link should now be operational. To
confirm this, check that you can access the far end terminal by clicking on its icon in
the Explorer Tree, and then select the Commissioning Workspace to check if any
alarms are present.
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.
&:4&GRNQ[OGPV
Refer to Appendix G
$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
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.
7UKPI&:40'6VQ%QPHKIWTGC0/57PKV
+PVTQFWEVKQP
This section covers the operations you should take to configure a NMS unit (SMA or
DXR 100 with NMS board) using a master blueprint. The network designer uses DXR NET to
create a master network blueprint or Design blueprint, containing all the information required
to configure the unit. This blueprint is then used at the time of installation to load the unit
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.
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 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.
DMC Stratex Networks advises that when checking or modifying the data, you have hard
copy of the expected values available to refer to before beginning the procedure.
DMC Stratex Networks advises that you save the configuration data of all your network
elements after initial setup and after any changes are made.
%QPHKIWTKPIC0/57PKV
This procedure covers configuring a NMS unit from a master blueprint. You will use
DXR NET to:
• connect to the unit using autodiscovery
• save any changes that are made to the unit configurations for later use
• save the modified Field blueprint for later use in a Commissioned blueprint
The following assumptions have been made:
• the unit has been installed, connected to power, and has been successfully powered up
• the DXR NET PC is connected to either the Setup connector on the SMA front panel or the
V.24 port on the DXR 100 front panel
• you know what the IP address of the unit is in the master blueprint
Note 1: Great care should be taken that the parameters are correct before writing any
changes to an unit.
Note 2: If you attempt to write default routing table values to a NMS unit, DXR NET will ask
you to confirm the action.
Procedure
Step 1: From the desktop, run DXR NET.
Step 2: Select the Configuration workspace from the Workspace Selection screen.
Step 3: Select the Connect button from the DXR NET toolbar. DXR NET will perform
autodiscovery, and a blueprint containing the NMS unit you are attached to will
appear in the Explorer Tree window. The NMS unit you are attached to will have a
small red plug symbol.
Step 4: Select the NMS unit in the Explorer Tree, and set the unit Real Time Clock and IP
address (refer to Setting the Real Time Clock and Setting the IP Address procedures
in this section).
Step 5: Once the new address has been written, the NMS unit will drop the network
connection to your PC, and DXR NET will ask if you want to reconnect. Select No,
Step 7: Select the Connect button from the DXR NET toolbar. DXR NET will mark the NMS
unit you are connected to on the Explorer tree with a small red plug symbol. Ensure
that the correct unit is selected in the tree before attempting to load the configuration
from the blueprint. If the correct unit is not selected, check the unit IP address in the
blueprint, click the Disconnect button in the DXR NET toolbar, close the blueprint,
then go back to Step 3.
Step 8: After you have ensured the correct NMS unit 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.
Step 9: Select the Write Configuration button from the DXR NET toolbar, then select Start
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 NMS unit icon in
the Explorer Tree, then select Write Configuration from the drop-down menu and
save the unit configuration to file.
Step 10: When you are finished viewing or modifying the network, save the blueprint, click
on the Disconnect button in the DXR NET toolbar, then select Exit from the File
menu.
5GVVKPIVJG+2#FFTGUUHQTC0/57PKV
NMS units (SMAs or NMS boards) use IP to communicate with other equipment, either
directly connected, or connected via a network. Because of this, each NMS unit must have its
own unique IP address.
Note: See earlier in this section for a simple IP address selection procedure.
To set the IP address for an NMS unit, connect to the unit (either using the Autodiscovery
feature or with the network blueprint loaded), then proceed as follows:
Procedure
Step 1: Select the NMS unit in the Explorer Tree.
Step 4: Double-click on IP address column entry for the NMS unit, and then type in the new
address.
Step 5: If the field in the IP Address Mask column for the NMS unit IP address is not
255.255.255.255, then double-click on the field and type in 255.255.255.255.
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, type in the correct IP address of
the NMS unit you are trying to connect to.
Step 9: After you have written the new IP address to the NMS unit, the connection to the
network will be dropped. DXR NET will then ask you if you wish to reconnect.
Select No. The changes you have made will now be reflected in the network
blueprint.
5GVVKPIVJG6GTOKPCN(TGSWGPEKGUCPF6TCPUOKVVGT2QYGT
You can change the transmit and receive frequencies and RF output power of a terminal using
the following procedure.
SETTING THE TERMINAL FREQUENCIES AND TRANSMITTER POWER. The
terminal frequencies and transmitter output power are dependent on the duplexer. 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.
Procedure
Step 1: Select the terminal in the Explorer Tree.
Step 4: 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 5: 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.
Step 6: 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.
5GVVKPIVJG0/57PKV4GCN6KOG%NQEM
Both the SMA and the NMS board have an internal clock to synchronize their operations. To
set this clock, proceed as follows:
Note: If the Real Time Clock is not set, an alarm (Real Time Clock not set) is generated
for the NMS unit. See Appendix A for details.
Procedure
Step 1: Select the NMS unit in the Explorer Tree.
Step 3: Select Set Real Time Clock from the drop-down menu.
5GVVKPIWRVJG4QWVGVQC2%HQTC0/57PKV
You can use the following procedure to set up a route by which the NMS unit can
communicate with any attached PC. For a SMA, the PC will be connected to the Setup port,
for a DXR 100 with NMS board, the PC will be connected to the V.24 port.
Note 1: The following assumes that you have already changed the NMS unit IP address from
the default factory setting. If this is not the case, refer to Setting the IP Address for a
NMS Unit, then return to this procedure.
Note 2: We advise you set the route to the PC before setting up the routes to any other
equipment.
Procedure
Step 1: Select the Configuration Workspace.
Step 3: Press the Insert key on the PC to add a new row to the table.
Step 3: Take the NMS unit IP address, make the last field in the address zero, then enter 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 V.24
from the drop-down list.
Step 6: 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.
Step 7: If you are not going to make any further changes to the terminal configuration, select
the Write Configuration button in the Toolbar. The NMS unit configuration will
now change to reflect the values set in the blueprint.
5GVVKPI7RVJG4QWVKPI6CDNGHQTC0/57PKV
NMS units (SMAs or NMS boards) use IP to communicate with other equipment, either
directly connected, or connected via a network. Each device on the network has a unique IP
address, and all messages sent using IP will contain the address of the device the message is
intended for (i.e. the destination IP address). When a NMS unit receives a message, it looks at
the destination IP address, and uses this to try and route the message to its intended
destination. The NMS unit therefore needs two sets of information:
• the IP addresses of all the other devices on the network
Procedure
Step 1: Select the NMS unit in the Explorer Tree.
Step 4: Press the Insert key on the PC to add a new row to the table.
Step 5: Take the address of one of the IP devices on the network, make the last field in this
address zero (e.g. for an IP address of 123.123.123.123 the new address would be
123.123.123.0), then enter this new address into the Destination IP Address column.
Step 6: For the IP address entered in Step 5, enter 255.255.255.0 in the Mask Address 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
Step 9: 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.
Step 10: If you are not going to 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.
5GVVKPIWRVJG5/#+PVGTHCEGU
5GVVKPIWRVJG4CFKQ.KPM2QTVU
You can set up the radio link ports (AUX and V.24) on an SMA front panel using the
following method.
Procedure
Step 1: Select the Configuration Workspace.
Step 4: In the Port section associated with the connectors you are to configure, click on the
Local Terminal field, and select the name of the terminal the port is connected to.
Step 5: 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.
Step 6: 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.
%QPHKIWTKPIVJG'19+PVGTHCEGQPC5/#
You can configure the following:
• Volume in the EOW handset ear piece.
• The PCM Coding Law used to translate analog voice signals into digital pulses for
transmission over DXR 700 auxiliary channel.
• Whether the analog voice signal from the handset is high pass filtered or not.
You can configure the EOW interface using the following method.
Procedure
Step 1: Select the Configuration Workspace.
Step 4: In the Engineering Order Wire (EOW) section, click on the Ear Piece Volume field,
and select the volume from the drop-down list. You can choose between Normal and
Loud.
Step 5: In the Engineering Order Wire (EOW) section, click on the PCM Coding Law field,
and select the coding law from the drop-down list. You can choose between Law
and A-Law.
Step 6: 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 list. You can
choose DXR 700 (default), DXR 200 and DXR 100 tones.
Step 7: 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.
Step 8: 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.
Step 9: 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.
5GVVKPIWRVJG%NQEM5QWTEGQPC5/#
You can set up the SMA clock source using the following method.
Note 1: You would normally set the clock source to build a Clocking Hierarchy for SMA
using SDM boards. See Appendix D for details.
Note 2: For either of the Option 1 or Option 2 selections to be valid, ie, synchronization
signal coming in via optional daughter board, the relevant slot in the SMA must be
occupied by an appropriate board.
Procedure
Step 1: Select the Configuration Workspace.
Step 4: In the Clock Sources section, click on the Primary field, and select the signal source
from the drop-down list. You can choose between Free-running (default, generated
internally), one of the four AUX ports (AUX A to D), the NMS In port, the NMS
Out port, or one of Option 1 or Option 2.
Step 5: In the Clock Sources section, click on the Secondary field, and select the signal
source from the drop-down list. You can choose between Free-running (default,
generated internally), one of the four AUX ports (AUX A to D), the NMS In port,
the NMS Out port, or one of Option 1 or Option 2.
Step 6: 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.
Step 7: 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.
5GVVKPI7RVJG5/##NCTO$QCTF
You can set up an alarm board in a SMA using the following procedure:
Note 1: DXR NET will only write the configuration to an alarm board if it finds that the
board type in the SMA matches the type set in the blueprint. You should therefore
check the type of board in the SMA before attempting set-up. You can check the
board type in the SMA Details page of the Commissioning Workspace.
Note 2: If you change the Electrical State field, you will also need to alter switch settings on
the alarm board, and also links on the board, to match the new signal setting.
Note 3: You must select a number between zero and twenty in the Rate field, and you must
select an integer value.
Note 4: You can only select the signal state (input/output) for a Mk I alarm board.
Procedure
Step 1: Select the Configuration Workspace.
Step 4: Double-click on the Identifier field, and type in the name of the alarm.
Step 5: If you are setting up a Mk I alarm board, double-click on the Type field, and select
Input or Output from the drop-down list.
Step 6: Double-click on the Electrical State field, and choose the appropriate setting from
the drop-down list. You can choose between current and no current for inputs, and
closed or open for outputs.
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.
Step 8: 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.
Step 9: If you are not going to make any further changes to the terminal configuration, select
the Write Configuration button in the Toolbar. The alarm board configuration will
now change to reflect the values set in the blueprint, as long as the board type in the
SMA matches the type in the blueprint.
5GVVKPIVJG6GTOKPCN2QYGT#NCTO.KOKVU
You can set the values of forward and reverse power which trigger the terminal Forward
Power Warning, and the Reflected Power Warning (see Appendix B for details). The
procedure is as follows:
Note 1: You can set the limits to their default values by clicking the Default button.
Note 2: In a protected terminal, there will be a set of fields for each radio.
Procedure
Step 1: Select the Configuration Workspace.
Step 4: 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 5: 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.
Step 6: 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.
Step 7: 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#)%#NCTO.KOKVUHQTC&:46GTOKPCN
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 B 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 1: Select the Configuration Workspace.
Step 4: 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.
Step 5: 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.
Step 6: 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.
5GVVKPIVJG455+#NCTO.KOKVUHQTC&:46GTOKPCN
You can set the range over which the RSSI can vary without triggering the Rx Path Warning
alarm (see Appendix B for details). You set the low and high RSSI limits of a terminal using
the following procedure.
Note 1: You can set the limits to their default values by clicking the Default button.
Note 2: In a protected terminal, there will be a set of fields for each radio.
Procedure
Step 1: Select the Configuration Workspace.
Step 4: 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.
Step 5: 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.
Step 6: 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.
5GVVKPIVJG4(/QFWNCVKQPHQTC&:46GTOKPCN
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 1: Select the Configuration Workspace.
Step 4: In the Modem Parameters section, select the modulation you require from drop-
down list displayed when you click-on the Modulation field.
Step 5: 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.
Step 6: 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/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 B for details).
Note: Refer to Appendix C for values of Correctable Bytes per Second.
You can change the Maximum Correctable Bytes per Second Threshold of a terminal using
the following procedure.
Note: You can set the limit to a default value by clicking the Default button.
Procedure
Step 1: Select the Configuration Workspace.
Step 4: 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.
Step 5: 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.
Step 6: 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.
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 terminal 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 1: Select the Configuration Workspace.
Step 4: 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.
Step 5: 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 6: 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.
Step 7: 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.
/CRRKPICP'XGPVVQCP#EVKQP
You can set a network element to create a pre-set alarm action when a specific event occurs.
This is known as mapping an event to an action, and is set up in the Action Table page.
Note: The same actions can be set for more than one event.
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 that are 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:
Procedure
Step 1: Select the Configuration Workspace.
Step 3: 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 4: 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 6: 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 drop-down list, then click on the Add Action button next to the list.
The action will appear in the lower pane of the window. If you decide to remove an
action after selection, select the action in the lower pane, then click on the Delete
Action button next to the drop-down list.
Step 7: 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.
Step 8: 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.
Step 9: 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.
4GOQXKPICP#EVKQPHTQOCP'XGPV
You can remove an action that you have enabled on a network element (see Mapping an
Event to an Action) using the following procedure:
Procedure
Step 1: Select the Configuration Workspace.
Step 3: 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.
Step 4: Move down the levels of the tree in the Events pane, until you can select the event
from which you want to remove an action. Any actions mapped to the event will be
displayed in the Mapped Actions pane.
Step 5: 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.
Step 6: 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.
Step 7: 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.
5GVVKPIVJG6GTOKPCN.KPG+PVGTHCEG
5GVVKPIVJG6GTOKPCN.KPG+PVGTHCEG6[RG
You can set the terminal line interface type using the following procedure:
CHANGING THE INTERFACE TYPE. The interface type is dependent on the interface
hardware in the terminal. Any changes you make to the software must reflect the hardware.
Procedure
Step 1: Select the Configuration Workspace.
Step 3: Click on the Interface Type field in the Interface section and select the interface type
from the displayed drop-down list.
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.
Step 5: 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.
5GVVKPIVJG2CTCOGVGTUHQTCP'.KPG+PVGTHCEG
SETTING THE LINE INTERFACE PARAMETERS. The interface capacity and the
tributary impedance are both dependent on the hardware in the terminal 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.
Note: DMC Stratex Networks supplies cabling matched to the line impedance for the
interface connectors on the terminals.
You can change the terminal line parameters using the following procedure:
Procedure
Step 1: Select the Configuration Workspace.
Step 4: If you wish to change the interface capacity, select the new capacity from the drop-
down list displayed when you click on the Interface Capacity field in the Interface
section.
Step 5: 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 list. Select the new impedance from the list.
Step 6: If you wish to change the impedance of all the tributaries to the same value, change
the value of the first tributary as described in Step 4, then click on the Impedance
column heading.
Step 7: 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 8: If you wish to change the commissioned state of all the tributaries to the same value,
change the state of the first tributary as described in Step 6, then click on the
Commissioned column heading.
Step 9: 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.
Step 10: 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.
Step 11: 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.
5GVVKPIVJG2CTCOGVGTUHQTCP'.KPG+PVGTHCEG
SETTING THE LINE INTERFACE PARAMETERS. The receiver sensitivity and the
tributary wayside line build-out are both dependent on the hardware in the terminal 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.
Note: DMC Stratex Networks supplies cabling matched to the line impedance for the
tributary wayside connector on the PMA front panel.
You can change the terminal line interface parameters using the following procedure:
Procedure
Step 1: Select the Configuration Workspace.
Step 4: If you wish to change the interface receiver sensitivity, select the Rx Sensitivity
column of the table in the Tributary section, then double-click to display the drop-
down list. Select the new sensitivity from the list. You can choose from Low,
Medium (default), or High.
Step 5: If you wish to enable or disable the transmitter level boost function in the line
interface, select the Tx Level Boost column of the table in the Tributary section,
then double-click to display the drop-down list. Select True (enabled) or False
(disabled) as required.
Step 6: If you wish to enable or disable the equalizer bypass function in the line interface,
select the Equalizer Bypass column of the table in the Tributary section, then
double-click to display the drop-down list. Select True (enabled) or False (disabled)
as required.
Step 7: If you wish to change the commissioned state of the line interface, select the
Commissioned column of the table in the Tributary section, then double-click to
display the drop-down list. Select True (enabled) or False (disabled) as required.
Step 8: 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.
Step 9: 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.
Step 10: 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.
5GVVKPIVJG2CTCOGVGTUHQTC&5.KPG+PVGTHCEG
You can change the terminal line interface parameters for a DS1 type interface using the
following procedure.
SETTING THE LINE INTERFACE PARAMETERS. The receiver sensitivity and the
tributary wayside line build-out are both dependent on the hardware in the terminal 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.
Note: DMC Stratex Networks supplies cabling matched to the line impedance for the
tributary wayside connector on the PMA front panel.
Procedure
Step 1: Select the Configuration Workspace.
Step 4: 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 double-click to display the drop-
down list. 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 5: 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 double-click to
display the drop-down list. Select True (enabled) or False (disabled) as required.
Step 6: If you wish to change the coding used on the line interfaces, select the Line
Encoding field in the Tributary section, then double-click to display the drop-down
list. Select the encoding from the list.
Step 7: 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 list.
You can choose between lengths of 0-133 feet (default), 133-266 feet, 266-399 feet,
399-533 feet and 533-655 ft.
Step 8: 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.
Step 9: 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.
5GVVKPIVJG2CTCOGVGTUHQTC&5.KPG+PVGTHCEG
You can change the terminal line interface parameters for a DS3 type interface using the
following procedure.
SETTING THE LINE INTERFACE PARAMETERS. The receiver sensitivity and the
tributary wayside line build-out are both dependent on the hardware in the terminal 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.
Note: DMC Stratex Networks supplies cabling matched to the line impedance for the
tributary wayside connector on the DXR 700 PMA front panel.
Procedure
Step 1: Select the Configuration Workspace.
Step 4: If you wish to change the interface receiver sensitivity, select the Rx Sensitivity
column of the top table in the Tributary section, then double-click to display the
drop-down list. Select the new sensitivity from the list. You can choose from Low,
Medium (default), or High.
Step 5: If you wish to enable or disable the transmitter level boost function in the line
interface, select the Tx Level Boost column of the table in the Tributary section,
then double-click to display the drop-down list. Select True (enabled) or False
(disabled) as required.
Step 6: If you wish to enable or disable the equalizer bypass function in the line interface,
select the Equalizer Bypass column of the table in the Tributary section, then
double-click to display the drop-down list. Select True (enabled) or False (disabled)
as required.
Step 7: If you wish to change the commissioned state of the line interface, select the check
box in the Commissioned column of the table in the Tributary section, then double-
click to display the drop-down list. Select True (enabled) or False (disabled) as
required.
Step 8: 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 double-click to
display the drop-down list. 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 9: 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.
Step 10: 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.
5GVVKPIVJG2CTCOGVGTUHQTC56/.KPG+PVGTHCEG
You can change the terminal line interface parameters for a STM-0 type interface using the
following procedure.
SETTING THE LINE INTERFACE PARAMETERS. The receiver sensitivity and the
tributary wayside line build-out are both dependent on the hardware in the terminal 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.
Note: DMC Stratex Networks supplies cabling matched to the line impedance for the
tributary wayside connector on the DXR 700 PMA front panel.
Procedure
Step 1: Select the Configuration Workspace.
Step 4: If you wish to change the interface receiver sensitivity, select the Rx Sensitivity
column of the top table in the Tributary section, then double-click to display the
drop-down list. Select the new sensitivity from the list. You can choose from Low,
Medium (default), or High.
Step 5: If you wish to enable or disable the transmitter level boost function in the line
interface, select the Tx Level Boost column of the table in the Tributary section,
then double-click to display the drop-down list. Select True (enabled) or False
(disabled) as required.
Step 6: If you wish to enable or disable the equalizer bypass function in the line interface,
select the check box in the Equalizer Bypass column of the table in the Tributary
section, then double-click to display the drop-down list. Select True (enabled) or
False (disabled) as required.
Step 7: 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 double-
click to display the drop-down list. Select True (enabled) or False (disabled) as
required.
Step 8: 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 double-click
to display the drop-down list. Select the new impedance from the list. You can
choose between impedances of 120 ohm (default) and 75 ohm.
Step 9: 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.
Step 10: 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.
5GVVKPI7R#NCTO+PRWVUHQTC&:46GTOKPCN
You can set up an alarm input to the DXR 100 using the following procedure:
Procedure
Step 1: Select the Configuration Workspace.
Step 4: If you wish to assign a name to the alarm input, then select the relevant input
identifier field and type in the name.
Step 5: If you wish to set the normal condition of the input, i.e. the input state that 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”.
Step 6: 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.
Step 7: 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.
5GVVKPI7R#NCTO1WVRWVUHQTC&:46GTOKPCN
You can set up an alarm output from the DXR 100 using the following procedure:
Procedure
Step 1: Select the Configuration Workspace.
Step 4: If you wish to assign a name to the alarm output, then select the relevant output
identifier field, and type in the name.
Step 5: 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 6: 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.
Step 7: 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.
Step 8: 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.
%JGEMKPIHQT#NCTOU
You can check to see if there are any alarms present on a network element by viewing the
Alarms page.
Procedure 1
Step 1: Select the Commissioning Workspace.
Step 4: If the LED icon in the Alarm Status section is red, click on the View Alarms button
to display the Alarms page.
Step 5: 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
name and a description of the most likely causes will be displayed in the right hand-
panes.
Step 6: When you have identified an active alarm, take the required action to correct it, i.e.
clear the alarm condition yourself, or if this is not possible, alert the appropriate
network personnel.
Procedure 2
Step 1: Select the Maintenance Workspace.
Step 4: 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
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.
7UKPI.QQRDCEMUVQ%JGEMC.KPM
You would use the loopback functions after commissioning the link, to check the link has
been set up properly, or during maintenance, when you are investigating problems with the
link.
You will require test equipment capable of generating and monitoring a Pseudo Random Bit
Stream (PRBS), eg BERL tester or similar. You should also be familiar with the remedial
actions to be carried out when you have traced a fault to a particular piece of equipment.
These will be laid down in your servicing policy.
LOOPBACK FUNCTIONS. Loopback functions interrupt network traffic.
RF/MODEM FUNCTIONS. You should select the functions in the RF/Modem section for
the local terminal (the terminal selected in the Explorer Tree) only, as selecting them in a
remote terminal could cause you to lose communication with the terminal.
Tributary Loopbacks
The Tributary Loopbacks section allows you to select the following:
Note: You can select the functions in the Tributary Loopbacks section for both the local
terminal (the terminal selected in the Explorer Tree), and its remote terminal (the
terminal at the other end of the link).
• Line Facing
• Radio Facing
You select a function by clicking its radio button.
LOOPBACK FUNCTIONS. Loopback functions interrupt network traffic.
When you select No Tributary Loopback, there are no loopbacks enabled, and the line
interface operates as normal.
When you select the Line Facing loopback function, the line interface will connect the
terminal line inputs and outputs. Any inputs to the local line interface are therefore fed
straight back out again without going through the rest of the terminal circuitry. You would
normally enable this on the local terminal to check the operation of your test equipment
before using it to test the actual link.
RF/Modem
The RF/Modem section allows you to select the following:
LOOPBACK FUNCTIONS. Loopback functions interrupt network traffic.
RF/MODEM FUNCTIONS. You should select the functions in the RF/Modem section for
the local terminal (the terminal selected in the Explorer Tree) only, as selecting them in a
remote terminal could cause you to lose communication with the terminal.
• Digital Loopback
• IF Loopback
5GSWGPEGQH1RGTCVKQPU
Normally, you would use loopback functions on two occasions:
• During commissioning, to check the link has been set-up properly.
• Check the test equipment and the connection to the local terminal by carrying out a line-
facing loopback on the local terminal.
• Check the link by carrying out a radio-facing loopback in the remote terminal.
If the results of the radio-facing loopback are satisfactory, the link is operational, and you
need take no further action. If the results are not satisfactory, there is a fault somewhere on
the link, and you should proceed as follows:
• If the radio-facing loopback results are unsatisfactory, try to localise the fault by carrying
out Digital, IF and RF loopbacks on the local terminal.
• If the fault cannot be found on the local terminal, carry out Digital, IF and RF loopbacks
on the remote terminal
7UKPI.QQRDCEMUVQ%JGEMVJG6GUV'SWKROGPVCPFVJG6GTOKPCN
%QPPGEVKQP
Before you can use your test equipment to monitor the performance of a link, it is a good idea
to check both the test equipment, and the connection between it and the terminal. Proceed as
follows:
Procedure
Step 1: Attach your test equipment to the line interface of the local terminal.
Step 2: Select the local terminal in the DXR NET Explorer Pane.
Step 5: Select the Line Facing loopback function from the Tributary Loopback section, click
the Apply button, then the OK button in the displayed Warning box.
Step 6: Compare the bit-stream output from the terminal against the input stream from your
test equipment.
Step 7: After you are finished comparing the bit-streams, select the No Tributary Loopback
radio button, then click the Apply button.
If any differences between the bit-streams are within the desired limits, go to “Using
Loopbacks to Check the Link”. If the differences are outside the limits, check:
• The connection between the test equipment and the terminal.
7UKPI.QQRDCEMUVQ%JGEMVJG.KPM
After you have carried out the procedure in “Using Loopbacks to Check the Test Equipment
and the Terminal Connection”, you can then use a radio-facing loopback to monitor the
performance of a link. Proceed as follows:
Step 1: Select the remote terminal in the DXR NET Explorer Pane.
Step 2: Select the Radio Facing loopback function from the Tributary Loopback section,
click the Apply button, then the OK button in the displayed Warning box.
Step 3: Check the bit-stream output from the local terminal against the input stream from
your test equipment.
Step 4: When you have finished comparing the bit-streams, select the No Tributary
Loopback radio button, then click the Apply button.
If the errors are within the desired range, the link is functioning properly, and you need take
no further action. If the errors are outside the set range, there is a problem with the link, and
you should use loopbacks to check the terminals at either end of the link.
7UKPI.QQRDCEMU6Q%JGEMVJG.KPM6GTOKPCNU
If you have identified a problem with a link, you should try and localise the problem by
carrying out Digital, IF and RF loopbacks on first the local, then the remote terminal. Connect
your test equipment to the terminal, then proceed as follows:
Note 1: When you have located a fault using a loopback, you should disable any loopbacks
present, then quit the procedure. You should not proceed with any following steps.
Note 2: If you are checking a DXR 100 terminal, you should select the FEC Disable
function after Step 1 of the procedure. Remember to deselect the function before
quitting the procedure. Refer to “Using FEC Disable While Checking DXR 100
Terminals” for details.
Step 2: Select the Digital loopback function from the RF/Modem section, than click the
Apply button, then the OK button in the displayed Warning box.
Step 3: Compare the bit-stream output from the terminal against the input stream from your
test equipment.
Step 4: When you are finished comparing the bit-streams, deselect the Digital loopback
function by clicking again on the selected check box.
Step 5: If the errors are outside the desired range, the problem is in the circuitry between the
G.703 interface and the Modulation and Demodulation circuitry. Quit this
procedure, and carry out any remedial action set out for this type of fault in your
servicing policy. If the errors are within the desired range, the problem is not in this
circuitry, and you should proceed to Step 6.
Step 6: Select the IF loopback function from the RF/Modem section, than click the Apply
button, then the OK button in the displayed Warning box.
Step 7: Compare the bit-stream output from the terminal against the input stream from your
test equipment.
Step 8: When you are finished comparing the bit-streams, deselect the IF loopback function
by clicking again on the selected check box.
Step 9: If the errors are outside the set range, there is a problem in the circuitry between the
Modulation and Demodulation circuitry and the Splitter/Combiner. Quit this
procedure, and carry out any remedial action set out for this type of fault in your
servicing policy. If the errors are within the desired range, the problem is not in this
circuitry, and you should proceed to Step 10.
Step 10: Set up a RF loopback by going to the Modem/RF Link Setup page in the
Configuration Workspace, and setting the transmit and receive frequencies to the
same frequency.
Step 11: Compare the bit-stream output from the terminal against the input stream from your
test equipment.
Step 12: When you have finished comparing the bit-streams, deselect the RF loopback
function by restoring the transmit and receive frequencies to their original settings.
152 DMC STRATEX NETWORKS
APRIL 2001
IOM-NMS-2/2.5
Using DXR NET NMT
Step 13: If the errors are outside the set range, there is a problem in the ODU. Quit this
procedure, and carry out any remedial action set out for this type of fault in your
servicing policy. If the errors are within the desired range, there are no faults in this
terminal.
Step 14: If you have not already investigated the terminal at the other end of the link,
disconnect the test equipment from the local terminal, go to the remote site, connect
the test equipment to the terminal at that site, then go through Steps 1 to 13 for this
terminal.
If you have gone through all the above steps at both terminals without being able to localise
the problem, this indicates one of the following:
• There is an antenna problem (eg, misalignment, matching).
7UKPI('%&KUCDNGYJKNG%JGEMKPI&:4 6GTOKPCNU
The DXR 100 uses Forward Error Correction (FEC) to correct any errored bytes received
over the radio link. Although this adds to the performance of the link during normal operation,
it can cause a problem when you are trying to identify faults using loopbacks. Since errors can
be corrected before reaching the output, you may therefore not obtain a true picture of the
terminal error-rate when comparing the input and output streams. This will make it more
difficult to track errors to a particular piece of circuitry in the terminal.
To combat this, DXR NET has a FEC Disable function for DXR 100 terminals. You can select
this from RF/Modem section in the Controls page. You click on the FEC Disable check box to
select the function, then click the box again when you wish to deselect it.
6GUVKPI2TQVGEVKQP5YKVEJKPI
Note: You can only enable protection switching in a protected terminal.
Procedure
Step 1: Select the Commissioning or Maintenance Workspace.
Step 4: Select the Manual switching option you require from the Protection Switching
section by clicking on the associated radio button.
Step 5: Select the transmitter or receiver you wish DXR 700 to switch to.
Step 6: Click the Apply button in the displayed dialog box, then the OK button in the
Warning box.
Step 7: 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 terminal using the following procedure.
Except for the RSSI Graph (DXR 700) or AGC Graph (DXR 100) page operations, 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.
Note: For a DXR 700, if the Single Carrier option is selected in the Advanced option in
the Tools menu, DXR NET monitors the baseband signal from each available
DXR 700 terminal to produce the diagrams. If the Multi-Carrier option is selected,
DXR NET monitors the individual carriers of the local DXR 700 terminal to produce
the diagrams.
Procedure
Step 1: Select the Maintenance Workspace.
Step 4: Select the terminals or carriers you wish to monitor by clicking the relevant button
in the Select Terminal section.
Step 5: 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.
Step 6: If you wish to clear all the diagrams, click on the Reset All button in the Select
Terminal section. If you wish to clear a particular diagram, click on the Reset button
in the diagram.
Step 7: 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+)TCRJHQTC&:46GTOKPCN
You can view the RSSI graph using the following procedure.
Except for the Constellation page operations, you cannot select other operations while RSSI
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.
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
graphs. 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
graphs.
Procedure
Step 1: Select the Maintenance Workspace.
Step 4: Select the terminals or carriers you wish to monitor by clicking on the relevant
button.
Step 5: 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 RSSI Graph for
the terminal or carrier.
Step 6: If you wish to clear all the graphs, click on the Reset All button in the Select
Terminal section. If you wish to clear a particular graph, click on the Reset button in
the graph.
Step 7: 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 (0 dBm and –100 dBm respectively).
Step 8: 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.
8KGYKPI#)%)TCRJHQTC&:46GTOKPCN
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
monitoring is in progress.
STOPPING MONITORING. You must remember that just because an AGC graph is not
shown for a terminal does NOT mean the terminal is not being monitored.
Procedure
Step 1: Select the Maintenance Workspace.
Step 4: Select the terminals you wish to monitor by clicking on the relevant button.
Step 5: You can start monitoring for all terminals by clicking the Monitor All button in the
Select Terminal section, or you can start monitoring for an individual terminal by
clicking the Monitor button in the particular AGC Graph for the terminal.
Step 6: If you wish to clear all the graphs, click on the Reset All button in the Select
Terminal section.
Step 7: 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 (+5V and 0V), and clear all the data.
Step 8: 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.
8KGYKPI'SWCNK\GT)TCRJHQTC&:46GTOKPCN
You can view the Equalizer graph for a DXR 100 terminal using the following procedure.
STOPPING MONITORING. You must remember that just because an equalizer graph is
not shown for a terminal does NOT mean the terminal is not being monitored.
Procedure
Step 1: Select the Maintenance Workspace.
Step 4: Select the terminals you wish to monitor by clicking on the relevant button.
Step 5: You can start monitoring for all terminals by clicking the Monitor All button in the
Select Terminal section, or you can start monitoring for an individual terminal by
clicking the Monitor button in the particular Equalizer Graph for the terminal.
Step 6: If you wish to clear all the graphs click on the Reset All button in the Select
Terminal section.
Step 7: After you have finished monitoring the Equalizer graphs, stop monitoring by
clicking on any indented monitoring buttons. Ensure that all the monitoring buttons
are raised before leaving the page.
.QCFKPI5QHVYCTGVQ0GVYQTM'NGOGPVU
LOADING SOFTWARE. Software can only be loaded to terminals via a NMS element
(NMS board or SMA). If you do not have an NMS element, you will require DXRloader.
Please contact DMC for information on using DXRloader.
You can use DXR NET to load both terminals and NMS elements with updated software. The
procedure has the following three steps:
• Installing the system software (ie, the available versions of terminal and NMS unit
software) on your PC.
• Removing any old software files from the NMS element you are using to load the
software.
+PUVCNNKPI5[UVGO5QHVYCTGQP;QWT2%
Before you can load software to a network element, you must have first install the System
Software containing the network element software into the DXR NET folder on your PC.
Step 1: Insert the System Software disk (CD or floppy) into your PC.
Step 4: If required, change the desired location specified for the System Software files.
&GNGVKPI1NF5QHVYCTG(KNGUHTQOC0/57PKV
After you have loaded new software to any network elements, the BIN files remain stored in
the NMS element. Before you load any new software, you should delete these files. You may
delete all files that are marked as read/write. DXR NET will not allow you to delete files
required by the NMS element.
The procedure is as follows:
Note: You must be connected to the network via a NMS unit (a SMA or a NMS board).
Step 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 6: Select and delete the BIN files in the File System window.
.QCFKPI5QHVYCTGVQC0GVYQTM'NGOGPV
Note 1: You must be connected to the network via a NMS unit (a SMA or a NMS board). If
you do not have an NMS unit, contact DMC on using other software loading tools.
Note 2: We recommend that software is loaded to remote elements first (see Note 3).
Note 3: Following the SW load into the NMS unit, the link will drop while the terminal is
loaded. This may happen any time in the 5 mins after the load completed,
depending on the terminal type. Do not attempt to perform software loads over the
link during this time.
Note 4: You can abort a software load at any time during the loading process. If DXR NET is
unable to communicate with certain element components, it will display a dialog
box so that you can select the available components for software loading. However,
if DXR NET detects that the element is not compatible with the software you are
trying to load, it will abort the loading process.
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 7: Click the ellipsis (“…”) button in Software Version Table window to get the folder
containing the System Software.
Step 8: 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 9: Select Load Software from the drop-down Configuration menu, then Start.
Step 10: When the Complete message appears, click the OK button.
Note: If you have any problems with this basic procedure contact customer support as
shown in the dialog box below. You can open this dialog box by choosing the
Customer Support option in the Help menu of DXR NET NMT.
5QHVYCTG%QORCVKDKNKV[2TQDNGOU
When you connect to a NMS unit with a network blueprint loaded, DXR NET checks that the
version of software it detects in the unit matches the version set in the blueprint. This is
known as SSC compatibility checking. If the versions do not match, a warning message will
appear in the Status Bar of the DXR NET GUI, and you will not be able to read or write to the
unit.
To overcome this, amend the blueprint to reflect the version of software in the NMS unit.
To amend the blueprint, proceed as follows:
Step 1: Connect to the NMS unit without having the blueprint loaded. This will
autodiscover the link.
Step 3: Note the version of software listed for the NMS unit in the Version field of the
Software Table.
Step 4: Disconnect from the NMS unit, and load the blueprint.
Step 7: For the NMS unit you are interested in, double click on the Version field in
Software Version Table window, select the version of software actually present in
the unit, then click OK.
The blueprint should now reflect the software version in the actual unit. To confirm this, try
to connect to the unit again with the blueprint loaded.
#NCTO$QCTFCPF1RVKQP$QCTF%QORCVKDKNKV[2TQDNGOU
When you connect to an SMA, DXR NET checks that the version of alarm board and option
boards it detects in the unit matches the version set in the blueprint. If the versions do not
match, a warning message will appear in the Status Bar of the DXR NET GUI, and you will
not be able to read or write to the unit.
To overcome this, amend the blueprint to reflect the version of board in the unit.
To amend the blueprint, proceed as follows:
Step 1: Connect to the NMS unit without having the blueprint loaded.
Step 5: Disconnect from the NMS unit, and load the blueprint.
Step 8: For the NMS unit you are interested in, change the alarm board type, or the option
board type to that which is actually present in the unit, then click OK.
The blueprint should now reflect the option board type in the actual unit. To confirm this, try
to connect to the unit again with the blueprint loaded.
4WPPKPI5ETKRV(KNGU
DXR NET allows you to load and run script files to carry out test procedures.
SCRIPT FILES. Script files should only be used under the direction of DMC.
Step 4: Select Load Script File from the drop-down Maintenance menu.
Step 5: Select the script you want to run in the Execute Script File box, then Start.
2TQFWEKPI4GRQTVU
You can use DXR NET Report facility to produce reports for network elements. The reports
are of two main kinds:
• Commissioning Reports – these contain details of network element status after the
element has been brought into service.
• Inventory Reports – these contain details of network element status during normal
operation.
The reports can be viewed on your PC, saved for later reference, or printed out to provide
hard copy. They are produced from stored templates, which can themselves be customized to
suit your requirements. The templates are stored in the Templates folder, and any reports
produced can be stored, for later reference and printing, in the Reports folder.
Note: The default location for these folders is off the DMC folder, but you can select other
locations for them. You would normally do this when you install DXR NET on your
PC.
2TQFWEKPI%QOOKUUKQPKPI4GRQTVU
You can produce Commissioning reports for the following network elements:
• DXR 100 terminals (protected and unprotected).
Procedure
To produce a Commissioning report for a terminal, proceed as follows:
Note: A report can only be successfully produced if there is a valid template available for
the terminal.
Step 2: If required, select either the Commissioning Workspace, and go to the Terminal
Details page.
Step 3: Click the Commissioning Report button in the Terminal Details page.
Step 4: If you decide not to continue with producing the report, click the Abort button in the
displayed dialog box.
Step 5: If the report has been successfully produced, the Report Dialog window is
displayed. You can then select the template used by the report from the Template
Selection combo box. This contains all the available templates for the element.
Step 6: After displaying the report, you can add any required additional information to the
Comments section. You can then save the report to the Reports folder, for storage or
printing, by clicking the Save button in the window.
Step 7: If the report has not been successfully produced, or you are finished using it, click
the Close button in the Report Dialog window to return to the main DXR NET
window.
2TQFWEKPI+PXGPVQT[4GRQTVU
You can produce Inventory reports for all DXR NETwork elements. The reports are produced
by clicking the Report button in the Details page for the element. These pages appear in both
the Commissioning and the Maintenance Workspaces.
Procedure
To produce an Inventory report for a network element, proceed as follows:
Note: A report can only be successfully produced if there is a valid template available for
the element.
Step 4: If you decide not to continue with producing the report, click the Abort button in the
displayed dialog box.
Step 5: If the report has been successfully produced, the Report Dialog window is
displayed. You can then select the template used by the report from the Template
Selection combo box. This contains all the available templates for the element.
Step 6: After displaying the report, you can add any required additional information to the
Comments section. You can then save the report to the Reports folder, for storage or
printing, by clicking the Save button in the window.
Step 7: If the report has not been successfully produced, or you are finished using it, click
the Close button in the Report Dialog window to return to the main DXR NET
window.
#RRGPFKZ#2TQDNGOU7UKPI&:40'6
)GPGTCN
Problems encountered using DXR NET might include:
• The network cannot be accessed.
2TQDNGOU#EEGUUKPIVJG0GVYQTM
Check you have the right type of interface for your connection by selecting the
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).
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 their likeliest
causes, are listed below.
Note: The warnings are not listed in full for reasons of space.
• 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 have not properly enabled your dial-up adaptor for NMS connections.
• You are using the wrong type of connection for the element to which you are connected.
• The IP address of the NMS element you are trying to connect to does not match the
address given in the blueprint.
Loss of link
This usually indicates problems with frequency settings or cable connections. Most common
causes are:
The transmitter (TX) and receiver (RX) frequencies are different at each end of the link.
The transmitter (TX) and receiver (RX) frequencies do not match the ODU duplexer settings
made at the factory. Check the correct factory settings by viewing the ODU details as
described on page 60 in this manual.
There is a faulty cable connection or you have loaded invalid software. Check for any alarms
in the radio. If none are present you may have lost contact with the ODU due to a cable
problem.
%QPVCEVKPI&/%5VTCVGZ0GVYQTMU
Selecting Help and then Customer Support will display the methods you can use to contact the
product support staff at DMC Stratex Networks.
#RRGPFKZ$#NCTOU
)GPGTCN
This appendix contains descriptions of the alarms that can be generated in DXR NET by the
following network elements:
• DXR 100
• DXR 200
• NMS board
• DXR 700
• SMA
8KGYKPI#NCTOU
)GPGTCN
DXR NET alarms are viewed in the Alarms page, which is divided into two panes. The left-
hand pane, Alarm Status and Related Information, lists all possible alarms in the 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 a 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 a unit,
and then to track the alarm to a particular component.
The alarm status indicated by the icons is given in the following table.
%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
• 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 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.
&:4#NCTOU
0247PKV#NCTO
When the NPR Unit Alarm is active, it indicates an alarm is present on an unprotected
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
*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.
167 DMC STRATEX NETWORKS
APRIL 2001
IOM-NMS-2/2.5
Appendix B: Alarms
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.
5QHVYCTG
This indicates that one or more software alarms are present on the DXR 100. The possible
alarms are shown in the following table.
#NCTO 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
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.
/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
possible alarms are shown in the following table.
#NCTO0COG 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
5GXGTKV[
AIS output Warning Communications AIS is enabled on all outgoing
enabled tributaries.
Trib radio Warning Communications The radio facing loopback is
facing loopback enabled for one or more tributaries.
active
Trib line facing Warning Communications The line facing loopback is enabled
loopback active for one or more tributaries.
Modulation
This indicates that one or more modulation alarms are present on the DXR 100. The possible
alarms are shown in the following table.
#NCTO0COG 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
5GXGTKV[
IF loopback Warning Communications The IF loopback is enabled.
active
Digital loopback Warning Communications The digital loopback is enabled.
active
FEC disabled Warning Communications Forward Error Correction is
disabled
RF
This indicates that one or both RF related alarms are present on the DXR 100. The possible
alarms are shown in the following table.
#NCTO0COG 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
5GXGTKV[
RF loopback Warning Communications The RF loopback is enabled.
active
TX PA muted Warning Communications The TX PA is muted.
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.
#NCTO0COG 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
5GXGTKV[
LOS Critical Communications Loss of signal has occurred. The
probable cause is a disconnected
Tributary cable.
AIS Warning Communications AIS is being detected.
Uncommissioned Warning Communications Traffic is being received on this
traffic 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, De-modulator not locked, which is present when the modem de-
modulator is out of lock. This is classed as a critical alarm, of the communications type.
RX Path 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 Synthesizer 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.
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 alarms are present on
the DXR 100.
#NCTO0COG 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
5GXGTKV[
Forward Warning Equipment The TX forward power is outside the user
power configured upper and lower thresholds.
259#NCTOU
When the PSW Unit Alarm is active, it indicates an alarm is present on the Protection Switch
unit of a protected DXR 100. The alarms that can trigger the PSW Unit Alarm can be grouped
into the following types:
• Hardware
• Software
• Maintenance
• Traffic
• Tx Switch
*CTFYCTG
This indicates that a hardware alarm is present on the PSW. 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 PSW. 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 PSW are 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 PSW 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 PSW 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.
5QHVYCTG
This indicates that one or more software alarms are present on the PSW. The possible alarms
are shown in the following table.
#NCTO 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
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.
/CKPVGPCPEG
This indicates that one or more maintenance alarms are present on the PSW. They comprise:
• AIS output enabled
6TCHHKE
This indicates that one or more traffic related alarm conditions are present on the PSW. They
comprise:
• Trib port
• Radio Link
Trib Port
This indicates that a traffic-related alarm is present on one of the PSW Tributary ports (Trib
n). Each tributary port listing can have one or all of the three possible alarms in the following
table.
#NCTO0COG 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
5GXGTKV[
LOS Critical Communications Loss of signal has occurred. The
probable cause is a disconnected
Tributary cable.
AIS Warning Communications AIS is being detected.
Uncommissioned Warning Communications Traffic is being received on this
traffic uncommissioned Tributary port.
4CFKQNKPM
This indicates that a radio link related alarm is present on the PSW.
Link failure
This indicates one or more of the radio link failure alarms is present on the PSW. These
comprise:
• TX Path Failure
• RX Path Failure
The RX Path Failure alarm indicates that the RX path has failed, i.e. the radio link is down.. It
is classed as a critical alarm, of the communications type.
6:5YKVEJ
This indicates that one or more TX path protection switching alarms are present on the PSW.
These comprise:
• Switch oscillation limit
• Cannot switch
Cannot Switch
The Cannot Switch alarm indicates that the TX path cannot switch to the standby PSW. 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 PSW.
24##NCTO
When the PRA Alarm is active, it indicates an alarm is present on the Protected Radio
Assembly of a protected DXR 100. The alarms that can trigger the PRA Alarm can be
grouped into the following types:
• Hardware
• Software
• Maintenance
• Modem
• Radio link
*CTFYCTG
This indicates that a hardware alarm is present on the PRA. 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 PRA. 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 PRA are 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 PRA chassis is outside the normal operating upper
and lower thresholds. It is classed as a warning alarm, of the environmental type.
5QHVYCTG
This indicates that one or more software alarms are present on the PRA. The possible alarms
are shown in the following table.
#NCTO 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
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.
/CKPVGPCPEG
This indicates that one or more maintenance alarms are present on the PRA. They comprise:
• Modulation
• RF
Modulation
This indicates that one or more modulation alarms are present on the PRA. The possible
alarms are shown in the following table.
#NCTO0COG 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
5GXGTKV[
IF loopback Warning Communications The IF loopback is enabled.
active
Digital loopback Warning Communications The digital loopback is enabled.
active
FEC disabled Warning Communications Forward Error Correction is
disabled
RF
This indicates that one or both RF related alarms are present on the PRA. The possible alarms
are shown in the following table.
#NCTO0COG 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
5GXGTKV[
RF loopback Warning Communications The RF loopback is enabled.
active
TX PA muted Warning Communications The TX PA is muted.
/QFGO
This indicates that one or more modem related alarm conditions are present on the PRA. 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 PRA RX path. It
has a single alarm under it, De-modulator not locked, which is present when the modem de-
modulator is out of lock. This is classed as a critical alarm, of the communications type.
RX Path Warning
This indicates one of two possible modem related alarms, due to the detection of errors in the
received data, is present on the PRA. 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 PRA.
Link failure
This indicates one or more of the radio link failure alarms is present on the PRA. These
comprise:
• TX Path Failure
• RX Path Failure
The TX Path Failure alarm indicates that a TX path failure alarm is present on the PRA. It has
a single alarm under it. The TX Synthesizer is not locked. This is classed as a critical alarm,
of the equipment type. The two most probable causes of this alarm are:
• An invalid TX frequency has been configured.
Link Warning
This indicates one or more of the radio link warning alarms is present on the PRA. These
comprise:
• TX Path Warning
• RX Path Warning
The TX Path Warning alarm indicates that one or both of the following alarms are present on
the PRA.
#NCTO0COG 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
5GXGTKV[
Forward Warning Equipment The TX forward power is outside the user
power configured upper and lower thresholds.
The RX Path Warning alarm indicates that the AGC alarm is present on the PRA. This
indicates that the AGC is outside the user configured upper and lower thresholds. It is classed
as a Warning, of the Communications type.
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
alarms are shown in the following table.
#NCTO 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
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.
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. 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 a NPR, PRA or
PSW alarm could be 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
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 RMA. 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 that 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.
#NCTO 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
0COG 5GXGTKV[
+5V supply Warning Equipment The +5V supply is outside of the
normal operating upper and lower
thresholds.
+12V supply Warning Equipment The +12V supply is outside of the
normal operating upper and lower
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
This indicates that one or more software alarms are present on the DXR 700 RMA. The
possible alarms are shown in the following table.
#NCTO 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
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.
/CKPVGPCPEG
This indicates that one or more maintenance alarms are present on the DXR 700 RMA. The
possible alarms are shown in the following table.
#NCTO 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
0COG 5GXGTKV[
IF loopback active Warning Communications The IF loopback is enabled on the
RMA.
Digital loopback Warning Communications The digital loopback is enabled on
active the RMA.
Modulation Warning Communications The modulation is disabled on one or
disabled more of the installed modem
modules on the RMA.
/QFGO
This indicates that one or more modem related alarm conditions are present on the DXR 700
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.
#NCTO0COG 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
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 synchronize 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.
#NCTO0COG 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
5GXGTKV[
Demodulator Major Communications One or more of the RMA demodulators is
not locked out of lock.
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.
182 DMC STRATEX NETWORKS
APRIL 2001
IOM-NMS-2/2.5
Appendix B: Alarms
&:42/##NCTO&GUETKRVKQPU
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.
#NCTO 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
0COG 5GXGTKV[
+5V supply Warning Equipment The +5V supply is outside of the
normal operating upper and lower
thresholds.
+12V supply Warning Equipment The +12V supply is outside of the
normal operating upper and lower
thresholds.
5QHVYCTG
This indicates that one or more software alarms are present on the DXR 700. The possible
alarms are shown in the following table.
#NCTO 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
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.
/CKPVGPCPEG
This indicates that one or more maintenance alarms are present on the PMA. The possible
alarms are shown in the following table.
#NCTO0COG 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
5GXGTKV[
AIS output Warning Communications AIS is enabled on all outgoing
enabled tributaries.
Trib radio Warning Communications The radio facing loopback is
facing loopback enabled for one or more tributaries.
active
Trib line facing Warning Communications The line facing loopback is enabled
loopback active for one or more tributaries.
Manual TX path Warning Communications TX protection switching is locked
enabled on manual.
Manual RX path Warning Communications RX protection switching is locked
enabled on manual.
6TCHHKE
This indicates that one or more traffic related alarm conditions are present on the PMA. They
comprise:
184 DMC STRATEX NETWORKS
APRIL 2001
IOM-NMS-2/2.5
Appendix B: Alarms
• Trib port
• 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.
#NCTO0COG 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
5GXGTKV[
LOS Critical Communications Loss of signal has occurred. The
probable cause is a disconnected
Tributary cable.
AIS Warning Communications AIS is being detected.
Note: That there is no AIS for some
variants.
4CFKQNKPM
This indicates that a radio link related alarm is present on the PMA. These comprise:
• Link failure
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.
6:5YKVEJ
This indicates that one or more TX path protection switching alarms are present on the PMA.
These comprise:
• Cannot switch
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
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
• Maintenance
• 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
• Temperature
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.
#NCTO 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
0COG 5GXGTKV[
+5V supply Warning Equipment The +5V supply is outside of the
normal operating upper and lower
thresholds.
+10V supply Warning Equipment The +10V supply is outside of the
normal operating upper and lower
thresholds.
Temperature
This indicates that one or both of the temperature alarms is present on the ODU. The possible
alarms are shown in the following table.
#NCTO 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
0COG 5GXGTKV[
Internal Warning Environmental The ODU internal temperature is
Temperature outside of the normal operating upper
and lower thresholds.
PA Warning Environmental The ODU PA heat sink temperature is
Temperature outside of the normal operating upper
and lower thresholds.
5QHVYCTG
This indicates that one or more software alarms are present on the DXR 700. The possible
alarms are shown in the following table.
#NCTO 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
0COG 5GXGTKV[
Configuration Major Processing Corruption of the ODU configuration
corrupt error data has been detected.
Settings not valid Major Processing The ODU configuration does not
error match the hardware capability.
/CKPVGPCPEG
This indicates that one or more maintenance alarms are present on the ODU. The possible
alarms are shown in the following table.
#NCTO0COG 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
5GXGTKV[
RF loopback Warning Communications The RF loopback is enabled.
active
TX PA muted Warning Communications The TX PA is muted.
4CFKQ.KPM
This indicates that a radio link related alarm is present on the ODU. These comprise:
• Link failure
• Link warning
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 Synthesizer 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.
Link Warning
• This indicates one or more of the radio link warning alarms is present on the ODU. These
comprise:
• TX Path Warning
• RX Path Warning
The TX Path Warning alarm indicates that one or both of the following alarms is present on
the ODU.
#NCTO0COG 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
5GXGTKV[
Forward Warning Equipment The TX forward power is outside the user
power configured upper and lower thresholds.
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 ODU. This
indicates that the RSSI is outside the user configured upper and lower thresholds. It is classed
as a Warning, of the Communications type.
5/##NCTO&GUETKRVKQPU
Note: that in Phase 2 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.
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
• Terminal 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.
#NCTO0COG 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
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.
SDM Alarms
In addition, when the SMA uses one of the SDM Option Boards, the following three alarms
can be present:
Note: In the alarm hierarchy, the Option board not installed alarm appears under the
Component Failure alarm, and the Option slot 1 and Option slot 2 alarm appear
under the Option board not installed alarm.
#NCTO$QCTF/CTM+
The Mark I Alarm Board alarm indicates that one or more of the alarms displayed in the
following table is present. The Mark I board has 12 input/output alarms. The alarms can be
configured via DXR NET as either:
Inputs, activated by grounding the pin alarm
Outputs, when activated the alarm pin is grounded (maximum current capacity 120mA, max
voltage 100V).
Dip switches are set to IN or OUT on the alarm circuit board to cut tracks that choose ground
reference or isolated. These settings are made by the DMC engineer or in the factory when the
SMA is assembled. The software must be set to match this configuration.
#NCTO$QCTF/CTM++
The Mark II Alarm Board has 6 input alarms and 6 output alarms. Input alarms are activated
when the alarm pin is grounded. When activated, the output alarms will ground the alarm pin
(maximum carrying capacity 120mA, maximum voltage 100V).
A SMA output alarm, when raised, will connect the appropriate pin to ground, and normally
has high impedance. Therefore, any alarm monitoring equipment must recognise the
grounding of the SMA alarm output as an active alarm. Output ports can withstand a
maximum voltage of 100V, and can carry a maximum current of 120 mA.
Note: The SMA must reflect that a Mark II board is installed.
#NCTO 0COG 2GTEGKXGF #NCTO 6[RG 2TQDCDNG %CWUG &GUETKRVKQP
5GXGTKV[
Ground referenced Warning Equipment Alarm Board ground referenced input 1a is
input 1a active.
Ground referenced Warning Equipment Alarm Board ground referenced input 1b is
input 1b active.
5QHVYCTG
This indicates that one or more software alarms are present on the SMA. The possible alarms
are shown in the following table.
#NCTO 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
0COG 5GXGTKV[
Configuration corrupt Major Processing Corruption of the configuration data
error has been detected.
Settings not valid Major Processing The configuration does not match the
error hardware capability.
Date and time not set Minor Processing The software clock date and time has
error not been set.
SDM Alarms
In addition, when the SMA uses one of the SDM Option Boards, the following three software
alarms can be present:
Note: In the alarm hierarchy, the Option 1 parameter fail and Option 2 parameter fail
appear under the Option board configuration alarm.
/CKPVGPCPEG
This indicates that one or both of the maintenance alarms are present on the SMA. The
possible alarms are shown in the following table.
#NCTO 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
0COG 5GXGTKV[
AUX loopback Warning Communications An AUX port loopback is enabled
active for one or more AUX ports on the
SMA.
Ethernet test mode Warning Communications Ethernet test mode is active on the
active 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 are 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 are present on the SMA. ‘n’ is the port
identifier, either IN or OUT.
The NMS n alarm indicates the LOS (Loss of Signal) alarm is present on NMS n of the SMA
(n = IN or OUT). The LOS alarm is classed as a Critical alarm, of the Communications type.
The most common cause is that the cable to the port has become disconnected.
V.24 Port
This indicates that one or more of the V.24 n alarms are 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 are present.
#NCTO 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
0COG 5GXGTKV[
Connection failure Major Communications NMS connection failure with the
device on this V.24 port has
occurred. The probable cause is a
disconnected V.24 port cable.
Unexpected unit Warning Communications NMS traffic is being received from
an unexpected unit on this V.24 port.
SDM Alarms
In addition, when the SMA uses one of the SDM Option Boards, the following four traffic
alarms can be present:
Note: In the alarm hierarchy, Option 1 and Option 2 appear under the Option port alarm,
and each of the Option 1 and Option 2 alarms has an Errors alarm under it.
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 that
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.
5GTKGU0GVYQTM#NCTOUHQT6GTOKPCNUQPVJG5/#
There are eight new SMA alarms for the DXR 200. These alarms reflect the highest alarm
condition on the indicated radio. This enables the SMA to map this condition to a SMA event.
#NCTO 2GTEGKXGF #NCTO6[RG 2TQDCDNG%CWUG&GUETKRVKQP
0COG 5GXGTKV[
Radio Alarms A monitored radio is reporting an
alarm condition.
Local radio n A local (near end) monitored radio is
(n=A,B,C,D) reporting an alarm condition.
Critical Critical A local (near end) monitored radio is
reporting a critical alarm condition.
Major Major A local (near end) monitored radio is
reporting a major alarm condition.
Minor Minor A local (near end) monitored radio is
reporting a minor alarm condition.
Warning Warning A local (near end) monitored radio is
reporting a warning alarm condition.
Remote radio n A remote (far end) monitored radio
(n=A,B,C,D) is reporting an alarm condition.
Critical Critical A remote (far end) monitored radio
is reporting a critical alarm
condition.
Major Major A remote (far end) monitored radio
is reporting a major alarm condition.
Minor Minor A remote (far end) monitored radio
is reporting a minor alarm condition.
Warning Warning A remote (far end) monitored radio
is reporting a warning alarm
condition.
&:4#NCTOU
An alarm hierarchy is generated based on the flat alarm structure supplied by the DXR 200
terminal. It is the responsibility of DXR NET to create and maintain this hierarchical structure.
DXR NET will only display the alarms that are appropriate for the terminal type and slot
configuration of the DXR 200.
Shaded entries indicate alarms that are specific to a given DXR 200 terminal type (i.e. SCP,
DCP Main, SCR, etc)
*CTFYCTG
This indicates that one or more hardware alarms are present on the DXR 200. The possible
alarms are shown in the table below.
5QHVYCTG
This indicates that one or more software alarms are present on the DXR 200. The possible
alarms are shown in the table below.
/CKPVGPCPEG
This indicates that one or more maintenance alarms are present on the DXR 200. The possible
alarms are shown in the table below.
6TCHHKE
This indicates that one or more traffic related conditions are present on the DXR 200. The
possible alarms are shown in the table below.
/QFGO
This indicates that one or more modem related alarm conditions are present on the DXR 200.
The possible alarms are shown in the table below.
4CFKQ.KPM
This indicates that a radio link related alarm is present on the DXR 200. The possible alarms
are shown in the table below.
#RRGPFKZ%%QPUVGNNCVKQP&KCITCOU
)GPGTCN
In a digital radio, the information contained in the baseband signal is carried by the signal’s
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.
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.
#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.
Radio Capacity Link Data Rate Bit Error Rate
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
2 x E3 79.836 80
1 x E3 40.769 41
16 x E1 40.762 41
8 x E1 19.747 20
4 x E1 9.792 10
2 x E1 5.01 5
1 x DS3 51.875 52
16 x DS1 30.731 31
8 x DS1 14.887 15
4 x DS1 7.382 7
2 x DS1 3.867 4
(TGSWGPE[4CPIGCPF5VGR5K\G
&:4
The following table shows the relationship between the frequency range and the frequency
step size, for a DXR 100 terminal.
Terminal Type Frequency Range Step Size
DXR 103 330-470 MHz 25 kHz
DXR 109 890-960 MHz 125 kHz
DXR 114 1350-1550 MHz 125 kHz
DXR 121 2000-2300 MHz 125 kHz
DXR 122 2100-2300 MHz 125 kHz
DXR 124 2300-2500 MHz 125 kHz
DXR 126 2500-2700 MHz 125 kHz
The following table shows the relationship between the frequency range and the frequency
step size, for a DXR 700 terminal.
Terminal Type Frequency Range Step Size
DXR 710 10.0-10.7 GHz 5 kHz
DXR 711 10.7-11.7 GHz 5 kHz
DXR 726 2.5-2.7 GHz 250 kHz
DXR 730 3.4-3.6 GHz 250 kHz
DXR 737 3.6-3.8 GHz 250 kHz
DXR 762 5.9-6.4 GHz 5 kHz
DXR 768 6.4-7.1 GHz 5 kHz
DXR 770 7.1-7.75 GHz 5 kHz
DXR 785 7.7-8.5 GHz 5 kHz
DXR 740 3.8-4.2 GHz 5 kHz
6Z1WVRWV2QYGT
&:4
The following table shows the relationship between the modulation, the capacity, and the
transmitter power output at the Tx port, for a DXR 100 terminal.
Modulation
Terminal Type
QPSK 16 QAM
1 x E1 2 x E1 4 x E1 1 x E1 2 x E1 4 x E1
DXR 103 37 dBm 37 dBm - 31 dBm 31 dBm 33 dBm
DXR 109 37 dBm 37 dBm 37 dBm - - 29 dBm
DXR 114 33/37 dBm 33/37 dBm 37 dBm 33 dBm 33 dBm 33 dBm
DXR 121 33 dBm 33 dBm 33 dBm - - 33 dBm
DXR 124 33 dBm - 33 dBm - - -
DXR 126 - - 33 dBm - - -
&:4
The following table shows the relationship between the modulation, the capacity, and the
transmitter power output at the Tx port, for a DXR 700 terminal.
Modulation
Terminal Type
16 QAM 64 QAM 32 QAM
2 x E1 4 x E1 8 x E1 16 x E1 E3 8 x E1 DS3 STM-0
DXR 710 +28dBm +28dBm +28dBm +28dBm +28dBm +26dBm +26dBm +26dBm
DXR 711 +28dBm +28dBm +28dBm +28dBm +28dBm +26dBm +26dBm +26dBm
DXR 724 +28dBm +28dBm +28dBm +28dBm +28dBm - - 26 dBm
DXR 726 +28dBm +28dBm +28dBm +28dBm +28dBm - - +26dBm
DXR 730 +28dBm +28dBm +28dBm +28dBm +28dBm - - +26dBm
DXR 737 +28dBm +28dBm +28dBm +28dBm +28dBm - - +26dBm
DXR 762 +28dBm +28dBm +28dBm +28dBm +28dBm +26dBm +26dBm +26dBm
DXR 768 +28dBm +28dBm +28dBm +28dBm +28dBm +26dBm +26dBm +26dBm
DXR 770 +28dBm +28dBm +28dBm +28dBm +28dBm - - +26dBm
DXR 785 +28dBm +28dBm +28dBm +28dBm +28dBm +26dBm +26dBm +26dBm
DXR 740 +28dBm +28dBm +28dBm +28dBm +28dBm +26dBm +26dBm +26dBm
#RRGPFKZ'7UKPI&:40'6YKVJ5&/
$QCTFU
)GPGTCN
This section covers how to use DXR NET to set up a data circuit between SMAs using the
optional Serial Data Module (SDM) boards. Such a circuit would 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.
• 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 allows serial data communications over the AUX bearers channel of the
SMA. There are three types of board:
• Low Speed Daughter Board
SERIAL SERIAL
DATA SMA SMA DATA
SDM SDM
AUX AUX
%TQUUEQPPGEVU
Unless the two SMAs at each end of the circuit are in direct communication with one another,
ie. at the opposite ends of the same radio link (as in Figure 55), you will have to relay the data
circuit via another SMA. You do this by setting up an internal cross-connect in each
connecting SMA.
CROSS-CONNECT SMA
%NQEMKPI*KGTCTEJ[
To synchronize communication between the SDM boards, each SMA on the data circuit
should be using the same timing signal. Ensure this by selecting one of the SMAs as the
primary clock source for the others (you can also select another SMA as the secondary clock
as required). This is known as setting up a clocking hierarchy. The primary clock source of
the selected SMA is set to free-running (clock generated internally), the other SMAs have
their primary clock source set to the port (AUX port or NMS In or NMS Out port) by which
they are connected to the selected SMA.
%QOOKUUKQPKPI9QTMURCEG
5/#&GVCKNU
The SMA Details tabbed page in the Commissioning Workspace now has the following
additional sections.
• Option Slot 1
• Option Slot 2
• Board ID text
• Part Number
• Serial Number
• Software Version
The Board ID text will contain one of the following:
• High speed daughter board 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.
Step 2: Select the SDM boards that give the required performance.
Step 3: Check that the SMA that will contain the boards has both channels and free 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 8: Test the data circuit to see that it can carry the required data.
%QPHKIWTKPIC.QY5RGGF&CWIJVGT$QCTF KPCP1RVKQP2CIG
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 1: Select the Configuration Workspace.
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.
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 SMAs, 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.
Step 12: When you have made your changes, select the Commit button in the Toolbar.
The changes you have made will be reflected in the network blueprint. If you are not going to
make any further changes to the SMA configuration, select the Write Configuration button in
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.
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 1: Select the Configuration Workspace.
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 “High 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: 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 channel field, or
the settings on any other board.
Step 8: Select one of the SMAs, 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 9: Select the SMA at the opposite end of the data circuit from the SMA in Step 8, 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.
Step 10: When you have made your changes, select the Commit button in the Toolbar.
The changes you have made will be reflected in the network blueprint. If you require no
further changes to the SMA configuration, select the Write Configuration button in the
Toolbar. The configuration of the SDM daughter board in the SMA will now change to reflect
the values set in the blueprint.
%QPHKIWTKPIC%QFKTGEVKQPCN&CWIJVGT$QCTFKPCP1RVKQP2CIG
You can use the following procedure to configure a Co-directional 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 1: Select the Configuration Workspace.
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 “Co-directional
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 Start at channel field, and select the channel on the AUX
port from where you want the board data stream to start using the drop-down menu.
Step 7: Select one of the SMAs, 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 8: Select the SMA at the opposite end of the data circuit from the SMA in Step 7, 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.
Step 9: 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 SMA configuration, select the Write Configuration button in
the Toolbar. The configuration of the SDM daughter board in the SMA will now change to
reflect the values set in the blueprint.
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 1: Select the Configuration Workspace.
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.
Step 6: 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, select the Write Configuration button in the Toolbar. The
configuration of the SMA will now change to reflect the values set in the blueprint.
5GVVKPI7RVJG%NQEMKPI*KGTCTEJ[
You can use the following procedure to set up the clocking hierarchy required to synchronize
data streams between SDM boards.
Note: We advise that you have read and understood “Setting up a Clock Source in a SMA”
in Section 4.
Procedure
Step 1: Select the SMA you wish to use as the primary clock source for the data circuit.
Step 2: Set the primary clock source of this SMA to free-running (generated internally).
Step 3: Set the primary clock source of all the other SMAs in the circuit to the port they are
connected to by the clock source SMA.
#RRGPFKZ(7UKPI&:40'6YKVJC.#0
)GPGTCN
You can connect the PC running DXR NET to a DXR NETwork in three ways:
Terminal connection, directly to a terminal (DXR 700, or DXR 100 without NMS board).
NMS connection, either directly, or via a modem, to a NMS unit (SMA or DXR 100 with
NMS board).
Ethernet connection, with the connection made over a LAN.
Terminal and NMS connections have already been previously covered (see Section 4 for
details). This document covers the ways in which you can use the Ethernet connection to
access a DXR NETwork over a LAN.
Note: This document assumes that you are familiar with the concepts of IP addressing and
DXR blueprint design, as covered in Section 4.
'VJGTPGV%QPPGEVKQP4GSWKTGOGPVU
Before you can use the DXR NET Ethernet connection, you must fulfil the following
requirements:
Your PC must have an Ethernet port set up.
You must have selected the Ethernet connection option for DXR NET (see Selecting the
DXR NET Ethernet Interface On Your PC).
If you are connecting to the DXR NETwork via a SMA, you must have set the IP address of
the SMA.
In addition, if you are using a router to connect your PC to the network, you must have a
suitable router (eg, Cisco 2509) and any required hub cross-connect cabling.
Note: Before you can set up the SMA for Ethernet, you should have carried out all other
configuration operations using the Setup port.
'VJGTPGV%QPPGEVKQP2TQVQEQN
When using the Ethernet connection to either a Router or a SMA, DXR NET communicates
with the NMS Unit or the Router Software using SNMP and TFTP.
LAN
SMA SMA
4GCUQPUHQT%QPPGEVKPIVQC&:40'6YQTMXKC'VJGTPGV
There are two main advantages in your connecting to a DXR NETwork via the Ethernet
connection:
• You can connect to the network via a corporate LAN.
• You can connect to the network over the Ethernet, i.e. via an ISP.
With both methods, you can connect your PC to the network without having to attach it to any
particular network element, or without having to be at any particular location (as long as you
can access the LAN). Ethernet connection therefore greatly increases your ability to access a
DXR NETwork, although it does require slightly more planning and configuration to obtain
the full benefits.
.#0%QPPGEVKQPUVQ&:40'6YQTMU
There are three possible ways in which a DXR NETwork can be connected to a LAN:
Via a router directly connected to a piece of DXR equipment.
Via a SMA connected directly to a LAN.
Via a router connected to a LAN containing a SMA.
Note: The LAN may be a hub, or you may use a "cross-over" cable - see DXR 700
installation for details.
&KTGEV4QWVGT%QPPGEVKQPVQ&:4'SWKROGPV
PC
Ethernet protocol
LAN
PPP DXR
Router Equipment
V.24 Port V.24 Port
In this case, the router is directly connected to a piece of DXR equipment, via the router V.24
port. The router communicates with the equipment using Point-to-Point Protocol (PPP), as for
a Terminal or NMS connection between a PC running DXR NET and the equipment. You
would connect your PC to the router over the LAN, using Ethernet protocol to communicate
with the router.
&KTGEV5/#%QPPGEVKQPVQ.#0
PC
Ethernet port
LAN Ethernet protocol LAN port
SMA
%QPPGEVKQPVQ5/#XKCC4QWVGT
PC
Ethernet protocol
LAN
Router
Ethernet protocol
LAN LAN Port
SMA
2NCPPKPIC.#0%QPPGEVKQPVQC&:40'6YQTM
Connecting a DXR NETwork to a LAN (corporate or ISP) requires three things to be designed:
• the LAN
.#0&:40'6YQTM+PVGTHCEG
Note: It is assumed that you are familiar with the concepts of IP addressing, as covered in
Section 4.
Both the DXR NETwork and the LAN will use IP addressing to decide the routes network
messages take to reach their destination. This means that the LAN will need an IP address for
the DXR NETwork, and any NMS units in the DXR NETwork will need an IP address for the
LAN.
LAN Requirements
The IP address that the LAN uses to talk to the DXR NETwork needs to fulfil two criteria:
• It must be a valid address.
5GVVKPI7RC&KTGEV4QWVGT%QPPGEVKQPVQ&:4'SWKROGPV
Consult the documentation that came with your router.
5GVVKPIWRC&KTGEV5/#%QPPGEVKQPVQC.#0
To set up a direct connection between a LAN and a SMA, you need to do the following:
• Set up the SMA LAN port.
• Change the network blueprint so that the DXR NETwork can communicate with the LAN.
5GVVKPIWRVJG5/#.#02QTV
To set up the LAN (Ethernet) port on a SMA, proceed as follows:
Note: We advise you carry out the following while directly connected to the SMA.
Procedure
Step 1: Obtain the network IP address for the SMA from your IT department.
Step 7: Double-click the SMA Ethernet interface in the IP Address Table. The red tick that
was next to the V.24 will now appear next to Ethernet.
Step 9: If you wish to save the changes to the active blueprint, select the Commit button in
the Toolbar.
The LAN port on the SMA is now set up to use Ethernet. Quit DXR NET if it is no longer
required.
0GVYQTM$NWGRTKPV%JCPIGU
The network blueprint changes consist of changing the routing tables of the SMA and all the
other NMS units on the network so that they can use the SMA Ethernet port IP address to
communicate with the LAN. The procedures for changing the routing tables are as already
covered, with one important exception. That is, if an octet of the SMA Network IP address is
zero, the corresponding octet in the Mask IP Address must also be set to zero.
Example
A small DXR NETwork containing two SMAs is connected to a LAN via one of the SMA. The
SMA that is connected to the LAN is known as "SMA Bottom", and the other SMA is known
as "SMA Top". SMA Top communicates with SMA Bottom via the AUX A ports.
Note: We assume here that the network is already up and functioning, using DXR NET and
the V.24 interface.
The IP address of the SMA Bottom Ethernet port will be 192.192.0.41, mask 255.255.255.0.
This is given by the LAN administrator and will be entered into the Advanced IP Address
table for the SMA Bottom Ethernet interface, with the specified mask.
In the SMA Bottom Routing Table, the Destination IP Address for the Ethernet interface will
be 192.192.0.0., and the Mask IP Address will therefore be 255.255.255.0. In the SMA Top
Routing Table, an entry will be added for the AUX A port with a Destination IP Address of
192.192.0.0. and a Mask IP Address of 255.255.0.0.
5GVVKPIWRVJG4QWVGVQVJG5/#
You need to manually set the route your PC uses to communicate with the SMA network, as
the SMA IP addresses are not visible on the LAN. As a result, the PC will be unable to
address a message to the SMA until you set the route. You set the route using the "route add"
facility in DOS.
To add the route, you need the subnet address of the SMA network, and the IP address of the
Ethernet port on the SMA. You then use the DOS route add command.
You would normally obtain the network IP address in consultation with your LAN System
Administrator (your IT department, or whoever else is responsible for the LAN). Deriving the
other two factors is slightly more complicated, as they depend on the degree of access you
want to have to the DXR NETwork. You must also take into account any possible addressing
conflicts between the IP addresses used in the network, and those used on the LAN. Normally,
we advise you set the Sub-net address to 10.0.0.0 and the mask to 255.0.0.0, as this will
enable you to access the entire DXR NETwork.
To manually set the route your PC uses to communicate with the SMA, proceed as follows:
Step 1: Restart your PC and log-on to the LAN.
Step 2: Go to MS-DOS window, and at the DOS prompt, enter the following:
This commands tells the PCs IP code to send messages for the 1.0 Network to the address
192.192.0.41, which will know how to route the traffic.
You can check the routes on the PC using the command "route print".
Step 4: If required, select the Ethernet connection for DXR NET (see Selecting the DXR NET
Ethernet Interface), then open the blueprint for the DXR NETwork and select the
Connect button.
You should now be able to access the network over the LAN.
5GVVKPIWRC5/#%QPPGEVKQPVQC.#0XKCC4QWVGT
Consult the documentation supplied with your router.
5GNGEVKPIVJG&:40'6'VJGTPGV+PVGTHCEG
To select the Ethernet connection option for DXR NET network interface, proceed as follows:
SELECTING THE INTERFACE. You must select the right type of interface for your
connection, or DXR NET will not be able to access the network.
Procedure
Step 1: Run DXR NET from the desktop.
Step 2: Select the Communication Setup option from the Tools menu.
Step 3: Select the Ethernet interface from the Scroll Box in the Communications Setup
screen.
Step 4: If you wish to make the Ethernet interface the default setting, click the Save Settings
button.
Step 5: Click the OK button to change the interface to the selected interface.
#RRGPFKZ)7UKPI&:40'6YKVJ&:4
)GPGTCN
This section covers how to use DXR NET to manage networks that incorporate DXR 200
radios.
DXR NET allows for the monitoring of DXR 200 alarms, and viewing of system details such
as hardware and software types and versions .
DXR 200 is incorporated into the DXR NET Network Management environment by treating
the SMA as a "proxy" for a DXR 200 network. The purpose of this functionality is to create a
bridge to the DXR 200 so that DXR NET and ProVision can monitor the DXR 200 radio.
Note: This appendix assumes that you are familiar with the concept of DXR blueprint
design, as covered in Section 4 of this manual.
%QPPGEVKQP2TQVQEQNHQT&:4
The SMA creates an SNMP bridge between the manager and the DXR 200. The SMA
connects a V.24 port to the DTI or set-up connector on the DXR 200. The manager uses
TCP/IP to communicate to the SMA, and the SMA communicates to the DXR 200 using the
DXR 200 proprietary protocol. In this manual, the manager is DXR NET, although ProVision
may also use the connection.
When the PC running DXR NET is connected to a DXR 200 radio via the SMA, DXR NET
identifies the DXR 200 terminal unit using the Terminal Number assigned to the DXR 200.
The DXR NET software uses TCP/IP addressing to communicate with the SMA.
The DXR 200 software has not been modified to recognise the SMA, and communicates with
it as if it is DXRsetup or DXRview. The SMA does not carry any DXR 200 signalling. As a
result, if a SMA is used between two DXR 200 networks, the networks are not aware of each
other due to the SMA.
ProVision
V.24 connector
DXR 200
&:40GVYQTM#FFTGUUKPI4GSWKTGOGPVU
DXR NET communicates with the DXR 200 terminals via the SMA, identifying each DXR
200 connected to the network with a combination of SMA IP address, SMA port the DXR 200
is attached via, and the DXR 200 terminal number.
The address is considered as:
SMA IP address, PORT(A-D), TERMINA #
In a network with multiple networks of DXR 200s, each group of DXR 200s connected via a
SMA port is considered to be a network. DXR 200s on other ports, or on other SMAs, are
separate networks, and can re-use the DXR 200 Terminal numbers.
&GHKPG6GTOKPCN0WODGTU
DXR NET requires a terminal number field to be completed when a DXR 200 is added to the
blueprint. This information is pre-set in the DXR 200 using DXRsetup. If a terminal number
is not correctly written to the blueprint (i.e. if it does not match the number defined by
DXRsetup), DXR NET will be unable to communicate with the DXR 200.
6GTOKPCN0WODGT7UCIG
The Terminal Number relates to the Control Module of the SMA. The SMA constantly polls
the DXR 200 for its alarm structure and lists all standard DXR 200 alarms. All terminals in
each DXR 200 network are accessed via the DXR 200 that is attached to the SMA.
&:40GVYQTM$NWGRTKPV
DXR NET writes the DXR 200 data from the blueprint to the configuration data that is sent to
the SMA.
DXR 200 terminals can be deployed at sites in the network blueprint, and then selected as
being managed by a SMA. When a SMA becomes a manager, each DXR 200 is assigned to a
particular SMA port. This port is connected to the DXR 200, and all management information
will use this port and DXR 200 connection.
%QORNGZ/QFGNU
If a DXR 200 is a complex model, such as Single or Dual chassis protected, or a single chassis
repeater, it will contain multiple control modules. Each control module must be deployed on
the blueprint as a DXR 200, with it own terminal number. DXR NET does not work with the
physical representation, but communicates with each control module via its own terminal
number.
.KOKVU
A maximum of 500 DXR 200 terminals can be added to the blueprint. Each SMA can have up
to 4 directly attached DXR 200 terminals. Each of these can be connected to a network of up
to 255 terminals, to the maximum of 500 per SMA and 500 per blueprint.
The terminal number must be unique within a network, but, since each port on each SMA is a
separate network, terminal numbers can be re-used.
6JGTGCTGVJTGGRQUUKDNGYC[UVQFGRNQ[C&:4PGVYQTM
Site
SMA
DXR 200
Terminal 2
DXR 200
Terminal 3
Site
DXR 200
Terminal 1
Figure 67: Deployment Option 2 - Indirect Connection.
Deploy the DXR 200 to a site and then set up indirect connection to a SMA at a later point.
Site
DXR 200
Terminal 1
SMA
%QPHKIWTCVKQP9QTMURCEGHQT&:46GTOKPCN
You use the Configuration Workspace to write the pre-defined terminal numbers to the
blueprint, to create terminal names, to configure the SMA to communicate with the DXR 200
and to set up remote radio connections.
You cannot configure the DXR 200 terminal using DXR NET. Configuration must be
performed by a PC running DXRsetup that is directly connected to the DXR 200 network.
Configuration Workspace can work with saved data, so you can build a network blueprint
offline. i.e. you can deploy and configure the DXR 200 data when your PC is not actually
connected to an element.
&GRNQ[KPIVJG&:40GVYQTM
Procedure
Step 1: First create all the sites within the blueprint.
Note: For complex DXR 200 terminals, deploy one instance of a DXR 200 for each
control module (these of course should be at the same site).
Step 3: Name each DXR 200 terminal, and assign the correct terminal number to each
terminal (see "Deploy the DXR 200 procedure" in this appendix).
Step 4: Where creating radio links, select the remote site and remote terminal on the RF
Link Setup page. For non-radio DXR 200, this is not necessary.
Step 5: Deploy the SMAs in the blueprint at the correct sites, and implement the IP table,
routing table and other items as described previously for the SMA.
Step 6: Enter an integer between 1 and 254 in the Terminal Number scrolling text box to
match the terminal number previously defined in DXRsetup.
Step 7: On the “ports” page of SMA configuration, assign the correct port to the attached
DXR 200. This will change the Terminal Management page to reflect this
connection. Perform this task for all DXR 200s that are connected to SMAs in the
blueprint.
Step 8: On the Terminal Management page, it is possible to now add all DXR 200s that are
not directly connected to a SMA. This can be done by selecting the SMA that is the
bridge to the DXR 200 network on the explorer tree, and them adding them to the
correct port at terminal management time.
Step 9: Find the DXR 200 that is directly connected to the SMA by expanding the network
under the SMA if required.
Note: Unmanaged DXR 200 terminals appear as light grey icons in the explorer tree pane,
and, once managed, they become dark and solid.
6CDDGF2CIGU
When you select a DXR 200 terminal in the Explorer Tree Pane, the Configuration
Workspace displays the following tabbed pages:
• General Setup
• Management Setup
• RF Link Setup
Note: All tabbed pages for a SMA in the Configuration Workspace are documented in
detail in Section 2 of this manual and will not be covered here.
)GPGTCN5GVWR
• Terminal Name
The Type field contains the equipment description of the terminal. This is determined by
DXR NET, depending on the unit selected in the Explorer pane and you cannot change it.
The Terminal Name field is used to hold the name assigned to the terminal in the Network
Blueprint. If you have not assigned a name to the terminal, the field contains the default string
"Terminal aaa" where "aaa" is a three letter sequence. You can change the name by selecting
the field with the mouse and typing in the new name.
The Terminal Name must be unique within the blueprint and can be between 1 and 16
characters long. The Terminal Name is not the terminal number, but you may use a terminal
name that relates to the terminal number, i.e. Terminal 2, if this does actually reflect the
correct terminal number.
Site Information
The Site Information section has three text fields:
• Name
• Description
• Contact Information
The Name field is used to hold the name you assigned to the site in the Network Blueprint. 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 any details of the site you feel should be noted. If you do
not input any details, the field is left blank.
The Contact Information field is used to hold the details of the person responsible for the site.
If you do not input any details, the field is left blank.
Normally, you would have set the details in these fields when you created the 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
(not the terminal icon) is selected in the Explorer Tree.
/CPCIGOGPV5GVWR
DXR 200 terminals can be managed or un-managed. A managed terminal has a SMA gateway
defined to it. This is achieved by adding a site, adding a SMA to a site, deploying DXR 200s
to the SMA and saving the configuration to the network blueprint. Terminals that are un-
managed by a SMA are displayed as greyed out icons in the Explorer Tree pane. Once a DXR
200 terminal is managed, it ceases to be greyed out and can now receive alarm information or
terminal details information.
Note: DXR 200 terminals cannot be monitored unless they have a managing SMA assigned.
Managed
The Managed section has two scrolling list boxes:
• Managing SMA
4(.KPM5GVWR
The RF Link Setup page allows you to pair radios at each end of a link. The terminal you wish
to link to (from your currently selected terminal) is known as a remote terminal.
• Terminal Name
Note: The list boxes are greyed out if the Remote Terminal check box is unchecked.
To set up a remote terminal, click on the Remote Terminal check box field with the mouse
and select the required Site Name and Terminal Name from the options displayed when you
click on the scrolling list box arrows.
Note: You can assign a radio to a remote link only where that radio has not already been
used as a remote link.
You can navigate from a terminal to the remote terminal by right clicking on the mouse and
selecting "Go to Remote Link".
&GRNQ[VJG&:4
Procedure
Step 1: Click on the Configuration Workspace button from the Workspace Selection screen.
Step 2: Add a network site by choosing the Add Site command from the Configuration
Menu, or by right-clicking the mouse button and choosing "Add Site".
Step 4: Click on the Commit button in the Toolbar to commit the change to the blueprint.
Step 5: Add a DXR 200 network element to the site by selecting the site icon in the
Explorer Tree pane and choosing the Add Network Element command from the
Configuration menu, or by right-clicking the mouse button to display the dialog box
below.
Step 6: Select DXR 200 from the list to add this terminal element to the selected site.
Step 7: Select the DXR 200 terminal icon you have added in the Explorer Tree pane.
Step 9: Click on the Commit button in the Toolbar to commit the change to the blueprint.
Step 11: Enter an integer between 1 and 254 in the Terminal Number scrolling text box to
match the terminal number previously defined in DXRsetup
Step 12: Click on the Commit button in the Toolbar to commit the change to the blueprint.
Step 14: Click on the Remote Terminal check box with the mouse.
Step 15: Select the name of the site containing the DXR 200 radio you wish to connect to
from the Site Name drop-down list box.
Step 16: Select the name of the DXR 200 terminal you wish to connect to from the Terminal
Name drop-down list box.
Step 17: Click on the Commit button in the Toolbar to commit the change to the blueprint.
Step 18: Right-click your mouse button on the DXR 200 terminal icon in the Explorer Tree
pane and choose Go to Remote Link to check the result.
#UUKIPC&:4VQC/CPCIKPI5/#
A DXR 200 terminal can be assigned to a SMA in a variety of ways as illustrated in Figures
65-67 in this appendix.
A direct connection to the SMA can be made via the Port and EOW screen. An indirect
connection to the SMA can be made via the Terminal Management screen. Alternatively, the
DXR 200 terminal can be connected to a site and then later connected to the SMA via the Port
and EOW settings page.
Direct Connections
You must assign one DXR 200 to a SMA directly before you can assign further DXR 200s.
See Figure 65 for an example of direct connection.
In the Port and EOW screen you tell the SMA which port it has a DXR 200 plugged into. The
screen contains four list boxes, designated Port A to Port D respectively, one for each for each
of the four possible DXR 200 and DXR 700 radio links the SMA can support. The list boxes
contain the name of the local terminal connected to this port on the SMA.
See "Port and EOW Settings" in Section 2 of this manual for a full explanation of the fields in
this screen.
Note: You cannot perform Terminal Management until you connect a SMA to a DXR
radio via the Port and EOW page.
Step 6: 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.
Note: If you deploy a DXR 200 under a SMA (as opposed to at a site and then adding the
DXR 200 to the SMA) the SMA will assume the first port as displayed in the
Terminal Management page.
6GTOKPCN/CPCIGOGPV5ETGGP
Indirect Connections
An indirect connection is a deployment of a SMA communicating to a DXR 200 via another
DXR 200. The Terminal Management screen enables you to add indirect DXR 200 terminals
(already in the blueprint) to this list, as required. Figure 66. provides an illustration of an
indirect connection.
Step 4: Select a group of terminals in the Unmanaged Terminals section of the dialog box
and choose OK to associate them with the desired V.24 Port of the SMA.
%QOOKUUKQPKPI9QTMURCEGHQT&:4
The Commisioning Workspace displays the Terminal Details screen for a selected DXR 200
terminal. Refer to "Terminal Details for DXR 200" in Section 2 of this manual.
%QOOKUUKQPKPI9QTMURCEGHQT5/#
The Commissioning Workspace displays the SMA Details screen for a selected SMA. Refer
to "SMA Details" in Section 2 of this manual.
The SMA Details Screen also enables Report Printing. Refer to "Producing Reports in Section
4 of this manual.
/CKPVGPCPEG9QTMURCEGHQT&:4
You can use the Maintenance Workspace to monitor the alarm data and terminal details of
any DXR 200 inside a DXR NETwork. This section discusses the alarms and report details for
DXR 200 via the Maintenance Workspace.
8KGY&:4#NCTOU
The alarm settings tabbed page allows you to view the DXR 200 alarm status. The SMA
constantly polls the DXR 200 for its alarm structure and lists all standard DXR 200 alarms.
DXR NET will only display the currently active alarms for a DXR 200 network element.
Alarms are presented in a flat structure on the DXR 200 alarms screen. The flat structure
shows the alarms for the selected terminal. DXR NET only displays alarms that are appropriate
for the terminal type and slot configuration of the DXR 200.
The refresh cycle period on each V.24 port depends on the number of DXR 200 terminals on
that port and on the round-trip to these terminals.
DXR NET will only display the current active alarms for a DXR 200 network element.
Refer to Appendix B in this manual for full details of DXR 200 alarms and descriptions.
Step 2: In the Explorer Tree pane select the DXR 200 terminal whose alarm state you wish
to view.
Step 4: Select the name of the active alarm whose details you wish to view. The alarm name
and a description of the most likely causes will be displayed in the right hand-pane.
Step 5: Take the required action to correct the active alarm, i.e. clear the alarm condition
yourself or, if this is not possible, alert the appropriate network personnel.
8KGY&:46GTOKPCN&GVCKNU
The Terminal Details screen allows you to monitor configuration data for the DXR 200. The
terminal details settings tabbed page is divided into three sections.
• General Information
• Hardware
• Software
The General Information section is self-explanatory.
The Hardware section displays details for the selected DXR 200 terminal, including the
physical positioning of modules, the serial number of each module and the HSC
(hardware/software compatibility number) for each module.
The Software section lists the software loaded into each module in the selected DXR 200
terminal.
Step 2: In the Explorer Tree pane select the DXR 200 icon whose terminal details you wish
to view.
2TQFWEKPIC&:4+PXGPVQT[4GRQTV
You can produce Inventory Reports for all DXR NETwork elements. To produce a report for
the DXR 200 network element selected in the Explorer Tree Pane, click on the Inventory
Report button in the Terminal Details page.
You can save the terminal details report in Word format by clicking on the Save Report
button. This document can then be printed out and used to provide a list of details when
commissioning a system.
/CKPVGPCPEG9QTMURCEGHQT5/#
You can use the Maintenance Workspace to diagnose any faults in a SMA in a DXR 200
network. The monitoring and diagnostic functions available include:
• Alarms
• SMA Details
• File System
8KGY5/##NCTOU
DXR NET polls the SMA to locate the alarms that are active according to the SMA.
• 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.
For Alarm Type field entries, see Section 2 of this manual.
Step 2: Select the SMA network element whose alarm conditions you wish to view.
Step 4: If the icon in the Alarm Status and Related Information pane is red, click on the icon
to move down the hierarchical alarm levels until the alarm is reached. The alarm
name and 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.
Step 6: Use the Alarm Status and Related Information pane to detect when an alarm is
present on a unit, and then to track the alarm to a particular component.
5/#&GVCKNU
DXRNET provides the ability to view the hardware and software details of network elements.
Refer to "SMA Details" in Section 2 of this manual for a description of the fields and buttons
in the SMA details tabbed page.
(KNG5[UVGO
The File System page is used to view and, if necessary, delete BIN files stored on the SMA.
These files are used when loading software to the elements under the control of the SMA, and
should be removed when loading new software.
#RRGPFKZ*7UKPI&:40'6YKVJ&KHHGTGPV
&CVC4CVGU
1XGTXKGY
DXR NET communications have a standard data rate of 38k4 bps, but it is possible to carry
them out over channels that have a lower capacity. This section describes three methods of
doing this.
AFFECTS ON PERFORMANCE. Using a lower port speed can affect performance, and
the size of the network you can monitor.
Note: This section does not contain full details of any required DXR NET functions and
operations already covered in the DXR NET IOM, or in the IOMs for the
DXR NETwork elements.
)GPGTCN
You can select the type of connection that DXR NET uses from the following three types:
• Terminal Connection – you use this when you want to connect your PC to a DXR 100
(without NMS board) or a DXR 700
• NMS Connection – you use this when you want to connect your PC to a DXR 100 (with
NMS board) or a SMA
• Ethernet Connection – you use this when you want to connect your PC to a SMA via a
LAN
With all three types of connection, your PC port will use a standard data rate of 38k4 bps to
communicate with the network. This corresponds to the rate used by the ports on the network
elements. You can therefore connect to a network element without having to worry about the
data rate, providing the actual channel you use has the capacity to support a rate 38k4 bps.
You can ensure this for terminal connections, and NMS connections where your PC is directly
connected to a network element, by using the cables supplied for this purpose by DMC
Stratex Networks. These are designed to support the standard 38k4 bps data rate.
Direct Connection
DXR Network
PC Data Rate = 38k4 bps
• Connect your PC to a data rate converter on the channel, then connect DXR NET to the
network via Ethernet.
5GVVKPIWRC0/5+P1WV%QPPGEVKQP
Although you cannot alter the data rate at which your PC port and the ports on the network
elements communicate, you can alter the rates of the NMS In and NMS Out ports on a SMA.
You can therefore use two SMA to communicate DXR NET communication over a low-
capacity channel by setting the data rate of these ports to less than the maximum capacity of
the channel, then connecting the ports via the channel.
Note 1: The SMA software needs to be SSC 3 or higher.
Note 2: If you change a SSC3 SMA to an SSC2 SMA in your blueprint, then you will only
be able to use the standard 38,400 bps baud rate.
NMS Connection
Data rate (selectable Baud
38k4 bps rate)
DXR Network
PC SMA Low Capacity SMA or
Channel NMS Board
Figure 80: DXR NET Connection to Network via SMA NMS Connection
247 DMC STRATEX NETWORKS
APRIL 2001
IOM-NMS-2/2.5
Appendix H: Using DXR NET with Different Data Rates
You can select baud rates of 2,400, 4,800, 9,600, 19,200, 38,400 or 57,600 bps.
Procedure
CHANGING BAUD RATES. If you make changes to the baud rate of a port that is already
in use, you can cause a loss of communication, requiring manual intervention at the remote
port to re-establish the link. We therefore advise you take great care when making any
changes to the baud rate of an existing link.
Note: This procedure assumes that you know how to configure SMAs using DXR NET.
Step 1: Obtain the maximum data rate of the channel, or the channel with the lowest
capacity in the circuit used to connect to the DXR NETwork.
Step 2: Select the Port/EOW page in the Configuration Workspace for one of the SMA.
Step 3: Select the port(s) you are going to use (NMS In Connected or NMS Out Connected)
by clicking the related check box.
Step 4: For each selected port, select the Site and NMS Unit that the ports are to be
connected to from the related list boxes. This should automatically configure the
ports at the other end of the link in the blueprint.
Step 5: Set the rates for the selected port(s) in the Baud Rates section. If you are changing
the data rate of a port already in use, DXR NET will warn you, and allow you to
Abort, Continue (make the change), or change the port baud rate to match the rate at
the other end of the link.
Step 6: For a new link, repeat Steps 2 to 5 at the SMA at the other end of the link.
Step 7: If required, connect the ports on the SMAs via the link.
You should now be able to communicate with the DXR NETwork by connecting your PC to
the Setup port of the SMA at your end of the link.
7UKPI&CVC4CVG%QPXGTVGTU
You can use two Data Rate Converters at each end of a low-capacity channel to allow the
channel to carry communications between DXR NET and the DXR NETwork. The convertors
take in the 38k4 bps streams from the PC and the network, convert them to streams of a rate
the channel can carry, and then convert the rate of streams received over the channel back to
38k4 bps.
DXR Network
PC Data Rate Low Data Rate SMA or
Converter Capacity Converter NMS Board
Channel
Figure 81: DXR NET Connection to Network using Data Rate Converters
You should refer to the manufacturer’s instructions on how to set up the converters to use the
channel.
7UKPI9KPFQYUK&KCN7R0GVYQTMKPILYKVJC&CVC4CVG%QPXGTVGT
You can connect the PC running DXR NET directly to a low speed channel, provided there is a
Data Rate Converter between the other end of the channel and the network. In this case, you
must connect the Ethernet port on your PC to the channel, use Dial-Up Networking to connect
your PC to the converter outside the DXR NET application, then start up DXR NET using the
Ethernet connection. DXR NET will use the “socket” already set up for the first connection,
and you will be able to access the converter, and therefore the network, over the channel.
Data Rate
38k4 bps
DXR Network
Procedure
Step 1: Connect the V.24 port of your PC to the channel.
Step 2: Go to the Windows Dial-Up Networking, select the modem connection that
DXR NET normally uses, and use this to connect to the converter.
Step 3: Start up DXR NET, and select the Ethernet type of connection. DXR NET will now
use the connection set up in Step 2, and you will therefore be able to access the
network via the low capacity channel.
#RRGPFKZ+&:45QHVYCTG5GVU
DXR software is released in sets. Each new release of any of the software in a set causes a
new set to be released. This allows some software to be in many sets, but each set contains a
different collection of DXR software.
Software for DXR 700 and SMA software is contained in different sets than DXR 100 and
DXR 100 NMS software. Some components of these two product families are common.
Before July 2000, the set numbers were re-used, so set numbers before this data do not
uniquely identify a collection of software.
Note: Details of the software sets for the latest release are supplied on the CD.
5GV
Release Pending
Date 8 Feb 2001
DXR NET 2.4c.2
700 PMA 2.0c
700 RMA 2.0c
700 ODU 2.0c
SMA 1.5a
DXRloader 1.2a
5GV
Release Set 29
Date 8 Feb 2001
DXR NET 2.4c.2
700 PMA 1.4f
700 RMA 1.4f
700 ODU 1.4f
SMA 1.5a
DXRloader 1.2a
5GV
Release Set 24
Date 1 Nov 2000
DXR NET 2.3k
700 PMA 1.4f
700 RMA 1.4f
700 ODU 1.4f
SMA 1.1b
DXRloader 1.2a
5GV
Limited Release Set 21
Date 25 Sep 2000
DXR NET 2.3k
700 PMA 1.3k
700 RMA 1.3k
700 ODU 1.3k
SMA 1.1b
DXR Loader 1.2a
5GV
Release 100-Set 18
Date
DXRTech 6.7d
PR-Base 6.7d
Trans.NMS 1.0g
5GV
Release 100-Set 17
Date
DXRTech 6.7d
NPR-Base 6.7d
Trans.NMS 1.0g
5GV
Release 100-Set 15
Date 14-Aug-00
DXR NET 2.3k
100 NMS 2.1b
100PR 2.0b
DXR Loader 1.0h
5GV
Release 100-Set 14
Date 14-Aug-00
DXR NET 2.3k
100 NMS 2.1b
100NPR 2.0c
DXR Loader 1.0h
5GV
Release Set 12
Date 9 Aug 2000
DXR NET 2.3k
700 PMA 1.3h
700 RMA 1.3h
700 ODU 1.3h
SMA 1.1b
DXR Loader 1.2a
5GV
Release 100-Set 11
Date
DXR NET 2.2d
100 NMS 1.3d
100PR 1.3d
5GV
Release 100-Set 10
Date
DXR NET 2.2d
100 NMS 1.3d
100 NPR 1.3d
5GV
Release Set 6
Date 3-Aug-00
DXR NET 2.2d
700 PMA 1.3h
700 RMA 1.3h
700 ODU 1.3h
SMA 1.0d
5GV
Limited Release Set 5
Date 19-Jul-00
DXR NET 2.2d
700 PMA 1.3g
700 RMA 1.3g
700 ODU 1.3g
SMA 1.0d
5GV
Limited Release Set 4
Date 12-Apr-00
DXR NET 2.2d
700 PMA 1.3d
700 RMA 1.3d
700 ODU 1.3d
SMA 1.0d
5GV
Release Set 2
Date 1-Feb-00
DXR NET 2.0c
700 PMA 1.2e
700 RMA 1.2e
700 ODU 1.3d
SMA 1.0d
#RRGPFKZ,&:40'65QHVYCTG%QORCVKDKNKV[6CDNG
1.1b 1.1c 1.2e 1.3d 1.3g 1.3h 1.4f 0.9x 0.91 1.0d 1.1b 0.6b 2.0a 2.0b 2.0c 1.9l 1.9m 2.0a 2.0b 2.1b
1.9g √ √ √ √ √ √
2.0a √ √ √ √ √ √ √ √ √
2.0b √ √ √ √ √ √ √ √ √ √
2.0c √ √ √ √ √ √ √ √ √ √ √
2.1h √ √ √ √ √ √ √ √ √ √ √ √ √ √
2.2b √ √ √ √ √ √ √ √ √ √ √ √ √ √
2.2c ? ? ? √ √ √ √ √ √ √ √ √ √ √ √ √ √
2.2d ? ? √ √ √ √ √ √ √ √ √ √ √ √ √ √ √
2.3k ? ? ? √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √
2.4c ? ? ? √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √
#RRGPFKZ-#DDTGXKCVKQPU
AGC Automatic Gain Control
ANSI American National Standards Institute
AUI TBD
BER Bit Error Rate
bps Bits per second
CEPT TBD
dB Decibels
dBm Decibels given relative to RF power
DB15 15 pin connector type
DQPSKDifferential Quadrature Phase Shift Keying
DS1 Digital Signal Level 1 (NADH line interface type)
DS3 Digital Signal Level 3 (NADH line interface type)
DXR DMC Stratex Network's Digital Cross-Connect Radio Product
EOW Engineering Order Wire
FEC Forward Error Correction
ft feet
GHz Gigahertz
IF Intermediate Frequency
kbs Kilobits per second
LAN Local Area Network
LED Light Emitting Diode
Mbs Megabits per second
NADH North American Digital Hierarchy
ODU Outdoor Unit
PC Personal Computer
PCM Pulse Code Modulation
PMA Protection Multiplex Adaptor
PSTN Public Switched Telephone Network
QAM Quadrature Amplitude Modulation
+PFGZ
Configuration Workspace, 2, 13, 21, 212, 213,
A 214, 215, 216
General Setup Page
Action Table, 41
Site Name Field, 60
Advanced IP Table, 221
Terminal Name Field, 60
AGC Alarm Limits, 136
Interface Setup Page, 60
AGC Graph, 156
Page Variation, 21
Alarm Board
Tabbed Pages, 21
Mk I, 42
Toolbar, 19
Mk II, 42
Working Offline, 21
Alarm Inputs for DXR 100, 146
CONNECTION PROTOCOL
Alarm IO, 39
DXR 100 WITH NMS, 8
Alarm Outputs for DXR 100, 146
DXR 100 WITHOUT NMS, 8
Alarms
DXR 700, 9
Commissioning Page
Connection Protocol for DXR 100 with a NMS
Alarm Information, 56
Board, 8
View Alarms Button, 56
Connection Protocol for DXR 100 without a NMS
External on SMA, 134
Board, 8
Forward and Reverse Power, 135
Connection Protocol for DXR 200, 227
SDM Board, 212
Connection Protocol for DXR 700, 9
Viewing Alarm Status, 147
Connection Protocol for SMA, 9
Viewing Alarms, 165
CONNECTION PROTOCOLS, 7
Alarms, Table of, 165
CONNECTION TYPE SELECTION, 8
Assign a DXR 200 to a SMA, 237
Connections to a DXR 200, 10
AUX Ports, 132
Constellation, 74
Constellation Diagram, 154, 203
B
constellation monitoring
Baud Rates, 24 24 hour, 74
Blueprint, 12 Contacting Digital Microwave Corporation, 164
Correctable Bytes per Second, 44
C Correctable Bytes per Second Calculation, 206
Correctable Bytes per Second Threshold, 137
Checking for Alarms, 147
Cross-connects, 210
Clock Source, 133
customer support
Clock Sources, 26
details, 159
Clocking Hierarchy, 210
Customer Support, 164
COMMISSIONING REPORTS, 161
CUSTOMIZATION
Commissioning Workspace, 2, 14, 20, 54, 211,
LANGUAGESUPPORT, 3
212
Toolbar, 19
D
Uses, 54
Commissioning Workspace for DXR 200, 240 DB15, 42
Commissioning Workspace for SMA, 240 Define Terminal Numbers, 228
Commit Configuration, 18 DELETING OLD SOFTWARE FILES, 158
Compatability Problems Deploy the DXR 200, 236
Alarm Boards, 160 Deploying the DXR 200 Network, 231
Complex Models, 229 Direct Connections, 237
CONFIGURATION DATA, 13 DS1 Line Interface Parameters, 143
WINDOWS 98, 93 F
WINDOWS 95, 85
Factory set duplexer freqency, 63
DIAL-UP NETWORKING, 88
Frequency Diversity, 35
INSTALLING DMC DXR DRIVER UTILITY, 89
Frequency Range, 207
INSTALLING DXRNET, 88
Frequency Step Size, 207
INSTALLING WINSOCK2, 90
STARTING WINDOWS® DIAL-UP
G
NETWORKING, 89
WINDOWS 98 General Setup, 232
REMOVING EARLIER VERSIONS, 91, 95 GUI
WINDOWS 98, 90 Explorer Window, 12
FROM CD, 93, 96 GUI, 2, 15
WINDOWS NT, 95
Configuring Dial-up Networking, 98 H
INSTALLING RAS, 98
Hardware Supported, 6
INSTALLATION REQUIREMENTS, 84
HELP MENU
HARDWARE, 84
ABOUT DXR NET, 19
NMT, 85
NMT, 84 High Speed Daughter Board, 214
REMOTE TERMINAL, 38 Hot Standby, 35
RSSI PAGE
MONITOR ALL/RESET ALL BUTTONS, 82 I
TOOL LEVEL, 1 IDU, 33
UNABLE TO COMMUNICATE, 56 Indirect Connections, 239
WARNING MESSAGE, 54 INSTALLING SYSTEM SOFTWARE, 157
WARNING MESSAGES, 163 Interface Setup, 28
DXR NET GUI, 3 INVENTORY REPORTS, 162
DXR NETwork, 100 IRU, 34
Element Configuration, 21
Network Blueprint, 100 L
Network Element, 54
Network Element Alarms, 58 LAN, 218
NMS Element Line Interface Type, 140
IP Addressing, 105 LOADING SOFTWARE TO NETWORK ELEMENTS, 157,
158
E Loopbacks
Checking terminals, 152
E1 Line Interface Parameters, 141 FEC disable, 153
E3 Line Interface Parameters, 142 Checking test equipment and terminal
Element Manager, 1 connection, 151
EM, 1 Checking the link, 151
E-mailing blueprints, 117 RF/Modem Loopbacks, 149
EOW, 25 Tributary Loopbacks, 148
SMA, 133 Types of, 148
EOW Interface, 133 Low Speed Daughter Board, 213
EOW Ring Tones, 25
Equalizer Graph, 156 M
ERROR MESSAGES, 20
Ethernet, 8, 9, 120 Maintenance Workspace, 2, 14, 21, 73, 212
Description, 120 Advanced Options, 18
Ethernet Interface, 226 Tabbed Pages, 73
Ethernet, Connection Requirements, 217 Toolbar, 19
Event Maintenance Workspace for DXR 200, 240
Mapping an Event to an Action, 138 Maintenance Workspace for SMA, 244
Removing an Event from an Action, 140 MANAGEMENT DOMAIN:, 7
Explorer Tree Pane, 20 Management Setup, 233
External Alarms on a SMA, 134 MANAGING NETWORK ELEMENTS, 13
External I/O - SMA, 42 Mask IP Address, 28