mediaband tdm-4 user manual v1.4

2012 Patapsco Designs Ltd

MediaBand TDM-4 User Manual V1.4

All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage and retrievalsystems - without the written permission of the publisher.Products that are referred to in this document may be either trademarks and/or registered trademarks of the respective owners. The publisher and the author make no claim to these trademarks.

While every precaution has been taken in the preparation of this document, the publisher and the author assume no responsibility for errors or omissions, or for damages resulting from the use of informationcontained in this document or from the use of programs and source code that may accompany it. In no event shall the publisher and the author be liable for any loss of profit or any other commercial damagecaused or alleged to have been caused directly or indirectly by this document.

Printed: March 2012 in UK

Patapsco has recently been acquired by Communications Systems, Inc. (CSI) and is now a part of Transition Networks, Inc., asubsidiary of CSI. The high-quality, reliable Transition Networks brand of products is now combined with the world classportfolio of telecommunications and data communications products from Patapsco Communications.

You can be assured that the same quality and support from both organizations will continue. Please contact either TransitionNetworks or Patapsco Communications for sales, support and product information.

Patapsco CommunicationsThe Passfield Oak, Passfield, Near Liphook,HampshireGU30 7RL UK

Tel: +44 (0) 1428 752900Fax: +44 (0) 1428 752901Email: [email protected] Site: www.patapsco.co.uk

Transition Networks10900 Red Circle DriveMinnetonkaMN 55343 USA

Tel: 952- 941-7600 or 1-800-526-9267Fax: 952-941-2322Email: [email protected] Web Site: www.transition.com

MediaBand TDM-4 User Manual2


Table of Contents1. Transition Networks - Patapsco Range 4

2. Navigating this Manual 5

3. Product Overview 7

4. Safety 8

................................................................................................................................... 84.1 Safety Statements

................................................................................................................................... 114.2 Approvals

................................................................................................................................... 134.3 Environmental Concerns

5. Getting Started 14

................................................................................................................................... 145.1 In the Box

................................................................................................................................... 155.2 Rack Mounting Kit

................................................................................................................................... 165.3 Connections and Cabling

................................................................................................................................... 175.4 Cable Spec

................................................................................................................................... 175.5 Install ing DbManager

................................................................................................................................... 185.6 Using DbManager

................................................................................................................................... 195.7 Connecting via Terminal

................................................................................................................................... 215.8 Connecting via IP

6. Device Window 24

................................................................................................................................... 246.1 Front Panel - LEDs

7. Configuration 25

................................................................................................................................... 267.1 Name and Management Settings

................................................................................................................................... 277.2 Ports and Clocking

................................................................................................................................... 287.3 Util i ties

................................................................................................................................................................................ 29Info 7.3.1

................................................................................................................................................................................ 31TDM Status 7.3.2

................................................................................................................................................................................ 31Rate Limiting Ports 7.3.3

................................................................................................................................................................................ 32Echo Test 7.3.4

................................................................................................................................................................................ 33Loopbacks 7.3.5

................................................................................................................................................................................ 34SFP 7.3.6

3Contents

3


8. Appendix 35

................................................................................................................................... 358.1 Event Messages

................................................................................................................................... 368.2 Boot Up Procedure

................................................................................................................................... 378.3 Glossary

................................................................................................................................... 448.4 FCC Affidavit



1. Transition Networks - Patapsco RangePatapsco MediaBand products allow the delivery of synchronous TDM and Serial data streams across asynchronous fibre or copperlinks. MediaBand will packetize traffic for transport across the IP link and transparently depacketize it at a remote site. The traffic willthen be played out to the data interfaces. MediaBand must be used as a two-ended solution, and an existing system can easily beexpanded with more MediaBand units to allow links to new sites and devices.

Please contact Transition Networks or Patapsco for any additional information on the product range, or for any other queriesregarding communications solutions:

Transition Networks10900 Red Circle Drive MinnetonkaMinnesota55343USA

Telephone: +1-952-941-7600 or: +1-800-526-9267 Fax: +1-952-941-2322 email: [email protected] [email protected] Web Site: www.transition.com

Patapsco CommunicationsThe Passfield OakPassfieldLiphookHampshireGU30 7RLUK

Telephone: +44 (0)1428 752900 Fax: +44 (0)1428 752901 email: [email protected] Web Site: www.patapsco.co.uk

mailto:[email protected]:[email protected]://www.transition.commailto:[email protected]://www.patapsco.co.uk

Navigating this Manual 5


2. Navigating this ManualThis manual is best viewed using the latest version of Adobe Reader, which is a free program. Click below to download the latestversion of the product from the Adobe Website.

Table of Contents

The Table of Contents starts on page 3. Click on a topic to navigate directly to the relevant page.

Bookmarks

Use the Bookmarks table on the left to navigate through the pages of the manual. Use the small + and - symbols to expand andcollapse the chapters of the manual.

Search

If there is a specific chapter of the manual which is required, it can be found using keywords. The keywords can then be entered intothe PDF search tool, and all occurrences of the keyword will be displayed.

Example: To find information on configuring clock sources, the keyword 'clock' can be used. Go to Edit Search (or press Ctrl+F) and enter Clock. Now Click Search and all the references to the keyword will bedisplayed below the search field. Click on any of the search results to go to the page immediately.

Printing

This manual can easily be printed if a hard copy is required for a presentation, or simply if a hard copy is preferred. To print themanual, open it with Adobe Reader and go to F ile P rint. Configure your printer and click P rint.

Notes on figures used in this manual

The following symbols will be used in this manual to highlight points of particular interest:

Info: A note about a subject which particular care should be taken with.

Example: An example scenario used to better describe an action or a situation.

Warning: A warning which must be read before taking any action. Ignoring the warning may potentially leadto a problem.

Arrow: This symbol indicates the next step, option or menu layer which needs to be accessed.

The Arrow symbol will be used often in this manual to quickly describe how to navigate to an option within the MediaBand TDM-4menu system.

http://get.adobe.com/reader/



For example, to navigate to this location:

The following figure would be used:

PKT 1 Util i ties P ing/Trace Session Trace Route

Other Formats

This manual can be provided in a variety of different help manual formats upon request. Please contact Patapsco for moreinformation.

Product Overv iew 7


3. Product OverviewA range of remotely manageable E1 T1 V.35 and X.21 media converters which transport serial interfaces across dark fibre plustransport Ethernet traffic at the same time.

Used in pairs; one at each end of the fibre, MediaBands are both locally and remotely manageable with good diagnostics and testfacilities - the MediaBand is a robust professional fibre converter.

Very flexible clock hierarchy which includes the ability to transport a provided clock across the fibre, to use its own very accurate(0.2ppm) internal clock or even to transport differently-clocked E1/T1s across the same fibre. As well as providing E1 T1 V.35 andX.21 media conversion over fibre, the MediaBand can use the same fibre to transport Ethernet traffic along-side the serial, so asingle fibre can be used more efficiently and for many purposes.

Can interface directly to carrier leased lines and ISDN services with the optional Telecoms Approvals feature.

MediaBands can be cascaded to deliver extra circuits and mix different interface types, using the fibre links very efficiently.

Datasheets are available for each MediaBand TDM-4 version, which give a wide range of information and specifications for thedevice, including application notes and examples. Please visit the main page for MediaBand TDM-4 or follow one of the links todatasheets below:

MediaBand-1 Single E1/T1

MediaBand-4 Quad E1/T1

MediaBand-VX Single X.21/V.35

MediaBand-32 multiple E1/T1

Patapsco's website has a detailed FAQ section which has a wealth of information on the product range, fault-finding and configuration.

http://www.patapsco.co.uk/Products/MediaBand/Mediaband_E1_Media_Converter_T1_to_Fibre_Fiber.htmlhttp://www.patapsco.co.uk/PDF-Products/MediaBand/T1_E1_Fibre_Fiber_Media_Converter_MediaBand_1.pdfhttp://www.patapsco.co.uk/PDF-Products/MediaBand/Media_Converter_4_T1_E1_Fibre_Fiber_Ethernet_MB4.pdfhttp://www.patapsco.co.uk/PDF-Products/MediaBand/E1_or_T1_and_V35_or_X21_Media_Converter_Fibre_Fiber.pdfhttp://www.patapsco.co.uk/PDF-Products/MediaBand/32_port_E1_Media_fibre_fiber_converter.pdfhttp://www.patapsco.co.uk/Top_Level/FAQs.html



4. SafetyPlease take a moment to observe the safety notices for this product and its accessories.

4.1. Safety Statements

Caution: Danger of electric shock. The device may be connected to hazardous voltages. Switch to power-off state before working on the device.

Caution: Danger of electrostatic discharge. Electronic components are sensitive to electrostatic dischargesthat might damage the device. Protect the device from electrostatic discharges by wearing an electrostaticwristband connected to a grounding terminal.

