ma334_a1

Technical Documentation

Copyright © 2002 Tellabs. All rights reserved.

Product family Tellabs® 6300 Managed Transport System

Product name Tellabs® 6300 Network Manager

Title Description of Management Application and Platform

Document Product DescriptionMA334 / Revision A1

Tellabs 6300 network manager Legal NoticesDescription of Management Application and Platform

Legal Notices

Copyright Statement This Tellabs manual is owned by Tellabs or its licensors and protected by U.S.and international copyright laws, conventions, and treaties. Your right to usethis manual is subject to limitations and restrictions imposed by applicable li-censes and copyright laws. Unauthorized reproduction, modification, distri-bution, display or other use of this manual may result in criminal and civilpenalties.

Trademark Notice The following trademarks and service marks are owned by Tellabs Opera-tions, Inc., or its affiliates in the United States and/or other countries: AUDIOPLUS®, CABLESPAN®, CEC-128™, DYNAMIC SIGNAL TRANSFER™,DXX®, DXX logo®, EC DUO®, ENHANCED AUDIO PLUS®, EX-PRESS/PATH®, FOCUS™, MARTIS®, MARTISDXX®, MARTIS logo®, MAR-TISDXX logo®, METROVANTAGE®, METROWATCH™, NETREACH®,NETWISE®, SCULPTURED SOUND™, TELLABS®, TELLABS and T sym-bol®, T symbol, TELLABS PROPARTNER™, TEL/MAP™, TEL/MOR®, THEWORLD COMMUNICATES THROUGH TELLABS™, TITAN®, VERITY™,YOUR NETWORKING PARTNER®.

Any other company or product names may be trademarks of their respectivecompanies.

2 MA334 • Rev. A1

Tellabs 6300 network manager Revision InformationDescription of Management Application and Platform

Revision Information

Revision history This document has changed as follows:

Rev. Date Description of Changes

A1 Nov. 30, 2002 First revision.

MA334 • Rev. A1 3

Tellabs 6300 network manager Revision InformationDescription of Management Application and Platform

4 MA334 • Rev. A1

Tellabs 6300 network manager ContentsDescription of Management Application and Platform

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Part 1 The Management Application

2 Description of Tellabs 6300 Manager . . . . . . . . . . . . . . . . . . . . . . 112.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.2 Representation of the Network in Tellabs 6300 Manager . . . . . . . . . 122.3 Indication and Presentation of Alarms . . . . . . . . . . . . . . . . . . . . . . . . 152.4 Viewing Timing in a Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.5 Management of Network Elements . . . . . . . . . . . . . . . . . . . . . . . . . . 192.6 Collection of Performance Data and Events . . . . . . . . . . . . . . . . . . . 222.7 Management of Network Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2.7.1 Network Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.7.2 Creating Trails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.7.3 Inspecting and Handling Trails . . . . . . . . . . . . . . . . . . . . . . . 292.7.4 Inspecting the Network Database . . . . . . . . . . . . . . . . . . . . . 352.7.5 Representing “Foreign” Equipment in the Network Model. . . 36

3 Tellabs 6300 Manager as a Structure of Licenses . . . . . . . . . . . 39

4 Connecting to Other Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Part 2 The Management Platform

5 The Platform of Tellabs 6300 Manager . . . . . . . . . . . . . . . . . . . . 455.1 The Main Structure of a Tellabs 6300 Manager System . . . . . . . . . . 455.2 The System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

5.2.1 Stand-Alone (Single-Server) Systems. . . . . . . . . . . . . . . . . . 465.2.2 Distributed (Multi-Server) Systems . . . . . . . . . . . . . . . . . . . . 475.2.3 Using Clusters to Improve Availability . . . . . . . . . . . . . . . . . . 485.2.4 Using Remote Standby Systems to Improve Availability . . . . 50

5.3 Configuration and Installation of the System . . . . . . . . . . . . . . . . . . . 515.4 System Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

5.4.1 Management of System Security. . . . . . . . . . . . . . . . . . . . . . 525.4.2 Default User Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

MA334 • Rev. A1 5

Tellabs 6300 network manager ContentsDescription of Management Application and Platform

6 MA334 • Rev. A1

Tellabs 6300 network manager 1 IntroductionDescription of Management Application and Platform

1 Introduction

Definition of a TMN A telecommunications management network (TMN) is a management net-work which is used to monitor and manage a telecommunications network;that is, monitoring and managing the equipment in the network as well as thetraffic in it. The TMN provides the various functions for managing the net-work as well as the actual communication with the equipment in the networkand with other TMNs.

A TMN can vary in complexity from a very simple connection between a man-agement system and a single piece of telecommunications equipment to acomplex network interconnecting many different types of management sys-tems and equipment. The TMN may provide management functions and offercommunications both between the management systems themselves, and be-tween management systems and the various parts of the telecommunicationsnetwork.

Tellabs 6300 manager The system architecture of Tellabs 6300 manager complies with the require-ments for a TMN architecture. It offers an open architecture with network el-ement management and network traffic management functionality, and it is afield-proven system for integrated management of SDH transmission net-works composed of network elements from multiple suppliers. On top of that,Tellabs 6300 manager offers open interfaces for interconnection to other TMNarchitectures to provide automated information processing.

• Management of end-to-end network traffic

• Management of individual network elements

• Management of the interconnecting data communications network

• Management of the management system itself.

The integration of these management functions with high availability optionsand security functions makes Tellabs 6300 manager a well suited solution foroverall management of transmission networks.

The platform Tellabs 6300 manager runs on a platform with the following configuration:

• Industry standard AlphaServer machines from HP used as servers.

• The Tru64 UNIX-based HP OpenView TeMIPTM software platform fromHP. TeMIP is an abbreviation of ‘Telecommunications Management Infor-mation Platform’.

• An Oracle SQL database.

The platform is delivered, installed and configured by Tellabs Denmark’s Sys-tems Integration department.

The communication between the management system and the telecommuni-cations equipment is handled by a data communications network (DCN).

MA334 • Rev. A1 7

Tellabs 6300 network manager 1 IntroductionDescription of Management Application and Platform

Advantages from the platform of Tellabs 6300 manager

The following items are just a selection of the advantages from the platform ofTellabs 6300 manager:

• Capacity for management of multi-vendor equipment

