Академический Документы
Профессиональный Документы
Культура Документы
OPERATING INSTRUCTIONS
Copyright
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.
Trademark List
Contents
3 NE Maintenance 31
3.1 Operation 31
3.2 Licence Handling 41
3.3 Inventory 43
6 Ethernet Screens 67
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
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
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
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.
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.
When you launch the Marconi OMS 1410 LCT, a trap distributor application
automatically starts in the background.
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
The system validates the logon input and opens the Marconi OMS 1410 LCT
Desktop.
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.
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)
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.)
• Right click the Trap Distributor icon in the system tray and select Shutdown
1.4.2 Users
This window presents the registered users for the NE. You can add, edit and
delete users here.
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 off
Only the system administrator has privileges to change the password and trap
settings for other users.
1. Click the Add icon on the tool bar, and the Create New User window
appears:
3. Enter the password, 6-34 characters and retype it to confirm the accuracy.
4. Press OK.
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. Select the user you want to edit from the users list.
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
2. Save.
From the desktop menu, select: Equipment > Change Current User Password.
If you forget or lose your password, a user with administrator rights must open
your user profile and give you a new password.
The severity of an alarm notification can either be reported from the NE or must
be defined in the 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.
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.
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.
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:
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.
If you are familiar with the windows folder structure, the navigation in the
Management tree is simple and intuitive. Here is an overview:
Select an item:
• Double click
If you right click an item, a selection menu appears with navigation options and
shortcuts to actual functions for the item.
Note: Using the Open in New Window function you can compare attribute
values on different items.
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.
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.
• Click the link directly to view attributes in the same browser window
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.
• 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.
You can select notification records, filter notification selections, and rearrange
and sort alarm columns in the Notification List.
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:
Warning
Information
Unmapped severity
Note: Logs can be saved to file, opened in, and deleted from the Log Viewer.
Clear removes all messages from the Log Viewer.
A Tooltip shows the entire value, if it does not fit inside the cell:
Note: The maximum number of current alarms is 5000. Trace lists have a
maximum of 1000 notifications.
2.3.2 Notifications
To remove a non-clearable alarm, right click on the alarm and select Remove.
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.
The lists contains notification records with a set of information. Alarm attributes
are listed in alphabetical order.
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
Source Identification of the NE that contains the Every item available in the Management
source of the alarm Tree
The lists contains notification records with a set of information. Attribute names
are listed in alphabetical order.
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.
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.
To view events reported from the NE, select the desired trace tab in the
Notification List.
For details on the notification attributes, see Section 2.3.2.5 Event Notification
on page 18.
One alarm in the Current Alarm list may represent multiple alarms (items) in the
Alarm Trace list.
The list is cleared and will be empty until new items are received.
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.
Note:
1. AND: All of the criteria must be fulfilled or the filter will not return any items
2. OR: If you do not choose any expression when adding criteria, the LCT will
automatically use OR
0 Press AND
6. Click OK.
• Select the required filter from the Filter drop-down box in the Notification List
2. Select the required filter from the Filter name drop-down box.
5. Click OK.
The selected filter has a new name. No changes have been made to the filter
setup.
2. Select the required filter from the Filter name drop-down box.
5. Click OK.
Note: The selected filter has a new content. Be aware of the filter name as
this might now be misleading.
2. Select the required filter from the Filter name drop-down box.
3. Click Delete.
4. Click OK.
The filter is removed from the Filter drop-down list in Notification List.
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.
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.
1. Select the history log (alarm, event or protection switch) you wish to save.
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. 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.
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.2 Edit
2.3.4.3 View
2.3.4.4 Equipment
Cross Connection See Section 9.3 SDH Cross Connection Management on page 127
manager
2.3.4.5 Tools
2.3.4.6 Help
Save
Save
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.
By default, entire rows are selected in a table, but single cells can easily be
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.
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
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.
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.
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.
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.
2. Drag and drop the column to its new position. The columns switch places
in the view.
1. Rest the mouse pointer to the right of desired column header. The mouse
pointer turns into a double-arrow.
3 NE Maintenance
3.1 Operation
Select NE Maintenance from the Equipment menu to open the NE Maintenance
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.
Select Device from the Management Tree and then Network Element >
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
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.
Select SSH Server from the Information grouping in the Management Tree.
In the Internal mode, the NE will use SSH to access the workstation to get
the file.
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.
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.
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).
A confirmation dialog box appears according to the command you have chosen,
before the session start. Only the relevant options are available.
You may change the restart option and switch bank setting.
You can turn off this function from the View menu:
3. Browse and select the file from the software folder and press Open.
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.
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.
To save management DCN bandwidth, only files that have changed between
currently running and targeted downloaded network release are downloaded by
the NE.
The LCT reads def-file properties and calculates download volume before
downloading the network release to the NE.
1. Select Device from the Management Tree and then Network Element >
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.
4.
5. Select Download Start time and Activation Start time. Please note slots
that are subject to traffic interruption.
8. At this stage you can safely close the wizard and watch the progress in
the NE Maintenance screen.
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. 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).
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.
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.
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.
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.
Caution!
Perform Backup CDB before the following procedure. See Section 3.1.7.1
Backup Configuration on page 39.
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.
The Node Licences view opens and shows the licence features on the NE
and links to related tasks, see figure below.
• 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
View information and status of licence key files currently installed on this NE.
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
Select the Licence Key file and press the Install LKF button. You will now get
feedback in the notification list.
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.
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.
Figure 37 Inventory
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.
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.
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.
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.
• No Change
0 This synchronizes the NE’s clock to match the clock on the computer
where the Commissioning Wizard is running
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.
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.
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.
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.
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.
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.
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.
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.
4.11 Finish
Figure 51 Summary
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.
The Restart and Shutdown buttons can be used in case of failure on a module.
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:
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.
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.
The Out-of-Band Management Interfaces are the DCC, management ports and
IP over OSI tunnels.
The Management Ports form contains settings for the management mode, IP
address and the subnet mask for the management port.
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
Note: When you change the management mode in the pull down menu, the
change takes effect at once.
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.
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.
• Not Used
• IP
• OSI
5.2.1.2.1 IP
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:
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.
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.
• R to R or M to M only
Figure 62 Transparency
5.2.4.1 IP Routing
6 Ethernet Screens
This chapter describes the screens for the Ethernet ports. Several attributes
are common, and are described below.
Table 16
Parameter Values Note
Administrative Status • In service
• Out of service
• Out of service - maintenance
• Out of service - auto in service
Priority • 802.1p
• Disabled
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.
The LAG screen allows you to create and maintain the LAG details.
The attributes presented in the LAG Port screen are not editable in the Port
screen of the respective members of the LAG.
When a port is configured as a UNI, the UNI setting are available under
Ethernet Services in the Management Tree, as shown below.
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.
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.
This screen shows detection and reporting for received alarm events.
The Link OAM Port Statistics screen is available from the Link OAM screen.
Here, you can adjust priority setting for the provider bridge.
• Queue Management
Note: These profiles have default profiles pre-defined that you cannot edit.
From the CoS screen, select the link to the type of profile you want to manage.
The procedure is similar for all types.
• 8 x Strict Priority
For Traffic Scheduling Management, you can edit the WFQ weight parameter
only (and only if you have chosen one of the WFQ profiles).
2. Set the Concatenation to one of the VCAT values. This ungrays the LCAS
icon.
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.
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.
7 Layer 2 Configuration
7.1 Introduction
This chapter guides you through management of the bridging service (L2
forwarding) on the NE.
This includes:
7.2 Bridge
This section describes the configuration operations supported by the bridge. It
is organized in two sections:
7.2.1 Examples
3. Click the Create New Static Forwarding Entries button to open the Static
Unicast Forwarding screen.
• 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.
• VLAN ID: Set the VLAN ID for which this entry applies
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.
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.
5. Save your change and then select the IGMP Snooping link.
7. Save.
7.3 Miscellaneous
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:
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.
To configure RSTP:
4. Save.
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.
Figure 82 MSTP
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
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.
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.
MAC Multicast Enable allows you to enable/disable the MAC Multicast control
tables.
• 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
• VLAN ID: Identifies the VLAN to which the filtering information applies
• 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
• VLAN ID: Identifies the VLAN to which the filtering information applies
The section also involves management of the complete life cycle of a VLAN,
including:
The NE supports:
There are three steps involved in the definition of a VLAN on the NE.
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.
The following examples show how a VLAN can be created and provisioned
with the VLAN Settings screen.
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.
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.
6. Save.
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.
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.
The task selection page allows you to choose between UNI Definitions or
Ethernet Service provisioning.
Configure UNIs on the NE. All LAN and WAN ports on the NE can be configured
as UNIs.
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.
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.
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.
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
Attributes Description
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
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
• Tunnel (only available for L2 CNP Port UNIs) - the L2CP frames are
tunnelled through the Provider network using the L2CP tunnelling mode
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
Note: To clear the entered values from the wizard, you have to close it and
restart it to start a new UNI creation flow.
• 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
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.
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
The Bandwidth Profile Target defines the flow to which the ingress bandwidth
profile is applied.
• 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
• 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 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.
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.
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.
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.
8.4.5 Summary
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.
Select the UNIs folder under Ethernet Service in the Management Tree to
display attributes for currently defined UNIs.
For details on UNI settings see Section 8.3 Create a UNI on page 97.
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.
2. Select the Services folder in the Management Tree. The system presents a
list of all configured Ethernet Services on the NE.
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.
• Committed Information Rate (CIR) expressed as bits per second. CIR >=0
• 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.
EBS -
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.
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.
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
The red frames are the frames that violate both the CIR/CBS and EIR/EBS
parameters and are dropped.
• 24-hour
The NE holds current data and historical data, the number of historical time
periods are
• 1 x 24-hours
In the Ingress PM Overview screen you can view details and clear the counters
of various ingress UNIs or services.
8.5.6 Definitions
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
User Network Interface The physical demarcation point between the responsibility of the
Service Provider and the responsibility of the Subscriber
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.
9 SDH
This chapter describes the basic configuration of the SDH ports. For more
information, please see the Technical Product Description.
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.
The following screens appear in sequence in the wizard and allow you to view
the existing structure and make the required changes.
• 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.
• 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
• PathTrace:
• 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
• PathTraceReceived:
0 The actual received Path Trace Identifier from the other side of
the link
6. Save.
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.
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.
• 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
3. Select the AU-4 and then the VC4 items as the port expands.
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.
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.
3. Save.
The section involves management of the complete life cycle of a MSP, including
creation, presentation, modification, deletion and manual operation the MSP
switch.
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
the network but uses a little more time to perform the switching than does a
unidirectional switching protocol.
• Revertive: traffic returns to the working trail when the working trail recovers
The time to wait before traffic reverts to a recovered working trail can be defined.
5. Save.
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).
1. In the Management Tree, expand the SDH port that is the working port.
4. Save.
1. In the Management Tree, right click the SDH port that is the working port.
3. Save.
1. In the Management Tree, expand the SDH port that is the working 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.
• 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.
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.
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.
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.
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
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
10 PDH
This chapter describes the basic management of the PDH ports. For further
information, please refer to the Technical Product Description.
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.
Depending on the slot mode configuration, the port forms will be different for
the E1 and E3 modes.
In the PDH screen for E1 Mode, you can view status and modify the slot, see
the figure and description below.
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.
3. Save.
Note: When Disabled, the PDH port generates AIS upstream and
downstream.
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)
The PDH line loopback (facility loopback, LL3) is performed in the VCT circuits,
the loop has the following characteristics:
4. Click on the Path Trace link to open the Path Trace screen:
5. 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.
4. Click the PM VCn Current Near End or PM VCn Current Far End links to
read PM data. The following attributes are available:
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.
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.
11 Cross Connections
There is a very large number of choices. In addition there are several different
types of cross connection:
• Point-to-point
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.
Cross-connections can be protected after they have been created. See Section
11.3 Protect Point-To-Point Cross Connections on page 141.
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.
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).
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.
3. Select the cross connections where you want to modify the protection
parameters (SHIFT and CTRL buttons can be used for multiple selection).
6. Save.
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.
2. Select the panel for the type of cross-connection(s) you want to delete
(VC/TU12, VC/TU3 or VC/AU-4).
5. Save.
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.
3. Select the TU12 termination points that you want to add to the B-ends of
the cross-connections in the same way.
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.
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.
4. Save.
4. Select a port.
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.
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.
• Remove L1 CC channels
• Remove the UNI from EVC and delete the UNI from ports