LCT and LCTS Operator's Reference

LCT and LCTS Operator’s Reference
Marconi OMS 1410 Release 1.0 Revision B
OPERATING INSTRUCTIONS
Copyright
© Copyright Ericsson AB 2009. All rights reserved.
Disclaimer
No part of this document may be reproduced in any form without the written
permission of the copyright owner.
The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use
of this document.
All trademarks and registered trademarks mentioned in a document of this

collection are the property of their respective holders.
Trademark List
Ericsson Telefonaktiebolaget LM Ericsson
1553-CXP 901 4102/10 Uen F 2009-09-25

Contents
Contents
1 Getting Started with the OMS 1410 Local Craft Terminal 1

1.1 Requirements 1
1.2 Installation 1
1.3 Use Marconi OMS 1410 LCT 1
1.4 User Management 3
2 Use the Marconi OMS 1410 LCT 11

2.1 Desktop 11
2.2 Management Tree and Browser 11
2.3 Notification List 15
3 NE Maintenance 31
3.1 Operation 31
3.2 Licence Handling 41
3.3 Inventory 43
4 The Commissioning Wizard 45

4.1 Introduction 45
4.2 Starting the Commissioning Wizard 45
4.3 Basic Setup 45
4.4 Time Setup 46
4.5 Shelf 47
4.6 Expected Port Modes 48
4.7 Port Interface Modules 49
4.8 Port Interface Settings 50
4.9 SDH Synchronization 51
4.10 Alarm Configuration 52
4.11 Finish 56
4.12 Management from the Management Tree 56
5 Data Communication Network (DCN) 59

5.1 Introduction 59
5.2 DCN Page 59
6 Ethernet Screens 67
1553-CXP 901 4102/10 Uen F 2009-09-25

6.1 Ethernet Port Attributes 67

6.2 The Link OAM Screen 73
6.3 Class of Service (CoS) Screen 77
6.4 RMON (Remote Monitoring) 79
6.5 Link Capacity Adjustment Scheme (LCAS) 79
7 Layer 2 Configuration 83
7.1 Introduction 83
7.2 Bridge 83
7.3 Miscellaneous 86
7.4 Manage VLAN 91
7.5 VLAN Provisioning 92
8 Ethernet Services Wizard 95

8.1 Recommended Reading 95
8.2 Ethernet Service Wizard 95
8.3 Create a UNI 97
8.4 Create Ethernet Service 101
8.5 Management Tree 108
9 SDH 117
9.1 SDH Screen 117
9.2 SDH Protection Management 122
9.3 SDH Cross Connection Management 127
10 PDH 131
10.1 Configure a Slot as PDH 131
11 Cross Connections 139

11.1 Cross Connection Management 139
11.2 Modify Cross Connections 141
11.3 Protect Point-To-Point Cross Connections 141
12 Removal of Provisioning from Entities 147

12.1 Removal of Provisioning from Slots 147
12.2 Removal of Provisioning from LAN Ports 147
12.3 Removal of Provisioning from WAN Ports 147
12.4 Removal of Provisioning from PDH Ports 148
12.5 Removal of Provisioning from SDH Ports 148
1553-CXP 901 4102/10 Uen F 2009-09-25

Getting Started with the OMS 1410 Local Craft Terminal
1 Getting Started with the OMS 1410 Local

Craft Terminal
This chapter describes how to get started with the Marconi OMS 1410 Local
Craft Terminal (LCT):
• Installation
• Logon/Logout
• User Management
1.1 Requirements
Operating system: Windows 2000; Windows XP.
Required disk space for the Marconi OMS 1410 LCT installation is a minimum
110 Mbytes.
1.2 Installation
1.2.1 Install Marconi OMS 1410 LCT

1. Insert the Marconi OMS 1410 LCT Software CD into the target PC, or
access a downloaded installation file (approximately 45MB).
2. Run OMS 1410 Craft.exe to launch the install shield.
3. Follow the instructions given in the Install Wizard.
1.2.2 Un-install Marconi OMS 1410 LCT

• Either:
0 Select Start > Programs > OMS 1410 Craft > Un-install and follow
the instructions given on screen.
0 Select Start > Settings > Control Panel > Add/Remove Programs.
1.3 Use Marconi OMS 1410 LCT

This section describes how to start up the Marconi OMS 1410 LCT and connect
to a Network Element (NE).
1553-CXP 901 4102/10 Uen F 2009-09-25 1

1.3.1 Start the Program
1.3.1.1 Start the Program on Windows
1. Select Programs from the Start menu.
2. Locate and select the Marconi OMS 1410 LCT program.
Figure 1 Marconi OMS 1410 LCT Program Menu on Windows
The system presents the Marconi OMS 1410 LCT logon window with
information about the product name and release edition. See Section 1.3.2
Logon on page 2.
1.3.1.2 SNMP Trap Distributor
When you launch the Marconi OMS 1410 LCT, a trap distributor application
automatically starts in the background.
Figure 2 SNMP Trap Distributor
The application is in use when there is more than one session of the Marconi
OMS 1410 LCT running on the same PC. Traps from different NEs are directed
to the correct session of the Marconi OMS 1410 LCT.
1.3.2 Logon
1.3.2.1 Logon Screen
Figure 3 Logon Window
2 1553-CXP 901 4102/10 Uen F 2009-09-25

• IP: The address of the NE
• User: Default = admin
• Password: Default = admin
The system validates the logon input and opens the Marconi OMS 1410 LCT
Desktop.
1.3.2.1.1 Failed Logon
If the logon input is not valid, the system displays an error message. You can
open the error log to see details about the error, see the figure above.
1.3.2.2 Logon with the LCT Port
Requirements:
• Ethernet cable (RJ-45 connector in both ends) that connects the OMS 1410
to a PC (crossover or straight cable, auto-detected and supported)
• PC with Marconi OMS 1410 LCT installed
1. Attach one connector to the network port of a PC with the LCT installed.
2. Attach the other RJ-45 connector, to the LCT port on one of the System
Controller (SC) modules.
3. Start the Marconi OMS 1410 LCT. (See Section 1.3.2 Logon on page 2
above.)
1.3.3 Log Off
• Select Exit from the File menu or press Alt and F4
• Right click the Trap Distributor icon in the system tray and select Shutdown
1.4 User Management

The User Management application allows system administrators to add and
remove users on an NE. Other users may only change their own settings.
1.4.1 Open NE User Management

From the menu, select: Equipment > NE User Management.
1553-CXP 901 4102/10 Uen F 2009-09-25 3

1.4.2 Users
Figure 4 User Management
This window presents the registered users for the NE. You can add, edit and
delete users here.
1.4.2.1 Default User
On every NE there is a default user with administrator rights for the initial logon.
• User: admin
• Password: admin
Note: To restrict access to the NE you should delete the default user and
create a new as described below.
• Log on using the default user account
• Create a new system administrator user
• Log off
• Log on using the new system administrator user
• Delete the default user
Only the system administrator has privileges to change the password and trap
settings for other users.
4 1553-CXP 901 4102/10 Uen F 2009-09-25

Table 1 User Categories

User role Privileges Access
• Create/delete user Super
System Administrator
• List users
Network Administrator Change own password Read-write
Operator Change own password Read-write
Guest Change own password Read-only
1.4.2.2 Add a User
Only users with administrator rights can edit other users.
1. Click the Add icon on the tool bar, and the Create New User window
appears:
2. Enter the user name, 6-34 characters.
3. Enter the password, 6-34 characters and retype it to confirm the accuracy.
4. Press OK.
5. Decide the user’s role (see Table 1 on page 5).
6. Set the expiration date for the user and password. The default value is one
year for the user account and six weeks for the password.
7. Save.
1.4.2.3 Edit a User
Administrators can edit the settings for other users.
1. Select the user you want to edit from the users list.
• To change the user’s password, click the Change Password button
1553-CXP 901 4102/10 Uen F 2009-09-25 5

0 Enter the new password (6-34 characters)
0 Retype the new password
0 Click OK
• To change the user’s role, select the drop down button at the end of the
role field and select a new role from the drop down list
• To change the user’s account expire date, or the user’s password

expiry date, click the calendar icon at the end of the appropriate field
and select a new date
2. Save.
1.4.2.4 Delete a User
1. Select the user you want to delete.
2. Click the Delete icon on the tool bar.
3. Click Yes to confirm.
1.4.2.5 Change Current User Password
All users can change their own password.
From the desktop menu, select: Equipment > Change Current User Password.
Figure 5 Change Current User Password
6 1553-CXP 901 4102/10 Uen F 2009-09-25

If you forget or lose your password, a user with administrator rights must open
your user profile and give you a new password.
1.4.2.6 Feature Permission
The role associates users with permission on identified system features in a

feature-to-role matrix. The roles are pre-defined and cannot be edited.
If the feature under security management is associated with a system

application, the permission is used to control the execution of the application,
the access to reading attributes and changing attributes.
If the feature under security management is associated with accessing NEs,

the permission is used to control the capability to monitor the NE, commission
the NE or manage services provided by the NE.
If the feature under security management is associated with accessing the

system information model, the permission is used to control the creation,
modification and deletion of objects within the model.
Table 2 Feature-to-Role Matrix

System Admini Network Admi
strator nistrator Operator Guest
Security Management
Audit Trail report R/W
Manage Users R/W R
Network Element Management
Slot configuration R/W R/W R R
MCN configuration R/W R/W R R
NE restart R/W R/W R/W
Software download R/W R/W R R
Configuration
backup/restore R/W R/W R R
Port enable/disable R/W R/W R/W R
Bandwidth Management R/W R/W R/W R
VLAN Management R/W R/W R/W R
Notification Management R/W R/W R/W R
Cross Connect setting R/W R/W R/W R
Note: R/W = Read/Write access

R = Read Only access
1.4.3 Subscribe for Alarms

The Marconi OMS 1410 LCT is registered as a trap receiver, and can poll
the NE for all current alarms and report alarms and events to the IP address
of the LCT by SNMP traps.
1553-CXP 901 4102/10 Uen F 2009-09-25 7

The SNMP traps are mapped to Notifications in the LCT.
The Notification Subscriber table on the NEs allows 16 instances of trap

receivers (users) to exist at the same time. The NE will always attempt to send
the traps to all the configured trap receivers.
In some situations, the NE may generate a large number of traps (alarm

storms). Under these special circumstances, the transmit buffers of the NE may
become overloaded, and it may not be possible to send all traps as intended.
This problem increases with the number of configured trap receivers and when
the DCN capacity is low.
To prevent loss of traps towards trap receivers, we recommend no more than

three instances configured as trap receivers. The Management Communication
Network (MCN) should also be designed with sufficient capacity. The trap
receivers may also poll the NE to check for updates to the alarm states, but
note that this causes further traffic increase in the MCN.
1.4.3.1 Alarm Notification Severity
The severity of an alarm notification can either be reported from the NE or must
be defined in the notification mapping.
1.4.3.2 Trap to Notification Mapping
The interpretation of alarm and event is slightly different in the NE and the
LCT. The mapping rules applied to the SNMP traps are illustrated in Figure
6 on page 8.
Figure 6 Trap to Notification Mapping
The TrapAlarmRaised and TrapAlarmCleared traps are mapped to Alarm

Notification. The time-stamp in the trap is used together with the severity. OMS
1410 has severity in the trap. This severity is used in the Notification.
If the Alarm Notification Clearable is set to True, it indicates that the

management system should expect a TrapAlarmCleared for this alarm.
8 1553-CXP 901 4102/10 Uen F 2009-09-25

Alarms that the NE is not able to clear, have the Clearable attribute set to
False These traps will be mapped to an Alarm Notification. The severity and
time-stamp from the traps are used in the Alarm Notification.
Other TrapAlarmEvents are mapped to Event Notifications. These have no

severity, but a Status defining the type of event. For example, info, confirm,
and so on. The severity in the trap might be used as the Status in the Event
Notification.
1.4.3.2.1 Unknown Traps
If the LCT receives a trap and there exists no mapping to any type of
notification, a notification will be generated. The notification contains all the
information that was received in the trap.
1553-CXP 901 4102/10 Uen F 2009-09-25 9

10 1553-CXP 901 4102/10 Uen F 2009-09-25

Use the Marconi OMS 1410 LCT
2 Use the Marconi OMS 1410 LCT
This chapter presents the Marconi OMS 1410 LCT desktop with its tools, menu
items, views and general navigation and editing functions.
2.1 Desktop
When you have logged on to an NE, the desktop opens with the initial view of
the NE. You will see the name, location and alarm status and so on. You can
start to explore and configure the NE with the different views available. The
figure below shows the desktop with main views indicated:
Figure 7 Marconi OMS 1410 LCT Desktop Overview
The following sections explain more about the different views.
2.2 Management Tree and Browser

This is the main tool to explore and configure the NE. In the Management Tree,
the structure of the items of the NE are presented in a folder-like structure.
Items can be expanded to show sub-items. In the browser window to the right,
you can view and edit the attributes of the selected item.
The next sections present these windows and explain how to navigate and
work with them.
1553-CXP 901 4102/10 Uen F 2009-09-25 11

2.2.1 The Management Tree
If you are familiar with the windows folder structure, the navigation in the
Management tree is simple and intuitive. Here is an overview:
Figure 8 Management Tree
Select an item:
• Select with the mouse
• Use the Up and Down arrows on the keyboard
• Type the first letter of the item’s name
Expand and close an item
• Double click
• Use the Right and Left arrow on the keyboard
12 1553-CXP 901 4102/10 Uen F 2009-09-25

Overlay icons indicate various conditions on items, as shown in the figure

below where a port is protected. If you hold the pointer over the item, a tool-tip
describes the condition.
Figure 9 Overlay Icons
If you right click an item, a selection menu appears with navigation options and
shortcuts to actual functions for the item.
Figure 10 Right Click Menu
Note: Using the Open in New Window function you can compare attribute
values on different items.
1553-CXP 901 4102/10 Uen F 2009-09-25 13

2.2.2 Navigation with the Location Bar
Figure 11 Location Bar
Use the arrows for backward and forward navigation. With the pull down menus
near the arrows and the address field, you can select previously visited items.
2.2.2.1 The Browser
When you select an item in the Management Tree, the browser area shows
a screen relating to the item chosen as shown in Figure 12 on page 14. The
browser is customized to the item chosen in Management Tree and contains
the attributes of the selected item along with useful information applicable to
the selected item.
Figure 12 Browser
Note: To go back to the previous browser view, right click and hold inside the
window and move the mouse to the left, then release. Move to the
right to go forward again.
14 1553-CXP 901 4102/10 Uen F 2009-09-25

2.2.2.2 Open Attribute Links
You have two options to view attribute links:
• Click the link directly to view attributes in the same browser window
• Right-click the link and choose Open in New Window
A new window shows attributes of the item.
2.3 Notification List

This section presents the Notification List, its views and functions. You
can control the display of the Notification List from the View menu. View >
Notification List (ticked - on; unticked - off).
The purpose of the Notification List is to present the current alarm and event
notifications. In addition, it shows the history of all alarms.
Alarms report failures in the NE. Events report other situations in the NE that
are not failures.
Note: The Notification List opens by default at the bottom of the screen. The
main screen toolbar buttons are still available for the Notification List.
Notifications are presented in various types of list views:
• The Current Alarm List: Lists the current state of the managed NE
• The Trace Lists: These chronologically list (if sorted by time stamp)
received notifications (alarm, protection switch and event)
• The Historical Lists: These chronologically log (if sorted by time stamp)
and are stored in the LCT. They are accessed from a separate screen, see
Section 2.3.3 Notification History List on page 23
The dynamic lists are updated every time a new notification is received, unless
the notification is suppressed by any selection.
Figure 13 Notification List View
1553-CXP 901 4102/10 Uen F 2009-09-25 15

You can select notification records, filter notification selections, and rearrange
and sort alarm columns in the Notification List.
2.3.1 Log Viewer
The Log Viewer contains a list of error messages reported in the LCT according
to level settings. If the log contains messages, this is shown in the status bar
with symbols indicating the severity of the message:
Table 3 Log Viewer Symbols

Error
Warning
Information
Unmapped severity
• If a symbol is shown, double-click the symbol to view the log, otherwise

double click the log area on the Notification List status bar as follows:
• Messages marked with the Note icon - - contain additional

information.
Note: Logs can be saved to file, opened in, and deleted from the Log Viewer.
Clear removes all messages from the Log Viewer.
Figure 14 Log Viewer
A Tooltip shows the entire value, if it does not fit inside the cell:
16 1553-CXP 901 4102/10 Uen F 2009-09-25

Figure 15 Log Viewer - Tooltip
Note: The maximum number of current alarms is 5000. Trace lists have a
maximum of 1000 notifications.
2.3.2 Notifications
A notification is a message informing of a specific occurrence, such as an alarm

situation or a state change. The LCT supports alarm notification and event
notification see Table 2 on page 7 and Table 3 on page 16.
2.3.2.1 Steady State Notification/Clearable Alarms
A notification informing of an occurrence that indicates a steady state change.

There are associated notifications that inform of changes to other steady states
in the originating object. Specifically for alarm notifications, such alarms are
called clearable, as there will always be an alarm cleared notification associated
with the alarm notification from the same object.
2.3.2.2 Stateless Notification/Non-Clearable Alarms
A notification informing of a transient occurrence. There are no associated

notifications that inform of a transient occurrence with the reverse effect.
Specifically for alarm notifications, such alarms are called non-clearable as
such an alarm is not associated with an alarm cleared notification.
To remove a non-clearable alarm, right click on the alarm and select Remove.
2.3.2.3 Alarm Lifecycle
The Notification List presents one row for each alarm point, like an alarm
source and alarm identification combination. When a new alarm notification for
the same alarm point is being presented, the row is possibly updated with the
severity of the new alarm and new time-stamps unless the alarm has been
cleared. A new row is created if the alarm point starts a new lifecycle instance.
Each new alarm notification might cause a transition from one severity to
another or to the Cleared severity which ends the lifecycle.
Note: No traps are sent to the IP address of the LCT if you have de-registered
as trap receiver.
2.3.2.4 Alarm Notifications
Alarm notification is a notification type to report a fault condition. A clearable