• A distributed, scalable computer network with efficient backup to ensureconstant availability

• Modular design for seamless migration

• Constant surveillance of not only the telecommunications network, butalso of the platform itself

• Interface to other management systems

• An easy-to-use graphical user interface.

These features, and others, are described in more detail in this document.

User workstations Tellabs 6300 manager is accessed from workstations with the following con-figuration:

• PCs used as clients

• Windows 2000TM software platform from Microsoft.

The workstations provide access to the graphical user interface described inthis document.

This document The focus of this document is to give you a general overview of the capabilitiesand potential of Tellabs 6300 manager as a complete SDH Management appli-cation. Therefore, to provide such an overview, the description is feature-by-feature rather than function-license by function-license (a brief introduction tothe function licenses is, though, given in ‘3 Tellabs 6300 Manager as a Struc-ture of Licenses’ on page 39).

The first part of the document describes how to use Tellabs 6300 manager fornetwork management, while the second part is a description of the platformused by Tellabs 6300 manager.

Further information The detailed information about the features of Tellabs 6300 manager is, ofcourse, to be found in the manuals accompanying the system.

We offer one set of manuals that are meant as a general introduction to the sys-tem (describing the general use of the system’s graphical user interface andthe procedures for alarm handling), and then, on top of that, the manuals de-scribing the main functionalities of the system individually (that is, one man-ual for management of a specific network element, one manual for traffic man-agement, and so on).

8 MA334 • Rev. A1

Tellabs 6300 network manager Part 1 The Management ApplicationDescription of Management Application and Platform

Part 1 The Management Application

• ‘2 Description of Tellabs 6300 Manager’ on page 11

• ‘3 Tellabs 6300 Manager as a Structure of Licenses’ on page 39

• ‘4 Connecting to Other Systems’ on page 41

MA334 • Rev. A1 9

Tellabs 6300 network manager Part 1 The Management ApplicationDescription of Management Application and Platform

10 MA334 • Rev. A1

Tellabs 6300 network manager 2 Description of Tellabs 6300 ManagerDescription of Management Application and Platform

2 Description of Tellabs 6300 Manager

Overview This chapter is meant to give you an idea of how Tellabs 6300 manager is usedfor managing telecommunications networks. We will, of course, focus mainlyon the special features of the system.

Part of the concept behind Tellabs 6300 manager is to provide you with aquick and easy overview of your network, with easy access to the relevantmanagement functions.

2.1 Introduction

The general features of the graphical user interface

The general features provided by the graphical user interface of Tellabs 6300manager are:

• A graphical representation of the network, with icons representing net-work elements and other objects.

• Use of a hierarchical map structure to split up the network representationin logical “groupings” (for example, grouping in geographical locations).In Tellabs 6300 manager, the maps are called domains and subdomains.

• Use of the mouse (point, click and drag) to navigate in the network, to ma-nipulate the displayed objects, to perform operations on the different ob-jects, etc.

Multiple users possible Several users can have access to Tellabs 6300 manager at the same time.

Single-server or multiple servers possible

A Tellabs 6300 manager system can be set up either as a single-server systemor as a distributed system with several servers (hosts) running the Tellabs6300 manager software. In a distributed system each host is responsible formanaging a specific group of network elements.

Such distribution makes the Tellabs 6300 manager system very scalable, asnew hosts can simply be added.

Command line interface also available

In addition to the graphical user interface described in this chapter, Tellabs6300 manager also offers you a text-based command line interface. This can beused to combine a series of manual operations into one compound operation.

MA334 • Rev. A1 11


2.2 Representation of the Network in Tellabs 6300 Manager

Showing the network structure

In Tellabs 6300 manager, the network is visualised with icons representingnetwork elements, manholes etc. and with lines representing the cables be-tween them. The network can be organised in a hierarchy of domains, witheach domain showing a specific part or level of the network.

A network element can be shown in several domains at the same time. Thisallows you to create some domains showing the network structure and otherdomains showing, for example, groups of network element types.

Navigating in the domain hierarchy

One of the special features of Tellabs 6300 manager is a domain browser,which shows the domain hierarchy as a tree structure. This makes it easy tonavigate between the domains.

12 MA334 • Rev. A1


Setting up the network model

Tellabs 6300 manager contains a network editor which is designed to make iteasy for you to set up the traffic model of your network. The network editoronly requires the creation of one ‘level’ and then automatically generates therepresentations of all relevant network levels from that one.

The work environment for using the network editor is provided by the Net-work Editor window. This window contains all the necessary tools for creat-ing a network model.

‘Working in the network editor’ on page 14 gives a brief overview of how touse the network editor.

MA334 • Rev. A1 13


Working in the network editor

The tree structures in the Network Editor window provide you with those net-work objects that can be placed in the domain map.

Actions

1. Create the network object in the appropriate tree.

2. Transfer the network object to the domain map.

3. Open the network object for further configuration (for example, to set up the matrix connections representing fibre interconnections in a manhole).

14 MA334 • Rev. A1


2.3 Indication and Presentation of Alarms

Indicating alarms When an alarm is received from a network element, a new alarm informationline appears in the alarm list in the Alarm Handling window and the icon rep-resenting the network element in TeMIP’s Iconic Map changes color to indi-cate the appearance of an alarm. The alarm indication color is determined bythe severity level of the alarm. The change of color happens in every mapwhere the network element is shown.

Similarly, if an alarm affects traffic in the network, Tellabs 6300 manager cangenerate alarms for affected network level entities such as end-to-end connec-tions (trails), and the alarm is indicated by a change of color of the trail namein a list of trails. This particular function is called trail surveillance (see ‘Trailsurveillance’ on page 32).

The alarm function presents the alarm information in fields according to thestandard ITU-T OSI alarm_Record (X.721), and it implements the ITU-T X.733and ITU-T X.735 standards.

Information about a new alarm

The detailed information for each new alarm includes the probable cause ofthe alarm, the name of the object that generated the alarm, the identity of theoperator who has acknowledged the alarm (when the alarm has been ac-knowledged), when the alarm was issued, and when it was received by Tel-labs 6300 manager.

You can open an extra window with the details of one specific alarm by eitherdouble-clicking on the alarm or by selecting the alarm and pressing the ‘FullInformation’ button.

MA334 • Rev. A1 15