Caution: Interruption of data transmission. Data transmission will be interrupted during any work on thetransmission line and/or deactivation of the power supply. Make sure that that any work will only becarried out on inactive lines (without data transmission) or during quiet times to reduce interference to livesystems.

Caution: Danger of damage to devices or service interruption. Access by unauthorized third persons maycause damaged devices and/or interrupted services. Make sure that subracks are only installed in lockablelocations.

Caution: Danger of overvoltage. During faults, dangerous unprotected voltages may be present. Ensuresufficient grounding of the housings, i.e. by connecting the grounding contact.

Safety Warnings

Safety requirements are not fulfilled unless this equipment is connected to a wall socket outlet with a protective earth (PE) contact.

The power cord used to connect this equipment must be HAR marked and fitted with an IEC320 connector and an ASTA approvedmoulded plug.

There are no user serviceable parts in this equipment. All servicing and repair tasks must be undertaken by qualified servicepersonnel.

Isolation from mains power is achieved by the removal of the main power cord.

Telecommunications Safety

The safety status of ports conform to EN60950.

Connections to ports must be made such that the equipment continues to comply with the standard defined by EN60950 for SELV/TNV circuits after such connections have been made.

Safety 9


Any equipment which is connected to a Patapsco system should be separately approved for connection.

Port Safety Status

ISDN Network Ports - TNV

Term and LAN Ports - SELV

SFP Ports

Optical SFPs use a small laser to generate a fiber-optic signal. Keep the optical transmit and receive ports covered whenever a cableis not connected to the ports.

Warning: Because invisible laser radiation may be emitted from the aperture of the ports when no fiber cable isconnected, avoid exposure to laser radiation and do not stare into open apertures.

Inserting an SFP Module

1. Attach an ESD preventive wrist strap to yourself and a bare metal surface.2. Remove the SFP module from its protective packaging.3. Ensure that any latches on the module are closed.4. Align the SFP module in front of the slot opening on MediaBand TDM-4.5. Insert the module into the slot until it snaps into place.

Note: Disconnect all cables from an SFP module before inserting or removing it.

Note: Do not remove and insert an SFP module more than is necessary. Doing so may shorten the useful life ofthe SFP module.

Note: The orientation of the SFP module when inserting it into the device will vary depending on itsmanufacturer. SFP modules include a mechanism to safeguard against incorrect insertion and removal. Neverforce or twist the module when inserting it into the MediaBand TDM-4 device.

Inserting F iber-optic Cables

1. Remove the dust covers from the SFP module and the cables.2. Insert the fiber-optic cables into the module noting the polarity of the connections.



Removing an SFP Module

1. Attach an ESD preventive wrist strap to yourself and a bare metal surface.2. Remove all cables from the SFP module.3. Insert the dust cover into the SFP module.4. Pull the handle down to unlock the module.5. Gently pull the module forward out of the socket.

Mains Connection (AC)

The power requirements for MediaBand TDM-4 are: 95VAC to 240VAC at 47-63Hz.

The Mains Plug should conform to: EL-302 to Nema 5-15P class 1 applications 10/15 A @ 125V 10A minimum >28AWG

The IEC Plug conforms to: El-701A to IEC320/C13 10A 250V rating.

The following rated mains cables must be used in the regions stated:

Safety 11


Region Standard Rated Current (Amps) Rated Voltage (Volts) Application

Europe CEE(7) VII 10 250 Class 1 Appliances

United Kingdom BS1363A 13 250 Class 1 Appliances

USA/Canada 5-15P 10 125 Class 1 Appliances

Australia AS 3112 10 250 Class 1 Appliances

South Africa BS546 10 250 Class 1 Appliances

International IEC 320/C13-C15 10 125/250 Class 1 Appliances

DC Connection

Unit may be fitted with a DC power inlet. The DC voltage connected should be in the range 36-70VDC. Typically 400mA @ 48VDC.

TDM Connections

TDM cables used should meet the following specifications:

24AWG 0.2mm/7 stranded bare copper 3 or 4 pairs dependent

Shielded or Non-Shielded with moulded US plug 8P8C gold plated 3U

European Deviations

S (FI, NO, SE) CLASS 1 PLUGGABLE EQUIPMENT TYPE A

Intended for connection to other equipment or a network shall, if safety relies on connection to protective earth or if surge suppressorsare connected between the network terminals and accessible parts, have a marking stating that the equipment must be connected toan earthed mains socket-outlet.

The marking text in the applicable countries shall be as follows:FI: "Laite on liitett soujamaadoitus-koskettimilla varustettuun pistorasiaan"NO: "Apparaten m tilkoples jordat stikkontakt"SE: "Apparaten skall anslutas till jordat uttag"

4.2. Approvals

All approvals are pending. Patapsco can provide approvals for MediaBand TDM-4 units' connection to carrier networks on request.These approvals can cover ETSI, ANSI and Scandinavian circuit connection and isolation. Please contact Patapsco for moreinformation.

Safety

This product meets EN60950-1 and carries the mark.

EMC

Europe and rest of the world where applicable covered by harmonisation:



Country Standards

Europe EN 55022, EN 55024

Australia and New Zealand AS/NZ CISPR 22

USA FCC pt 15b

WARNING: This is a class A product. In a domestic environment this product may cause radio interference inwhich case the user may be required to take adequate measures.

Telecoms

Country StandardsEurope ETSI - TBR3 Basic, Primary Rate Layer 1/2/3, TBR4Australia S016 Leased Line connectivity, S038 Primary Rate

requirements over TBR4New Zealand News Letter 125 testing for connectivityUSA TIA-968-ACanada CS-03

Safety 13


4.3. Environmental Concerns

Patapsco products comply to the Waste from Electrical and Electronic Equipment (WEEE) Directive which states that producers ofelectronic/electrical products must take responsibility for those products at the end of their life. The user may dispose of their wasteequipment by handing it over to a designated collection point for the recycling of waste electrical and electronic equipment, or byreturning it to Patapsco. The separate collection and recycling of waste equipment at the time of disposal will help to conservenatural resources and ensure that it is recycled in a manner that protects human health and the environment.

Please contact Patapsco for information on returning a product at the end of its life.



5. Getting StartedFollow these steps to connect up and install the unit, ready for configuration.

5.1. In the Box

All units are supplied with the following:

Terminal cable

This is used for configuration of the units when IP connection is not possible or where the default IP address is not usable. Please see Connecting via IP for details on IP management.

DbManager Installation Disk

This CD allows management software to be installed onto a PC for configuration and monitoring of the device. Please see InstallingDbManager for more information.

The following accessories are optional:

TDM Cables

TDM Port cable packs can be ordered with units as required.

LAN Network Cables

Cables to connect from a LAN to MediaBand TDM-4 can be ordered with MediaBand TDM-4 units as required.

SFP Module

SFP modules may be used with MediaBand TDM-4. Finisar SFP products are recommended for use with MediaBand TDM-4.

Rack Mounting Kit

Units can be supplied with brackets and accessories to enable the unit to be mounted in a 19" rack.

If any additional accessories are required, please contact Patapsco.

Getting Started 15


5.2. Rack Mounting Kit

All Patapsco units can be mounted in a standard 19" rack housing. To allow units to fit into a 19" rack, a Rack Mounting Kit must bepurchased for the unit(s). There are various rack mounting options depending on the size of the unit ordered. The following guidewill explain how to use the Rack Mounting Kit with Patapsco units.

2 x L -Bracket s

4 x Rack Mount Washers

4 x Rack Mount Cage Nuts

4 x Rack Mount Screws

4 x Long Patapsco Case Screws

[1] Remove the four short screws near the front or rear panel on the left and right hand sides of the Patapsco unit. The unit can bemounted with the front panel facing forward or with the ports facing forward as required.

[2] Fit one of the L-Brackets to the side of the unit. The four small fixing holes allow the unit to protrude forward or sit further backdepending on the desired position of the unit. The bracket may also face forwards or backwards depending on the desired position ofthe unit.

[3] Fix the L-Bracket in place using the Long Patapsco case screws.

[4] Fix the second L-Bracket to the other side of the case in the same way.

[5] Put the Rack Mount screws through the Rack Mount washers.

[6] Offer the unit up to the rack and fix it in place using the Rack Mount Screws and Rack Mount cage nuts.



5.3. Connections and Cabling

Please connect the cables to the MediaBand TDM-4 in the order below.

TDM Connections

MediaBand TDM-4 may be fitted with up to four RJ45 presentation TDM ports. Make the connection between the TDM access pointsor devices and the TDM ports on the MediaBand TDM-4 rear panel.

NOTE: Only shielded, approved cables should be used for these connections.

DbMgr Terminal Port