Alarm Notification has an associated alarm clear event, otherwise it is
non-clearable.
1553-CXP 901 4102/10 Uen F 2009-09-25 17

The lists contains notification records with a set of information. Alarm attributes
are listed in alphabetical order.
Table 4 Alarm Notification Attribute Values

Attribute
Name Description Legal Values
AddTxt Additional text (free form text

description)
AlarmId Unique identification of alarm
Alarm grouped into categories Equip (ment),
AlarmType env (ironment),
comm (unication), process
Boolean value to indicate if the alarm Checked/Unchecked
can be cleared or not. Some alarms
Clearable does not have duration and therefore
no Cleared severity
Ems Time Timestamp set by the LCT when the yyyy/mm/dd hh:mm:ss
alarm was received (LCT time)
The layer rate in which the item belongs Not Applicable (any other layer rate
Layer rate if applicable. supported by the NE). See Map viewer
and Map Designer
Location Location field from NE properties
NeTime Timestamp from NE (if available) yyyy/mm/dd hh:mm:ss
ProbCause The probable cause of the alarm (Legal values depend on the NE)
A probable cause qualifier if the (Legal values depend on the NE)
ProbCauseQ probable cause itself is not sufficient to
determine the exact error and source
Severity Severity of alarm Critical, Major, Minor, Warning,

Cleared, Indeterminate
Source Identification of the NE that contains the Every item available in the Management
source of the alarm Tree
2.3.2.5 Event Notification
Event notification is a notification type that reports state changes to items.
The lists contains notification records with a set of information. Attribute names
are listed in alphabetical order.
Table 5 Event Notification Attribute Values

Attribute
Name Description Legal Values
Additional text to explain the
AddTxt event
Description Additional text
Ems Time Time-stamp set by the LCT yyyy/mm/dd hh:mm:ss

when the alarm was received (server time)
18 1553-CXP 901 4102/10 Uen F 2009-09-25

2.3.2.6 Current Alarm List
The Current Alarm List is updated automatically, upon every new message
received. It presents alarm notification records, and alarms in an active state,
which were not cleared manually.
You can filter and sort the views. See Section 2.3.2.11 Notification Filter on
page 20 and Section 2.3.6 Rearrange Views on page 29.
2.3.2.7 Notification Trace List
The Trace Lists are dynamic views that present notifications from the moment
the view is opened. Events, Alarms and Protection switches are reported and
listed chronologically as messages from the NE state. The view contains no
history, but is continuously updated whenever new notifications are received
and/or updated.
You can filter, sort and clear the views. See Section 2.3 Notification List on
page 15.
2.3.2.8 View Trace Lists
To view events reported from the NE, select the desired trace tab in the
Notification List.
Figure 16 Protection Switch Trace Tab
For details on the notification attributes, see Section 2.3.2.5 Event Notification
on page 18.
2.3.2.9 View Alarm Trace List
One alarm in the Current Alarm list may represent multiple alarms (items) in the
Alarm Trace list.
1. Select the Alarm Trace tab in the Notification List.
2. View all alarms reported from the NE.
1553-CXP 901 4102/10 Uen F 2009-09-25 19

2.3.2.10 Clear Trace Lists
1. Select the Trace Tab.
2. Right- click in the Trace list.
3. Choose Clear List.
The list is cleared and will be empty until new items are received.
2.3.2.11 Notification Filter
This section presents how to see a subset of notifications in the Notification List
display, and introduces a filter to create such a selection.
You can at any time apply, create, delete or modify a filter to all Notification
List views.
Note: Filters generally filter in items, showing those that match the filter
criteria apart from those with NOT criteria.
Examples of filter criteria:
• The notifications generated in a specific time interval
• Only alarms with a specific severity
• Alarms with a specific probable cause
• Events with a specific status
• Alarms from only one item
Table 6 Filter Expressions

Expression Description
AND Choose value and add as second criteria - see Note

1 below
OR Choose value instead of first criteria if no response

- see Note 2 below
NOT Exclude value from list
> Value larger than...
< Value less than...
>= Value larger than or equal to...
<= Value less than or equal to...
Note:
1. AND: All of the criteria must be fulfilled or the filter will not return any items
20 1553-CXP 901 4102/10 Uen F 2009-09-25

2. OR: If you do not choose any expression when adding criteria, the LCT will
automatically use OR
2.3.2.12 Create a Single Filter
Click the Configure Filter icon in the Notification list -
The LCT opens the Alarm Notification List Filter.
Figure 17 Alarm Notification List Filter
• Example of time interval: Critical alarms latest hour (10:00 to 11:00):
0 Select type of time criteria (EMS time)
0 Set time value to larger than or equal to 10:00
0 Press AND
0 Press expression less than or equal to 11:00
To set the filter:
1. Click the New filter icon in the Filter menu.
2. Enter the name for the filter.
3. Select the criteria to filter on.

Available values are listed in the Possible Values pane on the right of the
screen.
4. Select an available value and double-click it.

The chosen value is added to selected filter criteria.
5. Select further filter criteria and values as required.
1553-CXP 901 4102/10 Uen F 2009-09-25 21

6. Click OK.
The LCT adds the filter to Filter list.
2.3.2.13 View Filtered Notification List
• Select the required filter from the Filter drop-down box in the Notification List
0 The LCT presents a filtered notification list
Note: The latest alarm is displayed in the Notification List independent of

any filter.
2.3.2.14 Modify Filter Name
1. Click the Configure Filter icon in the Notification list - .
2. Select the required filter from the Filter name drop-down box.
3. Click the Edit icon.
4. Rename the filter selected.
5. Click OK.
The selected filter has a new name. No changes have been made to the filter
setup.
Figure 18 Modify Filter Name
2.3.2.15 Modify Filter Content
3. View the filter setup in the Expression table.
4. Modify the content (attribute values).
5. Click OK.
Note: The selected filter has a new content. Be aware of the filter name as
this might now be misleading.
22 1553-CXP 901 4102/10 Uen F 2009-09-25

2.3.2.16 Delete Filter Selection
3. Click Delete.
4. Click OK.
The filter is removed from the Filter drop-down list in Notification List.
2.3.2.17 Clear Filter in the Notification List
• Click the Clear Filter icon in the Notification List -
The Notification List is unfiltered.
2.3.3 Notification History List

The Historical Lists present the notifications received from the NEs up to the
time the view is opened.
2.3.3.1 View History
Use this function to see a list of all notifications reported on the NE since the
last restart of the NE, or since the last clear of the history list in the NE:
Note: For attribute details, see Section 2.3.2.4 Alarm Notifications on page 17.
1. Select Notification History from the Equipment menu.
2. Click Refresh.
Note: Click Refresh to load the recent history. The view might be empty
until a load is yet to be performed.
3. Select between the Alarm, Events and Protection Switches tabs to view
the history.
1553-CXP 901 4102/10 Uen F 2009-09-25 23

Figure 19 Notification History
The LCT collects the notification history logs.
2.3.3.2 Save History Log(s)
1. Select the history log (alarm, event or protection switch) you wish to save.
2. Press Save on the toolbar.

The file browser opens.
3. Browse the directory and enter the file name.
4. Press Save in the file browser.

The selected history log (alarm, event or protection switch) is saved as
an xml-file to the selected directory. You can see the destination in the
window title field:
5. The next time you press Save, you will not be prompted for a filename. The
log you saved will be updated. Use File > Save As if you want to save
under a new name.
2.3.3.3 Open History Log(s)
1. Press Open from the toolbar The file browser opens.
2. Browse the directory and find the previously saved alarm or event log file.
Example: alarmlog.data.xml
3. Double click the file to display the saved alarms or events in the viewer. A
new tab with the name of the opened file appears:
You can now view the list, copy from it or print a report.
24 1553-CXP 901 4102/10 Uen F 2009-09-25

2.3.4 Menu Items
Note: The availability of the menu items may depend on the screen currently
selected. These tables show all menu items available for the various
screens.
2.3.4.1 Network Element Menu
Table 7 Network Element Menu Items

Menu item Action
Save Save
Reconnect Reconnect to the equipment
Exit Exit the LCT
2.3.4.2 Edit
Table 8 Edit Menu Items

Menu item Action
Copy Copy selected items to the system clipboard
Paste Paste content currently on the system clipboard
Add Add a row
Delete Delete the selected item(s)
Select all Select all items in the active view
Invert selection Invert the current selection in the active view
Clear selection Clear the current selection
2.3.4.3 View
Table 9 View Menu Items

Menu item Action
Standard: Check to make the Standard toolbar active
Navigation: Back/Forward
Attributes: Check to make the Attributes toolbar active
Toolbars Zoom: Toggle the zoom tool
Location: Check to make the location visible
Labels: Check to make labels visible on toolbar buttons
Lock the toolbars
Status bar Check to make the Status bar visible at the bottom of the LCT desktop
Management Tree Check to make the Management Tree an active application on the desktop
Notification List Check to make the Notification List an active application on the desktop
Last alarm Check to view latest received alarm in a separate window in the Notification List
1553-CXP 901 4102/10 Uen F 2009-09-25 25

Menu item Action

Back
Forward
Up
See Section 2.3.4.7 Toolbar Buttons on page 27
Home
Stop
Refresh
Error Log Open Error log. Log is also available from the status bar directly
2.3.4.4 Equipment
Table 10 Equipment Menu Items

Menu item Action
Open VLAN Settings screen
VLAN Settings
Cross Connection See Section 9.3 SDH Cross Connection Management on page 127
manager
Commissioning Open the Commissioning Wizard

Wizard
Ethernet Services Open the Ethernet Services Wizard

Wizard
Open Notification History
Notification History
See Section 2.3 Notification List on page 15
Open Software Download and Configuration Restore. Please see Section 3
NE Maintenance NE Maintenance on page 31
NE User Manageme Manage users of the NE
nt
Change Current User
Password
2.3.4.5 Tools
Table 11 Tools Menu Items

Menu item Action
Text Editor Open the text editor to create new, open and save text file(s)
Audit Log Open the Audit Log
2.3.4.6 Help
Table 12 Help Menu Items

Menu item Action
User Guide Launches the LCT and LCTS Operator’s Reference as a pdf file
26 1553-CXP 901 4102/10 Uen F 2009-09-25

Menu item Action

Alarms and Events Launches an Alarms and Events description document
Release Notes Launches release notes for installed LCT software
Bug Reporting Launches the Bug Reporting Tool
Ericsson Web Launches the Ericsson Internet site in your web browser
About Launches information about the installed LCT software
2.3.4.7 Toolbar Buttons
Table 13 Toolbar Buttons

Name Icon Description
Navigate in Topology - back or forward in navigation
history (only to main view; attributes and maps)
Back/Forward
Stop the current operation

Stop
Refresh the active view

Refresh
Return to the root node from the current view

Home
Move up one level in the Management Tree

Up
Paste content current on the clipboard. See Section

Paste 2.3.5.1 Copy and Paste on page 28
By default, entire rows are selected in a table, but

Cell mode single cells can easily be selected using the cell-mode
toggle button
Copy selected item(s) to the clipboard. See Section

Copy 2.3.5.1 Copy and Paste on page 28
Save
Save
Add new row

Add
Delete selected item(s)

Delete
1553-CXP 901 4102/10 Uen F 2009-09-25 27

2.3.5 Other Desktop Features
2.3.5.1 Copy and Paste
All LCT applications supporting table entry editing have a copy and paste
feature. When pasting, the LCT will verify that selected columns have the same
data type as the cells copied from. If not, you are asked if you would like to copy
the data based on the column names. Only editable columns with the same
name and data type will then be pasted. This enables copying and pasting
between tables with the same data but with different column order.
Figure 20 Copy Data from an LCT Application
Figure 21 Paste Data to Third Party Program
2.3.5.2 Cell-selection Mode
By default, entire rows are selected in a table, but single cells can easily be
selected using the cell-mode toggle button -
This way you can copy one table cell, select an entire column and press Paste
to copy the value into all selected cells. Copy and paste for ranges are also
supported. Thus you can copy values A and B and paste them into a large
range to get the A and B values repeated throughout the range.
Copy and paste to external applications is supported.
2.3.5.3 Navigation in Tables Using the Keyboard
The cell currently in focus is easily spotted and the arrow-keys can be used to
move the cursor (applies for editable tables only). Editing of a selected cell is
easily available through Enter or F2. The Tab key can be used for moving to
the next editable cell (from left to right and top to bottom). The selection is
28 1553-CXP 901 4102/10 Uen F 2009-09-25

circular, meaning when the last editable cell on the last row is reached, the first
editable cell in the first row will be activated.
To move to the first editable cell in a table, activate the window and press
the Tab-key twice.
See Section 2.3 Notification List on page 15.
2.3.5.4 Auto Fit Column Width
Double-click on the resize area in the column header to resize the column and
show the full values in the column. By default, the column name is not taken
into consideration, but this can be achieved by holding down the Shift key
while double-clicking.
2.3.6 Rearrange Views
2.3.6.1 Present Columns in View
You can choose which columns are to be visible in the Notification List. See
Table 2 on page 7 and Table 3 on page 16.
1. Select the desired tab in the Notification List.
2. Right-click the column heading and available columns are listed (checked
in default view).
3. Uncheck the undesired column(s) and they are no longer visible in the
Notification List.
Figure 22 Visible Columns
2.3.6.2 Change Column Order
1. Click and hold the column heading.
2. Drag and drop the column to its new position. The columns switch places
in the view.
1553-CXP 901 4102/10 Uen F 2009-09-25 29

Figure 23 Column Order
2.3.6.3 Resize Column(s)
1. Rest the mouse pointer to the right of desired column header. The mouse
pointer turns into a double-arrow.
2. Click and drag to suitable column-size.
Figure 24 Column Size
2.3.6.4 Sort Columns
• Click on the desired column heading to toggle between sort ascending

and sort descending.
Figure 25 Column Sorting
30 1553-CXP 901 4102/10 Uen F 2009-09-25

NE Maintenance
3 NE Maintenance
This chapter describes how to maintain an NE with downloaded network

releases, configuration and backup files through the NE Maintenance Interface,
and how to view the status of the NE in the Inventory form.
3.1 Operation
Select NE Maintenance from the Equipment menu to open the NE Maintenance
screen.
Figure 26 NE Maintenance - Welcome Screen
The NE is presented with panes to the left. When you select a suitable function
from the list on the left, data available on the equipment software banks and
data available in the management system repository is listed in the window to
the right as shown in the figure for the Configuration function below.
1553-CXP 901 4102/10 Uen F 2009-09-25 31

Figure 27 NE Maintenance - Configuration
You can navigate in the NE Maintenance screen when an activated session

runs in the background, but it is not possible to run several sessions at the
same time.
3.1.1 Software Download Process
The management system supplies the NE with the necessary information to

start downloading new files. The download process is controlled by the NE
itself. The NE is the Secure Shell (SSH) client, the LCT is the SSH server.
(External servers can also be used.)
Note: A network release supports a given set of traffic modules. If a new

module is introduced, the NE needs a new network release.
3.1.1.1 Downloading Files
Select Device from the Management Tree and then Network Element >
Download, or the Download icon - .
3.1.1.1.1 Network Release File
This is a collection of single files which are combined and packed into one file.
This file contains one or more independent upgrade components:
• Device software
• Device firmware
• Device licences
• Plug-in module software and firmware
32 1553-CXP 901 4102/10 Uen F 2009-09-25

NE Maintenance
This upgrade will be controlled by the embedded software on the NE which

checks which components are included in the release and asks for upgrade
of those components that are newer.
The files have administrative information that tells the NE whether it is a

software, hardware or configuration file. The files appear as *.package.zip,
sorted in file browser as file type ‘Packages and Network Releases’.
3.1.1.1.2 Location of Files
A prerequisite for software download is that the files are located in a directory
where the SSH download server can locate them. This is the ./res/software
directory of the installed LCT. The files may be placed in the download directory
manually, or by use of the Package Installer, see Section 3.1.3 How to Install
the file into the Management System on page 35.
3.1.2 SSH Server Settings

The embedded SSH host of the management system has a default interface
setup for an internal or external SSH daemon. These settings must be
performed for the NE to find the files to be downloaded onto the NE. You can
use an internal or an external SSH server.
Select SSH Server from the Information grouping in the Management Tree.
Figure 28 Select SSH Server
In the Internal mode, the NE will use SSH to access the workstation to get
the file.
Figure 29 SSH Server Settings
Use the 0.0.0.0 value for the Interface to listen to all interfaces or select an
IP address from the pull-down menu.
1553-CXP 901 4102/10 Uen F 2009-09-25 33

The default port is set to 13179 to avoid conflict with eventual existing SSH
sessions. You can use a port of your wish, but make sure that the firewall
settings allow the NE to access the selected port on the work station.
In the External mode, the NE will access an external server to get the files.
Figure 30 SSH Server Settings - External
The port is set to 22 by default. You can use a port of your wish, but make sure
that firewall settings allow the NE to access the port on the external server
(SCP (Secure CoPy) server is used).
3.1.2.1 Confirmation Dialog
A confirmation dialog box appears according to the command you have chosen,
before the session start. Only the relevant options are available.
Note: It is not possible to reselect Switch Bank for sessions concerning

licence and configuration.
Figure 31 Confirmation Dialog
You may change the restart option and switch bank setting.
You can turn off this function from the View menu:
34 1553-CXP 901 4102/10 Uen F 2009-09-25

NE Maintenance
Figure 32 Turn Off Confirmation Dialog
3.1.3 How to Install the file into the Management System

The Package Installer will help you install software into the management
system. You will select a file you already have or one that is downloaded from
the supplier’s site and add this to the central software repository. New software
for the equipment will then be available from the NE Maintenance screen.
Figure 33 Start Package Installer
1. Select Package Installer from the Network Element menu.
2. Read the information in the introduction window, and press Next.
3. Browse and select the file from the software folder and press Open.
4. Press Next for summary.
5. Verify the compatibility of the selected file for the NE and compare the
version and R-state numbers of the file to what is already installed on the
equipment.
Note: Press Back if you want to reject the current file and reselect in Step
1. To exit the wizard at any time, you can press Cancel.
6. Press Finish to activate file transfer. The selected file is unpacked and
transferred to the management system software repository.
7. Press Close to exit the wizard.
1553-CXP 901 4102/10 Uen F 2009-09-25 35