Trails affected by alarms from network elements

When a network element alarm appears, you can get direct information aboutwhich network traffic trails, if any, are affected by the specific alarm. This isdone via the pop-up menu for the relevant alarm line.

The figure shows how information about the trails affected by a specific alarmis displayed in the Find Trail window.

Filtering of alarms The TeMIP alarm handling used by Tellabs 6300 manager splits up alarmmonitoring into various operational areas (that is, monitoring of alarms fromdifferent areas of the network, from different element types etc.). This is doneby using special objects called operation contexts, where each operation con-text is assigned to a specific domain, and will therefore collect all alarms fromthat domain and all of its subdomains. When you set up the alarm handlingfunction, you specify which operation contexts to receive alarms from.

On top of that, you can create special filters for the presentation of alarms inthe alarm window and/or have Tellabs Denmark’s Systems Integration set upspecial low-level event filters.

Filtering criteria The following alarm filtering criteria are available in the alarm window:

• Alarm type

• Problem status

• Perceived severity

• Probable cause

• State

• Target entities

• Managed object

• Operation context

• Domain

16 MA334 • Rev. A1


• Security alarm cause

• Specific problem

• Before time

• After time

• Clearance report flag

• Correlated notification information

• Operator note

• Additional text

Saving alarm information All alarms are automatically stored in an alarm log. Each operation contexthas its own alarm log, in which you can search for specific alarms.

From the alarm log, the alarms can be archived in an SQL database fromwhich they can later be retrieved for further analysis.

MA334 • Rev. A1 17


2.4 Viewing Timing in a Network

The information shown The timing view of Tellabs 6300 manager provides a graphical view of theclock distribution and synchronization between network elements in the net-work. The timing view shows the following features:

• The active and alternative clock sources (SDH, PDH or external)

• The port number, quality and priority level of each timing source.

It can be used to discover timing loops and to improve the topology of the net-work.

Timing view Since the timing information is obtained from the MS overhead, the timingview is shown in the network representation of the MS layer in the NetworkManagement window. As illustrated in the figure below, the icons and linesordinarily used in network view are replaced by special icons and arrows, in-dicating the clock sources.

18 MA334 • Rev. A1


2.5 Management of Network Elements

Inspecting and managing network element configuration

The configuration of a network element (that is, the actual equipment installedin the physical network element), can be managed in an equipment view.

The equipment view is a graphic representation of the network element:showing the type and position of the modules in the network element, withalarm coloring. From this view, you can commission network elements, addnew modules, configure modules, look at alarms etc..

MA334 • Rev. A1 19


Setting up a new cross connection

The traffic view of the network element allows you to easily operate on the ex-isting cross connections and set up new cross connections. To set up a newcross connection, you use the mouse and simply select one of the connectionpoints, activate the pop-up menu, and then draw a line representing the crossconnection to the other connection point.

Description Illustration

1. Select the connection point and open the pop-up menu to select the type of connection.

2. A red line is attached to the mouse, starting in the selected connection point.

3. Drag the line to the other conenction point. The line changes color to green if con-nection is possible.

4. Click with the mouse to verify the connection. The connec-tion is created.

20 MA334 • Rev. A1


Configuring synchronization

The graphical representation of a network element’s synchronization architec-ture allows you to easily access all configuration aspects and operations ofsynchronization.

Note: The synchronization of the whole network can be inspected in the spe-cial timing view, as described in ‘2.4 Viewing Timing in a Network’ onpage 18.

From the Synchronization window you can synchronize the internal clockgenerator of the network element with an external stable and reliable synchro-nization source, and you can configure an external clock output from the net-work element, which can be used as a reference source for external equipment.

Element management functions

Other available element management functions are:

• Setup of data communication network (DCN)

• Performance monitoring of network element termination points

• Management of embedded software

• Management of network element backup

• Management of optical ports

• Management of termination points.

MA334 • Rev. A1 21


2.6 Collection of Performance Data and Events

Collecting performance data

All kinds of performance data can be collected (standard SDH performancecounters supported in the managed SDH network elements as well as GFPmapping data for Gigabit Ethernet cards). The performance data is stored in astandard SQL database and is presented in report form by a performance re-port generator.

22 MA334 • Rev. A1


Operations in performance data monitoring

The following operations are involved in monitoring of performance data:

• Starting and stopping the collection of performance data for network ele-ments or other monitored objects.

• Automatic collection and storage of performance counters in the perfor-mance database.

• Generating performance data reports based on the performance data. 15minute and 24 hour reports are available.

• Generating performance collection status reports that show all the activemonitored objects.

The performance data can be correlated from the network elements to thetrails. The performance management reports are generated per network ele-ment or per trail. It is, however, also possible to export the data in comma-sep-arated files and generate other types of reports.

Monitoring trail segments non-intrusively

In addition to the ordinary end-to-end trail monitoring, it is possible to mon-itor a trail segment without terminating the trail. This kind of "listen-only"monitoring is called non-intrusive monitoring and allows you to monitor theincoming and outgoing data flows in the segment separately.

Non-intrusive monitoring is, for example, useful when it is necessary to mon-itor a specific customer’s segment of the network.

Collecting event data Event logging can be used to record the events for a domain representing theentire network or a selected portion of the network. The events are placed inevent logs where you can analyse and manage the individual records (wheth-er you want to use only a single event log or multiple is up to you).

It is possible to search for specific event records, using such search criteria asmanaged object, notification identifier, log record class etc.

The event logging can also be suspended for a specific time interval and thenlater resumed.

Event logging implements the ITU-T X.734 Event Management Function andthe ITU-T X.735 Log Control Function.

The managed object classes (log and eventLogRecord) are ITU-T X.721 com-pliant.

2.7 Management of Network Traffic

Using a network model The key to the wide variety of network-layer management functions offeredby Tellabs 6300 manager for network traffic management is a powerful net-work model concept. The model is not concerned with the specific attributesof the network elements, but is intended to mainly represent the network’send-to-end connections (trails) and capacity (in the form of available time slotsbetween network elements) at the different bandwidth layers. Each networkelement is represented by a matrix that contains information about termina-tion points and internal connections.