There are two methods of management access to Patapsco devices. The terminal port allows the unit to be managed via a PC COMport. Connect the terminal cable between the terminal port on MediaBand TDM-4 and a spare PC COM port.

LAN Port Connections

MediaBand TDM-4 has a LAN port for management connections via a company network. The port should be connected to arouter, hub or ethernet switch using a straight-through CAT5e cable.

SFP Ports

The SFP interfaces can be fitted with a range of modules for interfacing with different types of equipment. Please ensure thatthe cables and modules used with the SFP cages are screened and of a high quality. Please see Safety Statements formore information on the SFP connections.

Power Cables

Connect the Mains lead directly to the mains power socket. The cord must be HAR marked and fitted with an IEC320 connector andan ASTA approved moulded plug. If the unit is fitted with a DC power supply, use the screw terminals to connect the DC source. Thesource should be a negative DC feed, so the 0V (positive) lead should connect to the 0V terminal on MediaBand TDM-4, while the -48V (negative) lead connects to the -48VDC terminal.

Power cords are not supplied with Patapsco equipment. Please contact Patapsco if power cords are required.

Please contact Patapsco with any additional cable requirements.

Please note: Only MediaBand TDM-4's dual Power Supply Units are hot-swappable (can be removed andreconnected while the unit is powered on). All other cards should not be removed until the unit is powered off.Please seek guidance from Patapsco before removing cards from MediaBand TDM-4.

Getting Started 17


5.4. Cable Spec

Specs for cables used with all Patapsco products are shown. The polarity of all connections is written from the point of view of acable connecting to the Patapsco unit.

Double-click on the cable names below to open the spec for each cable. The colour of the text corresponds to the colour suppliedby Patapsco.

Controller

Ethernet

Ethernet Crossover

TDM

TDM Crossover

RJ45 - BNC

5.5. Installing DbManager

Note: If you have an older DbManager installation on the management PC already, it is possible to upgrade tothe version of DbManager on the CD. A batch file on the CD can be used to do this automatically provided theapplication is installed in the default location (C:\Program Files\Patapsco\DbMgr). Please see the Upgradefolder on the installation disk for details. Upgrading to the latest version of DbManager is always recommended.

Please follow these steps to install DbMgr:

1. Insert the DbMgr disk into your CD drive. The installation will start. Read the license agreement and click Next >

2. Fill out the Customer Information form. If the version of DbMgr purchased is a multi-user and/or multi-device version, therewill be a serial number on the case for the DbMgr disk. Enter the serial number.

Note: If there is no serial number on the case, the DbMgr is a Lite version. Please leave the Serial Number fieldblank.

3. Choose a location to install DbMgr to and continue the installation.

4. DbMgr is now installed and ready to use.

Patapsco Designs Ltd Cable Specification Document

Part Number SEE BELOW Description Controller Cable Date 4/10/2008 Application Generic Authorised By Gary Strawbridge Colour Green Identifier Cont/02 Identifier Cont/02 Connector Type RJ12 Connector Type DB9S

Pin Number Patapsco Signal Pin Number 2 TX (from Patapsco) 2 1 RX (to Patapsco) 3 3 GND 5

Cable - Controller.pdf


Part Number SEE BELOW Description Ethernet Cable Date 20/04/10 Application Generic Authorised By Pete Cairns Colour Green Identifier C/Ethernet Identifier C/Ethernet Connector Type RJ45 Connector Type RJ45

Pin Number Signal Pin Number 1 Tx+ (from Patapsco) 1 2 Tx- (from Patapsco) 2

3 Rx+ (to Patapsco) 3 6 Rx- (to Patapsco) 6

4 Not used 4 5 Not used 5 7 Not used 7 8 Not used 8

= Twisted Pair

Cable - Ethernet.pdf


Part Number SEE BELOW Description Ethernet Crossover Cable Date 20/04/10 Application Generic Authorised By Pete Cairns Identifier C/EthernetXover Identifier C/EthernetXover Connector Type RJ45 Connector Type RJ45

Pin Number Signal Pin Number 1 Tx+ (from Patapsco) 3 2 Tx- (from Patapsco) 6 3 Rx+ (to Patapsco) 1 6 Rx- (to Patapsco) 2 4 Not used 4 5 Not used 5 7 Not used 7 8 Not used 8

= Twisted Pair

Cable - Ethernet Crossover.pdf


Part Number SEE BELOW Description PRI/TDM Cable Date 22/9/99 Application Generic Authorised By Steve Thickett Colour Green Identifier C/ISDN/PRI Identifier C/ISDN/PRI Connector Type RJ45 Connector Type RJ45

Pin Number Signal Pin Number 1 RX+ (to Patapsco) 1 2 RX- (to Patapsco) 2 3 GND 3 4 TX+ (from Patapsco) 4 5 TX- (from Patapsco) 5 6 GND 6 7 - 7 8 - 8

= Twisted pair

Cable - PRI.pdf


Part Number SEE BELOW Description PRI/TDM Crossover Cable Date 22/9/99 Application Generic Authorised By Steve Thickett Colour Yellow Identifier C/ISDN/PRIXover Identifier C/ISDN/PRIXover Connector Type RJ45 Connector

Type RJ45

Pin Number Signal Pin Number 1 RX+ (to Patapsco) 4 2 RX- (to Patapsco) 5 3 GND 3 4 TX+ (from Patapsco) 1 5 TX- (from Patapsco) 2 6 GND 6 7 - 7 8 - 8

= Twisted pair

Cable - PRI Crossover.pdf


Part Number SEE BELOW Description RJ45-BNC Cable Date 20/04/10 Application Generic Authorised By Pete Cairns Identifier C/RJ45-BNC Identifier C/ RJ45-BNC Connector Type RJ45 Connector Type BNC

Pin Number Signal Pin Number 1 RX+ (to Patapsco) Red Centre 2 RX- (to Patapsco) Case 3 GND Case 4 TX+ (from Patapsco) Green Centre 5 TX- (from Patapsco) Case 6 GND Case 7 - - 8 - -

= Twisted pair

Cable - RJ45-BNC.pdf



5.6. Using DbManager

This section will explain some of the principles of using DbManager with Patapsco devices.

Five Windows

DbManager is based around five windows which display information about the devices which are being monitored. These windowedcan be customized and arranged for a clear overview of events on an active system. Use the mouse to drag and resize the windows,or use the Window menu to automatically arrange the windows in a Cascade, Horizontal or Vertical tiles. The layout will be savedwhen exiting DbMgr.

Drag and resi ze the wi ndows to create a custom l ayout , or use the Window menu

Getting Started 19


The windows are used for the following:

Map The Map window shows a 4 layered, tree-structured map of a system. Each node on the upper layersrepresents a section of the network, while Nodes on the lowers layer represent individual Patapscodevices. With the IP addresses configured for each Node and Device, a large network of devices can bemonitored. Links can be configured between the nodes to represent the Links between units. The links arethen monitored for events. Multi-layer network topology can be represented using this window.

Connected to Dev ice This window is only visible once a management connection is started with an individual Patapsco devicefrom the lowest Map layer. This window shows the front and rear panels of the unit, which are used tomonitor the LED status of the device and access its configuration settings. The LED states will change inreal time.

Note: DbManager Lite only allows a single Node to be configured for use. Please contact Patapsco if multipleNodes are required.

OutstandingEvents

Outstanding events are events which require resolution, such as ports being disconnected. These eventswill stay in the Outstanding Events window until they are resolved; for example when the port isreconnected.

Event History The Event History records all events which are received from the devices.

Terminal The Terminal window shows the communications between the device and DbMgr in their raw state. Thiswindow is sometimes used for debugging systems by Patapsco engineers and their agents.

Configuring Devices

All device configuration is made from the Connected to Device window. Once changes have been made, theymust be uploaded to the device using the File Upload command. The Upload command loads changes fromDbMgr to a device, while the Download command does the opposite. A download is actioned upon connectingto a device.

Full DbManager Manual

The full user manual for DbManager explains all of the features and settings within the application. Please find the DbManager UserManual in the Documents & Manuals folder on the DbManager installation disk, or follow this link:

5.7. Connecting via Terminal

After connecting the terminal cable between the MediaBand TDM-4 and the PC, a management connection can be made. Pleasefollow these steps to connect to the unit.

[1] Go to View P roperties Terminal and select the Serial option. Set the Rate to 19200 and select the COM port whichthe terminal cable is connected to. DbMgr will show an error message if it cannot gain exclusive access to the COM port specified.

If the PC in use has any other applications running which use the PC COM ports, they may need to be closed


DbManager User Manual V2.2

All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage and retrievalsystems - without the written permission of the publisher.Products that are referred to in this document may be either trademarks and/or registered trademarks of the respective owners. The publisher and the author make no claim to these trademarks.

