Datatek UMI User Manual
UNIVERSAL MEDIATION
I
NTERFACE (UMI) MODULE
SER'S MANUAL
U
Release 28.x
UMI
UMI
102 SW Orange Blossom
Lake City, Florida
32025-1613
phone: 386-754-5700
email: sales@trdcusa.com
http://www.trdcusa.com
Manufacture & Distribution:
http://www.datatekcorp.com
CONTENTS
1 INTRODUCTION ................................................................................... 6
1.1 FEATURE SUMMARY ...................................................................................................... 6
1.1.1 504 Virtual Sessions per UMI .................................................................................... 6
1.1.2 Seamless Operation in Either Call Set-up Direction .................................................. 6
1.1.3 Closed User Groups (CUGs) ..................................................................................... 6
1.1.4 Hunt Groups ............................................................................................................... 6
1.1.5 Domain Name Server (DNS) capability ..................................................................... 6
1.1.6 Peer to Peer Encryption ............................................................................................. 6
1.1.7 TACACS+ RADIUS LOGIN Support .......................................................................... 7
1.1.8 Virtual PAD Support ................................................................................................... 7
2 PHYSICAL DESCRIPTION ....................................................................... 8
2.1 FACEPLATE ..................................................................................................................... 8
2.1.1 Light Emitting Diodes (LED) ...................................................................................... 8
2.1.2 Mode Switch .............................................................................................................. 8
2.1.3 Reset Button .............................................................................................................. 8
2.2 High Performance I/O Board ............................................................................................. 9
2.2.1 Serial .......................................................................................................................... 9
2.2.2 Console .................................................................................................................... 10
2.2.3 10/100 BaseT and Fiber LAN .................................................................................. 10
2.2.4 DSU.......................................................................................................................... 10
2.2.5 Variants .................................................................................................................... 10
2.3 Standard Performance I/O Board ................................................................................... 11
2.3.1 Console .................................................................................................................... 11
2.3.2 LAN .......................................................................................................................... 11
3 INSTALLATION .................................................................................. 12
3.1 INSERTING THE I/O BOARD ......................................................................................... 12
3.2 REMOVING THE I/O BOARD ......................................................................................... 12
3.3 INSERTING THE UMI MODULE .................................................................................... 12
3.4 REMOVING THE UMI MODULE .................................................................................... 12
3.5 CABLING ........................................................................................................................ 13
3.5.1 Cabling the I/O Console Port ................................................................................... 14
3.5.2
Cabling the CEY5 LAN Port ..................................................................................... 15
3.6 Field Upgrade and Software Registration ...................................................................... 16
4 CONFIGURATION ............................................................................... 19
4.1 OVERVIEW ..................................................................................................................... 19
4.2 BASE CONFIGURATION ............................................................................................... 20
4.3 OPERATIONAL CONFIGURATION ............................................................................... 21
4.3.1 BNS-to-IP Calling ..................................................................................................... 21
4.3.2 IP-to-BNS Calling ..................................................................................................... 26
4.4 CLOSED USER GROUPS .............................................................................................. 30
4.4.1 IP-to-BNS Calling ..................................................................................................... 30
4.4.2 Telnet Console ......................................................................................................... 31
4.4.3 SNMP Interface ........................................................................................................ 31
4.5 UMI CONFIGURATOR ................................................................................................... 31
5 UMI MODULE COMMAND REFERENCE ................................................... 32
5.1 LOGIN ............................................................................................................................. 32
5.2 LOGOUT ......................................................................................................................... 32
5.3 CHGPASS ....................................................................................................................... 32
5.4 LOCAL............................................................................................................................. 32
5.5 GATEWAY ...................................................................................................................... 33
5.6 DOMAIN NAME SERVER ............................................................................................... 33
5.7 TACACS+ RADIUS Servers ........................................................................................... 33
5.8 HELP ............................................................................................................................... 34
5.9 VERSION ........................................................................................................................ 34
5.10 REBOOT ..................................................................................................................... 34
5.11 REMOVE MODULE ..................................................................................................... 34
5.12 RESTORE MODULE ................................................................................................... 35
5.13 CLEAR MEASUREMENTS ......................................................................................... 35
5.14 DISPLAY MEASUREMENTS ...................................................................................... 35
5.15 VERIFY ........................................................................................................................ 35
5.16 HOST NAME ADMINISTRATION ............................................................................... 35
5.17 Mnemonic PDD ADMINISTRATION ........................................................................... 36
5.18 SNMP .......................................................................................................................... 36
5.19 INSTALL ( Software Registration ) .............................................................................. 37
5.20 RSTPASS ( Resetting the Password ) ........................................................................ 38
5.21 CONSOLE TIMEOUT .................................................................................................. 38
5.22
VIRTUAL PORT ADMINISTRATION .......................................................................... 39
5.23 VIRTUAL PAD ADMINISTRATION ............................................................................. 42
5.24 VIRTUAL PAD SNOOPER .......................................................................................... 44
5.25 CLOSED USER GROUP (CUG) ADMINISTRATION ................................................. 45
5.26 DISPLAY CONNECTIONS .......................................................................................... 45
5.27 DISCONNECT PORT .................................................................................................. 45
5.28 PING ............................................................................................................................ 45
5.29 TraceRoute .................................................................................................................. 46
5.30 Label ............................................................................................................................ 46
5.31 Administrative Password ............................................................................................. 47
5.32 CONSOLE Administration ........................................................................................... 47
5.33 HPIO Administration .................................................................................................... 47
5.34 ADMINISTER SECURITY BANNER ........................................................................... 48
5.35 DATA-BASE RESET ................................................................................................... 48
6 UMI SNMP AGENT .............................................................................. 49
6.1 SNMP Version 1 Commands .......................................................................................... 49
6.2 UMI SNMP MIB Variable Database ................................................................................ 49
7 SUPPORTED TRAPS ............................................................................ 51
8 APPENDIX A: UMI MODULE MEASUREMENTS ......................................... 52
9 APPENDIX B: UMI VIRTUAL PORT MEASUREMENTS ................................ 54
10 APPENDIX C: ALARMS ........................................................................ 55
10.1 Major Alarms ............................................................................................................... 55
10.2 Minor Alarms ............................................................................................................... 55
10.3 Info Alarms .................................................................................................................. 55
11 APPENDIX D: USING STARKEEPER TO CONFIGURE THE UMI ................... 56
11.1 PRE-CONFIGURATION ACTIVITIES ......................................................................... 56
11.1.1 Package Installation ................................................................................................. 56
11.1.2 Develop Configuration Information .......................................................................... 56
11.1.3 Perform BNS Activities............................................................................................. 58
11.1.4 Perform UMI Activities ............................................................................................. 58
11.2 USING THE UMI CONFIGURATOR ........................................................................... 58
11.2.1 UMI Configurator Menu of Operations ..................................................................... 58
11.2.2
Running the UMI Configurator ................................................................................. 59
11.3 POST-CONFIGURATION ACTIVITIES ....................................................................... 59
12 APPENDIX E: UMI HUNT GROUP DEMONSTRATION ................................. 60
13 APPENDIX F: UMI CLOSED USER GROUP DEMONSTRATION ..................... 61
14 Appendix G: Virtual PAD Example ......................................................... 63
15 Hardware Warranty ............................................................................ 64
16 Software End-User License Agreement .................................................. 64
16.1 Software License ......................................................................................................... 64
16.2 Intellectual Property Rights ......................................................................................... 64
16.3 Software Support ......................................................................................................... 64
16.4 Export Restrictions ...................................................................................................... 64
16.5 Limited Warranty ......................................................................................................... 65
16.6 No Other Warranties .................................................................................................... 65
16.7 Limitation of Liability .................................................................................................... 65
16.8 Special Provisions ....................................................................................................... 65
17 Sales & Distribution ............................................................................ 66
18 Author .............................................................................................. 66
UNIVERSAL MEDIATION INTERFACE (UMI) USER MANUAL
1 INTRODUCTION
Connectivity between an IP network and a BNS (refers to both BNS-2000 and BNS-2000 VCS)
network is accomplished using the Universal Mediation Interface Module (UMI). As a state-of the-art “solid state” module (no disks or fans) which resides in a BNS node, the UMI is both a
replacement and enhancement of the LCS60 product.
The UMI allows both synchronous and asynchronous endpoints connected to a BNS network to
access endpoints on an IP network. Similarly, endpoints on an IP network can access both
synchronous and asynchronous endpoints on a BNS network.
The UMI can be located anywhere in the BNS network, thus simplifying configuration,
administration and maintenance without affecting operation or connectivity.
1.1 FEATURE SUMMARY
The UMI provides a complete mediation interface (i.e., gateway) for BNS and IP protocols. The
basic features are:
1.1.1 504 Virtual Sessions per UMI
The UMI operates like a “virtual SAM504”, in effect mapping 504 SAM ports within a BNS network
to 504 “virtual ports” residing in the IP network, and vice versa.
1.1.2 Seamless Operation in Either Call Set-up Direction
The UMI provides the terminal/PC user on either network with a “terminal server” type interface
where a connection setup to a user/device on the other network can be made to appear to the
calling user as if the destination endpoint is on the same network.
1.1.3 Closed User Groups (CUGs)
The UMI supports Closed User Groups (CUGs) to restrict callers to specified destinations. This is
an important feature for protecting sensitive endpoints in a corporate wide network without the
burden of special “security servers”.
1.1.4 Hunt Groups
A Hunt Group is a set of UMI “virtual ports”, which are arranged to receive calls from the IP
network at a common address.
1.1.5 Domain Name Server (DNS) capability
The UMI can maintain a set of mnemonic host names, analogous to the /etc/hosts file on both
UNIX and Microsoft Windows platforms. This allows the UMI to perform a translation betwe en a
user-provided name and its associated IP address and TCP port number, for BNS-to-IP calls. The
use of a mnemonic name is optional; the UMI will always accept an IP address in its base form.
Additionally, the UMI allows for the definition of an external DNS to be used for translation of
mnemonic addresses not defined in the internal host table. Three DNS name server IP addresses
are supported by the UMI.
1.1.6 Peer to Peer Encryption
The UMI can encrypt user data on the IP network. This prevents unauthorized access to sensitive
information. Encryption can be enabled on a per session basis.
04/30/09
6
UNIVERSAL MEDIATION INTERFACE (UMI) USER MANUAL
1.1.7 TACACS+ RADIUS LOGIN Support
The UMI supports up to two TACACS+ RADIUS servers for login authentication. These are a
primary, and a secondary, although each is individually enabled. The TACACS+ support is for
either encrypted, or clear authorization. Encryption keys may contain spaces.
1.1.8 Virtual PAD Support
The UMI allows individual virtual ports to be defined a PAD functions. This allows IP resident
operations sytems (e.g. REACT) to communicate with network elements resident on DK/BNS
X25P and other modules. The PAD implementation is similar to that implemented on the DT-xx8x
devices.
At the current time, the Virtual Pad feature is only available to a UMI that is administered in the
DKCC as a SAM504.
04/30/09
7
UNIVERSAL MEDIATION INTERFACE (UMI) USER MANUAL
2 PHYSICAL DESCRIPTION
Reset
Mode
Datatek
Enabl
Diag
Disab
Fault
Off
Line
On
Line
Switch
Red
Yellow
Green
TN
2525
U M I
X
X
A
Y
O
O
Q
P
S
D
2.1 FACEPLATE
2.1.1 Light Emitting Diodes (LED)
The lights on the module faceplate are green, yellow, and red. They indicate on-line, off-line, and
fault states respectively. When the module circuitry detects an on-board fault, the red LED (fault)
is lit.
2.1.2 Mode Switch
The Mode Switch supports three positions: Enabl, Diag and Disab. The Mode switch must be in
the Enabl position for the UMI to function properly.
2.1.3 Reset Button
When the Reset button is pressed, the module buffers and registers are cleared, and the module
application program is restarted. The module is taken out of service, and all connection s are
terminated.
04/30/09
8
UNIVERSAL MEDIATION INTERFACE (UMI) USER MANUAL
2.2 High Performance I/O Board
The UMI1 mates with the DTK41 High Performance I/O (HPIO) board in support of the UTM
connectivity options. The DTK41 I/O board contains all the necessary connectors the UTM
requires for currently available Console and LAN connections.
Note: Cables and adapters are available
DTK41
Console
DSU
10/100 #3
10/100 #2
10/100 #1
DSU
10/100 #3
10/100 #2
10/100 #1
Serial
Fiber (SC)
Link
Traffic
100
Fiber (ST)
Fiber Indicators
Link
Traffic
ST Plug-In
(Only if ST Fiber
is required)
100
Power
2.2.1 Serial
The UMI does not use the serial interface of the DTK41 at this time. The DTK41 Serial interface is
software configurable. Options are as an RS-232C DTE for seri al rates up to 64Kbps, or as a
V.35 DTE for serial rates up to E1.
1
A Series 1:2 UMI is required for the DTK-41 (or any other I/O board which requires power) since the
original UMI did not provide any power whatsoever to the I/O module, and the original UMI did not
provide a management interface.
04/30/09
9
UNIVERSAL MEDIATION INTERFACE (UMI) USER MANUAL
2.2.2 Console
The UMI Console interface may be used for console activities and the initial configuration. It
assumes the connected device is configured as 9600 baud, 8 bits and no parity.
2.2.3 10/100 BaseT and Fiber LAN
The DTK41 LAN and Fiber ports are used for IP network connectivity. The UMI supports Internet
peer level protocols (e.g. IP, TCP, UDP, ICMP and SNMP). All of the 10/100 ports are fully
switched, not bridged. The capacity of the switch is over 1Gbps. The 10/100 and Fiber ports a re
managed from the UMI console. Each 10/100 port and the Fiber port may be enabled or disabled
individually. Alarms are generated if a link is established, or if a link is lost.
An advanced feature DTK41 is that no crossover cable is ever required on the 10/100 ports. The
10/100 ports will automatically correct for the cabling mismatch.
The 10/100 ports will self-configure to match the speed of the link (10 Mbps or 100 Mbps ), and
the Duplex ( Full or Half ). No configuration is required.
The Fiber interface connects to the industry standard SC cabling. If ST cabling is used, the
DTK41 ST plug-in module is used. No adapter cables are required.
2.2.4 DSU
The UMI does not utilize the DSU interface at this time. The DTK41 DSU (4-wire) interface is
software configurable for T1 or E1 rates. A value of T1 is used for domestic 1.544 MHz interfaces
with 193 Bit Superframes. A value of E1 is used for European 2.048 MHz interfaces with 256 Bit
Superframes. The DSU functionality is built in. This interface may be used for connectivity to
TDM, Frame Relay, and ATM networks.
2.2.5 Variants
The DTK41 high performance I/O board is available with two different mounting brackets. The
DTK41N incorporates a mounting bracket specifically designed to be installed in a BNS node, a
Datakit VCS node, or an MPC. The DTK41S has a mounting bracket specifically designed to be
placed in a SAM504, SAM64, or SAM128. It is anticipated that the UMI shall use only the
DTK41N variant of the DTK41.
04/30/09
10
UNIVERSAL MEDIATION INTERFACE (UMI) USER MANUAL
2.3 Standard Performance I/O Board
The UMI mates with the CEY5 I/O board in support of the UMI connectivity options. The CEY5
I/O board contains all the necessary connectors the UMI requires for currently available Console
and LAN connections.
Cables and adapters are available.
Serial
CEY5
(Currently Not Used)
Console
LAN
DSU
(Currently Not Used)
2.3.1 Console
This interface requires a standard RJ45 terminated, twisted pair, data cable. It connects as a
data terminating equipment (DTE) to an asynchronous device and uses RS-232C signaling.
Connection to the UMI console is required for UMI “Module-Based” Administra tion (described
later in this document) or StarKeeper® II NMS alarm collection
2
. Otherwise, the console can be
disconnected during normal operation.
2.3.2 LAN
This interface requires a standard RJ45 terminated Category 5, twisted pair, data cable. It
connects to a 10BaseT hub or Router on the local LAN segment.
2
The UMI also supports console access through a TCP telnet connection, which is accessed
using TCP port 1023. This service is available only when the unit is in service.
04/30/09
11
UNIVERSAL MEDIATION INTERFACE (UMI) USER MANUAL
3 INSTALLATION
UMI installation consists of:
inserting the DTK41 or CEY5 distribution board in the backplane slot
inserting the module in the corresponding shelf slot
cabling console and data ports
When installing a UMI:
Ensure protection from electromagnetic interference (EMI). Wear an electrostatic discharge
(ESD) wrist strap to prevent equipment damage.
To prevent damage to module circuitry, always insert the I/O board before inserting its
corresponding module. Never remove the I/O board before removing the module.
3.1 INSERTING THE I/O BOARD
The I/O board plugs into the backplane at the rear of the shelf; it is held in place by shrouds on
the backplane pinfield, and secured with two screws. Insert the I/O board before inserting its
corresponding UMI.
Align the I/O board backplane connector with the backpla ne pinfield, and align the screw slots
with the screw holes.
Slip the backplane connector onto the pins. The board should seat easily. If seating is
difficult, the board may be canted or some pins may be bent.
Insert the screws, and tighten them securely.
3.2 REMOVING THE I/O BOARD
Remove the I/O board only for relocation, replacement, or board type confirmation.
Requirement:
Disconnect all cabling to I/O board ports, labeling the cable ends if appropriate.
Remove the screws holding the I/O board in place.
Carefully rock the board as you pull it out.
The Module in the slot corresponding to the I/O board must be removed first.
3.3 INSERTING THE UMI MODULE
Requirement: The I/O board for the module must be installed in its corresponding slot on the
backplane at the rear of the shelf first.
Set the mode switch on the module faceplate to Disab.
With the module latch extended, carefully push the module all the way into the slot. The
backplane pins slip into the module receptacle.
Close the latch to lock the module into position.
Move the mode switch on the module faceplate to Enabl.
3.4 REMOVING THE UMI MODULE
You can remove and replace a UMI in an operating node without damaging the module itself, or
without disrupting calls on other modules. Only the calls on the UMI being removed are di srupted.
Requirement:
the rear of the shelf.
If the mode switch is in the Enabl position, move it to Disab.
Open the latch on the module faceplate.
Pull the module straight out of the slot.
I/O board for the module must still be in its corresponding slot on the backplane at
04/30/09
12
UNIVERSAL MEDIATION INTERFACE (UMI) USER MANUAL
3.5 CABLING
This section provides information on how to cable the UMI console and data ports with the CEY5
I/O board. Consult the following table for ordering information regarding all of the cabling options
shown in this section.
Cable / Adapter Description ED5P055-31 Group
Number or Comcode
258B adapter 50-pin M to 6 8-pin mod G(154)
Mod – DB15 adapter 8-pin mod to DB15 M
D8AH-M adapter 25-pin M to mod socket G(139)
D8AH-F adapter 25-pin F to mod socket G(147)
Console
8-pin mod to 8-pin mod 408198133
(special wiring)
Straight mod cable 8-pin mod to 8-pin mod G(137), G(G)
CAT5 cable 8-pin mod to 8-pin mod
(shielded)
Note: The AH adapter will be used to terminate the cable and will be attached to the appropriate
device. The attached device will determine the gender of the AH adapter.
Important! A Console cable with “SPECIAL WIRING”
can be ordered using the above table or built using
the following wiring diagram.
Console Cable - SPECIAL WIRING (U M I)
RJ45 RJ45
1
2
3
1
2
3
04/30/09
4
5
6
7
8
4
5
6
7
8
13
UNIVERSAL MEDIATION INTERFACE (UMI) USER MANUAL
3.5.1 Cabling the I/O Console Port
Depending upon access availability, one of the cables shown in the following diagram will be
needed to set up a UMI console connection.
AH SAM8/16
AH
AH
AH
258B
Modem
Patch Panel
PC or
Dumb Term
TY / SAM64
Mode
Datatek
2525
UMI
TN
Reset
Enabl
Diag
Disab
Fault
Off
Line
On
Line
straight mod cable
straight mod cable
Console
DSU
LAN #3
D
LAN #2
LAN #1
T
K
4
Serial
straight mod cable
console cable
special wiring
console cable
special wiring
1
X
X
A
Y
O
O
Q
P
S
D
FIBER
LAN
U
M
I
04/30/09
C
E
Y
5
Serial
Console
LAN
DSU
straight mod cable
straight mod cable
straight mod cable
console cable
special wiring
console cable
special wiring
AH
AH
AH
AH
258B
SAM8/16
Modem
Patch Panel
Dumb Term
TY / SAM6 4
14
UNIVERSAL MEDIATION INTERFACE (UMI) USER MANUAL
3.5.2 Cabling the CEY5 LAN Port
The following will be needed to set up a UMI data connection.
A Shielded Twisted Pair CAT5 cable is attached to the LAN port of the I/O board and will
allow for cabling to either a hub or router. The DTK41 I/O board may use a 10BaseT or
100BaseT hub or router. The CEY5 I/O board uses a 10BaseT hub or router.
Console
DSU
LAN #3
LAN #2
LAN #1
Serial
FIBER
LAN
STP CAT5
Cable
SC Fiber
or
ST Fiber
HUB / Switch
Router
HUB / Switch
Router
Mode
Datatek
TN
2525
UMI
Reset
Enabl
Diag
Disab
Fault
Off
Line
On
Line
X
X
A
OOY
Q
P
S
D
D
T
K
4
1
Mode
Reset
Datatek
TN
2525
UMI
Enabl
Diag
Disab
Fault
Off
Line
On
Line
X
X
A
Y
O
O
Q
P
S
D
C
E
Y
5
Serial
Console
LAN
DSU
STP CAT5
HUB / Switch
Cable
Router
04/30/09
15
UNIVERSAL MEDIATION INTERFACE (UMI) USER MANUAL
3.6 Field Upgrade and Software Registration
The
UMI, when initially delivered, will need one or more software keys to activate the software.
Software keys are also required when an optional individual feature packages are add ed to the
device. Finally, when the
required to register the installed software and any feature packages registered for the device.
UMI is upgraded with revised software, one or more software keys are
When performing an upgrade, the revised software is initially downloaded by
staging area and is not active. The software then is activated by a reboot. The new software will
execute normally prior to registration. However, no backup, reloads, or upgrades can be
performed. Module level parameters, such as the device IP address, may be changed and
activated. Interface specific parameters cannot be changed.
The procedure for performing a software registration has been mechanized. Manual pro ce dures
are error prone and not recommended. They are no longer covered in this user manual.
The mechanized Software Upgrade Registration procedure allows simplified administration of one
or more devices. When a quantity of devices are upgraded, manual software registration of each
device has the potential of becoming increasingly tedious. The mechanized software upgrade
registration process was designed to alleviate the problems associated with multiple device
upgrades. It is also preferred for single device upgrades as it eliminates any potential for error.
The new software is downloaded to the
for one or more devices. The “-r” option to the dtupgrade command will restart the device on the
new software after the download completes successfully. It is highly recommended. In the
alternative, the device may be downloaded without a restart and restarted at a later time during a
scheduled maintenance window. Restarting the device on the new software prior to registration is
required. After the restart, the devices will continue to operate normally on the new software
without registration. Some operations interface functions are inhibited pending software
registration. Below is an example of a typical
as it is recommended.
UMI via the upgrade command. This may be performed
upgrade invocation. Note the use of the “-r” option
upgrade into a
upgrade –v –d –r –mUMI 192.168.0.234 umi.28.1
Mechanized registration is performed in three steps. Each of which doe s not require user
intervention.
The steps are as follows:
1. The
04/30/09
getinfo utility is invoked on a file containing a list of devices to be administered.
This file is called the master device list file and is typically named “dt_device.master”.
The master device list file may have any name and it is provided as an argument to
16
UNIVERSAL MEDIATION INTERFACE (UMI) USER MANUAL
the
getinfo utility. The master device list may also contain devices that do not require
registration. The
and creates a device information file named “dt_device.info” in the current directory.
getinfo utility makes inquiry of each device in the master device list
2. The “dt_device.info” file is then sent via email to keys@trdcusa.com
processing.
3. A file name “dt_device.register” file is returned via email to be used as input in the
next step. A file named “dt_device.msgs” is a text file that may be displayed or
printed showing the results of the registration function.
4. The
5. The “dt_device.info” file and the “dt_device.register” file are deleted as they are
The source for the registration procedure is the inventory master device list file that is created,
and maintained, by the administrator using their favorite text editor.
The master device list file contains one IP address per line, with an optional TCP port, and an
optional password override, to access the device. The IP address is the console connection
address, and not necessarily the actual device IP address. Registration via the serial console is
explicitly supported. Comments are allowed between addresses, and after addresses. A
password override is only required if the default password of “initial” has been changed.
setreg utility is invoked and uses the “dt_device.register” file provided as an
argument. If no argument is provided, the file is assumed to be in the current
directory. The
been assigned keys. One or more keys are installed during the dialogue.
transient and have no further value. Neither can be reused for the purpose of
registration. However, the dt_device.info file may be used for inventory reports..
setreg utility contacts each device that requires registration and have
for registration
The master device file line format is as follows:
<IP ADDRESS> [<TCP PORT>] [-P<Password>] # Comment
An example “dt_device.master” file follows:
# This is a Sample master device list file “dt_device.master”.
# Note that there is one device ( Connect IP Address ) per line.
# TCP Port Override is allowed. Registration may use the serial console.
# Password Override is allowed.
# It is OK to have devices that do not need registration listed for inventory.
# Comments in this file are preceded with a pound symbol.
# Blank Lines are treated as comments.
# Basic Line Format is as follows:
04/30/09
17
UNIVERSAL MEDIATION INTERFACE (UMI) USER MANUAL
10.0.1.80 # Device at Location ‘A’
192.168.7.82 # Device at Location ‘B’
192.168.7.155 50001 # Example of TCP port Override.
192.168.7.156 50001 –pcustom1 # Example of Password Override.
Once the “dt_device.master” file is prepared, it is used as an input to the
dtgetinfo dt_device.master
This
getinfo utility will collect information on each device in the master file. The getinfo utility will
also make a determination if a registration is actually required. Consequently, the
also useful in performing inventory functions outside of the device registration. The output of the
getinfo utility.
getinfo utility is
getinfo utility is a file named “dt_device.info” that is always created in the current directory.
The file “dt_device.info” is attached to an email and sent to the address keys@trdcusa.com
registration procedure is performed and a file named “dt_device.register” is attached to return
email to the original sender. A messages file named “dt_device.msgs” is also attached and may
be printed as a report of the key generation function.
After receiving the “dt_device.register” file, the
“dt_device.register” file as it’s sole argument. The setreg utility will only contact the devices that
actually need registration, and for which one or more keys were successfully generated. All of the
appropriate keys, including a device key and multiple per port feature package keys, are installed
by the
setreg utility. The device is not restarted and this operation may occur during normal
transport operation.
setreg utility is invoked with the relative path of the
.The
A report utility
inventory information. The usage is as follows:
devrep is available. The devrep utility uses the “dt_device.info” file to display the
devrep [-v] dt_device.info
If the file is not specified, the dtdevrep utility attempts to use the “dt_device.info” file resident in
the current directory.
04/30/09
18
UNIVERSAL MEDIATION INTERFACE (UMI) USER MANUAL
4 CONFIGURATION
4.1 OVERVIEW
The following diagram is a functional representation of UMI operation, intended as an aid to
understanding the configuration process.
UMI Module in BNS Node
IP
Network
504 SAM
Sync / Async
Ports
504 UMI
Virtual Ports
Any
TCP/IP
Endpoint
BNS
Network
In order to allow it to be deployed in any BNS node without requiring an upgrade of the node
software, the UMI has been designed to appear to the node controller as a T1-T runk-connected
SAM504. This requires the administrator to follow the same configuration command sequence
that would be used for a SAM504 (with specific entry parameters described later in this
document), using either StarKeeper II NMS or the node’s local console. Administration of
additional parameters specific to the UMI, referred to as “Module Based” administration, is
accomplished through the UMI’s console function, which is accessed via the RS-232 con sol e port
on the CEY5 I/O board or via a TCP/telnet connection from a device anywhere in the IP network.
UMI “Module Based” administration can also be accomplished through StarKeeper II NMS.
I
04/30/09
19
UNIVERSAL MEDIATION INTERFACE (UMI) USER MANUAL
The overall configuration process can be divided into two phases:
Base Configuration – setting up the UMI for IP connectivity and console security
Operational Configuration – setting up the UMI and BNS node to enable users to make calls
between the BNS and IP networks
Actual command sequences will be presented in this section to illustrate the UMI and related
node configuration process. For node commands, the appropriate references are the Data
Networking Products Synchronous/Asynchronous Mul tiplexer Reference and Commands
Reference. Section 5 of this document should be used as the reference for UMI module
commands.
4.2 BASE CONFIGURATION
This phase of the configuration process sets up the UMI for IP networking. This includes the
UMI’s IP address and subnet mask, the IP address of the gateway router, the IP address of an
SNMP manager (optional), and the IP address of a domain name server (optional). It also
includes setting up console-security parameters, i.e., an administrative login password and the
(optional) timeout for automatic console logoff. These aspects of the configuration will rarely need
to be changed once they are satisfactorily set up.
The following is an example of base configuration:
<UMI> login passwd=initial
User is Logged in UMI
<UMI> chgpass old=initial new=secret confirm=secret
Password Change Operation Succeeded.
<UMI> rm
Remove
MODULE removed from service.
<UMI> local ipaddr=135.17.59.165 submask=255.255.255.0
<UMI> gateway ipaddr=135.17.59.1
<UMI> dns ipaddr1=135.17.59.6
<UMI> snmp ipaddr=135.17.59.7
<UMI> vfy mod
Current Configuration:
DK Module Type ==> TN1015 (TRK-T1) w/Serial# 0.
Service State ==> Out of Service.
Local MAC Address ==> 0.96.29.2.52.22
Local IP Address ==> 135.17.59.165
Subnet Mask ==> 255.255.255.0
Gateway IP Address ==> 135.17.59.1
DNS Name Server Address ==> [#1] 135.17.59.6
SNMP Trap Manager ==> 135.17.59.7 Port 162
<UMI> rs
Restore
Module restored to service
Reboot Initiated to Make Physical Parameters effective.
04/30/09
20
Loading...