The file (network release or single file) is available in the repository list(s) in the
Download wizard, and saved to the .res/ software directory of the installed
management system.
3.1.4 Download a Network Release
The following procedure explains necessary steps needed to download a

network release to an OMS 1410 NE.
To save management DCN bandwidth, only files that have changed between
currently running and targeted downloaded network release are downloaded by
the NE.
The def-file contains information on the contents of the network release

(hardware/software file references, module type associations, version/inventory
control system information, hardware compatibility information and
traffic-affecting status for the different modules).
The LCT reads def-file properties and calculates download volume before
downloading the network release to the NE.
Note: Module software and firmware releases are downloaded as part of

a network release.
3.1.4.1 Download a Network Release
1. Select Device from the Management Tree and then Network Element >
Download, or the Download icon in the toolbar - .
2. The Download wizard launches. Read the wizard summary and press
Next to continue.
3. Select the network release file you want to download and click Next.
36 1553-CXP 901 4102/10 Uen F 2009-09-25

NE Maintenance
Note: In this example the Add to repository button is not available

because an external server is used, thus only entries in the external
server are listed.
4.
Right click on the column heading to select visible columns in the

Repository list.
The wizard now initializes the download.
5. Select Download Start time and Activation Start time. Please note slots
that are subject to traffic interruption.
6. Click Next to start the download according to your time-settings.
7. Read the summary and click Finish to start the installation.
8. At this stage you can safely close the wizard and watch the progress in
the NE Maintenance screen.
1553-CXP 901 4102/10 Uen F 2009-09-25 37

After a successful download, the system will not accept any configuration
changes as long as the network release is not committed. The system will
automatically commit the network release after the period defined during the
initial steps of the download. You may commit the network release immediately
by selecting the NR Commit operation from the toolbar.
3.1.5 Rollback of a Network Release

Rollbacks can be performed to recover from non-successful network release
downloads. The rollback reverts the NE running configuration to the original
state.
Depending on the situation, a rollback may be initiated in two situations:
• A download session is partially completed due to an error sequence. The

system automatically rolls back to a previously known good situation
• You manually force a rollback based on error information from the NE
3.1.5.1 Rollback to Previous Network Release
1. Click Device in the Network Release pane.
2. In the toolbar click Rollback.
3. You are asked to confirm your action. Press Yes to start the rollback
operation.
4. View the Rollback progress and wait for the Status to become Finished.
Note: Only one rollback is allowed. That is, if ED00M is the rollback NR
and ED00A is the active NR and a rollback is performed, you cannot
afterwards rollback to ED00A (now the rollback NR).
38 1553-CXP 901 4102/10 Uen F 2009-09-25

NE Maintenance
3.1.6 Align a Network Release
This operation is only available when the NE has two SC modules with different
Network Releases (Duplex mode). To align the Network Releases of the
modules and set the modules to redundant mode, follow the procedure below.
1. Open the NE Maintenance screen.
2. Select Device.
The table lists the software entries for the SC modules; one will be indicated
as active, and the other as NR Mismatch.
3. Press the Align NR button and the mode changes to redundant mode.
This may take 1-2 minutes.
3.1.7 OMS 1410 - Configuration Backup and Restore
This section describes the steps to backup and restore the NE configuration.
The configuration is saved in a CDB (Configuration Data Base) file into the
download repository.
3.1.7.1 Backup Configuration
1. Select Configuration in the Management Tree:
2. Select the Backup icon from the toolbar.

A dialog box appears, and you can edit the suggested name for the
backup-file. Click OK to confirm the backup operation.
3. View the backup progress in the NE Maintenance screen.
1553-CXP 901 4102/10 Uen F 2009-09-25 39

4. The CDB file is now stored in .....\res\software\CFG.
3.1.7.2 Restore Configuration
1. Select Configuration in the Management Tree:
2. Select the Restore icon from the toolbar.

The Download wizard launches. Read the instructions and click Next.
3. Select the desired cdb-file to restore and click Next.
4. Read the summary and click Finish.
5. View the progress in the NE Maintenance screen.
3.1.7.3 Clear Configuration Data Base (CDB)
This procedure explains how to perform a limited clear CDB. This operation will
erase everything except local IP address, user configuration and the audit log.
Note: The default gateway will disappear. You need to have access to the
local subnet, or serial access, to continue management.
40 1553-CXP 901 4102/10 Uen F 2009-09-25

NE Maintenance
Caution!
Perform Backup CDB before the following procedure. See Section 3.1.7.1
Backup Configuration on page 39.
1. Select the Configuration pane:
2. Click the Clear CDB icon - - to perform a limited clear of the

configuration database in the equipment.
3. You are asked to confirm your action. Click Yes to perform a limited CDB
clear.
Connection lost/Equipment reconnected will be reported during the
clear-operation.
4. View the progress in the NE Maintenance screen. Also, click the Event
Trace in the Notification List.
3.2 Licence Handling

You access Licence Handling from the Management Tree; it is not accessible
from the NE Maintenance screen.
3.2.1 Open the Licence Handler

1. Click on Device in the Management Tree.
2. In the Device screen, click the Licence Handler icon.
1553-CXP 901 4102/10 Uen F 2009-09-25 41

The Node Licences view opens and shows the licence features on the NE
and links to related tasks, see figure below.
Figure 34 Node Licenses
3.2.2 Node Licences View

• NE Information: The fingerprint value is a unique identifier for the actual
NE and is used to connect the Licence Key to one specific NE
• Licensed Features: A list of features on the NE that are licensed. For R1.0
there is only a Basic Functionality licence. There is a grace period of 45
days to buy and install this licence
• Licence Tasks: The tasks Licence File Overview, Install Licences and
Create Licence Key File are described in the following sections
3.2.3 Licence File Overview
View information and status of licence key files currently installed on this NE.
3.2.4 Install Licences
For the licence installer to find the Licence Key File (LKF), it must be stored in
the LIC folder in the install directory of the LCT, such as:
C:\Program Files\OMS1410Craft_1.0\res\software\LIC
42 1553-CXP 901 4102/10 Uen F 2009-09-25

NE Maintenance
Figure 35 Download Licence Key
Select the Licence Key file and press the Install LKF button. You will now get
feedback in the notification list.
3.2.5 Create Licence Key File Request
When the installed licence expires, there is a grace period of 45 days before
the licence will be deactivated.
To order a new licence key, use this function to create an xml request file that
you send to your supplier contact.
Figure 36 Create License Key File Request
3.3 Inventory
To open the Inventory screen, select Device in the Management Tree, then
from the Device screen select the Inventory link icon.
The Inventory screen displays the information you need to identify the versions
of hardware and software in the NE, as illustrated by the figure below.
1553-CXP 901 4102/10 Uen F 2009-09-25 43

Figure 37 Inventory
44 1553-CXP 901 4102/10 Uen F 2009-09-25

The Commissioning Wizard
4 The Commissioning Wizard
4.1 Introduction
The Commissioning Wizard is an interface to set up an NE. A set of limited but
important features can be configured with the wizard.
Everything that can be configured here, can also be configured through the
Management Tree (see Section 4.12 Management from the Management Tree
on page 56). For a pre-configured NE, we recommend the Management Tree
for additional configuration.
Note: This chapter explains the use of the Commission Wizard to configure
an unconfigured NE. Configuration concepts, access limitations, and
the alike, are beyond the scope of this chapter.
4.2 Starting the Commissioning Wizard

Select Equipment > Commissioning Wizard from the Desktop menu bar.
4.3 Basic Setup

Name, Location and Owner identify describe an NE. They serve no technical
purpose, but are helpful for management. We recommend to at least set
Location, which is used to label the NE in the Management Tree.
User Management information about the registered users displays and a link
opens the User Management application to configure access to the NE. The
default user is admin with password admin. To restrict access to the NE, you
should replace the default user. Read more in Section 1.4 User Management
on page 3.
1553-CXP 901 4102/10 Uen F 2009-09-25 45

Figure 38 Basic Setup
4.4 Time Setup

NEs do not need to know the proper date and time. However, various events,
such as the raising of alarms, are assigned with time stamps. Having accurate
time stamps simplifies management.
The date and time can be kept locally in the NE. Alternatively, if a time server
is available, the NE can be configured to keep itself synchronized with the
Network Time Protocol server.
Using the Commissioning Wizard the time cannot be randomly assigned.

Setting the time will match the NEs clock to the clock on the computer where
the wizard is running.
The bottom of the window shows the NE’s clock. Additionally, if the NE is
already configured to synchronize with a time server, the server’s IP address is
also listed. However, when the wizard is used for its most common purpose, to
configure an unconfigured NE, the NE will not be pre-configured to synchronize
with a server.
46 1553-CXP 901 4102/10 Uen F 2009-09-25

Figure 39 Time Setup
• No Change
0 This leaves the current NE time unchanged
• Synchronize to Workstation Time
0 This synchronizes the NE’s clock to match the clock on the computer
where the Commissioning Wizard is running
• Synchronize to Time Protocol Server
0 This configures the NE to work with a server. The IP address of the

server must be provided
4.5 Shelf
Some modules have multiple modes, supporting different functionality.
Depending on the setting of Expected Mode, additional configurable attributes
will become available. For users familiar with the NEs, these attributes will be
self explanatory.
1553-CXP 901 4102/10 Uen F 2009-09-25 47

Figure 40 Shelf
As you can see in the figure above, for Slot 3, where a module is installed, the
inappropriate modes are marked by a warning icon to indicate the modes you
can select for the installed module.
4.6 Expected Port Modes

Some ports have multiple modes, supporting different functionality. On this
page, you can set up the port properties for the different ports.
48 1553-CXP 901 4102/10 Uen F 2009-09-25

Figure 41 Expected Port Modes - LAN Ports
Figure 42 Expected Port Modes - SDH Ports
4.7 Port Interface Modules

The SFP/XFP Port Interface modules must be provisioned with the correct
expected interface.
1553-CXP 901 4102/10 Uen F 2009-09-25 49

Figure 43 Port Interface Modules
4.8 Port Interface Settings

Select the expected wavelength for the provisioned Port interfaces with support
for Wave(length) Division Multiplexing (WDM) functionality.
Figure 44 Port Interface Settings
Note: This is for information only, it does not effect functionality.
50 1553-CXP 901 4102/10 Uen F 2009-09-25

4.9 SDH Synchronization

All SDH equipment requires a synchronization signal. The signal is referred to
as T0. A variety of sources can provide a signal to drive T0. If multiple sources
are identified, the additional ones are backups for use if the primary fails. If T0
sources are not provided, the NE will use its internal clock. Although this can
work, it is generally not recommended. Setting T0 sources is recommended.
Figure 45 SDH Synchronization
NEs have a SYNC port that can be used to send a synchronization signal to
external equipment. The signal, T4, is configured from the SDH Synchronization
setup step during commissioning. Unlike T0, T4 is not a critical setting and
is unused in many networks.
4.9.1 Adding Entries to the Synchronization Tables
Use the button to add a synchronization source to the table. After the entry
has been added, the fields can be set to identify and configure the source.
Table 14 SDH T0/T4 Synchronization Parameters

Parameter Values Note
SSM • Enabled Tx Synchronization Status Message
• Disabled
Lockout • Enabled Each source nominated in a priority table
can be temporarily locked out from the
• Disabled automatic sync selection process by
enabling Lockout against that source. The
source is reinstated in the automatic sync
selection process through a Clear Lockout
instruction against the port. Separate
lockout states can exist for the same
source in different selection processes (T0,
T4).
1553-CXP 901 4102/10 Uen F 2009-09-25 51


Wait to Restore Time 0 to 900 seconds The time in seconds before the system
reverts to a synchronization source that
has recovered from a failure
Priority 1 to 5 Each source that is to be considered as a
possible source for synchronization must
be given a priority 1 to 5. No two sources
may be set with the same priority. Sources
are selected in order of priority (1 is highest
priority)
Administrative Quality • SEC SEC - SDH Equipment Clock
• SSU-L SSU-L - Synchronization Supply Unit
• SSU-T PRC - Primary Reference Clock
• PRC
Hold Off Time 300 to 1800 ms This Hold Off is required if using multiple
protection schemes such as MSP or
MS-SPRING. It allows the MS layer
protection scheme to react and switch, and
pre-empt SNCP switching if a detected
fault would lead to switching actions is an
MS layer to correct the fault, otherwise
switching actions might occur in both the
MS layer and the VC-path layer
Highlighted entries can be deleted with the button
4.10 Alarm Configuration
4.10.1 Master Reporting

This step allows global NE alarms to be enabled or disabled. A brief description
of each alarm type is provided by the wizard. For users without experience or
guidance, it is recommended to Enable Master Alarm Reporting and Pointer
Justification Event, and to Disable Non-Intrusive Monitoring and Link Capacity
Adjustment Scheme during commissioning.
52 1553-CXP 901 4102/10 Uen F 2009-09-25

Figure 46 Master Alarm Reporting
4.10.2 Reporting
An NE has inputs for external alarms. If an external alarm is triggered,
a message can be sent to the management stations. Most commonly,
environmental conditions such as air conditioning failure, UPS power loss, or
temperature out of range, are set to trigger external alarms.
Alarms can be triggered closed or open loop, and each alarm’s message is
configurable (Description attribute). Configuring external alarms is not crucial,
and they are unused in many networks.
Figure 47 Alarm Reporting
Table 15 Alarm Reporting Parameters

Administrative State • In Service
• Out of Service
1553-CXP 901 4102/10 Uen F 2009-09-25 53


Description ASCII Characters Enter a description using up to 80 characters
Severity • Critical This defines the severity that you want to assign to the
selected alarm
• Major
• Minor
• Warning
Triggered When • Closes
• Opens
4.10.3 Configuration
Alarm Configuration is split into two parts. The upper part, Alarm Configuration,
provides a list of alarms that the NE can raise. It allows you to modify each
alarm’s description (Probable Cause Qualifier attribute) and each alarm’s
Severity. Modifying these fields is seldom required.
The lower part, Alarm Persistency, defines how long a problem must be present
before an alarm is raised, and how long the problem must be corrected
before an alarm is cleared. Understanding these settings requires SDH/PDH
experience, and should only be modified by knowledgeable users. Many
networks leave the defaults unchanged.
Figure 48 Alarm Configuration
54 1553-CXP 901 4102/10 Uen F 2009-09-25

4.10.4 Threshold
Alarm Thresholds are specific levels that set the requirements for a signal to
be in range. When a signal is out of range, an alarm is raised. Understanding
the thresholds requires SDH/PDH experience, and should only be modified by
knowledgeable users. Many networks leave the defaults unchanged.
Figure 49 Alarm Threshold
4.10.5 Suppression
Individual alarms can be suppressed. Alarm suppression requires SDH/PDH
experience, and should only be done by knowledgeable users. Many networks
leave the defaults unchanged. If changes are made, a common one is to
enable the AIS alarm, which is disabled by default.
Figure 50 Alarm Suppression
1553-CXP 901 4102/10 Uen F 2009-09-25 55

4.11 Finish
Figure 51 Summary
4.12 Management from the Management Tree

This section describes how to access parameters in the Management Tree for
necessary management activities that can be performed after you have used
the Commissioning Wizard.
4.12.1 Shelf Form
When you select Shelf in the Management Tree, a custom designed form as
illustrated in the figure below, appears in the browser window.
This presents an overview of all slots in the shelf, and you can see if and
what module is installed. You can select the expected mode for the module,
and enter a short description.
When you select Mode from the pull-down menu, the modes you should not
select are marked with a warning icon.
When you have made changes to the form, press the Save icon to commit the
changes, or you will be prompted to save changes if you try to navigate away
from the form.
56 1553-CXP 901 4102/10 Uen F 2009-09-25

Figure 52 Shelf Form
4.12.2 Slot Form

When you select Shelf > Slot, a custom designed form per slot appears in the
browser window. In this form you can enter or modify the slot description and
expected mode and toggle alarm reporting
The Restart and Shutdown buttons can be used in case of failure on a module.
Figure 53 Slot Form
1553-CXP 901 4102/10 Uen F 2009-09-25 57

58 1553-CXP 901 4102/10 Uen F 2009-09-25

Data Communication Network (DCN)
5 Data Communication Network (DCN)
5.1 Introduction
The following sections describe how to configure the Management Port and the
DCN interfaces.
The management traffic is IP based (XML and SSH messages), and therefore
configuring a management path comes to deciding which encapsulation shall
be used to send the IP datagrams carrying the management traffic over the
network. For the management interfaces, two main encapsulation types exist:
• IP directly carried over a Layer 2 protocol (Ethernet, PPP, or proprietary)
• IP encapsulated within Connectionless (mode) Network (layer) Protocol

(CLNP) carried over a Layer 2 protocol (IEEE 802.x or LAP-D)
In addition, each management interface can be turned off. This is an important

feature for security purposes, especially for the Management Port that is
physically accessible on the NE (main card). Actual encapsulation support
varies depending on the management interface type (Management Port or
DCC).
Note: The Management Port can run both IP over Ethernet and CLNP over
IEEE 802.x at the same time. On the contrary, a DCC can run only one
mode at a time. In addition, a maximum of 24 Data Communications
Channels (DCCs) can be used for management purposes - that is, up
to 24 DCCs can have their management mode set to Used.
5.2 DCN Page

Either select dcn from the Management Tree or select the DCN settings form
icon from the home page -
On the DCN page you can find links to tasks that are relevant to the
management of DCN channels. Related tasks (IP and OSI configuration) are
available through other objects in the Management Tree. The following sections
briefly describe the different forms you can open from this page. For further
information please refer to the Technical Product Description.
1553-CXP 901 4102/10 Uen F 2009-09-25 59