The model goes further in the sense that it registers those time slots (called linkconnections) between the network elements that are used by the trails. Vari-ous media —optical, electrical, microwave etc. — are represented in a uniformway. The network topology at the different bandwidth layers is stored togeth-er with element resources (‘capabilities’), and the logical states of the trailsacross the network are managed. This information, which is stored in a net-

MA334 • Rev. A1 23


work database (see ‘Network database’ on page 24), gives a ‘picture’ of thestate of the physical transmission network.

The network model also allows you to include representations of equipmentwhich is not actually managed as part of the specific network but which isused by the trails in it. Such “foreign” equipment could, for example, be aleased line in another supplier’s network or it could be one of your own net-works which is managed separately. See ‘2.7.5 Representing “Foreign” Equip-ment in the Network Model’ on page 36.

2.7.1 Network Information

Representing the network at different bandwidth layers

The network information is split up into information concerning the differentbandwidth layers, each represented by a network level.

The physical layer as well as the RS- and MS layers are modelled in order tosupport, for example, routing of working and protecting routes in physicallyseparated resources. The OCH and OMS layers are used to model densewavelength division multiplexing (DWDM) equipment.

Network database The main functions of the network database used by Tellabs 6300 manager areto provide:

• an information repository for all functions at the network level

• functions for registration of trails, links, matrices etc.

• the structural relations between entities at different traffic layers in theSDH multiplexing architecture

• the means for storing the operational state of network resources.

The network database is an implementation base on the ETSI ES 200 653 rec-ommendation for telecommunication management networks. That is, it storesinformation about SDH trail termination points (TTPs), connection termina-tion points (CTPs), links, link connections and matrices, which are the basicentities for using the network layer functions.

The contents of the database are presented either graphically or in tabularform, and the network information itself is implemented in an industry stan-dard SQL-database.

24 MA334 • Rev. A1


2.7.2 Creating Trails

Setting up trails in one operation

If you had to use the ordinary element management work procedures for set-ting up trails, you would have to operate on each individual network elementin the trail to create cross connections between one element and the next. Thiscould very easily result in misconnections of time slots between elements. Us-ing the special trail setup function, however, you can set up trails (end-to-endconnections) across all of the network elements as one single operation, withno risk of misconnections, simply by selecting the two end points for the trailin the graphical user interface.


1. Select one of the end points and open the pop-up menu to start trail setup.

2. A red line is attached to the mouse, starting in the selected end point icon.

MA334 • Rev. A1 25


The default trail created this way is a trail with only one, automatically select-ed route (that is, an unprotected trail) which is not reserved for any customer.However, the Setup Trail window contains a number of fields and toggle but-tons that can be used to specify of the trail’s parameters.

3. Drag the line to the other end point. The line changes color to green if a trail is possible.

4. Click with the mouse to verify the trail. The line changes color to yel-low and the Setup Trail window appears.


26 MA334 • Rev. A1


The main functions of trail setup

Trail setup in Tellabs 6300 manager is used for end-to-end trail configuration.It allows you to set up protected and unprotected bi-directional trails at theVC12, VC3 and VC4 layers across the SDH transmission network. The route(or routes if the trail is protected) can either be specified manually or be calcu-lated automatically. The main functions of trail setup are:

• Calculation of the optimal route and, optionally, an associated protectionroute

• Automatic and manual setup of trails in meshed networks according to cri-teria specified by the user

• Connection in the network elements of a reserved trail

Note: The other traffic in the network is not disturbed when Tellabs 6300manager establishes a new trail in the network elements.

Setting up trail using automatic route calculation

When you create trails using automatic route calculation, you only need to se-lect the desired end points for the trail and specify the routing preference cri-teria (cost parameter values and exclusion of specific resources). When that isdone, Tellabs 6300 manager executes the high-level process stages describedin the table.

Stage Description

1 The route is calculated according to the routing preference criteria (that is, specific cost parameter values for the route to be selected and exclusion of specific resources to ensure physically diverse routing).

Note: This calculation is highly sophisticated, with options to as-sign priority according to fibre kilometres, number of link connec-tions, spare capacity in link, traffic load factor, or a user-defined pa-rameter (corresponding to the cost parameters: length, jump, spare, load and user). Also it is possible to set up an Exclude List of those resources that are not to be used in the route.

2 The calculated route is reserved in the network database.

3 The trail is implemented in the physical network elements. During connection, alarms are suppressed.

MA334 • Rev. A1 27


Setting up the trail using manual route specification

When you want to set up the route (or routes) for the trail manually, you canselect the route in the graphical user interface of the Network Managementwindow simply by clicking on the links, one after the other, that are to formthe route. The selected links are highlighted in a special color, so that you cansee the selected route in the graphical user interface.

Note: The links forming the primary (working) route and the links formingthe alternative protection route are highlighted in different colors.

Partial protection of trails When you are setting up a new trail, you can only protect it with one end-to-end protecting route. Afterwards, however, you can set up partial protectionof the trail by adding protecting subroutes.

The figure shows an example of the use of partial protection. A trail passingtwo rings is protected in the two rings separately, thereby avoiding any de-pendency between the protection of the rings.

Trail trace identifiers To check that the routes of a specific trail are connected as planned, a trail traceidentifier (TTI) can be transmitted from one end of the trail and received at theother end. The received TTI is compared to the expected TTI value in moni-tored termination points along the trail’s route.

28 MA334 • Rev. A1


The TTI values can be either user-defined or generated by the system. Theycan be created when the trail is created and are then copied into the termina-tion points when the trail is connected. It is, however, also possible to recon-figure the TTIs for an existing trail, whether the trail is connected in the net-work elements or not.

Information about TTI values and validation can be displayed graphically fora specific trail. See ‘Inspecting trail trace identifiers’ on page 33.

2.7.3 Inspecting and Handling Trails

Finding and inspecting specific trails

You can use the Find Trail window to get information about all or some of theregistered trails.

The Find Trail window contains a ‘filter part’ that enables you to search fortrails terminating in specified end points, used by a specific customer and/orin a specific management state.

The window also contains an attribute filter so that you can display and com-pare a selection of attribute values for the trails.

MA334 • Rev. A1 29


A pop-up menu is attached to the trail name. With the menu items in this pop-up menu, you can activate trail operations and open other windows with in-formation about the selected trail.

Handling trails The main functions available in the trail pop-up menu in the Find Trail win-dow are:

• Disconnection of a reserved/connected trail