While every precaution has been taken in the preparation of this document, the publisher and the author assume no responsibility for errors or omissions, or for damages resulting from the use of informationcontained in this document or from the use of programs and source code that may accompany it. In no event shall the publisher and the author be liable for any loss of profit or any other commercial damagecaused or alleged to have been caused directly or indirectly by this document.

Printed: March 2012 in UK

Patapsco has recently been acquired by Communications Systems, Inc. (CSI) and is now a part of Transition Networks, Inc., asubsidiary of CSI. The high-quality, reliable Transition Networks brand of products is now combined with the world classportfolio of telecommunications and data communications products from Patapsco Communications.

You can be assured that the same quality and support from both organizations will continue. Please contact either TransitionNetworks or Patapsco Communications for sales, support and product information.

Patapsco CommunicationsThe Passfield Oak, Passfield, Near Liphook,HampshireGU30 7RL UK

Tel: +44 (0) 1428 752900Fax: +44 (0) 1428 752901Email: [email protected] Site: www.patapsco.co.uk

Transition Networks10900 Red Circle DriveMinnetonkaMN 55343 USA

Tel: 952- 941-7600 or 1-800-526-9267Fax: 952-941-2322Email: [email protected] Web Site: www.transition.com

DbManager User Manual2


Table of Contents1. Introduction 3

2. Hardware Requirements 4

3. Installing DbManager 5

4. Using DbManager 6

5. Map Window 8

................................................................................................................................... 95.1 Layers

................................................................................................................................... 115.2 Nodes

................................................................................................................................... 125.3 Links

6. Configuring Devices 15

7. Event History 16

8. Outstanding Events 19

9. CSV Files 20

10. Terminal 21

11. Users 22

12. Master/Slave Installations 23

13. Security Pack 25

14. SNMP Traps and Alarms 27

Introduction 3


1. Introduction

DbManager is a software application which allows configuration and monitoring of Patapsco devices. The basic version ofDbManager is called DbManager Lite, and is provided free with all Patapsco devices. Advanced versions of DbManager allowmonitoring and easy connection to groups of Patapsco units and the interlinks between them. Multiple PC workstations can beconfigured to operate as a Master/Slave system with synchronised event logging and reporting, and password protected useraccounts can be created and configured with four different operator levels which allow different levels of access to features ofDbManager and Patapsco devices.

Event logging is carried out in real-time by two event recording windows. Events can have comments tagged onto them by a user,allowing for simple trouble-ticketing. All events and comments are also logged to a data file on each PC in the system as apermanent record of system events.

Please contact Transition Networks or Patapsco for more information on DbManager versions.

Lite or Full Mode

DbManager can be used in two different modes - Lite and Full. The Lite version is designed as an installation/diagnostic tool, andhas everything required to install, configure and manage Patapsco devices. The Full version has options to access many morefeatures, including a multi-layer map of devices within a system showing the physical topography of a network of devices.DbManager will monitor all devices and collect events from them. Each device is allocated a node which represents that device andis used to show events relating the the device and initiate a management connection with it.

Please click this symbol to open a document showing the differences between Lite and Full DbManager:

DbManager Comparison Chart

Patapsco Communications, Passfield Oak, Passfield, Near Liphook, Hampshire, GU30 7RL England

Tel: +44 (0) 1 428 752900 Fax: +44 (0) 1 428 [email protected] www.patapsco.co.uk

Feature DbManager Lite Full DbManager

Network-wide visibility all nodes/devices and status Visibility of all links and their status Optional support for multiple work-stations Single node/device visibility/status Connect via COM port (auto-speed) Connect via IP Connect via ISDN management (specific products) Configure multiple device IP addresses Starter/Expert configuration modes Remote device software update Find Node option Find Link option View captured trace files Audible alarm settings Configure passwords for devices All Alarms/Events written to hard drive in real-time CSV format Simultaneous software updates to multiple devices Automatic polling to check unit status IP and DTE interface loops (PacketBand product range) Alarms on jitter buffer and packet loss Secure Management options 4 Level operator password access Device events displayed in node/link colours Find Node option in Event List Index column in Event List DTE and LL software loops (DataBand product range) ISDN Call Status display Sort Events by field type PC System Time displayed with Events Add operator comments (with time stamp) to Events Secure global deletion of system Events SNMP Traps and Alarms option Map window displaying customer name DbManager Demo modes

All details subject to change without notification E&OE Patapsco Designs Ltd 2008 and PacketBand is a registered Trademark of Patapsco Designs Ltd. Patapsco reserve the right to change any specification without notice. V1.2

- 1/1 -

DBManager_vs_DbLite_Features.pdf



2. Hardware RequirementsDbManager requires a windows operating system in order to be installed. If DbManager is being used to manage a single device,please see the Slave DbManager or DbManager Lite requirements. If multiple devices are to be managed, and/or multiple PCs are tobe used in a Master/Slave system, please see the Master DbManager PC requirements.

Slave DbManager or DbManager Lite PC Master DbManager PC

Minimum Specification: 500 MHz Processor256 MB Memory200 MB space on Hard DiskWindows 98 Second Edition or later100BT Fast Ethernet Network CardCD-ROM Drive Recommended Specification: 1 GHz or greater Processor512 MB Memory or greater500 MB or more space on Hard DiskWindows 2000, XP, Vista, Win 2003 Server or Win 2008 Server100BT Fast Ethernet Network CardCD-ROM Drive

Minimum Specification:

1 GHz Processor512 MB Memory200 MB space on Hard DiskWindows 2000, XP, Vista, Win 2003 Server or Win 2008 Server100BT Fast Ethernet Network CardCD-ROM Drive

Recommended Specification:

2 GHz or greater Processor1 GB Memory or greater1 GB or more space on Hard DiskWindows 2000, XP, Vista, Win 2003 Server or Win 2008 Server1000BT Fast Ethernet Network CardCD-ROM Drive

Install ing DbManager 5


3. Installing DbManager

Note: If you have an older DbManager installation on the management PC already, it is possible to upgrade tothe version of DbManager on the CD. A batch file on the CD can be used to do this automatically provided theapplication is installed in the default location (C:\Program Files\Patapsco\DbMgr). Please see the Upgradefolder on the installation disk for details. Upgrading to the latest version of DbManager is always recommended.

Please follow these steps to install DbMgr:

1. Insert the DbMgr disk into your CD drive. The installation will start. Read the license agreement and click Next >

2. Fill out the Customer Information form. If the version of DbMgr purchased is a multi-user and/or multi-device version, therewill be a serial number on the case for the DbMgr disk. Enter the serial number. If there is no serial number on the case, the DbMgris a Lite version. Leave the Serial Number field blank.

3. Choose a location to install DbMgr to and continue the installation.

4. DbMgr is now installed and ready to use.



4. Using DbManagerThis section will explain some of the principles of using DbManager with Patapsco devices.

Five Windows

DbManager is based around five windows which display information about the devices which are being monitored. These windowedcan be customized and arranged for a clear overview of events on an active system. Use the mouse to drag and resize the windows,or use the Window menu to automatically arrange the windows in a Cascade, Horizontal or Vertical tiles. The layout will be savedwhen exiting DbMgr.

Drag and resi ze the wi ndows to create a custom l ayout , or use the Window menu

Using DbManager 7


The windows are used for the following:

Map The Map window shows a 4 layered, tree-structured map of a system. Each node on the upper layersrepresents a section of the network, while Nodes on the lowers layer represent individual Patapscodevices. With the IP addresses configured for each Node and Device, a large network of devices can bemonitored. Links can be configured between the nodes to represent the Logical Links between units. Thelinks are then monitored for events. Multi-layer network topology can be represented using this window.

Connected to Dev ice This window is only visible once a management connection is started with an individual Patapsco devicefrom the lowest Map layer. This window shows the front and rear panels of the unit, which are used tomonitor the LED status of the device and access its configuration settings. The LED states will change inreal time.

Note: DbManager Lite only allows a single Node to be configured for use. Please contact Patapsco if multipleNodes are required.

OutstandingEvents

Outstanding events are events which require resolution, such as ports being disconnected. These eventswill stay in the Outstanding Events window until they are resolved; for example when the port isreconnected.

Event History The Event History records all events which are received from the devices.

Terminal The Terminal window shows the communications between the device and DbMgr in their raw state. Thiswindow is sometimes used for debugging systems by Patapsco engineers and their agents.



5. Map WindowThe Map window can be used to create a large-scale visual map of all Patapsco devices in a system and links between devices. Thefirst three Layers show Nodes representing smaller sections of the whole network and Links between them, while the fourth (lowest)layer shows Nodes representing individual Patapsco Devices. Management connections are initiated by double-clicking on deviceNodes at the lowest Layer.

Map Window 9


5.1. Layers