Figure 54 DCN Page
5.2.1 Out-of-Band Management Interfaces
The Out-of-Band Management Interfaces are the DCC, management ports and
IP over OSI tunnels.
5.2.1.1 Management Ports
The Management Ports form contains settings for the management mode, IP
address and the subnet mask for the management port.
Figure 55 Management Ports
In case of redundant SC module configuration, the physical interfaces on both

system controllers are connected to the active SC.
The DCN Management Port can run four types of encapsulation, referred to
as modes. A particular mode is selected by setting the variable mode (DCN >
Management Port > Management Mode):
• IP
• OSI
• IP and OSI
• Not used
60 1553-CXP 901 4102/10 Uen F 2009-09-25

Note: When you change the management mode in the pull down menu, the
change takes effect at once.
The LCT ports can only be configured to IP or Not Used.
Note: The LCT port is for connecting to NEs from LCT stations located in
the local segment only. Traffic from the LCT port will not be routed
outside the local LAN segment.
Depending on your topology, additional routing information might have to be

configured. You can define static routes, and/or control dynamic protocols
(RIP, OSPF).
5.2.1.1.1 Configure DHCP
Dynamic Host Configuration Protocol (DHCP) can be configured only for the
LCT port, and is enabled by default.
Figure 56 DHCP
The allocated addresses for the DHCP client can be verified from the DHCP
Client table, follow the link on the form.
5.2.1.2 Management DCC
A DCC can run three types of encapsulation mode. A particular mode is

selected by setting the variable mode. Required configuration for one of the
three possible modes is further detailed in the next sections.
• Not Used
• IP
• OSI
1553-CXP 901 4102/10 Uen F 2009-09-25 61

First, configure the DCC to IP or OSI. After saving, further configuration is

possible.
Figure 57 Management DCC
5.2.1.2.1 IP
Unnumbered DCC interfaces share a single IP address assigned to the

Loopback interface.
OSPF routing process uses the Loopback IP address as RouterID. Therefore,

in case Unnumbered DCC interfaces are used, and/or OSPF routing is enabled
- Loopback IP address must be configured first.
For an IP interface, you must first enter a description and then select Save.
Once the description is saved, the other configuration fields become available
as follows:
Figure 58 Management DCC - IP
For numbered DCC interfaces, every interface must be located in the different
IP subnets. It is not allowed to have different DCC interfaces in the same subnet
of intersecting subnets. For DCC channels over MSP-protected links, the Follow
MSP option must be configured in the same way on both sides of the link.
62 1553-CXP 901 4102/10 Uen F 2009-09-25

5.2.1.2.2 DCC in OSI Mode
Figure 59 Management DCC - OSI
5.2.1.3 OSI Tunnel
Figure 60 OSI Tunnel
5.2.2 In-Band Management Interfaces
5.2.2.1 Management VLAN
IP interface only, no OSI capabilities, only one instance per node.
Create the VLAN first in the VLAN interface (see Section 7.5 VLAN Provisioning
on page 92), then create the Management VLAN, and assign an IP address.
Note: The interface is always IP numbered.
1553-CXP 901 4102/10 Uen F 2009-09-25 63

Figure 61 Management VLAN
5.2.3 DCC Cross Connection - Transparency
• R to R or M to M only
• Only Not used interfaces
• Same limitation - 24 interfaces per node
Figure 62 Transparency
64 1553-CXP 901 4102/10 Uen F 2009-09-25

5.2.4 Related Tasks
5.2.4.1 IP Routing
Figure 63 IP Routing Form
5.2.5 OSI Routing
Figure 64 OSI Routing Form
1553-CXP 901 4102/10 Uen F 2009-09-25 65

66 1553-CXP 901 4102/10 Uen F 2009-09-25

Ethernet Screens
6 Ethernet Screens
This chapter describes the screens for the Ethernet ports. Several attributes
are common, and are described below.
To access these screens, expand Shelf in the Management Tree, expand a

suitable slot fitted with an Ethernet card/module.
6.1 Ethernet Port Attributes

In the illustration below, the LAN screen is used as an example. The attributes
available for the current state of the port are editable, and the fields with
non-editable attributes are gray.
Figure 65 Ethernet LAN Screen
Table 16
Administrative Status • In service
• Out of service
• Out of service - maintenance
• Out of service - auto in service
Priority • 802.1p
• Disabled
1553-CXP 901 4102/10 Uen F 2009-09-25 67


Capability • -- None -- • No capability set
• L1 • Layer 1
• L1 VLAN MUX • The port is used as a VLAN
multiplexer
• L2
• Layer 2
LAG Read-only If the port is a member of a LAG
(Link Aggregation Group), it will
be indicated here with the name
of the port. (Not for UNI (User
Network Interface) and LAG
screens)
Number of ACLs Read-only This states the number of Access
Control Lists applied to this port
6.1.1 The LAG Screen

The Link Aggregation Group screen contains the common attributes and related
tasks for the port members.
To access this screen, expand Bridge in the Management Tree, then expand
Link Aggregation Groups. If no LAG groups yet exist, or to create further
groups, right click on Link Aggregation Groups and select Add LAG.
Figure 66 Add LAG
The LAG screen allows you to create and maintain the LAG details.
68 1553-CXP 901 4102/10 Uen F 2009-09-25

Ethernet Screens
Figure 67 LAG Port Screen
The attributes presented in the LAG Port screen are not editable in the Port
screen of the respective members of the LAG.
Table 17 LAG Port Parameters

Description 0 to 80 ASCII characters Enter a meaningful name to identify the group
MAC Address Read-only
Administrative Status • In Service
• Out of Service
• Out of Service - maintenance
• Out of Service - auto in service
Operational status Read-only
Priority • Disabled
• 802.1p
Capability Read-only
Number of ACLs Read-only This shows the number of Access Control Lists
Link Aggregation Information
1553-CXP 901 4102/10 Uen F 2009-09-25 69


LAG Distribution Criteria MAC Source and MAC Destination There is only one choice available
An Aggregator Distributor reads user-selected criteria
bytes from ingress client frames. These bytes are
deemed to classify each frame as belonging to a
specific conversation. The distributor resolves to
always deliver the same distribution link number for
each of all like-classified conversation frames. Thus,
the distributor always resolves to allocate specific
conversation instances to specific active member
links on the LAG, at any given point in time. User
criteria byte selection currently offers the combination
of MAC Source Address, plus MAC Destination
Address, from ingress client frames.
LACP Control Mode • Static This disables (Static) or enables (Active) L2 LAC
PDU exchanges and PDU processing, by the Link
• Active Aggregation Control functions, between peering
devices across the LAG.
LACP Timeout • Short (3 s)econds Link Aggregation Control functions have a settable
LACP Timeout period.
• Long (90 s)econds
This sets the normal LACP PDU exchange rate
for periodic transmissions (Long = Slow = 30sec
periodicity); Short = Fast = 1sec periodicity). LAC
peers across a LAG determine when they need to
send and when they need to receive more PDU
information from the peer. Having received, a peer
starts a time-out timer (equal to 3 x the set periodic
transmission time). If it expires before another
needed PDU is received, the last PDU is invalidated
(assumed out-of-date). This leads to further need for
receiving PDUs from the peer.
LACP Activity Control • Passive Between communicating Link Aggregation Control
peers across the LAG, LACP Activity Control
• Active determines:
• Whether a peer only ever sends in response to

receipt of LAC PDU frames from its remote peer
(Passive); or
• Whether a peer sends LAC PDU frames proactively
whenever it wants to send information (Active)
70 1553-CXP 901 4102/10 Uen F 2009-09-25

Ethernet Screens

Collector Max Delay 0 to 65530 in steps of 10 • Click the stepper buttons to set the value up or
down in steps of 10
• Click the drop-down button to open a slider for
easier selection of wider range differences
• Enter a value directly into the field
With an Aggregator Distributor device and its remote
Aggregator Collector peering device over a LAG
link, when the construct of active member links on
the LAG changes, the distributor has to temporarily
stop transmitting client frames for an internally
defined Distribution Time-out time. It then runs a
client conversation frame redistribution algorithm
for the new LAG construct and then resumes frame
transmission. The Distribution Time-out time aims to
make sure that all frames previously transmitted have
been received and processed by the remote peer
collector device before the transmission resumes on
the new LAG construct. This might otherwise lead
to client conversation frame mis-ordering across the
LAG.
Inherent ingress frame buffering and aggregator
collector process delays determine a collector
function’s frame processing performance. This is
pre-determined by the platform packet processing
chip-set and is referred to, as Collector Max Delay.
If the distributor peer is aware of the Collector Max
Delay performance of its remote collector peer, it
can use this information to assist in setting its own
internal Distribution Time-out time. Accordingly,
local Collector Max Delay value information can be
sent to the remote peer distributor (over the LAG)
in the standards-defined field of LAC PDU frames.
The value carried in LAC PDUs can be adjusted by
the user, if desired. For example, adjusted-up to
cover any known, significant frame propagation delay
across the LAG that might be useful for the distributor
in setting its internal Time-out timer.
Bridge Port Settings

Acceptable Frame Type • Admit All Frames
• Admit Only VLAN Tagged Frames
• Admit Only Untagged or Priority
Tagged Frames
Ingress Filtering • Enabled
• Disabled
PVID 1 to 4094 Port VLAN (Virtual Local Area Network) Identifier
This is read-only unless the Provider Bridge Port
Type is set to CEP
Provider Bridge Port Type • PNP Provider Network Port
• CNP Customer Network Port
• CEP Customer Edge Port
CEP is not allowed if the port is a member of a VLAN
1553-CXP 901 4102/10 Uen F 2009-09-25 71

6.1.2 The UNI Port Screen
When a port is configured as a UNI, the UNI setting are available under
Ethernet Services in the Management Tree, as shown below.
Figure 68 UNI Port Relation
This screen represents the User Network Interface (UNI) setting for this port.
Here, you can edit the UNI port settings.
Note: Creation of the UNIs must be performed with the Ethernet Services
Wizard - see Section 8 Ethernet Services Wizard on page 95.
72 1553-CXP 901 4102/10 Uen F 2009-09-25

Ethernet Screens
Figure 69 UNI Port Screen
6.2 The Link OAM Screen

The Link OAM (Operation Administration Maintenance) screen, accessible from
a link on the LAN screen (see Figure 65 on page 67), contains information
and settings to adjust Ethernet first mile OAM settings per LAN port according
to IEEE 802.3ah.
Ethernet OAM is mainly used for detecting data link layer problems occurring
in the last mile. By enabling Ethernet OAM on two devices connected by a
point-to-point connection, you can monitor the link status of the link between
the two devices. Ethernet OAM provides the following functions.
• Link performance monitoring, to detect link errors
• Fault detection and alarm, to detect link errors to the administrators
• Loopback testing, to detect link errors through non-OAMPDUs
1553-CXP 901 4102/10 Uen F 2009-09-25 73

Figure 70 Link OAM Screen
Table 18 Link OAM Form Parameters

• Disabled By default Disabled. Select Enabled and save
Administrative Status
• Enabled
• Disabled – not active
• Enabled – active
Operational status
• Link fault – peer link signal
is lost
• Passive At least one of the ports must have the mode
set to Active
• Active
Mode Active mode: Only a device in active OAM
mode can initiate loopbacks and perform OAM
discovery
• Local (on local node, called Status of activated loopback
remotely)
Remote loopback testing is available only
• Remote (remote node after the OAM connection is established. With
looped towards the local remote loopback enabled, the OAM entity
Loopback status one) operating in active OAM mode issues remote
loopback requests and the peer responds to
them. If the peer operates in the loopback
mode, it returns all the Protocol/Packet Data
Units (PDUs) except OAMPDUs to the senders
along the original paths
Ignore RX Loopback • Yes

Cmd • No
• Initiate loopback For active port in the up state only
Loopback Command
• Terminate loopback
6.2.1 Link OAM Peer

The Link OAM Peer screen becomes available from the Link OAM screen when
the Link OAM Administrative Status is Enabled.
74 1553-CXP 901 4102/10 Uen F 2009-09-25

Ethernet Screens
The Link OAM Peer screen shows object attributes.
Figure 71 Link OAM Peer
6.2.2 Link OAM Port Event Configuration

The Link OAM Port Event Configuration screen is available from the Link OAM
screen.
This screen shows detection and reporting for received alarm events.
Figure 72 Link OAM Port Event Configuration
Table 19 Link OAM Port Event Configuration Parameters

• Disabled An undetermined critical event happened
Critical Event
• Enabled
• Disabled An unexpected fault, such as power failure, occurred
Dying Gasp
• Enabled
1553-CXP 901 4102/10 Uen F 2009-09-25 75

6.2.3 Link OAM Port Statistics
The Link OAM Port Statistics screen is available from the Link OAM screen.
This screen shows the statistics per port.
Figure 73 Link OAM Port Statistics
6.2.4 Priority Settings

The Priority Settings screen is available from the LAN screen.
Here, you can adjust priority setting for the provider bridge.
76 1553-CXP 901 4102/10 Uen F 2009-09-25

Ethernet Screens
Figure 74 Priority Settings
• Default Priority: from 0 to 7
6.3 Class of Service (CoS) Screen

The CoS screen, available from the COS item in the Management Tree,
contains links to various profiles where you can create and configure your
own CoS profiles.
Figure 75 CoS Screen
6.3.1 CoS Profiles

The Class of Service screen contains links to the various types of profile
available.
You can create new profiles for the following types:
• Priority to class profile
1553-CXP 901 4102/10 Uen F 2009-09-25 77

• CoS Level 802.1p profile
• Queue Management
Note: These profiles have default profiles pre-defined that you cannot edit.
6.3.1.1 Manage Profiles
From the CoS screen, select the link to the type of profile you want to manage.
The procedure is similar for all types.
Figure 76 Create Custom Profile
6.3.2 Traffic Scheduling
Figure 77 Traffic Scheduling
You can choose between three scheduling profiles:
• 3 x Strict Priority + 5 x Weighted Fair Queuing (WFQ)
• 8 x Strict Priority
• 4 x Strict Priority + 3 x WFQ + 1 Best Effort
For Traffic Scheduling Management, you can edit the WFQ weight parameter
only (and only if you have chosen one of the WFQ profiles).
78 1553-CXP 901 4102/10 Uen F 2009-09-25

Ethernet Screens
Figure 78 Traffic Scheduling Management
6.4 RMON (Remote Monitoring)

The RMON screen, available by selecting the RMON item in the Management
Tree, contains links to tables with RMON data.
Figure 79 RMON Reports
6.5 Link Capacity Adjustment Scheme (LCAS)

Use this function to switch Link Capacity Adjustment Scheme (LCAS) on and to
set up the basic LCAS parameters.
LCAS is an extension to Virtual Concatenation, and provides a control

mechanism to increase or decrease the capacity of a Virtual Concatenation
group without affecting traffic. In addition, the scheme automatically decreases
the capacity if a member of a Virtual Concatenation group fails and will increase
the capacity when the member recovers, again without affecting traffic.
LCAS is an end-to-end protocol between a pair of VC termination points, and

hence SDH units take no part in its operation. Configuration of LCAS is applied
at the adaptation point where a payload is mapped into the VC termination.
1553-CXP 901 4102/10 Uen F 2009-09-25 79

Figure 80 LCAS Selection
1. Referring to Figure 80 on page 80, from the management tree, select a

vcgroup from a WAN.
2. Set the Concatenation to one of the VCAT values. This ungrays the LCAS
icon.
3. Select the LCAS icon to call up the LCAS screen.
4. Set LCAS Operational Mode to LCAS.
5. Set Remove Member on EXC or DEG to Enabled or Disabled.
6. Refer to the section below on LCAS Operation for further details.
7. Save your changes.
6.5.1 LCAS Operation
6.5.1.1 Upsizing
Caution!
When increasing the size of the LCAS group, make sure that the sink end of
the connection is enabled before enabling the source end. This makes sure
that upsizing is hitless.
1. Create the required cross connection and enable the Admin capacity.
2. Add a new member and set the LCAS status upstream to Traffic.
80 1553-CXP 901 4102/10 Uen F 2009-09-25

Ethernet Screens
3. Add the new member at the other end of the link and make sure that the
LCAS Operational Mode of the member is set to LCAS.
6.5.1.2 Downsizing
Caution!
When decreasing the size of the LCAS group, make sure that the source end
of the connection is disabled before disabling the sink. There is no guarantee
that even if you do so, downsizing will be hitless.
1. Remove the member and set the LCAS status upstream to No Traffic.
2. Remove the link from the far end.
3. Disable the Admin capacity and delete the connections as required.
1553-CXP 901 4102/10 Uen F 2009-09-25 81

82 1553-CXP 901 4102/10 Uen F 2009-09-25

Layer 2 Configuration
7 Layer 2 Configuration
7.1 Introduction
This chapter guides you through management of the bridging service (L2
forwarding) on the NE.
This includes:
• Presentation and modification of the bridge
• Presentation and modification of MAC Multicast and Internet Group

Management Protocol (IGMP Snooping)
• Presentation and modification of Spanning Tree Protocol (STP) and

Rapid/Multiple Spanning Tree Protocol (RSTP/MSTP)
• Presentation and modification of traffic control
• Presentation and modification of VLAN
7.2 Bridge
This section describes the configuration operations supported by the bridge. It
is organized in two sections:
• Examples: this section contains simple, but typical configuration scenarios
• Miscellaneous: this section describes various features of the bridge
7.2.1 Examples
7.2.1.1 Static Unicast Forwarding
Static information is user-defined as opposed to equivalent information that is

learned. To configure an entry in the MAC unicast forwarding table:
1. In the Management Tree, click Bridge.
2. Click on the Unicast Forwarding Handler link.
1553-CXP 901 4102/10 Uen F 2009-09-25 83

3. Click the Create New Static Forwarding Entries button to open the Static
Unicast Forwarding screen.
4. Click the Add icon.

You must define the following attributes:
• VLAN ID: Set the VLAN ID for which this entry applies
• MAC Address: Set the MAC address. The MAC address must be a
unicast address
• Port: Set the bridge port number of the port through which the MAC
address can be reached
Note: Static Status is set to Permanent and you cannot change this.
5. Save.
7.2.1.2 Multicast Static
To configure an entry in the MAC multicast forwarding table:
1. Click on Bridge in the Management Tree.
2. Click on MAC Multicast, then in the resulting browser window click on