• Removal of trails

• Managing trail trace identifiers (TTIs)

• Managing protection

• Changing the configuration of a trail

• Viewing the detailed routing of a trail.

30 MA334 • Rev. A1


Inspecting the route(s) of a trail

The route(s) of a specific trail can be highlighted in the display of the network.But you can also open a more detailed view of the routes.

The detailed view of a trail’s routes shows the specific time slots and crossconnections used in the trail. Further details about the cross connections, timeslots and other entities (matrices and links) shown in the view can be obtainedby activating the operations in the pop-up menu attached to each type of en-tity. It is, for example, possible to open the traffic view of the network elementcorresponding to a matrix.

Any parts of a trail that do not form well-defined subroutes are also indicatedin the trail view, so that they can be identified and corrected.

Reconfiguring trails In connection with network repairs or periodic administration, it may be de-sirable to alter the configuration of a particular trail. This is done in a set ofwindows that each are dedicated to a specific reconfiguration operation:

• Changing the routes and subroutes of the trail.

• Protecting a trail (that is, adding alternative routes or subroutes).

• Unprotecting a protected trail (that is, removing routes or subroutes).

• Changing the signal structure of a VC4 trail (that is, the packing of VC3/VC12).

The trail reconfiguration functions are activated via the trail pop-up menu inthe Find Trail window.

Reallocating capacity in VC4 layer trails

The furnishing of VC12 capacities in a VC4 server trail can be reallocated, tofree up available VC3 capacity. In the VC4 signal, the individual VC12 timeslots are moved to a sequence of ‘nicely arranged’ VC12 time slots, so that asmuch ‘space’ as possible in the VC4 trail is left to VC3 time slots.

Note: This grooming function will generally affect traffic since VC12 traffic ismoved from one time slot to another.

MA334 • Rev. A1 31


Trail surveillance As mentioned in ‘Indicating alarms’ on page 15, the network can be monitoredfor alarms that affect trails. This is done by the trail surveillance, which emitsalarms for the trails and also changes the information in the network databaseabout the operational state of the trail (the operational state information re-flects the trail’s ability to provide service):

• A set of alarms for each termination point in the network elements aremonitored. Based on these alarms the operational state of the correspond-ing termination points in the network database is determined.

• Changes in operational state are propagated to all objects within the net-work database which are serviced — directly or indirectly — by those ter-mination points.

• Alarms are emitted for trails and connections that fail.

Non-intrusive monitoring of VC4 layer trails

The non-intrusive monitoring of a trail segment, mentioned above in ‘Moni-toring trail segments non-intrusively’ on page 23, is set up graphically in thetrail view. The monitored data flows are indicated by the use of labels at-tached to the termination point icons. These labels are also shown in the per-formance report.

32 MA334 • Rev. A1


Inspecting trail trace identifiers

The values of the trail trace identifiers for a specific trail and the validation re-sults in the trail’s monitored termination points can be inspected in the trailview

and in the more detailed view of individual matrix connections.

MA334 • Rev. A1 33


Switching traffic The switch status of the traffic flow in a protected trail can be inspected andchanged in the trail view.

You can use either manual or forced switching to change the active route ofthe trail.

34 MA334 • Rev. A1


2.7.4 Inspecting the Network Database

Looking at the contents of matrices and links

At each network level, you can inspect the configuration of the network modelin matrix views and link views.The matrix view shows the internal connections in the matrix (representing,for example, cross connections in a network element or fibre interconnectionsin a manhole). The link view shows the link connections in the link (represent-ing time slots in a cable).

MA334 • Rev. A1 35


Looking at a specific connection

In the matrix view, it can be difficult to see the details of a specific connection(especially a protected connection consisting of several legs). Via the pop-upmenu in matrix view, you can therefore open a separate window with a close-up of the selected connection. The figure shows how a protected connection isshown in the matrix view and in the detailed connection view.

2.7.5 Representing “Foreign” Equipment in the Network Model

“Foreign” equipment represented by an external matrix

If your network is connected to equipment which is not managed directly inthe current network model, but which is part of the trails in the managed net-work, you can let such “foreign” equipment be represented in the networkmodel by an external matrix.

We distinguish between two types of external matrix: a flexible external matrixand an inflexible external matrix.

• The flexible external matrix is used to represent equipment which you donot manage directly as part of the current network, but which you do, nev-ertheless, have some control over (for example, one of your own net-works).

• The inflexible external matrix is used to represent equipment which you donot have any control over and of which you can therefore only show theparts that are known to you (for example, the connection points to a specif-ic line leased from another supplier).

Managing external matrices

An external matrix can be considered as a “black box”, where only the differ-ent interfaces of the external matrix to which the managed network can beconnected, as well as the internal connections between some of the interfaces,are stored in the network database.

During trail setup, connection points and internal connections are created au-tomatically in the external matrix to support any requested trail routes. Tomake the necessary changes in the “foreign” equipment to support these re-quirements, you can use the matrix view to inspect the configuration of the ex-ternal matrix.

However, when the external matrix represents leased lines, it is important thatthe external matrix is allowed to contain only the capacity that you have access

36 MA334 • Rev. A1


to in the other supplier’s network. In that case, you use the matrix view tomake the external matrix inflexible and to delete all non-supported connec-tions.

MA334 • Rev. A1 37


38 MA334 • Rev. A1

Tellabs 6300 network manager 3 Tellabs 6300 Manager as a Structure of LicensesDescription of Management Application and Platform

3 Tellabs 6300 Manager as a Structure of Licenses

Overview Tellabs 6300 manager is sold as a series of licenses: a core license for the server,a number of user licenses, and licenses for the required management function-alities. This chapter contains a brief description of the different types of licens-es.

Server (core) license A core license is required for each server. The core license does not include anyuser licenses; these will have to be purchased separately.

User licenses There are two types of user licenses:

• Configured user licenses, which determine the number of users (that is, op-erator terminals) that can be attached to the system.

• Concurrent user licenses, which determine how many of the configuredusers that can be active on the server at any given time.

The number of concurrent user licenses will be less than or equal to the num-ber of configured user licenses.

Management functionality licenses

There are three levels of management functionality that can be licensed, de-pending on your requirements:

• Element management functionality, which provides element managementof the individual network elements in the network. Typical functionalitiesare configuration, alarm handling and collection of performance data.