DbManager has 4 map Layers, which represent different geographical locations, sites, and/or customers. An individual Layer withinthe map could be used to represent a geographical area, a particular customer or customer site, or any other locality within anetwork.

Example: The Layers below have been configured to represent the following areas of a network:

Layer 1: World. This Layer has Nodes representing different continents. Any intercontinental links are shownwith green lines between the Nodes. These could be IP (Logical) links, PRI, BRI or TDM services.

Layer 2: Europe. Double-clicking on the Europe Node takes us to the Europe Layer. Here each Noderepresents a network locality within a European country. Again, links between the countries areshown as green lines.

Layer 3: United Kingdom. Double-clicking on the United Kingdom Node opens the UK Layer, which showsNodes representing cities within the UK.

Layer 4: London. In this Layer each Node represents an individual Patapsco device. Double-clicking on a nodehere will start a management session with a particular unit.

Layer 1

Layer 1 i s con f i gured to show di f feren t con t i nen t s i n th i s case.

In tercon t i nen tal l i nks are shown between Nodes

Layer 2

Layer 2 shows coun t ri es wi th i n a con t i nen t , and l i nks goi ng to

any other part of the map



Layer 3

Note how l i nks to other Layers end i n

Layer 4

The Nodes on the f i nal Layer represen t i ndi v i dual Patapsco

dev i ces

Note: Each Layer of the Map window can be used to represent any subdivision of a network - the above layoutis provided only as an example.

Navigating Layers

When DbManager starts up, the top Layer (World in the example above) is displayed. To move down to lower layers, a user mustdouble-click on a Node. Repeat this process to move down the configured network Layers. To move back up the Layers, DbManagerhas browser buttons for navigation:

Up: Moves up by 1 Layer

Back: Back to the previous Layer

Refresh: Refreshes Nodes and Links with recent changes

Following Links

A convenient way to navigate around a configured network map is to follow the Links between Nodes. Double-clicking on a Link willtake the user to the Link's destination Layer.

Finding Nodes and Links

Map Window 11


As a network map grows in size, it can be difficult to locate Nodes and Links. DbManager has a built in tool to help quickly locatingNodes and Links. Go to Node on the menu bar and select F ind Node or F ind Link. Enter the Identifier of the Node or Link andclick on Search to find it. Alternatively, click List Dev ice Nodes to see all configured Nodes. Select a Node and click F ind. TheNetwork Map will go to the correct Layer and the Node or Link will flash red twice to identify itself.

5.2. Nodes

A Node represents a single Patapsco device. DbManager will connect to all available IP addresses upon start up using TCP and allevents reported from the devices will be logged by DbManager. Each node has an IP address, Identifier and Name associatedwith it. If the Identifier set in a Patapsco device's configuration matches the Identifier configured for it's Node in DbManager, theNode will change colour to indicate the status of Alarms relating to the device.

Nodes can be added to the map by right-clicking and selecting Add Node. Once a node is added, right-click it again and selectP roperties to configure the node for use.

Identifier

The Identifier is a unique name for the device. The node should be given the same Identifier as the Patapsco device which it willconnect to. When the Identifier of a device matches the node identifier the node will change colour when some Alarms, Warningsand Events are reported

Name

The Name of a device is used to add extra information about it. The name has no function other than to enter something memorableabout a device.



IP List

The IP list button accesses the list of device IP addresses configured in View Properties Terminal Device IPAddresses. Choosing one of these IP addresses sets which IP address the node will access when a managementconnection is initiated. Once an IP address is chosen, its number will be visible in the Node No. field.

ISDN/Can be used for Remote Access

These options are used with some Patapsco products to allow management connections to be made using ISDN calls. Please referto ISDN Management in the relevant product manuals for information on configuring ISDN Management.

5.3. Links

Once Nodes have been configured for each Patapsco device in the system, Links can be drawn between them to represent theconnections in use in the system. Links can pass between any two Nodes, and the Nodes can be located on different sections of thenetwork. If the Identifier of a Link on a Patapsco device matches the name of the Link configured on the Devices in World map,DbManager is able to identify the Link, and will change the colour of the Link when Alarms and Warnings are reported which relateto it.

The A larm 'No Data Recei ved f rom Remote' (Tx but no Rx) Tri ggers the l i nk goi ng bl ue

'Unresol ved & Inact i ve' (cannot see remote dev i ce/nearest Gateway) tu rns the L i nk red

Map Window 13


' L ogi cal L i nk Communi cat i ng ' i ndi cates the recovery of the L i nk, tu rn i ng the graph i c green

To add a Link, right-click on any Node and select Add Link.

The l i st shows al l con f i gured Nodes

Select a Node as a destination for the Link and click Select. A link will be created between the two Nodes. Right-click on the Linkand click P roperties to access the settings for it. Three options are available:

Identifier

This is used by Patapsco devices to associate the Link with a device. PacketBand units' Logical Links can be given an Identifier tomatch the Link, which enables the Link to change colour to represent its different states (Active, Half Duplex or Idle).

Identifier 2

As two devices share a Link, they may have different Identifiers configured to each other, both representing the same Link. This optionallows each device to use a different Identifier for the Link

Name



The Name of a Link is used to add extra information about it. The name has no function other than to enter something memorableabout a Link.

Note: Multiple links can be made between a pair of Nodes. To un-clutter the view of linked nodes, the LinkDraw Method can be changed to SGN Style. This option can be found in View Propert ies LinkDraw Method.

Configuring Dev ices 15


6. Configuring DevicesPatapsco devices which are to be managed all have configurable IP addresses. The IP addresses can be configured byaccessing the unit via the serial cable, the default IP address (192.168.0.1), or by asking Patapsco for pre-configuration ofunits. Once the IP addresses are set, DbManager can be configured to monitor the devices using their IP addresses.Please follow these steps to configure a list of IP addresses:

1. Go to View Properties Terminal Device IP Addresses and click Add.

2. Enter the IP Address and Identifier of the first device. Leave New IP Port set to 3001 (see note below).

3. Click OK and repeat this procedure to add more devices to the list

Note: The New IP Port option can be used to set a different TCP port to manage Patapsco devices with. AllPatapsco units use port 3001, but if a serial-to-IP Terminal Server is used, the server and DbManager can beconfigured to use an alternative port number.

Note: Unless a third-party Terminal Server device is in use, the IP Port option should always be set to 3001.

Warning: All device configuration is made from the Connected to Device window. Once changes have beenmade, they must be uploaded to the device using the File Upload command. The Upload commandloads changes from DbMgr to a device, while the Download command does the opposite. A download isactioned upon connecting to a device.



7. Event HistoryThis window displays a historical list of every Alarm, Warning, Event and Message reported to this DbMgr since startup. Events canbe sorted by certain columns (click on the Title button at the top of the column), and re-sorted into the original order of receipt (clickon Index). This is a useful tool to identify all messages associated with an individual Node or Link.

Events may be cleared individually by holding down the Ctrl key and clicking with the right hand mouse button. All the events can bedeleted by highlighting all the lines and repeating the above actions. Operator comments or messages, which have a security systemand audit trail, can be added to Events, and these are displayed on all workstations. This is a useful tool when running multipleworkstations, multiple offices and/or shifts.

The Event History window has the following columns:

Level

Each Device can be configured to report events of different levels.Level of event in terms of urgency:

Alarm

Warning

Event

Message

Note: Please see the Patapsco User Manuals for each product for details on the individual events reported byeach product.

Event History 17


Index

Sequential number allocated to each entry. This number provides a record of the original order in which the system received themessages and is used to reset the Events after they have been sorted using other parameters.

Date

Date of the events occurring. This is the date given by the Device reporting the Event. It is therefore important that the time and dateon remote Devices are configured correctly.

Time

Time of the event occurrence. This is the time generated from the Device reporting the Event.

Sys Time

Time the Event arrived at the DbMgr using the Master DbMgr clock. This is a backup should the remote units clock not be setcorrectly and allows the operator to see a close approximation of the order in which the Events took place.

Device Node ID

Identifier code for the devices reporting the alarm. This Node ID (Identifier) is configured into the remote Devices by the user and issent to the DbMgr with all Events. It is this Node ID which is used to change the status of the Icon representing this particular Device,for example to flash etc. in the Map Window. This is an important field which has to be configured accurately both in the Device and for the Node representing the Device in theMap window.

Interface ID

Identifier code for the interface within a Device. It is the name of the interface and could be the reference number or name given to aport by the user.This Interface ID is configured into the remote Devices by the user and is sent to the DbMgr with all Events. It is this Interface IDwhich is used to change the status of the link representing this particular circuit, to flash or change colour etc., in the Map Window.

Object

This field defines the module or port within the reporting Device that generated the message. For example, Port 10.1 would indicatethat Card 10 interface 1 on a system generated this message. Not all Events have an Object associated with them (for example, anin-coming management call).