Multicast Static.
3. Click the Add icon.
4. You must define the following attributes:
• VLAN ID: Set the VLAN ID for which this entry applies
84 1553-CXP 901 4102/10 Uen F 2009-09-25

• MAC Group Address: The MAC group address must be a multicast or

broadcast address
Note: Multicast Status is set to Permanent and you cannot change this.
5. Save.
When you save the entry, the Static Egress Ports and Static Forbidden Ports
fields become populated with Link icons. Click each one to set up the relevant
ports as follows:
• Static Egress Ports: Define the set of ports through which the
multicast/broadcast frame must be forwarded regardless of any dynamic
information. Enter the set of ports by selecting the required one from the
drop-down list and then adding further entries as required
• Static Forbidden Ports: Define the set of ports through which the frames
must not be forwarded regardless of any dynamic information. Enter the
set of ports by selecting the required one from the drop-down list and then
adding further entries as required
Note: When you add multicast forwarding information to the table, the same
entry is automatically added to the Bridge > MAC Multicast > Multicast
Forwarding table. The Multicast Forwarding table contains both static
(that is, user-defined) and learned entries related to group (multicast)
addresses.
7.2.2 IGMP Snooping

When a host wants to receive multicast traffic, it must inform the routers on its
LAN. The Internet Group Management Protocol (IGMP) is the protocol used
to communicate group membership information between hosts and routers on
a LAN. Based on the information received through IGMP, a router forwards
multicast traffic only through interfaces known to lead to interested receivers
(hosts).
On the contrary, bridges flood multicast traffic out on all ports by default, and
therefore waste valuable network resources. IGMP snooping on a bridge
can eliminate this inefficiency. IGMP snooping looks at IGMP messages to
determine which hosts are actually interested in receiving multicast traffic.
Based on this information, the bridge will forward multicast traffic only to ports
where multicast receivers are attached.
7.2.2.1 Enabling IGMP Snooping
To enable IGMP snooping on the NE:
1. Click on Bridge in the Management Tree.
2. Click on the MAC Multicast link in the browser.
3. Set the MAC Multicast Enable field to Enabled.
1553-CXP 901 4102/10 Uen F 2009-09-25 85

4. Click on the IGMP Snooping attribute in the attribute window.
5. Save your change and then select the IGMP Snooping link.
6. Set the IGMP Snooping Enable field to Enabled.
7. Save.
7.3 Miscellaneous
7.3.1 Configure Spanning Tree Protocol

The Spanning Tree Protocol (MSTP/RSTP) allows Layer 2 devices to discover
a subset of the topology that is loop-free, but still with a path between every
pair of LANs.
This version supports Rapid Spanning Tree Protocol (RSTP) according to

802.1d 2004, which is compatible with STP.
By default (when enabled) the device is set up to run RSTP, but when inserted
into a topology which runs MSTP, the algorithm will adapt to run this version
instead.
To configure STP:
1. Click Bridge in the Management Tree.
2. Select the Spanning Tree Service link.

As you can see in the figure below, you can enable or disable STP, and
choose STP type RSTP or MSTP. The links to the respective screens
become active according to your STP type selection.
3. Save your change and continue from the appropriate section - Section 7.3.2
Configure Rapid Spanning Tree Protocol (RSTP) on page 86 or Section
7.3.3 Configure Multiple STP (MSTP) on page 87.
Figure 81 Spanning Tree Service
7.3.2 Configure Rapid Spanning Tree Protocol (RSTP)

The NE supports RSTP according to the standard IEEE 802.1D (2004).
86 1553-CXP 901 4102/10 Uen F 2009-09-25

To configure RSTP:
3. Select the RSTP link.
4. Save.
7.3.3 Configure Multiple STP (MSTP)

A major limitation for STP/RSTP is that the protocol is VLAN unaware. This can
lead to sub-optimal use of the redundant link, and in the worst case blocked
links can prevent some VLANs from communicating.
MSTP allows you to define several spanning tree instances and to map several
VLANs to a single spanning tree instance.
OMS 1410 supports MSTP in accordance with the standard IEEE 802.1Q
(2003), and with up to 16 spanning tree instances.
3. Select the MSTP link.
4. Set the parameters as described below and select Save.
1553-CXP 901 4102/10 Uen F 2009-09-25 87

Figure 82 MSTP
Table 20 MSTP Parameters

The format selector value of the Configuration Identifier.
Format selector 0..0 This has a value of 0 to indicate the format specified in
the IEEE 802.1Q standard
0 to 32 ASCII Name of the MST region to which this device belongs
Configuration Name Characters
Revision Level 0 to 65535 Revision number of the MSTP configuration
Configuration Digest Read Only Numerical value derived from the VLAN-to-instance
mapping table
• Blank (---) Resets the MSTP values to their default values
Reset to default
• Reset to default
7.3.3.1 MST Common and Internal Spanning Tree (CIST)
Select MST CIST from the MSTP screen.
88 1553-CXP 901 4102/10 Uen F 2009-09-25

Figure 83 MST CIST
7.3.3.2 MST Instance
Select MST Instance from the MSTP screen.
Figure 84 MST Instance
7.3.4 MAC Multicast
Multicast is a method of sending one packet to multiple destinations.

Multicasting is used for applications such as video conferencing, and for
distribution of certain information like some routing protocols. A standard IEEE
802.1D bridge will forward multicast frames on all ports that are members of the
same VLAN as the port receiving such frames. This might not be desirable if
there is a lot of multicast traffic being transported through a multi-port bridge
where the recipients are connected on only one (or a few) of the bridge ports. To
alleviate unnecessary bandwidth consumption, the OMS 1410 supports specific
tables to control the forwarding of Multicast traffic if desired. Both devices also
1553-CXP 901 4102/10 Uen F 2009-09-25 89

support IGMP snooping which is used to update the multicast tables based on
the IGMP messaging between end nodes and IP multicast routers.
Note: Multicast traffic will be forwarded as usual if this feature is not enabled;
the use of these tables is only necessary for performance tuning.
7.3.4.1 Enabling MAC Multicast Control Tables
The internal resources of the NE used for the multicast tables are shared with
the VLAN tables. The total of VLAN entries and multicast groups registered is
4000, and both types of entry occupy the same amount of resources. Hence, to
enable the Multicast feature, make sure that the maximum number of VLANs is
less than 4000 according to how many multicast groups are anticipated. For
most applications, 4000 VLANs are well above what will be used, and in these
cases you can safely reserve a good chunk of entries for multicast traffic.
7.3.4.2 Configuring MAC Multicast
2. Select the MAC Multicast link.
MAC Multicast Enable allows you to enable/disable the MAC Multicast control
tables.
The MAC Multicast screen has the following links:
• Multicast Forwarding - see below
• Multicast Forward All - this screen lists the VLAN IDs and contains a link
to the All Static Ports screen where you can maintain a list of ports for
each VLAN ID
• Multicast Static - see Section 7.2.1.2 Multicast Static on page 84
• IGMP Snooping - see Section 7.2.2 IGMP Snooping on page 85
• Multicast Forward Unregistered - see Section 7.3.4.4 Multicast Forward

Unregistered on page 91
7.3.4.3 Multicast Forwarding
The Multicast Forwarding table contains multicast filtering information

configured into the bridge, or information learnt through IGMP Snooping. The
Multicast Forwarding table information specifies the allowed egress ports for a
given multicast group address on a specific VLAN, and indicates for which ports
(if any) this information has been learnt from IGMP snooping.
• VLAN ID: Identifies the VLAN to which the filtering information applies
• MAC Group Address: The MAC group address must be a multicast or

broadcast address
90 1553-CXP 901 4102/10 Uen F 2009-09-25

• Static Egress Ports: This links to the Static Egress Ports screen where
you define the set of ports through which the multicast/broadcast frame
must be forwarded regardless of any dynamic information. Enter the set
of ports by selecting the required one from the drop-down list and then
adding further entries as required
• Dynamic Ports: This links to the Static Egress Ports screen which lists all
ports that have been learnt dynamically
7.3.4.4 Multicast Forward Unregistered
The Multicast Forward Unregistered table defines the behavior of ports

regarding forwarding of packets that is not covered by any of the other tables.
• VLAN ID: Identifies the VLAN to which the filtering information applies
• Unregistered Static Ports: Links to the Unregistered Static Ports screen

where you can maintain the ports on a VLAN that can participate in a
Forward Unregistered group
7.4 Manage VLAN

This section guides you through management of a VLAN (Virtual Local Area
Network) on the NE.
The section also involves management of the complete life cycle of a VLAN,
including:
• Creation, presentation, modification, and deletion of a VLAN
• Creation, presentation, modification, and deletion of an Ethernet User

Defined Protocol
• Presentation and modification of GVRP (Generic Attribute Registration

Protocol VLAN Registration Protocol)
7.4.1 Virtual Local Area Networks

A LAN consists of a number of computers that share a common communication
line within a small geographical area. A Virtual LAN is a LAN where the grouping
of computers is based on logical connections, for example by types of users, by
department, and so on. It is easier than for a physical LAN to add and delete
computers to/from a VLAN and to manage load balancing. The management
system relates the virtual picture and the physical picture of the network.
The NE supports:
• VLAN per port
1553-CXP 901 4102/10 Uen F 2009-09-25 91

The number of Ethernet-ports that can be assigned to a VLAN is limited to 64.

The maximum number of Ethernet-ports per slot is 16.
There are three steps involved in the definition of a VLAN on the NE.
• Define a common VLAN type for the Bridge
• Define a set of common parameters for a new VLAN
• Add new ports to a VLAN
It is assumed you have the appropriate rights to perform management

operations.
7.5 VLAN Provisioning

The LCT has a custom screen for VLAN provisioning, see Figure 85 on page
92. The VLAN Setting screen makes VLAN related configuration easier by
grouping together a number of items and attributes under a unique screen.
Open the VLAN Settings screen either by clicking on VLAN Setting from
the Equipment menu on the LCT desktop, or by clicking on Bridge in the
Management Tree, and selecting the VLAN Setting link from the Bridge screen.
Figure 85 VLAN Settings
The following examples show how a VLAN can be created and provisioned
with the VLAN Settings screen.
7.5.1 Create a New VLAN

1. Click the Add icon on the toolbar.
92 1553-CXP 901 4102/10 Uen F 2009-09-25

2. The screen suggests default values for most of the attributes. Edit the
Description, and/or Learning attributes if required.
3. Save. When you save the entry, the system assigns a MAC address to it.
7.5.2 Configuration of a VLAN Port Member
7.5.2.1 Add Port Members to an Existing VLAN
1. Select the VLAN to which ports will be added. The VLAN is highlighted in
the Virtual Local Area Network pane (top pane). The list of ports already
members of the VLAN is displayed in the VLAN Ports pane (bottom pane).
2. Activate the VLAN Ports pane by clicking anywhere in the pane. The color
of the title bar for the VLAN Ports pane changes to indicate that the pane
is selected.
3. Click Add (or right click in the Ports pane and select Add from the pop-up
menu).
4. A new line is added to the Ports pane. Select the Port by clicking in the Port
field and selecting a valid port from the drop-down list.
1553-CXP 901 4102/10 Uen F 2009-09-25 93

5. Enable or disable the Tagging as required.
6. Save.
94 1553-CXP 901 4102/10 Uen F 2009-09-25

Ethernet Services Wizard
8 Ethernet Services Wizard
This chapter describes management of Ethernet services on the OMS 1410

NEs. The section does not cover a network level view of the Ethernet service
aspect.
Note: In the following section we assume that the creation of UNIs, Ethernet
services and some profiles are done in the Ethernet Services wizard,
while maintenance is performed from the Management Tree.
8.1 Recommended Reading

The following readings are recommended:
• Technical Product Description - Ethernet Overview
• http://www.metroethernetforum.org for both basic and in-depth studies
8.2 Ethernet Service Wizard

Note: Make sure that the end points of a service have the same configuration
if required, since the wizard is not end-to-end aware.
8.2.1 Start the Ethernet Service Wizard

• From the Equipment menu select Ethernet Service Wizard.
1553-CXP 901 4102/10 Uen F 2009-09-25 95

8.2.2 Welcome Page
With the wizard, you can configure UNIs and provision Ethernet services on the
OMS 1410.
Note: Use the wizard only for creation. General management of existing
Ethernet services and UNIs is done from the Management Tree.
After completing a wizard flow, you need to close the wizard and
reopen it to start a new flow.
Click Next when you are ready to begin the provisioning process.
8.2.3 Task Selection
The task selection page allows you to choose between UNI Definitions or
Ethernet Service provisioning.
Figure 86 Task Selection
8.2.3.1 UNI Definitions
Configure UNIs on the NE. All LAN and WAN ports on the NE can be configured
as UNIs.
A UNI is the physical demarcation point between the responsibility of a service

provider and the responsibility of the subscriber to Ethernet services.
96 1553-CXP 901 4102/10 Uen F 2009-09-25

On an NE this is represented as a characteristic of a LAN or a WAN port. The

LAN/WAN ports are not always associated with a UNI instance; for example if
used for transport inside the Metro Ethernet Network (MEN).
Note: At least one UNI on the NE is a pre-requisite for Ethernet service

provisioning.
8.2.3.2 Ethernet Service
Provision a new Ethernet service on the target NE. The wizard will not let you
provision any Ethernet service unless UNIs exist on the NE.
Note: The wizard is only provisioning the service on one NE at a time and
must be re-run on all elements containing UNIs in the service to
provision the Ethernet service network-wide.
8.3 Create a UNI

• In the Task Selection select UNI Definitions and click Next.
8.3.1 UNI Basic
In the first page, you configure a LAN or WAN port as a UNI. A UNI must be
assigned a name that is unique in the network. The system does not support
any uniqueness check.
Figure 87 UNI Basic
1553-CXP 901 4102/10 Uen F 2009-09-25 97

The UNI’s properties are assigned default values when possible.
1. Enter a name for the UNI that is unique in the network.
2. Select the Port drop-down list. The system presents available Ethernet
ports to be defined as a UNI. All ports defined as Layer 2 ports, Layer 1
ports, and all ports for which no capability has yet been set are presented
as UNI candidates.
For the ports already configured as Layer 2 ports, the system presents
the provider bridge port type (Customer Edge Port (CEP) or Customer
Network Port (CNP)) configured on the port (this applies only if the bridge
is configured as a provider bridge).
For ports for which no capability has yet been set, the system lets you
configure the capability for the port through the Layer attribute: the legal
values are L1, L2 CEP, and L2 CNP. The system also indicates the type
of the Ethernet interface, GE or XGE (10 GE).
Note: You cannot change speed and duplex setting on a LAN/WAN port
defined as UNI. Changes to port settings can only be done after
removing services and disabling UNI associated.
3. Edit the desired UNI properties.
Table 21 General/Port Selection

Attributes Description
UNI Identifier Assign a name to the UNI instance that is unique in the MEN
Select a LAN/WAN port. Physical port parameters for the LAN port speed and flow
Port control are presented
Table 22 UNI Properties

Service multiplexing:
If service multiplexing is enabled on a UNI, the UNI can be associated
with more than one service/Ethernet Virtual Connection (EVC)
Bundling:
Ranges of CE VLAN IDs can be mapped to service/EVC
Service multiplexing/bundling
One to One bundling:
Only one CE VLAN ID for each service/EVC
All to One bundling:
All CE VLAN IDs at UNI will be mapped to one service/EVC
Untagged VLAN ID All untagged traffic at the CE will be assigned this VLAN ID. It is used
for CE VLAN ID to EVC mapping
98 1553-CXP 901 4102/10 Uen F 2009-09-25

0-7
Default Port Priority
All untagged traffic at the CE will be assigned this L2 priority
This parameter is used to specify which VLAN (C-VLAN or S-VLAN) is
used to classify traffic into EVC at the UNI. If the selected UNI is L2 CEP,
Flow Classification only C-VLAN classification is allowed. If the selected UNI is L2 CNP, only
S-VLAN classification is allowed. If the selected UNI is L1, both C-VLAN
and S-VLAN classifications are allowed
8.3.2 Layer 2 Control Protocol (L2CP)

The next page of UNI creation is to set the disposition of the Layer 2 Control
Protocol.
Each protocol or set of protocols has its individual disposition value. The
disposition value tells the element how to treat a relevant frame. The available
dispositions depend on the Port Selection settings in the UNI Basic screen:
• Discard
• Forward unchanged
• Peer (only available for L2 Port UNIs)
• Tunnel (only available for L2 CNP Port UNIs) - the L2CP frames are
tunnelled through the Provider network using the L2CP tunnelling mode
When Tunnel is selected as the disposition, the L2CP Tunnelling Mode as

selected on the Bridge screen is used. This is shown as a read-only value
above the Protocol list.
1553-CXP 901 4102/10 Uen F 2009-09-25 99

Figure 88 Layer 2 Control Protocol
8.3.3 Summary
The Summary page shows the UNI you are about to create. Pressing Finish
commits the changes.
The view switches to the Progress tab and shows the progress of this operation.
Figure 89 Summary
100 1553-CXP 901 4102/10 Uen F 2009-09-25

Note: To clear the entered values from the wizard, you have to close it and
restart it to start a new UNI creation flow.
8.4 Create Ethernet Service

In this function you can configure the EVC service attributes. The Ethernet
Service must be assigned a name that is unique in the network and a
description. The system does not support any uniqueness check.
1. Assign an Ethernet service name (there is a one-to-one relation between

the Ethernet Service and EVC) that must be unique in the MEN.
2. Configure the Preservations attributes.
3. Select Next to continue.
Table 23 Ethernet Service Parameters

Attribute Description
EVC Identifier Enter a unique name of the EVC
Description Administrative description
CE VLAN ID Tick to enable preservation, untick to disable preservation
CE VLAN CoS Tick to enable preservation, untick to disable preservation
8.4.1 UNI List
The UNI List page consists of three tables: .
1553-CXP 901 4102/10 Uen F 2009-09-25 101