• Basic network management functionality, which provides network man-agement on top of the element management. The focus is on trails (end-to-end connctions) rather than on individual network elements and networklayers (path layers) are introduced.

• Enhanced management functionality, which provides such extra function-alities as grooming of trails and the use of the Connector.

Note: Licenses for basic management include element management function-ality, and licenses for enhanced management include both basic man-agement and element management functionality.

MA334 • Rev. A1 39

Tellabs 6300 network manager 3 Tellabs 6300 Manager as a Structure of LicensesDescription of Management Application and Platform

40 MA334 • Rev. A1

Tellabs 6300 network manager 4 Connecting to Other SystemsDescription of Management Application and Platform

4 Connecting to Other Systems

Managing 3rd party network elements

Instead of developing a fully customized, proprietary element access applica-tion for a 3rd party network element, Tellabs 6300 manager is connected to theother supplier’s own element management system. This leaves ‘equipmentnear’ management of duplicated modules, synchronisation etc. to the othervendor’s element manager, while Tellabs 6300 manager focuses on alarms,traffic flow configuration, and performance data

Letting the other vendor’s element manager act as mediating device, reducesthe dependency of specific versions of embedded software in the managednetwork element, and often allows implementation of a near-standard inter-connection between the management systems.

SNMP interface An SNMP Element Access is available for management of the data communi-cations network of routers, bridges, modems etc., which is used to connect themanagement system with remote users, network elements, and inferior/peer/superior management systems.

The SNMP management module supports SNMP Traps, which are mappedinto standardised OSI format alarms. These can be handled, logged etc. likealarms from any other management function in the system.

General ASCII interface Many older systems and PDH systems provide at best an ASCII-coded bitstream on an administrative port. Such equipment can easily be integrated un-der Tellabs 6300 manager by installation of the Graphical ASCII Toolkit. Adedicated toolkit allows the management module to be set up to support bothalarms, configuration, and supervision of such legacy equipment. The Graph-ical ASCII Toolkit parses the protocol, decodes the message set, and generallyprovides the mediation function between the managed network elements andTellabs 6300 manager.

A special implementation of the Graphical ASCII Toolkit is support for theTL-1 message set, often seen on equipment produced in USA.

In many cases, the network elements/EMSs are not able to support a robustsuite of TMN management functions. In many cases, Tellabs 6300 manager’selement management capabilities depend on the capabilities of the managednetwork elements to support specific management functions.

Integrating with other management systems

A northbound XML interface is available for integration of Tellabs 6300 man-ager with umbrella management systems (UMS). The interface allows:

• Real time forwarding and synchronization

• Provisioning of circuits

• Upload of network topology

• Monitoring of events for topology and circuit changes

• Monitoring of alarms.

Using the XML interface requires an understanding of both XML coding lan-guage and the Tellabs 6300 network database information model, as well asgeneral knowledge about TeMIP data representation.

MA334 • Rev. A1 41

Tellabs 6300 network manager 4 Connecting to Other SystemsDescription of Management Application and Platform

42 MA334 • Rev. A1

Tellabs 6300 network manager Part 2 The Management PlatformDescription of Management Application and Platform

Part 2 The Management Platform

• ‘5 The Platform of Tellabs 6300 Manager’ on page 45

MA334 • Rev. A1 43

Tellabs 6300 network manager Part 2 The Management PlatformDescription of Management Application and Platform

44 MA334 • Rev. A1

Tellabs 6300 network manager 5 The Platform of Tellabs 6300 ManagerDescription of Management Application and Platform

5 The Platform of Tellabs 6300 Manager

Overview This chapter is an introduction to the most important features of the platformof Tellabs 6300 manager.

5.1 The Main Structure of a Tellabs 6300 Manager System

Overview of main components

The figure outlines the main components of a Tellabs 6300 manager systemand their interconnections.

Computer system The computer system contains computer hardware and software. Among thehardware units are the computers themselves, the disk storage, the tape stor-age, and various communication devices. The software consists of Tellabs6300 manager and standard software products controlling the computer, thedatabases, and communication with external units.

The Tellabs 6300 manager software is run on a central Alpha server, while theusers’ access to the system is provided by a number of Windows 2000 PCs run-ning Tellabs 6300 manager client software and X Windows. The Tru64 UNIX-based HP OpenView TeMIP has been chosen as ‘platform’ to ensure that Tel-labs 6300 manager is a scalable multi-user system with standardized alarmhandling and with the ability for managing multi-vendor telecommunicationsequipment.

Data communications network

The data communications network (also known as DCN) transports the man-agement information from the computer system to the network elements inthe telecommunications network — and vice versa.

The DCN consists of different types of connections: embedded connections(the management information is transported within the telecommunicationssignal) and connections between the computer system and a network element(NE). The latter type of connections may be based on direct (point-to-point)connections, local area networks, leased lines, or some other media.

MA334 • Rev. A1 45


The data communications networks are continuously monitored, and alarmsare generated if errors or disturbances are detected.

Connections to multi-vendor equipment

Management of telecommunications equipment from other suppliers is doneby letting Tellabs 6300 manager connect to the other supplier’s element man-ager. This way, management of the network element itself is left to the othersupplier’s software while Tellabs 6300 manager focuses on management ofalarms, traffic flow and performance data.

Similarly, Tellabs 6300 manager can connect ‘upwards’ to an over-all manage-ment system from another supplier.

Tellabs 6300 manager self-management

The hardware, software and data communication are represented in the Tel-labs 6300 manager user interface in the same way as the telecommunicationsequipment; that is, as icons, lines etc. You can therefore manage the Tellabs6300 manager system itself in exactly the same way as managing the networkelements.

Key aspects of the computer system — such as free disk storage capacity andcommunication with external units — are monitored. Alarms will be generat-ed if disturbances or errors are detected.

5.2 The System Architecture

Factors to consider The Tellabs 6300 manager system can be built (that is, configured) in manydifferent ways. This flexibility is one of its main features. In deciding how toconfigure your management system, various factors need to be taken into con-sideration. For example:

• The number of network elements to be managed by the system

• The number of alarms that can be expected to be received from the networkelements.

• The number of network operators employed to manage the traffic, and thegeographical location of the operators.

• The expected future development of the system.