Message

Brief description of the event.

User Comment

A comment may be added in this field by a User (right-click on the Event in the Level column). The Comment will be attached tothis Event and distributed to all other active workstations/users.

User Name



Name of user making comments. This is entered by the system from the Users log-in name.

DbMgr Id

Identification number of the DbMgr where the comment was added. Automatically entered by the system unless it is a singleworkstation version.

User Date

Date comment was added - automatically inserted by the system.

User Time

Time comment was added - automatically inserted by the system.

Outstanding Events 19


8. Outstanding EventsThis window displays a list of all outstanding (unresolved) events that occur or have occurred in the network. Most Events types arecleared automatically by the system once the issue is resolved. For example, a Port Disconnected message will be deleted from this

area when it receives the corresponding Port Connected message. Some Events do not have a corresponding message to clearthem, and these must be manually deleted. Events may be cleared individually by holding down the Ctrl key and clicking with theright hand mouse button. All the events can be deleted by highlighting all the lines and repeating the above actions.

Events may be cleared individually by holding down the Ctrl key and clicking with the right hand mouse button. All the events can bedeleted by highlighting all the lines and repeating the above action. When a user deletes an Event from the Outstanding Eventswindow a message is sent to the Master workstation which then automatically sends details of the event deletion to all other Slaveworkstations. As critical Events are corrected within the network, they are deleted from this Window.



9. CSV FilesAll event messages which are reported to DbManager are also logged in flat CSV (Comma Separated Value) files on themanagement PC. These can be opened with Notepad, Excel, and most data logging tools/applications.

DbManager will create a new event file on Mondays with the date stamp and the number 1 (e.g. EVT20072009-1.CSV). When thisfile reaches 1 million characters, a new file is generated with the number EVT20072009-2.CSV. The numbering can go up to amaximum of 65535, which should be more than enough files for one week of events. On the next Monday, a new file will be createdwith the new date and the numbering set back to 1 (EVT27072009-1.CSV).

When using Microsoft Excel to view the files, each column contains an event. The following table details the data contained in eachcolumn

Full DbManager

Column Data

A Message Type

B Date

C Time

D PC System Time

E Device Name

F Logical Link no/DB120 Card no

G Logical Link no/DB120 Port no

H Event Message

I DDI/Subnet Mask

J Sub Address/Gateway

K CLI

L Call Start Date

M Call Start Time

N Call Duration

O Input Port

P Output Port

Q Originator of Call

R Call Clearing Message

DbManager Lite

Column Data

A Message Type

B Date

C Time

D Device Name

E Logical Link no/DB120 Card no

F Logical Link no/DB120 Port no

G Event Message

H DDI/Subnet Mask

I Sub Address/Gateway

J CLI

K Call Start Date

L Call Start Time

M Call Duration

N Input Port

O Output Port

P Originator of Call

Q Call Clearing Message

Note: DbManager Lite does not show the PC System time in the Event messaging. Therefore after column C,the event messages reported in each column are offset by one in comparison to the Full DbManager Event log.This should be taken into account if configuring a system to use the recorded statistics files.

Please click on the symbol below to see an example of an Events file with column headings added:

Note: This file is best viewed using Microsoft Excel. Excel Viewer can be downloaded free from www.microsoft.com/downloads

http://www.microsoft.com/downloads

http://www.microsoft.com/downloads

all_evts Description

FULL DBMANAGER

Message TypeDateTimePC System TimeDevice NameLogical Link No/Db120 Card NoLogical Link No/Db120 Port NoEvent messageDDI/Subnet MaskSub Address/GatewayCLICall Start DateCall Start TimeCall DurationInput PortOutput PortOriginator of call endingCall Clearing message in any

WRN5-Aug-0510:59:1010:16:58Switch Liberator--Call Connect Pri 23.1 - 752953/:2089434044/ - to Bri 4.2

ALM5-Aug-0511:01:3110:16:58Switch Liberator--Call Ended75295320894340445-Aug-0510:59:1000:00:02:21I23.01O04.020Normal call clearing

EVT5-Aug-0511:01:4810:16:58Switch Liberator--Incoming call Pri 23.1 - Call Barred

ALM5-Aug-0511:01:4810:16:58Switch Liberator--Call Ended75290079465135895-Aug-0511:01:4800:00:00:00I23.01O00.2551

EVT5-Aug-0511:03:0510:16:58Switch Liberator--Incoming call Pri 23.1 - 752932/:7796008138/ - to Bri 1.1 using Profile 23 TO BRI 1 - 4 (6)

WRN5-Aug-0511:03:0910:16:58Switch Liberator--Call Connect Pri 23.1 - 752932/:7796008138/ - to Bri 1.1

EVT5-Aug-0511:04:2910:16:58Switch Liberator--Incoming call Pri 23.2 - Call Barred

ALM6-Oct-0910:17:0010:17:00ISDN PRI HUBLogical Link 116Port 116Logical Link Unresolved & Inactive

ALM31-Dec-8523:59:5923:59:59---Reboot 1b8107ff - Copyright Patapsco Designs Ltd 1994-2007 - Vb811

ALM31-Dec-8523:59:5923:59:59---PRI 21 Failed

ALM31-Dec-8523:59:5923:59:59---New static IP address 192.168.0.1subnet mask 255.255.0.0gateway 0.0.0.0

DBMANAGER LITE

Message TypeDateTimeDevice NameLogical Link No/Db120 Card NoLogical Link No/Db120 Port NoEvent messageDDI/Subnet MaskSub Address/GatewayCLICall Start DateCall Start TimeCall DurationInput PortOutput PortOriginator of call endingCall Clearing message in any

ALM6-Oct-0910:27:25ISDN PRI HUBLogical Link 115Port 115Logical Link Unresolved & Inactive

ALM6-Oct-0910:27:25ISDN PRI HUBLogical Link 116Port 116Logical Link Unresolved & Inactive

ALM31-Dec-8523:59:59---Reboot 1b8107ff - Copyright Patapsco Designs Ltd 1994-2007 - Vb811

ALM31-Dec-8523:59:59---PRI 21 Failed

ALM31-Dec-8523:59:59---New static IP address 192.168.0.1subnet mask 255.255.0.0gateway 0.0.0.0

ALM31-Dec-8523:59:59---ETHERNET PORT 1 Failed

ALM31-Dec-8523:59:59---ETHERNET PORT 2 Failed

EVT17-Nov-0911:30:10Switch Lib--Incoming call Pri 22.3 - 07896533170/:752958/ - to Pri 21.3 using Profile 2 (9)

EVT17-Nov-0911:30:17Switch Lib--Call Connect Pri 22.3 - 07896533170/:752958/ - to Pri 21.3

EVT17-Nov-0911:30:18Switch Lib--Call Ended208543897775292317-Nov-0911:28:5500:00:01:23I22.01O21.010Normal call clearing

EVT17-Nov-0911:30:25Switch Lib--Call Ended789653317075295817-Nov-0911:30:1700:00:00:08I22.03O21.031Normal call clearing

CSV Description.xls

Terminal 21


10. TerminalThe Terminal window shows all exchanges of information between DbManager and a Patapsco device. The only time the Terminalwindow should be used is when instructed by a Patapsco engineer. All useful information displayed in the Terminal is logged asevent messages and displayed in the Event windows.



11. UsersDbManager users can be assigned different access levels so that different users are allowed to access different features withinDbManager.

Super User

After starting DbManager, the program asks for a username and password, or the Super User password.

Note: If the DbManager installation does not require more than one user, and level access restriction is notrequired, the default Super User account can be used for all configuration and monitoring.

There is no default password for the Super User, so DbManager can be accessed for the first time by simply pressing OK. The SuperUser password can be changed as required. Select User from the menu bar and select Change Password. Leave CurrentPassword blank and enter your chosen password in both the New Password and Confirm New Password entry boxes. Press theOK button. Now the new password will have to be entered upon starting up DbManager.

Adding, Editing and Deleting User Access

Users of DbManager can be assigned individual levels of access to devices. The access levels are as follows:

Feature

AccessLevel

EventMonitoring

Connectionto dev ices

Configurationof dev ices

Configurationof network map

Add/Edit/Deleteall users

Super

1

2

3

4

Users can be added to DbManager by selecting the User menu item and selecting Create User. Only the Super User is able toadd, edit, delete and view the list of users.

Passwords

A logged-in user can change their own password via the User menu, but only the Super User can change the passwords of allusers.

Master/Slave Installations 23


12. Master/Slave InstallationsDbManager can be configured to manage a group of devices via multiple PCs. It is necessary to correctly set up one PC as theMaster and the others as Slaves, as otherwise conflicts will occur and management will be impossible. Please follow these steps toconfigure the Master PC.

Master Configuration