• UNIs in the EVC is where you add UNIs to the Ethernet Service
• CE VLAN Id to EVC Mapping is where you view and add CE VLAN entries
to the EVC at the selected UNI
• Storm Protection is where you can enable or disable storm protection for
the thresholds applicable to the selected UNI
Figure 90 UNI List
1. UNIs in the EVC: Click the Add Icon and select one or more UNIs.
For each UNI, the bandwidth profile target (UNI, UNI and CoS, EVC, and
EVC and CoS) can be configured if the UNI is not already in another
service. If it is already in another service, the bandwidth profile target is
already configured, and cannot be changed.
2. CE VLAN Id to EVC Mapping: Click the Add Icon, and configure the
CE-VLAN IDs to be mapped From and To in the Ethernet service under
creation.
For each associated UNI, you must configure which CE VLAN ID(s) are
mapped to this EVC (Ethernet service). If more than one CE VLAN ID
is mapped to an EVC, the UNI must have the bundling attribute enabled
and if the all-to-one-bundling attribute is set, all CE VLAN IDs are mapped
to one EVC.
When a UNI is selected in the top table, the CE-VLAN to EVC mapping table
shows all the Ethernet services currently defined at this UNI. The Ethernet
service under creation is identified by (this service) in the Service Id column.
It is also possible to allocate all non-explicitly specified CE-VLAN ID to one
EVC by configuring a default mapping.
102 1553-CXP 901 4102/10 Uen F 2009-09-25

3. Storm Protection: The storm protection granularity depends on the

bandwidth profile target. For a bandwidth profile target set to UNI or UNI
and CoS, storm protection applies for the whole UNI selected in the top
table. For bandwidth profile target set to EVC or EVC and CoS, storm
protection applies for the EVC under creation.
The amount of unknown unicast and/or multicast and/or broadcast traffic is
limited to a user specified threshold. There is one threshold for unknown
unicast traffic, one threshold for multicast traffic, and one threshold for
broadcast traffic. These three thresholds are independent from each other.
The traffic that is higher than the threshold is dropped.
Table 24 UNIs in the EVC

Parameter Values
UNI Available User Network Interfaces
• UNI
Bandwidth Profile • UNI and CoS

Target • EVC
• EVC and CoS
Table 25 Selected UNI CE VLAN ID to EVC Mapping

Enable Default CE VLAN • Enabled (ticked) If enabled, all non-explicitly specified CE-VLAN
Mapping IDs are mapped to the EVC specified by the
• Disabled Default Service ID parameter
• Do Not Use Identify the EVC used for default mapping (see
above)
Default Service ID • Available EVCs
• (this service)
From CE-VLAN ID 1 to 4094 Start of a range
To CE-VLAN ID 1 to 4094 End of a range
Service ID Read-only System generated service identification. The

service under creation is identified by (this service)
Table 26 Storm Protection

Storm Protection
• Enabled
• Broadcast (ticked)
• Multicast • Disabled
• Unknown unicast
Max Information Read-only Maximum rate allowed
Rate
1553-CXP 901 4102/10 Uen F 2009-09-25 103

8.4.2 Bandwidth Profile (BWP) Assignment
In this function a bandwidth profile is assigned to each specified flow of ingress

service frames.
8.4.2.1 About BWP
A Bandwidth Profile is a characterization of the lengths and arrival times

for ingress Service Frames at the UNI. When a Bandwidth Profile is applied
to a given sequence of ingress Service Frames, each Service Frame in the
sequence is declared to be compliant or not compliant with the Bandwidth
Profile.
Figure 91 Bandwidth Profile
The Bandwidth Profile Target defines the flow to which the ingress bandwidth
profile is applied.
The possible targets are:
• UNI: the bandwidth profile is applied to all ingress service frames at the UNI
• UNI and CoS: the bandwidth profile is applied to all ingress service frames
with a specific Class of Service at the UNI
• EVC: the bandwidth profile applied to all ingress service frames of the
EVC at the UNI
104 1553-CXP 901 4102/10 Uen F 2009-09-25

• EVC and CoS: the bandwidth profile is applied to all ingress service frame
with a specific Class of Service of the EVC at the UNI
When the bandwidth profile target is either UNI and CoS or EVC and CoS,
the CoS profile must be specified. The CoS profile is used to specify how the
service frames are classified into different CoS groups based on their incoming
CoS value (for OMS 1410 r1.0, only 802.1p is supported as CoS type). The
CoS Bandwidth Profile table is then used to specify bandwidth profile and CoS
Level per CoS group.
When the bandwidth profile target is either UNI or EVC, only the Bandwidth
Profile Target and the CoS Level parameters in the top table are relevant.
The CoS Level attribute represents one of the 8 classes supported by OMS
1410:
• Network Control
• Internetwork Control
• Voice
• Video
• Critical Applications
• Excellent Effort
• Background
• Best Effort
as defined by IEEE 802.1. A CoS Level must be associated with each flow
to be rate limited.
The CoS Level does infer a degree of relatively better performance in at

least some performance objectives with network control as the class with the
highest performance, though they do not suggest any particular type of priority
mechanism (strict, weighted, and so on). You can configure how the different
CoS Levels are mapped to 802.1p priority. The mapping is defined in the CoS
Level to 802.1p Profile table available under CoS in the Management Tree.
The Bandwidth Profile Target attribute presents all the globally defined
bandwidth profiles as well as an option called private profile. If you select this
private profile, a dialog box opens, allowing you to configure a bandwidth profile
specifically for this service or UNI.
Select Edit BWP Profiles in the lower left corner of the wizard screen to open
the Global Bandwidth profiles in a new window.
1553-CXP 901 4102/10 Uen F 2009-09-25 105

Figure 92 Edit BWP Profiles
This window shows the table as you would see it from the Management Tree.
When new profiles are added here, they will show up in each drop-down list in
the wizard tables, after clicking the Refresh button in the relevant wizard screen.
8.4.3 Bandwidth Capacity on One UNI

A bandwidth profile is always associated with a UNI, either directly when
associated with the UNI or indirectly when associated with UNI and COS, or
EVC, or EVC and CoS. The UNI has a total possible bandwidth capacity that
can be supported.
8.4.4 Transport Setup

The Transport Setup screen is used to associate the service under creation
with a specific transport entity.
106 1553-CXP 901 4102/10 Uen F 2009-09-25

Figure 93 Transport Setup
8.4.4.1 Transport Definition for EVC
The following transport types are available:
• L2 VLAN: only available for a service defined as a Layer 2 UNI
• L1 VLAN MUX: only available for a service defined as a Layer 1 UNI
The possible transport entities are available from a drop-down in the Transport
Type field. If an L2 VLAN is used for transport, additional VLANs can be defined
at this stage by the Edit VLAN Settings button on the bottom left of the page.
If an L1 VLAN MUX is used for transport, the Push parameter is set to enabled
(ticked) and cannot be changed. This pushes the incoming service frames
before forwarding them through the L1 VLAN MUX. The VLAN ID parameter
specifies which tag is pushed.
8.4.4.2 Mapping of the CoS Level to the Transport Technology
The last step is to define how the CoS Level should be mapped to the transport
technology. In R1.0, OMS 1410 supports L2 VLAN and L1 VLAN MUX as
transports. Both use 802.1p to indicate CoS. You can define several CoS
Levels to 802.1p mapping profiles in the CoS Level to 802.1p Profile table
available under CoS in the Management Tree. The CoS Mapping parameter
in the wizard is used to select one of those profiles. The selected profile is
displayed for information in the wizard.
1553-CXP 901 4102/10 Uen F 2009-09-25 107

8.4.5 Summary
The Summary shows the details of the Ethernet Service.
• Press Finish to commit and save your changes.
The view automatically switches to the Progress tab and shows the progress
of the operation.
Figure 94 Summary
The system updates the number of currently active EVCs on the UNI.
8.5 Management Tree
8.5.1 Ethernet Services - Maintenance

After creating Ethernet Services with the wizard you can use the Management
tree for maintenance purposes on the active Ethernet Services.
• In the Management Tree, select Ethernet Services.
Figure 95 Ethernet Services
The following subsections describe the different maintenance tasks available.
108 1553-CXP 901 4102/10 Uen F 2009-09-25

8.5.2 UNI Overview
Select the UNIs folder under Ethernet Service in the Management Tree to
display attributes for currently defined UNIs.
Figure 96 UNI Overview
For details on UNI settings see Section 8.3 Create a UNI on page 97.
8.5.3 Ethernet Service Overview

Attributes for currently defined UNIs.
Figure 97 Ethernet Services
8.5.3.1 Edit Ethernet Service
1. Select the Ethernet Service you wish to edit.

Service related objects available for editing display with bold text. If other
changes are to be made, the Ethernet Service must be replaced by a new
service.
2. Save the updates.
Attribute value change notifications are generated to inform other connected

management systems about the updated instance.
• Description: Free text service description
• EVC Identifier: Unique name of the Ethernet Virtual Connection
• CE VLAN ID Preservation: Enabled or Disabled
1553-CXP 901 4102/10 Uen F 2009-09-25 109

• CE VLAN CoS Preservation: Enabled or Disabled
The links from this screen lead to:
• Remote UNI List which gives read-only information
• Local UNI List
The Local UNI List is used to add/remove a UNI to/from the selected service.
Additional parameters are available by selecting the FCP (Flow Control Point)
object under eth service:xx in the Management Tree. An FCP is the logical
representation of the EVC termination at a UNI.
Figure 98 FCP Object
8.5.3.2 Delete Ethernet Service
1. Select Ethernet Services in the Management tree.
2. Select the Services folder in the Management Tree. The system presents a
list of all configured Ethernet Services on the NE.
3. Select the Ethernet Service to be deleted and click Delete.
110 1553-CXP 901 4102/10 Uen F 2009-09-25

Figure 99 Delete Ethernet Service
The system releases all associations to profiles and updates the number of
users for the profiles.
The system removes the Ethernet Service CE VLAN ID(s) from the CE VLAN
ID to EVC mapping contained by UNIs of the service. The system updates the
number of currently active EVCs on UNIs. The system deletes PM data for
this service.
8.5.4 Bandwidth Profile Definitions
The link to this screen is from the Ethernet Services screen.
Figure 100 Bandwidth Profile Link
The bandwidth profile defines the set of traffic parameters applicable to a

sequence of service frames. Associated with the bandwidth profile is a
rate-limiting algorithm (policing) to determine service frame compliance with
the specified parameters. In this implementation there is currently one type of
bandwidth profile; Ingress Bandwidth Profile.
A bandwidth profile is enforced by the provider’s network and is part of a

service level specification between the subscriber and the service provider.
The outcome of any rate-limiting algorithm within the service provider network
is a set of service frames that are labeled as Green, Yellow, or Red based on
their level of conformance to the used bandwidth profile. Frames marked Red
are always dropped.
The parameters forming a bandwidth profile are:
• Committed Information Rate (CIR) expressed as bits per second. CIR >=0
1553-CXP 901 4102/10 Uen F 2009-09-25 111

• Committed Burst Size (CBS) expressed as bytes. When CIR > 0, CBS is
greater than or equal to the maximum service frame size
• Excess Information Rate (EIR) expressed as bits per second. EIR >=0
• Excess Burst Size (EBS) expressed as bytes. When EIR > 0, EBS is
greater than or equal to the maximum service frame size
• Color Mode (CM) has only one of two possible values, color-blind and
color-aware
• Coupling flag
The Coupling Flag (CF) is set to either 0 or 1. The choice of the value for
CF has the effect of controlling the volume of the yellow Service Frames
admitted to the network. When CF is set to 0, the long-term average bit
rate of bytes in yellow service frames admitted to the network is bounded
by EIR. When CF is set to 1, the long term average bit rate of bytes in
yellow Service Frames admitted to the network is bounded by CIR + EIR
depending on the volume of the offered green Service Frames. In both
cases the burst size of the yellow service frames admitted to the network
is bounded by EBS.
Since the CF has negligible effect in color-blind mode, a service definition
that uses color-blind operation does not require you to specify the value of
the CF.
Table 27 An Example of a Bandwidth Profile

Parameter Setting
CIR 50M
CBS 16 Kbit
EIR -
EBS -
Color mode Color blind

Coupling flag EIR bound
Figure 101 Bandwidth Profile Definitions
The system presents a list of all bandwidth profiles. Each profile is presented
with the Current Users parameter indicating how many services are currently
associated with that profile.
112 1553-CXP 901 4102/10 Uen F 2009-09-25

The CIR and EIR parameters can be set from 0 Mbps to 1000 Mbps in steps
of 1 Mbps for a GE port and from 0 Mbps to 4 Gbit/s in steps of 1 Mbps for a
10 GE port.
CBS/EBS are configurable from 100kBytes to 2 MB in steps of 100kBytes

both for GE and 10GE ports.
8.5.4.1 Delete Bandwidth Profile
• From the Bandwidth Profile Definitions screen, select a bandwidth profile

for deletion
• Click the Delete button at the right of the screen
0 The system verifies that the bandwidth profile is not in use by any
Ethernet service on the NE. If not in use, the profile is deleted. If it is in
use, the system warns and denies the deletion
8.5.5 Ethernet Service Performance Monitoring (PM)

The NEs support performance monitoring per flow. It is reported data about the
number of ingress and egress green, yellow, and red frames and green, yellow,
and red octets. Green frames are the frames that conform to the CIR/CBS part
of the bandwidth profile and are the traffic that can be guaranteed. The yellow
frames are the frames that meet the EIR/EBS part of the profile.
The red frames are the frames that violate both the CIR/CBS and EIR/EBS
parameters and are dropped.
Performance data is available for all flows.
The available time periods are:
• 15-minute (Metro Ethernet Forum (MEF) requirement)
• 24-hour
The NE holds current data and historical data, the number of historical time
periods are
• 32 x 15-minutes (MEF requirement)
• 1 x 24-hours
8.5.5.1 Clear PM Counters
To clear Ethernet PM counters, select Ethernet Services in the Management

Tree, then from the Clear PM Counters drop-down list, select either Clear All
PM Counters or select a specific UNI or FCP entry. Press Save.
1553-CXP 901 4102/10 Uen F 2009-09-25 113

Figure 102 Clear PM Counters
In the Ingress PM Overview screen you can view details and clear the counters
of various ingress UNIs or services.
8.5.6 Definitions
8.5.6.1 From Metro Ethernet Forum
Table 28 Metro Ethernet Forum

AVC Attribute Value Change
A characterization of ingress Service Frame arrival times and
Bandwidth Profile lengths at a reference point and a specification of the disposition
of each Service Frame based on its level of compliance with the
Bandwidth Profile. In this document the reference point is the UNI
CE-VLAN ID Customer Edge VLAN ID
CBS is a Bandwidth Profile parameter. It limits the maximum
Committed Burst Size number of bytes available for a burst of Service Frames sent at the
UNI speed to remain CIR-conformant
CIR is a Bandwidth Profile parameter. It defines the average rate in
bits/s of Service Frames up to which the network delivers Service
Committed Information Rate Frames and is committed to meeting the performance objectives
defined by the CoS Service Attribute
Egress Service Frame A Service Frame sent from the Service Provider network to the CE
E-LAN Service Ethernet LAN Service
E-Line Service Ethernet Line Service
An Ethernet Service Type distinguished by its use of a
Ethernet LAN Service Multipoint-to-Multipoint EVC
Ethernet Line Service An Ethernet Service Type distinguished by its use of a Point-to-Point
EVC
Ethernet Virtual Connection An association of two or more UNIs that limits the exchange of
Service Frames to UNIs in the Ethernet Virtual Connection
EVC Ethernet Virtual Connection
EBS is a Bandwidth Profile parameter. It limits the maximum
Excess Burst Size number of bytes available for a burst of ingress Service Frames
sent at the UNI speed to remain EIR-conformant
114 1553-CXP 901 4102/10 Uen F 2009-09-25

EIR is a Bandwidth Profile parameter. It defines the average rate

Excess Information Rate in bits/s of ingress Service Frames up to which the network may
deliver Service Frames without any performance objectives
Ingress Service Frame A Service Frame sent from the CE into the Service Provider network
MEN Metro Ethernet Network
An Ethernet frame transmitted across the UNI toward the Service
Service Frame Provider or an Ethernet frame transmitted across the UNI toward
the Subscriber
The contract between the Subscriber and Service Provider
Service Level Agreement specifying the agreed service level commitments and related
business agreements
Service Provider The organization providing Ethernet Service(s)
Subscriber The organization purchasing and/or using Ethernet Services
UNI User Network Interface
User Network Interface The physical demarcation point between the responsibility of the
Service Provider and the responsibility of the Subscriber
8.5.7 CIR and EIR

If only one bandwidth profile applies to all service frames on a UNI, then CIR +
EIR <= port capacity.
If more than one flow (or sequence of service frames) is defined for the UNI,
the sum of all CIRs in the used bandwidth profiles must not exceed the port
capacity. In this situation it is not correct to limit according to CIR + EIR since,
for multiple flows, oversubscription using statistical multiplexing can be used.
1553-CXP 901 4102/10 Uen F 2009-09-25 115

116 1553-CXP 901 4102/10 Uen F 2009-09-25

SDH
9 SDH
This chapter describes the basic configuration of the SDH ports. For more
information, please see the Technical Product Description.
9.1 SDH Screen
Figure 103 SDH Screen
9.1.1 Configuring SDH Port Structure

By default the SDH ports are unstructured when created. Only SDH Port, rs, ms
and aug(n) are available. In this state the paths inside the STM-n frame cannot
be terminated nor cross-connected, but the port can be used as a protection
port in an MSP protection scheme and a synchronization source candidate. It
can also carry DCN traffic in the DCC channels.
The motivation for structuring an SDH port is to identify the paths in the STM-n
frame and make them available for cross-connection. As you structure the port
it will fan out in the Management Tree, showing termination points that are
now available for cross connection.
9.1.2 SDH Structuring Wizard
9.1.2.1 Change the Structure of an SDH Object
• Select the desired SDH port. Right-click and select Structure.
1553-CXP 901 4102/10 Uen F 2009-09-25 117