Depending on these factors, the Tellabs 6300 manager system can be set up ei-ther as a stand-alone system with only one server (for management of smallernetworks) or as a distributed system with several servers (for management oflarger, expanding networks).

5.2.1 Stand-Alone (Single-Server) Systems

A stand-alone system A stand-alone Tellabs 6300 manager management system consists of a singleAlpha computer on which the software is installed. This computer supplies allprocessing power for the server side of the management system. A number ofWindows 2000 PCs for the network operators are connected to this server, ei-ther locally or remotely (that is, via a wide area network). The PCs have theTellabs 6300 manager client software installed.

Choosing a stand-alone system

A stand-alone system would probably be relevant to manage telecommunica-tions networks where network operators are on the same site (geographical lo-cation) as the central network management centre.

46 MA334 • Rev. A1


5.2.2 Distributed (Multi-Server) Systems

A distributed system In a stand-alone system with remote operators the data traffic can be enor-mous and greatly reduce the responsiveness of the system. Most data is pre-sented graphically in Tellabs 6300 manager, and graphical displays demandlarge data files.

A distributed Tellabs 6300 manager system places servers at each location. Be-sides reducing response time, this type of system architecture does, however,also enable distributed storage of data, making each server ‘responsible’ forthe data from part of the managed network.

System architecture of a distributed system

A distributed Tellabs 6300 manager management system consists of a numberof Alpha computer systems linked together via a data communications net-work. One server (the central server) is placed in the central management cen-tre and can, if necessary, manage the entire telecommunications network. Theother servers are either used for communication with various parts of themanaged network (AM servers) or used to provide the remote PCs with theiruser interface (PM servers)

Directors The servers in a Tellabs 6300 manager system (that is, the computers runningTeMIP) are known as “directors”. Each director is given its own unique name,and is made responsible for a number of network elements in the telecommu-nications network (usually equipment in a specific region). Such a director isknown as the “managing director” for these network elements. Information

MA334 • Rev. A1 47


about the network elements is stored in the managing director’s database andcan then be shared via the TeMIP Name Service.

TeMIP Name Service The TeMIP Name Service (TNS) makes a distributed system ‘transparent’; thatis, it makes it easier and faster to find information about any of the registeredentities in the network from anywhere in the system.

The information about a specific network element is stored its managing di-rector, but each director contains a so-called replica database with the ad-dresses of each registered entity in the whole managed network. This meansthat when a director requires information about a specific entity that is notmanaged by the director itself, it does not have to contact a central server toget the address but can locate the address of the entity in its own replica data-base and then contact the relevant managing director directly.

DCN The data communications network (DCN) between management system andnetwork elements consists of various types of equipment: computers, PCs,routers, and modems, which are connected together either via electrical/opti-cal cables or via Ethernet cables. Each component in the DCN is in some wayresponsible for transferring management data in the network.

A scalable system The use of ‘dedicated’ servers means that a distributed Tellabs 6300 managersystem can easily be scaled to cope with any new requirements from a grow-ing managed network:

• New PM servers can be added to cope with increased demands from net-work operators

• New AM servers can be added to cope in managing new network elements

• New servers can be added to the Central Server to cope with increased de-mands on the Central Network Management Centre.

5.2.3 Using Clusters to Improve Availability

Availability In the telecommunications world, downtime often results in service interrup-tion, which besides being expensive, can reduce an operator’s competitive-ness. In the open, liberalized market of today, this can be catastrophic. It is im-portant to investigate the factors affecting a system’s availability, that is theproportion of time that a system can be used for productive work.

The availability of a system is not dependent upon whether it is configured asa stand-alone or as a distributed system. The availability is dependent, amongother factors, on the way in which the computer system hardware is config-ured. One way of improving the availability of all Tellabs 6300 manager sys-tems is by using clusters.

48 MA334 • Rev. A1


Using clusters A cluster is a group of two or more interconnected computers, which are onthe same site, the same LAN and the same SCSI bus. The computers in a clus-ter share data, thereby safeguarding it against any kind of computer failure. Itis normally only central servers and AM servers that are made as clusters.

The computers in a cluster can share the data either through mirroring of thedisks or through the use of a redundant array of independent disks (a so-called RAID system).

Mirrored disks A cluster can share two disks that are exact copies of one another (mirror im-ages). Data stored in disk storage equipment A and is automatically copiedover to B. This means that if A fails, B can immediately take over A’s functions.

MA334 • Rev. A1 49


Redundant array of independent disks

Data storage in a redundant array of, for example, four independent disksmeans that independent data is stored on disks A, B and C, whereas disk Dcontains all the data from A, B and C. This way, if a disk fails, for example A,disk A can be replaced by a new one, and the information on the original diskA can be recovered by comparing data on disk D with the data on both B andC.

5.2.4 Using Remote Standby Systems to Improve Availability

Separate management center

The use of a separate management center means having a complete remotestandby system for your production system. Via a 2 Mbit/s line, a backup istransferred from the production system to the standby system at a program-mable time interval (normally once every 24 hours). The systems may beplaced physically very far apart.

At any time (except while the backup is taking place) the roles of the two sys-tems can be switched manually by the system administrator of the standbysystem. The use of advanced Site Synchronization software ensures stabilityand fast recovery in this ‘switch-over’ process.

The special advantage of a remote standby system is that it allows one of thesystems to be taken down for service, upgrades, expansion etc. while the othersystem is managing the network.

50 MA334 • Rev. A1


5.3 Configuration and Installation of the System

Help from Systems Integration

To ensure that you are able to implement the use of Tellabs 6300 manager asyour network management system as fast as possible, Tellabs Denmark’s Sys-tems Integration department offers to control and manage the entire project.That is, Systems Integration helps you with configuration, delivery, installa-tion, commissioning, training and subsequent support.

This will give you a fully functional, customized, ready-to-use managementsystem.

Systems Integration services

Tellabs Denmark’s Systems Integration department provides the followingservices:

• Planning support, including:

• Setup of Tellabs 6300 manager test systems

• Technical proposals, including system configurations, sizing and esti-mates for customizations.

• Overall technical management of the project

• Paste together of Tellabs Denmark’s products with 3. party hardware andsoftware

• Migration of data between platforms

• Support, including:

• Upgrading of software

• Maintenance of database.

