Beruflich Dokumente
Kultur Dokumente
MA199-08 • Issue 1
FCC Notification Federal Communications Commission (FCC) Rules require that you be noti-
Statement fied of the following:
This equipment has been tested and found to comply with the limits for a
Class A digital device, pursuant to part 15 of the FCC Rules. These limits are
designed to provide reasonable protection against harmful interference when
the equipment is operated in a commercial environment. This equipment gen-
erates, uses, and can radiate radio frequency energy and, if not installed and
used in accordance with the instruction manual, may cause harmful interfer-
ence to radio communications. Operation of this equipment in a residential
area is likely to cause harmful interference in which case the user will be re-
quired to correct the interference at his own expense.
Changes or modifications not expressly approved by Tellabs Operations, Inc.,
in writing can void the user’s authority to operate the equipment.
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 use
this 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 civil
penalties.
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: AUDIO
PLUS®, CABLESPAN®, CEC-128™, DYNAMIC SIGNAL TRANSFER™,
DXX®, DXX logo®, EC DUO®, ENHANCED AUDIO PLUS®, EX-
PRESS/PATH®, FOCUS™, MARTIS®, MARISDXX®, MARTIS logo®, and
MARTISDXX logo®, METROWATCH™, NETREACH®, NETWISE®,
SCULPTURED SOUND™, TELLABS®, TELLABS and T symbol®,
T symbol, TELLABS PROPARTNER™, TEL/MAP™, TEL/MOR®, THE
WORLD COMMINCIATES THROUGH TELLABS™, TITAN®, VERITY™,
YOUR NETWORKING PARTNER®.
Any other company or product names may be trademarks of their respective
companies.
2 MA199-08 • Issue 1
FOCUS NM2100nm Contents
Managing Traffic in a Network Element using Traffic View
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4 Equipment-Specific Information . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4.1 Showing the Traffic-Related Entities in Hierarchies . . . . . . . . . . . . . 67
4.2 Mapping Names of TPs in the NM2100nm System . . . . . . . . . . . . . 67
4.3 Cross Connection Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4.4 FOCUS 2500 Traffic View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
4.4.1 Relationship between Traffic View and the Entity Hierarchy
for FOCUS 2500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
4.4.2 Naming Termination Points in FOCUS 2500 . . . . . . . . . . . . 71
4.5 Marconi ADM-1 Traffic View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
4.5.1 Relationship between Traffic View and the Entity Hierarchy
for Marconi ADM-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
4.5.2 Naming Termination Points in Marconi ADM-1 . . .. . . . . . . . 73
MA199-08 • Issue 1 3
FOCUS NM2100nm Contents
Managing Traffic in a Network Element using Traffic View
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4 MA199-08 • Issue 1
FOCUS NM2100nm Preface
Managing Traffic in a Network Element using Traffic View
Preface
The purpose of this This manual describes the Traffic View option of FOCUS NM2100nm. Traffic
manual View is used to supervise and control the traffic flow inside a network ele-
ment.
We assume that you are familiar with the NM2100nm core system (TeMIP),
and that you know, for instance, how to enter and leave the system, perform
operations on selected network elements, use domains, and view and respond
to an alarm. This is described in [1] and [2].
We also assume that you have access to the User’s Manual for the Element Ac-
cess product for the network element in question, and that you are familiar
with its contents.
Product version Check the Software Release Notes to make sure that this manual corresponds
to your current product version.
Style conventions The following style conventions are used in the manual:
• Names from the screen
Bold typeface are used for names of, for instance, windows, operations,
fields, and push buttons when the names appear on the screen (example:
the Traffic View window). When it is clear that we are referring to, for in-
stance, a push button, the name is used alone (example: Press OK). Note
that bold typeface are also used in other contexts.
Note: Window names that do not appear on the screen are printed in
Times font and normal typeface (example: the map window).
• Text from the screen
“Quotation marks” are used for text strings from the screen (example:
“Identifier too long”).
• Words to be substituted
Italics in angle brackets are used for words to be substituted by the system
(for example: Protect <Name of TP>).
Note: Italics are also used in other contexts.
MA199-08 • Issue 1 5
FOCUS NM2100nm Preface
Managing Traffic in a Network Element using Traffic View
• Menus
Arrows are used for indicating the menu structure in instructions on how
to select a certain menu item (example: Select Connect → PointToPoint Bid).
• Keyboard shortcuts
The keyboard shortcut for a menu item is the key combination Ctrl + <let-
ter>. In the text, such keyboard shortcuts are written as, for example,
Ctrl+A.
References [1] Tellabs Denmark A/S, FOCUS NM2100nm, Working in NM2100nm, Us-
er’s Manual, MA220-xx
[2] Tellabs Denmark A/S, FOCUS NM2100nm, Handling Alarms in
NM2100nm, User’s Manual, MA219-xx
[3] Tellabs Denmark A/S, FOCUS NM2100nm, System Administration
Guide and Reference, MA 119-xx
[4] Tellabs Denmark A/S, FOCUS NM2100nm, Managing Trails in your Net-
work Vols.1-3, User’s Manual, MA258-xx, MA259-xx and MA260-xx
[5] Tellabs Denmark A/S, FOCUS NM2100nm, FOCUS AC1 Element Ac-
cess, User’s Manual, MA153-xx
[6] Tellabs Denmark A/S, FOCUS NM2100nm, FOCUS AC4 Element Ac-
cess, User’s Manual, MA157-xx
[7] Tellabs Denmark A/S, FOCUS NM2100nm, FOCUS 2500 Element Ac-
cess, User’s Manual, MA113-xx
6 MA199-08 • Issue 1
FOCUS NM2100nm Preface
Managing Traffic in a Network Element using Traffic View
MA199-08 • Issue 1 7
FOCUS NM2100nm Preface
Managing Traffic in a Network Element using Traffic View
8 MA199-08 • Issue 1
FOCUS NM2100nm 1 A General Description of Traffic View
Managing Traffic in a Network Element using Traffic View
Introduction Traffic View provides a graphical user interface to SDH network elements,
from which it is possible to manage the traffic aspects of the SDH equipment.
The graphics shown in the Traffic View window illustrate the traffic structure
and matrix connections in a generic, intuitive way. Each time Traffic View is
started up or the Traffic View window is refreshed, information about the cur-
rent traffic configuration of the relevant network element (NE) is uploaded.
The general features of the Traffic View window are described here, as well as
the methods for opening the window. The contents of the Traffic View window
for each specific type of network element is described in ‘4 Equipment-Specif-
ic Information’ on page 67.
What does the Traffic The Traffic View window provides a graphical illustration of the ports and the
View window show? connections that currently exist within the selected network element (NE).
The menu items in the main menus and the pop-up menus allow you to create
and modify both higher-order and lower-order cross connections and to view
information about the ports.
MA199-08 • Issue 1 9
FOCUS NM2100nm 1 A General Description of Traffic View
Managing Traffic in a Network Element using Traffic View
Zoom options In the upper right-hand corner of the Traffic View window are 3 zoom icons
that allow you to reduce or enlarge the contents of the window.
Alarm indication You can get an alarm indication in the Traffic View window. An alarm indica-
tion field is placed in the lower right-hand corner of the window. When an
alarm occurs, the alarm indication field and the icon representing the affected
port change colour (as shown in the figure).
The alarm indication field also changes colour when a non-traffic alarm occurs
in the NE.
10 MA199-08 • Issue 1
FOCUS NM2100nm 1 A General Description of Traffic View
Managing Traffic in a Network Element using Traffic View
The different parts of the The work area is split into three separate columns, each representing different
work area parts of a traffic structure:
MA199-08 • Issue 1 11
FOCUS NM2100nm 1 A General Description of Traffic View
Managing Traffic in a Network Element using Traffic View
The icons used in the Icons are used to graphically represent containers (for example, TUGs), termi-
Traffic View window nation points and cross connections.
The containers and TTPs are shown in tree structures representing the signals
contained in the container or TTP. The trees can be collapsed and expanded.
A container or TTP that can be expanded, is represented by an icon with a plus
(+) in the middle; a container or TTP that can be collapsed, is represented by
an icon with a minus (–) in the middle.
See the procedures for expanding and collapsing ports and TTPs in
‘2.4 Expanding Containers and TTPs’ on page 22 and ‘2.5 Collapsing Contain-
ers and TTPs’ on page 23.
When part of the tree structure is collapsed, it may happen that only one of the
termination points of a particular cross connection is shown while the other(s)
are hidden. In that case, the cross connection cannot be shown as a line but is
indicated by a the use of a special icon for the shown TP.
12 MA199-08 • Issue 1
FOCUS NM2100nm 1 A General Description of Traffic View
Managing Traffic in a Network Element using Traffic View
Test access points and loopback connections are supported in FOCUS LX 2.0.
A test access point (TAP) is represented by an icon with an x in the middle; a
loopback connection is indicated by a loop.
See a description of test access connections and the procedures for creating
and removing them in ‘3.7 Working with Test Access Groups’ on page 56.
Identification of You can identify containers, ports, TPs and connections in the Traffic View
containers, ports, TPs window by placing the cursor over the icon representing the object in ques-
and connections tion. This highlights the icon (colour change), and the full name of the contain-
er, port, TP or connection it represents, appears in a text ‘bubble’ alongside the
cursor. The figure shows an example of such a text ‘bubble’.
MA199-08 • Issue 1 13
FOCUS NM2100nm 1 A General Description of Traffic View
Managing Traffic in a Network Element using Traffic View
The pop-up menus in Each object in the Traffic View window’s work area has a pop-up menu at-
Traffic View tached to it. The pop-up menu contains the operations specifically related to
the object. You display the pop-up menu for an object by placing the cursor
over the object and pressing mouse button 3.
14 MA199-08 • Issue 1
FOCUS NM2100nm 1 A General Description of Traffic View
Managing Traffic in a Network Element using Traffic View
Where can Traffic View Traffic View can be started up from any graphical user interface where the rel-
be started up from? evant NE is represented by an icon (an NE icon or an NEMatrix icon). That is,
from:
• An Iconic Map window showing an NE domain (see ‘In a map window
showing an NE domain’ on page 16)
• An Iconic Map window showing a network layer domain (see ‘In a map
window showing a network layer domain’ on page 16)
• A Network Management window showing a network layer domain (see ‘In
a Network Management window showing a network layer domain’ on
page 17)
• A Trail View window showing the route(s) of a trail (see ‘In a Trail View
window’ on page 18).
In an Iconic Map window, the menu item for starting up Traffic View is placed
in the icon’s Operations menu. In the network layer management GUI win-
dows, the menu item is placed in the icon’s pop-up menu.
How does Traffic View When you call Traffic View, an empty Traffic View window appears, showing
start up? the message “Retrieving NE configuration, please wait ...” in the information
field. If the network element consists of a large number of ports or subracks, a
selection window also appears, allowing you to specify which ports or sub-
racks are to be displayed in the Traffic View window.
After a period of time, the containers, ports, termination points and any con-
nections that already have been made in the NE will be shown graphically in
the work area of the Traffic View window (see the example in ‘What does the
Traffic View window show?’ on page 9). This information is read directly
from the selected NE.
MA199-08 • Issue 1 15
FOCUS NM2100nm 1 A General Description of Traffic View
Managing Traffic in a Network Element using Traffic View
In a map window When you are working in an Iconic Map window showing an NE domain
showing an NE domain (that is, showing NE icons), you can start up Traffic View by activating the
Traffic View menu item in the NE icon’s Operations menu. The figure shows an
example of such a map window and the Operations menu for an NE icon.
In a map window When you are working in an Iconic Map window showing a network layer do-
showing a network layer main (that is, showing NEMatrix icons), you can start up Traffic View by acti-
domain vating the NE Traffic View menu item in the NEMatrix icon’s Operations menu.
The figure shows an example of such a map window and the Operations menu
for an NEMatrix icon.
16 MA199-08 • Issue 1
FOCUS NM2100nm 1 A General Description of Traffic View
Managing Traffic in a Network Element using Traffic View
In a Network When you are working in a Network Management window showing a network
Management window layer domain (that is, showing NEMatrix icons), you can start up Traffic View
showing a network layer by activating the NE Traffic View menu item in the NEMatrix icon’s pop-up
domain menu. The figure shows an example of such a window and the pop-up menu
for an NEMatrix icon.
MA199-08 • Issue 1 17
FOCUS NM2100nm 1 A General Description of Traffic View
Managing Traffic in a Network Element using Traffic View
In a Trail View window When you are working in a Trail View window (showing a trail route with
NEMatrix icons), you can start up Traffic View by activating the NE Traffic
View menu item in the NEMatrix icon’s pop-up menu. The figure shows an ex-
ample of such a window and the pop-up menu for an NEMatrix icon.
18 MA199-08 • Issue 1
FOCUS NM2100nm 2 Operating in the Traffic View Window
Managing Traffic in a Network Element using Traffic View
Overview The following basic work procedures in Traffic View are described:
• Using the mouse
• Choosing the naming convention for ports
• Showing/Hiding selected ports
• Expanding containers/TPs
• Collapsing containers/TPs
• Specifying the signal structure of TUG3s
• Printing the contents of the Traffic View window
• Refreshing the Traffic View window
• Closing the Traffic View window
In addition, we describe how to access, via the Traffic View window, opera-
tions that are normally available in the Operations menu of the Iconic Map
window.
How to open the Traffic View window is described in ‘1.2 Starting up Traffic
View’ on page 15. The procedures for creating and changing cross connections
are described in ‘3 Working with Cross Connections in Traffic View’ on page
29.
A three-button mouse The mouse that you use in Traffic View has three buttons. When referring to
the buttons, we use the numbering shown in the figure.
The operations that you When you work in the Traffic View window, you use a mouse with 3 buttons
perform with the mouse (see ‘A three-button mouse’ on page 19) to perform all operations, for example
making selections, selecting objects and making cross connections. The table
describes the terminology used in the manual for these operations.
MA199-08 • Issue 1 19
FOCUS NM2100nm 2 Operating in the Traffic View Window
Managing Traffic in a Network Element using Traffic View
Display pop-up menu place the cursor over the object in the window
and press mouse button 3.
To choose the naming In some NEs the names given to the ports in the NE equipment do not match
convention used in the name convention used in the NM2100nm system (see ‘4.2 Mapping
Traffic View Names of TPs in the NM2100nm System’ on page 67). However, Traffic View
allows you to choose the naming system that you prefer, using this procedure:
Step Action
20 MA199-08 • Issue 1
FOCUS NM2100nm 2 Operating in the Traffic View Window
Managing Traffic in a Network Element using Traffic View
To show/hide selected In the Traffic View window you can show or hide selected ports. This proce-
ports dure describes how you select which ports to show and which ports to hide.
Step Action
2 On the left of the area showing Not shown ports in the port selection
window, click on the toggle button representing the type of port you
wish to show (for example, 2 Mbit/s).
Lists appear in the two areas labelled Not shown and Shown, indicat-
ing which ports are hidden and which ports are shown in the present
Traffic View window.
3 If you want to show some of the ports that are currently hidden, first
select the required ports in the Not shown area, using one of the three
methods described below:
• To select one port at a time, click on the name of the port. The port
name is highlighted.
• To select a number of ports that are not listed directly one after
the other, press and hold down Ctrl and Shift and then click indi-
vidually on the name of each port. Each of the selected ports are
highlighted individually.
• To select a number of ports that appear directly one after the oth-
er in the list, click on the uppermost port you wish to select and
then drag the cursor (with mouse button 1 pressed down) over all
the ports you wish to select. The selected ports are highlighted as
one block.
MA199-08 • Issue 1 21
FOCUS NM2100nm 2 Operating in the Traffic View Window
Managing Traffic in a Network Element using Traffic View
Step Action
The ports that you selected in Step 3 move from the Not shown list to
the Shown list, and icons representing them appear in the Traffic View
window.
5 If you want to hide some of the ports that are currently shown, first
select the required ports in the Shown area, using one of the three
methods described in Step 3.
The ports that you selected in Step 5 move from the Shown list to the
Not shown list, and the icons representing them disappear from the
Traffic View window.
7 When the Traffic View window shows the ports that you wish to see,
close the port selection window by clicking on the Dismiss button.
Which containers/TTPs The containers and TTPs that can be expanded have a plus (+) sign within the
can be expanded? icons which represent them. You can expand:
• All containers/TTPs in a Traffic View window at the same time
• All containers/TTPs that are free (that is, not yet connected)
• All containers/TTPs that are connected
• One container/TTP at a time.
How to expand The table describes how to expand containers/TTPs in the Traffic View win-
containers/TTPs dow.
22 MA199-08 • Issue 1
FOCUS NM2100nm 2 Operating in the Traffic View Window
Managing Traffic in a Network Element using Traffic View
Which containers/TTPs The containers and TTPs that can be collapsed have a minus (-) sign within the
can be collapsed? icons which represent them. You can collapse:
• All containers/TTPs in a Traffic View window at the same time
• One container/TTP at a time.
How to collapse The table describes how to collapse containers/TTPs in the Traffic View win-
containers/TTPs dow.
Changing TUG3 signal In Traffic View, you can change the signal structure of a TUG3 from 1 tu3CTP
structure to 21 tu12CTPs or vice versa, provided none of the TUG3’s currently existing
CTPs are connected.
To define the signal To define or change the signal structure of a TUG3 (that is, to choose whether
structure of a TUG3 the TUG3 contains 1 tu3CTP or 21 tu12CTPs):
Step Action
1 Place the mouse cursor over the TUG3 termination point and press
mouse button 3.
The pop-up menu for a TUG3 appears.
MA199-08 • Issue 1 23
FOCUS NM2100nm 2 Operating in the Traffic View Window
Managing Traffic in a Network Element using Traffic View
Step Action
2 Select the menu item that corresponds to the required signal struc-
ture:
• To get 1 tu3CTP (VC-3), select Modify signal structure to 1 tu3.
To print the Traffic View This procedure describes how you print the contents of the Traffic View win-
window contents dow to your default printer.
Step Action
An example of a print-out The figure shows the print-out of the contents of the Traffic View window for
a FOCUS AC1 network element.
24 MA199-08 • Issue 1
FOCUS NM2100nm 2 Operating in the Traffic View Window
Managing Traffic in a Network Element using Traffic View
To access traffic-related Via the Traffic View window, you can access all traffic-related operations that
operations are normally available in the Operations menu of TeMIP’s user interface. This
procedure describes how you access these traffic-realated operations.
Step Action
1 Place the cursor over the port, TP, cross connection or protected con-
nection on which you wish to perform an operation.
The relevant object is highlighted and its name appears alongside the
cursor.
To find out more about the individual operations, see the relevant NE’s Ele-
ment Access User’s Manual ([5], [6], [7], [8], [9] and [10]) and the manual about
performance monitoring ([11]).
MA199-08 • Issue 1 25
FOCUS NM2100nm 2 Operating in the Traffic View Window
Managing Traffic in a Network Element using Traffic View
Examples of pop-up The figure shows examples of the pop-up menus available in the Traffic View
menus window.
26 MA199-08 • Issue 1
FOCUS NM2100nm 2 Operating in the Traffic View Window
Managing Traffic in a Network Element using Traffic View
To access non-traffic- This procedure describes how you access the non-traffic-related operations. A
related operations FOCUS AC1 is used as an example.
Step Action
Note: If only operations for NE Global are available, the menu item
for each operation will be listed directly in the Operations menu.
MA199-08 • Issue 1 27
FOCUS NM2100nm 2 Operating in the Traffic View Window
Managing Traffic in a Network Element using Traffic View
Step Action
3 Select the operation that you wish to perform in the submenu and in
any subsequent submenus (where relevant) that appear.
The relevant window from Iconic Map appears in the Traffic View
window. The figure shows an example of such a window.
To find out more about the individual operations, see the relevant NE’s Ele-
ment Access User’s Manual ([5], [6], [7], [8], [9] and [10]) and the manual about
performance monitoring ([11]).
To refresh the Traffic To refresh (update) the contents of the Traffic View window:
View window
Step Action
28 MA199-08 • Issue 1
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
Overview The Traffic View work procedures concerning cross connections are described
here.
• ‘3.2 Making Cross Connections’ on page 33
• ‘3.3 Aborting a Cross Connection Operation’ on page 43
• ‘3.4 Changing a Cross Connection’ on page 44
• ‘3.5 Showing the Other End of a Cross Connection’ on page 54
• ‘3.6 Finding Traffic in a Protected Cross Connection’ on page 55.
• ‘3.7 Working with Test Access Groups’ on page 56
Some general background information about cross connections is given first
(in ‘3.1 Types of Cross Connection’ on page 29).
Introduction Before you start creating cross connections in Traffic View, we recommend
that you familiarize yourself with the types of cross connections that you can
create and with the names given to these cross connections.
Note: Some cross connection types may not be supported by the NE that you
are working with. See ‘In which NEs?’ on page 68 for information about
which cross connection types the various NEs support.
Which types of cross There are the following types of cross connection:
connection?
• Point-to-point bidirectional (PointToPoint Bid)
• SNC protected point-to-point bidirectional (SNC Protected PointToPoint
Bid)
– Single
– Double
Note: The text in brackets shows what these connections are called in Traffic
View.
Concept of point-to-point A point-to-point cross connection describes a connection where traffic flows
connections from one termination point (TP) to another TP. A unidirectional connection
means that the traffic can only flow in one direction, whereas a bidirectional
connection means that the traffic can flow in either direction. The figure illus-
trates the two types of point-to-point connection.
MA199-08 • Issue 1 29
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
Concept of an SNC Subnetwork connection protection (SNCP) means that the traffic flow is pro-
protected point-to-point tected by two possible routes being available to the signals (the working route
bidirectional connection and the protecting route). An SNC protected point-to-point bidirectional cross
connection inside an NE consists of a pair of connections with one shared ter-
mination point, as shown in the figure.
30 MA199-08 • Issue 1
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
Concept of a double Double subnetwork connection protection (double SNCP) means that two
SNC protected point-to- pairs of SNC protected point-to-point bidirectional cross connections are set
point bidirectional up inside the NE, with one pair of routes protecting the other pair. Thereby
connection each of the four termination points in the ‘group’ has two possible routes for
the traffic to/from the TP, as shown in the figure.
MA199-08 • Issue 1 31
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
Concept of a bulk Making a bulk connection means that point-to-point bidirectional cross con-
connection nections for all free tu12CTPs in a specific container (A-end) are set up simul-
taneously. The Z-end of the cross connections may be either the tu12CTPs in
a container of the same type as the A-end or a group of 2Mbit/s ports.
If 2Mbit/s ports are selected as Z-end, the tu12CTPs are connected to ports on
the same interface card (that is, ports with identical rack-subrack-slot num-
bers). The first free tu12CTP is connected to the first free 2Mbit/s port, the sec-
ond free tu12CTP is connected to the second free 2Mbit/s port (with increas-
ing port number).
Note: Busy tu12CTPs and 2Mbit/s ports in A-end and Z-end remain unaffect-
ed when a bulk connection is set up. Connections are only set up be-
tween free termination points.
The procedures to make bulk connections are described in detail in ‘To make
a bulk of point-to-point bidirectional connections between tu12CTPs and
2Mbit/s ports’ on page 35 and ‘To make a bulk of point-to-point bidirectional
connections between tu12CTPs’ on page 36.
32 MA199-08 • Issue 1
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
Overview The procedures for creating the following types of cross connection are de-
scribed:
• ‘3.2.2 Making Point-to-Point Bidirectional Connections’ on page 34
• ‘3.2.3 Making an SNC Protected Point-to-point Bidirectional Connection’
on page 38
• ‘3.2.4 Making a Double SNC Protected Point-to-point Bidirectional Con-
nection’ on page 41)
The type of connection which can be made depends on the NE in question (see
the table in ‘In which NEs?’ on page 68).
Before you start any kind of cross connection procedure, however, it is impor-
tant to read ‘3.2.1 Points to be Noted about Cross Connection Procedures’ on
page 33.
Valid connections You can only start a connection procedure from a ‘legal’ termination point
(TP) or, for bulk connections, from a container.
Color indication of While you are creating the connection, the cursor is connected to the ‘start’ TP
whether a connection is with a ‘rubber band’ line. The color of this line indicates whether it is possible
possible to make a connection from the ‘start’ TP to the TP that you have placed the cur-
sor on.
Windows shown during a A window may appear during some of the connection procedures, asking for
procedure additional information about the connection you are trying to make, for exam-
ple: Connection Label, Administrative State, and Protection Mode, User Label.
For an explanation of these attributes and their possible values, refer to the El-
ement Access manual for the NE in question (see [5], [6], [7], [8], [9] and [10]).
Message boxes shown A message box with an error message appears if the chosen connection cannot
during a procedure be made because there is a fault in the NE itself. For an explanation of these
messages, refer to the Element Access manual for the NE in question (see [5],
[6], [7], [8], [9] and [10]).
MA199-08 • Issue 1 33
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
Before you start the Read ‘3.2.1 Points to be Noted about Cross Connection Procedures’ on page 33
procedure before starting the cross connection procedure.
To make a single point- This procedure describes how you make a single point-to-point bidirectional
to-point bidirectional cross connection in Traffic View.
connection
Step Action
1 Place the cursor over the termination point (TP) you wish to connect
to another, and press mouse button 3.
A pop-up menu appears.
3 Move the cursor to the TP you wish to connect to the ‘start’ TP.
The line is dragged along with the cursor and changes color to green
if connection is possible.
34 MA199-08 • Issue 1
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
To make a bulk of point- This procedure describes how you make several point-to-point bidirectional
to-point bidirectional cross connections between tu12CTPs and 2Mbit/s ports in Traffic View.
connections between
Note: Busy tu12CTPs and 2Mbit/s ports are not affected.
tu12CTPs and 2Mbit/s
ports
Step Action
1 Place the cursor over the container whose free tu12CTPs you wish to
connect to 2Mbit/s ports, and press mouse button 3.
A pop-up menu appears.
3 Move the cursor to the first of the free 2Mbit/s ports you wish to
connect to the free tu12CTPs in the container.
The line is dragged along with the cursor and changes color to green
if connection is possible.
4 If the line is green, click on the 2Mbit/s port to verify the connection.
A Result window appears, reporting the number of cross connec-
tions created.
If the container is expanded, you can also see the lines representing
the connections.
MA199-08 • Issue 1 35
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
Step Action
The first free tu12CTP in the container is connected to the first free
2Mbit/s port (the selected port), the second free tu12CTP to the sec-
ond free 2Mbit/s port etc., starting with the selected port and with
increasing port number.
To make a bulk of point- This procedure describes how you make several point-to-point bidirectional
to-point bidirectional cross connections between tu12CTPs in Traffic View (that is, from container to
connections between container).
tu12CTPs
Note: Busy tu12CTPs are not affected.
Step Action
1 Place the cursor over one of the two containers whose free tu12CTPs
you wish to connect to each other, and press mouse button 3.
A pop-up menu appears.
36 MA199-08 • Issue 1
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
Step Action
3 Move the cursor to the ’end’ container whose free tu12CTPs you
wish to connect to the free tu12CTPs in the ’start’ container.
Note: The two containers must be of the same type.
The line is dragged along with the cursor and changes color to green
if connection is possible.
4 If the line is green, click on the ’end’ container to verify the connec-
tion.
A Result window appears, reporting the number of cross connec-
tions created.
If the containers are expanded, you can also see the lines represent-
ing the connections.
Each pair consists of the two tu12CTPs with identical slot numbers,
as illustrated in the figure.
MA199-08 • Issue 1 37
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
Before you start the Read ‘3.2.1 Points to be Noted about Cross Connection Procedures’ on page 33
procedure before starting the cross connection procedure.
The concept of creating a The figure illustrates the stages involved in creating an SNC protected point-
protected connection to-point bidirectional cross connection in Traffic View.
Note: A-Z is known as the protected part, and A-PZ is known as the protect-
ing part.
38 MA199-08 • Issue 1
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
To make a protected In this procedure, it is assumed that the first connection you make is the one
point-to-point you wish to protect, and the second connection you make is the one that pro-
bidirectional connection vides an alternative connection. If traffic cannot travel through the first con-
nection then traffic can be diverted to the second (alternative) connection.
To make an SNC protected point-to-point connection:
Step Action
1 Place the cursor over the termination point that corresponds to the A
termination point in ‘The concept of creating a protected connection’
on page 38, and press mouse button 3.
A pop-up menu appears.
3 Move the cursor to the TP you wish to connect to the ‘start’ TP.
The line is dragged along with the cursor and changes color to green
if connection is possible.
MA199-08 • Issue 1 39
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
Step Action
40 MA199-08 • Issue 1
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
The concept of creating a The figure illustrates the stages involved in creating a double SNC protected
double protected point-to-point bidirectional cross connection in Traffic View.
connection
MA199-08 • Issue 1 41
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
To make a double In this procedure, we use the names for the termination points as they are de-
protected point-to-point scribed in ‘The concept of creating a double protected connection’ on page 41.
bidirectional connection
To make a double SNC protected point-to-point connection:
Step Action
2 Place the cursor over one of the connections in the SNC protected
connection and press mouse button 3.
A pop-up menu appears.
4 Move the cursor to the termination point that you want as the PA ter-
mination point (that is, the TP which is to protect the A termination
point).
Two lines are drawn: one between the PA termination point and the
Z termination point and one between the PA termination point and
the PZ termination point.
42 MA199-08 • Issue 1
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
To abort a connection Any type of connect operation in the Traffic View window can be aborted by
operation performing the following procedure:
Step Action
1 Place the cursor anywhere in the window where the line attached to
the cursor remains red (that is, anywhere except over a free and com-
patible TP).
MA199-08 • Issue 1 43
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
To disconnect one When you disconnect a cross connection, you remove it completely. This
connection means that if you perform the disconnect procedure on one of the connection
parts in an SNC protected connection, all of the connection parts will be dis-
connected.
To disconnect a connection:
Step Action
44 MA199-08 • Issue 1
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
Step Action
To disconnect a bulk of This procedure describes how you disconnect all of the cross connections re-
connections lated to a specific container.
Warning: The procedure deletes ALL connections in the selected container, re-
gardless of whether they were previously created as single connec-
tions or as bulk connections.
Step Action
1 Place the cursor over the container related to the connections that
you wish to disconnect, and press mouse button 3.
A pop-up menu appears.
MA199-08 • Issue 1 45
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
Step Action
If the container is expanded, you can also see that the connections
have disappeared.
46 MA199-08 • Issue 1
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
To unprotect an SNC When you unprotect one of the parts of an SNC protected bidirectional con-
protected connection nection (either the protected part or the protecting part), the part that you are
unprotecting is retained and the other part of the cross connection is removed.
For example, if you unprotect the protected part, the protecting part is re-
moved, and vice versa. The procedure describes how to unprotect either of the
parts.
Note: In some NEs it may only be possible to unprotect the protected part of
an SNC protected connection.
Step Action
1 Place the cursor over one of the parts of the SNC protected connec-
tion and press mouse button 3.
A pop-up menu appears.
MA199-08 • Issue 1 47
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
The concept of The figures below illustrate the possible ways of unprotecting a double SNC
unprotecting a double protected point-to-point bidirectional cross connection in Traffic View.
protected connection
The original double SNC protected connection:
If you unprotect termination point Z, the A-Z connection and the connection
protecting it (PA-Z) are retained:
48 MA199-08 • Issue 1
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
To unprotect a double When you unprotect a double SNC protected bidirectional connection, it is
SNC protected only possible to select one of end points of the ‘main’ connection for unprotec-
connection tion (that is, an end point of the A-Z connection as shown in ‘The concept of
creating a double protected connection’ on page 41). One of the following two
possible connection combinations is retained: A-Z + A-PZ or A-Z + PA-Z, de-
pending on which end point you choose to unprotect.
The procedure describes how to retain either of the two connection combina-
tions.
Step Action
1 Place the cursor over one of the parts of the double SNC protected
connection and press mouse button 3.
A pop-up menu appears.
Note: Even though the pop-up menu contains menu items for un-
protecting either of the four end points, it is only possible to unpro-
tect one of the end points of the ‘main’ part.
MA199-08 • Issue 1 49
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
The concept of The figures below illustrate the ways in which a bidirectional connection can
protecting a point-to- be protected.
point connection
The original bidirectional connection:
If you protect termination point Z, A-Z is the protected connection and A-PZ
is the protecting connection:
If you protect termination point A, Z-A is the protected connection and Z-PA
is the protecting connection:
Note: When the protecting connection is created, the name of the original
point-to-point connection (A-Z) changes to signify the protected part of
an SNC protected connection.
To protect an existing If you want to protect an existing unprotected cross connection, you can use
point-to-point connection the following procedure:
Step Action
50 MA199-08 • Issue 1
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
Step Action
MA199-08 • Issue 1 51
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
Step Action
The concept of locking An SNC protected cross connection has two parts, the protected and the pro-
traffic tecting part (see ‘Concept of an SNC protected point-to-point bidirectional
connection’ on page 30). If you need to divert traffic from one of these parts,
then you need to “lock” the traffic on the other part, that is, force traffic to flow
through the other part.
To lock traffic This procedure describes how to lock traffic in one of the parts of an SNC pro-
tected connection.
Step Action
1 Place the cursor over the connection part through which you wish to
force traffic to flow.
The connection is highlighted and the name of the selected part ap-
pears alongside the cursor.
52 MA199-08 • Issue 1
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
Step Action
To release traffic again, use the procedure described in ‘To release traffic’ on
page 53.
The concept of releasing Releasing traffic on part of an SNC protected cross connection, involves “re-
traffic leasing” the lock placed on it by the Lock Traffic procedure described in ‘To
lock traffic’ on page 52. Once the lock has been released on part of the protect-
ed connection, the NE is able to decide which part of the SNC protected con-
nection to use for traffic.
To release traffic This procedure describes how to release the lock that has been placed on the
traffic in an SNC protected connection using the procedure in ‘3.4.5 Locking
Traffic on an SNC Protected Connection’ on page 52. Once the lock has been
released, the NE can decide which part of the connection to use for traffic.
Step Action
1 Place the cursor over the connection part through which your traffic
was forced to flow.
The connection is highlighted and the name of the selected part ap-
pears alongside the cursor.
MA199-08 • Issue 1 53
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
Step Action
Icon indicating a not- If only one end of a cross connection is visible in the Traffic View window, the
shown connection visible end point (TP) has a special icon attached to it.
To show the other end of If an existing cross connection is not shown as a line because only one of its
a collapsed cross end points (TPs) is shown in the present Traffic View window, you can use this
connection procedure to show the other termination point(s) of the connection:
Step Action
1 Place the cursor over the end point (TP) which is shown in the Traffic
View window (that is, the one which has the special icon shown in
‘Icon indicating a not-shown connection’ on page 54 attached to it).
The TP and the attached icon are highlighted, and the name of the TP
appears alongside the icon.
54 MA199-08 • Issue 1
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
Step Action
To locate traffic in a To find out which connection part in a protected connection is presently car-
protected connection rying traffic:
Step Action
1 Place the cursor over one of the connections in the protected connec-
tion and press mouse button 3.
The pop-up menu for a protected connection appears.
MA199-08 • Issue 1 55
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
Step Action
Overview FOCUS LX 2.0 supports test access connections and the forcing of alarm indi-
cation signals (AIS). The procedures concerning test access groups are de-
scribed here.
• ‘3.7.1 Introduction to Test Access Connections’ on page 56
• ‘3.7.2 Creating Test Access Groups’ on page 57
• ‘3.7.3 Removing Test Access Groups’ on page 63
What is a test access A test access connection is a unidirectional test connection that can be used in
connection? the following ways:
• To allow non-intrusive monitoring of a signal
• To allow looping of a signal
• To allow the splitting of a connection, enabling intrusive access to one side
of the connection and the possibility of AIS signal insertion in the other
side of the connection.
Test access points One end point of a test access connection is a so-called test access point (TAP).
A test access point is a specifically assigned termination point that is not able
to participate in usual cross connections.
Any not-connected termination point (TP) can be changed to a TAP. Similarly,
a not-connected TAP can be changed back to the original TP.
Note: A TAP is managed in the same way as the underlying TP.
56 MA199-08 • Issue 1
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
Test access groups A test access group consists of one, two or three termination points (TPs and/
or TAPs).
• One TP or TAP in the case of only a loopback connection.
• Two TPs in the case of a loopback connection and an ordinary cross con-
nection.
• One TP and one TAP in the case of a monitor connection or a monitor+in-
sertion connection pair.
• Two TPs and one TAP in the case of a monitor or monitor+insertion con-
nection and an ordinary cross connection.
The possible test access groups and how to create them are described in ‘Cre-
ating test access groups’ on page 61.
To convert a TP to a TAP This procedure describes how to convert a termination point to a test access
point.
Note: Any not-connected termination point can be converted to a test access
point.
Step Action
1 Place the cursor over the termination point (TP) you wish to convert
and press mouse button 3.
A pop-up menu appears.
MA199-08 • Issue 1 57
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
Step Action
To make a loopback Loopback test access connections can be applied to termination points and to
test access points, as described in this procedure.
Note: It is not possible to make a loopback if the TP/TAP is already the desti-
nation of another test access connection.
Step Action
1 Place the cursor over the relevant termination point (TP) or test ac-
cess point (TAP) and press mouse button 3.
A pop-up menu appears.
To make a unidirectional This procedure describes how to make an insertion test access connection.
insertion test access
connection Step Action
1 Place the cursor over the test access point (TAP) you wish to create
the insertion connection from and press mouse button 3.
A pop-up menu appears.
58 MA199-08 • Issue 1
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
Step Action
To make a unidirectional This procedure describes how to make a monitor test access connection.
monitor test access
connection Step Action
1 Place the cursor over the termination point (TP) you wish to create
the monitor connection from and press mouse button 3.
A pop-up menu appears.
MA199-08 • Issue 1 59
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
Step Action
3 Move the cursor to the TAP you wish to connect to the TP.
The line is dragged along with the cursor and changes color to green
if connection is possible.
To force AIS insertion This procedure describes how to insert an alarm indication signal (AIS) in the
continuing signal.
Step Action
1 Place the cursor over the termination point (TP) where you wish to
insert an AIS signal and press mouse button 3.
A pop-up menu appears.
60 MA199-08 • Issue 1
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
Creating test access The table shows how to create the valid test access groups:
groups
Test Access Group Directions
MA199-08 • Issue 1 61
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
62 MA199-08 • Issue 1
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
To convert a TAP to a TP This procedure describes how to convert a test access point to a termination
point.
Note: Test access points can only be converted to termination points if they
are not involved in any test access connections.
Step Action
1 Place the cursor over the test access point (TAP) you wish to convert
and press mouse button 3.
A pop-up menu appears.
To disconnect a This procedure describes how to disconnect a loopback test access connection.
loopback
Step Action
1 Place the cursor over the termination point (TP) or test access point
(TAP) with the loopback and press mouse button 3.
A pop-up menu appears.
MA199-08 • Issue 1 63
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
1 Place the cursor over one of the end points of the connection and
press mouse button 3.
A pop-up menu appears.
1 Place the cursor over one of the end points of the connection and
press mouse button 3.
A pop-up menu appears.
64 MA199-08 • Issue 1
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
Step Action
To stop AIS insertion This procedure describes how to stop the insertion of an alarm indication sig-
nal (AIS) in the continuing signal.
Step Action
1 Place the cursor over the termination point (TP) where you wish to
stop the AIS signal insertion and press mouse button 3.
A pop-up menu appears.
2 Select the menu item Test Access → Stop Force AIS Insertion.
The TP’s forceAisInsertion attribute is set to disabled.
MA199-08 • Issue 1 65
FOCUS NM2100nm 3 Working with Cross Connections in Traffic View
Managing Traffic in a Network Element using Traffic View
66 MA199-08 • Issue 1
FOCUS NM2100nm 4 Equipment-Specific Information
Managing Traffic in a Network Element using Traffic View
4 Equipment-Specific Information
Overview For each NE type, the relevant part of the entity hierarchy is shown, to allow
you to see which entities from the hierarchy are represented in Traffic View
and where they are placed in the window. In addition, the naming conven-
tions are described.
The contents of the entity The entity hierarchy is set up according to the following rules:
hierarchies
• The grey boxes represent entities the number of which depends upon the
configuration.
• The white boxes represent entities that are always present if their parent
entities exist.
• The numbers beneath some of the boxes indicate the possible number of
boxes. A single number means that there is always this exact number of the
particular box. Two numbers separated by a comma mean that the number
of boxes is one of the two numbers. Two numbers separated by an ellipsis
(...) mean that the number of boxes varies between these two numbers.
Configuration Traffic View uploads information about the traffic configuration of the NE in
information about TPs question. Based on this information it can create a graphical representation of
the CTPs and TTPs and create names for them.
TTP names TTPs are named by four numbers separated by “–”. These four numbers are:
• Rack number for the hardware that implements the TTP
• Subrack number for the hardware that implements the TTP
• Slot number for the hardware that implements the TTP
• Connector number or a consecutive number.
Note: The different types of NEs supported by the NM2100nm system are
represented differently. Therefore, general terms such as rack, subrack,
slot, connector are interpreted differently by the system depending on
the actual type of NE. A description of the terms can be found in the
hardware manual, as well as the User Manual for the Element Access,
for the NE in question.
Example: A TTP named 1–1–2–1 can be located in rack No. 1, subrack No. 1,
slot No. 2 and connector/consecutive No. 1.
MA199-08 • Issue 1 67
FOCUS NM2100nm 4 Equipment-Specific Information
Managing Traffic in a Network Element using Traffic View
CTP names At the physical, RS- and MS layer, a CTP has the same name as its server TTP
(that is, the TTP representing the signal that contains the timeslot represented
by the CTP). At the VC-4, VC-3 and VC-12 layers, the CTP is named by the
same four numbers as the server TP followed by an additional qualification.
Example at the VC-4 layer: A CTP named 1–1–2–1–2 can be located in rack No.
1, subrack No. 1, slot No. 2, connector/consecutive No. 1 and AUG No. 2.
Example at the VC-3 layer: A CTP named 1–2–2–2–2 can be located in rack No.
1, subrack No. 2, slot No. 2, connector/consecutive No. 2 and TUG-3 No. 2.
Example at the VC-12 layer: A CTP named 1–2–2–2–2–3–1 can be located in
rack No. 1, subrack No. 2, slot No. 2, connector/consecutive No. 2, TUG-3 No.
2, TUG-2 No. 3 and TU-12 No. 1.
In which NEs? Each type of NE only allows the use of some of the available cross connection
types. The table describes which connections can be made.
FOCUS AC1 X X
(bidirectional) (single)
FOCUS LX X X
(bidirectional) (single)
FOCUS AC4 X X
(bidirectional) (single)
Marconi XC-1 X X
(bidirectional) (both single and double)
Marconi ADM-1 X X
(bidirectional) (single) (the ADM-1R
only)
Marconi MSH11 X X
(bidirectional) (single)
68 MA199-08 • Issue 1
FOCUS NM2100nm 4 Equipment-Specific Information
Managing Traffic in a Network Element using Traffic View
Names in cross The names given to the parts of the cross connections in Traffic View depend
connections on the NE in question. FOCUS network elements use one naming convention,
and Marconi NEs use another convention, as described in the table below. The
illustrations in the table are provided for easy identification of the relevant
cross connection part.
Note: The name is shown when you place the mouse cursor on the connection
part.
MA199-08 • Issue 1 69
FOCUS NM2100nm 4 Equipment-Specific Information
Managing Traffic in a Network Element using Traffic View
Overview This section describes how the traffic-related entities of a FOCUS 2500 are
shown in the Traffic View window.
4.4.1 Relationship between Traffic View and the Entity Hierarchy for FOCUS
2500
Entities shown in the The figure shows a labelling of the various objects (entities) in the Traffic View
FOCUS 2500 Traffic of a FOCUS 2500, corresponding to the labelling in ‘Entity hierarchy of a FO-
View window CUS 2500’ on page 70.
Entity hierarchy of a The figure shows the entity hierarchy of a FOCUS 2500 TM4 or TM16. The la-
FOCUS 2500 bels correspond to the labelling in the figure in ‘Entities shown in the FOCUS
2500 Traffic View window’ on page 70.
70 MA199-08 • Issue 1
FOCUS NM2100nm 4 Equipment-Specific Information
Managing Traffic in a Network Element using Traffic View
Entities used for The figure shows the entities of the FOCUS 2500 TM4 and TM16 which are
identifying TPs used for determining the NE’s traffic configuration.
TTP and CTP names of a In TM4 and TM16 equipment TTPs and CTPs exist at the physical, RS, MS and
FOCUS 2500 VC-4 layer.
• Rack number: 1
• Subrack number: 1
• Slot number:
– 1 for Aggregate
– 3 for Tributary 1 to Tributary 4
– 4 for Tributary 5 to Tributary 8
– 5 for Tributary 9 to Tributary 12
– 6 for Tributary 13 to Tributary 16
• Connector number:
1 – 4 for the four connectors on each tributary board
• AUG number:
– 1 for the tributary side
– 1 – 16 for the aggregate side.
Examples: In the figure in ‘Entities shown in the FOCUS 2500 Traffic View
window’ on page 70, A and B are called Tributary 1, and C is called Tributary 4.
MA199-08 • Issue 1 71
FOCUS NM2100nm 4 Equipment-Specific Information
Managing Traffic in a Network Element using Traffic View
Overview This section describes how the traffic-related entities of a Marconi ADM-1 are
shown in the Traffic View window.
4.5.1 Relationship between Traffic View and the Entity Hierarchy for Marconi
ADM-1
Entities shown in the Three different types of Marconi ADM-1 network element exist – ADM-1,
Marconi ADM-1R Traffic ADM-1R and TM-1. However, as these are very alike, no distinction is made
View window between them in the Traffic View window, except that SNC protection is only
available in ADM-1R. The figure shows a labelling of the various objects (en-
tities) in the Traffic View of a Marconi ADM-1R, corresponding to the label-
ling in ‘Entity hierarchy of a Marconi ADM-1R’ on page 73.
72 MA199-08 • Issue 1
FOCUS NM2100nm 4 Equipment-Specific Information
Managing Traffic in a Network Element using Traffic View
Entity hierarchy of a The figure shows the entity hierarchy of a Marconi ADM-1R. The labels corre-
Marconi ADM-1R spond to the labelling in the figure in ‘Entities shown in the Marconi ADM-1R
Traffic View window’ on page 72.
Entities used for The figure shows the entities of the Marconi ADM-1 which are used for deter-
identifying TPs mining the NE’s traffic configuration.
MA199-08 • Issue 1 73
FOCUS NM2100nm 4 Equipment-Specific Information
Managing Traffic in a Network Element using Traffic View
TTP and CTP names of a The TP names are defined for Marconi ADM-1, Marconi ADM-1R and TM-1.
Marconi ADM-1R CTPs and TTPs exist at all layers.
• Rack number: 1
• Subrack number: 1
• Slot number:
– 1 for Aggregate West (working)
– 2 for Aggregate East (working)
– 3 for Tributary STM1 1 or Tributary 2Mbit 1
– 4 for Tributary STM1 2 or Tributary 2Mbit 2
– 5 for Tributary STM1 3 or Tributary 2Mbit 3
– 6 for Tributary STM1 4 or Tributary 2Mbit 4
• Connector number:
– 1 for STM-1 interfaces
– 1 – 16 for 2 Mbit/s interfaces (for VC12 1 to VC12 16)
• AUG number: 1
• TUG-3 number:
1 – 3 for TUG3 1 to TUG3 3
• TUG-2 number:
Derived from the number of VC12 (see the table in ‘TUG-2 and TU-12 num-
bers’ on page 74)
• TU-12 number:
Derived from the number of VC12 (see the table in ‘TUG-2 and TU-12 num-
bers’ on page 74)
TUG-2 and TU-12 The table shows the TUG-2 numbers and TU-12 numbers derived from the
numbers VC-12 number.
VC12 1 1 1
VC12 2 1 2
VC12 3 1 3
VC12 4 2 1
VC12 5 2 2
VC12 6 2 3
VC12 7 3 1
VC12 8 3 2
VC12 9 3 3
VC12 10 4 1
74 MA199-08 • Issue 1
FOCUS NM2100nm 4 Equipment-Specific Information
Managing Traffic in a Network Element using Traffic View
VC12 11 4 2
VC12 12 4 3
VC12 13 5 1
VC12 14 5 2
VC12 15 5 3
VC12 16 6 1
VC12 17 6 2
VC12 18 6 3
VC12 19 7 1
VC12 2 7 2
VC12 21 7 3
Example of a CTP name The TU12CTP labelled H in the figure in ‘Entities shown in the Marconi ADM-
1R Traffic View window’ on page 72 has the full name:
Aggregate West_Working TUG3 3 VC12 4.
Rack No. is 1, subrack No. is 1, slot No. for Aggregate West is 1, connector No.
is 1. The TUG3 number for TUG3 3 is 3. VC12 4 corresponds to the TUG2 num-
ber 4 and TU-12 number 1. The ID of the CTP is therefore:
1-1-1-1-3-4-1.
MA199-08 • Issue 1 75
FOCUS NM2100nm 4 Equipment-Specific Information
Managing Traffic in a Network Element using Traffic View
Overview This section describes how the traffic-related entities of a Marconi MSH11 are
shown in the Traffic View window.
4.6.1 Relationship between Traffic View and the Entity Hierarchy for Marconi
MSH11
Entities shown in the The figure shows a labelling of the various objects (entities) in the Traffic View
Marconi MSH11 Traffic of a Marconi MSH11, corresponding to the labelling in ‘Entity hierarchy of a
View window Marconi MSH11’ on page 77.
76 MA199-08 • Issue 1
FOCUS NM2100nm 4 Equipment-Specific Information
Managing Traffic in a Network Element using Traffic View
Entity hierarchy of a The figure shows the entity hierarchy of a Marconi MSH11. The labels corre-
Marconi MSH11 spond to the labelling in the figure in ‘Entities shown in the Marconi MSH11
Traffic View window’ on page 76.
Entities used for The figure shows the entities of the Marconi MSH11 which are used for deter-
identifying TPs mining the NE’s traffic configuration.
MA199-08 • Issue 1 77
FOCUS NM2100nm 4 Equipment-Specific Information
Managing Traffic in a Network Element using Traffic View
TTP and CTP names of a The TP names are defined for Marconi MSH11. CTPs and TTPs exist at all lay-
Marconi MSH11 ers.
• Rack number: 1
• Subrack number: 1
• Slot number:
– 1 for Aggregate West (working)
– 2 for Aggregate East (working)
– 3 for Tributary STM1 1 or Tributary 2Mbit 1
– 4 for Tributary STM1 2 or Tributary 2Mbit 2
– 5 for Tributary STM1 3 or Tributary 2Mbit 3
– 6 for Tributary STM1 4 or Tributary 2Mbit 4
• Connector number:
– 1 for STM-1 interfaces
– 1 – 16 for 2 Mbit/s interfaces (for VC12 1 to VC12 16)
– 1 – 3 for 34 Mbit/s interfaces (for VC12 1 to VC12 16)
• AUG number: 1
• TUG-3 number:
1 – 3 for TUG3 1 to TUG3 3
• TUG-2 number:
Derived from the number of VC12 (see the table in ‘TUG-2 and TU-12 num-
bers’ on page 78)
• TU-12 number:
Derived from the number of VC12 (see the table in ‘TUG-2 and TU-12 num-
bers’ on page 78)
TUG-2 and TU-12 The table shows the TUG-2 numbers and TU-12 numbers derived from the
numbers VC-12 number.
VC12 1 1 1
VC12 2 1 2
VC12 3 1 3
VC12 4 2 1
VC12 5 2 2
VC12 6 2 3
VC12 7 3 1
VC12 8 3 2
VC12 9 3 3
VC12 10 4 1
78 MA199-08 • Issue 1
FOCUS NM2100nm 4 Equipment-Specific Information
Managing Traffic in a Network Element using Traffic View
VC12 11 4 2
VC12 12 4 3
VC12 13 5 1
VC12 14 5 2
VC12 15 5 3
VC12 16 6 1
VC12 17 6 2
VC12 18 6 3
VC12 19 7 1
VC12 2 7 2
VC12 21 7 3
Example of a CTP name The TU12CTP labelled H in the figure in ‘Entities shown in the Marconi
MSH11 Traffic View window’ on page 76 has the full name:
Aggregate East_Working TUG3 1 VC12 1.
Rack No. is 1, subrack No. is 1, slot No. for Aggregate East is 2, connector No.
is 1. The TUG3 number for TUG3 1 is 1. VC12 1 corresponds to the TUG-2 num-
ber 4 and TU-12 number 1. The ID of the CTP is therefore:
1-1-2-1-1-4-1.
MA199-08 • Issue 1 79
FOCUS NM2100nm 4 Equipment-Specific Information
Managing Traffic in a Network Element using Traffic View
Overview This section describes how the traffic-related entities of a Marconi XC-1
(MSH80, MSH83 and MSH84) are shown in the Traffic View window.
Selecting which When you open the Traffic View of a Marconi XC-1 (using one of the methods
subracks to display in the described in ‘1.2 Starting up Traffic View’ on page 15), a Subrack Selection
Marconi XC-1 Traffic window appears first, to allow you to specify which subracks are to be dis-
View window played in the Traffic View window.
In this window, you can move subracks from the Shown: list to the Not shown:
list to reduce the amount of subracks shown in the Traffic View window. When
you click on the OK button, the subracks in the Shown: list are displayed in the
Traffic View window.
80 MA199-08 • Issue 1
FOCUS NM2100nm 4 Equipment-Specific Information
Managing Traffic in a Network Element using Traffic View
4.7.2 Relationship between Traffic View and the Entity Hierarchy for Marconi
XC-1
Entities shown in the Three different types of Marconi XC-1 network element exist – MSH80,
Marconi XC-1 Traffic MSH83 and MSH84. However, as the main difference between them is their
View window size, no distinction is made between them in the Traffic View window. The fig-
ure shows a labelling of the various objects (entities) in the Traffic View of a
Marconi XC-1 (MSH80), corresponding to the labelling in ‘Entity hierarchy of
Marconi XC-1’ on page 82.
MA199-08 • Issue 1 81
FOCUS NM2100nm 4 Equipment-Specific Information
Managing Traffic in a Network Element using Traffic View
Entity hierarchy of The figure shows the entity hierarchy of an MSH8x_04/MSH8x_62 network
Marconi XC-1 element. The labels correspond to the labelling in the figure in ‘Entities shown
in the Marconi XC-1 Traffic View window’ on page 81.
82 MA199-08 • Issue 1
FOCUS NM2100nm 4 Equipment-Specific Information
Managing Traffic in a Network Element using Traffic View
Entities used for The figure shows the entities of the Marconi XC-1 which are used for deter-
identifying TPs mining the NE’s traffic configuration. Marconi XC-1 MSH80 is used as an ex-
ample, but the principle of numbering applies to all Marconi XC-1 NEs.
TTP and CTP names of a The TP names are defined for Marconi XC-1 MSH80, MSH83 and MSH84.
Marconi ADM-1R CTPs and TTPs exist at all layers.
• Rack number: 1
• Subrack number:
– 1 – 48 for Traffic2-34 1 to Traffic2-34 48
or 1 – 48 for Traffic140-155 1 to Traffic140-155 48 for MSH80
– 1 – 14 for Traffic2-34 1 to Traffic2-34 14
or 1 – 14 for Traffic140-155 1 to Traffic140-155 14 for MSH83
– 1 – 86 for Traffic2-34 1 to Traffic2-34 86
or 1 – 86 for Traffic140-155 1 to Traffic140-155 86 for MSH84
• Slot number:
1 – 8 for 16x2Mbit 1 to 16x2Mbit 8 or 140Mbit 1 to 140Mbit 8
or the STM1 1 to STM1 8 or 3x34Mbit 1 and/or 3x34Mbit 5
• Connector number:
– 1 for STM-1 interfaces
– 1 for 140 Mbit/s interfaces
– 1 – 16 for 2 Mbit/s interfaces (the VC12 1 to VC12 16)
• AUG number: 1
MA199-08 • Issue 1 83
FOCUS NM2100nm 4 Equipment-Specific Information
Managing Traffic in a Network Element using Traffic View
• TUG-3 number:
1 – 3 for TUG3 1 to TUG3 3
• TUG-2 number:
Derived from the number of VC12 (see the table in ‘TUG-2 and TU-12 num-
bers’ on page 84)
• TU-12 number:
Derived from the number of VC12 (see the table in ‘TUG-2 and TU-12 num-
bers’ on page 84)
TUG-2 and TU-12 The table shows the TUG-2 numbers and TU-12 numbers derived from the
numbers VC-12 number.
VC12 1 1 1
VC12 2 1 2
VC12 3 1 3
VC12 4 2 1
VC12 5 2 2
VC12 6 2 3
VC12 7 3 1
VC12 8 3 2
VC12 9 3 3
VC12 10 4 1
VC12 11 4 2
VC12 12 4 3
VC12 13 5 1
VC12 14 5 2
VC12 15 5 3
VC12 16 6 1
VC12 17 6 2
VC12 18 6 3
VC12 19 7 1
VC12 2 7 2
VC12 21 7 3
84 MA199-08 • Issue 1
FOCUS NM2100nm 4 Equipment-Specific Information
Managing Traffic in a Network Element using Traffic View
Examples of object The table lists both the full name of the objects labelled A to H in the figure in
names in Marconi XC-1 ‘Entities shown in the Marconi MSH11 Traffic View window’ on page 76, as
Traffic View well as the shortened name given to them in the Traffic View window.
Object Label in
Full Name of Object Name in Traffic View
Type Figure
MA199-08 • Issue 1 85
FOCUS NM2100nm 4 Equipment-Specific Information
Managing Traffic in a Network Element using Traffic View
86 MA199-08 • Issue 1
FOCUS NM2100nm 5 Error Messages
Managing Traffic in a Network Element using Traffic View
5 Error Messages
Introduction The error conditions or irregularities that may be detected and reported by
FOCUS NM2100nm Traffic View are listed here and briefly explained. The er-
ror messages are listed alphabetically.
Note: Error messages related to the core system (TeMIP) of FOCUS
NM2100nm and to the relevant NE’s Element Access are not included.
Responses to successful operations are not included either.
Cross connection could not be set up: Connections of this type can not go across two different STM-1 ports
In a Marconi XC-1, you have attempted to set up a cross connection from an
AU-4 to a VC-4 on a different STM-1 interface.
Cross connection could not be set up: Violation of limitation in protection mechanism
In a Marconi ADM-1, you have attempted to set up a protected cross connec-
tion from a 2 Mbit/s port to two TU-12s, which are not in the same time slot
in the two aggregate interfaces.
MA199-08 • Issue 1 87
FOCUS NM2100nm 5 Error Messages
Managing Traffic in a Network Element using Traffic View
88 MA199-08 • Issue 1
FOCUS NM2100nm Index
Managing Traffic in a Network Element using Traffic View
Index
A accessing operations 25
changing 44
Abbreviations 6
disconnecting 44
Aborting a connection operation 43
disconnecting a bulk 45
AIS signal
finding traffic in protected 55
inserting 60
icon when hidden 12
stopping 65
icon when one end point hidden 54
Alarm indication 10
icons representing 12
Arrows
identifying 13
use of 6
making 33
names 69
B showing other end 54
Bold types of 29
use of 5
Bulk Connect menu item 35, 36
Bulk connections
D
concept of 32 Disconnect Insertion menu item 64
disconnecting 45 Disconnect Loopback menu item 63
making 35, 36 Disconnect menu item 45
Bulk Disconnect menu item 45 Disconnect Monitor menu item 65
Disconnecting a connection 44
Disconnecting a loopback 63
C Disconnecting a monitor (Test access) 64
Changing a cross connection 44 Disconnecting an insertion (Test access) 64
Closing the Traffic View window 28 Disconnecting bulk connections 45
Collapse menu item Dismiss button 22
All item 23 Double SNC protected point-to-point
Collapsing bidirectional connections
a single container/TP 23 concept of 31
all containers/TPs at the same time 23 making 41
Collapsing containers/TPs 23 names in 69
Configuration menu unprotecting 48
Exit item 28
Naming Convention item 20
Show/Hide Ports item 21
E
Entity hierarchy
Connect Insertion menu item 59
for FOCUS 2500 70
Connect Loopback menu item 58
for Marconi ADM-1R 72
Connect menu item
for Marconi MSH11 76
PointToPoint Bid item 34
for MarconiXC-1 81
SNC Protected PointToPoint Bid item 39
rules for 67
Connect Monitor menu item 60
Error messages 87
Connection Parameters window 51
Exit menu item 28
Containers
Expand menu item
collapsing 23
All item 22
expanding 22
Connected item 23
icons representing 12
Free item 22
identifying 13
Expanding
Convert to TAP menu item 58
a single container/TP 23
Convert to TP menu item 63
all connected containers/TPs at the same
Cross connections 29
time 23
aborting an operation 43
MA199-08 • Issue 1 89
FOCUS NM2100nm Index
Managing Traffic in a Network Element using Traffic View
90 MA199-08 • Issue 1
FOCUS NM2100nm Index
Managing Traffic in a Network Element using Traffic View
T U
Termination points
Unprotect <Name of TP> menu item 47, 49
accessing operations 25
Unprotecting a bidirectional connection 47
choosing naming convention for 20
Unprotecting a double SNC protected
collapsing 23
bidirectional connection 48
expanding 22
icons representing 12
identifying 13 W
mapping names in NM2100nm system 67 Work Area 9
naming in FOCUS 2500 71
naming Marconi ADM-1 73
naming Marconi MSH11 77
Z
Zoom 10
naming Marconi XC-1 83
icons 10
Test access 56
converting TAP 63
creating TAP 57
MA199-08 • Issue 1 91
FOCUS NM2100nm Index
Managing Traffic in a Network Element using Traffic View
92 MA199-08 • Issue 1