1. Find out the IP addresses of all PCs which are to be included in the system. If the management system is to cross IP networksegments, the settings of any routers in use must be taken into account. DbManager uses TCP port 100 for communicationbetween PCs. The IP addresses can be found by opening a Command prompt (Start Run cmd and press Return), enteringipconfig and pressing Return.

2. Start DbManager on the PC which is to be assigned as the Master and go to View P roperties Systems IP Address.

3. Enter the IP address of the Master PC (the PC being worked on).

4. Click Show DbMgr List.

5. Select the blue Master listing (M) and click Edit. Enter the IP address of the system as found in step 1.

6. Select the Slave listings (S) and enter the IP addresses of each Slave PC.

7. Click Exit, then OK and restart DbManager.

The Master PC will automatically send the Slave PC list as well as any Device IP addresses, Nodes and Links which are configured.The Slave PCs each need to be configured with the Master PCs IP address and their own address in order for this to happen:

Slave Configuration

1. Start DbManager on the PC which is to be assigned as a Slave and go to View P roperties Systems IP Address.

2. Enter the IP address of the PC.

3. Click Show DbMgr List.

4. Select the blue Master listing (M) and click Edit. Enter the IP address of the Master PC.

5. Select the Slave listings (S) and enter the IP addresses of the Slave PC (the PC being worked on). The other Slave listings can beleft blank.

6. Click Exit, then OK and restart DbManager.

Now when DbManager is started up on the Master PC, the message This DbManager is being configured as the master unit will beshown.

When DbManager is started up on a Slave PC, the message This DbManager is being configured as a slave unit will be shown,followed by Have now established link to master DbManager.

The slave PCs will be sent the full list of slave PC IP addresses by the master, and device IP addresses, Nodes and Links which areconfigured on any PC will be accessible from all other PCs in the system.



Events from the Patapsco devices are all sent to the Master PC using TCP port 3001. The Master PC relays these events to all of theSlave PCs. Similarly, when a management connection is started from a Slave PC, they connect to the devices via the Master PC.

Security Pack 25


13. Security PackPatapsco devices can be configured to use strong 128 bit AES encryption for security. The security system uses 3 security keys:

1. Call Signaling: Encryption of the ISDN information elements (dialed numbers etc) within the SIP call signaling messages sentbetween PacketBand units when a call is started (PacketBand ISDN/LanBand only).

2. Messaging: Encryption of all data sent from the Patapsco unit to DbManager and vice versa.

3. Authentication: An encrypted message sent from DbManager to the unit when initially connecting.

Set the keys

The keys must be set on each unit using the Terminal port to connect to a PC COM port. It is not possible to set the keys via an IPconnection. Also, the Identifier of each unit must match the identifiers set in DbMgr in order to connect to the units. To set the keys:

1. Connect to the first unit with DbMgr using a serial (COM port) connection.

2. Click the Terminal port and select Dev ice Settings.

3. Enter an Identifier for the unit. Please do not use the following characters: # > < ~

4. Click the Key Config button.

5. Enter the desired keys. The keys must be 64 characters in length and all hexadecimal (0123456789ABCDEF).

6. Click Update to load the keys to the unit.

7. Disconnect from the unit and repeat this process with the other boxes.

Note: The Call Signaling key must match between PacketBand ISDN/LanBand units in order for them tocommunicate.

DbManager must be configured to use the IP addresses, Identifiers and keys:

1. Go to View P roperties and tick the Secure DbMgr checkbox.

2. Go to the Terminal tab and click Dev ice IP Addresses and Add.

3. Enter The IP address and Identifier for the first device.

4. Click the Key Management button and enter the keys for the device.

5. Add the IP address, Identifier and Keys for each device.

6. Add a device node for each secure device by hovering the mouse over the Devices in World map and right-clicking. Select AddNode. Answer No to the DB120 question.

7. Right-click the node and select P roperties to add a Name and Identifier for the device. The name can be anything, but theIdentifier must match the Identifier configured in each device.

8. Click the IP List button to link the node with a devices IP address.



9. Click OK.

Now that the devices and DbMgr have the keys configured, the units are ready to be connected to by DbMgr. Close down DbMgrand save all the settings, then start up again before trying to connect.

Any connection attempt made with the wrong authentication keys will cause the Patapsco unit to lock for 30seconds, during which a management connection will not be possible. Further connection attempts will causethis timer to stack, so there could be a long wait before being able to log in. To unlock a unit, the timer mustexpire or the unit can be rebooted to get around it.

Please make sure that keys are configured accurately and are kept safe. There is no way to extract and view thekeys from an existing secure PacketBand; DbMgr may only configure new keys once connected. If the keys arelost due to misconfiguration, the only way to access a unit is locally via the terminal port.

Any other Patapsco devices which are not using encryption will not be affected by the secure option being set inDbMgr. However, the secure devices will not be able to inter-work with the non-encrypted units.

SNMP Traps and Alarms 27


14. SNMP Traps and AlarmsDbManager is able to send SNMP Traps and Alarms to a PC running SNMP monitoring software. SNMP functionality can bepurchased as an optional upgrade for any DbManager system. Tools for installing, configuring and testing SNMP can be found onthe DbManager installation disk. The following guide shows how to set up a SNMP reporting system.

Firstly, each PC in the system must have Microsoft Windows SNMP software installed. Click Start Control Panel Add orRemove P rograms Add/Remove Windows Components Management and Monitoring Tools (make sure thatyou do not select or clear, tick or untick its check box to change the existing selection), and then click Details. Select SimpleNetwork Management P rotocol OK. Windows start installing SNMP, and you may be prompted to insert a windowsinstallation disk to access the files required for SNMP.

Once SNMP is installed, the service must be enabled and configured on each PC:

SNMP Monitor PC DbManager PC

Go to Start Right-click on My Computer Manage Serv ices and Applications Serv ices SNMP Serv iceand right-click it. Select Start or Restart if the service is alreadyrunning. Do the same for SNMP Trap Serv ice. SNMP servicescan be configured to start automatically from this menu.

Go to Start Right-click on My Computer Manage Serv ices and Applications Serv ices SNMP Serv iceand double-click it. go to Traps and enter a community name(for example Patapsco), then click Add to List and thenAdd.. . . Enter the IP address of the SNMP monitor PC (forexample 10.1.1.107) and click Add. More IP addresses can beadded if required. Now right-click on SNMP Serv ice SelectStart or Restart if the service is already running. Do the samefor SNMP Trap Serv ice.SNMP services can be configured to start automatically from thismenu.

Now that one PC can monitor SNMP and one transmit, they can now be configured to receive and send SNMP messagesrespectively:



SNMP Monitor PC DbManager PC

Install the HP SNMP Browser from the DbManager installationdisk using the SETUP.EXE file, then start up the HP SNMP Browserfrom the installation. The default installation path is C:\snmp_apps. Click on Events F ilters, switch all filters offand click OK.

Install the Patapsco SNMP Agent from the DbManagerinstallation disk using the SETUP.EXE file. The application willstart automatically. Now start TRAPTEST.EXE, enter 1 in TrapOID and click Open DCTI.

Now click Send Trap(s) and SNMP messages should be reported to the SNMP Monitor PC. Now DbManager can be started onthe DbManager PC and SNMP enabled. Go to View P roperties SNMP Traps and tick the Enable button. The system isnow ready for SNMP reporting.

Cover

Table of Contents

Introduction

Hardware Requirements

Installing DbManager

Using DbManager

Map Window

Layers

Nodes

Links

Configuring Devices

Event History

Outstanding Events

CSV Files

Terminal

Users

Master/Slave Installations

Security Pack

SNMP Traps and Alarms

DbManager User Manual V2.2.pdf



down. If DbMgr still cannot gain exclusive access to the COM port, it may be necessary to reboot the PC. Thisis due to some applications not correctly hanging up COM port connections.

[2] Select the green Dev ices in World window and double click on the Device Node. At this point, the default login timeout of 30minutes is displayed. The login timer is a security feature to prevent multiple users from not being able to access a unit. Change thevalue if required. Entering a login time of 0 will make DbMgr never automatically log out the connection.

Double cl i ck to connect

[3] DbMgr will initialize a connection at 19200bps on the selected COM port. If the connection is successful, the Connected toDev ice window will appear.

A l l con f i gurat i on changes are made f rom th i s wi ndow. The port s di spl ayed may vary depending on model

Getting Started 21


[4] If DbMgr does not connect, it will cycle through the available port rates and try to connect. If no connection is made, pleasecheck that the cable is correctly connected and the COM port is accessible to DbMgr.

[5] Once the connection is established, the speed can be changed to speed up the upload and download time if required. Click onthe Terminal port on the rear panel display and select Dev ice Settings. Change the Serial Port Rate to the new desired speedand click OK. Now go to F ile Upload to load the change to the unit.