MA334 • Rev. A1 51


5.4 System Administration

The system administrator’s tasks

The design of Tellabs 6300 manager allows the system to run practically unat-tended, so the tasks of the system administrator are limited to those of dailymanagement:

• Managing system security and user accounts

• Archiving alarms and performance data

• Managing back-ups (restoring lost user files, checking the daily back-up,and managing tape media)

• Starting and shutting down the system

• Keeping an eye on the system load

• Upgrading software

• Recognizing system trouble, if any, and calling for service.

5.4.1 Management of System Security

Introduction The management of system security is part of Tellabs 6300 manager’s TeMIPcore system. The security facilities are flexible and can be adjusted to meet theneeds of your organization.

Security policy The security policy of Tellabs 6300 manager is:

• A number of people must be authorized to perform a variety of tasks with-in the system.

• Users must be allowed to perform only the tasks that are relevant for theirjobs.

• Unauthorized persons must not be able to log in to the system.

Security mechanisms The following basic security mechanisms are used to implement the securitypolicy of the Tellabs 6300 manager system:

• The password check ensures that only authorized personnel can log in tothe system.

• The user profile facility allows users of the system to be divided intogroups with different access rights. In this way network monitoring taskscan be separated from the tasks of network planning and administrationand from the tasks related to maintaining the hardware and software of theTellabs 6300 manager system. The contents and number of these profilesmay be adapted to the needs of each customer. See a description of the de-fault user profiles in Section 5.4.2.

• It is possible to log operations performed in the system.

Note: The access to various functions is adjusted to the user profile of the in-dividual user.

Session manager The session manager establishes and manages user sessions on the UNIX serv-er host. The session manager is responsible for starting and stopping Tellabs6300 manager GUIs and the PC application interfacing to the UNIX server.

52 MA334 • Rev. A1


A user session is protected by a login mechanism, which validates the user’sright to access the system. After the user is validated, he/she may run appli-cations against the server. The session manager controls processes while thesession is established, and removes processes when the session is terminated.

5.4.2 Default User Profiles

Introduction Tellabs 6300 manager contains the pre-defined user profiles described in thissection. Each of these default profiles can be modified and more can be addedin the overall integration project, to fit your company’s network, system archi-tecture and organization.

The guest A guest has read-only access to the Tellabs 6300 manager system and cannotperform any operations.

The network operator A network operator is responsible for administrating and supervising themanaged network. That is:

• Add new network elements to the system. This includes configuring thenetwork elements and setting up the data communications network(DCN).

• Define the network operator’s field of responsibility, that is divide thecomposite supervision task into tasks of appropriate size.

• Set up the performance data collection, if available.

• Restructure the entire representation of the managed network, if expan-sion on top of expansion has made the current representation obsolete.

• Monitoring the alarm activity

• Keeping up to date with the performance of the managed equipment

• Taking action to restore traffic in case of errors, disturbances, or degrada-tion of transmission quality.

The system manager A system manager or system administrator is responsible for the hardwareand software of the Tellabs 6300 manager system, including archiving ofalarm and performance data, back-up, user administration, software upgrad-ing, and several other tasks (see ‘The system administrator’s tasks’ on page52).

MA334 • Rev. A1 53


54 MA334 • Rev. A1

Tellabs 6300 network manager IndexDescription of Management Application and Platform

Index

AAdvantages 8Alarms 15

affecting trails 16filtering 16filtering criteria 16indicating 15information about 15saving information 17trail surveillance 32

Architecture of system 46ASCII interface 41Availability 48

CClusters

use of 49Command line interface 11Configuration 7Configuring the system 51Connecting to other systems 41Connection view of network model 36Cost parameters in route calculation 27Cross connections in network elements 20

DData about events

logging 23Data about performance

collecting 22monitoring 23

Data communications network 45, 48Database for network traffic management 24DCN 45, 48Directors 47Disks

independent in array 50mirrored 49

Distributed system 47Domain hierarchy

navigating in 12

EEvent data

logging 23ExternalMatrices 36

FFiltering of alarms 16

filtering criteria 16Find Trail function 29

GGeneral features 11Grooming VC4 layer trails 31Guest 53

IInstalling the system 51ITU-T standards

X.721 15, 23X.733 15X.734 23X.735 15, 23

LLicenses 39Link view of network model 35

MManagement of system 46Manuals 8Matrix view of network model 35Mirrored disks 49Monitoring

non-intrusive 32Multiple servers 11Multiple users 11Multi-vendor equipment 46

NNavigating in domain hierarchy 12Network

bandwidth layers 24foreign equipment 36model 23representation 12structure 12synchronization 18timing view 18

Network database 24inspecting 35

Network editor 13working in 14

MA334 • Rev. A1 55

Tellabs 6300 network manager IndexDescription of Management Application and Platform

Network elementscross connections in 20equipment view 19management of 19synchronization 21traffic view 20

Network operator 53Network traffic management 23

creating trails 25database 24layers 24

Non-intrusive monitoring 32

PPerformance data

collecting 22monitoring 23

Platform 45

RRedundant array of independent disks 50Routes

calculating 27creating manually 28inspecting 31

SScalability 48Security 52Separate management center 50Server directors 47Session manager 52Single-server 11SNMP interface 41Stand-alone system 46Standards

X.721 15, 23X.733 15X.734 23X.735 15, 23

Standby system 50Structure 45Synchronization

in a network element 21in the network 18

System administrator 52, 53System manager 53Systems Integration 51

TTelecommunications management network 7TeMIP 45

TeMIP Name Service 48Text-based user interface 11Third party network elements

managing 41Timing view 18TMN 7Traffic

switching 34Traffic management 23Traffic view of network elements 20Trail trace identifiers 28, 33Trails

affected by alarms 16creating 25creating routes manually 28finding 29grooming 31handling 29inspecting 29non-intrusive monitoring 32partial protection 28reallocating capacity 31reconfiguring 31route inspection 31surveillance for alarms 32switching traffic 34trail trace identifiers 28, 33using automatic route calculation 27

UUNIX 45User interface

graphical 11text-based 11

User profiles 53User workstations 8

WWorkstations 8

XX.721 standard 15, 23X.733 standard 15X.734 standard 23X.735 standard 15, 23

56 MA334 • Rev. A1

ma334_a1

Documents