0 The SDH Structuring Wizard starts
The following screens appear in sequence in the wizard and allow you to view
the existing structure and make the required changes.
• Structure Information: Displays the current SDH structure. The decisions

you make in subsequent steps will affect this structure
• Structure Type: Select the type of SDH structure you want
• Completing the SDH Structuring Wizard: This step lists all the changes
that will be performed when you press Finish
No changes will be performed until you press Finish, and you can abort the
wizard at any time with the Cancel button.
The following sections show how to perform structuring, using the Management
Tree.
118 1553-CXP 901 4102/10 Uen F 2009-09-25

SDH
9.1.3 Setting and Reading Path Trace Identifiers
Path Trace is available at two levels in the SDH port:
• RS Path Trace that will be terminated in the STM-n port on the opposite
side of the link
• VC-4 Path Trace that will be terminated in the SDH node terminating the
VC-4 path
9.1.3.1 Set or Read RS Path Trace Identifiers
1. Expand an SDH port.

2. Click on rs.
3. Click on the Path Trace link in the browser.
4. The following attributes can be set:
• PathTrace:
0 Set to Enable if TIM alarms should be reported when there is a

mismatch between PathTraceReceived and PathTraceExpected
• PathTraceExpected:
0 Enter a value for the Path Trace Identifier that you expect to receive
from the other side of the path
The C/H button at the end of this field allows you to toggle the
setting between ASCII Characters or Hex values.
• PathTraceTransmitted:
0 Enter a value for the Path Trace Identifier that you want to transmit
to the other side of the path
5. Where a value is available, the following attribute can be read:
• PathTraceReceived:
0 The actual received Path Trace Identifier from the other side of
the link
6. Save.
9.1.3.2 Set or Read VC-4 Path Trace Identifiers
Note: VC4 Path Trace is available only when the SDH port is structured with a
VC-4 object. aug1 structure is 3xTUG-3. See Section 9.1.1 Configuring
SDH Port Structure on page 117.
1. Expand an SDH port to the desired vc4.
1553-CXP 901 4102/10 Uen F 2009-09-25 119

2. Click on Path Trace in the browser and set the path trace parameters. The
attributes are the same as for RS Path Trace.
3. Save.
Note: When Path Trace is set to enabled, AIS is inserted downstream instead
of the original signal when there is a mismatch between expected and
received Path Trace.
9.1.4 Monitoring SDH Port Performance

Performance Monitoring (PM) is available at three levels in the SDH port:
• RS PM: monitoring the near end of the Regenerator Section
• MS PM: monitoring the near and far end of the Multiplexer Section
• VC-4 PM: monitoring the near and far end of the VC-4 path
9.1.4.1 Read RS PM Counters
2. Select the RS item.
3. In the browser, click on PM Near End to read near end PM data or PM

Far End to read far end PM data.
The following attributes are available:
• Current 15-minute BBE, ES, SES, and UAS
• Current 24-hour BBE, ES, SES, and UAS
4. To see the Performance history of the previous 24-hour counters, click

on Interval 24 Hour, or click on Interval 15 Min to see the previous 16 x
15-minute counters.
The following attributes are available:
• Interval 24-hour ES, SES, BBE and UAS
• Interval 15-minute BBE, ES, SES, and UAS
9.1.4.2 Read MS PM Counters
2. Select the MS item.
120 1553-CXP 901 4102/10 Uen F 2009-09-25

SDH

The attributes are the same as for RS PM.
9.1.4.3 Read VC-4 PM Counters
2. Select the aug1 item that contains the VC4 to measure.
3. Select the AU-4 and then the VC4 items as the port expands.

The attributes are the same as for RS PM in Section 9.1.4.1 Read RS
PM Counters on page 120.
9.1.5 Enable the SDH Port to Carry Traffic and Report Alarms
By default the Administrative Status of the SDH port is set to disabled when
the port is created. No traffic will pass through the port and no alarms are
reported before it is enabled.
9.1.5.1 Enable Administrative Status
1. Select an SDH port.
2. In the browser, set Administrative Status to In Service.
3. Save.
Note: When disabled, the SDH port inserts VC4-UNEQ out of the port and
AU-4-AIS towards the cross-connection matrix.
Even if the SDH port is enabled, it will only report alarms if the Alarm
Reporting attribute of the slot is set to Enabled.
9.1.6 Port Synchronization Quality Output Signalling

STM-n signals are often used to carry synchronization information. A dedicated
protocol is used to indicate the quality of the signal that is output from one SDH
node to the next SDH node.
9.1.6.1 Synchronization Quality
1. Select an SDH port.
2. In the browser, set Egress SSM to t0 or Do Not Use. t0 always indicates

the quality status of the internal clock.
3. Save.
1553-CXP 901 4102/10 Uen F 2009-09-25 121

Note: When an SDH port is used as a synchronization source candidate, the

S1 byte is automatically set to Do Not Use.
9.2 SDH Protection Management

This section guides you through management of the 1+1 linear Multiplex
Section Protection (MSP) between two SDH Ports.
The section involves management of the complete life cycle of a MSP, including
creation, presentation, modification, deletion and manual operation the MSP
switch.
9.2.1 Multiplex Section Protection

The 1+1 MSP provides protection of the SDH ports by replacing the supporting
trail when it fails. This is a 100% redundant protection scheme.
Figure 104 Protection Switching Scenarios
Both working and protection trails are enabled and the signal is bridged to
both, see Part a) of Figure 104 on page 122. The received signal from the
working trail is forwarded to the receiving client while the protection is not. If the
working trail fails and a switch is performed, the traffic on the protection trail
is received by the client, see Part b) of Figure 104 on page 122. Traffic from
the working trail is ignored.
The NE uses a bidirectional switching protocol - that is, both ends of the trail
switch simultaneously. To synchronize this simultaneous switching, the NEs
signal to each other in the K1 and K2 bytes in the MS overhead of the SDH
traffic. A bidirectional switching protocol gives better control of the traffic in
122 1553-CXP 901 4102/10 Uen F 2009-09-25

SDH
the network but uses a little more time to perform the switching than does a
unidirectional switching protocol.
The switching has two different modes:
• Revertive: traffic returns to the working trail when the working trail recovers
• Non-revertive: traffic stays on the protection trail indefinitely or until

manually changed
The time to wait before traffic reverts to a recovered working trail can be defined.
When switching either from or to protection, an event notification is given.
9.2.2 Protect Section by MSP

1. In the Management Tree, right click on the SDH port that you want to be
the MSP working port.
2. Select MSP > Add in the pop-up menu.
3. The Add MSP screen requests the protection details.
4. Select the Protection parameters as detailed in Table 29 on page 124.
5. Save.
1553-CXP 901 4102/10 Uen F 2009-09-25 123

Table 29 MSP Protection Parameters

Protection SDH Port Available Ports The list will only contain ports that satisfy the
following conditions:
Working and Protection Ports must be
selected from Slot 1 and 2 or 3 and 4. For
example, it is not possible to set up MSP
protection with Working Port from Slot 1 and
Protection Port from Slot 3. Working and
Protection Ports can be selected from the
same slot
A Protection Port must be unstructured on
the highest structurable level:
• aug4 for STM-4 and STM-16

• aug1 for STM-1
Note that STM-4 and STM16 ports are
automatically structured to the AUG-1 level
and must manually be structured to the
AUG-4 level.
The port must not be connected to a remote
module
Working and Protection Ports must both
have the same STM-n rate
Enabled • Enabled Define whether the protection scheme is
currently enabled or disabled
• Disabled
Mode • Unidirectional
• Bidirectional
Operation Type • Reverting Define whether traffic should revert to the
original working path following its recovery
• Non-Reverting
WTR Time 0 to 720 seconds When Reverting is selected above, this is the
time that the system waits before restoring
traffic to a working path that has recovered
Once Enabled, The MSP scheme is created and starts working immediately.
In the Management Tree, you will also see that an MSP item is now available
under both the working and protection ports. You will also see that if the MSP
has the same Identifier as the parent SDH port, the port is a Working port. If
it has an Identifier that is different from the parent SDH port (for example the
SDH port is 1.4 and its MSP is 1.2) this shows the port is a protection port for
the relevant SDH port (in this example, SDH port 1.4 is protecting port 1.2).
9.2.2.1 Modify MSP
1. In the Management Tree, expand the SDH port that is the working port.
2. Select the MSP object below the SDH port.
3. Modify the attributes of the MSP scheme.
4. Save.
124 1553-CXP 901 4102/10 Uen F 2009-09-25

SDH
Figure 105 Amend MSP
Note: If the link is operating on the Protection section in bidirectional mode,

you may break traffic if you set the attributes Enabled to Disabled or
Operating Mode to Unidirectional in one of the nodes. This is due to
the behavior of the Automatic/Autonomous Protection Switch(ing)
(APS) protocol.
To avoid problems, always make sure the link is operating on the
Working section and to command it to lockout of protection before
making any modifications.
9.2.2.2 Delete MSP
Note: Be aware that it is possible to delete an MSP scheme when traffic is on

the Protection Section. This causes a short break during switchover
time (if the working section is available).
To avoid problems, always make sure the link is operating on the
working section and to command it to lockout of protection before
deleting the MSP.
1. In the Management Tree, right click the SDH port that is the working port.
2. Select MSP > Delete from the pop-up menu.

The MSP object disappears both from the Working Port and the Protection
Port in the Management Tree.
3. Save.
9.2.2.3 Command MSP Switch
1. In the Management Tree, expand the SDH port that is the working port.
1553-CXP 901 4102/10 Uen F 2009-09-25 125

2. Select the MSP object below the SDH port.
3. In the browser, select the required command from the Command drop-down
list.
4. Save.
Note: Commands will only take effect if there are no higher priority requests
in the system.
A new command will clear the current command before executing the
new command. In this case the new command may not be executed
when the new command has lower priority than the old command
because the MSP searches for the request with highest priority present.
For example sending a Manual Switch to Protection command instead
of a Forced Switch to Protection command will not work if there is a
Signal Degrade request on the protection section.
All commands can be cleared by the Clear command.
9.2.2.4 Legal Combinations of SNCP and MSP
It is possible to use both Sub Network Connection Protection (SNCP) and

Multiplex Section Protection (MSP) simultaneously, as long as the following is
satisfied:
• The Protected SNCP entity can be part of an MSP protected port, but the
Working or Protection entity can not
Consider this example: an STM-4 ring where some TU12s are dropped off the
ring and sent to through an STM-1 link. In this case, SNCP can be used in the
ring, protecting the TU12s to be dropped from the ring towards the NE. MSP can
then be used for the STM-1 link to protect the traffic. This is because the TU12s
that are dropped from the ring are the Protected TU12s, while the TU12s in the
ring are the Working and Protection TU12s. Consequently, it is not possible to
use MSP on the East or West links of the ring, since the TU12s that are carried
here are the Working or Protection part of the SNCP protected paths.
9.2.3 Subnetwork Connection Protection (SNCP)

SNCP is strongly related to the cross-connection that is protected in the NE. In
the LCT, SNCP related issues are handled from the Cross-Connections screen.
Note: The maximum number of SNCP instances that can be used with a
guaranteed switching time below 50 ms, is 252. This corresponds to
one full STM-4 (or four STM-1s) structured into TU12s. These 252
SNCP instances can be a mixture of AU-4, TU3 and TU12 in any
combination, and taken from any CBKLM (addressing schema for data
container) address within an STM-1/4/16. A larger number of instances
than 252 may be used, but in this case we cannot guarantee switching
times below 50 ms.
126 1553-CXP 901 4102/10 Uen F 2009-09-25

SDH
The resolution of the Hold-off timer is N x 100ms +/- 60 ms. For a 500 ms
Hold-off timer, the real timer value may be any value between 440 ms and
560 ms.
The Working, Protection and Protected parts of an SNCP protected path can be
carried over different link rates. For example, for an SNCP protected TU12, the
Working TU12 could be carried over an STM-16 link, while the Protection TU12
could be carried over an STM-4 link.
9.2.3.1 Protect Connection by SNCP
SNCP Uni-directional Cross-connection Limitations:
Note: When one direction of a path forms part of an SNCP unidirectional

cross-connection, the other direction cannot form part of a different
SNCP unidirectional cross connection. But the two directions can form
part of two different unidirectional unprotected cross connections. This
applies to unidirectional cross-connections on all path layers.
Suppose the unidirectional VC-12 cross-connection from 1/1/1.1.1.1.1

(input) to 1/2/1.1.1.1.1 (output) is SNCP protected by 1/3/1.1.1.1.1
(input). In this case, the output direction of 1/1/1.1.1.1.1 and
1/3/1.1.1.1.1, and the input direction of 1/2/1.1.1.1.1 are unused.
However, due to the above mentioned limitation, they cannot be
part of a new SNCP protected unidirectional cross connection. For
example from 1/2/1.1.1.1.1 (input) to 1/1/1.1.1.1.1 (output) protected
by 1/14/1.1.1.1.1. They may however form part of unprotected
unidirectional cross connections.
9.3 SDH Cross Connection Management

This section describes the tasks involved when managing cross connections
between termination points on the NE.
The section involves management of the complete life cycle of a cross

connection, including creation, presentation, modification, deletion and manual
operation of the SNCP switch.
A cross connection is defined by its termination points. Only termination

points with the same characteristic information can be cross-connected. The
characteristic information of a termination point defines the format of the signal
that can be transferred by this termination point. Format defines the capacity
of the signal, for example TU12 and VC-12 have the same characteristic
information since they both have a 2Mbit/s traffic capacity.
The first part of this section gives a short introduction to SDH layers and
cross connections which is meant to help the reader in understanding the
requirements specified in this document. For further reading on SDH and cross
connections, please see ITU-T Recommendations G-Series.
1553-CXP 901 4102/10 Uen F 2009-09-25 127

9.3.1 SDH Layer Network and Cross Connections
An SDH network has a layered structure as depicted in Figure 106 on page

128. The layers operate in a client/server based scenario. The service layer
generates the bit streams that are to be carried across the SDH network. This
layer is not part of SDH. The path layer is a virtual layer and can only be
observed through a management system. It is in this layer the cross connection
management and structuring of the SDH ports are performed. The path layer
works on containers.
Figure 106 SDH Layer Network
9.3.2 SDH Port Structuring

The multiplexing structure of the SDH ports determines which layers and their
termination points are available to be cross connected. The multiplexing
structure for SDH in all layers is shown in Figure 107 on page 129 (taken
from ITU-T Recommendation G.707.) The CBKLM value determines the path
through the structure. The usage of the CBKLM value follows the rules defined
in Table 30 on page 129.
Only traffic on non-terminated containers called connection termination points

can be cross connected, such as AU-4, TU3, and TU12. The other containers,
VC-4, VC-3, and VC-12, represent trail termination points where the traffic
can be read.
128 1553-CXP 901 4102/10 Uen F 2009-09-25

SDH
Figure 107 SDH Multiplexing Structure
9.3.3 CBKLM Value Usage

Table 30 CBKLM Value Usage
Rule Example
When referring to SDH objects the complete CBKLM
value is used even if some fields are insignificant
AU-4 in STM-16: C.B.0.0.0
Not significant fields in CBKLM are set to 0
TU3 in STM-16: C.B.K.0.0
STM-1: C = 1, B = 1
There is one AUG-1 in STM-1 and a phantom
AUG4
STM-4: C = 1, B = 1 - 4
There is one AUG4 in STM-4
C identifies which AUG-4. If no AUG4 exists, its is set STM-16: C = 1 - 4, B = 1 - 4
to 1, like a phantom AUG4
Example:
B identifies which AUG-1. If no AUG-1 exists, its is set AU-4 in STM-1: 1.1.0.0.0
to 1, like a phantom AUG-1 TU3 in STM-4: 1.3.3.0.0
TU12 in STM-16: 2.4.2.7.2
VC-12 on E1 module: 1.1.1.1.1

Protecting: 1.1.1.1.2
The CBKLM value is used for VC objects associated VC-3 on E3 module: 1.1.1.0.0
with E1, E3, and E4 modules but the C and B values Protecting: 1.1.2.0.0
are always 0
VC-4 on E4 module: 1.1.0.0.0 (not Release
1)
Protecting: 1.2.0.0.0
1553-CXP 901 4102/10 Uen F 2009-09-25 129

Rule Example
VC-12 on E1 module: 1.1.x.y.z
VC-3 on E3 module: x.y.z.0.0 (not Release
For VC objects for WAN 1)
VC-4 on E4 module: x.y.0.0.0 (not Release
1)
Combination 0.0.0.0.0 is not a legal value and can
be used as an error code
130 1553-CXP 901 4102/10 Uen F 2009-09-25

PDH
10 PDH
This chapter describes the basic management of the PDH ports. For further
information, please refer to the Technical Product Description.
10.1 Configure a Slot as PDH

PDH modules can only be configured in Slot 3 and 4. As a result of the
provisioning, Slot 7 and 8 will be auto-provisioned with the expansion modules.
PDH modules can be in Slot 5 and 6 as well, but only as standby in an
equipment protection setup.
There are two PDH port types:
• E1: (2 Mbit/s) supporting transparent data and NT functionality of ISDN

PRA. E1 ports are available when the slot is configured for the 63 x E1
module
• E3: (34/45 Mbit/s) supporting transparent data. E3 ports are available

when the slot is configured for the 6 x E3 module
1. Select Shelf in the Management Tree to see the available slots.
2. Click the slot you want to configure, and the Slot screen opens in the
viewer. See Figure 108 on page 131.
3. The Expected Mode menu lists the supported modes for the slot. Select
the mode and save.
Figure 108 Set Expected Mode
Depending on the slot mode configuration, the port forms will be different for
the E1 and E3 modes.
1553-CXP 901 4102/10 Uen F 2009-09-25 131

10.1.1 PDH E1 Port Screen
In the PDH screen for E1 Mode, you can view status and modify the slot, see
the figure and description below.
Figure 109 PDH Port Screen in E1 Mode
The following parameters can be set:
Table 31 PDH Port E1 Parameters