[6] When the progress bar reaches the end, there will be no upload confirmation message, as the connection speed of DbMgr isnow different to the connection speed of the unit. Close down the Connected to Device window and reconnect to the unit (see step[2] above). DbMgr will cycle the port rates until it finds the correct one.

Note: The upload and download time can also be increased by changing the Upload Method from Slow to Fastin DbMgr. Go to View Properties General to find this option.

5.8. Connecting via IP

MediaBand TDM-4 has default IP settings which allow a DbMgr IP management connection to be made straight out of the box. Thedefault settings are:

IP Address: 192.168.0.1Subnet Mask: 255.255.0.0

Please follow these steps to configure DbMgr for connection to the MediaBand TDM-4:

1. Go to View P roperties Terminal TCP/IP Dev ice IP Addresses. If the default IP address is already configuredin the list, exit this menu. If the default IP address is not shown, click Add and enter the IP address and an Identifier for it. ClickOK to the open windows and the IP address will be added to the list.

Note: The New IP Port option changes the TCP port which DbMgr uses for management traffic. This optionshould only be changed from the default setting of 3001 if using a third party terminal server for management.Patapsco units always use TCP port 3001 for management traffic.

2. Go to the Dev ices in World map. Hover the mouse cursor over the Device node and right-click. Now select P roperties IPList. Highlight the default IP address and click OK.

3. Select the green Dev ices in World window and double click on the Device Node. At this point, the default login timeout of 30minutes is displayed. The login timer is a security feature to prevent multiple users from not being able to access a unit. Changethe value if required. Entering a login time of 0 will make DbMgr never automatically log out the connection.

Double cl i ck to connect

4. DbMgr will initialize a IP connection to the MediaBand TDM-4. If the connection is successful, the Connected to Dev ice



window will appear.

A l l con f i gurat i on changes are made f rom th i s wi ndow. The port s di spl ayed may vary depending on model

5. If DbMgr does not connect, please try a ping test to see if the IP address is active. Go to Start Run.. . and type 'cmd'. PressReturn and the Command Prompt window will appear. Enter 'ping 192.168.0.1' and press Return. You will see replies if theIP address is active.

Getting Started 23


A pi ng test proves that the PC can see the MediaBand TDM-4' s I P address

6. Now try disconnecting the MediaBand TDM-4 and retrying the test. If you see replies, a different device is using the same IPaddress as the MediaBand TDM-4. Either connect to the unit via terminal to change the IP address or disconnect the other device.MediaBand TDM-4 can be connected directly to a PC using a normal CAT5e cable and run as a standalone system fordebugging.

Note: All Patapsco devices respond to ICMP, but some other ethernet devices do not.

7. Once connected, the IP address of the MediaBand TDM-4 can be changed as required. Go to Terminal Dev ice Settingsand enter the IP Address, Subnet Mask and Gateway as required. Click OK and go to F ile Upload to load the new IPaddress to the MediaBand TDM-4.

8. Observe the Event History window. An event message will be generated just before the MediaBand TDM-4 switches to the newIP address. Close down the Connected to Dev ice window and go back to step [1] to enter the new IP address for theMediaBand TDM-4.

The Even t H i story wi ndow shows the new IP address detai l s



6. Device WindowThe Device window or Connected to Device window shows the front and rear panels of the unit. The front panel shows the LED statusof the unit, which are updated in real time.

The rear panel shows the Terminal port, LAN portsand TDM ports. Click on a port to access the configuration options relevant to theport.

6.1. Front Panel - LEDs

The LEDs on the front panel display show the status of the ports. The table below describes what the port status lights indicate.

Port/LED LED On Off

TDM E1/T1 Ports 21-24

Upper LED Layer 1 and 2 established. Ready for operation No connection established

Lower LED Connections active on interface No connections active on interface

Link Status Upper LED Link transmitting Link not transmitting

Lower LED Link receiving Link not receiving

PKT Port FD LED Full Duplex Half Duplex

ACT LED Connected (flash when data sent/received) No connection detected

100 LED 100BT network detected 10BT network detected

1G LED 1000BT network detected No 1000BT network detected

SFP Port Tx LED Transmit line detected No transmit line detected

Rx LED Receive line detected No receive line detected

Pwr Power Supply is running No power connected

Run Flash once/sec - Ready for operationFlash fast - 4 times/sec - Ready, no config

Unit not operating

Configuration 25


7. ConfigurationThe Configuration screen opens as soon as the confirmation message is clicked after connecting to MediaBand TDM-4. All of thesettings for MediaBand TDM-4 can be found on this screen. The configuration screen can be accessed at any time by clicking on thespanner symbol:

Notes on configuring MediaBand TDM-4

Uploading

Changes to config can be made on each window and saved using the OK key when exiting each window. When happy with theconfiguration, it must be uploaded to MediaBand TDM-4 for the new settings to come into effect.

To upload, go to F ile Upload or press the Upload button on the config window

Sav ing F iles

Configuration files can be saved in order to backup settings or copy settings across to another unit. Once configuration has beenuploaded, go to F ile Save F ile and choose a location to save the file to.

Loading F iles

Once connected to a unit, an existing configuration file can be loaded to the device. Go to F ile Open F ile and navigate to thesaved file. Click Open. Now the file must be uploaded to MediaBand TDM-4. Go to F ile Upload and wait until the progressbar completes.

Warning: When loading existing configuration files to a unit, please ensure that the correct configuration filesare used for the unit type in use. MediaBand TDM-4 configuration files are not compatible with other Patapscoplatforms.

Settings missing?

If any of the windows or settings shown in this manual are missing, it is most likely because DbMgr is running in Starter mode ratherthan Expert. Starter does not show some of the more advanced options, as it is intended to show a scaled down version of theconfiguration options, while Expert shows all options.

There is a prompt on whether to run in Starter or Expert mode when DbMgr is started. The mode can be changed at any time bygoing to View P roperties Dev ice Configuring.



7.1. Name and Management Settings

The Name, This is Dev ice.. . identifier and Ethernet Management settings identify each MediaBand unit within a system, andenable LAN management from any PC connected to the system and running DbManager.

Device Name

Enter a unique name for the MediaBand TDM-4 unit. This name is used by DbMgr for reporting events. Having a unique DeviceName also makes for easier system debugging when looking at event logs and traces.

Enter any alphanumeric combination of up to 30 characters. Please do not use the following characters: > < ~ #

This is Device...

MediaBand units in a system are identified as A and B or A1 and B1. If a link only requires two MediaBand units, one unit shouldbe configured as A while the other is configured as B. If a second pair of MediaBand units are connected across the same link, theymust be configured as A1 and B1 to avoid conflicts between the two pairs.

Use A and B un l ess usi ng 4 MediaBands

Connected to Ethernet?

This option should only be enabled if MediaBand is to be managed over a company LAN or similar connection. Ticking the Connected to Ethernet box opens extra options for configuring IP details for the MediaBand.

IP

The IP address of the device must be unique within the scope of the local network, and is used as an identifier for a unit.Management traffic will be directed to and from this IP address by switches and other Patapsco devices within a system. If in anydoubt as to which IP address to use on a unit, please consult a network administrator.

Enter the IP address using number keys. The full-stop . key can be used as a separator for each octet.

Mask

The Subnet Mask is used to break up a network consisting of many devices into smaller networks. Each device will be part of aSubnet, and the Subnet Mask is used to determine how many devices may be part of that smaller network. If in any doubt as to whichSubnet Mask to use on a unit, please consult a network administrator.

Enter the Subnet Mask using number keys. The full-stop . key can be used as a separator for each octet.

Partner's IP Address

Configuration 27


When the Connected to Ethernet option is enabled, the IP address of the MediaBand at the opposite side of the point-to-pointlink must be entered.

Enter the IP address using number keys. The full-stop . key can be used as a separator for each octet.

Note: If ethernet management of the MediaBand is not required, there is no need to enter the IP details for thesystem. MediaBand will configure itself based on the A/B/A1/B1 setting configured in This is Device...

7.2. Ports and Clocking

MediaBand TDM-4 can support up to four E1/T1 ports. Each of the links between MediaBand units can be switched on and offindividually, and the clocking of the unit can be configured to dynamically switch between sources using a hierarchy table.

TDM Ports

E1 refers to the protocol used in most of the world which supports up to 32 channels (2.048Mbps). T1 is the PRI protocol used inNorth America and Japan. This protocol supports 24 channels plus 8 bits for framing (1.544Mbps). MediaBand TDM-4 must berebooted after changing Presentation Type and uploading.

Enabling T1 opens the Line Code option. Choose from B8ZS or AMI.

B8ZS - Bipolar with 8 Zeros Substitution - Point-to-point T-carrier line coding.AMI - Alternate Mark Inversion - Basic bipolar encoding.

75/120 Imp