• Out of Service
E1 Mode • tra • Transparent Leased Line
• pra • ISDN primary rate access
• pra fixed • ISDN primary rate access with
fixed pointer
• fra
• Framed Leased Line
• fra fixed
• Framed Leased Line with fixed
pointer
FRA Settings • All Ones Sa-bits - Term This is only available if the E1
CRC-4/E-bits mode is either fra or fra fixed
• Transp Sa-bits - Term
CRC-4/E-bits
• Transp Sa-bits - Transp
CRC-4/E-bits
Transport Mode • PDH over SDH
• PDH over CES
• SDH over CES
AIS Alarms • Enabled (ticked)
• Disabled
132 1553-CXP 901 4102/10 Uen F 2009-09-25

PDH

Maintenance - Administrative • No loop Only available when the
Loop Mode Administrative Status above is set
• LL2 (to network) to Out of Service - Maintenance
• LL3 (to customer) See Section 10.1.4 Administrative
Loop Mode on page 134
Synchronization • Free Read only
• Used Used indicates that the port is
used as a sync source
10.1.2 PDH E3 Port Screen

In the PDH screen for E3 Mode, you can view the status and modify the slot,
see the figure and description below.
Figure 110 PDH Port Form in E3 Mode
The following parameters can be set:
Table 32 PDH Port E1 Parameters

• Out of Service
E3 Mode • e3
• t3
Maintenance - Administrative • No loop Only available when the
Loop Mode Administrative Status above is set
• LL2 (to network) to Out of Service - Maintenance
• LL3 (to customer) See Section 10.1.4 Administrative
Loop Mode on page 134
1553-CXP 901 4102/10 Uen F 2009-09-25 133

10.1.3 Enable the PDH Port to Carry Traffic and Report Alarms
By default, the Administrative Status of the PDH port is set to Disabled when
the port is created. No traffic will pass through the port and no alarms are
reported before it is Enabled.
1. Select a PDH port.
2. In the browser, set Administrative Status to In Service.
3. Save.
Note: When Disabled, the PDH port generates AIS upstream and
downstream.
10.1.4 Administrative Loop Mode

When the Administrative Status for a PDH port is set to Out Of Service -
Maintenance, you can set the Administrative Loop Mode to:
• LL2 (loop back to network)
• LL3 (loop back to customer)
Note: There are restrictions for setting the loops of PDH Ports:
• The LCT cannot set and release loops when the E1Mode is set
to pra. (In this mode, loops can only be managed from an NT1
or similar)
• A loop cannot be set when PDH Port Admin Status is set to

Disabled.
Figure 111 Administrative Loop Mode
134 1553-CXP 901 4102/10 Uen F 2009-09-25

PDH
10.1.4.1 LL2 (to Network)
The PDH Terminal loopback (LL2) is performed in the Virtual Container

Terminal (VCT) circuits, the loop has the following characteristics:
• The entire PDH E1 or E3 signal is looped back towards the NE itself
• AIS is transmitted towards the line at nominal rate
10.1.4.2 LL3 (to Customer)
The PDH line loopback (facility loopback, LL3) is performed in the VCT circuits,
the loop has the following characteristics:
• The entire PDH E1 or E3 signal is looped back
• The loopback is performed after the clock extraction
• AIS is inserted towards the NE itself
10.1.5 Set and Read Path Trace Identifiers

1. Expand a PDH port.
2. Click on the e1 or e3 item.
3. Click on the VC12 (E1) or VC3 (E3) item.
4. Click on the Path Trace link to open the Path Trace screen:
Set the parameters as described in Table 33 on page 135:
5. Save.
Table 33 Path Trace Parameters

Path Trace • Enabled Set to Enabled if TIM alarms should be reported when there
is a mismatch between Path Trace Received and Path Trace
• Disabled Expected
Path Trace • H Enter a value for the Path Trace Identifier that you want to
Transmitted transmit to the other side of the path
• C
1553-CXP 901 4102/10 Uen F 2009-09-25 135


Path Trace Expected • H Enter a value for the Path Trace Identifier that you expect to
receive from the other side of the path
• C
Path Trace Received Read-only The actual received Path Trace Identifier from the other side
of the link
Note: When Path Trace is set to Enabled, AIS is inserted downstream instead
of the original signal when there is a mismatch between expected and
received Path Trace.
10.1.6 Monitor PDH Port Performance
1. Expand a PDH port.
2. Select the e1 or e3 item.
3. Click on the VC12 (for e1 ports) or VC3 (for e3 ports).
4. Click the PM VCn Current Near End or PM VCn Current Far End links to
read PM data. The following attributes are available:
• Current 15-minute BBE, ES, SES and UAS
• Current 24-hour BBE, ES, SES and UAS
5. To see the performance history of the previous 16 x 15-minute counters,

click on Interval 15-min. Click on Interval 24-hour to see the previous
24-hour counter history.
6. The following attributes are available:
• Interval 15-minute BBE, ES, SES and UAS
• Interval 24-hour ES, SES, BBE and UAS
Figure 112 PM Data Example
136 1553-CXP 901 4102/10 Uen F 2009-09-25

PDH
10.1.7 Monitor the PDH E1 Port Performance
The E1 counters are based on CRC-4 counters for near end and E-bit counters
for far end monitoring. Defect criteria for near end is LOS-TX(Loss Of Signal),
LOF-TX(Loss Of Frame) and module/slot alarms. For far end there are no
alarms present to indicate any defects.
The valid flag for previous intervals and past 24-hours is set only when the
port has been in PRA-mode during the whole period. For ports in TRA-mode,
the PM counters can only be used to indicate SES/UAS due to LOS-TX or
module/slot alarms.
1. Select a PDH E1 port.
2. When the PDH port is expanded, select the E1 object.
3. Click on the PM E1 Current Near End link to read near end PM data or the
PM E1 Current Near End link to read far end PM data.
4. To see the performance history of the counters, click the Interval 24-hour
or the Interval 15-min link.
5. The following attributes are available:
• Interval 24-Hour ES, SES, BBE and UAS
• Interval 15-minute BBE, ES, SES and UAS
1553-CXP 901 4102/10 Uen F 2009-09-25 137

138 1553-CXP 901 4102/10 Uen F 2009-09-25

Cross Connections
11 Cross Connections
11.1 Cross Connection Management

Cross connection management is the management of connectivity within the
NE itself. Cross connections (XC) are set up between connection termination
points with the same characteristic information, for example, cross connections
between AU-4s, or between TU3s, between VC-12 and TU12, or between
two VC-12s.
There is a very large number of choices. In addition there are several different
types of cross connection:
• Point-to-point
• WAN XCs (special type of point-to-point)
These types can be with or without protection and unidirectional or bidirectional,

see the following figures.
Figure 113 Unidirectional XC - Unprotected
Unprotected, unidirectional cross connections can be used for test loops, as

illustrated by A1 in Figure 113 on page 139.
In Figure 114 on page 140, protection has been set up for the termination point
A1 and B2. The protected termination point A1 has no switching possibility since
the cross connection is unidirectional, but termination point B2 has switching.
1553-CXP 901 4102/10 Uen F 2009-09-25 139

Figure 114 Unidirectional XC - Protected
The bidirectional, unprotected cross connection is depicted in Figure 115

on page 140. For bidirectional cross connections, all termination points
have switching possibilities when protected. In Figure 116 on page 140, the
termination points A1 and B2 are protected, A1 can choose to receive from
either B1 or the protection and B2 can switch between A2 or the protection.
Figure 115 Bidirectional XC - Unprotected
Figure 116 Bidirectional - Protected
Figure 117 Example of Bidirectional Unprotected Point-To-Point XC
140 1553-CXP 901 4102/10 Uen F 2009-09-25

Cross Connections
Figure 118 Example of Bidirectional Protected Point-To-Point XC
11.2 Modify Cross Connections

A cross-connection is a relationship between termination points and the
relationship cannot be modified after it has been created.
It is not possible to modify the direction (bidirectional or unidirectional) of a

cross connection. The only parameter that can be modified is the description of
the cross connection.
Cross-connections can be protected after they have been created. See Section
11.3 Protect Point-To-Point Cross Connections on page 141.
11.3 Protect Point-To-Point Cross Connections

The A-end or B-end of a cross-connection can be protected by the SNCP
scheme when a cross connection is being set up or after the cross connection
has been set up.
Note: When the cross-connection is unidirectional and protected TP is a, a

static bridge will be created from the A-end to the B and Protection
termination points. (SNCP parameters are not used).
When the cross-connection is unidirectional and protected TP
is b, an SNCP switch is created where the signal from A is the
working connection and the signal from Protection is the protection
connection. In this case the SNCP parameters are available after the
cross-connection has been saved.
1. Open the Cross Connection Manager from the Equipment menu.
2. Set the Protected TP attribute to a or b for one or more cross connections.

This is the termination point you want to protect.
3. Select the Available TP List in the Content panel. The list contains the free
TU12/VC12 or TU3/VC3 or AU-4 termination points.
1553-CXP 901 4102/10 Uen F 2009-09-25 141

Note: If the Available TP List in the Content panel does not show the
termination points that you want to protect your WAN channel
with, you have to make sure they are made available for cross
connection.
You can protect bidirectional or unidirectional cross connections. In
the Available TP List you will see whether the termination point is
available in both directions or as A-end or B-end.
4. Select the termination point that you want to protect your A- or B-end with.
5. Click on the Set Prot button in the toolbar. The protection TP is filled in
for the selected cross-connection.
6. Save.
Note: By default, the protection is disabled and will not work before it is
enabled. Follow the instructions below to enable SNCP.
11.3.1 SNCP
1. Select the cross connections where you want to enable protection. (SHIFT
and CTRL buttons can be used for multiple selection).
2. Click the SNCP button in the toolbar.
3. Set the Enabled attribute to Enabled and click OK.
Figure 119 SNCP
Note: It is not possible to modify the Protection termination point after it has
been saved. If you want to modify it, the ProtectedTP must first be
saved as none. Then the Protection TP can be modified. Remember to
set the Protected TP back to a or b.
142 1553-CXP 901 4102/10 Uen F 2009-09-25

Cross Connections
11.3.1.1 Modify Protection Parameters of a Cross Connection
The A-end and B-end of cross connections are protected as described in

Section 11.3 Protect Point-To-Point Cross Connections on page 141. The
SNCP is then set up with a number of default parameters. The parameters can
easily be modified as follows:
2. Select a cross connection in the Cross Connection Manager.
3. Select the cross connections where you want to modify the protection
parameters (SHIFT and CTRL buttons can be used for multiple selection).
5. Modify the SNCP parameters and click OK.
6. Save.
11.3.2 Command Cross Connection Protection Switch

You can control the SNCP switching by sending a command.
2. Select the cross-connections where you want to modify protection

parameters (SHIFT and CTRL buttons can be used for multiple selection).
4. Select the required SncpCommand and click OK.
Depending on the priority of the command and current status of each channel,
a switch may now take place for some or all selected cross-connections.
1553-CXP 901 4102/10 Uen F 2009-09-25 143

11.3.3 Delete Cross Connections
1. Select the Cross connection Manager from the Equipment menu.
2. Select the panel for the type of cross-connection(s) you want to delete
(VC/TU12, VC/TU3 or VC/AU-4).
3. Select the cross-connections that you want to delete.
4. Click Delete on the toolbar.
5. Save.
11.3.4 Advanced Cross Connection Operations

For frequent users of the LCT, it is possible to make use of the enhanced
editing facilities to speed up the configuration work.
11.3.4.1 Set up Multiple Cross-Connections by Multiple Selection
1. Select the Termination points (TPs) that you want to use as A-ends. Use
the SHIFT or CTRL buttons to select more than one termination point.
2. Click Add on the toolbar. The same number of cross-connections as the

selected TPs are created with the A-end filled in.
3. Select the TU12 termination points that you want to add to the B-ends of
the cross-connections in the same way.
4. Click the Set B button on the toolbar.
5. If you want to protect the connections, select the TU12 termination points
that you want to add to the cross connections.
6. Click the Set Prot button on the toolbar. Remember to set Protected TP
to a or b.
7. Save.
Note: You are only allowed to set the B or Protection termination points of
cross connections where B or P are not in use. If you want to modify
the A or B termination point, the cross connection must be deleted and
created again. If you want to modify the Protection termination point,
the Protected TP must first be saved as none. Then the Protection TP
can be modified. Remember to set the Protected TP back to a.
If you do not select the same number of instances of cross connections
and termination points, the A or B end will be filled in with as many TPs
as available, starting from the top of the selected cross-connection
list. If more TPs are selected than cross connections, the last TPs
will not be used.
144 1553-CXP 901 4102/10 Uen F 2009-09-25

Cross Connections
11.3.4.2 Set up Multiple Cross Connections by Repeated Operations
1. Double click the termination point you want to use as the A-end. A new
cross-connection is created.
2. Double click the termination point you want to use as B-end. The B-end is
filled in.
3. Repeat 1 and 2 for as many cross-connections as you want.
4. Save.
11.3.4.3 Enter Termination Points Manually
1. Add a new cross-connection.
2. Click on the A, B or Protection termination points. A list of slots appears.
3. Select a slot. A list of ports appears.
4. Select a port.
5. Continue selecting each of the CBKLM values.
6. Enter the information the same way (or select from a list of free TPs) for
the other termination points.
7. Save.
Note: The information can also be entered directly without selecting the
numbers from the drop down list. Remember to use the following
format: slot/port/CBKLM.
1553-CXP 901 4102/10 Uen F 2009-09-25 145

146 1553-CXP 901 4102/10 Uen F 2009-09-25

Removal of Provisioning from Entities
12 Removal of Provisioning from Entities
If you wish to remove the provisioning of entities from the OMS 1400, you have
to perform certain required activities in sequence - for example you cannot
remove the provisioning for a slot until you have first removed the provisioning
of all XFP/SFP interface modules on the ports for that slot.
12.1 Removal of Provisioning from Slots

• Remove provisioning from all ports (investigate SM/SC/EM dependencies)
• Remove provisioning from all XFP/SFP interface modules on the ports
• Remove module protection
12.2 Removal of Provisioning from LAN Ports

• Delete EVC on the specific UNI and delete the UNI from ports
• Remove any Provide Bridge VID entries from the port
• Disable LLF for L1 ports
• Remove the port from all VLANs
• Remove the port from any L1 VLAN-muxes
• Remove the port from all LAG groups
• Disable Link OAM
• Remove L1/L2 capability
12.3 Removal of Provisioning from WAN Ports

• Remove SDH cross connections to the WAN port
• Set the bandwidth to zero
• Set the VC-concatenation to none
• Remove L1 CC channels
• Remove the UNI from EVC and delete the UNI from ports
• Remove any Provide Bridge VID entries from the port
1553-CXP 901 4102/10 Uen F 2009-09-25 147

• Remove the port from all VLANs
• Remove the port from any L1 VLAN-muxes
• Disable Link OAM
• Remove L1/L2 capability
12.4 Removal of Provisioning from PDH Ports

• Remove the port from the SYNC sources table
• Remove all cross connections from this port
12.5 Removal of Provisioning from SDH Ports

• Remove the port from the SYNC source table
• Remove all DCN DCC interfaces
• Remove all cross connections from the port
• Remove MSP protection
• Unset the SDH speed
148 1553-CXP 901 4102/10 Uen F 2009-09-25

LCT and LCTS Operator's Reference

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

LCT and LCTS Operator's Reference

Caricato da

Copyright:

Formati disponibili

LCT and LCTS Operator’s Reference

Marconi OMS 1410 Release 1.0 Revision B

© Copyright Ericsson AB 2009. All rights reserved.

All trademarks and registered trademarks mentioned in a document of this

Ericsson Telefonaktiebolaget LM Ericsson

1553-CXP 901 4102/10 Uen F 2009-09-25

1 Getting Started with the OMS 1410 Local Craft Terminal 1

2 Use the Marconi OMS 1410 LCT 11

4 The Commissioning Wizard 45

5 Data Communication Network (DCN) 59

1553-CXP 901 4102/10 Uen F 2009-09-25

6.1 Ethernet Port Attributes 67

8 Ethernet Services Wizard 95

11 Cross Connections 139

12 Removal of Provisioning from Entities 147

1553-CXP 901 4102/10 Uen F 2009-09-25

1 Getting Started with the OMS 1410 Local

1.2.1 Install Marconi OMS 1410 LCT

2. Run OMS 1410 Craft.exe to launch the install shield.

3. Follow the instructions given in the Install Wizard.

1.2.2 Un-install Marconi OMS 1410 LCT

1.3 Use Marconi OMS 1410 LCT

1553-CXP 901 4102/10 Uen F 2009-09-25 1

1.3.1 Start the Program

1.3.1.1 Start the Program on Windows

1. Select Programs from the Start menu.

2. Locate and select the Marconi OMS 1410 LCT program.

Figure 1 Marconi OMS 1410 LCT Program Menu on Windows

1.3.1.2 SNMP Trap Distributor

Figure 2 SNMP Trap Distributor

1.3.2.1 Logon Screen

Figure 3 Logon Window

2 1553-CXP 901 4102/10 Uen F 2009-09-25

• IP: The address of the NE

• User: Default = admin

• Password: Default = admin

1.3.2.1.1 Failed Logon

1.3.2.2 Logon with the LCT Port

• PC with Marconi OMS 1410 LCT installed

1.3.3 Log Off

• Select Exit from the File menu or press Alt and F4

1.4 User Management

1.4.1 Open NE User Management

1553-CXP 901 4102/10 Uen F 2009-09-25 3

Figure 4 User Management

1.4.2.1 Default User

• Log on using the default user account

• Create a new system administrator user

• Log on using the new system administrator user

• Delete the default user

4 1553-CXP 901 4102/10 Uen F 2009-09-25

Table 1 User Categories

1.4.2.2 Add a User

Only users with administrator rights can edit other users.

2. Enter the user name, 6-34 characters.

5. Decide the user’s role (see Table 1 on page 5).

1.4.2.3 Edit a User

Administrators can edit the settings for other users.

• To change the user’s password, click the Change Password button

1553-CXP 901 4102/10 Uen F 2009-09-25 5

0 Enter the new password (6-34 characters)

0 Retype the new password

• To change the user’s account expire date, or the user’s password