Lucent Optical Management System (OMS) Release - Alcatel

See notice on first age
Lucent Optical Management System (OMS)
Release 5.0.1
Provisioning Guide for LambdaUnite ® MSS, Release 8.0.2
365-312-876R8.0.2
CC109643890
Issue 2
July 2008
Alcatel-Lucent - Proprietary
This document contains proprietary information of Alcatel-Lucent and
is not to be disclosed or used except in accordance with applicable agreements.
Copyright © 2008 Alcatel-Lucent
Unpublished and Not for Publication
All Rights Reserved
See notice on first age
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their
respective owners.
The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright © 2008 Alcatel-Lucent. All Rights Reserved.
Alcatel-Lucent - Proprietary
See notice on first page
Contents
About this information product
Purpose
..........................................................................................................................................................................................
....................................................................................................................................................................
xiii
......................................................................................................................................................................
xiii
..........................................................................................................................................................................
xiv
Safety information
Conventions used
Orientation aids
Related information
...................................................................................................................................................................
...................................................................................................................................................................
xvii
Technical support
.....................................................................................................................................................................
xvii
.............................................................................................................................................................................
xvii
How to comment
.....................................................................................................................................................................
xvii
Safety
Overview
......................................................................................................................................................................................
Basic safety aspects
1-1
............................................................................................................................................
1-3
.................................................................................................................................................................
1-5
Structure of hazard statements
...................................................................................................................................
1-7
......................................................................................................................................................................................
2-1
Symbols used in hazard statements
2
xv
Document support
How to order
1
xiii
Security administration tasks
Overview
....................................................................................................
2-2
...............................................................................................................................
2-5
To retrieve the current user’s security information
To retrieve user security information
To modify the current user’s security information
.....................................................................................................
2-9
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
iii
Issue 2, July 2008
See notice on first page
Contents
To modify user security information
..............................................................................................................................
.........................................................................................................................
2-16
..................................................................................................................................................
2-18
...............................................................................................................................................................
2-20
.........................................................................................................................................................................
2-23
To modify the current user’s password
To terminate user sessions
To create new users
To delete users
3
Management communication setup concepts
Overview
......................................................................................................................................................................................
DCN configurations
3-2
.................................................................................................................................................................
3-5
DCN configuration guidelines
NSAP address structure
.............................................................................................................................................
3-9
..............................................................................................................................................
3-10
.......................................................................................................................................................
3-12
DCN protocols and services
...........................................................................................................................
3-14
...............................................................................................................................................................................
3-17
Data communication channels (DCC)
LAN access
3-1
.............................................................................................................................................................
Basic DCN principles
Name-to-address translation
...............................................................................................................................................
Orderwire and user bytes
3-18
..................................................................................................................................
3-19
....................................................................................................................................................
3-21
OMS-to-NE connections concepts
4
2-12
Management communication setup tasks
Overview
......................................................................................................................................................................................
4-1
Tasks related to OMS-to-NE connections
....................................................................................................................
4-3
....................................................................................................................................
4-4
To view a list of OMS-to-NE connections
To add an OMS-to-NE connection
To modify an OMS-to-NE connection
.............................................................................................................................
....................................................................................................................
4-13
.........................................................................................................................
4-15
.............................................................................................................................
4-17
To deactivate an OMS-to-NE connection
To activate an OMS-to-NE connection
To delete an OMS-to-NE connection
4-9
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
iv
Contents
To delete an NE
......................................................................................................................................................................
4-19
...........................................................................................................
4-21
To retrieve DCC related parameters
...............................................................................................................................
4-23
To modify DCC related parameters
................................................................................................................................
4-26
To display the communication state of an NE
Tasks related to DCC
To retrieve DCC/EOW status information for a port
..............................................................................................
4-28
To modify DCC/EOW status information for a port
...............................................................................................
4-30
.............................................................................................
4-32
...............................................................................................................
4-34
To view a list of transparent DCC cross-connections
To add a transparent DCC cross-connection
..........................................................................................................
4-36
.................................................................................................................................................
4-38
To delete a transparent DCC cross-connection
Tasks related to system provisioning
To view NE date and time
To modify NE date and time
5
.............................................................................................................................................
4-40
Equipment provisioning concepts
Overview
......................................................................................................................................................................................
5-1
System configurations
Network element configurations
.........................................................................................................................................
...............................................................................................................................
5-12
..........................................................................................................................................
5-19
Pluggable optical interface modules
Overview of replaceable units
........................................................................................................
5-26
...................................................................................................................................................................................
5-27
NE hardware components and their identifiers
Port types
5-2
Miscellaneous discrete inputs and outputs
...................................................................................................................
5-31
Equipment protection
...............................................................................................................
5-33
....................................................................................................................................................
5-38
CTL equipment protection (duplex control)
XC equipment protection
STM-1E equipment protection
........................................................................................................................................
5-41
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
v
Issue 2, July 2008
See notice on first page
Contents
DS3/EC-1 equipment protection
LOXC equipment protection
6
......................................................................................................................................
5-48
.............................................................................................................................................
5-56
Equipment provisioning tasks
Overview
......................................................................................................................................................................................
6-1
Provisioning of slots and SFP modules
To view a list of slots
.............................................................................................................................................................
6-3
Port provisioning
..........................................................................................................................................
6-4
.............................................................................................................................................
6-5
To view a list of physical ports
To view a list of logical ports
To view a list of loopback-enabled ports
.......................................................................................................................
To provision or deprovision a loopback on a port
.....................................................................................................
To modify the parameters of a physical or logical port
6-7
6-9
......................................................................................................................
6-11
............................................................................................................................................
6-26
..................................................................................................................................................
6-30
Parameters for SDH/SONET/PDH ports
Parameters for Ethernet ports
Parameters for VCG ports
...........................................................................................
6-6
Provisioning of NE event controls
To inhibit the forwarding of autonomous messages
................................................................................................
6-38
To allow the forwarding of autonomous messages
..................................................................................................
6-40
................................................................................................................................
6-42
..........................................................................................................................................
6-44
To switch on an MDO
........................................................................................................................................................
6-46
To switch off an MDO
.......................................................................................................................................................
6-48
Provisioning of MDIs and MDOs
To retrieve the MDO configuration
To set the MDO configuration
To retrieve the MDO state
..................................................................................................................................................
..................................................................................................................................
6-52
...........................................................................................................................................
6-54
To retrieve the MDI configuration
To set the MDI configuration
6-50
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
vi
Contents
Equipment protection
...............................................................................................
6-56
........................................................................................................................
6-59
To retrieve equipment protection group information
To add an equipment protection group
To operate an equipment protection group
................................................................................................................
6-61
To release an equipment protection group
...................................................................................................................
6-63
.....................................................................................................................
6-65
To delete an equipment protection group
7
Timing provisioning concepts
Overview
......................................................................................................................................................................................
......................................................................................................................
7-2
Timing interfaces
......................................................................................................................................................................
7-6
Timing references
.....................................................................................................................................................................
7-9
NE timing – general functional overview
Timing link switches
.............................................................................................................................................................
Timing quality
7-12
............................................................................................................................................
7-18
.........................................................................................................................................................................
7-20
The internal timing generator
Timing protection
...................................................................................................................................................................
Synchronization characteristics – external timing inputs
Synchronization characteristics – external timing outputs
Synchronization characteristics – system timing
7-21
......................................................................................
7-23
....................................................................................
7-25
.............................................................................
7-30
......................................................................................................
7-35
Synchronization characteristics – assigned timing references
8
7-1
Timing provisioning tasks
Overview
......................................................................................................................................................................................
To retrieve synchronization information
.........................................................................................................................
8-7
.....................................................................................................
8-9
................................................................................................
8-11
................................................................................................................
8-14
To set the synchronization - external timing output
To set the synchronization - system timing
8-2
............................................................................................
To set the synchronization - assigned timing reference
To set the synchronization - external timing input
8-1
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
vii
Issue 2, July 2008
See notice on first page
Contents
To release the synchronization switch (REF)
.............................................................................................................
To release the synchronization switch (MOD)
..........................................................................................................
8-18
To operate the synchronization switch (MOD)
..........................................................................................................
8-20
...................................................................................................
8-22
............................................................................................................
8-24
To release the synchronization switch (OUTREF)
To operate the synchronization switch (REF)
To operate the synchronization switch (OUTREF)
9
8-16
..................................................................................................
8-26
Traffic provisioning concepts
Overview
......................................................................................................................................................................................
9-1
SDH/SONET traffic provisioning concepts
Cross-connections
.....................................................................................................................................................................
Lower-order cross-connections (LOXC)
9-8
..........................................................................................................................................
9-11
...............................................................................................................................................
9-13
Path protection (SNCP/UPSR)
Line protection (MSP/APS)
.........................................................................................................................
9-2
Ring protection (MS-SPRing/BLSR)
.............................................................................................................................
9-15
............................................................................
9-20
.....................................................................................................
9-21
...........................................................................................................................................................
9-23
..............................................................................................................................................................................
9-25
Dual node interworking / Dual ring interworking (DNI/RNI)
Ethernet traffic provisioning concepts
TransLAN ® Ethernet over SDH implementation
Virtual concatenation
Virtual LAN
Tagging schemes
.....................................................................................................................................................................
.........................................................................................................................................................
9-28
...................................................................................................................................................................
9-30
Spanning tree protocol
Link path through
10
9-27
Traffic provisioning tasks
Overview
....................................................................................................................................................................................
10-1
Provisioning of cross-connections
To view all cross-connections
...........................................................................................................................................
10-4
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
viii
Contents
To view lower-order cross-connections
.........................................................................................................................
To view higher-order cross-connections
.....................................................................................................................
10-8
10-12
To add an uncorrelated lower-order cross-connection
..........................................................................................
10-16
To add an uncorrelated higher-order cross-connection
........................................................................................
10-19
To modify a lower-order cross-connection’s topology
.........................................................................................
10-22
To modify a higher-order cross-connection’s topology
.......................................................................................
10-26
.............................................................................................................
10-30
To modify a cross-connection’s parameters
To change a higher-order cross-connection from ONNS to traditional mode
............................................
10-33
To roll the input of a lower-order cross-connection from one tributary port to another
.......................
10-35
To roll the input of a higher-order cross-connection from one tributary port to another
......................
10-38
...........................................................................................................................................
10-41
To delete a cross-connection
.........................................................................................................
10-44
............................................................................................................
10-46
To retrieve ONNS to UPSR/SNCP constructs
To add an ONNS to UPSR/SNCP construct
To delete an ONNS to UPSR/SNCP construct
........................................................................................................
10-48
Provisioning of path protection groups (SNCP, UPSR)
....................................................................................
10-50
..............................................................................................
10-52
To view a list of path protection groups (SNCP, UPSR)
To modify a path protection group (SNCP, UPSR)
To operate a path protection group switch (SNCP, UPSR)
................................................................................
10-54
...........................................
10-56
..........................................................................................
10-58
To add a 1+1 MSP protection group
...........................................................................................................................
10-59
To add a 1x1 MSP protection group
...........................................................................................................................
10-61
To operate an SNCP VC-4 protection group switch on constituent members
Provisioning of MSP protection groups
To view a list of 1+1 or 1x1 MSP protection groups
.....................................................................................................
10-63
.......................................................................................................
10-65
.........................................................................................................................
10-67
To modify a 1+1 or 1x1 MSP protection group
To delete a 1+1 or 1x1 MSP protection group
To operate an MSP protection switch
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
ix
Issue 2, July 2008
See notice on first page
Contents
Provisioning of APS protection groups
...........................................................................................
10-69
To add a 1+1 APS protection group
............................................................................................................................
10-70
To add a 1x1 APS protection group
............................................................................................................................
10-72
To view a list of 1+1 or 1x1 APS protection groups
......................................................................................................
10-74
........................................................................................................
10-76
..........................................................................................................................
10-78
To modify a 1+1 or 1x1 APS protection group
To delete a 1+1 or 1x1 APS protection group
To operate an APS protection switch
Provisioning of MS-SPRing protection groups
.....................................................................................
10-80
.......................................................................................................
10-81
To view a list of 2-fiber MS-SPRing protection groups
To add a 2-fiber MS-SPRing protection group
................................................................................................
10-83
..................................................................................................
10-85
To modify a 2-fiber MS-SPRing protection group
To delete a 2-fiber MS-SPRing protection group
To operate a 2-fiber MS-SPRing protection switch
..............................................................................................
.....................................................................................
10-89
.......................................................................................................
10-90
To view a list of 4-fiber MS-SPRing protection groups
To add a 4-fiber MS-SPRing protection group
10-87
................................................................................................
10-92
..................................................................................................
10-94
To modify a 4-fiber MS-SPRing protection group
To delete a 4-fiber MS-SPRing protection group
..............................................................................................
10-96
.................................................................................................
10-98
...................................................................................................................
10-99
To operate a 4-fiber MS-SPRing protection switch
Provisioning of BLSR protection groups
To view a list of 2-fiber BLSR protection groups
To add a 2-fiber BLSR protection group
.........................................................................................................
10-101
...........................................................................................................
10-103
To modify a 2-fiber BLSR protection group
To delete a 2-fiber BLSR protection group
To operate a 2-fiber BLSR protection switch
.......................................................................................................
..............................................................................................
10-107
................................................................................................................
10-108
To view a list of 4-fiber BLSR protection groups
To add a 4-fiber BLSR protection group
10-105
To modify a 4-fiber BLSR protection group
.........................................................................................................
10-110
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
x
Contents
To delete a 4-fiber BLSR protection group
............................................................................................................
To operate a 4-fiber BLSR protection switch
11
10-114
Software and NE database management concepts
Overview
....................................................................................................................................................................................
Functionality description
Software upgrade
12
........................................................................................................
10-112
11-1
.....................................................................................................................................................
11-2
....................................................................................................................................................................
11-5
Software and NE database management tasks
Overview
....................................................................................................................................................................................
12-1
Tasks related to NE generics
....................................................................
12-3
...................................................................................................
12-4
To view a list of NE generics stored on the management system
To add an NE generic to the management system
To delete an NE generic from the management system
........................................................................................
To transfer an NE generic from the management system to an NE
.................................................................
To schedule the transfer of an NE generic from the management system to an NE
12-6
12-8
........................................................................................
12-11
............................................................................................................
12-12
To view a list of in-progress transfers of NE generics
To abort an in-progress NE generic transfer
................................
12-5
.....................................................................................................
12-15
To activate an NE generic on an NE
..........................................................................................................................
12-17
To commit an NE generic on an NE
...........................................................................................................................
12-20
To revert an NE generic on an NE
..............................................................................................................................
12-22
To schedule NE generic activation
...............................................................................................................................
12-24
To view a list of NE generics stored on an NE
Tasks related to NE databases
...............................................
12-28
...................................................................................
12-31
To view a list of NE database versions stored on the management system
To view a list of NE database versions stored on an NE
To back up NE database versions onto the management system
....................................................................
To schedule the backup of an NE database version onto the management system
.................................
12-32
12-37
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
xi
Issue 2, July 2008
See notice on first page
Contents
To restore an NE database version from the management system to an NE
.............................................
12-39
Glossary
Index
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
xii
About this information product
About this information product
Purpose
This information product provides information specific to the LambdaUnite ® MSS
network element managed with Lucent Optical Management System (OMS). It is
designed to cover mainly the Lucent OMS tasks that are traditionally related to the
element management level.
Safety information
This information product contains hazard statements for your safety. Hazard statements
are given at points where safety consequences to personnel, equipment, and operation
may exist. Failure to follow these statements may result in serious consequences.
Conventions used
These conventions are used in this document:
Numbering
The chapters of this document are numbered consecutively. The page numbering
restarts at “1” in each chapter. To facilitate identifying pages in different chapters, the
page numbers are prefixed with the chapter number. For example, page 2-3 is the third
page in chapter 2.
Cross-references
Cross-reference conventions and numbering conventions are identical. The first number
in a reference to a particular page refers to the corresponding chapter.
Keyword blocks
This document contains so-called keyword blocks to facilitate the location of specific
text passages. The keyword blocks are placed to the left of the main text and indicate
the contents of a paragraph or group of paragraphs.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
xiii
Issue 2, July 2008
See notice on first page
,
About this information product
Typographical conventions
Special typographical conventions apply to elements of the graphical user interface
(GUI), file names and system path information, keyboard entries, alarm messages, and
so on
•
•
•
Examples of text that appears on a graphical user interface (GUI), such as menu
options, window titles or push buttons:
– Provision{, Delete, Apply, Close, OK (push-button)
– Provision Timing/Sync (window title)
– View Equipment Details{ (menu option)
– Administration → Security → User Provisioning{ (path for invoking a
window)
Examples for file names and system path information:
– console
– /usr/local/bin/
Examples for keyboard entries:
– F1, Esc X, Alt-F, Ctrl-D, Ctrl-Alt-Del (simple keyboard entries)
A hyphen between two keys means that both keys have to be pressed
simultaneously. Otherwise, press a single key or a number of keys in sequence.
Abbreviations
Abbreviations used in this document can be found in the “Glossary” unless it can be
assumed that the reader is familiar with the abbreviation.
Orientation aids
This document contains the following orientation aids:
•
•
•
Overall TOC
Chapter TOCs
Index
The following graphic depicts the principle structure of this document:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
,
xiv
About this information product
Overall TOC
Chapter TOC
Index
Overall TOC
The overall table of contents (TOC) provides a structural overview of the entire
document. It lists the content of each chapter and the associated page number where
the respective information can be found.
The overall table of contents can be found after the legal page, before the “About this
information product” preface.
Chapter TOCs
Each chapter contains a table of contents (TOC) in its “Overview” section. The scope
of each chapter TOC is limited to the corresponding chapter. As in the overall TOC,
page numbers indicate where the respective information can be found.
Index
This manual also contains an alphabetical index, which can be found at the end of the
document, after the “Glossary”.
The index helps users to find specific information quickly by providing an alphabetical
list of key words with associated page numbers.
Related information
The manuals related to LambdaUnite ® MSS are shown in the following table:
Document title
Document code
LambdaUnite ® MSS Applications and Planning Guide
365-374-176R8.0.2 (109643833)
Presents a detailed overview of the system, describes its applications, gives
planning requirements, engineering rules, ordering information, and
technical specifications.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
xv
Issue 2, July 2008
See notice on first page
,
About this information product
Document title
LambdaUnite ®
Document code
MSS User Operations Guide
365-374-177R8.0.2 (109643858)
Provides step-by-step information for use in daily system operations. The
manual demonstrates how to perform system provisioning, operations, and
administrative tasks by use of WaveStar ® ITM-CIT.
LambdaUnite ® MSS Alarm Messages and Trouble Clearing Guide
365-374-178R8.0.2 (109643841)
Gives detailed information on each possible alarm message. Furthermore, it
provides procedures for routine maintenance, troubleshooting, diagnostics,
and component replacement.
LambdaUnite ® MSS Installation Guide
365-374-179R8.0.2 (109643874)
A step-by-step guide to system installation and set up. It also includes
information needed for pre-installation site planning and post-installation
acceptance testing.
LambdaUnite ® MSS Operations System Engineering Guide (TL1 Reference
Manual)
365-374-180R8.0.2 (109643866)
A reference for all TL1 commands which can be used to operate the
network element. The manual gives an introduction to the concept of the
TL1 commands and instructs how to use them.
Documentation CD-ROM LambdaUnite ® MSS (all manuals on a CD-ROM)
Documentation CD-ROM
LambdaUnite ®
MSS Software Release Description
365-374-181R8.0.2 (109643882)
This document is delivered with the NE
software.
LambdaUnite ® MSS Engineering and Ordering Information
Drawing ED8C948-10
LambdaUnite ® MSS Interconnect and Circuit Information
Drawing ED8C948-20
The documentation set related to Lucent OMS is shown in the following table:
Document title
Document code
Lucent OMS Getting Started Guide
365-315-145R5.0.1
Instructs new users how to use Lucent OMS. This document contains a
glossary of terms.
Lucent OMS Connection Management Guide
365-315-150R5.0.1
Instructs users how to use Lucent OMS to provision and manage network
connections.
Lucent OMS Network Element Management Guide
365-315-146R5.0.1
Instructs users how to use Lucent OMS to provision and manage network
elements.
Lucent OMS Ethernet Management Guide
365-315-147R5.0.1
Instructs users on how to use the Ethernet Management feature to provision
and manage Ethernet connections in a network.
Lucent OMS Service Assurance Guide
365-315-148R5.0.1
Instructs users on how to manage and interpret fault information collected
from the network.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
,
xvi
About this information product
Document title
Document code
Lucent OMS Administration Guide
365-315-149R5.0.1
Instructs users on how to administer and maintain Lucent OMS and the
network.
In addition, it is highly recommended to consult the TransLAN ® Ethernet SDH
Transport Solution Applications and Planning Guide, 365-377-001 (109584045) when
planning to use LambdaUnite ® MSS for Ethernet applications.
These documents and drawings can be ordered at or downloaded from the Customer
Information Center (CIC) (http://www.cic.lucent.com/) or via your Local Customer
Support.
Document support
The document support telephone numbers are:
•
•
1 630 713 5000 (for all countries)
1 888 727 3615 (for the continental United States)
Technical support
For technical support, contact your local customer support team. Reach them via the
web (https://support.lucent.com/) or the telephone number listed under the Technical
Assistance Center menu (http://www.lucent.com/contact/).
How to order
The order number of this document is 365-312-876R8.0.2 (issue 2).
How to comment
To comment on this information product, go to the Online Comment Form
(http://www.lucent-info.com/comments/enus/) or e-mail your comments to the
Comments Hotline (comments@alcatel-lucent.com).
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
xvii
Issue 2, July 2008
See notice on first page
,
1
S afety
1
Overview
...................................................................................................................................................................................................................................
Purpose
The aim of this chapter on safety is to provide users of LambdaUnite ® MSS systems
with the basic safety information.
In addition, the LambdaUnite ® MSS Release 8.0.2 Safety Guide, 365-374-159 contains
all the relevant information and safety guidelines to safeguard against personal injury
in a large number of languages. Furthermore, the Safety Guide may be useful to
prevent material damage to the equipment. The Safety Guide must be read by the
responsible technical personnel before carrying out relevant work on the system. The
valid version of that document must always be kept close to the equipment.
Potential sources of danger
The LambdaUnite ® MSS equipment has been developed in line with the present
state-of-the-art and fulfils the current national and international safety requirements. It
is provided with a high degree of operational safety resulting from many years of
development experience and continuous stringent quality checks in our company.
The equipment is safe in normal operation. There are, however, some potential sources
of danger that cannot be completely eliminated. In particular, these arise during the:
•
•
•
Opening of housings or equipment covers
Manipulation of any kind within the equipment, even if it has been disconnected
from the power supply
Disconnection of optical or electrical connections
through possible contact with the following:
•
•
•
•
Live parts
Laser light
Hot surfaces
Sharp edges
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
1-1
Issue 2, July 2008
See notice on first page
Safety
Overview
Contents
Structure of hazard statements
1-3
Basic safety aspects
1-5
Symbols used in hazard statements
1-7
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
1-2
Safety
Structure
of hazard statements
...................................................................................................................................................................................................................................
Overview
Hazard statements describe the safety risks relevant while performing tasks on
Alcatel-Lucent products during deployment and/or use. Failure to avoid the hazards
may have serious consequences.
General structure
Hazard statements include the following structural elements:
Item
Structure element
Purpose
1
Personal-injury symbol
Indicates the potential for personal injury
(optional)
2
Hazard-type symbol
Indicates hazard type (optional)
3
Signal word
Indicates the severity of the hazard
4
Hazard type
Describes the source of the risk of damage or
injury
5
Damage statement
Consequences if protective measures fail
6
Avoidance message
Protective measures to take to avoid the hazard
7
Identifier
The reference ID of the hazard statement
(optional)
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
1-3
Issue 2, July 2008
See notice on first page
Safety
Structure of hazard statements
Signal words
The signal words identify the hazard severity levels as follows:
Signal word
Meaning
DANGER
Indicates an imminently hazardous situation (high risk) which, if
not avoided, will result in death or serious injury.
WARNING
Indicates a potentially hazardous situation (medium risk) which,
if not avoided, could result in death or serious injury.
CAUTION
When used with the personal injury symbol:
Indicates a potentially hazardous situation (low risk) which, if
not avoided, may result in personal injury.
When used without the personal injury symbol:
Indicates a potentially hazardous situation (low risk) which, if
not avoided, may result in property damage, such as service
interruption or damage to equipment or other materials.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
1-4
Safety
Basic
safety aspects
...................................................................................................................................................................................................................................
General safety requirements
In order to keep the technically unavoidable residual risk to a minimum, it is
imperative to observe the following rules:
•
•
•
•
•
•
•
•
•
•
Transport, storage and operation of the system must be under the permissible
conditions only.
See accompanying documentation and information on the system.
Installation, configuration, and disassembly must be carried out only by expert
personnel and with reference to the respective documentation.
Due to the complexity of the system, the personnel requires special training.
The system must be operated by expert and authorized users only.
The user must operate the system only after having read and understood this
chapter on safety and the parts of the documentation relevant to operation. For
complex systems, additional training is recommended. Any obligatory training for
operating and service personnel must be carried out and documented.
The system must not be operated unless it is in perfect working order.
Any faults and errors that might affect safety must be reported immediately by the
user to a person in responsibility.
The system must be operated only with the connections and under the
environmental conditions as described in the documentation.
Any conversions or changes to the system or parts of the system (including the
software) must be carried out by qualified Lucent Technologies personnel or by
expert personnel authorized by Lucent Technologies.
All changes carried out by other persons lead to a complete exemption from
liability.
No components/spare parts must be used other than those recommended by the
manufacturer and those listed in the procurement documents.
The removal or disabling of safety facilities, the clearing of faults and errors, and
the maintenance of the equipment must be carried out by specially qualified
personnel only.
The respective parts of the documentation must be strictly observed. The
documentation must also be consulted during the selection of measuring and test
equipment.
Calibrations, special tests after repairs, and regular safety checks must be carried
out, documented, and archived.
Non-system software is used at one’s own risk. The use/installation of non-system
software can adversely affect the normal functioning of the system.
Only use tested and virus-free data carriers (CD, DVD, floppy disks, streamer
tapes, {).
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
1-5
Issue 2, July 2008
See notice on first page
Safety
Basic safety aspects
Summary of important safety instructions
Especially observe the following safety instructions, they are of particular importance
for LambdaUnite ® MSS systems:
•
•
•
•
•
•
•
•
•
This equipment is to be installed only in Restricted Access Areas in business and
customer premises.
Applications in accordance with Articles 110-16, 110-17 and 110-18 of the National
Electrical Code, ANSI/NFPA No. 70. Other installations exempt from the
enforcement of the National Electrical Code may be engineered according to the
accepted practices of the local telecommunications utility.
This product should only be operated from the type of power source indicated on
the marking label.
This equipment must be provided with a readily accessible disconnect device as
part of the building installation.
Installation must include an independent frame ground drop to the building ground.
Refer to the LambdaUnite ® MSS Installation Guide.
For information on proper mounting instructions, consult the LambdaUnite ® MSS
Installation Guide.
Install only equipment identified in the LambdaUnite ® MSS Installation Guide
provided with this product. Use of other equipment may result in improper
connection of circuitry leading to fire or injury to persons.
To reduce the risk of electrical shock, do not disassemble this product. Installation
and service should be performed by trained personnel only. Opening or removing
covers and/or circuit boards may expose you to dangerous voltages or other risks.
Incorrect re-assembly can cause electrical shock when the unit is subsequently
used.
Slots and openings in this product are provided for ventilation. To protect the
product from overheating, these openings must not be blocked or covered. This
product should not be placed in a built-in installation unless proper ventilation is
provided.
Never push objects of any kind into this product through slots as they may touch
dangerous voltage points or short-cut parts that could result in a risk of fire or
electrical shock. Never spill liquids of any kind on the product.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
1-6
Safety
Symbols
used in hazard statements
...................................................................................................................................................................................................................................
Symbol table
The following symbols are defined for hazard statements:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
Legend:
1
Personal injury symbol
12
Heavy overhead load
2
Electric shock
13
Noxious substance
3
Hazard of laser radiation
14
Explosion hazard
4
Components sensitive to electrostatic
discharge (ESD)
15
Falling object hazard
5
Electromagnetic radiation
16
Risk of suffocation
6
Flammable material / risk of fire
17
Pinch hazard
7
Service disruption hazard
18
Lifting hazard, heavy object
8
Laceration hazard
19
Inhalation hazard
9
Corrosive substance
20
Slip hazard
10
Hazard caused by batteries
21
Trip hazard
11
Hot surface
22
Hazard of falling
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
1-7
Issue 2, July 2008
See notice on first page
2
S ecurity administration tasks
2
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter informs about how to perform the most common tasks related to security
and user (login) administration.
Contents
To retrieve the current user’s security information
2-2
To retrieve user security information
2-5
To modify the current user’s security information
2-9
To modify user security information
2-12
To modify the current user’s password
2-16
To terminate user sessions
2-18
To create new users
2-20
To delete users
2-23
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
2-1
Issue 2, July 2008
See notice on first page
Security administration tasks
To
retrieve the current user’s security information
...................................................................................................................................................................................................................................
When to use
Use this task to view security information for the current user (current login) on a
network element. The information is related to the NE primary login used when the
OMS-to-NE connection has been set up.
Related information
For a more detailed explanation, please refer to the description of the RTRV-USER
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Users.
In the Function field, select Retrieve User.
Click Go.
Result: The Retrieve User page is displayed.
...................................................................................................................................................................................................
3
Optional, for expert users only: The NE Command panel may be used to edit the
native command language of the function.
...................................................................................................................................................................................................
4
Click Submit.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
2-2
Security administration tasks
To retrieve the current user’s security information
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
...................................................................................................................................................................................................
5
The output parameters for this function are:
1. uid – User ID
User ID whose security parameters are displayed. the NE primary login used when
the OMS-to-NE connection has been set up.
2. page – Password Aging Interval
This parameter specifies the period in days after which the user has to change the
password of their account.
Type: integer
Range: 0 - password aging function is disabled, 7-999 [days]
Default: 90
3. screen – Message Screening
This parameter specifies what output messages are associated with the uid. This
parameter is omitted if the user has none of these values. Any combination of these
values may be displayed using ampersand (&)
Range:
• DBCHG
Data Base Change notifications: changes in creation of entities, in user
provisionable parameters, in deletion of entities will be reported (data base
changes).
File Transfer In-progress notifications: The user will receive REPT DBCHG
and REPT EVT FXFR messages.
The value DBCHG shall always be used together with the value STCHG.
• STCHG
State Change notifications – report changes in user non-provisionable
parameters (state changes). The user will receive REPT DBCHG messages.
The value STCHG shall always be used together with the value DBCHG.
• PSCHG
Protection switch notifications – report protection switch changes. User will
receive REPT EVT and REPT SW messages.
• ALARMS
Alarm notifications. The user will receive REPT ALM ENV, REPT ALM, and
REPT EVT messages.
• ONNS
ONNS Notifications. Database and state changes associated with entities
managed by ONNS application and only issued when xcsetup = NN. The
related ONNS TL1 notifications are REPT PTHCHG, REPT PTHEVT, REPT
NNCHG, REPT NNEVT.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
2-3
Issue 2, July 2008
See notice on first page
Security administration tasks
•
To retrieve the current user’s security information
SECURITY: Security event notifications
•
OWN
Responses to own commands. The user will receive no other notifications.
• NA
Not applicable. For users with uidclass=MEMADMIN only this value is
allowed. The notification behavior is controlled in this case by the user class. If
the value NA is applied for users of other user classes, then the value has the
same effect as DBCHG.
4. tmout – Inactivity Timeout Period
If there are no messages between the user and the NE over the Timeout Period, the
session is logged off. A value of 0 disables the timeout function.
5. uidclass – UID Class
This is the user class of a uid.
Type: alphanumeric value set
Range:
• OTHER – This is the default class. For users in this class, command privileges
and notifications are controlled only by their UPCs and their notification
Registration List.
• MEMADMIN – User class for memory administration users. All users of this
class share the same atag counter for autonomous messages and are allowed to
execute the command RTRV-AO.
6. upc – User Privilege Code List
This parameter specifies the user privilege code UCFC/UCAL pair assigned to a
user. If a user tries to operate a command with a privilege code higher than
assigned to the user for the category of the command, the command will be denied.
Type: alphanumeric string. Also allowed is ’&’ for concatenation.
Range: Pi, Mi, Ti, Si, PMi, Di where “i” is an integer ranging from 0 to 5, with
i=0 implying that there is no authorization for the functional category. Note: S0 is
not allowed.
Default: P1&M1&T1&S1&PM1
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
2-4
Security administration tasks
To
retrieve user security information
...................................................................................................................................................................................................................................
When to use
Use this task to view security information for one or all users (logins) on a network
element.
Related information
For a more detailed explanation, please refer to the description of the RTRV-USER-SECU
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Users.
In the Function field, select Retrieve User Security.
Click Go.
Result: The Retrieve User Security page is displayed.
...................................................................................................................................................................................................
3
In the User identifier field, enter a login (user) name. To retrieve information for all
logins (users), leave the field empty.
...................................................................................................................................................................................................
4
Optional, for expert users only: The NE Command panel may be used to edit the
native command language of the function.
...................................................................................................................................................................................................
5
Click Submit.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
2-5
Issue 2, July 2008
See notice on first page
Security administration tasks
To retrieve user security information
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
...................................................................................................................................................................................................
6
The output parameters for this function are:
1. uid – user ID
User ID whose security parameters are to be retrieved. the NE primary login used
when the OMS-to-NE connection has been set up.
2. alw_login – allow login
This parameter displays the enable/disable state of a User ID.
A User ID can be automatically disabled by the system when the time specified by
parameter usrage expires or via the ED-USER-SECU command. A User ID can be
enabled via the ED-USER-SECU command.
If a User ID is disabled, logins with that User ID are denied.
3. initobs – initialization observability
This parameter allows the system to accept commands before it has completed
initialization.
4. page – password aging interval
This parameter specifies the period in days after which the user has to change the
password of their account.
Type: integer
Range: 0 - password aging function is disabled, 7-999 [days]
Default: 90
5. screen – message screening
This parameter specifies what output messages are associated with the uid. This
parameter is omitted if the user has none of these values. Any combination of these
values may be specified using ampersand (&)
Range:
• DBCHG
Data base change notifications: changes in creation of entities, in user
provisionable parameters, in deletion of entities will be reported (data base
changes).
File transfer in-progress notifications: The user will receive REPT DBCHG and
REPT EVT FXFR messages.
The value DBCHG shall always be used together with the value STCHG.
• STCHG
State change notifications – report changes in user non-provisionable parameters
(state changes). The user will receive REPT DBCHG messages.
The value STCHG shall always be used together with the value DBCHG.
• PSCHG
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
2-6
Security administration tasks
6.
7.
8.
9.
To retrieve user security information
Protection switch notifications – report protection switch changes. User will
receive REPT EVT and REPT SW messages.
• ALARMS
Alarm notifications. The user will receive REPT ALM ENV, REPT ALM, and
REPT EVT messages.
• ONNS
ONNS notifications. Database and state changes associated with entities
managed by ONNS application and only issued when xcsetup = NN. The
related ONNS TL1 notifications are REPT PTHCHG, REPT PTHEVT, REPT
NNCHG, REPT NNEVT.
• SECURITY: Security event notifications
• OWN
Responses to own commands. The user will receive no other notifications.
• NA
Not applicable. For users with uidclass=MEMADMIN only this value is
allowed. The notification behavior is controlled in this case by the user class. If
the value NA is applied for users of other user classes, then the value has the
same effect as DBCHG.
tmout – inactivity timeout period
If there are no messages between the user and the NE over the Timeout Period, the
session is logged off. A value of 0 disables the timeout function.
ucpl – user community priority level
This value is always set to 1.
uidclass – UID class
This is the user class of a uid.
Type: alphanumeric value set
Range:
• OTHER – This is the default class. For users in this class, command privileges
and notifications are controlled only by their UPCs and their notification
Registration List.
• MEMADMIN – User class for memory administration users. All users of this
class share the same atag counter for autonomous messages and are allowed to
execute the command RTRV-AO.
upc – user privilege code list
This parameter specifies the user privilege code UCFC/UCAL pair assigned to a
user. If a user tries to operate a command with a privilege code higher than
assigned to the user for the category of the command, the command will be denied.
Type: alphanumeric string. Also allowed is ’&’ for concatenation.
Range: Pi, Mi, Ti, Si, PMi, Di where “i” is an integer ranging from 0 to 5, with
i=0 implying that there is no authorization for the functional category. Note: S0 is
not allowed.
Default: P1&M1&T1&S1&PM1
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
2-7
Issue 2, July 2008
See notice on first page
Security administration tasks
To retrieve user security information
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
2-8
Security administration tasks
To
modify the current user’s security information
...................................................................................................................................................................................................................................
When to use
Use this task to modify security information for the current user (the current login) on
a network element. The information is related to the NE primary login used when the
OMS-to-NE connection has been set up.
Related information
For a more detailed explanation, please refer to the description of the ED-USER
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Users.
In the Function field, select Edit User.
Click Go.
Result: The Edit User page is displayed.
...................................................................................................................................................................................................
3
In the Message screening field, enter an alphanumeric string composed of a list of
values from the list below. To enter more than one value, concatenate using the ’&’
symbol.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
2-9
Issue 2, July 2008
See notice on first page
Security administration tasks
To modify the current user’s security information
Range:
•
•
•
•
•
•
•
•
DBCHG
Data Base Change notifications: changes in creation of entities, in user
provisionable parameters, in deletion of entities will be reported (data base
changes).
File Transfer In-progress notifications: The user will receive REPT DBCHG and
REPT EVT FXFR messages.
The value DBCHG shall always be used together with the value STCHG.
STCHG
State Change notifications – report changes in user non-provisionable parameters
(state changes). The user will receive REPT DBCHG messages.
The value STCHG shall always be used together with the value DBCHG.
PSCHG
Protection switch notifications – report protection switch changes. User will receive
REPT EVT and REPT SW messages.
ALARMS
Alarm notifications. The user will receive REPT ALM ENV, REPT ALM, and
REPT EVT messages.
ONNS
ONNS Notifications. Database and state changes associated with entities managed
by ONNS application and only issued when xcsetup = NN. The related ONNS TL1
notifications are REPT PTHCHG, REPT PTHEVT, REPT NNCHG, REPT NNEVT.
SECURITY: Security event notifications
OWN
Responses to own commands. The user will receive no other notifications.
NA
Not applicable. For users with uidclass=MEMADMIN only this value is allowed.
The notification behavior is controlled in this case by the user class. If the value
NA is applied for users of other user classes, then the value has the same effect as
DBCHG.
...................................................................................................................................................................................................
4
Optional, for expert users only: The NE Command panel may be used to edit the
native command language of the function.
...................................................................................................................................................................................................
5
Click Submit.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
2-10
Security administration tasks
To modify the current user’s security information
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
2-11
Issue 2, July 2008
See notice on first page
Security administration tasks
To
modify user security information
...................................................................................................................................................................................................................................
When to use
Use this task to modify security information for the users (logins) on a network
element.
Related information
For a more detailed explanation, please refer to the description of the ED-USER-SECU
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Users.
In the Function field, select Edit User Security.
Click Go.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
2-12
Security administration tasks
To modify user security information
Result: The Edit User Security page is displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
Current user identifier – the login (user) for which the security settings should be
modified.
Range: 1 to 10 characters
•
•
•
•
•
•
New password identifier – specifies the new password ID for the addressed login.
This is an optional parameter and in the absence of a value the default is the
current value.
Range: 6 to 10 legal characters. Valid passwords consist of at least two
non-alphabetic characters with at least one special character. The special character
can be one of the required non-alpha characters. For example, TEST1+ is a valid
password. The first character of a password must be a letter.
User privilege code list – specifies the user privilege code UCFC/UCAL pair
assigned to a user. Multiple UCFC/UCALs can be specified using single
ampersands (&). If a user tries to operate a command with a privilege code higher
than assigned to the user for the category of the command the command will be
denied.
Range: Pi, Mi, Ti, Si, PMi, Di where i is an integer ranging from 0 to 5, with i
= 0 implying that there is no authorization for the functional category. S0 is not
allowed.
Allow login – specifiess the enable/disable state of a User ID.
A User ID can be automatically disabled by the system or via the ED-USER-SECU
command. A User ID can be enabled via the ED-USER-SECU command.
If a User ID is disabled, logins with that User ID are denied.
Range:
– YES: User ID is enabled
– NO: User ID is disabled
New user identifier – allows to rename the 2 predefined super-users. It cannot be
used to rename a non-super-user login. .
Range: 1 to 10 characters
The uid ALL is not allowed in any combination of upper or lower cases.
Password aging interval (days) – specifies the period in days after which the user
has to change the password of their account. If the value is set to 0 then the
password aging function is disabled.
Range: 0, 7 to 999 [days]
Message screening – enter an alphanumeric string composed of a list of values
from the list below. To enter more than one value, concatenate using the ’&’
symbol.
Range:
– DBCHG
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
2-13
Issue 2, July 2008
See notice on first page
Security administration tasks
•
•
To modify user security information
Data Base Change notifications: changes in creation of entities, in user
provisionable parameters, in deletion of entities will be reported (data base
changes).
File Transfer In-progress notifications: The user will receive REPT DBCHG
and REPT EVT FXFR messages.
The value DBCHG shall always be used together with the value STCHG.
– STCHG
State Change notifications – report changes in user non-provisionable
parameters (state changes). The user will receive REPT DBCHG messages.
The value STCHG shall always be used together with the value DBCHG.
– PSCHG
Protection switch notifications – report protection switch changes. User will
receive REPT EVT and REPT SW messages.
– ALARMS
Alarm notifications. The user will receive REPT ALM ENV, REPT ALM, and
REPT EVT messages.
– ONNS
ONNS Notifications. Database and state changes associated with entities
managed by ONNS application and only issued when xcsetup = NN. The
related ONNS TL1 notifications are REPT PTHCHG, REPT PTHEVT, REPT
NNCHG, REPT NNEVT.
– SECURITY: Security event notifications
– OWN
Responses to own commands. The user will receive no other notifications.
– NA
Not applicable. For users with uidclass=MEMADMIN only this value is
allowed. The notification behavior is controlled in this case by the user class. If
the value NA is applied for users of other user classes, then the value has the
same effect as DBCHG.
Inactivity timeout period (min) – if there are no messages between the user and
the NE for the time specified, the session is logged off. A value of 0 disables the
timeout function.
Range: 0 – 999 [minutes]
User identifier class – specifies the user class.
Range:
– Other – This is the default class. For users in this class, command privileges
and notifications are controlled only by their UPCs and their notification
Registration List.
– Memory Adminstration User – User class for memory administration users. All
users of this class share the same atag counter for autonomous messages and
are allowed to execute the command RTRV-AO.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
2-14
Security administration tasks
To modify user security information
...................................................................................................................................................................................................
4
Optional, for expert users only: The NE Command panel may be used to edit the
native command language of the function.
...................................................................................................................................................................................................
5
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
2-15
Issue 2, July 2008
See notice on first page
Security administration tasks
To
modify the current user’s password
...................................................................................................................................................................................................................................
When to use
Use this task to modify the current user’s password (which is the current login on a
network element). The information is related to the NE primary login used when the
OMS-to-NE connection has been set up.
Related information
For a more detailed explanation, please refer to the description of the ED-PID
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Users.
In the Function field, select Edit Password Identifier.
Click Go.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
2-16
Security administration tasks
To modify the current user’s password
Result: The Edit Password Identifier page is displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
Old password identifier – specifies the password ID for the addressed login. This
•
is an optional parameter and in the absence of a value the default is the current
value.
Range: 6 to 10 legal characters. Valid passwords consist of at least two
non-alphabetic characters with at least one special character. The special character
can be one of the required non-alpha characters. For example, TEST1+ is a valid
password. The first character of a password must be a letter.
New password identifier – specifies the password ID for the addressed login. This
is an optional parameter and in the absence of a value the default is the current
value.
Range: 6 to 10 legal characters. Valid passwords consist of at least two
non-alphabetic characters with at least one special character. The special character
can be one of the required non-alpha characters. For example, TEST1+ is a valid
password. The first character of a password must be a letter.
...................................................................................................................................................................................................
4
Optional, for expert users only: The NE Command panel may be used to edit the
native command language of the function.
...................................................................................................................................................................................................
5
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
2-17
Issue 2, July 2008
See notice on first page
Security administration tasks
To
terminate user sessions
...................................................................................................................................................................................................................................
When to use
Use this task to terminate all login sessions of a particular user or all users within the
NE.
Related information
For a more detailed explanation, please refer to the description of the CANC-USER-SECU
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Users.
In the Function field, select Cancel User Security.
Click Go.
Result: The Cancel User Security page is displayed.
...................................................................................................................................................................................................
3
In the User identifier field, enter the login (user) for which the session should be
terminated. To terminate all user’s session, leave the field empty. Only privileged users
can log out other users.
...................................................................................................................................................................................................
4
Optional, for expert users only: The NE Command panel may be used to edit the
native command language of the function.
...................................................................................................................................................................................................
5
Click Submit.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
2-18
Security administration tasks
To terminate user sessions
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
2-19
Issue 2, July 2008
See notice on first page
Security administration tasks
To
create new users
...................................................................................................................................................................................................................................
When to use
Use this task to create new logins (users) and the related security information on a
network element.
Related information
For a more detailed explanation, please refer to the description of the ENT-USER-SECU
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Users.
In the Function field, select Enter User Security.
Click Go.
Result: The Enter User Security page is displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
•
User identifier – the new login (user) name.
Range: 1 to 10 characters
Password identifier – specifies the password ID for the addressed login. This is an
optional parameter and in the absence of a value the default is the current value.
Range: 6 to 10 legal characters. Valid passwords consist of at least two
non-alphabetic characters with at least one special character. The special character
can be one of the required non-alpha characters. For example, TEST1+ is a valid
password. The first character of a password must be a letter.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
2-20
Security administration tasks
•
•
•
To create new users
User privilege code list – specifies the user privilege code UCFC/UCAL pair
assigned to a user. Multiple UCFC/UCALs can be specified using single
ampersands (&). If a user tries to operate a command with a privilege code higher
than assigned to the user for the category of the command the command will be
denied.
Range: Pi, Mi, Ti, Si, PMi, Di where i is an integer ranging from 0 to 5, with i
= 0 implying that there is no authorization for the functional category. S0 is not
allowed.
Password aging interval (days) – specifies the period in days after which the user
has to change the password of their account. If the value is set to 0 then the
password aging function is disabled.
Range: 0, 7 to 999 [days]
Message screening – enter an alphanumeric string composed of a list of values
from the list below. To enter more than one value, concatenate using the ’&’
symbol.
Range:
– DBCHG
Data Base Change notifications: changes in creation of entities, in user
provisionable parameters, in deletion of entities will be reported (data base
changes).
File Transfer In-progress notifications: The user will receive REPT DBCHG
and REPT EVT FXFR messages.
The value DBCHG shall always be used together with the value STCHG.
– STCHG
State Change notifications – report changes in user non-provisionable
parameters (state changes). The user will receive REPT DBCHG messages.
The value STCHG shall always be used together with the value DBCHG.
– PSCHG
Protection switch notifications – report protection switch changes. User will
receive REPT EVT and REPT SW messages.
– ALARMS
Alarm notifications. The user will receive REPT ALM ENV, REPT ALM, and
REPT EVT messages.
– ONNS
ONNS Notifications. Database and state changes associated with entities
managed by ONNS application and only issued when xcsetup = NN. The
related ONNS TL1 notifications are REPT PTHCHG, REPT PTHEVT, REPT
NNCHG, REPT NNEVT.
– SECURITY: Security event notifications
– ALL
All notifications.
This value can be used in input direction as a short-hand notation for
DBCHG&STCHG&PSCHG&ALARMS&ONNS&SECURITY
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
2-21
Issue 2, July 2008
See notice on first page
Security administration tasks
To create new users
–
•
OWN (default)
Responses to own commands. The user will receive no other notifications.
– NA
Not applicable. For users with uidclass=MEMADMIN only this value is
allowed. The notification behavior is controlled in this case by the user class. If
the value NA is applied for users of other user classes, then the value has the
same effect as DBCHG.
Inactivity timeout period (min) – if there are no messages between the user and
the NE for the time specified, the session is logged off. A value of 0 disables the
timeout function.
Range: 0 – 999 [minutes]
•
User identifier class – specifies the user class.
–
–
Other – this is the default class. For users in this class, command privileges and
notifications are controlled only by their UPCs and their notification registration
list.
Memory administration user – user class for memory administration users. All
users of this class share the same atag counter for autonomous messages and
are allowed to execute the command RTRV-AO.
...................................................................................................................................................................................................
4
Optional, for expert users only: The NE Command panel may be used to edit the
native command language of the function.
...................................................................................................................................................................................................
5
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
2-22
Security administration tasks
To
delete users
...................................................................................................................................................................................................................................
When to use
Use this task to delete a particular user (login) within the NE.
Related information
For a more detailed explanation, please refer to the description of the DLT-USER-SECU
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Users.
In the Function field, select Delete User Security.
Click Go.
Result: The Delete User Security page is displayed.
...................................................................................................................................................................................................
3
In the User identifier field, enter the login (user) to be deleted.
...................................................................................................................................................................................................
4
Optional, for expert users only: The NE Command panel may be used to edit the
native command language of the function.
...................................................................................................................................................................................................
5
Click Submit.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
2-23
Issue 2, July 2008
See notice on first page
Security administration tasks
To delete users
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
2-24
3
3 anagement communication
M
setup concepts
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter presents concept information related to management communication setup
on LambdaUnite ® MSS network elements using Lucent OMS.
Contents
Basic DCN principles
3-2
DCN configurations
3-5
DCN configuration guidelines
3-9
DCN protocols and services
3-10
NSAP address structure
3-12
Data communication channels (DCC)
3-14
LAN access
3-17
Name-to-address translation
3-18
OMS-to-NE connections concepts
3-19
Orderwire and user bytes
3-21
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
3-1
Issue 2, July 2008
See notice on first page
Management communication setup concepts
Basic
DCN principles
...................................................................................................................................................................................................................................
Purpose
A data communication network (DCN) is used for the exchange of management data.
This section provides an overview of the data communication network and describes
the type of communication between the nodes in the network and the protocols used.
SDH/SONET management network
The SDH/SONET management network is an overlay of the transmission network. The
management system (for example Lucent OMS) and the network elements (NEs)
together are the nodes of this network. The 10/100BASE-T interface and data
communication channel (DCC) provide the physical connection between the nodes.
DCN physical components
The figure below illustrates a data communication network (DCN) as defined by the
Open Systems Interconnection (OSI) model. This figure refers to the physical
components and connections in the DCN. It does not give information about the logical
configuration of the DCN.
WaveStar®
ITM-CIT
Management
System
Router
Q-LAN
Gateway
NE
Q-LAN
DCC
Gateway
NE
DCC
NE
DCC
NE
NE
DCC
NE
NE
Q-LAN
(LCN)
NE
DCC
DCC
NE
NE
NE
The figure shows three LANs and a number of DCC channels in an SDH/SONET
transmission network with point-to-point configuration and two rings connected to a
management system, for example Lucent OMS. The management system is connected
to the transmission network via gateway network elements (GNE) by the LAN. The
network elements are connected to each other by DCC channels.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
3-2
Management communication setup concepts
Basic DCN principles
Local Communications Network (LCN)
In the case where there is no DCC connectivity between nodes, a local
communications network (LCN) can be used to connect the nodes to each other. See
the LCN on the right side of the figure.
“NE” versus “Node”
Network elements can be identified by their target identifier (TID), that is their NE
name (“NE name” and “TID” are used synonymously throughout this manual), whereas
a node is identified by its network service access point (NSAP) address or its network
entity title (NET). Each NSAP address or NET within a network constitutes a node
which can individually be addressed. A node represents an end system (ES)
(represented by the NSAP address) and/or an intermediate system (IS) (represented by
the NET) in a data communications network (DCN).
Multiple OSI nodes
A network element can consist of multiple OSI nodes (OSI node1 to OSI node8). An
OSI node is a fully provisionable OSI routing node, which can be seen externally via
the routing data base. The default node is OSI node1, which is the only node to offer
the 7 layer OSI services to all application parts. Only node1 is represented by the
NSAP address. All other OSI nodes only provide the TARP and the network layer
services and are represented by their NET.
DCN communication protocols
Communication protocols used in the data communication network (DCN) between the
nodes include:
•
•
Ethernet (on the 10BASE-T) LAPD (on the DCC channels)
OSI network protocol (DCN wide)
The OSI network protocol (OSI-DCN) is used for routing management data between
nodes in the DCN.
ISO-OSI network protocol
The network protocol used between nodes is the ISO-OSI network protocol (ISO/IEC
8648). According to this protocol a node in the network can behave as an end system
(ES) or as an intermediate system (IS), sometimes called a router.
End systems (ES)
Nodes behaving as end systems (ES) perform no forwarding of data packets. They
communicate with each other on an end-to-end basis via intermediate systems.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
3-3
Issue 2, July 2008
See notice on first page
Management communication setup concepts
Basic DCN principles
Intermediate systems (IS)
Intermediate systems (IS) are used for routing data between nodes and (sub) networks.
The end system to intermediate system (ES-IS) protocol is responsible for the exchange
of data between an end system and intermediate system. A network element can act
both as an end system as well as an intermediate system. However, a Lucent OMS, for
example, can only act as end system.
ES - IS protocol
The end system to intermediate system protocol (ES-IS protocol) provides information
to ISs on the existence of ESs within an area. This information is sent periodically to
the ISs via a broadcast mechanism. The ES-IS protocol permits ESs to discover the
existence and reachability of ISs and vice versa. Furthermore, the ES-IS protocol
provides information to ISs supporting the computation of the shortest path first (SPF)
algorithm. LambdaUnite ® MSS products make use of the ES-IS protocol acc. to ISO
9542.
IS-IS protocol
The intermediate system to intermediate system (IS-IS) protocol is used between
intermediate systems in the DCN. The IS-IS protocol maintains the IS routing
information base (RIB). The information in this information base is used for the
routing of management data packets in the DCN by the intermediate systems.
Routing information base and LSPs
Each RIB comprises a number of tables. These tables contain information on network
service access point (NSAP) addresses of nodes in the network and ports of the IS
through which these nodes can be reached. Intermediate systems exchange routing
information regularly with one another as part of the IS-IS protocol by the use of link
state protocol data units (LSP).
The LSPs contain the information on the NSAP addresses of nodes used in the tables
of the RIBs.
Management protocol: TL1
The management of LambdaUnite ® MSS products is based on the use of the
transaction language 1 (TL1), defined by Telcordia Technologies, formerly Bellcore,
standards on the OSI application layer.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
3-4
Management communication setup concepts
DCN
configurations
...................................................................................................................................................................................................................................
Hierarchical routing
Hierarchical routing is used for large networks when the number of NSAP entries in
the RIB databases of the intermediate systems is too large. When this happens, it
causes an exponential increase of exchanged LSPs between intermediate systems. This
in turn causes the performance of the DCN to decrease due to the computation of the
shortest path first algorithm.
Hierarchical routing definition
In hierarchical routing, the DCN addressing domain is divided into a number of areas.
Each area is assigned a unique identifier. The value of the area identifier of each
node’s NSAP address is set according to the area the node is part of.
Level 1, level 2 definition
Each area contains a number of:
•
•
•
End systems
First level (level 1) intermediate systems
Second level (level 2) intermediate systems
Level 1 intermediate systems provide interconnectivity between nodes within the same
area. Level 2 intermediate systems provide interconnectivity between nodes belonging
to different areas.
Level 2 subdomain
The complete set of level 2 intermediate systems is also referred to as the level 2
subdomain. All areas in a network are connected via the level 2 subdomain.
Area-divisioning of a DCN
Partitioning is configuration of the DCN in such a way that the exchange of LSPs
between intermediate systems is limited.
When networks are partitioned into areas, the RIB database(s) in the systems are much
smaller and hence the routing overhead is significantly reduced. Intermediate systems
in an area only exchange information (LSPs) on nodes with other systems in their own
area. Information on other areas is exchanged by level 2 intermediate systems only and
maintained by the level 2 intermediate systems of the area.
In this way, the data management load in the network is strongly reduced, while
keeping the dynamic re-routing capabilities of intermediate systems in case of failures
intact. It is important to notice that although the DCN is divided into areas, ES-ES
communication between all nodes in the DCN is still possible.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
3-5
Issue 2, July 2008
See notice on first page
Management communication setup concepts
DCN configurations
The figure below illustrates how a network can be partitioned into areas, connected by
level 2 intermediate systems. Each area has at least one level 2 intermediate system
assigned and can have a number of level 1 intermediate systems and end systems.
Area 4
B
A
Level 2 subdomain
Area 1
Area 3
ES
Area 2
Level 1 IS
Level 2 IS
C
Routing management data
The following scenario describes routing management data in a divisioned network.
Suppose a node A wants to send messages to another node. If this node is in its own
area (determined by the area ID part in the area address field), the messages from A to
this particular node (B) are routed directly using the level 1 intermediate system (see
previous figure).
Alternatively, if the required destination is in a different area (C), the messages are sent
to a second, higher level (level 2) intermediate system. This intermediate system routes
the messages coming from node A to other level 2 intermediate systems until they
reach a level 2 intermediate system attached to the destination area of C. From there it
is routed within the area using level 1 intermediate systems to node C.
Notice that in both of the above cases the ES-ES communication between nodes in the
same or in different areas is still possible.
OSI-DCN networks types
In general, the OSI-DCN network can be classified in three types:
•
•
•
Undivided
IS-IS clustered
IS-IS area divided network
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
3-6
Management communication setup concepts
DCN configurations
Undivided network definition
An undivided network consists of a single routing domain. There is no division
between the nodes at the network protocol level. All nodes in the network and
especially the intermediate systems can exchange routing information with each other.
Although a network element can only be managed by one Lucent OMS at a time, the
IS-IS protocol is running between all nodes in the network. This leads to the exchange
of LSPs between all intermediate systems of the network.
Management
System
Management
System
LCN
IS-IS clustered DCN
In order to avoid the decrease of performance, the exchange of LSPs over a certain
port can be disabled in some nodes. A node can exchange LSPs over its DCC or LAN
(10BASE-T) ports. The exchange of LSPs over the DCC channel can be disabled.
However, this also prevents the exchange of management data over this port and
prevents the use of this DCC port for re-routing in case of a failure of another port.
Management
System
LCN
Remote
Cluster
Disabling exchange of LSPs
Another option is to disable the exchange of LSPs over the LAN (10BASE-T) port.
This can be done by choosing the IS to have a NO-IS-IS port. This node is also
referred to as a NO-IS-IS (gateway) node. If this is done for all intermediate systems
on a LAN, the LAN becomes a NO-IS-IS LAN. In NO-IS-IS LANs, the IS-IS protocol
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
3-7
Issue 2, July 2008
See notice on first page
Management communication setup concepts
DCN configurations
is not run on the 10BASE-T. This prevents the exchange of LSPs between intermediate
systems on a 10BASE-T. This results in a network which comprises several clusters of
nodes. Between the clusters there is no IS-IS traffic.
ES-ES communication
Within a cluster the ES-ES, ES-IS and IS-IS communication is still possible. There is
however no communication possible between nodes in different clusters. For example a
WaveStar ® ITM-CIT can be connected to a node in a cluster for maintenance activities
on nodes within a cluster. However, it is then not possible to do a remote login from
this node to a node of another cluster.
Management system connections
The management system connected to the 10BASE-T can still communicate with all
nodes in the clusters since the ES-IS protocol on the 10BASE-T is not disabled.
Important to notice is that the nodes in a remote cluster lose their association with the
management system when NO-IS-IS is chosen on the gateway node of the remote
cluster. It is advised to connect the management system to the 10BASE-T that connects
the clusters to each other and to assign NO-IS-IS only to nodes on this LAN.
IS-IS area divided DCN
The division of the DCN in areas by introducing level 2 intermediate systems is
similar to disabling the IS-IS protocol over the 10BASE-T port of nodes, as described
earlier.
Similar to clustering, the exchange of level 1 LSPs between intermediate systems in
different areas is prevented. However, level 2 LSPs are still exchanged between level 2
intermediate systems.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
3-8
Management communication setup concepts
DCN
configuration guidelines
...................................................................................................................................................................................................................................
Guidelines
Please observe the following engineering guidelines when configuring a DCN with
LambdaUnite ® MSS systems involved:
•
•
•
•
•
•
•
A maximum of 250 nodes (NSAP addresses) is supported in an area.
Notice that a LambdaUnite ® MSS network element can contain one or more nodes.
A maximum of 50 areas is supported in a subnetwork.
All nodes in an area must have the same area address.
All nodes in an area must have DCC or LAN connectivity within the area to all
other nodes in the same area.
At least one level-2 IS is required per area in area-divided DCNs for
communication accross area boundaries. Two level-2 ISs are recommended in each
area for DCC communications redundancy to/from each area.
All level-2 ISs must have DCC connectivity, either directly or indirectly via other
level-2 ISs, to all other level-2 ISs in the subnetwork to form a single level-2
subdomain that provides connectivity to all areas.
To distribute the load of management data in a subnetwork, it is recommended,
when feasible, but not required that:
– All area sizes be approximately the same.
– The number of level-2 ISs be about the same as the average area size.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
3-9
Issue 2, July 2008
See notice on first page
Management communication setup concepts
DCN
protocols and services
...................................................................................................................................................................................................................................
Overview
LambdaUnite ® MSS network elements support the exchange of management
information over DCC, OSI LAN or TCP/IP. The DCC and OSI LAN network
operations capabilities use the section DCC bytes in the SDH/SONET overhead of the
optical signals. WaveStar ® ITM-CIT dialogues and OS messages are transmitted in
these DCC bytes.
The LambdaUnite ® MSS OS interface is accessed through one of the rear panel LAN
connectors (10BASE-T or 100BASE-T). The LambdaUnite ® MSS interface supports
transaction language 1 (TL1) for commands/messages and file transfer and access
management (FTAM) for software downloads and provisionable data backup and
restore.
The LambdaUnite ® MSS OS interfaces supported include the following:
•
•
•
•
OSI LAN/WAN
TL1 TCP/IP (using the internal gateway function)
FTAM protocol for software download, database backup and restore.
FTP for software download, database backup and restore.
Standard 7-layer OSI stack
LambdaUnite ® MSS network elements support the exchange of management
information over the standard 7-layer OSI protocol stack over Local Area Networks
(LAN) and over Data Communication Channels (DCC) acc. to the Telcordia
Technologies (formerly Bellcore) GR-253 standard.
Protocols and services
The following figure shows how LambdaUnite ® MSS network elements support the
OSI protocols and services.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
3-10
Management communication setup concepts
DCN protocols and services
0x5353 S-SEL
0x5454 T-SEL
LAPD (AITS/UITS)
10/100 Base-TX / IEEE 802.3 MAC
FTAM
File Transfer, Access and Management (FTAM), defined by ISO 8571, is an
Application Service Element (ASE). FTAM facilitates file transfer and allows file
manipulation across a network. The FTAM protocol is used for LambdaUnite ® MSS
software management purposes, such as software download, backup or restoration.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
3-11
Issue 2, July 2008
See notice on first page
Management communication setup concepts
NSAP
address structure
...................................................................................................................................................................................................................................
NE addressing
A LambdaUnite ® MSS NE that runs OSI has at least one node, which is referred to as
node1. Additional nodes can be added, with a subset of the functionality of node1.
When a node acts as an intermediate system (all nodes), SEL is 0, implying that we
are concerned with the network entity title (NET) alone. When a node acts as an end
system (node1), which is where the network services are provided, SEL is not 0,
implying we are concerned with the NSAPs.
A node is known by its unique NET. If it provides multiple services, then each service
has a unique access point, the NSAP (NSAP = NET + SEL). One NSAP differs from
the other only in the SEL value.
In TL1 messages toward the user interfaces, the NSAP for TL1 management via node1
will be presented. For the other nodes, the NET is used.
Background
The following three NSAP structures can be distinguished:
•
•
•
ISO DCC NSAP address format (fixed 20-byte address structure). This format is
used by most Lucent Technologies network element types in the network.
Local Lucent Technologies NSAP address format (fixed 10-byte address structure).
This format is also used by a number of Lucent Technologies network element
types.
Flexible NSAP address structure. An alternative to the previous two formats.
Although different NSAP address formats exist, preferably all nodes in a network
should use the same address format.
LambdaUnite ® MSS supports the ISO DCC NSAP address format (fixed 20-byte
address structure).
Fixed 20-byte address structure
The fixed 20-byte address structure (ISO DCC NSAP address format, in accordance
with ISO 8348) is shown in the following figure:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
3-12
Management communication setup concepts
1 Byte
2 Bytes
1 Byte
AFI IDI(+pad) DFI
NSAP address structure
3 Bytes
2 Bytes
2 Bytes
2 Bytes
6 Bytes
1 Byte
Organization/
Operator
Spare
RD
Area
System ID
SEL
IDP
DSP
20 Bytes
Address fields
The meaning of the NSAP address fields is described in the following table:
Field
Meaning
Description
Initial domain part (IDP):
AFI
Authority and format identifier specifying the
NSAP address format.
The predefined value is 0x39 (hex.), indicating that
the ISO Data Country Code (ISO-DCC) is the
address format.
IDI
Initial domain identifier specifying the country
code. The designation “IDI+pad” indicates that the
field is padded to its maximum length
The predefined value is 0x0000 (hex.).
Domain specific part (DSP):
DFI
DSP format identifier specifying the DSP format.
The predefined value is 0x80 (hex.).
Operator
Organization or operator identifier representing the
network service provider (NSP).
The predefined value is 0x000000 (hex.).
Spare
Reserved portion of the NSAP.
The predefined value is 0x0000 (hex.).
RD
Routing domain.
The predefined value is 0x0000 (hex.).
Area
Area identifier indicating the routing area to which
a node belongs.
The predefined value is 0x0000 (hex.).
System ID
System identifier representing the node. The IEEE
802.3 MAC address.
A IEEE-MAC number is reserved and physically
stored on every NE.
SEL
Selector field used to direct the protocol data units
(PDU) to the correct destination.
The predefined value is 0x01 (hex.).
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
3-13
Issue 2, July 2008
See notice on first page
Management communication setup concepts
Data
communication channels (DCC)
...................................................................................................................................................................................................................................
Data communication channels (DCC)
The data communication channels (DCC) are part of the data communication network
(DCN). The channels are used to exchange management data between the management
system and the network elements. The channels are also used for communication
between the different network elements (for example remote logins). The DCC
connection is achieved by means of layer 2 protocol High Level Data Link Control
(HDLC) Frame bridging (at the data link layer level). HDLC Frame bridging always
applies to two ports (labelled TTP1 and TTP2); more than two ports (that is,
broadcasting) is not supported. The DCC connection is implemented via Layer
bridging.
DCC channel selection
The following DCC channels exist on an STM-n connection:
•
•
DCC bytes of the RSOH (bytes D1-D3) termed RS-DCC.
DCC bytes of the MSOH (bytes D4-D12) termed MS-DCC.
Transparent DCC cross-connections
The transparent DCC cross-connect feature allows to transparently pass-through certain
DCC channels which cannot or should not be processed by the system.
Transparent DCC cross-connections are to be used when there is a router on one side
of the SDH/SONET network which uses the DCC to transport some IP-based protocol
to a router on the other side of the network. This feature can be used to avoid
interworking with equipment from a different vendor in a common routing domain.
The transparent DCC cross-connection path is transparent. This means that no
processing at all will be done as the data travels along the path. Therefore, the entire
transparent DCC cross-connection path counts as a single hop for the network elements
at the ends of the path.
The transparent DCC cross-connections are completely independent from the
transmission cross-connections. There is no relation between the number of “normal”
(terminated) DCC channels and the number of transparent DCC channels. They are
taken from different pools.
Therefore, enabling a “normal” (terminated) DCC channel does not reduce the number
of available transparent DCC channels, and vice versa.
For each DCC channel, transparent DCC cross-connection and traditional DCC
processing on the CTL/DCF are mutually exclusive.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
3-14
Management communication setup concepts
Data communication channels (DCC)
Functional requirements
The following functional requirements to the transparent DCC channels:
•
•
The number of bidirectional transparent DCC channels is limited to 25.
It is possible to use transparent DCC cross-connections for RS-DCC and MS-DCC.
Establishing transparent DCC cross-connections
Transparent DCC cross-connections are to be established by identification of the two
ports of an NE that are to be cross-connected and the DCC type (RS-DCC or
MS-DCC).
LAPD protocol
The LAPD protocol, which controls communication between the network elements,
operates in either of the following modes:
•
•
Network side
The LAPD is assigned as network. This mode complies with the standards and
interoperates successfully with other LAPDs operating in user_side mode.
User side
The LAPD is assigned as user. This mode complies with the standards and
interoperates successfully with other LAPDs operating in network_side mode.
Please note that the DCCs work according to the master/slave principle, that is the
LAPD modes of two interconnected SDH ports must be set differently. A
corresponding “user-network side failure” alarm will be generated if the LAPD mode is
the same at both ends of a DCC.
AITS and UITS supported
LambdaUnite ® MSS network elements support the acknowledged information transfer
service (AITS) and the unacknowledged information transfer service (UITS) as the
basis for the LAPD or LinkID protocol with the UITS mode being the default mode of
operation. AITS should only be used if required by other NE types. UITS is
furthermore used for link protocol at the same time when AITS is chosen.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
3-15
Issue 2, July 2008
See notice on first page
Management communication setup concepts
Data communication channels (DCC)
AITS and UITS functional principles
In the LAPD protocol, all PDUs are sent with a checksum to verify that the data has
not been corrupted during the transmission over the DCC link. If a PDU is received
with a bad checksum, it is not acknowledged and will be resent:
•
•
In the unacknowledged information transfer service (UITS) (default), corrupted
PDUs are ignored and no further actions taken. Upper layers of the OSI stack are
responsible for recovery actions.
In the acknowledged information transfer service (AITS), PDUs are numbered and
transmitted sequentially, and acknowledgement PDUs are sent back from the
receiver to the sender. If a PDU is lost, that is, if the sender gets no
acknowledgement, the PDU is retransmitted.
Functional principle of the AITS
PDU 3 corrupted
Node A
3
Ack. 1
retransmission of
2
1
Node B
Ack. 2
no Ack. 3 !
3
Ack. 3
DCC over 1+1 MSP protected interfaces
To support DCC communication over 1+1 MSP protected STM-n links, two modes of
operation are defined, which can be selected independently for RS-DCC and MS-DCC
1. MSP DCC Independent Mode
In this mode the DCC channels over the working and protection STM-n interface
operate independently from the MSP protocol and can individually be
enabled/disabled. DCC protection is performed at the IS-IS protocol level.
2. MSP DCC Slave Mode
In this case the DCC information in the transmit direction is bridged over both the
working and the protection part of the MSP connection. At the receive end the
DCC is retrieved from the service (= active) part.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
3-16
Management communication setup concepts
LAN
access
...................................................................................................................................................................................................................................
Overview
4 LAN ports with automatic 10/100BASE-T selection are supported. All LANs have an
own MAC address. No hub is supported in HW on the CTL/DCF.
The 4 LAN ports are available as follows:
1. LAN1: Internally connected via the CIP [8] to the CTL/DCF. Accessible on User
Panel (UPL), intended for CIT access.
2. LAN2: Internally connected via the CIP to the CTL/DCF. Accessible on LAN
I/O-Panel at the rear, intended for EMS access.
3. LAN3: Internally connected via the CIP to the CTL/DCF. Accessible on LAN
I/O-Panel at the rear, reserved for future applications (e.g. SNN, or as backup port
for an EMS).
4. LAN4: This LAN interface is HW-prepared only. There is no protocol definition
available yet.
TARP LAN storm suppression (TLSS)
TARP LAN storm suppression (TLSS) works by using enhanced propagation rules for
TARP PDUs of types 1, 2 and 4, for either level-1 or level-2 IS routers. For LANs, the
enhanced propagation rules result in significantly fewer TARP/CLNP messages. If N is
the number of network elements on the LAN, then the number of messages launched
for each propagated query (type 1 or 2 message) or autonomous notification (type 4
message) would be of order N instead of order N*N.
Network elements that implement TLSS can co-exist with network elements that do not
implement TLSS. The performance improvement will of course be less when there are
network elements present that do not implement TLSS.
LAN connectors
The RJ-45 LAN connectors are located on the User Panel (connector labelled “CIT
(LAN)”) and on the LAN I/O-Panel at the rear (connector labelled “LAN 2”).
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
3-17
Issue 2, July 2008
See notice on first page
Management communication setup concepts
Name-to-address
translation
...................................................................................................................................................................................................................................
Overview
The communication between LambdaUnite ® MSS network elements and their
management systems, such as the WaveStar ® ITM-CIT, is established by using TL1
command messages.
A TL1 message addresses a network element by its “name”, also referred to as its
target identifier (TID), whereas nodes within an OSI network are identified by their
NSAP address. Hence a name-to-address translation becomes necessary.
TID to NSAP-address translation
LambdaUnite ® MSS offers two possible ways to accomplish the TID to NSAP-address
translation:
1. A static routing table
2. The TID address resolution protocol (TARP).
To establish a management association to a remote NE, the WaveStar ® ITM-CIT first
evaluates the static routing table. If the corresponding name/address pair cannot be
found in the table, the TARP will automatically be used.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
3-18
Management communication setup concepts
OMS-to-NE
connections concepts
...................................................................................................................................................................................................................................
Definition: OMS-to-NE connection
An OMS-to-NE connection is the communications connection between the
management system and an NE. This connection is established when the NE is added
to the management system. OMS-to-NE connections exist only in the management
system; the addition of an OMS-to-NE connection has no influence on an NE.
Functionality description
The management system is used to establish and manage OMS-to-NE connections. An
OMS-to-NE connection is established when an NE is added to the management system.
When an OMS-to-NE connection is established, the communications interface that will
be used for communication from the NE to the management system is selected.
In a High Availability configuration, if any NE is manually added to the primary
management system using the management system’s graphical user interface, in the
same way, the NE must also be manually added to the secondary management system.
Similarly, any NE that is auto-discovered by the primary management system will be
auto-discovered by the secondary management system.
Preconditions
A minimum subset of provisioning must be done before NEs can be added to the
management system The craft interface terminal (WaveStar ® ITM-CIT) must be used
to provision certain information when the NE is set up.
Consult the LambdaUnite ® MSS User Operations Guide for instructions on how to
provision an NE so it is ready to be managed by a management system such as Lucent
OMS.
For LambdaUnite ® MSS NEs that use OSI communications, the NSAP address of the
management system must be added to the access list of the NE so the NE can
communicate with the management system.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
3-19
Issue 2, July 2008
See notice on first page
Management communication setup concepts
OMS-to-NE connections concepts
Supported communications interfaces
LambdaUnite ® MSS supports the following types of communications interfaces:
•
•
•
OSI: Communication occurs via a direct connection between the management
system and each of the NEs.
TCP/IP GNE: The management system communicates with a subnetwork of NEs
through one NE that has been designated as the gateway. An NE using a
communications interface of TCP/IP GNE has been designated as the gateway NE
(GNE), which means it is the gateway for communications between the
management system and the other NEs in a network communications group. The
GNE is used by the management system to communicate with all NEs in a network
communications group.
TCP/IP RNE: The management system communicates with a subnetwork of NEs
through one NE that has been designated as the gateway. An NE using a
communications interface of TCP/IP RNE is has been designated as a remote NE
(RNE), which means it is not the gateway for communications with the subnetwork.
An RNE is an NE in a network communications group that the management system
accesses through a GNE.
The management system communicates with a GNE using TCP/IP, while the managed
NEs in a network communications group communicate with each other using OSI.
FTP/FTAM gateway
An FTP/FTAM gateway converts FTP, which is the file transfer protocol used in
TCP/IP networks, to FTAM, which is the file transfer protocol used in OSI networks.
Every RNE and GNE must have an FTP/FTAM gateway defined because the following
features of the management system utilize file transfer protocol:
•
•
•
Backup NE database version
Restore NE database version
Download from Management System to NE
If it is not done already, the user must, either via the WaveStar ® ITM-CIT or the
management system NE Management Functions page, provision the NE selected as
the FTP/FTAM gateway to serve that role before any file transfer activity is attempted.
File transfer attempts will fail if the NE is not enabled for that role.
When adding a NE to the management system, the user must specify the FTP/FTAM
gateway designations. If the NE is automatically discovered without the FTP/FTAM
gateway designations, the operator can establish the designations afterwards.
Reference
For more detailed explanations related to the concepts of OMS-to-NE connections,
refer to the Lucent OMS Network Element Management Guide.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
3-20
Management communication setup concepts
Orderwire
and user bytes
...................................................................................................................................................................................................................................
Introduction
Each LambdaUnite ® MSS network element provides six user byte interfaces which can
be used to access certain overhead bytes of an SDH/SONET transport signal. If
desired, an external orderwire equipment can be connected to these interfaces for
example.
User bytes can be provisioned by associating or disassociating an SDH/SONET port
with a user byte interface.
Important! Orderwire and user byte access is supported by 155-Mbps and 10-Gbps
port units (EP155, OP155, OP10) only.
Overhead bytes
Each SDH/SONET port supports three dedicated user bytes:
•
•
•
The E1 byte in the SDH regenerator section overhead (RSOH) or SONET section
overhead (SOH), respectively, can be used as a 64-kbps orderwire channel.
The E2 byte in the SDH multiplex section overhead (MSOH) or SONET line
overhead (LOH), respectively, can be used as a 64-kbps orderwire channel.
The F1 byte in the SDH regenerator section overhead (RSOH) or SONET section
overhead (SOH), respectively, can be used as a 64-kbps user data channel.
Each shelf provides user-provisionable access to up to six of these bytes from among
the provisioned SDH/SONET ports in the shelf.
User byte interfaces
The six user byte interfaces are available on the CI-CTL (connection interface of the
controller; accessible from the rear side of the shelf).
There are four universal interfaces which can be used as G.703 co-directional or V.11
contra-directional interfaces. Two interfaces can be used as V.11 only.
These interfaces can be used as G.703 or V.11 interfaces:
•
•
•
•
User
User
User
User
byte
byte
byte
byte
interface
interface
interface
interface
#1
#2
#3
#4
(USERBIO1)
(USERBIO2)
(USERBIO3)
(USERBIO4)
These interfaces can only be used as V.11 interfaces:
•
•
User byte interface #5 (USERBIO5)
User byte interface #6 (USERBIO6)
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
3-21
Issue 2, July 2008
See notice on first page
Management communication setup concepts
Orderwire and user bytes
Pin assignment
The pin assignment of the user byte interfaces is described in the LambdaUnite ® MSS
Installation Guide.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
3-22
4
4 anagement communication
M
setup tasks
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter informs about how to perform the most common tasks related to
management communication setup and to system provisioning.
Contents
Tasks related to OMS-to-NE connections
4-3
To view a list of OMS-to-NE connections
4-3
To add an OMS-to-NE connection
4-4
To modify an OMS-to-NE connection
4-9
To deactivate an OMS-to-NE connection
4-13
To activate an OMS-to-NE connection
4-15
To delete an OMS-to-NE connection
4-17
To delete an NE
4-19
To display the communication state of an NE
4-21
Tasks related to DCC
4-23
To retrieve DCC related parameters
4-23
To modify DCC related parameters
4-26
To retrieve DCC/EOW status information for a port
4-28
To modify DCC/EOW status information for a port
4-30
To view a list of transparent DCC cross-connections
4-32
To add a transparent DCC cross-connection
4-34
To delete a transparent DCC cross-connection
4-36
Tasks related to system provisioning
4-38
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
4-1
Issue 2, July 2008
See notice on first page
Management communication setup tasks
Overview
To view NE date and time
4-38
To modify NE date and time
4-40
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
4-2
Management communication setup tasks
Tasks related to OMS-to-NE connections
To
view a list of OMS-to-NE connections
...................................................................................................................................................................................................................................
When to use
Use this task to view a list of OMS-to-NE connections.
Task
...................................................................................................................................................................................................
1
Use the object links to follow this path: Management Network → OMS to NE Connections.
Result: The Search section of the OMS to NE Connections page is displayed.
...................................................................................................................................................................................................
2
Make selections in one or more of the following fields in the Search section of the
window:
•
•
•
•
In the NE type field, select a type of NE.
In the NE name(s) field, the Available table contains all NEs of the selected NE
type available on the management system. The Selected table contains the NEs
that are to be considered in the search. Click an NE and use the arrow buttons to
move one or more NEs from the Available table to the Selected table, or click the
double arrows to move all the NEs to the Available table.
In the Comm type field, select a type of communication interface between the NE
and the management system.
In the Net Comm Group field select the NCG name from the drop-down list. The
NCG names displayed depend on the selection in the Comm type field.
...................................................................................................................................................................................................
3
Click Search.
Result: The list at the bottom of the OMS to NE Connections page is populated
with a list of the OMS-to-NE connections in the network that meet your search
criteria.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
4-3
Issue 2, July 2008
See notice on first page
Management communication setup tasks
To
add an OMS-to-NE connection
...................................................................................................................................................................................................................................
When to use
Use this task to add an NE and establish an OMS-to-NE connection between the
management system and the new NE.
Important! Indirectly managed NEs cannot be added using this task.
Before you begin
Gather the following information about the NE to be added:
•
•
•
•
•
NE name
NE type (here: LambdaUnite ® MSS)
Communications type (here: OSI or TCP/IP)
Network communications group to which the NE will be assigned; ensure that it
exists
NSAP information or IP address of the NE, respectively
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
•
Use the object links to follow this path: Network. The Network Map is displayed.
Click on the New tool in the toolbar and select Network element from the
drop-down list.
Use the object links to follow this path: Network Elements. Click on the New tool
in the toolbar.
Use the object links to follow this path: Management Network → OMS-to-NE
connections. Click on the New tool in the Search section of the window.
Result: The Add OMS-to-NE connection page is displayed.
...................................................................................................................................................................................................
2
In the NE name field, enter a name that will be used by the management system to
identify this NE. This field accepts a maximum of 20 characters. Use the target
identifier (TID) of the NE, which was provisioned during installation of the NE as NE
name. See the Lucent OMS Getting Started Guide for a list of allowable characters.
...................................................................................................................................................................................................
3
In the NE type field, select LambdaUnite ® MSS.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
4-4
Management communication setup tasks
To add an OMS-to-NE connection
...................................................................................................................................................................................................
4
In the Comm type field, select on of the following
•
•
•
OSI – the NE in question communicates via the OSI interface
TCP/IP GNE – the NE in question communicates via the TCP/IP interface and acts
as gateway NE for a subnetwork
TCP/IP RNE – the NE in question communicates via the TCP/IP interface and acts
as a remote NE. That means the NE is not the gateway for communications with
the subnetwork.
...................................................................................................................................................................................................
5
Move to the OMS-to-NE connections details panel by clicking the number 2 in the
navigation aid or click Next.
Result: The OMS-to-NE connections details panel is displayed.
...................................................................................................................................................................................................
6
If you add{
then{
an OSI NE
go to Step 7.
a TCP/IP GNE
go to Step 8.
a TCP/IP RNE
go to Step 9.
...................................................................................................................................................................................................
7
Set the fields of the OMS-to-NE connections details panel as required:
•
•
Net Comm Grp – select the network communications group to which the
OMS-to-NE connection belongs from the drop-down list.
NSAP address – enter the NSAP address details of the NE in the following text
fields:
– AFI – the authority and format identifier specifying the NSAP address format (1
hexadecimal digit). The predefined value is 0x39 (hex.), indicating that the ISO
Data Country Code (ISO-DCC) is the address format.
– IDI+pad – the initial domain identifier specifying the country code, padded to
its maximum length (2 hexadecimal digits).
– DFI – the DSP format identifier specifying the DSP format (2 hexadecimal
digits).
– Operator ID – the operator or organization identifier representing the network
service provider (NSP) (3 hexadecimal digits).
– RD – the routing domain (2 hexadecimal digits).
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
4-5
Issue 2, July 2008
See notice on first page
Management communication setup tasks
To add an OMS-to-NE connection
–
Area – the area identifier indicating the routing area to which a node belongs
–
(4 hexadecimal digits).
System ID – the system identifier representing the node. The IEEE 802.3 MAC
address (12 hexadecimal digits).
Continue with Step 10.
...................................................................................................................................................................................................
8
Set the fields of the OMS-to-NE connections details panel as required:
•
•
•
•
Net Comm Grp – select the network communications group to which the
OMS-to-NE connection belongs from the drop-down list.
Primary IP address – enter the four fields of the network element’s IP address.
Secondary GNE – optionally select a secondary GNE to connect through from the
list of all GNEs in the network communications group provided.
FTP/FTAM gateway – select one of the following options:
– This NE does not use a FTP/FTAM gateway
– This NE is a FTP/FTAM gateway. If this option is selected, provide the
controller #1 NSAP address.
– This NE uses the following FTP/FTAM gateway. If this option is selected,
choose one of the FTP/FTAM gateway NEs from the drop-down list provided.
Continue with Step 10.
...................................................................................................................................................................................................
9
Set the fields of the OMS-to-NE connections details panel as required:
•
•
•
•
Net Comm Grp – select the network communications group to which the
OMS-to-NE connection belongs from the drop-down list.
Primary GNE – select the primary GNE to connect through from the list of all
GNEs in the network communications group provided.
Secondary GNE – optionally select a secondary GNE to connect through from the
list of all GNEs in the network communications group provided.
FTP/FTAM gateway – select one of the following options:
– This NE does not use a FTP/FTAM gateway
– This NE uses the following FTP/FTAM gateway. If this option is selected,
choose one of the FTP/FTAM gateway NEs from the drop-down list provided.
...................................................................................................................................................................................................
10
Click Next.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
4-6
Management communication setup tasks
To add an OMS-to-NE connection
Result: The OMS to NE connections security information panel is displayed.
...................................................................................................................................................................................................
11
Set the fields of the OMS-to-NE security information panel as required:
•
•
•
•
•
•
NE primary login – enter the primary login (user) of the NE for establishing
association. This must be a valid login ID in the NE.
NE primary password – enter the primary password of the NE for establishing
association.
Retype NE primary password – reenter the primary password of the NE.
NE secondary login – optionally enter the secondary login (user) of the NE for
establishing association. This must be a valid login ID in the NE.
NE secondary password – optionally enter the secondary password of the NE for
establishing association.
Retype NE secondary password – optionally reenter the secondary password of
the NE.
Click Next.
Result: The OMS-to-NE connection summary panel is displayed.
...................................................................................................................................................................................................
12
Review the summary for this OMS-to-NE connection.
Do one of the following:
•
•
If you wish to return to a panel to change a selection, either click the panel number
on the navigation aid, or click Edit for that panel, or click the hyperlink for that
panel. Change the appropriate information, and then return to this step.
If the selections are all correct, click Submit to complete the addition of the
OMS-to-NE connection.
Result: A confirmation is issued in the Message section of the OMS-to-NE
connection summary page, the NE is added to the management system and a
communications connection is established between the management system and the
new NE.
The addition of an NE to the management system initiates a full database
synchronization. The NE is automatically added to the Network Map. The NE is
added to the remaining pages of the management system after a refresh is executed.
If the OMS-to-NE connection being added is a GNE, a message is displayed: “The
system will be unable to perform most management functions until the full
database synchronization with the NE is completed. Do you want to activate the
automatic database synchronization after the NE is added?”. The user can choose
“Yes” or “No”. If the user chooses “Yes”, the system initiates a full database
synchronization after the OMS-to-NE connection is successfully added. If the user
chooses “No”, the system does not initiate a full database synchronization after the
OMS-to-NE connection is successfully added.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
4-7
Issue 2, July 2008
See notice on first page
Management communication setup tasks
To add an OMS-to-NE connection
Initially, the color of the NE icon will be magenta, which indicates a loss of
communications. Once the NE addition is complete, the color of the NE icon will
change to green, indicating normal status, or another color that indicates the
presence of an alarm.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
4-8
Management communication setup tasks
To
modify an OMS-to-NE connection
...................................................................................................................................................................................................................................
When to use
Use this task to modify an OMS-to-NE connection.
Important! Changing OMS-to-NE connection details may result in a loss of
association. Incorrect values for the parameters may result in the NE becoming
unmanageable.
Task
...................................................................................................................................................................................................
1
Use the object links to follow this path: Management Network → OMS-to-NE
Connections.
Result: The Search section of the OMS-to-NE Connections page is displayed.
...................................................................................................................................................................................................
2
Make selections in one or more of the following fields in the Search section of the
window:
•
•
•
•
In the NE type field, select a type of NE.
In the NE name(s) field, the Available table contains all NEs of the selected NE
type available on the management system. The Selected table contains the NEs
that are to be considered in the search. Click an NE and use the arrow buttons to
move one or more NEs from the Available table to the Selected table, or click the
double arrows to move all the NEs to the Available table.
In the Comm Type field, select a type of communication interface between the NE
and the management system.
In the Net Comm Grp field select the NCG name from the drop-down list. The
NCG names displayed depend on the selection in the Comm Type field.
...................................................................................................................................................................................................
3
Click Search.
Result: The list at the bottom of the OMS-to-NE Connections page is populated
with a list of the OMS-to-NE connections in the network that meet your search
criteria.
...................................................................................................................................................................................................
4
The NE name column of the table lists the names of the OMS-to-NE connections. The
name in this column is a hyperlink.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
4-9
Issue 2, July 2008
See notice on first page
Management communication setup tasks
To modify an OMS-to-NE connection
Do one of the following:
•
•
Click the name of the OMS-to-NE connection you wish to view.
Click the radio button next to the OMS-to-NE connection you wish to modify.
From the Go menu, select Modify and click Go.
Result: The OMS-to-NE connections general information page is displayed.
...................................................................................................................................................................................................
5
On the OMS-to-NE connections general information panel, no modifications are
possible if you want to modify an OSI NE or a TCP/IP GNE.
If you want to modify a TCP/IP RNE to be a TCP/IP GNE, change the
Communications type.
...................................................................................................................................................................................................
6
Move to the OMS-to-NE connections details panel by clicking the number 2 in the
navigation aid or click Next.
Result: The OMS-to-NE connections details panel is displayed.
...................................................................................................................................................................................................
7
If you modify{
then{
an OSI NE
go to Step 8.
a TCP/IP GNE
go to Step 9.
a TCP/IP RNE
go to Step 10.
...................................................................................................................................................................................................
8
Set the fields of the OMS-to-NE connections details panel as required:
•
•
Net Comm Grp – select the network communications group to which the
OMS-to-NE connection belongs from the drop-down list.
NSAP address – enter the NSAP address details of the NE in the following text
fields:
– AFI – the authority and format identifier specifying the NSAP address format (1
hexadecimal digit). The predefined value is 0x39 (hex.), indicating that the ISO
Data Country Code (ISO-DCC) is the address format.
– IDI+pad – the initial domain identifier specifying the country code, padded to
its maximum length (2 hexadecimal digits).
– DFI – the DSP format identifier specifying the DSP format (2 hexadecimal
digits).
– Operator ID – the operator or organization identifier representing the network
service provider (NSP) (3 hexadecimal digits).
– RD – the routing domain (2 hexadecimal digits).
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
4-10
Management communication setup tasks
To modify an OMS-to-NE connection
–
Area – the area identifier indicating the routing area to which a node belongs
–
(4 hexadecimal digits).
System ID – the system identifier representing the node. The IEEE 802.3 MAC
address (12 hexadecimal digits).
Continue with Step 11.
...................................................................................................................................................................................................
9
Set the fields of the OMS-to-NE connections details panel as required:
•
•
•
•
Net Comm Grp – select the network communications group to which the
OMS-to-NE connection belongs from the drop-down list.
Primary IP address – enter the four fields of the network element’s IP address.
Secondary GNE – optionally select a secondary GNE to connect through from the
list of all GNEs in the network communications group provided.
FTP/FTAM gateway – select one of the following options:
– This NE does not use a FTP/FTAM gateway
– This NE is a FTP/FTAM gateway. If this option is selected, provide the
controller #1 NSAP address.
– This NE uses the following FTP/FTAM gateway. If this option is selected,
choose one of the FTP/FTAM gateway NEs from the drop-down list provided.
Continue with Step 11.
...................................................................................................................................................................................................
10
Set the fields of the OMS-to-NE connections details panel as required:
•
•
•
•
Net Comm Grp – select the network communications group to which the
OMS-to-NE connection belongs from the drop-down list.
Primary GNE – select the primary GNE to connect through from the list of all
GNEs in the network communications group provided.
Secondary GNE – optionally select a secondary GNE to connect through from the
list of all GNEs in the network communications group provided.
FTP/FTAM gateway – select one of the following options:
– This NE does not use a FTP/FTAM gateway
– This NE uses the following FTP/FTAM gateway. If this option is selected,
choose one of the FTP/FTAM gateway NEs from the drop-down list provided.
...................................................................................................................................................................................................
11
Click Next.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
4-11
Issue 2, July 2008
See notice on first page
Management communication setup tasks
To modify an OMS-to-NE connection
Result: The OMS to NE connections security information panel is displayed.
...................................................................................................................................................................................................
12
Set the fields of the OMS-to-NE security information panel as required:
•
•
•
•
•
•
NE primary login – enter the primary login (user) of the NE for establishing
association. This must be a valid login ID in the NE.
NE primary password – enter the primary password of the NE for establishing
association.
Retype NE primary password – reenter the primary password of the NE.
NE secondary login – optionally enter the secondary login (user) of the NE for
establishing association. This must be a valid login ID in the NE.
NE secondary password – optionally enter the secondary password of the NE for
establishing association.
Retype NE secondary password – optionally reenter the secondary password of
the NE.
Click Next.
Result: The OMS-to-NE connection summary panel is displayed.
...................................................................................................................................................................................................
13
Review the summary for this OMS-to-NE connection.
...................................................................................................................................................................................................
14
Do one of the following:
•
•
If you wish to return to a panel to change a selection, either click the panel number
on the navigation aid, or click Edit for that panel, or click the hyperlink for that
panel. Change the appropriate information, and then return to this step
If the selections are all correct, click Submit to complete the modification of the
OMS-to-NE connection.
Result: A confirmation is issued in the Message section of the OMS-to-NE
connection summary page, and the OMS-to-NE connection is modified.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
4-12
Management communication setup tasks
To
deactivate an OMS-to-NE connection
...................................................................................................................................................................................................................................
When to use
Use this task to deactivate the communications connection between the management
system and an NE. When you deactivate an OMS-to-NE connection, the NE is not
communicating with the management system.
Before you begin
In order to deactivate an OMS-to-NE connection, the NE communications status must
be either Up (the NE is communicating with the management system) or Down (the
NE is not communicating with the management system and the management system is
attempting to regain communications).
Task
...................................................................................................................................................................................................
1
Use the object links to follow this path: Management Network → OMS-to-NE
Connections.
Result: The Search section of the OMS-to-NE Connections page is displayed.
...................................................................................................................................................................................................
2
Make selections in one or more of the following fields in the Search section of the
window:
•
•
•
•
In the NE type field, select a type of NE.
In the NE name(s) field, the Available table contains all NEs of the selected NE
type available on the management system. The Selected table contains the NEs
that are to be considered in the search. Click an NE and use the arrow buttons to
move one or more NEs from the Available table to the Selected table, or click the
double arrows to move all the NEs to the Available table.
In the Comm Type field, select a type of communication interface between the NE
and the management system.
In the Net Comm Grp field select the NCG name from the drop-down list. The
NCG names displayed depend on the selection in the Comm Type field.
...................................................................................................................................................................................................
3
Click Search.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
4-13
Issue 2, July 2008
See notice on first page
Management communication setup tasks
To deactivate an OMS-to-NE connection
Result: The list at the bottom of the OMS-to-NE Connections page is populated
with a list of the OMS-to-NE connections in the network that meet your search
criteria.
...................................................................................................................................................................................................
4
The NE name column of the table lists the names of the OMS-to-NE connections.
Click the radio button next to the OMS-to-NE connection you wish to deactivate. From
the Go menu, select Deactivate and click Go.
Result: A confirmation is issued in the Message section of the OMS to NE
connections page, the management system logs out of the NE and sets the
communications status to Deactivated.
To update the OMS to NE connections page, click the refresh button.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
4-14
Management communication setup tasks
To
activate an OMS-to-NE connection
...................................................................................................................................................................................................................................
When to use
Use this task to activate the communications connection between the management
system and an NE. When you activate an OMS-to-NE connection, the NE is not
communicating with the management system.
Before you begin
In order to activate an OMS-to-NE connection, the NE communication status must be
Deactivated. The NE is not communicating with the management system because the
user manually deactivated the OMS-to-NE connection.
Task
...................................................................................................................................................................................................
1
Use the object links to follow this path: Management Network → OMS-to-NE
Connections.
Result: The Search section of the OMS-to-NE Connections page is displayed.
...................................................................................................................................................................................................
2
Make selections in one or more of the following fields in the Search section of the
window:
•
•
•
•
In the NE type field, select a type of NE.
In the NE name(s) field, the Available table contains all NEs of the selected NE
type available on the management system. The Selected table contains the NEs
that are to be considered in the search. Click an NE and use the arrow buttons to
move one or more NEs from the Available table to the Selected table, or click the
double arrows to move all the NEs to the Available table.
In the Comm Type field, select a type of communication interface between the NE
and the management system.
In the Net Comm Grp field select the NCG name from the drop-down list. The
NCG names displayed depend on the selection in the Comm Type field.
...................................................................................................................................................................................................
3
Click Search.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
4-15
Issue 2, July 2008
See notice on first page
Management communication setup tasks
To activate an OMS-to-NE connection
Result: The list at the bottom of the OMS-to-NE Connections page is populated
with a list of the OMS-to-NE connections in the network that meet your search
criteria.
...................................................................................................................................................................................................
4
The NE name column of the table lists the names of the OMS-to-NE connections.
Click the radio button next to the OMS-to-NE connection you wish to activate. From
the Go menu, select Activate and click Go.
Result: A confirmation is issued in the Message section of the OMS to NE
connections page, the management system connects to the NE and sets the
communications status to Activated.
To update the OMS to NE connections page, click the refresh button.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
4-16
Management communication setup tasks
To
delete an OMS-to-NE connection
...................................................................................................................................................................................................................................
When to use
Use this task to delete the communications connection between the management
system and an NE. When you delete an OMS-to-NE connection, its corresponding NE
is also deleted from the management system’s database.
Before you begin
An NE and its corresponding OMS-to-NE connection cannot be deleted in the
following situations:
1. When the NE is a GNE for a Network Communications Group, and it has RNEs
assigned to it
2. When the NE has cross-connections being used in network connections. For
information about how to delete a network connection, see the Lucent OMS
Connection Management Guide.
3. When the NE is being used as an FTP/FTAM gateway
4. When a database synchronization is in progress for that NE
5. When a software download is in progress for that NE
6. If the management system cannot delete the NE from the primary network adapter
7. When a backup or restore is in progress for that NE
Task
...................................................................................................................................................................................................
1
Use the object links to follow this path: Management Network → OMS-to-NE
Connections.
Result: The Search section of the OMS-to-NE Connections page is displayed.
...................................................................................................................................................................................................
2
Make selections in one or more of the following fields in the Search section of the
window:
•
•
In the NE type field, select a type of NE.
In the NE name(s) field, the Available table contains all NEs of the selected NE
type available on the management system. The Selected table contains the NEs
that are to be considered in the search. Click an NE and use the arrow buttons to
move one or more NEs from the Available table to the Selected table, or click the
double arrows to move all the NEs to the Available table.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
4-17
Issue 2, July 2008
See notice on first page
Management communication setup tasks
•
•
To delete an OMS-to-NE connection
In the Comm Type field, select a type of communication interface between the NE
and the management system.
In the Net Comm Grp field select the NCG name from the drop-down list. The
NCG names displayed depend on the selection in the Comm Type field.
...................................................................................................................................................................................................
3
Click Search.
Result: The list at the bottom of the OMS-to-NE Connections page is populated
with a list of the OMS-to-NE connections in the network that meet your search
criteria.
...................................................................................................................................................................................................
4
The NE name column of the table lists the names of the OMS-to-NE connections.
Click the radio button next to the OMS-to-NE connection you wish to delete. From the
Go menu, select Delete and click Go.
Result: A confirmation window is displayed.
...................................................................................................................................................................................................
5
Click Yes.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Network Elements page, and the OMS-to-NE connection is deleted.
The NE is automatically deleted from the Network Map. The NE is deleted from
the remaining pages of the management system after a refresh is executed.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
4-18
Management communication setup tasks
To
delete an NE
...................................................................................................................................................................................................................................
When to use
Use this task to delete an NE from the management system’s database. When you
delete an NE, its corresponding OMS-to-NE connection is also deleted.
There are two methods for this task.
Before you begin
An NE and its corresponding OMS-to-NE connection cannot be deleted in the
following situations:
1. When the NE is a GNE for a Network Communications Group, and it has RNEs
assigned to it
2. When the NE has cross-connections being used in network connections. For
information about how to delete a network connection, see the Lucent OMS
Connection Management Guide.
3. When the NE is being used as an FTP/FTAM gateway
4. When a database synchronization is in progress for that NE
5. When a software download is in progress for that NE
6. If the management system cannot delete the NE from the primary network adapter
7. When a backup or restore is in progress for that NE
Task, method 1: from the Network Elements page
...................................................................................................................................................................................................
1
Use the object links to follow this path: Network Elements.
Result: The Network Elements page is displayed. It includes a table that lists all
NEs.
...................................................................................................................................................................................................
2
The NE name column of the table lists the names of the NEs. Click the radio button
next to the NE you wish to delete. From the Go menu, select Delete and click Go.
Result: A confirmation window is displayed asking you to confirm the deletion.
...................................................................................................................................................................................................
3
Click OK.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
4-19
Issue 2, July 2008
See notice on first page
Management communication setup tasks
To delete an NE
Result: A progress indication followed by a confirmation is issued in the Message
section of the Network Elements page, and the NE is deleted.
If the management system finds that the NE to be deleted has cross-connections in
that NE that are being used in network connections, a failure notice is displayed.
E...................................................................................................................................................................................................
ND OF STEPS
Task, method 2: from the Network Map
...................................................................................................................................................................................................
1
On the Network Map, right-click the ODO_AREA and select Expand all, then
right-click the NE icon that represents the NE you wish to delete.
Result: The Node menu is displayed.
...................................................................................................................................................................................................
2
Select Delete.
Result: A confirmation window is displayed asking you to confirm the deletion.
...................................................................................................................................................................................................
3
Click OK.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Network Map page, and the NE is deleted.
If the management system finds that the NE to be deleted has cross-connections in
that NE that are being used in network connections, a failure notice is displayed.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
4-20
Management communication setup tasks
To
display the communication state of an NE
...................................................................................................................................................................................................................................
Procedure
...................................................................................................................................................................................................
1
Use the object link Network Elements.
Result: The Search for Network Elements page is displayed.
...................................................................................................................................................................................................
2
The Search for Network Elements page allows you to search for a specific network
element or a number of network element elements. Note that additional search fields
are displayed by selecting the More button.
Depending on the expected type of search result, use one or more of the following
fields to refine the search request:
•
•
•
•
•
•
NE name – this is a hyperlink to the Network Elements pop up window, from
which you may select an NE to include in your search. You can also enter the NE
name in the text box. The text box includes the use of “*” as wildcard.
NE type – select the type of NE from the drop down list.
Central office name – this is a hyperlink to the Central Offices pop up window,
from which you may select a central office to include in your search. You can also
enter the central office name in the text box. The text box includes the use of “*”
as wildcard.
Comms status – select the communications status of the NE from the drop down
box.
Activity state – select the activity state of the NE from the drop down box.
Last outage time – enter the time that the management system last experienced a
loss of communications with the NE. Manually enter a date followed by a time in
either the To or From text box or use the calendar function next to each text box to
choose the date and time information.
Click Search.
Result: The lower part of the page is populated with a list of network elements that
meet your search criteria.
...................................................................................................................................................................................................
3
Use the column Comms status to analyze the communication status of a network
element.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
4-21
Issue 2, July 2008
See notice on first page
Management communication setup tasks
To display the communication state of an NE
The possible values for communications status are described in the following table:
Communications status
Definition
Up
Communications with the NE are working.
Down
Loss of communications. The management system
continues to attempt to communicate with the NE.
Failed
Permanent loss of communications. The management
system has stopped attempting to communicate with
the NE.
Unknown
Communications status cannot be determined.
Deactivated
The NE is not communicating with the system
because the OMS to NE connection was manually
deactivated.
NA
Not Applicable. For Non-managed NEs and
Unmanageable Devices only.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
4-22
Management communication setup tasks
Tasks related to DCC
To
retrieve DCC related parameters
...................................................................................................................................................................................................................................
When to use
Use this task to view DCC related parameters for an NE.
Related information
For a more detailed explanation, please refer to the description of the RTRV-FECOM
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Data Communication Networks.
In the Function field, select Retrieve Far End OSI Communications.
Click Go.
Result: The Retrieve Far End OSI Communications page is displayed.
...................................................................................................................................................................................................
3
To limit the information output to a single port, enter the ID of the port in question in
the DCC port field. To retrieve information for all ports, leave the field empty.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
4-23
Issue 2, July 2008
See notice on first page
Management communication setup tasks
To retrieve DCC related parameters
To further restrict the information displayed, select a value in the following fields:
•
DCC type
–
•
Line: the information relates to the SDH multiplex section overhead (MSOH) or
the SONET line overhead (LOH), respectively.
– Section: the information relates to the SDH regenerator section overhead
(RSOH) or the SONET section overhead (SOH), respectively.
Network type – select either MCN (management communication network) or SCN
(signaling communications network).
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
...................................................................................................................................................................................................
5
The output parameters for this function are:
1. port – DCC port
This parameter indicates the port AID of a circuit pack which is used together with
dcctype to identify the DCC channel.
2. dcctype
This parameter indicates whether the LINE/MS or SECTION/RS DCC parameters
of the port are reported by the command.
3. dccprottp
This parameter reports the protection type of the DCC channel. 0X1 means the port
is not involved in a protection group or DCC protection switching is disabled. 1+1
means DCC protection switching is enabled: In these case only the active worker
line is shown.
4. dccstat
This parameter indicates whether management communication network (MCN)
communication over the DCC channel is enabled or if it is used in a transparent
DCC cross-connection.
5. lapdmode
This parameter indicates the type of LAPD service. Modes are AITS and UITS.
6. lapdrl
This parameter indicates the LAPD role. This parameter is also used to determine
the service for the LinkID protocol.
7. osinode
Assignment of a DCC channel to an MCN node in the NE. The parameter is
omitted when dccstat=ENABLE.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
4-24
Management communication setup tasks
To retrieve DCC related parameters
8. scn_dccstat
This parameter indicates whether the DCC channel is used for communication over
the signaling communications network (SCN) or is involved in a transparent DCC
cross-connection.
9. uni_dccstat
Indicates whether the DCC channel is used for UNI communication.
Type: Alphanumeric value set
Range: DISABLE (default), ENABLE, TRANSPARENT
Note: Output responses with uni_dccstat=DISABLE will only sent when either
dccstat=ENABLE or scn_dccstat=ENABLE.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
4-25
Issue 2, July 2008
See notice on first page
Management communication setup tasks
To
modify DCC related parameters
...................................................................................................................................................................................................................................
When to use
Use this task to modify DCC related parameters for an NE.
Related information
For a more detailed explanation, please refer to the description of the ENT-FECOM
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Data Communication Network.
In the Function field, select Enter Far End OSI Communications.
Click Go.
Result: The Enter Far End OSI Communications page is displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
Port – the port AID of a circuit pack which is used together with dcctype to
identify the DCC channel. You may copy the ID of the port from the Port page to
fill this field.
•
DCC type
–
–
Line: the modification relates to the DCC using the SDH multiplex section
overhead (MSOH) or the SONET line overhead (LOH) of the port, respectively
Section: the modification relates to the DCC using the SDH regenerator section
overhead (RSOH) or the SONET section overhead (SOH) of the port.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
4-26
Management communication setup tasks
•
•
•
•
•
•
To modify DCC related parameters
DCC stat – indicates whether communication over the DCC channel is enabled or
disabled. Select either Enable or Disable.
LAPD mode – indicates the type of LAPD service. Select either AITS
(acknowledged information transfer service) or UITS (unacknowledged information
transfer service).
LAPD role – indicates the LAPD role. Select either User side or Network side.
OSI node – assigns a DCC channel to a management communication network
(MCN) node in the NE. Possible values are:
– osinode1 (LAN1, 2, or 3)
– osinode2 (LAN2 or LAN3) to osinode8 (LAN2 or LAN3)
– scnnode (LAN2 or LAN3)
Unidirectional DCC over SCN – indicates whether the DCC channel is used for
communication over the signaling communications network (SCN). Select either
Enable or Disable.
Unidirectional DCC – indicates whether the DCC channel is used for UNI
communication. Select either Enable or Disable.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
4-27
Issue 2, July 2008
See notice on first page
Management communication setup tasks
To
retrieve DCC/EOW status information for a port
...................................................................................................................................................................................................................................
When to use
Use this task to retriev DCC/EOW status information for a single port or a number of
ports.
Related information
For a more detailed explanation, please refer to the description of the RTRV-OW
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Network Elements.
In the Function field, select Retrieve Orderwire and User Bytes.
Click Go.
Result: The Retrieve Orderwire and User Bytes page is displayed.
...................................................................................................................................................................................................
3
Use the field Access identifier to specify for which user byte the output is to be
retrieved. Possible values are 1-1-ubio1 to 1-1-ubio6 for the six user byte interfaces
which can be used to access certain overhead bytes of an SDH/SONET transport
signal. To retrieve information for all userbytes, use the value 1-1-ubioall.
...................................................................................................................................................................................................
4
Click Submit.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
4-28
Management communication setup tasks
To retrieve DCC/EOW status information for a port
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
...................................................................................................................................................................................................
5
The output parameters for this function are:
1. aid – access identifier
Indicates the overhead access port for which the following information is displayed.
2. intfctype – interface type
This parameter indicates which electrical interface standard of the overhead access
port is used.
• G703 – electrical interface according to G.703
• V11 – electrical interface according to V.11.
3. ohbyte – overhead byte
Indicates which of the overhead bytes is used:
• E1 and F1 in the SDH regenerator section overhead (RSOH) or the SONET
section overhead (SOH), respectively
• E2 in the SDH multiplex section overhead (MSOH) or the SONET line
overhead (LOH), respectively
4. portaid
Shows the optical port (of an OPn) with which the overhead access port (given by
the output parameter aid) is associated.
The value NOCONNECT is used to indicate that the port given by portaid is not
associated to the overhead access port given by the parameter aid.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
4-29
Issue 2, July 2008
See notice on first page
Management communication setup tasks
To
modify DCC/EOW status information for a port
...................................................................................................................................................................................................................................
When to use
Use this task to modify DCC/EOW status information for a port.
Related information
For a more detailed explanation, please refer to the description of the SET-OW
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Network Elements.
In the Function field, select Set Orderwire and User Bytes.
Click Go.
Result: The Set Orderwire and User Bytes page is displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
•
Access identifier – specify the overhead access port to be used for association (or
removing the association).
Type: UserBytePortAID.
Range: 1-1-ubio1 to 1-1-ubio6
Note: The value ubioall is not allowed.
Interface Type – specify the electrical interface according to either G.703 or V.11as
selectable.
Note: The overhead access ports ubio1 to ubio4 are configurable with both “G.703”
or “V.11”, ubio5 and ubio6 are fixed to “V.11”.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
4-30
Management communication setup tasks
•
To modify DCC/EOW status information for a port
Overhead-Byte – specifies which of the overhead bytes is used:
–
•
E1 and F1 in the SDH regenerator section overhead (RSOH) or the SONET
section overhead (SOH), respectively
– E2 in the SDH multiplex section overhead (MSOH) or the SONET line
overhead (LOH), respectively.
Port Identifier – specifies the optical/electrical port (of an OPn/EPn) of the
userbyte to which the overhead access port is associated. You may copy the ID of
the port in question from the Port page to fill the field.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
4-31
Issue 2, July 2008
See notice on first page
Management communication setup tasks
To
view a list of transparent DCC cross-connections
...................................................................................................................................................................................................................................
When to use
Use this task to view a list of transparent DCC cross-connections for a selected NE.
Related information
For a more detailed explanation, please refer to the description of the RTRV-CRS-FECOM
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Data Communication Network.
In the Function field, select Retrieve Transparent DCC Cross Connection.
Click Go.
Result: The Retrieve Transparent DCC Cross Connection page is displayed.
...................................................................................................................................................................................................
3
If you want to retrieve information related to a specific port of the NE, enter a port ID
in the DCC port field. To retrieve information for all ports of the NE, leave the field
empty.
If you want to restrict the information to a specific type of DCC cross-connection,
select the type (either Line or Section) in the DCC type field. To retrieve information
for all types of DCC cross-connections, leave the field empty.
...................................................................................................................................................................................................
4
Click Submit.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
4-32
Management communication setup tasks
To view a list of transparent DCC cross-connections
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
...................................................................................................................................................................................................
5
If a transparent DCC cross-connection exists the output parameters for this function
are:
1. port_aid1 – DCC port 1
This parameter indicates the first optical port AID of an OPn circuit pack which is
used together with dcctype to identify the DCC channel which is involved in a
transparent DCC cross-connection.
2. port_aid2 – DCC port 2
This parameter indicates the second optical port AID of an OPn circuit pack which
is used together with dcctype to identify the DCC channel which is involved in a
transparent DCC cross-connection.
3. dcctype
• LINE/MS: the information relates to the SDH multiplex section overhead
(MSOH) or the SONET line overhead (LOH), respectively.
• SECTION/RS: the information relates to the SDH regenerator section overhead
(RSOH) or the SONET section overhead (SOH), respectively.
otherwise only the completion report COMPLD returns.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
4-33
Issue 2, July 2008
See notice on first page
Management communication setup tasks
To
add a transparent DCC cross-connection
...................................................................................................................................................................................................................................
When to use
Use this task to add a transparent DCC cross-connection between two port overheads
in a selected NE.
Related information
For a more detailed explanation, please refer to the description of the ENT-CRS-FECOM
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Data Communication Networks.
In the Function field, select Enter Transparent DCC Cross Connection.
Click Go.
Result: The Enter Transparent DCC Cross Connection page is displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
•
DCC port 1 – indicates the first optical port AID of an OPn circuit pack which is
used together with dcctype to identify the DCC channel which is involved in a
transparent DCC cross-connection. You may copy the ID of the port in question
from the Port page to fill the field.
DCC port 2 – indicates the second optical port AID of an OPn circuit pack which
is used together with dcctype to identify the DCC channel which is involved in a
transparent DCC cross-connection. You may copy the ID of the port in question
from the Port page to fill the field.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
4-34
Management communication setup tasks
•
To add a transparent DCC cross-connection
DCC type
–
–
Line: the transparent DCC cross-connection is to be established via the SDH
multiplex section overhead (MSOH) or the SONET line overhead (LOH) of the
port, respectively.
Section: the transparent DCC cross-connection is to be established via the DCC
using the SDH regenerator section overhead (RSOH) or the SONET section
overhead (SOH) of the port, respectively.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
4-35
Issue 2, July 2008
See notice on first page
Management communication setup tasks
To
delete a transparent DCC cross-connection
...................................................................................................................................................................................................................................
When to use
Use this task to delete a transparent DCC cross-connection.
Related information
For a more detailed explanation, please refer to the description of the DLT-CRS-FECOM
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
To get information about the transparent DCC cross-connections in place, refer to task
“To view a list of transparent DCC cross-connections” (p. 4-32).
If you already have the necessary data, do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Data Communication Networks.
In the Function field, select Delete Transparent DCC Cross Connection.
Click Go.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
4-36
Management communication setup tasks
To delete a transparent DCC cross-connection
Result: The Delete Transparent DCC Cross Connection page is displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
DCC port 1 – indicates the first optical port AID of an OPn circuit pack which is
•
used together with dcctype to identify the DCC channel which is involved in a
transparent DCC cross-connection. You may copy the ID of the port in question
from the Port page to fill the field.
DCC port 2 – indicates the second optical port AID of an OPn circuit pack which
is used together with dcctype to identify the DCC channel which is involved in a
transparent DCC cross-connection. You may copy the ID of the port in question
from the Port page to fill the field.
•
DCC type
–
–
Line: the DCC cross-connection has been established via the DCC using the
SDH multiplex section overhead (MSOH) or the SONET line overhead (LOH)
of the port, respectively.
Section: the DCC cross-connection has been established via the SDH
regenerator section overhead (RSOH) or the SONET section overhead (SOH) of
the port, respectively.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
4-37
Issue 2, July 2008
See notice on first page
Management communication setup tasks
Tasks related to system provisioning
To
view NE date and time
...................................................................................................................................................................................................................................
When to use
Use this task to view the NE date and time.
Related information
For a more detailed explanation, please refer to the description of the RTRV-HDR
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Network Elements.
In the Function field, select Retrieve Header.
Click Go.
Result: The Retrieve Header page is displayed.
...................................................................................................................................................................................................
3
Click Submit.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
4-38
Management communication setup tasks
To view NE date and time
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function. The response includes the current date and time.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
4-39
Issue 2, July 2008
See notice on first page
Management communication setup tasks
To
modify NE date and time
...................................................................................................................................................................................................................................
When to use
Use this task to modify the NE date and time. Note that when the date is changed in a
way that a performance monitoring period is crossed, than one history bin will be lost.
Related information
For a more detailed explanation, please refer to the description of the ED-DAT
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Network Elements.
In the Function field, select Edit Date and Time.
Click Go.
Result: The Edit Date and Time page is displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
•
Date – specifies the current date as YY-MM-DD. If the parameter time is not
specified, the current value is not changed, but then date must be specified.
Range: YY-MM-DD, with YY between 00 and 99, MM between 01 and 12, DD
between 01 and 31.
Time – specifies the current time of day as HH-MM-SS. If the parameter date is
not specified, the current value is not changed, but then time must be specified.
Range: HH-MM-SS, with HH between 00 and 23, MM between 00 and 59, SS
between 00 and 59.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
4-40
Management communication setup tasks
To modify NE date and time
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function. Note that the response does not show the modified date and
time.
...................................................................................................................................................................................................
5
To verify that date and time meet are correct, follow the instructions in “To view NE
date and time” (p. 4-38).
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
4-41
Issue 2, July 2008
See notice on first page
5
5 quipment provisioning
E
concepts
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter presents concept information related to equipment provisioning on
LambdaUnite ® MSS network elements using Lucent OMS.
Contents
System configurations
5-2
Network element configurations
5-2
Pluggable optical interface modules
5-12
Overview of replaceable units
5-19
NE hardware components and their identifiers
5-26
Port types
5-27
Miscellaneous discrete inputs and outputs
5-31
Equipment protection
5-33
CTL equipment protection (duplex control)
5-33
XC equipment protection
5-38
STM-1E equipment protection
5-41
DS3/EC-1 equipment protection
5-48
LOXC equipment protection
5-56
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-1
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
System configurations
Network
element configurations
...................................................................................................................................................................................................................................
Supported LXC configurations
These LXC configurations are supported:
•
•
•
•
LXC
LXC
LXC
LXC
with a max. switching capacity of 160 Gbps
with a max. switching capacity of 320 Gbps
with a max. switching capacity of 640 Gbps
supporting ONNS applications
All these configurations can be realized by using a dual unit row (DUR) shelf.
DUR shelf
A DUR shelf can be equipped from the front as well as from the rear side.
A DUR shelf is designed such that optical interfaces can be accessed from the front
while electrical interfaces can be accessed from the rear side.
Available slots on the front side
The following illustration shows the available circuit pack slots on the front side of a
DUR shelf.
User panel
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
XC (P) slot
Universal slot
XC (W) slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
1
2
3
4
5
6
7
8
9
10 11 12 13 14 15 16 17 18 19
CTL (W) slot
Universal slot
Universal slot
31 32 33 34 35 36 37 38 39
Universal slot
21 22 23 24 25 26 27 28
Universal slot
CTL (P) slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
40
front view
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-2
Equipment provisioning concepts
Network element configurations
A DUR shelf provides the following circuit pack slots on the front side:
•
•
•
•
2 dedicated slots for CTL (slots 11 and 31, “W” = worker, “P” = protection).
2 dedicated slots for XC cross-connection and timing units (slots 9 and 10, “W” =
worker, “P” = protection).
32 “universal slots” for port units (slots 1-8, 12-19, 21-28, and 32-39).
1 dedicated slot for the user panel (slot 40).
Slots
1{8
Slot equipage
Universal slots1
12{19
Universal slots can be used for any mix of port units:2
•
Electrical DS3 (45 Mbps, plesiochronous) or EC-1 (51 Mbps, synchronous) port
units (EP51{) 3
For the EP51 port units, there are dedicated slots for the electrical connection
interfaces (ECI) on the rear side of the shelf.
•
Electrical 155-Mbps (STM-1E) port units (EP155{) 3
For the EP155 port units, there are dedicated slots for the electrical connection
interfaces (ECI) on the rear side of the shelf.
21{28
32{39
•
Optical 155-Mbps port units (OP155{)
•
622-Mbps port units (OP622{)
•
2.5-Gbps port units (OP2G5{)
•
•
10-Gbps port units (OP10{)
40-Gbps port units (OP40{)
An OP40 port unit occupies four universal slots.
•
1-Gigabit Ethernet interface (GE1)
•
10-Gigabit Ethernet WANPHY interface (realized on an OP10 port unit)
Lower order cross-connection units (LOXC):
The slots 4, 17, 18, 19, 37, and 39 can be used for lower order cross-connection
units, depending on the maximum switching capacity of the system and the type of
LOXC.
9
XC (W) slot
Cross-connection and timing unit (XC) – worker (W).4
This XC is paired with the XC in the protection slot in a 1+1 non-revertive
protection mode configuration. Furthermore, the XC contains the timing generator
function for the NE.
10
XC (P) slot
Cross-connection and timing unit (XC) – protection (P).4
This XC is paired with the XC in the worker slot in a 1+1 non-revertive protection
mode configuration. Furthermore, the XC contains the timing generator function for
the NE.
11
CTL (W) slot
Controller (CTL) – worker (W).4
Controller including the non-volatile memory (NVM, CompactFlash ® card). After
initial system startup (power on), this Controller takes on the active role.
31
CTL (P) slot
Controller (CTL) – protection (P).4
Optionally, a second Controller can be equipped for CTL equipment protection
(duplex control). After initial system startup (power on), this Controller takes on the
standby role.
40
User panel
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-3
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
Slots
Network element configurations
Slot equipage
The slots 20, 29, and 30 do not exist.
Notes:
1.
Slots for port units are called “universal slots”. The transmission capacity of a port unit in a universal slot
can be up to 20 Gbps per slot.
2.
If not stated otherwise, each port unit occupies one universal slot,.
3.
The electrical port units (EP{) can only be used in the universal slots in the upper row of the shelf (slots
21 { 28, and 32 { 39), and in a shelf of type DUR/2.
4.
The terms “worker” and “protection” are used to describe the static role within a protection, whereas the
terms “active” and “standby” are used to describe the current (dynamic) role.
Available slots on the rear side
The following illustration shows the available slots on the rear side of a DUR shelf.
80
ECI
slot
ECI
slot
ECI
slot
ECI
slot
78
76
74
72
PI/-
Fan unit
TI (B) TI (A)
69
70
PI (B)
56
ECI
slot
67
CI-CTL
PI/100
ECI
slot
65
ECI
slot
63
ECI
slot
61
PI/PI/100
PI (A)
54
52
51
45
43
41
Air filter
rear view
A DUR shelf provides the following slots on the rear side:
•
•
•
•
•
One dedicated slot for the connection interface of the Controller (CI-CTL).
Two dedicated slots for timing interfaces (TI A and TI B).
Two dedicated slots for power interfaces (PI A and PI B).
Eight dedicated slots for electrical connection interfaces (ECI).
One dedicated slot for the fan unit.
Slots
Slot equipage
41
– (reserved for future applications)
43
– (reserved for future applications)
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-4
Equipment provisioning concepts
Network element configurations
Slots
Slot equipage
45
Power interface (PI A)
The PI/100 variant of the power interface requires a wider slot than the PI/variant.
51
Connection interface of the Controller (CI-CTL)
52
– (reserved for future applications)
54
– (reserved for future applications)
56
Power interface (PI B)
The PI/100 variant of the power interface requires a wider slot than the PI/variant.
61{67
Electrical connection interfaces (ECI).
Grouping of the slots
•
when EP51 is used: 61 and 65, or 63; the respective ECI is 4 slots wide;
•
when EP155 is used: 61, 63, 65, 67 the respective ECI is 2 slots wide.
69
Timing interface (TI A)
70
Timing interface (TI B)
72{78
Electrical connection interfaces (ECI).
Grouping of the slots
80
•
when EP51 is used: 72 and 76, or 74; the respective ECI is 4 slots wide;
•
when EP155 is used:72, 74, 76, 78; the respective ECI is 2 slots wide.
Fan unit
General configuration rules and guidelines
Observe the following general rules and guidelines with regard to the shelf
configuration. Take all these rules and guidelines into consideration as the ordering in
the list does not necessarily reflect the order of importance.
1. Use the configurator tool to verify if a certain subrack equipage is permitted.
For example: Do not install a GE1 port unit in the lower row of the subrack below
an OP10 port unit in the upper row. This rule applies to all supported OP10
versions except the OP10/1.3IOR1.
2. Ensure that both power feeders are operating. If this is not possible due to
maintenance operations, and if the system configuration consumes more than 2200
W, ensure that the power battery is in “charging mode” (also known as “floating
mode”). Do not perform maintenance operations on the power feeder while the
power plant is in “battery mode”, that is, while the voltage at the system power
interface (PI) is less than 49 V.
3. Never operate a LambdaUnite ® MSS system without a fan unit for more than two
(2) minutes to avoid overheating of the system.
Leaving the fan unit out of operation for more than two minutes may cause the
respective network element to fail.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-5
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
Network element configurations
4. Do not operate a network element without a CI-CTL, as the initialization/reinitialization of the CTL may fail when no CI-CTL is present.
5. Do not insert circuit packs simultaneously. When several circuit packs have to be
inserted, they should be inserted one after the other, with intervals of at least one
second.
6. Cover unequipped slots and OM sockets with blank front plates or OM socket
covers to guarantee proper cooling, airflow, and EMC behavior. Do not leave
unequipped slots uncovered for more than ten (10) minutes to avoid overheating of
the system. Disregarding this warning could cause the system to fail and voids
warranty. Blank front plates are available as orderable items (cf. LambdaUnite ®
MSS Installation Guide). Parent boards for optical modules are shipped with the
OM sockets covered.
The cooling of the LambdaUnite ® MSS system relies on sufficient airflow.
Uncovered slots or OM sockets prevent an adequate cooling because
LambdaUnite ® MSS systems make use of the stack effect.
7. To avoid damaging the blank front plates, ensure that the maximum upward and
downward displacement of the latches does not exceed 5 mm.
8. To avoid damage to the NE database stored on the CompactFlash ® card, it is of
great importance to follow a special procedure for removing the Controller (CTL)
from its slot. Proceed as follows:
a. Open the latches of the CTL to be replaced. Do not immediately remove the
CTL from its slot at that time.
The green activity LED on the faceplate of the CTL starts flashing.
b. Wait until the green activity LED has stopped flashing (about five seconds).
c. Remove the CTL from its slot.
9. Please note that, if you insert a circuit pack into a universal slot, which is neither
(auto-)provisioned nor preprovisioned, and you do not close the latches of the
circuit pack, then no alarm will be reported to indicate that communication between
this circuit pack and other circuit packs of the system will not be possible.
Specific configuration rules and guidelines
Specific configuration rules and guidelines apply depending on the maximum switching
capacity of a LambdaUnite ® MSS system and on the desired application.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-6
Equipment provisioning concepts
Network element configurations
Maximum switching capacity
A LambdaUnite ® MSS system can be configured for different values of the maximum
cross-connect capacity (Maximum Switch Capacity):
LXC160
The maximum switch capacity of the system is 160 Gbps
(3072 × 3072 VC-3/STS-1; 1024 × 1024 VC4).
This is the default value after a new NE installation with Release
4.0 (or higher) NE software and an empty database.
LXC320
The maximum switch capacity of the system is 320 Gbps
(6144 × 6144 VC-3/STS-1; 2048 × 2048 VC4).
This is the default value after an upgrade from a previous NE
software release to Release 4.0 (or higher) NE software.
LXC640
The maximum switch capacity of the system is 640 Gbps
(12288 × 12288 VC-3/STS-1; 4096 × 4096 VC4).
Important! The maximum switch capacity is independent of the type of
cross-connection and timing unit used. However, the shelf equipage concerning the
cross-connection and timing units depends on the maximum switch capacity.
LXC with a max. switching capacity of 160 Gbps
These rules and guidelines apply when the Maximum Switch Capacity of the system
is set to LXC160:
1. The maximum switching capacity of the system is 160 Gbps (3072 × 3072
VC-3/STS-1; 1024 × 1024 VC4).
2. Each type of cross-connection and timing unit (XC160, XC320, XC640) can be
provisioned in slot 9 and slot 10. However, the maximum switching capacity that
can be used is 160 Gbps, and the slot equipage rules as described above apply
independent of which cross-connection and timing unit is used.
3. Port units can only be used in the upper row of the DUR shelf, that is, in the
universal slots 21 { 28 and 32 { 39.
When a port unit is installed in any of the remaining universal slots, then the green
activity LED of that port unit will be flashing, and a
Circuit Pack Type Mismatch alarm will be reported. An attempt to preprovision
a port unit for any of these slots will be denied.
Cover all unequipped slots with blank front plates.
4. Port units with a transmission capacity of 20 Gbps (for example an OP2G5D/PAR8
parent board, equipped with 8 optical modules) can only be used in the universal
slots 22, 24, 26, 28, 33, 35, 37, and 39. The slot left to a slot where such a port
unit is installed has to remain unequipped, that is, cannot be used for other
applications. Please also refer to the diagram subsequent to this list.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-7
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
Network element configurations
5. Lower order cross-connection units of type LOXC/1 can be used in the universal
slots 37 (worker slot) and 39 (protection slot). The slot left to an LOXC/1 has to
remain unequipped, that is, cannot be used for other applications.
Lower order cross-connection units of type LOXC40G2S/1 cannot be used in a
system with a maximum switching capacity of 160 Gbps. However, the universal
slot pairs 36/37 and 38/39 can be used for lower order cross-connection units of
type LOXC40G2S/1 (2 slots wide) after the system has been upgraded to a
maximum switching capacity of 640 Gbps (XC in-service upgrade XC160 →
XC640).
Lower order cross-connection units of type LOXC40G3S/1 cannot be used in a
system with a maximum switching capacity of 160 Gbps. However, the universal
slots 2/3/4 and 17/18/19 can be used for lower order cross-connection units of type
LOXC40G3S/1 (3 slots wide) after the system has been upgraded to a maximum
switching capacity of 320 Gbps (XC in-service upgrade XC160 ® XC320).
6. XC160 cross-connection and timing units support ONNS applications.
7. Lucent recommends to use two XC160 cross-connection and timing units. Thus,
both the cross-connect as well as the timing function are automatically 1+1
equipment protected. However, an LXC configuration with a single, but
unprotected XC160 cross-connection and timing unit is also possible.
User panel
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
XC (P) slot
Universal slot
XC (W) slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
1
2
3
4
5
6
7
8
9
10 11 12 13 14 15 16 17 18 19
CTL (W) slot
Universal slot
Universal slot
31 32 33 34 35 36 37 38 39
Universal slot
21 22 23 24 25 26 27 28
Universal slot
CTL (P) slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
40
front view
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-8
Equipment provisioning concepts
Network element configurations
LXC with a max. switching capacity of 320 Gbps
These rules and guidelines apply when the Maximum Switch Capacity of the system
is set to LXC320:
1. The maximum switching capacity of the system is 320 Gbps (6144 × 6144
VC-3/STS-1; 2048 × 2048 VC4).
2. Only XC320 or XC640 cross-connection and timing units can be provisioned in
slot 9 and slot 10. However, the maximum switching capacity that can be used is
320 Gbps, and the slot equipage rules as described above apply independent of
whether an XC320 or XC640 is used.
When an XC160 cross-connection and timing unit is installed in slot 9 or slot 10,
then the green activity LED of that XC160 will be flashing, and a
Circuit Pack Type Mismatch alarm will be reported.
3. Port units can be used in all universal slots.
However, port units with a transmission capacity of 20 Gbps (for example an
OP2G5D/PAR8 parent board, equipped with 8 optical modules) can only be used in
the universal slots 2, 4, 6, 8, 13, 15, 17, 19, 22, 24, 26, 28, 33, 35, 37, and 39. The
slot left to a slot where a 20-Gbps port unit is installed has to remain unequipped,
that is, cannot be used for other applications. Please also refer to the diagram
subsequent to this list.
Cover all unequipped slots with blank front plates.
4. Lower order cross-connection units of type LOXC/1 can be used in the universal
slots 4, 17, 19, 37, and 39.
The slots 4, 17 and 37 are worker slots. The slots 19 and 39 are protection slots. If
the worker LOXC/1 is installed either in slot 4 or in slot 17, then the protection
LOXC/1 must be installed in slot 19. If the worker LOXC/1 is installed in slot 37,
then the protection LOXC/1 must be installed in slot 39. The slot left to an
LOXC/1 has to remain unequipped, that is, cannot be used for other applications.
Lower order cross-connection units of type LOXC40G2S/1 cannot be used in a
system with a maximum switching capacity of 320 Gbps. However, the universal
slot pairs 3/4, 18/19, 36/37 and 38/39 can be used for lower order cross-connection
units of type LOXC40G2S/1 (2 slots wide) after the system has been upgraded to a
maximum switching capacity of 640 Gbps (XC in-service upgrade XC320 →
XC640).
Lower order cross-connection units of type LOXC40G3S/1 cannot be used in a
system with a maximum switching capacity of 160 Gbps. However, the universal
slots 2/3/4 and 17/18/19 can be used for lower order cross-connection units of type
LOXC40G3S/1 (3 slots wide) after the system has been upgraded to a maximum
switching capacity of 320 Gbps (XC in-service upgrade XC160 ® XC320).
Please note that at most one LOXC equipment protection group may exist, that is,
at most one worker slot can be used in combination with one protection slot.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-9
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
Network element configurations
5. Only the XC320/B variant of the XC320 cross-connection and timing units
supports ONNS applications.
6. Lucent recommends to use two XC320 cross-connection and timing units. Thus,
both the cross-connect as well as the timing function are automatically 1+1
equipment protected. However, an LXC configuration with a single, but
unprotected XC320 cross-connection and timing unit is also possible.
User panel
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
XC (P) slot
3
4
5
6
7
8
9
10 11 12 13 14 15 16 17 18 19
Universal slot
XC (W) slot
Universal slot
Universal slot
2
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
1
CTL (W) slot
Universal slot
Universal slot
31 32 33 34 35 36 37 38 39
Universal slot
21 22 23 24 25 26 27 28
Universal slot
CTL (P) slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
40
front view
LXC with a max. switching capacity of 640 Gbps
These rules and guidelines apply when the Maximum Switch Capacity of the system
is set to LXC640:
1. The maximum switching capacity of the system is 640 Gbps (12288 × 12288
VC-3/STS-1; 4096 × 4096 VC4).
2. Only XC640 cross-connection and timing units can be provisioned in slot 9 and
slot 10.
When any cross-connection and timing unit other than an XC640 is installed in
slot 9 or slot 10, then the green activity LED of that cross-connection and timing
unit will be flashing, and a Circuit Pack Type Mismatch alarm will be reported.
3. Port units can be used in all universal slots, and all universal slots can be used.
4. Lower order cross-connection units of type LOXC/1 can be used in the universal
slots 4, 17, 18, 19, 37, and 39. The slots 4, 17, 18 and 37 are worker slots. The
slots 19 and 39 are protection slots. If the worker LOXC/1 is installed in slot 4, 17,
or 18, then the protection LOXC/1 must be installed in slot 19. If the worker
LOXC/1 is installed in slot 37, then the protection LOXC/1 must be installed in
slot 39.
Lower order cross-connection units of type LOXC40G2S/1 (two slots wide) can be
used in the universal slot pairs 3/4, 16/17, 18/19, 36/37, and 38/39. The slot pairs
3/4, 16/17 and 36/37 are worker slots. The slot pairs 18/19 and 38/39 are protection
slots. If the worker LOXC40G2S/1 is installed in the slot pairs 3/4 or 16/17, then
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-10
Equipment provisioning concepts
Network element configurations
the protection LOXC40G2S/1 must be installed in the slot pair 18/19. If the worker
LOXC40G2S/1 is installed in the slot pair 36/37, then the protection
LOXC40G2S/1 must be installed in the slot pair 38/39.
Lower-order cross-connection units of type LOXC40G3S/1 can be used in the
universal slots 4 and 19 (worker LOXC40G3S/1 in the slots 2/3/4, protection
LOXC40G3S/1 in the slots 17/18/19).
Please note that at most one LOXC equipment protection group may exist, that is,
at most one worker slot can be used in combination with one protection slot.
5. XC640 cross-connection and timing units support ONNS applications.
6. Lucent recommends to use two XC640 cross-connection and timing units. Thus,
both the cross-connect as well as the timing function are automatically 1+1
equipment protected. However, an LXC configuration with a single, but
unprotected XC640 cross-connection and timing unit is also possible.
User panel
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
CTL (P) slot
Universal slot
Universal slot
XC (W) slot
XC (P) slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
1
2
3
4
5
6
7
8
9
10 11 12 13 14 15 16 17 18 19
CTL (W) slot
Universal slot
Universal slot
31 32 33 34 35 36 37 38 39
21 22 23 24 25 26 27 28
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
40
front view
LXC supporting ONNS applications
A special shelf equipage is required for ONNS applications.
Observe these rules and guidelines with regard to an LXC configuration supporting
ONNS applications:
1. Only Controllers of type CTL/2 (with a 512-MByte CompactFlash ® card), CTL/3S
(with a 1-GByte CompactFlash ® card), or CTL/4S (with a 512-MByte
CompactFlash ® card), and cross-connection and timing units of type XC160,
XC320/B, or XC640 are suitable for ONNS applications.
Lucent recommends to use two suitable Controllers (duplex control) and two
suitable cross-connection and timing units (XCs). Thus, both the Controllers as well
as the cross-connection and timing units are automatically 1+1 equipment
protected.
2. All available port units except for OP40, EP51, and OPT2G5 can be used for
ONNS applications.
3. Lower order cross-connections are not supported by ONNS.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-11
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
Pluggable
optical interface modules
...................................................................................................................................................................................................................................
Port units with optical interface modules
LambdaUnite ® MSS supports optical port units consisting of a parent board which can
be equipped with field-replaceable optical interface modules.
An optical module is a replaceable unit with a receiver and transmitter function
providing the optical port. LambdaUnite ® MSS optical interface modules are “hot
pluggable” (field-replaceable), i.e. the interface modules can be inserted or removed
while the parent board is in operation, without affecting the service of other interface
modules on the same parent board.
The following parent boards with field-replacable optical interface modules are
supported:
Parent board
Available optical
interface modules
Remark
OPLB/PAR8
OM155/1.3IR1
The OPLB/PAR8 parent board can be equipped with up to 8
optical interface modules (ports), each having a transmission
capacity of either 155 Mbps or 622 Mbps.
OM155/1.3LR1
OM155/1.5LR1
OM622/1.3IR1
Mixing of ports with different reaches is supported on a
single parent board. However, mixing of ports with different
bit rates is not supported.
OM622/1.3LR1
OM622/1.5LR1
OP2G5D/PAR8
OM2G5/1.3SR1
OM2G5/1.3LR1
OM2G5/1.5LR1
OM2G5/CL47S1,
OM2G5/CL49S1, {
OM2G5/CL61S1
The OP2G5D/PAR8 parent board can be equipped with up to
8 optical interface modules (ports), each having a
transmission capacity of 2.5 Gbps. Thus, the transmission
capacity of a fully equipped OP2G5D/PAR8 port unit is
20 Gbps. Therefore, specific configuration rules need to be
observed, please refer to “Specific configuration rules and
guidelines” (p. 5-6).
Mixing of ports with different reaches and/or different
wavelengths is supported on a single parent board.
OM2G5/CL47L1,
OM2G5/CL49L1, {
OM2G5/CL61L1
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-12
Equipment provisioning concepts
Pluggable optical interface modules
Parent board
Available optical
interface modules
Remark
OP2G5/PAR4
OM2G5/1.3SR1
The OP2G5/PAR4 parent board can be equipped with up to
4 optical interface modules (ports), each having a
transmission capacity of 2.5 Gbps.
OM2G5/1.3LR1
OM2G5/1.5LR1
Mixing of ports with different reaches and/or different
wavelengths is supported on a single parent board.
OM2G5/CL47S1,
OM2G5/CL49S1, {
OM2G5/CL61S1
OM2G5/CL47L1,
OM2G5/CL49L1, {
OM2G5/CL61L1
OPT2G5/PAR3
OM2G5/1.3SR1
OM2G5/1.3LR1
OM2G5/1.5LR1
The OPT2G5/PAR3 transparency parent board can be
equipped with up to 3 optical interface modules (ports), each
having a transmission capacity of 2.5 Gbps.
Mixing of ports with different reaches and/or different
wavelengths is supported on a single parent board.
OM2G5/CL47S1,
OM2G5/CL49S1, {
OM2G5/CL61S1
OM2G5/CL47L1,
OM2G5/CL49L1, {
OM2G5/CL61L1
OP10/PAR1XFP
OMX10/10KM1
OMX10/40KM1
OMX10/ 80KM1
OP10D/PAR2
OM10/1.3IOR1
OM10/1.5IR1
OM10/1.5LR1
OP10D/PAR2XFP
OMX10/10KM1
OMX10/40KM1
OMX10/ 80KM1
The OP10/PAR1XFP parent board can be equipped with an
optical XFP interface module with a transmission capacity of
10 Gbps. Thus, the transmission capacity of a fully equipped
OP10D/PAR2 port unit is 20 Gbps. Therefore, specific
configuration rules need to be observed, please refer to
“Specific configuration rules and guidelines” (p. 5-6).
The OP10D/PAR2 parent board can be equipped with up to
2 optical interface modules (ports), each having a
transmission capacity of 10 Gbps. Thus, the transmission
capacity of a fully equipped OP10D/PAR2 port unit is
20 Gbps. Therefore, specific configuration rules need to be
observed, please refer to “Specific configuration rules and
guidelines” (p. 5-6).
Mixing of ports with different reaches and/or different
wavelengths is supported on a single parent board.
The OP10D/PAR2XFP parent board can be equipped with up
to 2 XFP optical interface modules (ports), each having a
transmission capacity of 10 Gbps. Thus, the transmission
capacity of a fully equipped OP10D/PAR2XFP port unit is
20 Gbps. Therefore, specific configuration rules need to be
observed, please refer to “Specific configuration rules and
guidelines” (p. 5-6).
Mixing of ports with different reaches and/or different
wavelengths is supported on a single parent board.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-13
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
Pluggable optical interface modules
Parent board
Available optical
interface modules
Remark
GE10PL1/1A8
OMGE1/SX1
The GE10PL1/1A8 is a high density private line unit for
Gigabit Ethernet applications. The parent board can
optionally be equipped with either one 10-Gbps or eight
1-Gbps optical interface modules (ports).
OMGE1/LX1
OMGE1/ZX1
OMX10/10KM1
OMX10/40KM1
OMX10/ 80KM1
The major advantage of these optical port units is that the optical interface modules
(ports) can be added, exchanged, or removed in the field without requiring special
tools, and without impacting the operation of the remaining ports. Thus, the
transmission capacity of a LambdaUnite ® MSS system can easily be adapted. It is
possible to leave the receptacles of optical modules (OM sockets) unequipped as long
as the transmission capacity of these ports is not needed.
Important! Cover unequipped slots and OM sockets with blank front plates or OM
socket covers to guarantee proper cooling, airflow and EMC behavior. Do not leave
unequipped slots uncovered for more than ten (10) minutes to avoid overheating of
the system. Disregarding this warning could cause the system to fail and voids
warranty. Blank front plates are available as orderable items (cf. LambdaUnite ®
MSS Installation Guide). Parent boards for optical modules are shipped with the
OM sockets covered.
Types of optical interface modules
For LambdaUnite ® MSS systems, the following types of optical interface modules can
be used:
•
•
For the 10-Gbps optical interface modules, these types of optical interface modules
are available:
– Slide-in modules with a Lucent Technologies proprietary design
– 10 Gigabit Small Form-factor Pluggable (XFP) modules
For the 155-Mbps, 622-Mbps and 2.5-Gbps optical interface modules, standardized
Small Form-factor Pluggable (SFP) modules are used which comply to the SFP
MSA standard of the SFF Committee.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-14
Equipment provisioning concepts
Pluggable optical interface modules
OM socket
SFP module
Parent board
OP10D
Parent board
Slide-in module
Available modules
The available optical interface modules are basically characterized by their bit rate,
wavelength and reach.
155 Mbps
The following optical interface modules with a bit rate of 155 Mbps are available:
Opt. interface module
Apparatus code
Bit rate
Wavelength
Reach
OM155/1.3IR1 (SFP)
OM155A184
STM-1/OC-3
1310 nm
15 km
OM155/1.3LR1 (SFP)
OM155A183
STM-1/OC-3
1310 nm
40 km
OM155/1.5LR1 (SFP)
OM155A185
STM-1/OC-3
1550 nm
80 km
622 Mbps
The following optical interface modules with a bit rate of 622 Mbps are available:
Opt. interface module
Apparatus code
Bit rate
Wavelength
Reach
OM622/1.3IR1 (SFP)
OM622A182
STM-4/OC-12
1310 nm
15 km
OM622/1.3LR1 (SFP)
OM622A181
STM-4/OC-12
1310 nm
40 km
OM622/1.5LR1 (SFP)
OM622A180
STM-4/OC-12
1550 nm
80 km
1 Gbps (Gigabit Ethernet)
The following optical interface modules are available for Gigabit Ethernet applications:
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-15
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
Pluggable optical interface modules
Opt. interface module
Apparatus code
Bit rate
Wavelength
Reach
OMGE1/SX1
OMSX1
1 Gbps (1 GbE)
850 nm
550 m
OMLX1
1 Gbps (1 GbE)
1310 nm
10 km
OMZX1
1 Gbps (1 GbE)
1550 nm
70 km
(SFP, 1000BASE-SX)
OMGE1/LX1
(SFP, 1000BASE-LX)
OMGE1/ZX1
(SFP, 1000BASE-ZX)
2.5 Gbps
The following optical interface modules with a bit rate of 2.5 Gbps are available:
Opt. interface module
Apparatus code
Bit rate
Wavelength
Reach
OM2G5/1.3SR1 (SFP)
OM2G5A12
STM-16/OC-48
1310 nm
2 km
OM2G5/1.3LR1 (SFP)
OM2G5A203
STM-16/OC-48
1310 nm
40 km
OM2G5/1.5LR1 (SFP)
OM2G5A204
STM-16/OC-48
1550 nm
80 km
OM2G5/CL47S1
2CL47S1
STM-16/OC-48
1471 nm
40 km
2CL49S1
STM-16/OC-48
1491 nm
40 km
2CL51S1
STM-16/OC-48
1511 nm
40 km
2CL53S1
STM-16/OC-48
1531 nm
40 km
2CL55S1
STM-16/OC-48
1551 nm
40 km
2CL57S1
STM-16/OC-48
1571 nm
40 km
2CL59S1
STM-16/OC-48
1591 nm
40 km
2CL61S1
STM-16/OC-48
1611 nm
40 km
2CL47L1
STM-16/OC-48
1471 nm
80 km
2CL49L1
STM-16/OC-48
1491 nm
80 km
2CL51L1
STM-16/OC-48
1511 nm
80 km
(CWDM SFP)
OM2G5/CL49S1
(CWDM SFP)
OM2G5/CL51S1
(CWDM SFP)
OM2G5/CL53S1
(CWDM SFP)
OM2G5/CL55S1
(CWDM SFP)
OM2G5/CL57S1
(CWDM SFP)
OM2G5/CL59S1
(CWDM SFP)
OM2G5/CL61S1
(CWDM SFP)
OM2G5/CL47L1
(CWDM SFP)
OM2G5/CL49L1
(CWDM SFP)
OM2G5/CL51L1
(CWDM SFP)
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-16
Equipment provisioning concepts
Pluggable optical interface modules
Opt. interface module
Apparatus code
Bit rate
Wavelength
Reach
OM2G5/CL53L1
2CL53L1
STM-16/OC-48
1531 nm
80 km
2CL55L1
STM-16/OC-48
1551 nm
80 km
2CL57L1
STM-16/OC-48
1571 nm
80 km
2CL59L1
STM-16/OC-48
1591 nm
80 km
2CL61L1
STM-16/OC-48
1611 nm
80 km
(CWDM SFP)
OM2G5/CL55L1
(CWDM SFP)
OM2G5/CL57L1
(CWDM SFP)
OM2G5/CL59L1
(CWDM SFP)
OM2G5/CL61L1
(CWDM SFP)
10 Gbps
The following optical interface modules with a bit rate of 10 Gbps are available:
Opt. interface module
Apparatus code
Bit rate
Wavelength
Reach
OM10/1.3IOR1
OM10G7
STM-64/OC-192
1310 nm
600 m
OM10G14
STM-64/OC-192
1550 nm
40 km
OM10G6
STM-64/OC-192
1550 nm
80 km
OMX10G10
10 Gbps (10 GbE,
STM-64/OC-192)
1310 nm
10 km
OMX10G40
10 Gbps (10 GbE,
STM-64/OC-192)
1550 nm
40 km
OMX10G80
10 Gbps (10 GbE,
STM-64/OC-192)
1550 nm
80 km
(Slide-in module)
OM10/1.5IR1
(Slide-in module)
OM10/1.5LR1
(Slide-in module)
OMX10/10KM1
(XFP, 10GBASE-LR / I-64.1)
OMX10/40KM1
(XFP, 10GBASE-ER / S-64.2b)
OMX10/80KM1
(XFP, 10GBASE / L-64.2)
Notes:
1.
The OMX10 optical interface modules can optionally be used with a GE10PL1/1A8, OP10/PAR1XFP, or
OP10D/PAR2XFP parent board.
Provisioning of optical interface modules
Optical interface modules can be autoprovisioned, preprovisioned, provisioned, and
deprovisioned, just like any other optical interface.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-17
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
Pluggable optical interface modules
Preprovisioning
The desired type of optical interface module, being suitable for the corresponding port
unit (parent board), can be preprovisioned for an OM socket. Afterward, exactly the
preprovisioned type of optical interface module needs to be inserted into that OM
socket. Otherwise an Optical Module Type Mismatch alarm will be reported.
Please also consider the specific rules that apply to the OPLB (see below).
Autoprovisioning
Any type of optical interface module which is suitable for the corresponding port unit
(parent board) can be inserted into an empty OM socket, and thus be autoprovisioned.
Please also consider the specific rules that apply to the OPLB (see below).
Provisioning
Provisioning an optical interface module is equivalent to provisioning an optical port.
Deprovisioning
Optical interface modules can either be deprovisioned explicitly by deprovisioning each
module individually, or implicitly by deprovisioning the parent board.
Exchangeability
It is possible to exchange the provisioned type of an optical interface module. For
example, you can exchange an optical module by another module of the same bit rate
but different wavelength and/or reach.
Special case: OPLB
A special case is the OPLB parent board as it supports two different bit rates.
The following applies to the OPLB parent board:
•
•
When for an OPLB parent board an optical module with a bit rate of either 155 or
622 Mbps is preprovisioned or present in one of the OM sockets, then only optical
modules of the same bit rate can be inserted or preprovisioned for the remaining
OM sockets.
When an OPLB parent board with two or more pre-installed optical modules is
inserted into a slot, and nothing has been preprovisioned, then the bit rate
supported by the OPLB parent board is determined by the bit rate of the optical
module in the OM socket with the lowest number. Further optical modules with the
same bit rate will be autoprovisioned. Already present or subsequently inserted
optical modules with a different bit rate will be alarmed
(Optical Module Type Mismatch).
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-18
Equipment provisioning concepts
Overview
of replaceable units
...................................................................................................................................................................................................................................
Shelves
These types of shelves are supported:
Type
Functional
name
Functional
qualifier
Apparatus
Code
Remarks
DUR/-
DUR
–
(none)
Dual unit row shelf for LXC
configurations (without support of
electrical port units)
DUR/2
DUR
2
(none)
Dual unit row shelf for LXC
configurations (with support of
electrical port units)
DUR/3
DUR
3
(none)
Dual unit row shelf supporting
scalable packet switching and lower
order cross-connection units with a
higher switching capacity (LOXC40)
External system interfaces and peripheral units
These external system interfaces and peripheral units are supported:
Interface
Functional
name
Functional
qualifier
Apparatus
Code
Remarks
TI/E1/DS1
TI
E1/DS1
(none)
Timing interface
PI/-
PI
–
(none)
Power interfaces
100
(none)
PI/100
UPL/-
UPL
–
(none)
User panel
FU/-
FU
–
(none)
Fan unit for DUR/- and DUR/2
shelves
FU/2
FU
2
(none)
Fan unit for DUR/3 shelves
ECI/155MP8
ECI
155MP8
(none)
155ME8
(none)
Electrical connection interfaces for
EP155 port units
MP72
(none)
ECI/155ME8
ECI51/MP72
ECI51
Electrical connection interface for
EP51 port units
Notes:
1.
These system components are not listed in the acceptable circuit pack type list. As they
are replaceable units the above table is included in this document for the sake of
completeness.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-19
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
Overview of replaceable units
Controllers (CTL)
These types of controllers are supported:
Circuit pack
Occupied
slots
Apparatus
Code
Remarks
Type
Functional
name
Functional
qualifier
CTL/-
CTL
–
1
KFA1
•
256 MByte NVM storage capacity
CTL/2
CTL
2
1
KFA531
•
512 MByte NVM storage capacity
•
ONNS support
•
1 GByte NVM storage capacity
•
LOXC support
•
Support of 180 DCCs
•
1 GByte NVM storage capacity
•
ONNS support
•
LOXC support
•
Support of 180 DCCs
CTL/3T
CTL/3S
CTL/4T
CTL
CTL
CTL
3T
3S
4T
1
1
1
KFA536
KFA537
KFA538
Redesigned hardware, fully compatible
with the CTL/-:
•
CTL/4S
CTL
4S
1
KFA539
256 MByte NVM storage capacity
Redesigned hardware, fully compatible
with the CTL/2:
•
512 MByte NVM storage capacity
•
ONNS support
Non-volatile memory
The system’s non-volatile memory (NVM) is realized by means of a CompactFlash ®
card with IDE interface. The required size of the CompactFlash ® card depends on the
Controller used:
•
•
•
•
The CTL/- Controller variant requires a CompactFlash ® card with a 256-MByte
NVM storage capacity.
The CTL/2 Controller variant requires a CompactFlash ® card with a 512-MByte
NVM storage capacity.
The CTL/3T Controller variant requires a CompactFlash ® card with a 1-GByte
NVM storage capacity.
The CTL/3S Controller variant requires a CompactFlash ® card with a 1-GByte
NVM storage capacity.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-20
Equipment provisioning concepts
•
•
Overview of replaceable units
The CTL/4T Controller variant requires a CompactFlash ® card with a 256-MByte
NVM storage capacity.
The CTL/4S Controller variant requires a CompactFlash ® card with a 512-MByte
NVM storage capacity.
Cross-connect units (XC)
These cross-connect units are supported:
Circuit pack
Type
Functional
name
Functional
qualifier
XC160/-
XC160
–
XC320/-
XC320/A
XC320/B
XC640/-
LOXC/1
XC320
XC320
XC320
XC640
LOXC
–
A
B
–
1
Occupied
slots
Apparatus
Code
Remarks
1
KFD3
Cross-connection and timing unit:
1
1
1
1
1
KFD1
KFD1A
KFD1B
KFD2
KFA700
•
160-Gbps switching capacity
•
Suitable for ONNS applications
Cross-connection and timing unit:
•
320-Gbps switching capacity
•
Not suitable for ONNS applications
Cross-connection and timing unit:
•
320-Gbps switching capacity
•
Not suitable for ONNS applications
Cross-connection and timing unit:
•
320-Gbps switching capacity
•
Suitable for ONNS applications
Cross-connection and timing unit:
•
640-Gbps switching capacity
•
Suitable for ONNS applications
Lower order cross-connection unit:
•
LOXC40G2S/1
LOXC40G2S
1
2
KFA702
15-Gbps switching capacity
Lower order cross-connection unit:
•
40-Gbps switching capacity
Only in combination with XC640.
LOXC40G3S/1
LOXC40G3S
1
3
KFA 703
Lower order cross-connection unit:
•
40-Gbps switching capacity
Only in combination with XC320.
40-Gbps optical port units (SDH/SONET)
These 40-Gbps optical SDH/SONET port units are supported:
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-21
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
Overview of replaceable units
Circuit pack
Occupied
slots
Apparatus
Code
Number of
ports
Remarks
Type
Functional
name
Functional
qualifier
OP40/1.5LR1O
OP40
1.5LR1O
4
KFA3
1
–
OP40/1.3IOR1
OP40
1.3IOR1
4
KFA202
1
–
OP40/9280XT {
OP40/8650XT
OP40
9280XT {
8650XT
4
KFA290 {
KFA353
1
64 port unit variants for
interworking with
LambdaExtreme ™ Transport
Please refer to the LambdaUnite ® MSS Applications and Planning Guide for more
detailed technical specifications (optical wavelength or reach for example).
10-Gbps optical port units (SDH/SONET)
These 10-Gbps optical SDH/SONET port units are supported:
Circuit pack
Occupied
slots
Apparatus
Code
Number
of ports
Remarks
Type
Functional
name
Functional
qualifier
OP10/1.5LR1
OP10
1.5LR1
1
KFA6
1
–
OP10/1.3IOR1
OP10
1.3IOR1
1
KFA7
1
–
OP10/1.5IR1
OP10
1.5IR1
1
KFA14
1
–
OP10/01/800G {
OP10/80/800G
OP10
01/800G {
40/800G
1
KFA9,
KFA81 {
KFA159
1
80 port unit variants for
interworking with WaveStar ®
(800G)
OP10/01/PWDM {
OP10/16/PWDM
OP10
01/PWDM {
16/PWDM
1
KFA11,
KFA61 {
KFA75
1
16 port unit variants for
passive WDM applications
(36-km reach)
OP10/17/PWDM {
OP10/32/PWDM
OP10
17/PWDM {
32/PWDM
1
KFA515 {
KFA530
1
16 port unit variants for
passive WDM applications
(22-km reach)
OP10/9285XT {
OP10/8650XT
OP10
9285XT {
8650XT
1
KFA210 {
KFA482
1
128 port unit variants for
interworking with
LambdaExtreme ™ Transport
OP10/XTTC
OP10
XTTC
1
KFA361
1
Port unit with tunable laser
(C-Band) for interworking with
LambdaExtreme ™ Transport
(laser tunable from
1554.54 nm to 1568.36 nm,
that is, 192.85 THz to
191.15 THz, 50-GHz spacing,
35 colors)
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-22
Equipment provisioning concepts
Overview of replaceable units
Circuit pack
Type
Functional
name
Functional
qualifier
OP10/XTTL
OP10
XTTL
Occupied
slots
Apparatus
Code
Number
of ports
Remarks
1
KFA362
1
Port unit with tunable laser
(L-Band) for interworking with
LambdaExtreme ™ Transport
(laser tunable from
1568.77 nm to 1607.47 nm,
that is, 191.10 THz to
186.50 THz, 50-GHz spacing,
93 colors)
OP10D/PAR2
OP10D
PAR2
1
KFA630
1-2
Parent board for up to 2 SFP
optical interface modules
OP10D/PAR2XFP
OP10D
PAR2XFP
1
KFA632
1-2
Parent board for up to 2 XFP
optical interface modules
OP10/PAR1XFP
OP10
PAR1XFP
1
KFA631
1
Parent board for 1 XFP optical
interface module
For more detailed information (technical specifications for example), also refer to the
LambdaUnite ® MSS Applications and Planning Guide.
2.5-Gbps optical port units (SDH/SONET)
These 2.5-Gbps optical SDH/SONET port units are supported:
Circuit pack
Occupied
slots
Apparatus
Code
Number
of ports
Remarks
Type
Functional
name
Functional
qualifier
OP2G5/1.3SR4
OP2G5
1.3SR4
1
KFA12
4
–
OP2G5/1.3LR4
OP2G5
1.3LR4
1
KFA203
4
–
OP2G5/1.5LR4
OP2G5
1.5LR4
1
KFA204
4
–
OP2G5/PARENT
OP2G5
PARENT
1
KFA20
1-2
Parent board for up to 2
passive WDM interface
modules
OM2G5/921PWDM
{
OM2G5/959PWDM
OM2G5
921PWDM {
959PWDM
–
OM2G5A921
{
OM2G5A959
1
Optical interface modules
for passive WDM
applications
OP2G5D/PAR8
OP2G5D
PAR8
1
KFA620
1-8
Parent board for up to eight
pluggable optical interface
modules
OP2G5/PAR4
OP2G5
PAR4
1
KFA621
1-4
Parent board for up to four
pluggable optical interface
modules
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-23
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
Overview of replaceable units
Circuit pack
Type
Functional
name
Functional
qualifier
OPT2G5/PAR3
OPT2G5
PAR3
Occupied
slots
Apparatus
Code
Number
of ports
Remarks
1
KFA540
1-3
Transparency parent board
for up to three pluggable
optical interface modules
For more detailed information (technical specifications for example), also refer to the
LambdaUnite ® MSS Applications and Planning Guide.
622-Mbps and 155-Mbps optical port units (SDH/SONET)
These 622-Mbps and 155-Mbps optical SDH/SONET port units are supported:
Circuit pack
Occupied
slots
Apparatus
Code
Number of
ports
Remarks
Type
Functional
name
Functional
qualifier
OP622/1.3IR16
OP622
1.3IR16
1
KFA17
16
OC-12/STM-4 port unit
(622-Mbps)
OP155M/1.3IR16
OP155M
1.3IR16
1
KFA18
16
OC-3/STM-1 port unit
(155-Mbps)
OPLB/PAR8
OPLB
PAR8
1
KFA180
1-8
Parent board for up to
eight pluggable optical
interface module
For more detailed information (technical specifications for example), also refer to the
LambdaUnite ® MSS Applications and Planning Guide.
Electrical port units
The following electrical port units are supported:
Circuit pack
Occupied slots
Apparatus
Code
Number of
ports1
Remarks
Type
Functional
name
Functional
qualifier
EP155/EL8
EP155
EL8
1
KFA533
8
Electrical port unit
(STM-1)
EP51/EL36
EP51
EL36
1
KFA535
36
Electrical port unit
(DS3 or EC-1)
EP51/EL36B
EP51
EL36B
1
KFA535B
36
Electrical port unit
(DS3 or EC-1)
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-24
Equipment provisioning concepts
Overview of replaceable units
Notes:
1.
The STM-1e, DS3, or EC-1 ports respectively are located on electrical connection interfaces (ECI) which
have to be installed in corresponding rear-side slots.
Gigabit Ethernet port units
These Gigabit Ethernet port units are supported:
Circuit pack
Occupied
slots
Apparatus
Code
Number of ports
Remarks
Type
Functional
name
Functional
qualifier
GE1/SX4
GE1
SX4
1
KFA13
4
1000BASE-SX interface
(short reach)
GE1/LX4
GE1
LX4
1
KFA532
4
1000BASE-LX interface
(long reach)
GE10PL1/1A8
GE10PL1
1A8
1
KFA720
1 × 10GbE
(XFP), or
Private Line Gigabit
Ethernet unit with either
1 × 10GBASE-X or
8 × 1000BASE-X
interfaces
8 × 1GbE (SFP)
Refer to the LambdaUnite ® MSS Applications and Planning Guide for more detailed
technical specifications.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-25
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
NE
hardware components and their identifiers
...................................................................................................................................................................................................................................
Reference
For a complete and up-to-date list of all hardware items with the respective comcodes,
refer to the Engineering Drawings ED8C948-10 and ED8C948-20. You can order them
in the latest version from the Lucent’s Product Documentation web site
(http://www.cic.lucent.com/drawings.html).
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-26
Equipment provisioning concepts
Port
types
...................................................................................................................................................................................................................................
Definition of port
A port is a connectable point that can terminate a physical or logical network
connection.
There are two types of ports:
•
•
A physical port is a physical connection point. Transmission lines attach to physical
ports.
A logical port is a logical connection point within a physical connection point. At
the logical port the overhead bytes are terminated: in the transmit direction
overhead bytes are added, in the receive direction overhead bytes are extracted.
Therefore logical ports are also called termination points. Logical ports are
contained within physical ports. Logical ports can contain other logical ports.
An example for the principle definition of physical and logical ports is shown in the
following figure:
2 Mbps
physical
Termination of
Overhead Bytes
TU-12
logical
Add and delete ports
Ports are automatically created in the management system when an NE is added to the
management system or when a circuit pack is installed. Upon addition to the
management system the port parameters are available for provisioning.
For logical ports, only the ones that exist on the NE and also have associated port
parameters are supported in the management system. For the majority NEs, logical
ports are supported only when they are involved in cross-connections.
Ports are automatically deleted from the management system when an NE is deleted
from the management system or when a circuit pack is removed.
Supported ports
All ports that carry port parameters are supported by the management system. These
ports include physical ports or logical ports. For logical ports, typically the ports only
carry parameters after being involved in a cross-connection. However, there are cases
in which logical ports have parameters even when they are not used in a
cross-connection.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-27
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
Port types
Supported port rates
The available port rates are shown in the following table:
Port rate
Description
Category
STM-256
Optical interface, 40 Gbps
SDH physical
OC-768
Optical interface, 40 Gbps
SONET physical
STM-64
Optical interface, 10 Gbps
SDH physical
OC-192
Optical interface, 10 Gbps
SONET physical
STM-16
Optical interface, 2.5 Gbps
SDH physical
OC-48
Optical interface, 2.5 Gbps
SONET physical
STM-4
Optical interface, 622 Mbps
SDH physical
OC-12
Optical interface, 622 Mbps
SONET physical
STM-1
Optical interface, 255 Mbps
SDH physical
OC-3
Optical interface, 255 Mbps
SONET physical
STM-1
Electrical interface, 255 Mbps
SDH physical
EC-1
Electrical interface, synchronous, 51.840 Mbps
SONET physical
T3
Electrical DS3 interface, plesiochronous 44.736 Mbps
SONET physical
E3
Electrical interface, 34 Mbps
SDH physical
E1
Electrical interface, 2 Mbps
SDH physical
DS1
Electrical interface, 1.5 Mbps
SDH physical
10 Gb Ethernet
Gigabit Ethernet interface
Ethernet physical
1 Gb Ethernet
Gigabit Ethernet interface
Ethernet physical
VCG
Virtual concatenation group
VCG physical
OS
Optical channel
VC-4-64C
Virtual container concatenated
VC-4-64C logical
VC-4-16C
Virtual container concatenated
VC-4-16C logical
VC-4-4C
Virtual container concatenated
VC-4-4C logical
VC-4
Virtual container
VC-4 logical
HO-VC-3
Virtual container
HO-VC-3 logical
ODU10G
Virtual container
ODU10G
Port names
The name of the physical ports consists of two parts separated by a dot. The first part
is related to the slot name, the second part is the port number within that slot.
Example: LP2.1, TP1.3
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-28
Equipment provisioning concepts
Port types
The name of the logical ports consists of the physical port name followed by the AU-4
number and for low order signals, the VC number (VC-12 or VC-3). The VC number
consists of:
•
•
•
The number of the TUG-3 inside the VC-4
The number of the TUG-2 inside the TUG-3
The TU-12 number inside the TUG-2
TP1.1,1.112
Slot
Port
AU-4 number
VC-12 (or VC-3) number
VC-12:
112
TUG-3
TUG-2
TU-12
VC-3:
100
TUG-3
Port ID formats
The management system supports two port ID formats and the ability to control which
format is used:
•
•
Native Name: This format is the default setting.
ITU-T G.707 Format: This format applies to certain logical ports.
The management system allows the user to select which format is used for port names
throughout the management system. This is controlled on the Preferences page.
The management system also allows the user to select which format is used for port
names on specific pages. This is controlled by a toggle button on the Add
Connection, Graphical Layout, and Ports pages.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-29
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
Port types
The two states of the Port ID Format button are shown in the following table:
Button state
Port ID format
Native name
ITU-T G.707
Test loops
An incoming test loop (inloop) can be set on the 1.5 Mbps, 2 Mbps, 34 Mbps, and 45
Mbps ports. The input signal is directly routed back to its corresponding output without
altering the signal format. This loop can be used to test the connectors. Only one
inloop can be set at the same time.
An outgoing test loop (outloop) can be set on the 1.5 Mbps, 2 Mbps, 34 Mbps, and 45
Mbps ports. The output signal is directly routed back to its corresponding input without
altering the signal format. This loop can be used to test how the signal passes through
the system.
If a test loop is enabled, the abnormal state is activated. After disabling the test loop
the cross-connections that existed before setting the test loop are restored.
Test loops for physical ports of tributary port units are shown in the following figure:
Inloop
Cross-Connect
Physical Port
Cross-Connect
Physical Port
Outloop
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-30
Equipment provisioning concepts
Miscellaneous
discrete inputs and outputs
...................................................................................................................................................................................................................................
Purpose
Miscellaneous discrete inputs (MDIs) and miscellaneous discrete outputs (MDOs) make
it possible to use a LambdaUnite ® MSS network element to monitor and control
external equipment co-located with the system.
Miscellaneous discrete inputs (MDIs)
LambdaUnite ® MSS systems feature a set of eight MDIs for user-defined applications.
MDIs can be used to monitor co-located equipment, a temperature sensor for example.
MDIs can thus be used to trigger the reporting of application-specific environmental
alarms.
Each MDI can be assigned a Name as well as a descriptive text (Environment
Message) identifying the type of environmental alarm condition in more detail. The
latter will be displayed in the WaveStar ® ITM-CIT NE Alarm List when a
corresponding alarm is present.
Furthermore, an Environmental Alarm Inversion parameter can be specified per MDI
which indicates whether an alarm is to be generated if the relay associated to the MDI
is switched on (activated) or if the relay is switched off (deactivated). A “door closed”
contact for example would activate the connected MDI whereas it might be intended
that an open door causes an alarm.
Miscellaneous discrete outputs (MDOs)
LambdaUnite ® MSS systems feature a set of eight MDOs for user-defined applications.
These MDOs are realized by means of relays (make contact, latching type).
MDOs can be used to control external equipment, an additional fan or an air-condition
system for example.
Modes of operation
MDOs can be operated in two different modes:
•
•
Automatic mode
The MDO has a probable cause assigned and becomes activated as soon as at least
one alarm with this probable cause is active.
Manual mode
The MDO is not bound to an alarm but can be activated/deactivated manually.
Transient behavior in the case of a restart or reset
As the MDOs are initialized to a hardware-defined state after a system restart (power
up) or a full reset of the controller (CTL), they may transiently indicate a wrong state
until the state before the reset is reestablished.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-31
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
Miscellaneous discrete inputs and outputs
Reference
Refer to “Provisioning of MDIs and MDOs” (p. 6-42) for detailed tasks related to MDI
and MDO provisioning.
MDI/MDO interface
The MDI/MDO interface is realized on the CI-CTL (connection interface of the
controller) as a 25-pin female D-subminiature connector.
Electrical specifications
The MDI ports are sensitive to passive switches (Ron ≤ 50 Ω, Roff ≥ 20 kΩ) or input
voltages up to –72 VDC (threshold voltage –3 VDC to –10 VDC). They are ESD safe up
to 2 kV.
The MDO ports are capable to switch 500 mA at 72 VDC and 2 A at 30 VDC. They
are ESD safe up to 2 kV.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-32
Equipment provisioning concepts
Equipment protection
CTL
equipment protection (duplex control)
...................................................................................................................................................................................................................................
Introduction
Optionally, a 1+1 equipment protection of the system and DCC control functions (SCF,
DCF) can be realized by adding a redundant Controller to a LambdaUnite ® MSS
system. Thus the reliability of the control functions can be increased.
Simplex control vs. Duplex control
In a simplex control configuration (one single, unprotected Controller), a defective
Controller leads to a loss of management communication to the affected network
element (NE), and may also lead to a loss of management communication to other
NEs.
Operations interfaces, such as the user panel, office alarm indicators or Miscellaneous
Discrete Inputs/Outputs (MDI/MDO) for example become unavailable as well.
Furthermore, some other system functions (for example XC equipment protection,
BLSR/MS-SPRing internal management communication, ONNS, or event logging) are
stopped.
The only way to regain the control in such a case is to replace the defective Controller.
In a duplex control configuration, the redundant (standby) Controller can take over the
full control functionality in case of a defect of the active Controller, and thus
automatically restore the control.
In addition, maintenance action can be executed more easily if the Controller which
needs to be temporarily removed has been switched into the standby role first.
To summarize, the major functions of duplex control are:
•
•
•
Automatic restoration of control in case of a defective active Controller.
Manual switching between both Controllers for maintenance reasons.
Seamless CTL hardware upgrade.
Static and dynamic role in a protection
The terms “worker” and “protection” are used to describe the static role within a
protection, whereas the terms “active” and “standby” are used to describe the current
(dynamic) role in a protection.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-33
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
CTL equipment protection (duplex control)
Preconditions for duplex control
Duplex control can only be activated if:
•
•
the currently installed NE software release supports duplex control, and
a CTL equipment protection group exists (i.e. two Controllers are equipped).
The LambdaUnite ® MSS NE software release 3.0 is the first NE software generic that
supports both simplex control and duplex control (depending on the shelf equipage).
NE software releases prior to the release 3.0 do not support duplex control but only
simplex control.
Controller variants
These Controller variants exist:
•
•
•
•
•
•
CTL/- with a 256-MByte NVM storage capacity (CompactFlash ® card).
CTL/2 with a 512-MByte NVM storage capacity (CompactFlash ® card).
CTL/3T with a 1-GByte NVM storage capacity (CompactFlash ® card).
CTL/3S with a 1-GByte NVM storage capacity (CompactFlash ® card).
CTL/4T with a 256-MByte NVM storage capacity (CompactFlash ® card),
redesigned hardware, fully compatible with the CTL/-.
CTL/4S with a 512-MByte NVM storage capacity (CompactFlash ® card),
redesigned hardware, fully compatible with the CTL/2.
The CTL/3 variants offer enhanced DCC capabilities (support of 180 DCCs) and a
greater NVM storage capacity in comparison with the other Controller variants.
The CTL/2, CTL/3S, and CTL/4S support ONNS applications while the CTL/-,
CTL/3T, and CTL/4T do not.
The use of a Controller of type CTL/3S or CTL/3T is required to support lower order
cross-connection units (LOXC).
It is not permitted to permanently operate a LambdaUnite ® MSS system in a mixed
Controller configuration for duplex control unless the CTL combination is explicitly
supported. Otherwise, a mixed Controller configuration is only temporarily possible
during an upgrade.
The following diagram shows the supported CTL combinations:
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-34
Equipment provisioning concepts
Standby
CTL/4T
CTL/4S
CTL/3T
CTL/3S
CTL/2
CTL/-
CTL equipment protection (duplex control)
CTL/CTL/2
CTL/3S
CTL/3T
CTL/4S
CTL/4T
Active
Supported CTL combination for normal operation
Temporarily supported CTL combination during upgrade
Important! Although ONNS applications are in principle possible in a simplex
control configuration, it is strongly recommended to operate the system in duplex
control mode for ONNS applications.
Creation of a CTL protection group
A CTL equipment protection group is created automatically when a second Controller
is plugged in or preprovisioned.
All duplex control related functionality is only operational if a CTL protection group
exists.
Important! Please observe the following rules:
1. Do not remove or reset the standby (inactive) CTL while a software download
or database restoration is in progress. Otherwise, the software download or
database restoration will be aborted.
2. Do not open the latches of both CTLs at the same time because this would lead
to the recovery of the master CTL to be blocked for approx. 15 minutes after
closing the latch again.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-35
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
CTL equipment protection (duplex control)
In case you have mistakenly opened both CTLs at the same time, close both
latches again and wait the 15 minutes in which the system is blocked.
Deletion of a CTL protection group
A CTL equipment protection group is deleted automatically when one of the two
Controllers is deprovisioned (plugged out).
Important! As the default alarm severity of the Duplex Control not Present
alarm is “Not reported”, no alarm will be reported when the standby Controller is
removed unless you explicitly change the alarm severity to a value other than “Not
reported”.
Mode of operation
The CTL equipment protection operates in 1+1 non-revertive mode.
Only one of the two Controllers can be active at a time, the redundant Controller
operates in a so-called “warm standby” mode.
The non-volatile memories (NVMs) on both Controllers are synchronized during a
synchronization process. Once the initial NVM synchronization process has finished,
all NVM-related operations (configuration and status updates of the NVM) are
performed synchronously. Thus, both Controllers share the same configuration and
status information (for example alarm supervision).
The standby Controller takes over the functionality of the previously active Controller
as soon as an autonomous or manual switch request is present (see switching criteria).
Active/standby role and slot assignment
In the case that two error free Controllers are present in the system, one takes on the
active role and the other one the standby role. The decision is made by
intercommunication between the two Controllers. A successful protection switch leads
to a swap of both roles.
There is no strict assignment between the CTL worker or protection slot (slot 11:
worker, slot 31: protection) and the active or standby role of the respective Controller.
In general, the active role assignment depends on the previous history.
The Controller which first becomes operational after a reset takes on the active role. If
both Controllers recover at the same time, for example after a system reset or an initial
system startup, then the Controller in the worker slot takes on the active role, and the
Controller in the protection slot takes on the standby role.
Switching criteria
Besides an autonomous protection switch in the case of an equipment failure condition
of the currently active Controller, also user-initiated switch requests are possible.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-36
Equipment provisioning concepts
CTL equipment protection (duplex control)
The following list summarizes the possible switch requests (autonomous and
user-initiated):
•
Autonomous protection switch in the case of an equipment failure condition (e.g.
hardware defect, or removal of the currently active Controller)
•
Manual To Working
Manual protection switch to the Controller in the CTL worker slot (slot 11)
•
Manual To Protection
Manual protection switch to the Controller in the CTL protection slot (slot 31)
•
Clear
Manual clearing of a previously performed protection switch
Important! A protection switch from the currently active to the standby Controller
is only possible if the standby Controller is in a position to take over the active
role. This is the reason why no provision is made for forced protection switches.
Furthermore, instead of using the manual switch commands, it is rather
recommended to provoke an autonomous protection switch (by removing the active
CTL) for triggering an intentional CTL equipment protection switch.
Alarm signaling after a CTL protection switch
After a CTL protection switch, all currently present alarms are redetected and reported
again. As a consequence the alarm signaling is as follows:
•
•
•
All currently present alarms, including those that were previously acknowledged by
means of the ACO button on the user panel, will be signaled again by the user
panel LEDs and the office alarm interfaces.
In the NE Alarm List, the same alarms are listed as before the CTL protection
switch. They are, however, marked with a new timestamp.
In the NE Alarm Log, alarms may appear twice, but with different timestamps,
without a clear notification between the two log entries.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-37
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
XC
equipment protection
...................................................................................................................................................................................................................................
Introduction
An active XC cross-connection and timing unit (XC160, XC320, or XC640) can be
protected by a standby unit. Both the cross-connnect function as well as the timing
function are protected on this way and form a single protection object. The equipment
protection process is fully performed by a central process in the Controller (CTL).
Support of ONNS applications
Only the XC160, XC320/B, and XC640 support ONNS applications. Especially when
the ONNS functionality is used, it is recommended to operate the cross-connection and
timing units in a 1+1 equipment protected configuration.
Static and dynamic role in a protection
The terms “worker” and “protection” are used to describe the static role within a
protection, whereas the terms “active” and “standby” are used to describe the current
(dynamic) role in a protection.
Creation
An XC equipment protection group is created automatically if
•
•
•
the second cross-connection and timing unit is inserted into the shelf, or
the two slots for the working and the protection cross-connection and timing unit
are preprovisioned, or
one of the two slots is autoprovisioned and the other one is preprovisioned.
Mode of operation
An XC equipment protection operates in 1+1 non-revertive mode.
Hot standby
The standby cross-connection and timing unit works in the so-called hot-standby mode,
which means both cross-connection and timing units work in parallel. The whole
configuration of the XC cross-connection and timing unit is broadcasted by the CTL to
both the active as well as the standby unit.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-38
Equipment provisioning concepts
XC equipment protection
Switch Info
The following switch commands are denied and the error message
“Command did not execute successfully. Execution of the following
commands failed” is displayed.
Active unit
Active switch request
Denied switch request
Worker
Forced Switch
Force To Protection
Protection
Forced Switch
Force To Working
Worker
Equipment Failed
Manual To Working
Protection
Equipment Failed
Manual To Working
Worker
Equipment Failed
Manual To Protection
Protection
Equipment Failed
Manual To Protection
Worker
Manual Switch
Manual To Protection
Protection
Manual Switch
Manual To Working
Worker
Forced Switch
Manual To Working
Protection
Forced Switch
Manual To Working
Worker
Forced Switch
Manual To Protection
Protection
Forced Switch
Manual To Protection
Furthermore, a forced switch to the standby side will be denied if {
•
•
•
{ the standby XC is only preprovisioned but not yet installed in its slot.
{ the latches of the standby XC are open.
{ the standby XC has been removed from its slot.
Deletion
An XC equipment protection group is deleted automatically, if one of the two
cross-connection and timing units is removed, and the respective slot is deprovisioned,
or if a preprovisioned slot is deprovisioned.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-39
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
XC equipment protection
Important XC equipment protection switching details
Please observe these functional details with respect to XC equipment protection
switching:
1. After an equipment protection switch, wait at least one minute before applying a
manual or forced equipment protection switch command to prevent traffic hits.
2. When a standby cross-connection and timing unit is inserted into the system (i.e.
when the latches are closed) it enters a warming-up state for several minutes.
During this warming-up state the system timing quality level is explicitely set to
DNU/DUS (Do not use for synchronization). If an equipment protection switch
occurs during the warming-up period of the standby unit the quality level at the
timing outputs of the system will change to DNU/DUS which could cause timing
rearrangements in other NEs.
Therefore, wait approx. 15 minutes after the insertion of a standby cross-connection
and timing unit before performing a manual or forced equipment protection switch.
3. On a cross-connection and timing unit, performance monitoring data is stored in the
current bin and one recent bin. Both cross-connection and timing units operate in a
hot-standby mode with regard to performance monitoring. However, no transfer of
the performance monitoring data is performed in case of an XC equipment
protection switch. Thus, an XC equipment protection switch may result in loss of
performance monitoring data, depending on the time the standby unit was plugged
into the system.
Prior to an (intentional) XC equipment protection switch the standby unit should
have been present in the system for a full 24-hours binning period. Otherwise,
performance monitoring data may be lost.
4. In rare cases, provisioning or deprovisioning of port units may cause an XC
equipment protection switch.
In-service hardware upgrades
These in-service hardware upgrades of cross-connection and timing units (in protected
and unprotected configurations) are supported:
From {
to {
XC160/-
XC320/-, XC320/A, XC320/B, or XC640/-
XC320/- or XC320/A
XC320/B
XC320/-, XC320/A or XC320/B
XC640/-
Please note that a downgrade of the cross-connection and timing units (i.e. reducing
the switch capacity of the system) is not possible, because it is not possible to decrease
the Maximum Switch Capacity parameter.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-40
Equipment provisioning concepts
STM-1E
equipment protection
...................................................................................................................................................................................................................................
Introduction
LambdaUnite ® MSS systems support electrical STM-1 interfaces (STM-1E) in
unprotected as well as protected configurations.
To accomplish STM-1E transmission (with or without 1+1 equipment protection),
EP155 port units can be used in combination with electrical connection interfaces
(ECI).
EP155 slot assignment
EP155 port units have to be installed in the upper row of the DUR shelf.
40
(W / P
or
P / W)
(W / P
or
P / W)
(W / P
or
P / W)
(W / P
or
P / W)
21 22 23 24 25 26 27 28
(W / P
or
P / W)
(W / P
or
P / W)
(W / P
or
P / W)
(W / P
or
P / W)
31 32 33 34 35 36 37 38 39
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19
In an STM-1E equipment protection configuration, the EP155 worker (W) and
protection (P) port units are adjacently inserted as pairs, as shown in the preceding
figure. The worker port unit can be flexibly configured on the right hand side or on the
left hand side of the protection port unit.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-41
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
STM-1E equipment protection
Worker and protection role
These rules apply concerning the worker and protection role assignment:
•
•
•
The worker role can be assigned flexibly to either of the two EP155 port units of
an STM-1E equipment protection group as long as there are no cross-connections,
timing reference assignments, transmission protection schemes, DCN or orderwire
connections, facility or cross-connection loopbacks, or transparent DCC connections
provisioned for any of the two EP155 port units.
Only one of the two EP155 port units of an STM-1E equipment protection group
may have cross-connections, timing reference assignments, transmission protection
schemes, DCN or orderwire connections, facility or cross-connection loopbacks, or
transparent DCC connections provisioned. This EP155 port unit can take on the
worker role.
If both EP155 port units of an STM-1E equipment protection group have
cross-connections, timing reference assignments, transmission protection schemes,
DCN or orderwire connections, facility or cross-connection loopbacks, or
transparent DCC connections provisioned, then none of these two port units can
take on the worker role. In that situation, all these provisionings need to be
removed for at least one of the two EP155 port units.
Electrical connection interfaces
The STM-1E input and output ports are located on the electrical connection interfaces.
There are two types of electrical connection interfaces:
ECI/155ME8
16-ports variant for unprotected configurations only (see “Specific
STM-1E configuration aspects” (p. 5-44)).
ECI/155MP8
8-ports variant for protected and unprotected configurations (see
“Specific STM-1E configuration aspects” (p. 5-44)).
The electrical connection interfaces have to be installed in the rear-side slots 61, 63,
65, 67, 72, 74, 76, and 78.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-42
Equipment provisioning concepts
STM-1E equipment protection
80
69
70
78
76
56
74
72
54
52
67
51
65
45
63
61
43
41
Important! The electrical connection interfaces and their inventory data are only
accessible when at least one EP155 port unit is installed in the corresponding
front-side slot pair.
Association between EP155 and ECI slots
The association between two adjacent EP155s and the a rear-side electrical connection
interface (ECI) is as follows:
EP155 slot pair
ECI slot
21/22
61
23/24
63
25/26
65
27/28
67
32/33
72
34/35
74
36/37
76
38/39
78
STM-1E equipment protection groups
Up to 8 STM-1E equipment protection groups can exist per shelf.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-43
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
STM-1E equipment protection
Each STM-1E equipment protection group is formed by two adjacent EP155s in
combination with a rear-side ECI, as listed in “Association between EP155 and ECI
slots” (p. 5-43).
Please also refer to “Specific STM-1E configuration aspects” (p. 5-44).
Mode of operation
The STM-1E equipment protection operates in 1+1 non-revertive mode.
Creating an STM-1E equipment protection group
STM-1E equipment protection groups need to be created manually.
Static and dynamic role in a protection
The terms “worker” and “protection” are used to describe the static role within a
protection, whereas the terms “active” and “standby” are used to describe the current
(dynamic) role in a protection.
Specific STM-1E configuration aspects
These are the supported combinations of EP155 port units with electrical connection
interfaces:
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-44
Equipment provisioning concepts
STM-1E equipment protection
Protected
8 ports
8 ports
ECI/155MP8
EP155
(W)
ECI/155MP8
EP155
(P)
EP155
(P)
EP155
(W)
Unprotected
8 ports
8 ports
ECI/155MP8
ECI/155MP8
EP155
EP155
➀
16 ports
(8 ports used)
16 ports
ECI/155ME8
EP155
EP155
ECI/155ME8
16 ports
(8 ports used)
ECI/155ME8
EP155
EP155
➀
Legend:
1
These slots may be empty, or equipped with an optical SDH/SONET or Gigabit
Ethernet port unit, but not with an EP51 or EP155 port unit.
Important! When installing EP155 port units without having an ECI installed,
unexpected ECI Comm Failure and Loss of Signal alarms may be reported.
Therefore, always first install the ECI before installing the EP155 port units!
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-45
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
STM-1E equipment protection
STM-1E protected configuration
There is one dedicated configuration for STM-1E equipment protection:
•
Two EP155 port units in a universal slot pair as listed in “Association between
EP155 and ECI slots” (p. 5-43), and an ECI/155MP8 electrical connection interface
in the corresponding ECI slot.
STM-1E unprotected configurations
There are five possible unprotected configurations:
•
•
One EP155 port unit in either of the two slots of a universal slot pair as listed in
“Association between EP155 and ECI slots” (p. 5-43), and either of the two
possible electrical connection interfaces (ECI/155MP8 or ECI/155ME8) in the
corresponding ECI slot (→ four possible combinations).
Two EP155 port units in a universal slot pair as listed in “Association between
EP155 and ECI slots” (p. 5-43), and an ECI/155ME8 electrical connection interface
in the corresponding ECI slot. This is the only configuration where 16 STM-1E
ports are available.
Configuration changes
These configuration changes are possible without impacting the service:
•
•
•
•
ECI/155ME8 with 1 × EP155 → ECI/155ME8 with 2 × EP155.
This configuration change can be achieved by adding the second EP155.
ECI/155ME8 with 1 × EP155 and empty adjacent slot → ECI/155ME8 with
1 × EP155 and an optical SDH/SONET or Gigabit Ethernet port unit in the
adjacent slot.
This configuration change can be achieved by adding the optical SDH/SONET or
Gigabit Ethernet port unit.
ECI/155MP8 with 1 × EP155 → ECI/155MP8 with 2 × EP155.
This configuration change can be achieved by adding the second EP155. In this
case, you also need to create the STM-1E equipment protection group.
ECI/155MP8 with 1 × EP155 and empty adjacent slot → ECI/155MP8 with
1 × EP155 and an optical SDH/SONET or Gigabit Ethernet port unit in the
adjacent slot.
This configuration change can be achieved by adding the optical SDH/SONET or
Gigabit Ethernet port unit.
Furthermore, observe these rules concerning configuration changes:
•
If you want to convert an unprotected configuration with two EP155s
(ECI/155ME8 with 2 × EP155) into a protected configuration (ECI/155MP8 with
2 × EP155), then:
1. Delete all cross-connections, DCC terminations, orderwire and user byte
assignments etc. for the EP155 port unit in the protection slot.
2. Remove and deprovision both EP155 port units.
3. Replace the ECI/155ME8 by an ECI/155MP8.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-46
Equipment provisioning concepts
STM-1E equipment protection
4. Re-install the EP155 port units.
•
5. Create the STM-1E equipment protection group. Creating an STM-1E
equipment protection group is not possible as long as both EP155 port units
have cross-connections, DCC terminations, orderwire and user byte assignments
etc. assigned.
If you want to convert a protected configuration (ECI/155MP8 with 2 × EP155)
into an unprotected configuration with two EP155s (ECI/155ME8 with
2 × EP155), then:
1. Delete all cross-connections, DCC terminations, orderwire and user byte
assignments etc.
2. delete the STM-1E equipment protection group.
3. Remove and deprovision both EP155 port units.
4. Replace the ECI/155MP8 by an ECI/155ME8.
5. Re-install the EP155 port units.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-47
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
DS3/EC-1
equipment protection
...................................................................................................................................................................................................................................
Introduction
LambdaUnite ® MSS systems support electrical DS3 and EC-1 interfaces in unprotected
as well as protected configurations.
To accomplish DS3 or EC-1 transmission (with or without 1+1 equipment protection),
EP51 port units are used in combination with ECI51 electrical connection interfaces.
Each port of an EP51 port unit can separately be configured for the transport of one of
the following signals:
DS3
Plesiochronous 44.736 Mbps (SONET)
EC-1
Synchronous 51.840 Mbps (SONET)
An EP51 port unit can be operated in a mixed configuration with DS3 and EC-1 on
different ports.
Important! No traffic will be possible via a DS3/EC-1 port of an EP51 port unit if
a signal of the wrong type is applied. When a DS3 signal is applied to a port in
EC-1 mode then a Loss of Frame alarm will be reported. However, no specific
alarm will be reported when an EC-1 signal is applied to a port in DS3 mode.
Therefore, always ensure to apply a signal of the correct type to a DS3/EC-1 port
on an EP51 port unit, i.e. a signal in compliance with the port configuration (EC-1
signals to ports in EC-1 mode, DS3 signals to ports in DS3 mode).
EP51 slot assignment
EP51 port units can be inserted only in the upper row of the DUR shelf.
40
(W / P
or
P / W)
(W / P
or
P / W)
(W / P
or
P / W)
(W / P
or
P / W)
21 22 23 24 25 26 27 28
(W / P
or
P / W)
(W / P
or
P / W)
(W / P
or
P / W)
(W / P
or
P / W)
31 32 33 34 35 36 37 38 39
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-48
Equipment provisioning concepts
DS3/EC-1 equipment protection
In a DS3/EC-1 equipment protection configuration, the EP51 worker (W) and
protection (P) port units are adjacently inserted as pairs, as shown in the preceding
figure. The worker port unit can be flexibly configured on the right hand side or on the
left hand side of the protection port unit.
Worker and protection role
These rules apply concerning the worker and protection role assignment:
•
•
•
The worker role can be assigned flexibly to either of the two EP51 port units of an
DS3/EC-1 equipment protection group as long as there are no cross-connections,
timing reference assignments, transmission protection schemes, DCN or orderwire
connections, facility or cross-connection loopbacks, or transparent DCC connections
provisioned for any of the two EP51 port units.
Only one of the two EP51 port units of an DS3/EC-1 equipment protection group
may have cross-connections, timing reference assignments, transmission protection
schemes, DCN or orderwire connections, facility or cross-connection loopbacks, or
transparent DCC connections provisioned. This EP51 port unit can take on the
worker role.
If both EP51 port units of an DS3/EC-1 equipment protection group have
cross-connections, timing reference assignments, transmission protection schemes,
DCN or orderwire connections, facility or cross-connection loopbacks, or
transparent DCC connections provisioned, then none of these two port units can
take on the worker role. In that situation, all these provisionings need to be
removed for at least one of the two EP51 port units.
Electrical connection interfaces
The DS3/EC-1 input and output ports are located on the ECI51/MP72 electrical
connection interfaces.
The ECI51/MP72 electrical connection interfaces must be installed in the rear-side slot
pairs 61/63, 63/65, 65/67, 72/74, 74/76, or 76/78.
Important! The electrical connection interfaces and their inventory data are only
accessible if at least one EP51 port unit is installed in the corresponding front-side
slot.
EP51/ECI51 slot assignments
The association between the slots for the EP51s and the rear-side electrical connection
interface (ECI51) slots is as follows:
EP51 slots
ECI51 slots
ECI51 position
21 ... 24
61/63
63
25 ... 28
65/67
67
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-49
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
DS3/EC-1 equipment protection
EP51 slots
ECI51 slots
ECI51 position
32 ... 35
72/74
74
36 ... 39
76/78
78
23 ... 26
63/65
65
34 ... 37
74/76
76
ECI51
Services 2 ECI
and 4 EP51 slots
ECI position 76
Rear view
(ECI51 cards)
ECI51
Services 2 ECI
and 4 EP51 slots
ECI position 78
Rear view
(ECI51 slots)
Front view
(EP51 slots)
78
39
ECI51
Services 2 ECI
and 4 EP51 slots
ECI position 74
76
38
37
Top row
74
36
35
Using this ECI position
prevents a fullfill of
DS3s in this quadrant.
This would be ECI
position 76
33
ECI51
Services 2 ECI
and 4 EP51 slots
ECI position 67
2)
2nd
3rd3)
72
34
ECI51
Services 2 ECI
and 4 EP51 slots
ECI position 65
1)
32
Bottom
67
4)
28
ECI51
Services 2 ECI
and 4 EP51 slots
ECI position 63
65
27
26
63
25
24
61
23
22
21
Using this ECI position
prevents a fullfill of
DS3s in this quadrant.
This would be ECI
position 65
1)
Top row represents ECI51 cards (DS3 paddle boards) that could be installed in positions 65 and/or 76 on the third row.
Second row represents ECI51 cards (DS3 paddle boards) that could be installed in positions 63, 67, 74, and/or 78.
3)
Third row represents ECI51 slots on the rear of the LambdaUnite® shelf where ECI51 cards (DS3 paddle boards) can be installed.
4)
Bottom row represents the channel slots on the front of the LambdaUnite® shelf and are shown under the ECI51 slots that serve them.
2)
NOTE:
If ECI51 position 65 is used, positions 63 and 67 are not available. If ECI51 position 76 is used, positions 74 and 78 are not available.
DS3/EC-1 equipment protection groups
Up to 8 DS3/EC-1 equipment protection groups can be set up per shelf.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-50
Equipment provisioning concepts
DS3/EC-1 equipment protection
Each DS3/EC-1 equipment protection group is formed by two adjacent EP51s, cf.
“EP51 slot assignment” (p. 5-48), in combination with half a rear-side ECI51, as listed
in the preceding table “EP51/ECI51 slot assignments” (p. 5-49).
Please also refer to “Specific EP51 configuration aspects” (p. 5-51).
Mode of operation
The DS3/EC-1 equipment protection operates in 1+1 non-revertive mode.
Creating a DS3/EC-1 equipment protection group
DS3/EC-1 equipment protection groups need to be created manually.
Static and dynamic role in a protection
The terms “worker” and “protection” are used to describe the static role within a
protection, whereas the terms “active” and “standby” are used to describe the current
(dynamic) role in a protection.
Specific EP51 configuration aspects
There is no restriction regarding the allocation of the worker and protection EP51 port
units within the protection slot pair as long as the rules concerning the worker and
protection role assignment as listed in “EP51 slot assignment” (p. 5-48) are observed.
Therefore all combinations of EP51 port units with ECI51 electrical connection
interfaces are supported for protected configurations:
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-51
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
DS3/EC-1 equipment protection
Digital Distribution Frame (DDF)
36 ports
36 ports
Digital Distribution Frame (DDF)
ECI51/MP72
EP51
(W)
EP51
(P)
EP51
(W)
ECI51/MP72
EP51
(P)
Digital Distribution Frame (DDF)
36 ports
36 ports
EP51
(P)
EP51
(W)
EP51
(W)
EP51
(W)
EP51
(P)
EP51
(W)
Digital Distribution Frame (DDF)
36 ports
36 ports
ECI51/MP72
EP51
(P)
36 ports
36 ports
ECI51/MP72
EP51
(P)
EP51
(W)
EP51
(P)
EP51
(P)
EP51
(W)
For unprotected configurations the following combinations of EP51 port units with
ECI51 electrical connection interfaces are supported:
Digital Distribution Frame (DDF)
36 ports
36 ports
ECI51/MP72
EP51
Digital Distribution Frame (DDF)
36 ports
36 ports
ECI51/MP72
EP51
➀
➀
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-52
Equipment provisioning concepts
DS3/EC-1 equipment protection
Digital Distribution Frame (DDF)
36 ports
36 ports
Digital Distribution Frame (DDF)
36 ports
ECI51/MP72
36 ports
ECI51/MP72
EP51
EP51
➀
➀
Digital Distribution Frame (DDF)
36 ports
36 ports
Digital Distribution Frame (DDF)
36 ports
ECI51/MP72
EP51
ECI51/MP72
EP51
EP51
➀
➀
Digital Distribution Frame (DDF)
36 ports
36 ports
EP51
➀
EP51
Digital Distribution Frame (DDF)
36 ports
ECI51/MP72
EP51
36 ports
36 ports
ECI51/MP72
EP51
EP51
➀
Legend:
1
These slots may be empty, or equipped with an optical SDH/SONET or Gigabit
Ethernet port unit, but not with an EP51 or EP155 port unit.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-53
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
DS3/EC-1 equipment protection
Any mix of protected and unprotected configurations is possible, maintaining the pair
pattern of the EP51 protection slot pairs, as displayed in “EP51 slot assignment”
(p. 5-48). The following figure shows examples for mixed configurations:
Digital Distribution Frame (DDF)
36 ports
36 ports
Digital Distribution Frame (DDF)
36 ports
ECI51/MP72
EP51
(W)
EP51
36 ports
ECI51/MP72
EP51
(P)
EP51
(P)
EP51
(W)
EP51
➀
➀
Legend:
1
These slots may be empty, or equipped with an optical SDH/SONET or Gigabit
Ethernet port unit, but not with an EP51 or EP155 port unit.
Important!
1. Do not use two EP51 port units in adjacent slots with an ECI51 installed but
without having a DS3/EC-1 equipment protection group created. Such an
unsupported configuration may lead to a loss of traffic.
2. When installing EP51 port units without having an ECI51 installed, unexpected
ECI Comm Failure and Loss of Signal alarms may be reported. Therefore,
always first install the ECI51 before installing the EP51 port units!
DS3/EC-1 protected configurations
Protected DS3 configurations can be set up as follows:
•
Two EP51 port units in a universal slot pair as listed in “EP51 slot assignment”
(p. 5-48), and an ECI51 in the corresponding ECI slot (half of its capacity used),
cf. “EP51/ECI51 slot assignments” (p. 5-49).
DS3/EC-1 unprotected configurations
Unprotected DS3 configurations can be set up as follows:
•
One EP51 port unit in one of the two slots of a universal slot pair as listed in
“EP51 slot assignment” (p. 5-48), and an ECI51 in the corresponding ECI slot (half
of its capacity used), cf. “EP51/ECI51 slot assignments” (p. 5-49).
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-54
Equipment provisioning concepts
DS3/EC-1 equipment protection
Configuration changes
These configuration changes are possible without impacting the service:
•
•
Half an ECI51 with 1 × EP51 (unprotected) → ECI51 with 2 × EP51 (protected).
This configuration change can be achieved by adding the second EP51 in the
respective protection pair slot, cf. “EP51 slot assignment” (p. 5-48), and creating
the DS3/EC-1 equipment protection group
Half an ECI51 with 1 × EP51 and empty adjacent slot → ECI51 with 1 × EP51
and an optical SDH/SONET or Gigabit Ethernet port unit in the adjacent slot.
This configuration change can be achieved by adding the optical SDH/SONET or
Gigabit Ethernet port unit.
Note that the maximum number of active DS3/EC-1 ports per LambdaUnite ® MSS NE
is 288 (4 ECI51 with 72 ports each, 8 EP51 with 36 ports each), regardless if protected
or not.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-55
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
LOXC
equipment protection
...................................................................................................................................................................................................................................
Terminology
“LOXC” is the collective term for lower order cross-connection units (LOXC/1,
LOXC40G2S/1, LOXC40G3S/1).
“LOXC40” is the collective term for lower order cross-connection units with a
switching capacity of 40 Gbps (LOXC40G2S/1, LOXC40G3S/1).
Lower order cross-connections
LambdaUnite ® MSS systems support switching of lower order cross-connections.
Lower order tributaries cannot be terminated within the LambdaUnite ® MSS system,
but are embedded in substructured higher order transport signals which need to be
terminated before the embedded lower order signals can be cross-connected.
In the input direction, the higher order transport signals are terminated before the
contained lower order tributaries are cross-connected. In the output direction, the lower
order signals are integrated into the substructure of a newly generated higher order
transport signal.
Lower order cross-connections can be unidirectional or bidirectional.
Signal rates
These types of lower order tributaries are supported:
•
•
•
VT1.5 (SONET)
VC-12 (SDH)
VC-3 (SDH)
These types of substructured higher order transport signals are supported:
•
•
STS-1 (SONET), carrying VT1.5 signals
VC-4 (SDH), carrying VC-3 or VC-12 signals, or a mix of VC-3 and VC-12
Hardware prerequisites
The usage of a lower order cross-connection unit (LOXC) in combination with a
Controller of type CTL/3S or CTL/3T is required.
Important! An LOXC can support either SONET or SDH traffic.
Equipment protection groups may be configured for both the LOXC as well as the
Controller.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-56
Equipment provisioning concepts
LOXC equipment protection
LOXC switching capacity
When an LOXC is inserted into a permissible slot (see “Specific LOXC equipage
rules” (p. 5-57)), then it becomes autoprovisioned with a switching capacity of 0 Gbps.
Important! You can activate at most one LOXC by explicitly setting the switching
capacity to 15 Gbps or 40 Gbps, respectively. A second LOXC automatically may
get a switching capacity of 15 Gbps or 40 Gbps assigned when it is included in an
LOXC equipment protection group as the protection unit. However, only one LOXC
may be active at a time.
LOXC equipment protection
Please also refer to “Specific LOXC equipage rules” (p. 5-57).
Mode of operation
The LOXC equipment protection operates in 1+1 non-revertive mode.
Activating of an LOXC
In order to activate an LOXC, its lower order switching capacity must be set to a value
different from 0.
Creating an LOXC equipment protection group
LOXC equipment protection groups need to be created manually.
Static and dynamic role in a protection
The terms “worker” and “protection” are used to describe the static role within a
protection, whereas the terms “active” and “standby” are used to describe the current
(dynamic) role in a protection.
LOXC in-service upgrade
Please note that no LOXC in-service upgrade is supported in the present software
release.
Specific LOXC equipage rules
LOXC lower order cross-connection units must be installed in dedicated universal slots
or slot combinations. Moreover, which universal slots or slot combinations support the
lower order cross-connection functionality also depends on the maximum switching
capacity of the system.
These are the supported slot combinations for the usage of lower order
cross-connection units ((W): worker; (P): protection):
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-57
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
Max. switching capacity
LXC160
LXC320
Option 1
(1)
LOXC equipment protection
Slot assignment
LOXC (W)
LOXC (P)
Remarks and additional equipage guidelines
37
39
The slots 36 and 38 must remain empty.
4
19
The slots 3 and 18 must remain empty.
Bear in mind, that the slots 2 and 17 may be required at a later
date in case an in-service upgrade is planned towards LOXC
units which occupy 3 slots.
Option 2
17
19
Alternative equipage if slot 4 is occupied.
The slots 16 and 18 must remain empty.
Option 3
LXC640
(2)
37
39
The slots 36 and 38 must remain empty.
Option 1(1)
4
19
Bear in mind, that the slots 3 and 18 may be required at a later
date in case an in-service upgrade is planned towards LOXC
units which occupy 2 slots.
Option 2(3)
17
19
Bear in mind, that the slots 16 and 18 may be required at a later
date in case an in-service upgrade is planned towards LOXC
units which occupy 2 slots.
Option 3(4)
18
19
–
Option 4(5)
37
39
Bear in mind, that the slots 36 and 38 may be required at a later
date in case an in-service upgrade is planned towards LOXC
units which occupy 2 slots.
Notes:
1.
Option 1 is the preferred option.
2.
LXC320, option 3, is the preferred option for a seamless upgrade from LXC160 to LXC320.
3.
LXC640, option 2, is the preferred option for a seamless upgrade from LXC320 to LXC640.
4.
LXC640, option 3, is the preferred option for maximized automatic I/O slot usage by Telcordia ®
Technologies.
5.
LXC640, option 4, is the preferred option for a seamless upgrade from LXC160 to LXC640.
Important! There may be at most one active LOXC. A second LOXC may be
configured for protection purposes. This implies that at most one LOXC equipment
protection group may exist.
The following figures serve to visualize the permissible LOXC slot positions (W:
worker, P: protection), depending on the system’s maximum switching capacity:
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-58
Universal slot
XC (W) slot
XC (P) slot
(W)
4
5
6
7
8
9
10 11 12 13 14 15 16 17 18 19
(W)
(W)
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
XC (W) slot
XC (P) slot
2
3
4
5
6
7
8
9
10 11 12 13 14 15 16 17 18 19
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
CTL (P) slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
(W)
Universal slot
Universal slot
40
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
1
CTL (W) slot
Universal slot
40
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
21 22 23 24 25 26 27 28
Universal slot
CTL (P) slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
21 22 23 24 25 26 27 28
CTL (W) slot
Universal slot
3
Universal slot
Universal slot
2
Universal slot
Universal slot
1
Universal slot
Universal slot
Equipment provisioning concepts
LOXC equipment protection
LXC160:
User panel
(P)
31 32 33 34 35 36 37 38 39
front view
LXC320:
User panel
(P)
31 32 33 34 35 36 37 38 39
front view
(P)
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-59
Issue 2, July 2008
See notice on first page
Equipment provisioning concepts
LOXC equipment protection
LXC640:
User panel
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
(P)
XC (P) slot
4
5
6
7
8
9
10 11 12 13 14 15 16 17 18 19
(W)
Universal slot
XC (W) slot
3
Universal slot
Universal slot
2
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
1
CTL (W) slot
Universal slot
Universal slot
31 32 33 34 35 36 37 38 39
Universal slot
21 22 23 24 25 26 27 28
Universal slot
(W)
CTL (P) slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
Universal slot
40
(W) (W) (P)
front view
Preconditions for creating an LOXC equipment protection group
Before an LOXC equipment protection group can be created, the following
preconditions must all be fulfilled:
•
•
•
At least one cross-connection and timing unit (XC) is provisioned.
The potential worker LOXC
– has been provisioned,
– is not yet involved in an LOXC equipment protection group, and
– has already been activated (switching capacity is 15 Gbps or 40 Gbps).
The potential protection LOXC
– has been provisioned, and
– has a switching capacity of 0 Gbps (i.e. is currently inactive).
Switch requests
Besides an autonomous protection switch in the case of an equipment failure condition
of the currently active LOXC, also user-initiated switch requests are possible.
The following list summarizes the possible switch requests (autonomous and
user-initiated):
•
Autonomous protection switch in the case of an equipment failure condition (e.g.
hardware defect, or removal of the currently active LOXC)
•
Manual To Working
Manual protection switch to the LOXC in the worker slot.
•
Manual To Protection
Manual protection switch to the LOXC in the protection slot.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
5-60
Equipment provisioning concepts
•
LOXC equipment protection
Forced To Working
Forced protection switch to the LOXC in the worker slot.
•
Forced To Protection
Forced protection switch to the LOXC in the protection slot.
•
Clear
Manual clearing of a previously performed protection switch.
Important LOXC equipment protection switching details
Please observe these functional details with respect to LOXC equipment protection
switching:
1. Note that a manual or forced LOXC equipment protection switch causes short
traffic hits even if the destination LOXC works properly.
The traffic is interrupted for a few milliseconds. B3 errors are detected. No alarm
will be raised.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
5-61
Issue 2, July 2008
See notice on first page
6
E quipment provisioning tasks
6
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter informs about how to perform the most common tasks related to
equipment provisioning.
Contents
Provisioning of slots and SFP modules
6-3
To view a list of slots
6-3
Port provisioning
6-4
To view a list of physical ports
6-4
To view a list of logical ports
6-5
To view a list of loopback-enabled ports
6-6
To provision or deprovision a loopback on a port
6-7
To modify the parameters of a physical or logical port
6-9
Parameters for SDH/SONET/PDH ports
6-11
Parameters for Ethernet ports
6-26
Parameters for VCG ports
6-30
Provisioning of NE event controls
6-38
To inhibit the forwarding of autonomous messages
6-38
To allow the forwarding of autonomous messages
6-40
Provisioning of MDIs and MDOs
6-42
To retrieve the MDO configuration
6-42
To set the MDO configuration
6-44
To switch on an MDO
6-46
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-1
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
Overview
To switch off an MDO
6-48
To retrieve the MDO state
6-50
To retrieve the MDI configuration
6-52
To set the MDI configuration
6-54
Equipment protection
6-56
To retrieve equipment protection group information
6-56
To add an equipment protection group
6-59
To operate an equipment protection group
6-61
To release an equipment protection group
6-63
To delete an equipment protection group
6-65
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-2
Equipment provisioning tasks
Provisioning of slots and SFP modules
To
view a list of slots
...................................................................................................................................................................................................................................
When to use
Use this task to view a list of slot information for a selected NE.
Task
...................................................................................................................................................................................................
1
Use the object links to follow this path: Network Elements → Equipment.
Result: The Search for Equipment page is displayed.
...................................................................................................................................................................................................
2
Do the following:
In the NE type field, select a type of NE.
In the NE name field, select the name of the target NE.
In the Equipment type field, select Slot/Circuit pack.
For the Search by field, select the option Equipment ID.
5. Leave the Equipment ID field empty.
6. Click Search.
1.
2.
3.
4.
Result: The Equipment - Slots/Circuit Packs page is displayed. It includes a list
of slots for the selected NE.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-3
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
Port provisioning
To
view a list of physical ports
...................................................................................................................................................................................................................................
When to use
Use this task to view a list of physical ports.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network. The Network Map is displayed.
Right-click an NE icon. From the resulting Node menu, select Network Element
→ Ports.
Use the object links to follow this path: Network Elements → Ports.
Result: The Search for Ports page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to begin to specify the criteria for your search.
1. In the NE type field, select a type of NE (if not already present).
2. In the NE name field, select the name of an NE (if not already present).
3. In the Port type field, select Physical.
...................................................................................................................................................................................................
3
If{
then{
you want the search to return a
single port,
in the Search by field, select Port ID. In the Port ID
field, enter the port ID. Click Search.
you want the search to return a
list of multiple ports,
in the Search by field, select Port list. Select a Port
rate and/or a Slot / Circuit Pack. Click Search.
Result: The list at the bottom of the Ports page is populated with a list of ports in
the NE that meet your search criteria.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-4
Equipment provisioning tasks
To
view a list of logical ports
...................................................................................................................................................................................................................................
When to use
Use this task to view a list of logical ports.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network. The Network Map is displayed.
Right-click an NE icon. From the resulting Node menu, select Network Element
→ Ports.
Use the object links to follow this path: Network Elements → Ports.
Result: The Search for Ports page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to begin to specify the criteria for your search.
1. In the NE type field, select a type of NE (if not already present).
2. In the NE name field, select the name of an NE (if not already present).
3. In the Port type field, select Logical.
...................................................................................................................................................................................................
3
If{
then{
you want the search to return a
single port,
in the Search by field, select Port ID. In the Port ID
field, enter the port ID. Click Search.
you want the search to return a
list of multiple ports,
in the Search by field, select Port list. Select a Port
rate, a Parent port rate, and a Slot / Circuit Pack.
Click Search.
Result: The list at the bottom of the Ports page is populated with a list of ports in
the NE that meet your search criteria.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-5
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
To
view a list of loopback-enabled ports
...................................................................................................................................................................................................................................
When to use
Use this task to view a list of loopback-enabled ports.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network. The Network Map is displayed.
Right-click an NE icon. From the resulting Node menu, select Network Elements
→ Ports.
Use the object links to follow this path: Network Elements → Ports.
Result: The Search for Ports page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to begin to specify the criteria for your search.
1. In the NE type field, select a type of NE (if not already present).
2. In the NE name field, select the name of an NE (if not already present).
...................................................................................................................................................................................................
3
In the Search by field, select Port list.
...................................................................................................................................................................................................
4
In the Port type field, select Physical.
...................................................................................................................................................................................................
5
Make a selection in the Port rate and the Slot/Circuit Pack field. If not selectable,
change the selection of the Port rate.
...................................................................................................................................................................................................
6
In the Filter by field, select the Loopback provisioned option button.
...................................................................................................................................................................................................
7
Click Search.
Result: The list at the bottom of the Ports page is populated with a list of
loopback enabled ports. If the list is empty, no loopbacks are provisioned.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-6
Equipment provisioning tasks
To
provision or deprovision a loopback on a port
...................................................................................................................................................................................................................................
When to use
Use this task to provision or deprovision a loopback on a port.
CAUTION
Service-disruption hazard
Provisioning a loopback may result in a disruption of traffic, timing, and the possible
loss of DCN connections.
Before you begin
Loopback is supported only on physical ports.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network. The Network Map is displayed.
Right-click an NE icon. From the resulting Node menu, select Network Element
→ Ports.
Use the object links to follow this path: Network Elements → Ports.
Result: The Search for Ports page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to begin to specify the criteria for your search.
1. In the NE type field, select a type of NE (if not already present).
2. In the NE name field, select the name of an NE (if not already present).
3. In the Port type field, select Physical.
...................................................................................................................................................................................................
3
If{
then{
you want the search to return a
single port,
in the Search by field, select Port ID. In the Port ID
field, enter the port ID. Click Search.
you want the search to return a
list of multiple ports,
in the Search by field, select Port list. Select a Port
rate, a Parent port rate, and a Slot / Circuit Pack.
Click Search.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-7
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
To provision or deprovision a loopback on a port
Result: The list at the bottom of the Ports page is populated with a list of ports in
the NE that meet your search criteria.
...................................................................................................................................................................................................
4
The Native name column of the table lists the names of the ports. Click the radio
button next to the port on which you wish to provision loopback.
...................................................................................................................................................................................................
5
From the Go menu, select Provision loopback and click Go.
Result: The Loopback Provisioning page is displayed.
...................................................................................................................................................................................................
6
In the Loopback type field, click the radio button in either of the following fields:
•
•
Inloop Loopback
Outloop Loopback
Result: The Operation field changes to Provision or Deprovision, depending on
your selection, and whether an inloop loopback or outloop loopback is provisioned
on the port.
...................................................................................................................................................................................................
7
In the Operation field, select Provision or Deprovision and click Submit.
Important! The NE will reject loopback creation if the port is in service.
Result: A confirmation window is displayed asking you to confirm the provisioning
or deprovisioning.
...................................................................................................................................................................................................
8
Click Yes.
Result: A progress indication followed by a confirmation is issued in the Message
section of the page, and the loopback is provisioned or deprovisioned on the port.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-8
Equipment provisioning tasks
To
modify the parameters of a physical or logical port
...................................................................................................................................................................................................................................
When to use
Use this task to modify the parameters of a port.
CAUTION
Service-disruption hazard
Modification of port parameters may be traffic affecting.
Before starting to modify port parameters, make sure that the port is not in use. The
traffic provided on the respective path must have previously been removed (for example
rerouted to another path).
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network. The Network Map is displayed.
Right-click an NE icon. From the resulting Node menu, select Network Element
→ Ports.
Use the object links to follow this path: Network Elements → Ports.
Result: The Ports page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to begin to specify the criteria for your search.
1. In the NE type field, select a type of NE.
2. In the NE name field, select the name of an NE.
3. In the Port type field, select Physical or Logical, respectively, depending on the
type of port you want to modify.
...................................................................................................................................................................................................
3
If{
then{
you want the search to return a
single port,
in the Search by field, select Port ID. In the Port ID
field, enter the port ID. Click Search.
you want the search to return a
list of multiple ports,
in the Search by field, select Port list. Select a Port
rate, a Parent port rate, and a Slot / Circuit Pack.
Click Search.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-9
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
To modify the parameters of a physical or logical port
Result: The list at the bottom of the Ports page is populated with a list of ports in
the NE that meet your search criteria.
...................................................................................................................................................................................................
4
The Native name column of the table lists the names of the ports. Each name is a
hyperlink.
Do one of the following:
•
•
Click the name of the port you wish to modify.
Click the radio button next to the port you wish to modify. From the Go menu,
select View/modify port parameters and click Go.
Result: The View/modify port page is displayed.
...................................................................................................................................................................................................
5
Change the entries or selections for any modifiable port parameters.
Detailed information about the parameters to be modified and the possible values is
provided in the following sections:
•
•
•
“Parameters for SDH/SONET/PDH ports” (p. 6-11).
“Parameters for Ethernet ports” (p. 6-26).
“Parameters for VCG ports” (p. 6-30).
...................................................................................................................................................................................................
6
Click Submit.
Result: A confirmation window is displayed asking you to confirm the
modification.
...................................................................................................................................................................................................
7
Click Yes.
Result: The port parameters are modified, and a confirmation is issued in the
Messages panel. The Job Updates page is displayed and reports the status of the
modification of the port parameters.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-10
Equipment provisioning tasks
Parameters
for SDH/SONET/PDH ports
...................................................................................................................................................................................................................................
Introduction
This section lists the parameters that can be modified for SDH, SONET, or PDH ports.
Note that not all parameters and possible values apply to all port types, plug-in units,
and network element configurations.
For a number of parameters, the network elements can report the value not applicable.
This value is for information purposes only, it cannot be entered.
Transmission
In the Transmission section of the Port page, the following parameters can be
modified:
Parameter
Function
Possible values
Port mode
Indicates the monitoring state of the
specified port.
Depending on the port rate and type
the following values are possible:
FEC type
Electrical interface type
Transmitted interface standard
Inloop/Facility loopback
•
on – the port is being monitored.
•
auto – the port is ready to
transition into a monitored state,
when a signal is detected.
•
off – the port is not being
monitored.
Specifies the FEC type on a DWDM
port of a G.709 10G OT.
RS_FEC – out-of-band FEC making
use of an RS(255,239) reed-solomon
code; V_FEC – Lucent-proprietary
enhanced forward error correction
(EFEC, also referred to as ultra
forward error correction, UFEC) using
an OTU2V frame structure acc. to the
ITU-T Rec. G.709/Y.1331 (03/2003),
appendix II.
For a port on the electrical
transmission unit EP51, this parameter
specifies the type of input signal the
port has been provisioned for.
DS3, EC1.
The interface standard setting.
SONET, SDH.
The field name is a hyperlink. To
create or delete a loopback, click the
link and follow the task “To provision
or deprovision a loopback on a port”
(p. 6-7).
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-11
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
Parameter
Outloop/Terminal loopback
Service condition
Parameters for SDH/SONET/PDH ports
Function
Possible values
The field name is a hyperlink. To
create or delete a loopback, click the
link and follow the task “To provision
or deprovision a loopback on a port”
(p. 6-7) .
The status of the port concerning
service involvement.
•
in service – provisioning values
for service will be accepted.
•
out of service – provisioning
values for service will not be
accepted.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-12
Equipment provisioning tasks
Parameters for SDH/SONET/PDH ports
Parameter
Function
Possible values
Tributary mode
The user-provisionable attribute of
tributaries of a port.
fixed, adaptive.
It can be of two types:
•
Fixed-rate tributary mode:
In this mode, a tributary is
provisioned for an expected and
fixed signal rate, which is used for
cross-connection rate validation.
SDH ports can only be provisioned
for fixed-rate operation, so a
cross-connection from a tributary
on an SDH port provisioned for
VC-4 must be at the VC-4 rate and
can contain only a VC-4 signal, not
three VC-3 signals. (If 3 × VC-3
did appear on the tributary input,
the associated pointer processor
would declare loss of pointer and
path AIS would be inserted
downstream.) With SONET ports
provisioned for fixed-rate
operation, the only allowed
constituents for an STS-1, STS-3,
STS-12, STS-48, or STS-192
cross-connection from a fixed-rate
port are respectively STS-1,
STS-3c, STS-12c, STS-48c, or
STS-192c. LO cross-connections
can only be switched from input
ports in fixed rate tributary mode.
Also within the HO VC-4 / STS-1
there is only fixed rate operation
for the LO constituents.
•
Adaptive-rate tributary mode (also
known as “pipe mode”):
In this mode, a tributary is not
provisioned for an expected signal
rate. The system identifies, and
adapts to transitions in, the signal
rates.With adaptive-rate tributary
operation, an STS-N
cross-connection could have a
single STS-Nc constituent signal or
any mix of multiple lower-rate
constituent signals (for example
STS-1s and STS-3cs in an STS-12),
consistent with the SONET
standard. Transitions between these
constituent signal rates can take
place. The system adapts to the
current concatenation state by
auto-detection of the concatenation
indicators in the signal. This “pipe
mode” can only be provisioned for
SONET ports.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-13
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
Parameter
Tributary input signal rate
Tributary output signal rate
Sub structure
Optical channel
Optical output enable
OTN client port
Outgoing Z0 byte
Parameters for SDH/SONET/PDH ports
Function
Possible values
The tributary input signal rate indicates
the expected tributary structure for the
port in the incoming direction.
For a SONET port, a valid value is a
string of the format NX-NX- NX{-NX,
where N is the number of Xs and X can
be 1, 3, 12, 48, or 192 (representing
STS1, STS3, STS12, STS48, or
STS192, respectively). For an SDH
port, a valid value is a string of the
format NX-NX-NX{- NX, where N is the
number of Xs and X can be 3, 4, 4C,
16C, or 64C (representing VC3, VC4,
VC4-4C, VC4-16C, or VC4-64C,
respectively).
The tributary output signal rate
indicates the expected tributary
structure for the unequipped signal that
will be transmitted when there are no
cross connections.
For a SONET port, a valid value is a
string of the format NX-NX- NX{-NX,
where N is the number of Xs and X can
be 1, 3, 12, 48, or 192 (representing
STS1, STS3, STS12, STS48, or
STS192, respectively). For an SDH
port, a valid value is a string of the
format NX-NX-NX{- NX, where N is the
number of Xs and X can be 3, 4, 4C,
16C, or 64C (representing VC3, VC4,
VC4-4C, VC4-16C, or VC4-64C,
respectively).
This parameter is used to indicate
whether a VC-4 (SDH) or STS-1
(SONET) CTP contains LO CTPs or
not.
no – no substructure; mansub – manual
substructure; yes – automatic
substructure.
Indicates whether the Optical Channel
(OCh) is enabled or disabled. Applies
only to port units that support
out-of-band FEC. The OCh needs to be
enabled for out-of-band FEC
enable, disable.
Enables the OT1 port of an optical
port unit with tunable laser.
enable, disable.
Specifies if the port of an optical port
unit with tunable operates as OTN
client port or as SDH/SONET port.
yes – OTN client port; no –
SDH/SONET port.
This parameter only applies to OC-48
and lower rate SONET interfaces.
Possible values are:
•
Fixed CChex
The value of the Z0 byte is CC hex
(hexadecimal value).
•
STS-Id
The value of the Z0 byte is the
STS identifier (the number) of the
corresponding STS frame.
It indicates the configured mode of
outgoing Z0 byte insertion.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-14
Equipment provisioning tasks
Parameter
Parameters for SDH/SONET/PDH ports
Function
Possible values
Specifies the TID of the node at which
the service is added to the BLSR
ring.It is required for the input of
tributaries to be used by ONNS on
ports of portClass=EDGE being
members in BLSR/MS-SPring
protection groups.
Ring A node ID
Specifies the TID of the node at which
the service is added to the BLSR
ring.It is required for the input of
tributaries to be used by ONNS on
ports of portClass=EDGE being
members in BLSR/MS-SPring
protection groups.
Ring Z node ID
The provisioned DS3 signal format:
Frame format
•
C-bit parity
C-bit parity channelized DS3
format, which supports full P-bit
parity VMR, VM, or no VM. It
may also use full C-bit parity
monitoring.
•
M23
M23 channelized DS3 format,
which supports full P-bit parity
VMR, VM, or no VM. The C-bit
monitoring is disabled for this
format.
•
Unframed and Clear Channel
P-bit parity VMR, VM, and C-bit
parity monitoring is disabled.
CBIT, M23, UNFRAMEDCC.
The cable length applicable for the
DS3 port.
short (0 to 68.5 m; 0 to 225 ft); long
(68.5 to 137 m; 225 to 450 ft)
Indicates whether an AIS, DS3AIS or
IDLE signal is transmitted in response
to an unconnected input.
AIS, DS3AIS, idle.
DS3 violation monitoring mode
The status of the DS3 P-bit parity
violation monitoring and removal.
NO-VM – no violation monitoring;
VMR – violation monitoring and
removal; VM – violation monitoring.
PDI-P switching
Enables payload defect indication on
path level (PDI-P) switching.
enable, disable.
Line build out
Unconnected output maintenance signal
Optics
In the Optics section of the Port page, the following parameters can be modified:
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-15
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
Parameters for SDH/SONET/PDH ports
Parameter
Function
Possible values
Optical wavelength (nm)
The optical wavelength in nanometers
of the signal transmitted and received
at that port.
For a DWDM port of a G.709 10G OT
the following values are possible:
•
0 (undefined)
•
OP10/XTTC: 35 wavelengths in
the BAND_C (1554.537 nm to
1568.362 nm)
•
OP10/XTTL: 93 wavelengths in
the BAND_L (1568.773 nm to
1607.466 nm)
Supported optical wavelengths
DWDM ports of a G.709 10G OT support the following wavelength:
OP10/XTTC
OP10/XTTL
35 wavelengths in the BAND_C:
93 wavelengths in the BAND_L:
1554.537,
1556.555,
1558.578,
1560.606,
1562.640,
1564.679,
1566.723,
1554.940,
1556.959,
1558.983,
1561.013,
1563.047,
1565.087,
1567.133,
1555.343,
1557.363,
1559.389,
1561.419,
1563.455,
1565.496,
1567.542,
1555.747,
1557.768,
1559.794,
1561.828,
1563.863,
1565.905,
1567.952,
1556.151,
1558.173,
1560.200,
1562.233,
1564.271,
1566.314,
1568.362
1568.773,
1570.828,
1572.888,
1574.954,
1577.025,
1579.102,
1581.184,
1583.271,
1585.365,
1587.463,
1589.568,
1591.678,
1593.793,
1595.914,
1598.041,
1600.173,
1602.311,
1604.455,
1606.605,
1569.183,
1571.239,
1573.301,
1575.368,
1577.440,
1579.518,
1581.601,
1583.690,
1585.784,
1587.884,
1589.989,
1592.100,
1594.217,
1596.339,
1598.467,
1600.600,
1602.740,
1604.885,
1607.035,
1569.594,
1571.651,
1573.714,
1575.782,
1577.855,
1579.934,
1582.018,
1584.108,
1586.203,
1588.304,
1590.411,
1592.523,
1594.641,
1596.764,
1598.893,
1601.028,
1603.168,
1605.314,
1607.466
1570.005,
1572.063,
1574.127,
1576.196,
1578.270,
1580.350,
1582.436,
1584.527,
1586.623,
1588.725,
1590.833,
1592.946,
1595.065,
1597.189,
1599.320,
1601.455,
1603.597,
1605.744,
1570.416,
1572.476,
1574.540,
1576.610,
1578.686,
1580.767,
1582.854,
1584.946,
1587.043,
1589.146,
1591.255,
1593.369,
1595.489,
1597.615,
1599.746,
1601.883,
1604.026,
1606.174,
Trace information
In the Trace Information section of the Port page, the following parameters can be
modified:
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-16
Equipment provisioning tasks
Parameter
Expected trail trace out format
Transmitted trail trace value
Parameters for SDH/SONET/PDH ports
Function
Possible values
Specifies the expected trail trace out
format on a STM-16/OC48 port in
transparent mode.
Depending on the port and signal type,
a subset of the following:
•
1: non-specific byte – a single
byte with a fixed hexadecimal
value of 0x00 (ITU/ETSI mode 2).
•
2: specific byte (1-byte string) – a
single byte (hexadecimal format
using the printable T.50/ASCII
character set) (SONET mode).
•
16: 16-byte string – a 16-bytes
hexadecimal format using the
printable T.50/ASCII character set,
with the first byte being a CRC-7
(ITU/ETSI mode 1).
•
64: 64-byte string – a 64-bytes
hexadecimal format using the
printable T.50/ASCII character set,
with the last two bytes being a
carriage return, line feed
(SONET).
If the Expected trail trace out format
parameter is set to specific byte (1-byte
string), 16-byte string, or 64-byte
string, the expected character string is
set here.
The field name is a hyperlink. Click it
to open a window where you can enter
the desired string.
Trail trace out mismatch detection mode
Controls the RS TIM out monitor
(SDH) or the section TIM out monitor
(SONET), respectively, on a
STM-16/OC48 port in transparent
mode.
enable, disable.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-17
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
Parameters for SDH/SONET/PDH ports
Parameter
Function
Possible values
Transmitted trail trace format
Selects the format of the transmitted
trail trace identifier (TTI).
Depending on the port and signal type,
a subset of the following:
Transmitted trail trace value
•
non-specific byte – a single byte
with a fixed hexadecimal value of
0x00 (ITU/ETSI mode 2).
•
specific byte (1-byte string) – a
single byte (hexadecimal format
using the printable T.50/ASCII
character set) (SONET mode).
•
16-byte string – a 16-bytes
hexadecimal format using the
printable T.50/ASCII character set,
with the first byte being a CRC-7
(ITU/ETSI mode 1).
•
64-byte string – a 64-bytes
hexadecimal format using the
printable T.50/ASCII character set,
with the last two bytes being a
carriage return, line feed
(SONET).
If the transmitted trail trace format
parameter is set to specific byte (1-byte
string), 16-byte string, or 64-byte
string, the transmitted character string
is set here. Since the possible values
depend on the setting of the
transmitted trace display mode
parameter, it is recommended to set
that parameter in advance.
The field name is a hyperlink. Click it
to open a window where you can enter
the desired string.
Transmitted trace display mode
If the transmitted trail trace format
parameter is set to specific byte (1-byte
string), 16-byte string, or 64-byte
string, the format of the transmitted
character string is set here.
ascii, hex.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-18
Equipment provisioning tasks
Parameters for SDH/SONET/PDH ports
Parameter
Function
Possible values
Expected trail trace format
Selects the format of the expected trail
trace identifier (TTI).
Depending on the port and signal type,
a subset of the following:
Expected trail trace value
•
non-specific byte – a single byte
with a fixed hexadecimal value of
0x00 (ITU/ETSI mode 2).
•
specific byte (1-byte string) – a
single byte (hexadecimal format
using the printable T.50/ASCII
character set) (SONET mode).
•
16-byte string – a 16-bytes
hexadecimal format using the
printable T.50/ASCII character set,
with the first byte being a CRC-7
(ITU/ETSI mode 1).
•
64-byte string – a 64-bytes
hexadecimal format using the
printable T.50/ASCII character set,
with the last two bytes being a
carriage return, line feed
(SONET).
If the expected trail trace format
parameter is set to specific byte (1-byte
string), 16-byte string, or 64-byte
string, the transmitted character string
is set here. Since the possible values
depend on the setting of the expected
trace display mode parameter, it is
recommended to set that parameter in
advance.
The field name is a hyperlink. Click it
to open a window where you can enter
the desired string.
Expected trace display mode
Accepted trace display mode
Trail trace mismatch detection mode
Consequent action on trail trace
mismatch
Signal label mismatch detection mode
If the expected trail trace format
parameter is set to specific byte (1-byte
string), 16-byte string, or 64-byte
string, the format of the expected
character string is set here.
ascii, hex.
Sets the format of the accepeted
character string.
ascii, hex.
Controls the detection mode.
enabled, disabled.
Enables / disables consequent action in
case of a trace identifier mismatch
detection. For SDH: Note that this
function is only supported if the
related trace read format is set to
16-byte string.
enabled, disabled.
Controls the signal label mismatch
detection for VC-4 or STS-1 ports.
enable, disable.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-19
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
Parameters for SDH/SONET/PDH ports
Timing
In the Timing section of the Port page, the following parameters can be modified:
Parameter
ForceDNU
Function
Possible values
Force DNU allows to force an S1 byte
value DNU into an outgoing signal.
When an outgoing signal is forced to
carry DNU, this signal cannot be used
for synchronization by another NE.
enable, disable.
Fault management
In the Fault Management section of the Port page, the following parameters can be
modified:
Parameter
Alarm profile name
Signal degrade/signal fail mode
Function
Possible values
The name of a pre-defined alarm
severity assignment profile (ASAP) to
be used for the port in question. An
ASAP is a list of alarms which can
occur in a network element and which
each have an alarm severity assigned.
1 to 24 characters.
Sets the preferred mode of bit error
monitoring to monitor the bit error
performance during transmission.
•
burst – this mode of bit error
monitoring means that a bursty
distribution of bit errors is
presumed (default setting for SDH
ports).
•
poisson – this mode of bit error
monitoring means that a random
(“Poisson”) distribution of bit
errors is presumed (default setting
for SONET ports).
Tooltip: For an STS1 on an EC1, the
value is fixed to poisson. Info: For
EP51 (modifier: STS)
Bursty error threshold (%)
Bursty interval (sec)
Defines the threshold value for bursty
errors. This parameter can only be set
if the signal degrade/signal fail mode
is “burst”.
Integer in the range from 0 to 50 in
steps of 5.
Defines the measurement interval for
bursty errors. This parameter can only
be set if the signal degrade/signal fail
mode is “burst”.
Integer in the range from 2 to 10.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-20
Equipment provisioning tasks
Parameters for SDH/SONET/PDH ports
Parameter
Function
Possible values
REI mode
Specifies the MS remote error
indication (REI) mode.
Single – provision is made for
interworking with older equipment
(only the M1 byte is used for the
remote error indication). Extended –
no provision is made for interworking
with older equipment (the M0 byte and
the M1 byte are used for the remote
error indication).
Sets the signal degrade threshold, the
value is an exponent of 10. It defines
the bit error ratio (BER) that must be
exceeded before a Degraded Signal
alarm is reported. This parameter can
only be set if the signal degrade/signal
fail mode is “poisson”.
Integer in the range from –5 to –9.
Sets the signal fail threshold, the value
is an exponent of 10. It defines the bit
error ratio (BER) that must be
exceeded before an
Excessive Bit Error Ratio alarm is
reported. This parameter can only be
set if the signal degrade/signal fail
mode is “poisson”.
Integer in the range from –3 to –5.
Depending on the port capabilities, this
parameter specifies the NE to include
the Foward Error Correction (FEC)
information in the outgoing signal.
Modifying the FEC parameters during
operation may be traffic affecting.
Therefore, it is recommended to
configure all FEC parameters prior to
putting the corresponding port unit into
operation and leave them unchanged
during operation.
enable, disable.
Specifies the polynomial used by the
WaveWrapper ™ scrambler on the
Optical Channel (OCh) to generate a
pseudo random binary sequence
(PRBS) for STM-64 and OC-192 ports.
Possible values are:
Signal degrade threshold (10 Exp)
Signal fail threshold (10 Exp)
Forward error correction
Forward error correction scrambling
polynomial
The FEC Scrambling Polynomial is of
special importance for the interworking
with wavelength division multiplexing
(WDM) systems (such as
WaveStar ® OLS 1.6T or
LambdaXtreme ™). It is relevant only if
the FEC Type is Out-Band, and the
Optical Channel is enabled.
•
1 – x 7 + x + 1 (acc. to ITU-T
Rec. G.975)
•
2 – x16 + x 12 + x 3 + x + 1 (acc.
to ITU-T Rec. G.709)
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-21
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
Parameters for SDH/SONET/PDH ports
Performance management
In the Performance section of the Port page, the following parameters can be
modified:
Parameter
Function
Possible values
TCA reset mode
Specifies the TCA mode.
TRRTR – implicit reset method, also
known as transient condition method,
for SDH and Ethernet ports only. TR –
explicit reset method, also known as
standing condition method.
Near-end PM
Controls the near-end path performance
monitoring.
enable, disable.
Far-end PM
Controls the far-end path performance
monitoring.
enable, disable.
Pointer justification event PM enable
Controls the pointer justification event
PM monitor.
enable, disable.
Incoming PM enable
Controls the DS3 incoming
performance monitoring.
enable, disable.
Outgoing PM enable
Controls the DS3 outgoing
performance monitoring.
enable, disable.
Far-end incoming path PM enable
Controls the incoming DS3 far-end
path performance monitoring.
enable, disable.
Far-end outgoing path PM enable
Controls the outgoing DS3 far-end path
performance monitoring.
enable, disable.
Incoming line PM enable
Controls the DS3 incoming line
performance monitoring.
enable, disable.
Controls the performance monitoring
on regenerator section level (SDH) or
section level (SONET), respectively.
enable, disable.
Controls the performance monitoring
(outgoing) on STM-16 regenerator
section level (SDH) or OC-48 section
level (SONET), respectively, for
transparent services.
enable, disable.
Controls the near-end performance
monitoring on multiplex section level
(SDH) or line level (SONET),
respectively.
enable, disable.
Controls the far-end performance
monitoring on multiplex section level
(SDH) or line level (SONET),
respectively.
enable, disable.
Specifies the near-end path SES
threshold.
The range of possible values depends
on the port rate and the plug-in unit
used.
Section/RS PM enable
Section/RS out PM enable
Near-end line/MS PM
Far-end line/MS PM enable
Near-end path SES threshold
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-22
Equipment provisioning tasks
Parameters for SDH/SONET/PDH ports
Parameter
Function
Possible values
Far-end path SES threshold
Specifies the far-end path SES
threshold.
The range of possible values depends
on the port rate and the plug-in unit
used.
Incoming line SES threshold
Specifies the SES threshold (errors in
a second) for incoming DS3 lines.
Integer in the range from 1 to 8000.
Incoming path SES threshold
Specifies the SES threshold (errors in
a second) for incoming DS3 paths.
Integer in the range from 1 to 8000.
Far-end path SES threshold
Specifies the far-end SES threshold
(errors in a second) for DS3 paths.
Integer in the range from 1 to 8000.
Specifies the near-end SES threshold
on regenerator section level (SDH) or
section level (SONET), respectively.
Integer in the range from 1 to 64000.
Specifies the near-end outgoing SES
threshold on STM-16 regenerator
section level (SDH) or OC-48 section
level (SONET), respectively, for
transparent services.
The range of possible values depends
on the port rate.
Specifies the near-end SES threshold
on multiplex section level (SDH) or
line level (SONET), respectively.
The range of possible values depends
on the port rate.
Specifies the far-end SES threshold
(errors in a second) on multiplex
section level (SDH) or line level
(SONET), respectively.
The range of possible values depends
on the port rate.
Far-end outgoing path SES PM
threshold
Specifies the far-end SES threshold
(errors in a second) for outgoing DS3
paths.
Integer in the range from 1 to 8000.
Outgoing path SES PM threshold
Specifies the SES threshold (errors in
a second) for outgoing DS3 paths.
Integer in the range from 1 to 8000.
PM section/RS near-end SES threshold
PM section/RS near-end out SES
threshold
Near-end line/MS SES threshold
PM line/MS far-end SES threshold
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-23
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
Parameter
TCA profile name
Parameters for SDH/SONET/PDH ports
Function
Possible values
Specifies the name of a pre-defined
threshold crossing alert (TCA) profile
to be used for the port in question. The
TCA profiles are used to store the
threshold values of the performance
parameters related to a specific
parameter group.
1 to 24 characters.
TCA profiles exist for these groups of
performance parameters:
•
Parameters related to the SDH
Regenerator Section and Multiplex
Section
•
Parameters related to the SONET
Section and Line
•
Parameters related to SDH and
SONET tributaries (including
VCG tributaries)
•
Parameters related to Ethernet and
VCG ports
•
Parameters related to transparent
services (Optical Data Unit,
ODU1)
A default profile (“DEFAULT”) is
predefined for each of these TCA
profile types.
Physical TCA profile name
Reported payload type
Specifies the name of the “Physical”
TCA profile.
1 to 24 characters.
Specifies the reported payload type for
for transparent services on STM-16
(SDH) or OC-48 (SONET),
respectively.
Two hexadecimal digits.
Control plane
In the Control Plane section of the Port page, the following parameters can be
modified:
Parameter
Function
Possible values
Network interface
The port class of an ONNS capable
port.
None – traditional; CustomerClient –
Edge; InternalNetwork – internal
network-to-network interface (iNNI);
UserNetworkInterface – UNI
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-24
Equipment provisioning tasks
Parameters for SDH/SONET/PDH ports
Parameter
Function
Possible values
UNI network TNA type
The type of transport network assigned
(TNA) adress used for UNI ports.
IPV4 – an IPv4, a 4-byte address
represented by four dot-separated
decimal values, each in the range from
0 to 255; IPV6 – an IPv6 address, a
16-byte address represented by eight
dash-separated hexadecimal values;
NSAP – an NSAP address, a 20-byte
address represented by a hexadecimal
value.
The value of the transport network
assigned (TNA) adress of the selected
UNI port. The value depends on the
type of TNA.
Depends on the UNI network TNA
type.
UNI network logical port identifier
Unique identifier for a single UNI port
within a TNA address
Integer in the range from 0 to
4294967295.
UNI client node identiy
The IP address of the client node of
the UNI port.
Four dot-separated integer values, each
in the range from 0 to 255.
Automatically switched transport
network (ASTN) propagation delay
value for iNNI ports.
Integer in the range from 0 to 255.
Administrative cost for iNNI ports.
Integer in the range from 0 to 65535.
Shared risk link groups ID list for
iNNI ports. Shared risk link groups are
groups of port connections that share
the same risk. For instance: port
connections that terminate on the same
card, in the same network element or
that share the same fiber duct.
A list of strings “N-N-N” or
“N-N-N-N-N-N-N-N-N-N” where N is
an integer in the range from 0 to
65535, step by 1.
For iNNI ports: the minimum
cross-connect rate implemented by the
switch fabric and the port/channels in
the link bundle. This represents the
minimum concatenated signal sub-rate
at which the port can multiplex or
demultiplex.
Depending on the port type, the
following values are possible:
UNI network TNA address
ASTN propagation delay (msec)
Cost
Shared risk link group
Minimum NN crossconnect rate
•
VC3, VC4, VC44C, VC416C,
VC-464C (SDH)
•
STS1, STS3, STS12, STS48,
STS192 (SONET).
The minimum NN cross-connect rate
cannot be greater than the maximum
NN cross-connect rate.
Maximum NN crossconnect rate
For iNNI ports: the maximum
cross-connect rate implemented by the
switch fabric and the port/channels in
the link bundle. This represents the
minimum concatenated signal sub-rate
at which the port can multiplex or
demultiplex.
Depending on the port type, the
following values are possible:
•
VC3, VC4, VC44C, VC416C,
VC-464C (SDH)
•
STS1, STS3, STS12, STS48,
STS192 (SONET).
The maximum NN cross-connect rate
cannot be smaller than the minimum
NN cross-connect rate.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-25
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
Parameters
for Ethernet ports
...................................................................................................................................................................................................................................
Introduction
This section lists the parameters that can be modified for Ethernet ports. Note that not
all parameters and possible values apply to all port types, plug-in units, and network
element configurations.
For a number of parameters, the network elements can report the value not applicable.
This value is for information purposes only, it cannot be entered.
Transmission
In the Transmission section of the Port page, the following parameters can be
modified:
Parameter
Function
Possible values
Port mode
Indicates the monitoring state of the
specified port.
Depending on the port rate and type
the following values are possible:
Service condition
The status of the port concerning
service involvement.
•
on – the port is being monitored.
•
auto – the port is ready to
transition into a monitored state,
when a signal is detected.
•
off – the port is not being
monitored.
•
in service – provisioning values
for service will be accepted.
•
out of service – provisioning
values for service will not be
accepted.
Controls the consequent action upon
the receipt of a client signal fail (CSF)
indication.
Enable – the receipt of CSF causes the
laser to be switched off (this is the
default setting); Disable – the laser
will not be switched off upon the
receipt of CSF.
The applicable pause mode.
enable, disable.
Specify the configuration for the pause
operation.
Depending on the type of plug-in unit
used, possible values are: auto,
disable, asymtopartner, asymtolocal,
sym.
Auto negotiation mode
Controls the autonegotiation mode.
enable, disable.
Default user priority
The default priority for the port.
high, low.
Link pass thru mode
Provisioned pause mode
Provisioned flow control mode
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-26
Equipment provisioning tasks
Parameters for Ethernet ports
Fault management
In the Fault Management section of the Port page, the following parameters can be
modified:
Parameter
Alarm profile name
Signal degrade threshold (10 Exp)
Signal fail threshold (10 Exp)
Function
Possible values
The name of a pre-defined alarm
severity assignment profile (ASAP) to
be used for the port in question. An
ASAP is a list of alarms which can
occur in a network element and which
each have an alarm severity assigned.
1 to 24 characters.
Sets the signal degrade threshold, the
value is an exponent of 10. It defines
the bit error ratio (BER) that must be
exceeded before a Degraded Signal
alarm is reported. This parameter can
only be set if the signal degrade/signal
fail mode is “poisson”.
Integer in the range from –5 to –9.
Sets the signal fail threshold, the value
is an exponent of 10. It defines the bit
error ratio (BER) that must be
exceeded before an
Excessive Bit Error Ratio alarm is
reported. This parameter can only be
set if the signal degrade/signal fail
mode is “poisson”.
Integer in the range from –3 to –5.
Performance management
In the Performance section of the Port page, the following parameters can be
modified:
Parameter
Function
Possible values
TCA reset mode
Specifies the TCA mode.
TRRTR – implicit reset method, also
known as transient condition method,
for SDH and Ethernet ports only. TR –
explicit reset method, also known as
standing condition method.
Performance monitoring
Controls the performance monitoring.
enable, disable.
Near-end PM
Controls the near-end path performance
monitoring.
enable, disable.
Far-end PM
Controls the far-end path performance
monitoring.
enable, disable.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-27
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
Parameter
TCA profile name
Parameters for Ethernet ports
Function
Possible values
Specifies the name of a pre-defined
threshold crossing alert (TCA) profile
to be used for the port in question. The
TCA profiles are used to store the
threshold values of the performance
parameters related to a specific
parameter group.
1 to 24 characters.
TCA profiles exist for these groups of
performance parameters:
•
Parameters related to the SDH
Regenerator Section and Multiplex
Section
•
Parameters related to the SONET
Section and Line
•
Parameters related to SDH and
SONET tributaries (including
VCG tributaries)
•
Parameters related to Ethernet and
VCG ports
•
Parameters related to transparent
services (Optical Data Unit,
ODU1)
A default profile (“DEFAULT”) is
predefined for each of these TCA
profile types.
Spanning tree
In the Spanning Tree section of the Port page, the following parameters can be
modified:
Parameter
Function
Possible values
STP port priority
The priority of the port for the
spanning tree protocol.
Integer in the range from 0 to 255.
The port path cost. For a port with the
spanning tree protocol active, this
parameter defines the contribution of
this port to the path cost of paths
towards the spanning tree root which
included this port.
Integer in the range from 1 to
200000000.
Port path cost
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-28
Equipment provisioning tasks
Parameters for Ethernet ports
Port path cost details
According to IEEE 802.1Q 1998, this parameter should be related to the bandwidth of
the link in which the port participates. Link speed is mapped to port path costs as
follows:
Link speed
Path cost
2 Mbps
10,000,000
4 Mbps
5,000,000
6 Mbps
3,400,000
8 Mbps
2,500,000
10 Mbps
2,000,000
50 Mbps
400,000
100 Mbps
200,000
1 Gbps
20,000
10 Gbps
2,000
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-29
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
Parameters
for VCG ports
...................................................................................................................................................................................................................................
Introduction
This section lists the parameters that can be modified for VCG ports. Note that not all
parameters and possible values apply to all port types, plug-in units, and network
element configurations.
For a number of parameters, the network elements can report the value not applicable.
This value is for information purposes only, it cannot be entered.
Transmission
In the Transmission section of the Port page, the following parameters can be
modified:
Parameter
Function
Possible values
Port mode
Indicates the monitoring state of the
specified port.
Depending on the port rate and type
the following values are possible:
Input membership
Output membership
LCAS mode
LCAS hold-off time (ms)
•
on – the port is being monitored.
•
auto – the port is ready to
transition into a monitored state,
when a signal is detected.
•
off – the port is not being
monitored.
Specifies whether the tributary shall
take part in the transmission of its
owning VCG in input direction.
enable, disable.
Specifies whether the tributary shall
take part in the transmission of its
owning VCG in output direction.
enable, disable.
The operation mode of the link
capacity adjustment scheme (LCAS)
for this VCG.
on, off.
The LCAS hold-off time. If a tributary
is configured to be a member of the
VCG, and a fault is detected for that
tributary, then it is taken out of
transmission by LCAS after the hold
off time. By means of different
hold-off times, it can be defined which
protection should switch first. The
hold-off time is configured on group
level, that means all tributaries of a
VCG have the same hold-off time.
Integer in the range from 0 to 10000
in steps of 100, and 99999.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-30
Equipment provisioning tasks
Parameter
LCAS wait to restore time (min)
Consequent action mode
Default user priority
Parameters for VCG ports
Function
Possible values
The LCAS wait-to-restore (WTR) time.
If a tributary is configured to be a
member of the VCG, and that tributary
recovers from a faulty state then it is
taken in again to transmission by
LCAS after the wait-to-restore time.
The wait-to-restore time is configured
on group level, that means all
tributaries of a VCG have the same
wait-to-restore time.
Integer in the range from 0 to 60.
The consequent action to be taken in
the egress direction (towards the
synchronous port) in case a signal fail
condition is detected on the ODU layer
(STM-16 or OC-48).
genericais – generic AIS; msais –
MS-AIS; laseroff – laser off.
The default priority for the port.
high, low.
Trace information
In the Trace Information section of the Port page, the following parameters can be
modified:
Parameter
Function
Possible values
Transmitted trail trace format
Selects the format of the transmitted
trail trace identifier (TTI).
Depending on the port and signal type,
a subset of the following:
•
non-specific byte – a single byte
with a fixed hexadecimal value of
0x00 (ITU/ETSI mode 2).
•
specific byte (1-byte string) – a
single byte (hexadecimal format
using the printable T.50/ASCII
character set) (SONET mode).
•
16-byte string – a 16-bytes
hexadecimal format using the
printable T.50/ASCII character set,
with the first byte being a CRC-7
(ITU/ETSI mode 1).
•
64-byte string – a 64-bytes
hexadecimal format using the
printable T.50/ASCII character set,
with the last two bytes being a
carriage return, line feed
(SONET).
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-31
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
Parameter
Transmitted trail trace value
Parameters for VCG ports
Function
Possible values
If the transmitted trail trace format
parameter is set to specific byte (1-byte
string), 16-byte string, or 64-byte
string, the transmitted character string
is set here. Since the possible values
depend on the setting of the
transmitted trace display mode
parameter, it is recommended to set
that parameter in advance.
The field name is a hyperlink. Click it
to open a window where you can enter
the desired string.
Transmitted trace display mode
Expected trail trace format
Expected trail trace value
If the transmitted trail trace format
parameter is set to specific byte (1-byte
string), 16-byte string, or 64-byte
string, the format of the transmitted
character string is set here.
ascii, hex.
Selects the format of the expected trail
trace identifier (TTI).
Depending on the port and signal type,
a subset of the following:
•
non-specific byte – a single byte
with a fixed hexadecimal value of
0x00 (ITU/ETSI mode 2).
•
specific byte (1-byte string) – a
single byte (hexadecimal format
using the printable T.50/ASCII
character set) (SONET mode).
•
16-byte string – a 16-bytes
hexadecimal format using the
printable T.50/ASCII character set,
with the first byte being a CRC-7
(ITU/ETSI mode 1).
•
64-byte string – a 64-bytes
hexadecimal format using the
printable T.50/ASCII character set,
with the last two bytes being a
carriage return, line feed
(SONET).
If the expected trail trace format
parameter is set to specific byte (1-byte
string), 16-byte string, or 64-byte
string, the transmitted character string
is set here. Since the possible values
depend on the setting of the expected
trace display mode parameter, it is
recommended to set that parameter in
advance.
The field name is a hyperlink. Click it
to open a window where you can enter
the desired string.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-32
Equipment provisioning tasks
Parameter
Expected trace display mode
Expected trail trace out format
Trail trace mismatch detection mode
Consequent action on trail trace
mismatch
Parameters for VCG ports
Function
Possible values
If the expected trail trace format
parameter is set to specific byte (1-byte
string), 16-byte string, or 64-byte
string, the format of the expected
character string is set here.
ascii, hex.
Specifies the accepted trail trace
format.
Depending on the port and signal type,
a subset of the following:
•
1: non-specific byte – a single
byte with a fixed hexadecimal
value of 0x00 (ITU/ETSI mode 2).
•
2: specific byte (1-byte string) – a
single byte (hexadecimal format
using the printable T.50/ASCII
character set) (SONET mode).
•
16: 16-byte string – a 16-bytes
hexadecimal format using the
printable T.50/ASCII character set,
with the first byte being a CRC-7
(ITU/ETSI mode 1).
•
64: 64-byte string – a 64-bytes
hexadecimal format using the
printable T.50/ASCII character set,
with the last two bytes being a
carriage return, line feed
(SONET).
Controls the detection mode.
enabled, disabled.
Enables / disables consequent action in
case of a trace identifier mismatch
detection. For SDH: Note that this
function is only supported if the
related trace read format is set to
16-byte string.
enabled, disabled.
Fault management
In the Fault Management section of the Port page, the following parameters can be
modified:
Parameter
Alarm profile name
Function
Possible values
The name of a pre-defined alarm
severity assignment profile (ASAP) to
be used for the port in question. An
ASAP is a list of alarms which can
occur in a network element and which
each have an alarm severity assigned.
1 to 24 characters.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-33
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
Parameter
Transparent alarm profile name
Signal degrade/signal fail mode
Bursty error threshold (%)
Bursty interval (sec)
Signal degrade threshold (10 Exp)
Signal fail threshold (10 Exp)
Parameters for VCG ports
Function
Possible values
The alarm severity assignment profile
(ASAP) of type “Fully Transparent
Service” assigned to that VCG. This
may be either the default ASAP or any
other previously defined ASAP of that
type.
1 to 24 characters.
Sets the preferred mode of bit error
monitoring to monitor the bit error
performance during transmission.
•
burst – this mode of bit error
monitoring means that a bursty
distribution of bit errors is
presumed (default setting for SDH
ports).
•
poisson – this mode of bit error
monitoring means that a random
(“Poisson”) distribution of bit
errors is presumed (default setting
for SONET ports).
Defines the threshold value for bursty
errors. This parameter can only be set
if the signal degrade/signal fail mode
is “burst”.
Integer in the range from 0 to 50 in
steps of 5.
Defines the measurement interval for
bursty errors. This parameter can only
be set if the signal degrade/signal fail
mode is “burst”.
Integer in the range from 2 to 10.
Sets the signal degrade threshold, the
value is an exponent of 10. It defines
the bit error ratio (BER) that must be
exceeded before a Degraded Signal
alarm is reported. This parameter can
only be set if the signal degrade/signal
fail mode is “poisson”.
Integer in the range from –5 to –9.
Sets the signal fail threshold, the value
is an exponent of 10. It defines the bit
error ratio (BER) that must be
exceeded before an
Excessive Bit Error Ratio alarm is
reported. This parameter can only be
set if the signal degrade/signal fail
mode is “poisson”.
Integer in the range from –3 to –5.
Performance management
In the Performance section of the Port page, the following parameters can be
modified:
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-34
Equipment provisioning tasks
Parameters for VCG ports
Parameter
Function
Possible values
TCA reset mode
Specifies the TCA mode.
TRRTR – implicit reset method, also
known as transient condition method,
for SDH and Ethernet ports only. TR –
explicit reset method, also known as
standing condition method.
Performance monitoring
Controls the performance monitoring.
enable, disable.
Near-end VCG PM
The near-end path performance
monitoring activation status.
enable, disable.
Far-end VCG PM
The far-end path performance
monitoring activation status.
enable, disable.
Near-end PM
Controls the near-end path performance
monitoring.
enable, disable.
Far-end PM
Controls the far-end path performance
monitoring.
enable, disable.
The VCG near-end path SES
declaration threshold indicating the
number of errored blocks (SDH) or
code violations (SONET) per second to
declare a second severly errored.
Integer in the range from 1 to 163360.
The VCG far-end path SES declaration
threshold indicating the number of
errored blocks (SDH) or code
violations (SONET) per second to
declare a second severly errored.
Integer in the range from 1 to 163360.
Near-end path SES threshold
Specifies the near-end path SES
threshold.
The range of possible values depends
on the port rate and the plug-in unit
used.
Far-end path SES threshold
Specifies the far-end path SES
threshold.
The range of possible values depends
on the port rate and the plug-in unit
used.
Near-end vcg SES threshold
Far-end vcg SES threshold
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-35
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
Parameter
TCA profile name
Parameters for VCG ports
Function
Possible values
Specifies the name of a pre-defined
threshold crossing alert (TCA) profile
to be used for the port in question. The
TCA profiles are used to store the
threshold values of the performance
parameters related to a specific
parameter group.
1 to 24 characters.
TCA profiles exist for these groups of
performance parameters:
•
Parameters related to the SDH
Regenerator Section and Multiplex
Section
•
Parameters related to the SONET
Section and Line
•
Parameters related to SDH and
SONET tributaries (including
VCG tributaries)
•
Parameters related to Ethernet and
VCG ports
•
Parameters related to transparent
services (Optical Data Unit,
ODU1)
A default profile (“DEFAULT”) is
predefined for each of these TCA
profile types.
Control plane
In the Control Plane section of the Port page, the following parameters can be
modified:
Parameter
Function
Possible values
Network interface
The port class of an ONNS capable
port.
None – traditional; CustomerClient –
Edge; InternalNetwork – internal
network-to-network interface (iNNI);
UserNetworkInterface – UNI
UNI network TNA type
The type of transport network assigned
(TNA) adress used for UNI ports.
IPV4 – an IPv4, a 4-byte address
represented by four dot-separated
decimal values, each in the range from
0 to 255]; IPV6 – an IPv6 address, a
16-byte address represented by eight
dash-separated hexadecimal values;
NSAP – an NSAP address, a 20-byte
address represented by a hexadecimal
value.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-36
Equipment provisioning tasks
Parameter
Parameters for VCG ports
Function
Possible values
The value of the transport network
assigned (TNA) adress of the selected
UNI port. The value depends on the
type of TNA.
Depends on the UNI network TNA
type.
UNI network logical port identifier
Unique identifier for a single UNI port
within a TNA address
Integer in the range from 0 to
4294967295.
UNI client node identiy
The IP address of the client node of
the UNI port.
Four dot-separated integer values, each
in the range from 0 to 255.
UNI network TNA address
Spanning tree
In the Spanning Tree section of the Port page, the following parameters can be
modified:
Parameter
Function
Possible values
STP port priority
The priority of the port for the
spanning tree protocol.
Integer in the range from 0 to 255.
The port path cost. For a port with the
spanning tree protocol active, this
parameter defines the contribution of
this port to the path cost of paths
towards the spanning tree root which
included this port.
Integer in the range from 1 to
200000000.
Port path cost
Port path cost details
According to IEEE 802.1Q 1998, this parameter should be related to the bandwidth of
the link in which the port participates. Link speed is mapped to port path costs as
follows:
Link speed
Path cost
2 Mbps
10,000,000
4 Mbps
5,000,000
6 Mbps
3,400,000
8 Mbps
2,500,000
10 Mbps
2,000,000
50 Mbps
400,000
100 Mbps
200,000
1 Gbps
20,000
10 Gbps
2,000
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-37
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
Provisioning of NE event controls
To
inhibit the forwarding of autonomous messages
...................................................................................................................................................................................................................................
When to use
Use this task to inhibit the forwarding of autonomous messages on the user session or
per system. Autonomous messages are messages which are provided by the system
itself without a trigger via the management interface (for example alarms, switch
reports)
Related information
For a more detailed explanation, please refer to the description of the INH-MSG
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Network Elements.
In the Function field, select Inhibit Message.
Click Go.
Result: The Inhibit Message page is displayed.
...................................................................................................................................................................................................
3
In the Affected sessions field, select Current to inhibit messages for the current
session.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-38
Equipment provisioning tasks
To inhibit the forwarding of autonomous messages
...................................................................................................................................................................................................
4
Optional, for expert users only: The NE Command panel may be used to edit the
native command language of the function.
...................................................................................................................................................................................................
5
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-39
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
To
allow the forwarding of autonomous messages
...................................................................................................................................................................................................................................
When to use
Use this task to allow the forwarding of autonomous messages on the user session or
per system. Autonomous messages are messages which are provided by the system
itself without a trigger via the management interface (for example alarms, switch
reports)
Related information
For a more detailed explanation, please refer to the description of the ALW-MSG-ALL
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Network Elements.
In the Function field, select Allow All Messages.
Click Go.
Result: The Allow All Messages page is displayed.
...................................................................................................................................................................................................
3
In the Affected sessions field, select Current to allow messages for the current
session.
...................................................................................................................................................................................................
4
Optional, for expert users only: The NE Command panel may be used to edit the
native command language of the function.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-40
Equipment provisioning tasks
To allow the forwarding of autonomous messages
...................................................................................................................................................................................................
5
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-41
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
Provisioning of MDIs and MDOs
To
retrieve the MDO configuration
...................................................................................................................................................................................................................................
When to use
Use this task to to retrieve the configuration associated with a miscellaneous output
control (MDO).
Related information
For a more detailed explanation, please refer to the description of the RTRV-ATTR-CONT
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select External Control and Monitoring Points.
In the Function field, select Retrieve Attribute Control.
Click Go.
Result: The Retrieve Attribute Control page is displayed.
...................................................................................................................................................................................................
3
In the field Port Identifier, select either a single MDO (misc_out1 to misc_out8) or
misc_outall to retrieve information for all MDOs at once.
...................................................................................................................................................................................................
4
Click Submit.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-42
Equipment provisioning tasks
To retrieve the MDO configuration
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
...................................................................................................................................................................................................
5
The output parameters for this function are:
•
•
•
•
•
aid – access identifier
Indicates the MDO to which the information relates.
contmsg – control message
This is the name associated to a MDO (environmental control).
durmode – duration mode
Defines in which mode the device connected to the MDO is expected to be
operated. It is a fixed value because this feature will be not supported by the
system. This parameter is in for compatibility reason.
Range: CONTS (continuous duration)
initcstat – initial control state
This value is always “RLS” (release). This parameter is in for compatibility reason.
asgncond – assigned condition type
This parameter identifies the probable cause (type of alarm indication) which is
assigned to an MDO. If one or more alarm(s) of this probable cause appears, then
the MDO will be switched on.
The value “UNDEF” indicates that no probable cause is assigned.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-43
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
To
set the MDO configuration
...................................................................................................................................................................................................................................
When to use
Use this task to set the description associated with a miscellaneous output (MDO). This
way you set the value that identifies the probable cause (type of alarm indication)
which is assigned to an MDO.
Related information
For a more detailed explanation, please refer to the description of the SET-ATTR-CONT
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select External Control and Monitoring Points.
In the Function field, select Set Attribute Control.
Click Go.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-44
Equipment provisioning tasks
To set the MDO configuration
Result: The Set Attribute Control page is displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
•
•
Port Identifier – select a single MDO (misc_out1 to misc_out8).
Control message – enter a string of up to 26 characters which must be surrounded
by double quotes. The string will be used as name associated to the respective
MDO. The string can consist of any lower-case or upper-case characters except
double quotes and backslash.
Assigned condition type – Enter a valid condition type defined for the NE
preceded by a comma. The value identifies the probable cause (type of alarm
indication) which is assigned to an MDO. If one or more alarm(s) of this probable
cause appears then the MDO will be switched on. Example “,LOS”. If the value is
omitted, then the actual value will not be changed.
Range: All defined probable causes and “UNDEF:” if no probable cause is
assigned.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-45
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
To
switch on an MDO
...................................................................................................................................................................................................................................
When to use
Use this task to to switch on (operate) a miscellaneous output control (MDO).
Related information
For a more detailed explanation, please refer to the description of the OPR-EXT-CONT
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select External Control and Monitoring Points.
In the Function field, select Operate External Control.
Click Go.
Result: The Operate External Control page is displayed.
...................................................................................................................................................................................................
3
In the field Port Identifier, select the MDO to switch on (misc_out1 to misc_out8).
...................................................................................................................................................................................................
4
Click Submit.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-46
Equipment provisioning tasks
To switch on an MDO
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-47
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
To
switch off an MDO
...................................................................................................................................................................................................................................
When to use
Use this task to switch off (release) a miscellaneous output control (MDO).
Related information
For a more detailed explanation, please refer to the description of the RLS-EXT-CONT
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select External Control and Monitoring Points.
In the Function field, select Release External Control.
Click Go.
Result: The Release External Control page is displayed.
...................................................................................................................................................................................................
3
In the field Port Identifier, select the MDO to switch off (misc_out1 to misc_out8).
...................................................................................................................................................................................................
4
Click Submit.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-48
Equipment provisioning tasks
To switch off an MDO
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-49
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
To
retrieve the MDO state
...................................................................................................................................................................................................................................
When to use
Use this task to retrieve of a single miscellaneous output control (MDO) or all MDOs.
Related information
For a more detailed explanation, please refer to the description of the RTRV-EXT-CONT
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select External Control and Monitoring Points.
In the Function field, select Retrieve External Control.
Click Go.
Result: The Retrieve External Control page is displayed.
...................................................................................................................................................................................................
3
In the field Port Identifier, select the MDO for which the information should be
retrieved (misc_out1 to misc_out8). To retrieve information for all MDOs, leave the
field empty or select the value misc_outall.
...................................................................................................................................................................................................
4
Click Submit.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-50
Equipment provisioning tasks
To retrieve the MDO state
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
...................................................................................................................................................................................................
5
The output parameters for this function are:
•
•
•
aid – access identifier
Indicates the MDO to which the information relates.
dur – duration
Defines in which mode the device connected to the MDO is expected to be
operated. It is a fixed value because this feature will be not supported by the
system. This parameter is in for compatibility reason.
Range: CONTS (continuous duration).
contstate – control state
The current state of the MDO.
Range:
– OPER – operated, that means the MDO is switched on.
– RLS – released, that means the MDO is switched off.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-51
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
To
retrieve the MDI configuration
...................................................................................................................................................................................................................................
When to use
Use this task to retrieve the alarm message, name, and assigned ASAP of a single
miscellaneous discrete input (MDI) or all MDIs.
Related information
For a more detailed explanation, please refer to the description of the RTRV-ATTR-ENV
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select External Control and Monitoring Points.
In the Function field, select Retrieve Attribute Environment.
Click Go.
Result: The Retrieve Attribute Environment page is displayed.
...................................................................................................................................................................................................
3
In the field Port Identifier, select the MDI for which the information should be
retrieved (misc_in1 to misc_in8). To retrieve information for all MDIs, leave the field
empty or select the value misc_inall.
...................................................................................................................................................................................................
4
Click Submit.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-52
Equipment provisioning tasks
To retrieve the MDI configuration
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
...................................................................................................................................................................................................
5
The output parameters for this function are:
•
•
•
•
•
aid – access identifier
Indicates the MDI to which the information relates.
envinv – environmental alarm inversion
Indicates for the MDI whether an alarm shall be generated if the port is on or if the
port is off.
Range:
– YES – the alarm will be inverted.
– NO – the alarm will not be inverted.
envmsg – environment message
The condition description which is associated with the MDI. This description will
be sent with the alarm generated from the MDI port.
envname – environmental point name
The name associated to an MDI. It is a description which can be retrieved by the
management system. It is not to be mixed up with the envmsg parameter. The
envname is just a name of the MDI port and not reported via the condition
description of an alarm.
pfname – profile name
The name of the alarm severity assignment profile (ASAP) that is assigned to the
MDI.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-53
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
To
set the MDI configuration
...................................................................................................................................................................................................................................
When to use
Use this task to set the alarm message, the name, and the assigned alarm severity
assignment profile (ASAP) of a miscellaneous descrete input (MDI).
Related information
For a more detailed explanation, please refer to the description of the SET-ATTR-ENV
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select External Control and Monitoring Points.
In the Function field, select Set Attribute Environment.
Click Go.
Result: The Set Attribute Environment page is displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
•
Port identifier – select a single MDI (misc_in1 to misc_in8).
Alarm message – enter a string of up to 32 characters which must be surrounded
by double quotes. This is the condition description which is associated with the
MDI. This description will be sent with the alarm generated from the MDI. The
string can consist of any lower-case or upper-case characters except double quotes
and backslash.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-54
Equipment provisioning tasks
•
•
•
To set the MDI configuration
Point name – enter a string of up to 26 characters which must be surrounded by
double quotes. This is the name associated to an MDI. It is a description which can
be retrieved by the management system. It is not to be mixed up with the alarm
message parameter. The point name is just a name of the MDI port and not
reported via the condition description of an alarm. The string can consist of any
lower-case or upper-case characters except double quotes and backslash.
Environmental alarm inversion – indicates for the MDI whether an alarm shall be
generated if the port is on or if the port is off.
Range:
– Invert alarm – the alarm will be inverted.
– Do not invert alarm – the alarm will not be inverted.
Profile name – the name of the alarm severity assignment profile (ASAP) that is
assigned to the MDI. The ASAP must be of the type ENV. Range: up to 24
characters.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-55
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
Equipment protection
To
retrieve equipment protection group information
...................................................................................................................................................................................................................................
When to use
Use this task to retrieve information related to a single equipment protection group or
to all equipment protection groups.
Related information
For a more detailed explanation, please refer to the description of the RTRV-PROTN-GRP
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1. In the NE type field, select a type of NE. If you selected the target NE in the
previous step, this field is already populated with your selection.
2. In the NE name field, select the name of the target NE. If you se.lected the target
NE in the previous step, this field is already populated with your selection.
3. In the Category field, select Protection Groups.
4. In the Function field, select Retrieve Protection Group - 1+1 Equipment
Protection Group.
5. Click Go.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-56
Equipment provisioning tasks
To retrieve equipment protection group information
Result: The Retrieve Protection Group - 1+1 Equipment Protection Group page
is displayed.
...................................................................................................................................................................................................
3
In the field Protection group identifier, enter the ID of the protection group for which
the information should be retrieved. In the field Protection type, select a type of
equipment protection group.
The following table shows the possible combinations:
Type of equipment protection
Value for Protection group
Value for Protection type
identifier
All
1-1-eall
ALL
High order switch fabric and timing
1-1-estgrp
Switch Fabric
System controller
1-1-ectlgrp
System Controller
Electrical 51 Mbps interfaces
1-1-eep{01{99}
EP51 Circuit Pack
Electrical 155 Mbps interfaces
1-1-eep{01{99}
EP155 Circuit Pack
Low order switch fabric
1-1-eloxc1
LOXC Circuit Pack
The last character of
this identifier is the
digit one.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
...................................................................................................................................................................................................
5
The output parameters for this function are:
•
•
•
aid – access identifier
Specifies the 1+1 protection equipment group.
actunit – active unit state
This value specifies which unit is currently selected within the protection group as
active unit. The value WKG specifies that the worker unit is active. The value
PROTN specifies that the protection unit is active.
protn – protection unit
Specifies the protection circuit pack AID being a member of the 1+1 equipment
protection group.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-57
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
•
•
•
•
•
To retrieve equipment protection group information
protnsiglvl – protection fault status
Specifies the current fault status of the protection unit as used by the protection
state machine. The value EF (equipment failed) is used if an equipment defect used
as switch criteria is currently present for the protection unit. The value NONE is
used if no such defect is currently present.
protype – protection type
Specifies the type of the protection group.
Range:
– EQPTSWFBR – high order switch fabric and timing protection
– EQPTCT, – system controller protection
– EQPTEP155 – electrical 155 Mbps interfaces protection
– EQPTEP51 – electrical 51 Mbps interfaces protection
– EQPTLOXC – low order switch fabric protection
swreq – switch request state
Specifies the current switch request state of the protection state machine. The value
EQPTFAILED (equipment failed) is used if an equipment failed condition is the
current state. The value FS (forced switch) is used if a forced switch is the current
state. The value MS (manual switch) is used if a manual switch is the current state.
The value NR (no request) is used if no request is the current state.
wkg – worker unit
Specifies the worker circuit pack AID being a member of the 1+1 equipment
protection group.
wkgsiglvl – worker fault status
Specifies the current fault status of the worker unit as used by the protection state
machine. The value EF (equipment failed) is used if an equipment defect used as
switch criteria is currently present for the worker unit. The value NONE is used if
no such defect is currently present.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-58
Equipment provisioning tasks
To
add an equipment protection group
...................................................................................................................................................................................................................................
When to use
Use this task to add an equipment protection group.
You can add the following types of equipment protection groups:
•
•
•
Electrical 51 Mbps interfaces protection
Electrical 155 Mbps interfaces protection
Lower-order switch fabric protection
The system automatically creates the following types of equipment protection groups:
•
•
Higher-order switch fabric and timing protection
System controller protection
Related information
For a more detailed explanation, please refer to the description of the ENT-PROTN-GRP
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Detailed configuration rules for equipment protection groups are also part of the
LambdaUnite ® MSS User Operations Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
In
In
In
In
the
the
the
the
NE type field, select a type of NE (if not already present).
NE name field, select the name of the target NE (if not already present).
Category field, select Protection Groups.
Function field, select Enter Protection Group - Equipment Protection
Group.
5. Click Go.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-59
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
To add an equipment protection group
Result: The Enter Protection Group - Equipment Protection Group page is
displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
•
•
•
Protection type – select one of the following types (available values depend on
the NE configuration):
– EQPTEP155 – electrical 155 Mbps interfaces protection
– EQPTEP51 – electrical 51 Mbps interfaces protection
– EQPTLOXC – low order switch fabric protection
Protection group Id – the protection group ID as component of the protection
group AID. For protection groups of electrical 155 Mbps interfaces or electrical 51
Mbps interfaces, enter a numerical value in the range 01 to 99. For other protection
types, enter 01.
Protection unit – the protection circuit pack AID being a member of the 1+1
equipment protection group. You may copy the circuit pack ID from the
Slot/circuit pack view page.
Worker unit – the worker circuit pack AID being a member of the 1+1 equipment
protection group.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-60
Equipment provisioning tasks
To
operate an equipment protection group
...................................................................................................................................................................................................................................
When to use
Use this task to operate (to switch) an existing equipment protection group.
Related information
For a more detailed explanation, please refer to the description of the OPR-PROTNSW
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Protection Groups.
In the Function field, select Operate Protection Switch - 1+1 Equipment Group.
Click Go.
Result: The Operate Protection Switch - 1+1 Equipment Group page is
displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
In the field Protection group identifier, enter the ID of the protection group for which
the information should be retrieved. In the field Protection type, select a type of
equipment protection group.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-61
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
To operate an equipment protection group
The following table shows the possible combinations:
Type of equipment protection
Value for Protection group
Value for Protection type
identifier
Higher-order switch fabric and timing
1-1-estgrp
Switch Fabric
System controller
1-1-ectlgrp
System Controller
Electrical 51 Mbps interfaces
1-1-eep{01{99}
EP51 Circuit Pack
Electrical 155 Mbps interfaces
1-1-eep{01{99}
EP155 Circuit Pack
Lower-order switch fabric
1-1-eloxc1
LOXC Circuit Pack
Note that the last character of
this identifier is the digit one.
Destination specifies the destination of the switch command; that means which side
shall be active in terms of the member role within the protection group after the switch
has been executed. The following values are supported: Worker, Protection.
Switch command specifies the switch command to be executed by the protection state
machine. Select one of the following values: Forced switch (for all equipment
protection types), or Manual switch (for all equipment protection types but system
controller protection).
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-62
Equipment provisioning tasks
To
release an equipment protection group
...................................................................................................................................................................................................................................
When to use
Use this task to release an existing equipment protection group, that means to clear
protection switch requests.
Related information
For a more detailed explanation, please refer to the description of the RLS-PROTNSW
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Protection Groups.
In the Function field, select Release Protection Switch - 1+1 Equipment Group.
Click Go.
Result: The Release Protection Switch - 1+1 Equipment Group page is
displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
In the field Protection group identifier, enter the ID of the protection group for which
the information should be retrieved. In the field Protection type, select a type of
equipment protection group.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-63
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
To release an equipment protection group
The following table shows the possible combinations:
Type of equipment protection
Value for Protection group
Value for Protection type
identifier
Higher-order switch fabric and timing
1-1-estgrp
Switch Fabric
System controller
1-1-ectlgrp
System Controller
Electrical 51 Mbps interfaces
1-1-eep{01{99}
EP51 Circuit Pack
Electrical 155 Mbps interfaces
1-1-eep{01{99}
EP155 Circuit Pack
Lower-order switch fabric
1-1-eloxc1
LOXC Circuit Pack
Note that the last character of
this identifier is the digit one.
Switch command specifies the switch command to be executed by the protection state
machine. Select Clear.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-64
Equipment provisioning tasks
To
delete an equipment protection group
...................................................................................................................................................................................................................................
When to use
Use this task to delete an existing equipment protection group.
The following types of equipment protection groups can be deleted:
•
•
•
Electrical 51 Mbps interfaces protection
Electrical 155 Mbps interfaces protection
Lower-order switch fabric protection
Related information
For a more detailed explanation, please refer to the description of the DLT-PROTN-GRP
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
In
In
In
In
the
the
the
the
NE type field, select a type of NE (if not already present).
NE name field, select the name of the target NE (if not already present).
Category field, select Protection Groups.
Function field, select Delete Protection Group - Equipment Protection
Group.
5. Click Go.
Result: The Delete Protection Group - Equipment Protection Group page is
displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
6-65
Issue 2, July 2008
See notice on first page
Equipment provisioning tasks
To delete an equipment protection group
In the field Protection group identifier, enter the ID of the protection group for which
the information should be retrieved. In the field Protection type, select a type of
equipment protection group.
The following table shows the possible combinations:
Type of equipment protection
Value for Protection group
Value for Protection type
identifier
Electrical 51 Mbps interfaces
1-1-eep{01{99}
EP51 Circuit Pack
Electrical 155 Mbps interfaces
1-1-eep{01{99}
EP155 Circuit Pack
Lower-order switch fabric
1-1-eloxc1
LOXC Circuit Pack
Note that the last character of
this identifier is the digit one.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
6-66
7
Timing provisioning concepts
7
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter presents concept information related to timing provisioning on
LambdaUnite ® MSS network elements using Lucent OMS.
Contents
NE timing – general functional overview
7-2
Timing interfaces
7-6
Timing references
7-9
Timing link switches
7-12
The internal timing generator
7-18
Timing quality
7-20
Timing protection
7-21
Synchronization characteristics – external timing inputs
7-23
Synchronization characteristics – external timing outputs
7-25
Synchronization characteristics – assigned timing references
7-30
Synchronization characteristics – system timing
7-35
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
7-1
Issue 2, July 2008
See notice on first page
Timing provisioning concepts
NE
timing – general functional overview
...................................................................................................................................................................................................................................
Introduction
Each LambdaUnite ® MSS network element provides two external timing inputs
(station clock inputs) and two external timing outputs (station clock outputs), located
on the timing interfaces (TI A and TI B) which are accessible from the rear side of
the shelf.
A station clock input is an external interface where an external timing reference signal
can be supplied. A station clock output is an external interface where an external
timing reference signal can be made available which can be used to synchronize other
equipment in the same office. Besides the external timing references, up to six line
timing references (clock information derived from STM-n or OC-m input ports) can be
used for synchronization purposes.
TI B
TI A
IN
Ext. timing
references
(station clock inputs)
OUT
Ext. timing
references
(station clock outputs)
XC
Line timing
references
6
Cross-connect
and
timing unit
STM-N/OC-M
output ports
The timing reference information is processed by the system timing function located on
the cross-connection and timing units (XC160, XC320, XC640).
NE synchronization mode
The synchronization characteristics of a LambdaUnite ® MSS system depend on the
configurable NE synchronization mode. The NE synchronization mode basically
impacts the NE-internal functional details, the expected external timing reference
signals, the synchronization status message (SSM) handling, and the output timing
mode of operation.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
7-2
Timing provisioning concepts
NE timing – general functional overview
LambdaUnite ® MSS network elements support these NE synchronization modes:
SDH synchronization
mode
The system timing complies with SDH synchronization
requirements. The SDH synchronization mode should be
chosen when a LambdaUnite ® MSS network element is to
be integrated into an SDH network environment.
SONET synchronization
mode
The system timing complies with SONET synchronization
requirements. The SONET synchronization mode should be
chosen when a LambdaUnite ® MSS network element is to
be integrated into a SONET network environment.
The NE-internal functional details that depend on the NE synchronization mode will
subsequently be explained in more detail.
SDH- and SONET-specific functional implementation
The implementations of the timing functionality for SDH and SONET are very similar.
However, they differ in some details. The SDH implementation has a separate output
timing link switch for example, while the SONET implementation has two hardwired
output lines.
The following two functional block diagrams serve to illustrate both the commonalities
as well as the differences. However, not all aspects can be covered in these diagrams
(for example the supported types of external timing input signals). These aspects will
be dealed with in the subsequent sections.
SDH-specific timing functionality
The following functional block diagram gives an overview of the SDH-specific timing
functionality of a LambdaUnite ® MSS network element:
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
7-3
Issue 2, July 2008
See notice on first page
Timing provisioning concepts
NE timing – general functional overview
External timing
inputs
➀
Timing generator
(system clock)
External
reference 1
External
reference 2
Timing refernece assignment
➁
System
timing link
switch
(TLS)
~
Line
reference 1
Holdover
memory
Line
reference 2
STM-N/OC-M
output port
Line
reference 3
Line
reference 4
SETG
Line
reference 5
Line
reference 6
STM-N/OC-M input
ports
(line timing inputs)
STM-N/OC-M
output port
➀
Output
timing link
switch
(TLS)
➁
TLS
Output
selection
External timing
outputs
SONET-specific timing functionality
The following functional block diagram gives an overview of the SONET-specific
timing functionality of a LambdaUnite ® MSS network element:
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
7-4
Timing provisioning concepts
NE timing – general functional overview
External timing
inputs
➀
Timing generator
(system clock)
External
reference 1
External
reference 2
Timing refernece assignment
➁
Line
reference 1
Line
reference 2
System
timing link
switch
(TLS)
~
Holdover
memory
STM-N/OC-M
output port
Line
reference 3
Line
reference 4
Line
reference 5
Line
reference 6
STM-N/OC-M input
ports
(line timing inputs)
STM-N/OC-M
output port
Line reference 1
Line reference 2
➀
➁
External timing
outputs
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
7-5
Issue 2, July 2008
See notice on first page
Timing provisioning concepts
Timing
interfaces
...................................................................................................................................................................................................................................
Overview
Each LambdaUnite ® MSS network element can be equipped (from the rear side of the
shelf) with up to two timing interfaces (TI A, TI B).
Each timing interface provides an external timing input and an external timing output.
External timing inputs
An external timing input (station clock input) is an interface port which is specifically
used to extract a synchronization reference to be used in the network element. A station
clock input can be used for timing purposes only, it cannot be used for data transport.
The format of the station clock input signal is provisionable. These signal formats are
supported, depending on the NE synchronization mode:
•
•
SDH synchronization mode:
– 2048 kHz (2 MHz) acc. to ITU-T Rec. G.703. This is the default setting in the
SDH synchronization mode.
– Unframed 2 Mbps acc. to ITU-T Rec. G.703.
– Framed 2 Mbps acc. to ITU-T Rec. G.703 with a frame/multiframe structure
acc. to G.704.
SONET synchronization mode:
– DS1 Superframe Format (DS1 SF) with B8ZS line code acc. to the Telcordia
Technologies GR-499-CORE standard.
– DS1 Extended Superframe Format (DS1 ESF) with B8ZS line code acc. to the
Telcordia Technologies GR-499-CORE standard. This is the default setting in
the SONET synchronization mode.
The following diagram gives a functional overview (including the provisioning
options):
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
7-6
Timing provisioning concepts
Timing interfaces
Sa bit location
(2 Mbps framed)
input type
selection
SSM support
enabled/disabled
Management
interface
SDH
2 MHz
2 Mbps
unframed
ext. timing
input signal
reference signal
(to the system
timing link switch)
2 Mps
framed
DS1 SF
DS1 ESF
SSM
extraction
defect indications
SONET
At the external timing inputs, the incoming signal is terminated, and the timing
reference information is derived. Furthermore, the external timing input signal is
monitored for defects, and the Synchronization Status Message (SSM) is extracted,
where applicable (2 Mbps framed and DS1 ESF input signals with SSM support
enabled). The SSM is used by the system timing link switch to select the best available
reference signal.
Lockout of an external timing input
It is possible to temporarily lockout an external timing input. A locked out timing input
is not available for timing reference selection.
External timing outputs
The external timing outputs (station clock outputs) can be used to synchronize other
equipment in the same office.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
7-7
Issue 2, July 2008
See notice on first page
Timing provisioning concepts
Timing interfaces
The format of the station clock output signals is provisionable. These signal formats
are supported, depending on the NE synchronization mode:
•
•
SDH synchronization mode:
– 2048 kHz (2 MHz) acc. to ITU-T Rec. G.703. This is the default setting in the
SDH synchronization mode.
– Unframed 2 Mbps acc. to ITU-T Rec. G.703.
– Framed 2 Mbps acc. to ITU-T Rec. G.703 with a frame/multiframe structure
acc. to G.704.
SONET synchronization mode:
– DS1 Superframe Format (DS1 SF) with B8ZS line code acc. to the Telcordia
Technologies GR-499-CORE standard.
– DS1 Extended Superframe Format (DS1 ESF) with B8ZS line code acc. to the
Telcordia Technologies GR-499-CORE standard. This is the default setting in
the SONET synchronization mode.
The clock reference for the station clock outputs also depends on the NE
synchronization mode:
•
•
SDH synchronization mode:
The timing reference signal for the external timing outputs can be derived either
from the NE-internal timing generator (SETG, “Synchronous Equipment Timing
Generator”), or, via the output timing link switch (TLS), from the line timing
references 1 to 6.
The same timing reference signal is available at both station clock outputs.
SONET synchronization mode:
The timing reference signals for the external timing outputs are derived directly
from the line timing references 1 and 2:
– The timing reference signal for the external timing output 1 is derived directly
from line timing reference 1.
– The timing reference signal for the external timing output 2 is derived directly
from line timing reference 2.
It is possible to provision different signal formats for the two station clock output
signals.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
7-8
Timing provisioning concepts
Timing
references
...................................................................................................................................................................................................................................
Up to eight timing references
The total number of timing references is limited to eight, two external timing
references and six line timing references:
ext. timing
input 1
ext. timing ref. 1
ext. timing
input 2
ext. timing ref. 2
optical or electrical
SDH/SONET ports
line timing ref. 1
line timing ref. 2
line timing ref. 3
line timing ref. 4
line timing ref. 5
line timing ref. 6
External timing references
There is a direct and fix relation between the two external timing inputs (station clock
inputs) and the two external timing references:
•
•
Ext. timing input 1 → ext. timing reference 1
Ext. timing input 2 → ext. timing reference 2
However, the two external timing inputs are not automatically assigned as external
timing references. This assignment needs to be done manually (and individually for
both external timing references), and the internal timing generator needs to be operated
in locked mode for the external timing reference assignment to take effect.
Important! When the system clock is locked to an external timing reference, then
removing or replacing the standby cross-connection and timing unit (XC160,
XC320, XC640) causes the external timing reference to be declared failed
temporarily, and a timing reference switch will occur.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
7-9
Issue 2, July 2008
See notice on first page
Timing provisioning concepts
Timing references
You have the following options:
•
•
Before removing or replacing the standby cross-connection and timing unit,
make sure that the system clock is not locked to an external timing reference by
manually switching to a different timing reference, or entering the forced
holdover mode.
Accept the intermediate timing reference switch (traffic is not affected).
Line timing references
Up to six out of the available incoming SDH/SONET transport signals can be assigned
as line timing references. An 8-kHz timing reference signal is then derived from the
inherent clock information.
The assignment needs to be done manually by specifying an SDH/SONET port as a
line timing reference.
Important! Please observe these guidelines concerning the line timing reference
assignment:
a
Only one SDH/SONET port per port unit can be assigned as a line timing
reference.
b
The line timing reference assignment will have no effect on the system timing
unless the Clock Mode of the System Timing is set to Locked.
c
Due to their role in the internal data communication between port units and the
cross-connection and timing unit, it is not possible to select one of the following
input ports as a line timing reference:
• 2.5-Gbps port units (OP2G5): port 4
• 622-Mbps port units (OP622): ports 6, 7, 13, and 14
This applies to all OP2G5 or OP622 port units, and independent of the slot
position where they are installed.
d
The OPT2G5 input signals cannot be used as line timing references because the
Multiplex Section (MS) layer is neither terminated nor monitored on the OPT2G5
port unit. On the multiplex section (MS) layer, the synchronization status message
(SSM) functionality is located in the client signal.
e
EP51/EL36 port units: EC-1 or DS3 input signals cannot be used as line timing
references. In the outgoing direction, however, the synchronization status message
(SSM) is supported.
f
When you assign a line timing reference while the timing generator operates in
autonomous holdover mode, then a Loss of Synchronisation alarm will be
reported for 10 seconds which, however, can be ignored. The timing functionality
is not impaired.
g
GE1 and GE10PL1 port units: Gigabit Ethernet input signals at GE1, 1GEPL, or
10GEPL ports cannot be used as line timing references.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
7-10
Timing provisioning concepts
h
Timing references
The input signals of port 4 and port 8 of an OP2G5D/PAR8 port unit cannot be
used as line timing references.
Timing reference selection
The LambdaUnite ® MSS timing function is designed such that always the most
suitable clock source is selected for synchronization.
The selection is based on the quality of the available timing reference signals in
combination with their provisionable priority:
•
•
If the System SSM Mode is set to QL Enable (that means the SSM information is
evaluated), then initially the signal with the highest quality level is used as the
timing reference signal. If it fails, the system switches to the signal with the next
lower quality level. If there are several timing references with the same quality
level, they are used according to the priority list.
If the System SSM Mode is set to QL Disable, then only the priorities of the
timing reference signals are evaluated.
If all possible timing reference signals fail, then the timing generator autonomously
enters the holdover mode.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
7-11
Issue 2, July 2008
See notice on first page
Timing provisioning concepts
Timing
link switches
...................................................................................................................................................................................................................................
Two types of timing link switches
LambdaUnite ® MSS supports two types of timing link switches:
•
•
System timing link switch
Output timing link switch (only in the SDH synchronization mode)
Automatic timing reference selection
A timing link switch (TLS) allows reference switching between all possible timing
references. By means of a provisional input port priority scheme and, optionally,
quality levels (QLs, determined by evaluating the synchronization status message
(SSM)), one of the inputs is selected as the reference to be forwarded to either the
internal timing generator (in the case of the system timing link switch), or to the
external timing output selection (in the case of the output timing link switch).
System timing link switch
The system timing link switch has access to all available timing references (external as
well as line timing references). It is used to supply the internal timing generator with
the best available clock source. The internal timing generator then provides the clock
information for the SDH/SONET output ports.
Priorities
ext. timing ref. 1
ext. timing ref. 2
line timing ref. 1
line timing ref. 2
line timing ref. 3
line timing ref. 4
line timing ref. 5
line timing ref. 6
Switch
requests
QL enabled/
QL disabled
Management
interface
system clock
Re-synchronization after frequency offsets
In case of a frequency offset at a timing input port which is currently used as the
active system timing reference, a re-synchronization process starts which may last up
to 180 seconds, depending on the size of the frequency step (a frequency offset of 5
ppm requires a re-synchronization period of approximately 24 seconds, for example).
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
7-12
Timing provisioning concepts
Timing link switches
Usually, frequency offsets up to 12 ppm do not cause a timing reference protection
switch, and are not externally visible. However, should it happen that you perform an
XC protection switch immediately after such a frequency offset, then an output timing
reference switch and even TXI failures might occur which will afterwards be cleared
autonomously.
Output timing link switch
The output timing link switch is only supported in the SDH synchronization mode.
The output timing link switch has access to all available line timing references. It has
no access to the external timing references because this could lead to undesirable
synchronization loops in the office.
Priorities
Switch
requests
QL enabled/
QL disabled
Management
interface
line timing ref. 1
line timing ref. 2
external timing
output selection
line timing ref. 3
line timing ref. 4
line timing ref. 5
line timing ref. 6
The output timing link switch is used to provide the external timing output selection
with the best available line timing reference. Alternatively, the clock source for the
external timing outputs can also be derived from the internal timing generator
(synchronous equipment timing generator, SETG).
System clock (SETG)
➀
line timing ref. 1
line timing ref. 2
line timing ref. 3
line timing ref. 4
line timing ref. 5
line timing ref. 6
Output
timing link
switch
➁
TLS
Output
selection
External timing
outputs
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
7-13
Issue 2, July 2008
See notice on first page
Timing provisioning concepts
Timing link switches
Reference priorities
An input of a timing link switch can be assigned a priority between “1” (highest
priority) and “8” (lowest priority). Furthermore, it is also possible to assign a priority
of “0”, which means to disable the corresponding input. It is possible to assign the
same priority to multiple inputs.
Priority
Meaning
0
Disabled
1
Highest priority
↓
↓
8
Lowest priority
Enabled
The selection between revertive and non-revertive mode is achieved via the priority
setting of a timing reference. All references with the same priority are non-revertive
timing references. If two timing references are the same in terms of quality level (QL)
provisioning, revertive switching is provisioned by giving one timing reference a
higher priority than the other. The timing reference with the highest priority always
will be the active timing reference (if both are available).
In the default setting, all inputs are disabled (priority = 0).
Besides the possibility to permanently disable an input of a timing link switch, it is
also possible to temporarily exclude an input.
Timing reference switching
LambdaUnite ® MSS systems provide revertive timing reference switching between the
enabled inputs of a timing link switch.
The selection criteria for the automatic timing reference selection are based on quality
and priority, and can be provisioned to one of the following modes:
Quality level (QL) enabled mode
(default setting)
The automatic timing reference selection is based
on the incoming quality level (= Synchronization
Status Message (SSM)) in combination with the
reference priority.
Quality level (QL) disabled mode
The automatic timing reference selection is based
on the reference priority only.
Manual timing reference switching is also possible by means of specific switch
requests.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
7-14
Timing provisioning concepts
Timing link switches
Timing reference switching in QL-enabled mode
In the QL-enabled mode, the timing reference selection is according to the following
criteria, provided that no external forced or manual switch request is active:
1. The active timing reference is selected from all the enabled inputs (enabled and not
locked out) which have a quality level better than “Do not use for synchronization”
(DNU/DUS).
2. Out of these timing references, the reference with the highest quality level is
selected.
The following order of quality levels applies (in decreasing order of quality from
left to right):
• SDH: PRC → SSU_T → SSU_L → SEC → DNU
• SONET: PRS → STU → ST2 → ST3 → DUS
If there is more than one reference with the same highest quality level, then the
reference with the highest priority is selected, if the priority is unique. If a group of
references has the same highest priority (and the same highest quality level), then
the existing reference selection remains unchanged if the selected reference is
among this group. Otherwise, an arbitrary reference from this group is selected.
3. If a timing reference can be selected, then the output of the timing link switch
forwards the corresponding quality level.
If no timing reference can be selected, then the output forwards the signal status
“Unacceptable” and the quality level “Do not use for synchronization”
(DNU/DUS).
The automatic timing reference selection is triggered by the following events:
•
•
•
•
•
•
The QL-enabled mode is activated, and no external forced or manual switch request
is active.
A change of the quality level is detected on an enabled input (enabled and not
locked out), and no external forced switch request overrides the autonomous
selection.
A change of reference priority is detected on an enabled input (enabled and not
locked out), and no external forced or manual switch request overrides the
autonomous selection.
An active external forced or manual switch request is cleared.
Timing references are enabled or cleared from lockout, while no external forced or
manual switch is active.
The currently active timing reference is disabled or locked out.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
7-15
Issue 2, July 2008
See notice on first page
Timing provisioning concepts
Timing link switches
Timing reference switching in QL-disabled mode
In the QL-disabled mode, the timing reference selection is according to the following
criteria, provided that no external forced or manual switch request is active:
1. The active timing reference is selected from all the enabled inputs (enabled and not
locked out) which have a “Normal” signal status.
2. Out of these timing references, the reference with the highest priority is selected.
If a group of references has the same highest priority, then the existing reference
selection remains unchanged if the selected reference is among this group.
Otherwise, an arbitrary reference from this group is selected.
3. If a timing reference can be selected, then the output of the timing link switch
forwards the signal status “Normal”.
If no timing reference can be selected, then the output forwards the signal status
“No Signal”.
In case the System SSM Mode is set to QL Disable, then the signal forwarded by the
output timing link switch depends on the timing generator operational mode as follows:
Timing generator
operational mode
Signal forwarded by the output timing link switch
Normal
“Do not use for synchronization” (DNU/DUS) in both
synchronization modes
Locked
Forced Holdover
Free Running
Autonomous
Holdover
“Do not use for synchronization” (DNU) in the SDH
synchronization mode,
“Synchronized - Traceability Unknown” (STU) in the SONET
synchronization mode
The automatic timing reference selection is triggered by the following events:
•
•
•
•
•
•
The QL-disabled mode is activated, and no external forced or manual switch
request is active.
A change of the signal status is detected on an enabled input (enabled and not
locked out), and no external forced switch request overrides the autonomous
selection.
A change of reference priority is detected on an enabled input (enabled and not
locked out), and no external forced or manual switch request overrides the
autonomous selection.
An active external forced or manual switch request is cleared.
Timing references are enabled or cleared from lockout, while no external forced or
manual switch is active.
The currently active timing reference is disabled or locked out.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
7-16
Timing provisioning concepts
Timing link switches
External switch requests
These external switch requests exist:
Switch request
Meaning
Lockout
can be used to temporarily disable (lock out) an input of
a timing link switch.
The “ABN” LED on the user panel is lit while this
request is active, and a corresponding abnormal condition
event will be shown.
Clear lockout
clears (reverts) a lockout request.
Forced switch to reference
can be used to force the selection of a desired (not locked
out) timing reference for timing reference selection.
The “ABN” LED on the user panel is lit while this
request is active, and a corresponding abnormal condition
event will be shown.
Manual switch to reference
can be used to switch to another (not locked-out) timing
reference, provided that the quality of the desired timing
reference equals the quality of the previously active
timing reference.
Clear reference switch
clears (reverts) a manual or forced switch request.
Clear wait-to-restore (not
applicable to the SDH
output timing link switch)
can be used to terminate the wait-to-restore period, i.e. to
reset the wait-to-restore timer immediately.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
7-17
Issue 2, July 2008
See notice on first page
Timing provisioning concepts
The
internal timing generator
...................................................................................................................................................................................................................................
Function of the timing generator
LambdaUnite ® MSS synchronizes all add, drop and through signals by using one
timing source. The timing is ensured by the internal timing generator on the
cross-connection and timing unit which generates one common internal clock. When
two cross-connection and timing units are present in the NE, a 1+1 non-revertive
protection of the timing function is provided.
System timing operational modes
The LambdaUnite ® MSS internal timing generator can be operated in one of the
following modes:
•
•
•
Locked mode
The system clock is locked to one of the two external timing references or one of
the six line timing references.
Free-running mode
The internal timing generator is supplying timing to the system, uncorrected by any
external or line timing references, and independent from historical reference data.
This is the default value of the system timing operational mode (especially needed
for the initial startup of an NE when no valid timing references are assigned).
The “ABN” LED on the user panel is lit as long as the timing generator operates in
the free-running mode, and a corresponding abnormal condition event will be
shown.
It is strongly recommended to switch from the free-running mode to the locked
mode as soon as valid timing references are available and assigned.
Holdover mode
The timing generator autonomously enters the holdover mode if all timing
reference signals fail (autonomous holdover mode). The internal oscillator on the
timing generator supplies a clock signal with a frequency that matches the last
known good reference frequency as close as possible within the limits of the
internal oscillator’s frequency accuracy (holdover accuracy). The timing generator
will revert to normal operation (locked mode) as soon as the incoming timing
reference signal becomes acceptable again.
Additionally it is also possible to force the internal oscillator on the timing
generator into the holdover mode (forced holdover mode).
Switching to the holdover mode is only possible from the locked mode.
The “ABN” LED on the user panel is lit as long as the timing generator operates in
the forced holdover mode, and a corresponding abnormal condition event will be
shown. No abnormal condition will be indicated when the timing generator operates
in the autonomous holdover mode.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
7-18
Timing provisioning concepts
The internal timing generator
Important! When you assign a line timing reference while the timing generator
operates in autonomous holdover mode, then a Loss of Synchronisation alarm
will be reported for 10 seconds which can be ignored. The timing functionality is
not impaired.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
7-19
Issue 2, July 2008
See notice on first page
Timing provisioning concepts
Timing
quality
...................................................................................................................................................................................................................................
Synchronization status message
A synchronization status message (SSM) is defined for SDH/SONET transport signals,
and for framed 2-Mbps and DS1 ESF external timing input signals.
The purpose of the SSM is to signal the reference clock quality level from NE to NE
to:
•
•
•
enable the timing generator to extract the timing reference signal with the best
quality,
make it possible to autonomously enter the holdover mode in case there is no
suitable timing reference signal, and to
prevent timing loops.
These timing quality levels are defined (top down in decreasing order of timing
quality):
SDH
SONET
Timing quality
PRC
PRS
best timing quality
SSU-T
STU
↓
SSU-L
ST2
↓
SEC
ST3
↓
DNU
DUS
↓
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
7-20
Timing provisioning concepts
Timing
protection
...................................................................................................................................................................................................................................
Timing reference protection switching
If the system SSM mode is set to QL enable, then initially the signal with the highest
quality level is used as timing reference signal. If it fails, the system switches to the
signal with the next lower quality level. If there are several timing references with the
same quality level, they are used according to the priority list.
If the system SSM mode is set to QL disable, then only the priorities of the timing
reference signals are evaluated.
If all possible timing reference signals fail, then the timing generator enters the
holdover mode.
The following signals can be used as a timing reference:
•
•
2 external netclock input signals (2048 kHz or 2 Mbps acc. to G.703)
6 reference signals derived from the incoming STM-n/OC-m line signals (n = 1, 4,
16, 64, 256; m = 3, 12, 48, 192, 768).
Timing equipment protection switching
A network element can contain two cross-connection and timing units (XC160, XC320,
XC640) on which the timing function is located. If there are two timing functions, then
timing equipment protection switching is possible.
When two timing circuit packs are present the timing is derived from one circuit pack,
called the active timing circuit pack. The other timing circuit pack is standby. It
produces the same timing signal as the active one but is not used, unless the active
timing circuit pack fails.
For the initial start-up of the system and initial provisioning of the 1+1 protection
group the free running mode is used. For the system reset after the 1+1 protection was
in operation, the system restores the cross-connection and timing unit as the active one
which was active before the system reset operation.
If only one cross-connection and timing unit is present (worker) and the protection
cross-connection and timing unit is inserted, LambdaUnite ® MSS is in a warm-up state
for about 6 minutes. During this time the system timing quality is set to “Do not use
for synchronization” (DNU/DUS). During this state it is not allowed to perform a
manual switch command to the standby cross-connection and timing unit.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
7-21
Issue 2, July 2008
See notice on first page
Timing provisioning concepts
Timing protection
Wait-to-restore time
If a timing signal is restored, then – after a defined period of time (wait-to-restore
time, WTR) – a decision is made based on the timing quality and on priority selection
criteria, which signal to select. If the same signal has the best quality and/or highest
priority, then the same signal will be selected, else another signal.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
7-22
Timing provisioning concepts
Synchronization
characteristics – external timing inputs
...................................................................................................................................................................................................................................
Overview
LambdaUnite ® MSS provides two external timing inputs:
•
•
External Input 1
External Input 2
The configuration parameters of these external timing inputs are described in the
following.
External input signal format
The External input signal format is the format of the external timing input signal.
These external timing input signal formats are supported:
SDH synchronization
mode
2MHZ: 2-MHz signal (default setting)
2MBIT-FRAMED: framed 2-Mbps signal
2MBIT-UNFRAMED: unframed 2-Mbps signal
SONET synchronization
mode
SF (DS1 Super Frame)
ESF (DS1 Extended Super Frame)
ISSM support
The synchronization status message (SSM) support can be enabled for framed 2-Mbps
(SDH synchronization mode) and ESF (SONET synchronization mode) external timing
input signals.
Possible settings of the ISSM Support parameter are:
SUPPORTED
The SSM support is enabled.
This is the default setting in the SONET synchronization
mode.
NOT-SUPPORTED
The SSM support is disabled.
This is the default setting in the SDH synchronization mode.
Sa bit location
This parameter is only applicable in the SDH synchronization mode, and only in case
the selected signal format is 2MBIT-FRAMED, and SSM Support is enabled.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
7-23
Issue 2, July 2008
See notice on first page
Timing provisioning concepts
Synchronization characteristics – external timing inputs
If the SSM Support is disabled, then the value of the SA bit Location parameter is of
no relevance.
If the SSM Support parameter is enabled, then the SSM is extracted from the Sa bits
starting at the location defined by the SA bit Location parameter.
Possible values are:
•
•
•
SA4 (default setting)
•
•
SA7
SA5
SA6
SA8
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
7-24
Timing provisioning concepts
Synchronization
characteristics – external timing outputs
...................................................................................................................................................................................................................................
Overview
The system provides two external timing output ports. Depending on the system timing
mode, the output ports have different meanings:
•
•
SDH synchronization mode:
The output signals of the two external timing output ports are identical. Therefore,
only the first external timing output port (External Output 1) is displayed
representing the parameters of the external timing output ports 1 and 2.
SONET synchronization mode:
The output signals of the two external timing output ports are different. Therefore,
each of the two external timing output ports (External Output 1, External Output
2) is displayed individually. The same is true for the provisioning of the external
timing output ports.
The Signal Format of the output signals is the same as the signal format at the
external timing input ports.
The output signal selected depends on the state of the Prov. Source Selection
parameter:
SETG (Synchronous
The output signal is derived from the system clock.
Equipment Timing
Generator)
TLS (Timing Link
The output signal is derived from the Timing Link Switch.
Switch)
Availability of output signals
The availabilty of output signals depends on the system timing mode:
•
•
SDH mode:
Both external timing output ports are connected to both cross-connection and
timing units (worker in slot 9, protection in slot 10). If at least one of the two
cross-connection and timing units is present, and if the external timing output ports
are enabled, then there are output signals available at all times.
SONET mode:
Each external timing output port is connected to a particular cross-connection and
timing unit (XC). The External Output 1 is connected to the XC in slot 9 (worker)
while the External Output 2 is connected to the XC in slot 10 (protection).
If only one cross-connection and timing unit is present, then an output signal is
available only at the corresponding external timing output port (provided that the
output is enabled).
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
7-25
Issue 2, July 2008
See notice on first page
Timing provisioning concepts
Synchronization characteristics – external timing outputs
Derived output timing
Parameter
Possible values
Meaning
External output
enable
ENABLE,
This parameter indicates whether a timing signal is forwarded to the
output port.
External timing
outut selection
SDH mode:
DISABLE (default)
•
SETG (default setting)
This parameter indicates from which source the external timing signal
is derived.
•
TLS
SDH mode:
SONET mode:
•
LINE1
•
LINE2
•
SETG (Synchronous Equipment Timing Generator)
The external timing output signal is derived from the system
clock.
•
TLS (Timing Link Switch)
The external timing output signal is derived from one of the six
timing references.
In principle, the same selection criteria apply as for system timing.
The following preconditions must be fulfilled for a timing
reference to be selectable as an external timing output signal:
–
The Output Ref. Priority must be enabled (i.e. must have a
value between 1 and 6, but must not be disabled).
–
The Lockout Status must be set to No Lockout.
–
If the System SSM Mode is set to QL Enable, then signals
with a valid quality level other than “Do not use for
synchronization” (DNU/DUS) can be selected.
SONET mode:
•
The external timing output port 1 is fix connected to the line
timing reference 1.
•
The external timing output port 2 is fix connected to the line
timing reference 2.
Signal settings
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
7-26
Timing provisioning concepts
Synchronization characteristics – external timing outputs
Parameter
Possible values
Meaning
External Timing
Output Format
SDH synchronization mode:
This parameter shows the signal format of the outgoing timing
signal:
•
2MHZ (default setting)
•
2MBIT-FRAMED
•
2MBIT-UNFRAMED
•
SONET synchronization mode:
•
SF
•
ESF (default setting)
SDH synchronization mode:
–
2MHZ: 2-MHz signal
–
2MBIT-FRAMED: framed 2-Mbps signal
For framed 2-Mbps timing signals, the generation and
evaluation of synchronization status message (SSM)
information on the timing quality is supported as per
ITU-T Rec. G.704.
–
•
2MBIT-UNFRAMED: unframed 2-Mbps signal
SONET synchronization mode:
–
SF: DS1 Super Frame
–
ESF: DS1 Extended Super Frame
For DS1 ESF timing signals, the generation and
evaluation of synchronization status message (SSM)
information on the timing quality is supported as per
the Telcordia Technologies GR-253-CORE standard.
Cable Equalization
•
20% (default setting)
•
40%
•
60%
•
80%
•
100%
The Cable Equalization parameter is available in the SONET
synchronization mode only.
It determines the timing output cable equalization to adjust the
specified timing reference output signal power (in order to
compensate a given cable attenuation).
All percentage values relate to the given max. cable attenuation of
3 dB:
•
0.6 dB cable attenuation → 20% cable equalization
1.2 dB cable attenuation → 40% cable equalization
1.8 dB cable attenuation → 60% cable equalization
2.4 dB cable attenuation → 80% cable equalization
3 dB cable attenuation → 100% cable equalization
Regenerator
Parameter
Possible values
Meaning
Timing
Regenerator Loop
Delay
0 ... 60 s
Delay during which DNU/DUS (do not use) is maintained after the
Regenerator Loop conditions are no longer present.
The default value is 10 s.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
7-27
Issue 2, July 2008
See notice on first page
Timing provisioning concepts
Parameter
Possible values
Timing
Regenerator Loop
SDH synchronization mode:
Synchronization characteristics – external timing outputs
Meaning
This parameter serves to avoid timing loops in the office between the timing outputs and one or both
of the timing inputs through a stand-alone synchronization equipment (SASE) office clock.
The meaning of the possible settings is as follows:
•
DISABLE (default setting)
The regenerator loop functionality is disabled. Timing loops are not considered.
•
EXTREF1: External reference 1
If the quality level of the incoming framed 2-Mbps timing signal at the external timing input 1 is
equal to the quality level of the timing signal that is transmitted to the external timing output
ports, “Do not use for synchronization” (DNU) is inserted for the outgoing timing signal as a
timing loop might be present.
•
EXTREF2: External reference 2
If the quality level of the incoming framed 2-Mbps timing signal at the external timing input 2 is
equal to the quality level of the timing signal that is transmitted to the external timing output
ports, “Do not use for synchronization” (DNU) is inserted for the outgoing timing signal as a
timing loop might be present.
•
BOTH
The regenerator loop functionality is applied to both external timing inputs.
Timing loops might occur, if the NE forwards timing to an SASE via one or both of the external
timing output ports, and at the same time receives a timing signal from the same SASE via one or
both of the external timing input ports. If Regenerator Loop is set, and the system clock is operated
in the locked mode, and derived from an external timing input signal, then “Do not use for
synchronization” (DNU) is forwarded to the timing outputs to avoid such timing loops.
SONET synchronization mode:
This parameter serves to avoid timing loops in the office between the timing outputs and one or both
of the timing inputs through a building integrated timing supply (BITS) office clock.
The meaning of the possible settings is as follows:
•
•
ENABLE (default setting)
The regenerator loop functionality is applied to both external timing inputs.
DISABLE
The regenerator loop functionality is disabled. Timing loops are not considered.
Timing loops might occur, if the NE forwards timing to a BITS via one or both of the external
timing output ports, and at the same time receives a timing signal from the same BITS via one or
both of the external timing input ports. If Regenerator Loop is set, and the system clock is operated
in the locked mode, and derived from an external timing input signal, then “Do not use for
synchronization” (DUS) is forwarded to the timing outputs to avoid such timing loops.
SSM parameters
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
7-28
Timing provisioning concepts
Synchronization characteristics – external timing outputs
Parameter
Possible values
Meaning
External output SA bit
Location
SA4 (default setting)
This parameter is only applicable in the SDH synchronization
mode, and only in case the selected signal format is
2MBIT-FRAMED, and SSM Support is enabled.
SA5,
SA6,
If the SSM Support is disabled, then the value of the SA bit
Location parameter is of no relevance.
SA7,
External timing output AIS
Mode
SA8
If the SSM Support parameter is enabled, then the SSM is
extracted from the Sa bits starting at the location defined by
the SA bit Location parameter.
AIS MODE,
This parameter is only supported in case the selected signal
format is framed 2-Mbps (SDH synchronization mode), or
DS1 ESF (SONET synchronization mode), respectively.
QL MODE (default)
It specifies which type of signal (AIS or DNU/DUS) will be
inserted into the outgoing timing signal if the signal quality is
below the quality acceptance level (Acc. QL for AIS), or if “Do
not use for synchronization” (DNU/DUS) is forced to be
consistently inserted into the outgoing timing signal (Sync
Message Force DNU / Sync Message Force DUS).
Accept. qual level-out thrs.
AIS
SDH synchronization mode:
PRC,
SSUT,
SSUL,
SEC (default setting)
This parameter defines the quality acceptance level for
external timing output signals.
When the incoming signal is below this level, then AIS or
“Do not use for synchronization” (DNU/DUS) will be inserted
into the external timing output signal, depending on the AIS
Mode setting.
SONET synchronization
mode:
PRS,
STU,
ST2.,
ST3 (default setting)
Alarming
Parameter
Possible values
Meaning
ASAP
Any specific ASAP of type “System
Timing”, or the default ASAP of type
“System Timing” (“DEFAULT”).
The assigned alarm severity assignment profile (ASAP) of type
“System Timing”.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
7-29
Issue 2, July 2008
See notice on first page
Timing provisioning concepts
Synchronization
characteristics – assigned timing references
...................................................................................................................................................................................................................................
Overview
A timing reference is an external signal to which the internal SDH/SONET equipment
clock is locked.
These signals can be used as timing reference:
•
•
External timing references
One or two external net clock input signals (2048 kHz, 2048 kbps acc. to ITU-T
recommendations, or DS1 SF or ESF acc. to Telcordia Technologies standards)
Line timing references
Up to six reference signals derived from the available incoming SDH/SONET
transport signals.
Active system timing reference
Parameter
Possible values
Meaning
Timing Reference
Identifier
NONE (default setting)
The currently active system timing reference which is used to
derive the system clock in the locked mode of system timing.
EXTREF1
EXTREF2
LINE1 ... LINE6
The value NONE is displayed if no timing reference is assigned, or
if all timing references have failed.
Timing references
The timing references include the line timing references and the external timing
references. The parameters of the line timing references and the external timing
references are explained in the following tables.
Line timing references
The following table shows the possible settings of the line timing references:
Parameter
Possible values
Meaning
Timing Ref.
assigned
Not connected
The respective timing reference source is not used.
Port AID of an SDH/SONET
port
The clock information is derived from the respective SDH/SONET
transport signal.
Sys. Tim. Ref. Prio.
Priority 0 (Disabled) { Priority
8.(default setting)
The configured priority of the respective timing reference signal.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
7-30
Timing provisioning concepts
Synchronization characteristics – assigned timing
references
Parameter
Possible values
Meaning
Quality Provisioned
SDH synchronization mode:
The quality level of the respective timing reference assigned by
provisioning.
PRC
If the provisioned quality level is AUTO, then the incoming SSM
Value is used as the quality level.
SSUT
SSUL
Otherwise, if the provisioned quality level has any value other than
SEC
AUTO, then the incoming SSM Value is not used, but this
AUTO (default setting)
provisioned value is used as the quality level.
SONET synchronization
mode:
PRS
STU
ST2
ST3
AUTO (default setting)
SONET synchronization
mode:
PRS
STU
ST2
ST3
DUS
NONE (default setting)
Timing Output Ref.
Priority
Disabled, 1 (highest priority),
2, 3, ..., 6 (lowest priority)
This parameter is applicable in the SDH synchronization mode
only! It shows the priority assigned to the timing reference signal
for the usage as an output timing reference.
ASAP name
Any specific ASAP of type
“System Timing”, or the
default ASAP of type
“System Timing”
(“DEFAULT”).
The alarm severity assignment profile (ASAP) of type “System
Timing” assigned to the respective timing reference.
Timing Port Mode
Monitoring
Monitored, Not Monitored
This parameter indicates whether the respective timing port will be
monitored for timing reference failures (Monitored) or not
(Not Monitored).
If a timing port is set to Not Monitored, then no timing reference
failure alarms will be reported for that port.
External timing references
The table below shows the possible settings of the external timing references:
Parameter
Possible values
Meaning
Port AID
Not connected
The respective timing reference source is not used.
Port AID of an external timing
input port (exttmg0, exttmg1)
The clock information is derived from the
respective external timing input port.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
7-31
Issue 2, July 2008
See notice on first page
Timing provisioning concepts
Synchronization characteristics – assigned timing
references
Parameter
Possible values
Meaning
Sys. Tim. Ref. Prio.
Disable (default setting)
The configured priority of the respective timing
reference signal.
1 (highest priority), 2, 3,
{ 8 (lowest priority)
Signal Status
Lockout Status
QL Value
Normal
The timing reference signal is fault-free.
Failed
The timing reference signal failed.
Wait-To-Restore
The timing reference signal has failed and is now
being restored. A waiting period is implemented
for a defined time (wait-to-restore time) to see
whether the signal is stable, before the system
switches back to it.
Not-Connected
The timing reference is not used.
Lockout
No Lockout
The Lockout Status determines if the respective
timing reference can be used as a system timing
reference (No Lockout) or not ( Lockout).
SDH synchronization mode:
The quality level of the timing reference port.
PRC
If the provisioned quality level (cf. QL
Provisioned) has any value other than AUTO, then
the quality level is the same as the QL
Provisioned.
SSUT
SSUL
SEC
DNU (default setting)
SONET synchronization mode:
If the provisioned quality level is AUTO, then the
quality level has the same value as the incoming
SSM Value.
PRS
STU
ST2
ST3
DUS (default setting)
Input QL Status
Valid,
Invalid,
Not Supported,
Indicates the validity of the incoming quality
level:
•
Valid
The quality level is a valid Synchronization
Status Message (SSM) and stable.
Not Applicable
•
Invalid
The quality level is not a valid SSM, or
instable.
•
Not Supported
Evaluating the SSM is not supported on the
respective interface due to the chosen format
of the input signal (e.g. in case of a 2-MHz
timing input signal).
•
Not Applicable
No port is assigned to the current timing
reference, or the assigned timing reference
experiences a reference fail.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
7-32
Timing provisioning concepts
Synchronization characteristics – assigned timing
references
Parameter
Possible values
Meaning
QL Provisioned
SDH synchronization mode:
The quality level of the respective timing
reference assigned by provisioning.
PRC
SSUT (default setting)
SSUL
SEC
AUTO
SONET synchronization mode:
If the provisioned quality level is AUTO, then the
incoming SSM Value is used as the quality level.
Otherwise, if the provisioned quality level has any
value other than AUTO, then the incoming SSM
Value is not used, but this provisioned value is
used as the quality level.
PRS
STU
ST2
ST3
AUTO (default setting)
SSM Value
SDH synchronization mode:
PRC
The quality level as received from the external
signal when the signal has a valid Input QL Status
(see above).
SSUT
SSUL
SEC
DNU
UNSTABLE
NONE (default setting)
SONET synchronization mode:
PRS
STU
ST2
ST3
DUS
NONE (default setting)
Output Ref. Priority
Not applicable
This parameter is not applicable to external timing
references!
In the SDH synchronization mode, the value ″Not
applicable″ is displayed on the graphical user
interface. In the SONET synchronization mode,
the Output Ref. Priority is not displayed on the
graphical user interface.
Output Lockout State
Not applicable
This parameter is not applicable to external timing
references!
In the SDH synchronization mode, the value ″Not
applicable″ is displayed on the graphical user
interface. In the SONET synchronization mode,
the Output Lockout State is not displayed on the
graphical user interface.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
7-33
Issue 2, July 2008
See notice on first page
Timing provisioning concepts
Synchronization characteristics – assigned timing
references
Parameter
Possible values
Meaning
ASAP
Any specific ASAP of type
“System Timing”, or the
default ASAP of type “System
Timing” (“DEFAULT”).
The Alarm Severity Assignment Profile (ASAP) of
type “System Timing” assigned to the respective
timing reference.
By means of the Detail button, more detailed
information on the available ASAPs of type
“System Timing” can be retrieved.
Detail
Timing Port Mode
Monitored, Not Monitored
This parameter indicates whether the respective
timing port will be monitored for timing reference
failures (Monitored) or not (Not Monitored).
If a timing port is set to Not Monitored, then no
timing reference failure alarms will be reported for
that port.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
7-34
Timing provisioning concepts
Synchronization
characteristics – system timing
...................................................................................................................................................................................................................................
General system timing parameters
Parameter
Possible value
Meaning
System SSM Mode
QL Enable, QL Disable
This parameter indicates whether the synchronization status
message (SSM) is evaluated for the selection of the timing
reference from which the system timing is derived (QL
Enable) or not ( QL Disable).
In case the System SSM Mode is set to QL Disable, then the
System Quality Level Status is DNU in the SDH
synchronization mode, and STU in the SONET
synchronization mode.
Wait to Restore
SDH synchronization mode:
1 { 60 minutes in steps of
1 minute (default setting:
5 minutes)
SONET synchronization mode:
•
0
•
20 seconds (default setting)
•
1 { 60 minutes in steps of
1 minute
•
Infinite
The wait-to-restore time specifies the time interval that has
to elapse before every single switching from one timing
reference to another is performed.
An “infinite” wait-to-restore time can be used in situations
when enough timing references are available, and you do not
want to use a timing reference again that has failed before.
The respective timing reference can be made available again
only by means of a Clear Wait to Restore command.
Clock
Parameter
Possible value
Meaning
Clock Mode
Free Running (default setting)
The operational mode of the internal timing generator:
Locked
•
Free Running
The free-running mode is selected. The internal timing
generator is not locked to an external timing reference
signal. The system clock is generated by an internal
oscillator.
•
Locked
The locked mode is selected. The internal timing
generator is locked to an external timing reference
signal.
Alarming
Parameter
Possible values
Meaning
ASAP
Any specific ASAP of type “System
Timing”, or the default ASAP of type
“System Timing” (“DEFAULT”).
The assigned alarm severity assignment profile (ASAP) of type
“System Timing”.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
7-35
Issue 2, July 2008
See notice on first page
8
Timing provisioning tasks
8
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter informs about how to perform the most common tasks related to timing
provisioning.
Contents
To retrieve synchronization information
8-2
To set the synchronization - assigned timing reference
8-7
To set the synchronization - external timing input
8-9
To set the synchronization - external timing output
8-11
To set the synchronization - system timing
8-14
To release the synchronization switch (REF)
8-16
To release the synchronization switch (MOD)
8-18
To operate the synchronization switch (MOD)
8-20
To release the synchronization switch (OUTREF)
8-22
To operate the synchronization switch (REF)
8-24
To operate the synchronization switch (OUTREF)
8-26
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
8-1
Issue 2, July 2008
See notice on first page
Timing provisioning tasks
To
retrieve synchronization information
...................................................................................................................................................................................................................................
When to use
Use this task to display the provisioning and operational information of the
synchronization attributes as set by the SET-SYNCN command and after initial system
start-up. It also displays the status of the external timing reference input and output
ports.
Related information
For a more detailed explanation, please refer to the description of the RTRV-SYNCN
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Timing References.
In the Function field, select Retrieve Synchronization.
Click Go.
Result: The Retrieve Synchronization page is displayed.
...................................................................................................................................................................................................
3
This parameter displays the active timing reference, which the system clock is
currently using for locked mode of system timing.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
8-2
Timing provisioning tasks
To retrieve synchronization information
Use the field Identifier to specify the requested information as the following table
shows:
To retrieve information related to{
select{
system timing,
system.
assigned timing references,
exttmg0, exttmg1, or exttmgall.
external timing references,
extref1, extref2, or extrefall.
external timing outputs,
exttmg0_out, exttmg1_out, or
exttmg_outall.
line timing,
line1 to line6, or lineall.
all timing parameters
all.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
...................................................................................................................................................................................................
5
The general output cammand parameter is:
•
aid – access identifier
Shows the category to which the information in the respective output line is related
to.
The output parameters for system timing are:
•
•
•
•
•
•
active_ref – active timing reference status
Displays the active timing reference, which the system clock is currently using for
locked mode of system timing.
clkmod – clock mode
Specifies the provisioned operational mode of the system timing.
clkmod_stat – system clock mode status
Specifies the state of the system clock.
refsw_stat – reference switch status
Is a state of the system timing.
stratum_level – stratum level status
This parameter provides information about the level of the system clock.
syncmsg – system synchronization status messaging mode
This parameter is used to enable or disable the SSM protocol.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
8-3
Issue 2, July 2008
See notice on first page
Timing provisioning tasks
To retrieve synchronization information
•
sysql_stat – system quality level status
Indicates the overall system timing quality level status.
•
timing – ASAP name
Specifies the name of the ASAP (alarm severity assignment profile) that is assigned
to timing.
wtr – wait to restore
Specifies the provisioned wait to restore timer used for all timing ports for
revertive switching. This is the amount of time it takes to switch from lower
priority to higher priority references.
wu_stat – warm up status
This parameter is an attribute of the timing pack hardware design. At initial start up
of the system and at replacing of the active or standby timing function the system
is in warm-up state.
•
•
The output parameters for output timing (instance only valid for SDH) are:
•
•
active_oref_stat – active output timing reference status
Displays the current selected timing reference of the timing link switch for the
external output.
orefswr_stat – output timing reference switch request status
Indicates the output timing reference switch request state.
The output parameters for assigned timing reference are:
•
•
•
•
•
•
extout_pri – timing output reference priority
Specifies the priority assignment of the timing link switch of the external output
timing. This parameter is only for SDH and for line timing references.
inql – assigned timing reference quality value
Displays the input synchronization message for each port of the timing link switch
provisioning of the system timing and of the output timing.
inql_stat – input quality status
Indicates the synchronization messaging quality level status for the specified timing
reference.
ql_prov – quality provisioned
Defines the quality for the specified timing reference to a fixed SSM value. It is
the provisioned quality level sync message value that will be received on timing
references.
ref_lock – timing reference lockout status
Displays the timing reference lockout state to the specified timing reference. It is
the input status for each port of the timing link switch provisioning of the system
timing.
ref_stat – assigned timing reference signal status
Is a status of each timing reference.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
8-4
Timing provisioning tasks
To retrieve synchronization information
•
sclkref_lockstat – station clock output timing reference lockout state
Indicates the assigned station clock output timing reference lockout state. This
parameter is only for SDH and for line timing references.
•
syncref_pri – system timing reference priority
Defines the priority for assigned timing references. When multiple input references
have been given the same priority value, it implies non-revertive switching between
the associated references. Otherwise, it implies revertive switching to the reference
with the highest assigned priority.
tpmode – timing port mode monitoring
Specifies the monitoring status of the timing port.
tpql_in – incoming SSM value of the timing port
Indicates the QL value for the timing port.
tref_aid – timing reference assigned port AID
Specifies the port AID of the assigned timing reference AID.
•
•
•
The output parameters for external timing input are:
•
•
•
ext_if – external input signal format
Specifies the format of the external timing input.
ext_isa – external input sa bit location
Defines the external input Sa bit location.
ext_issm – external input ssm support
Specifies if the SSM mode is supported or not on the external timing input port.
The output parameters for external timing output are:
•
•
•
•
•
•
•
ext_equ – cable equalization
Specifies the timing output cable equalization to adjust the specified timing
reference output signal power. This parameter is valid only for DS1 (SONET).
ext_of – external output signal format
Specifies the external output signal format.
ext_osa – external output sa bit location
Defines the external output Sa bit location.
ext_out_sig_stat – external output signal status
Indicates the external output signal status.
extout_en – external timing output enabling/disabling
Specifies whether the external timing output is enabled or disabled.
extout_prov – external timing output selection
Specifies the operation mode of the external output timing.
extout_ssm – external timing output AIS mode
Specifies which value will be send when the signal level is below the quality
acceptance level or when frcdus is enabled.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
8-5
Issue 2, July 2008
See notice on first page
Timing provisioning tasks
To retrieve synchronization information
•
frcdus – forced DNU/DUS
Specifies the synchronization messaging forced DNU/DUS enable or disable for the
timing output port. DUS applies to SONET and DNU applies to SDH.
•
loopdelay – timing regenerator loop delay
Indicates the delay in the SASE/BITS loop operation. The values are represented
by seconds in steps of 1 seconds per loop.
ql_out – quality of the external timing output port
Indicates the quality value on the signal for the timing output port.
qlout_tais – acceptance quality level for output threshold AIS
Indicates the provisioned quality acceptance level for external timing output.
regen_loop – timing regenerator loop
Specifies the avoiding of loops over the SASE/BITS clocks.
•
•
•
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
8-6
Timing provisioning tasks
To
set the synchronization - assigned timing reference
...................................................................................................................................................................................................................................
When to use
Use this task to set the assign timing references, to modify, or remove them.
Related information
For a more detailed explanation, please refer to the description of the SET-SYNCN
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Timing References.
In the Function field, select Set Synchronization - Assigned Timing Reference.
Click Go.
Result: The Set Synchronization - Assigned Timing Reference page is
displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
•
Timing reference identifier – select either a single access identifier extref1, extref2
or (Line 1 to Line 6) to separate the parameters related to assigned timing
references.
Timing output ref. priority – select either a single parameter Priority 0 (Disabled)
or (Priority 1 to Priority 6) to specify the priority assignment of the timing link
switch of the external output timing.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
8-7
Issue 2, July 2008
See notice on first page
Timing provisioning tasks
•
To set the synchronization - assigned timing reference
Quality provisioned – select a single parameter to define the quality for the
specified timing reference to a fixed SSM value.
•
•
•
•
– SONET: AUTO, PRS, STU, ST2, or ST3.
– SDH: AUTO, PRC, SSUL, SSUT, or SEC.
The “AUTO” value implies sync message support and is rejected if SSM is not
supported for the assigned timing reference.
System timing ref. priority – select either a single parameter
Priority 0 (Disabled) or (Priority 1 to Priority 8) to define the priority for
assigned timing references.
ASAP name – enter an alphanumeric string with 1 to 24 characters to specifies the
name of the “ASAP” (alarm severity assignment profile) that is assigned to timing.
A hyphen is additionally allowed in the name.
Timing port mode monitoring – select either a single parameter Monitored or
Not-Monitored to specify the monitoring status of the timing port.
Timing ref. assigned port AID – enter the timing reference assigned port AID to
specify the port AID of the assigned timing reference AID.
Note: The parameter is rejected, if the timing reference is already assigned to
timing port.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
8-8
Timing provisioning tasks
To
set the synchronization - external timing input
...................................................................................................................................................................................................................................
When to use
Use this task to set the external timing input port attributes, to modify, or to remove
them.
Related information
For a more detailed explanation, please refer to the description of the SET-SYNCN
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Timing References.
In the Function field, select Set Synchronization - External Timing Input.
Click Go.
Result: The Set Synchronization - External Timing Input page is displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
•
External timing identifier – select a single access identifier exttmg0 or exttmg1 to
separate the parameters related to assigned timing references.
External input signal format – select the format of the external timing input:
– SONET: Super Frame or Extended Super Frame.
– SDH: 2 MHz, 2 Mbit-unframed, or 2 Mbit-framed.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
8-9
Issue 2, July 2008
See notice on first page
Timing provisioning tasks
•
To set the synchronization - external timing input
External input sa bit location – select SA4, SA5, SA6, SA7, or SA8 to define the
external input Sa bit location.
•
External input ssm support – select Supported or Not-Supported to specify
whether the SSM mode on the external timing input port is supported or not.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
8-10
Timing provisioning tasks
To
set the synchronization - external timing output
...................................................................................................................................................................................................................................
When to use
Use this task to set the external timing output port attributes, to modify or to remove
them.
Related information
For a more detailed explanation, please refer to the description of the SET-SYNCN
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Timing References.
In the Function field, select Set Synchronization - External Timing Output.
Click Go.
Result: The Set Synchronization - External Timing Output page is displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
•
External timing identifier – select a single access identifier exttmg, exttmg0_out,
or exttmg1_out to separate the parameters related to assigned timing references.
Cable equalization – select 20, 40, 60, 80, or 100 to specify the timing output
cable equalization to adjust the specified timing reference output signal power for
DS1 (SONET) only. The values are represented by percentage (100% = 3.0 dB,
80% = 2.4 dB; 60% = 1.8 dB; 40% = 1.2 dB and 20% = 0.6 dB).
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
8-11
Issue 2, July 2008
See notice on first page
Timing provisioning tasks
•
To set the synchronization - external timing output
External output signal format – select the format of the external output signal
format:
–
–
•
•
•
•
•
•
•
•
•
SONET: Super Frame or Extended Super Frame.
SDH: 2 MHz, 2 Mbit-unframed, or 2 Mbit-framed.
External output sa bit location – select SA4, SA5, SA6, SA7, or SA8 to define the
external output Sa bit location.
External output enabling/disabling – select Enable or Disable to specify whether
the external timing output is active or not.
External timing output selection – select a single parameter to define the
operation mode of the external output timing:
– SONET: Line 1 or Line 2.
– SDH: SETG or TLS.
The value “SETG” means the system clock, the value “TLS” means the output.
External timing output AIS mode – select AISMODE or QLMODE to specify
which value will be send when the signal level is below the quality acceptance
level or when frcdus is enabled.
Forced DNU/DUS – select Enable or Disable to enable or disable the
synchronization messaging forced DNU (SDH)/DUS (SONET) for the timing
output port.
Timing regenerator loop delay – enter a numeric value in the range from 0 to 60
in 1 second steps to indicate the delay in the SASE/BITS loop operation.
Accept qual lvl - out thrs AIS – select the provisioned quality acceptance level for
the external timing output:
– SONET: PRS, STU, ST2, or ST3
– SDH: PRC, SSUL, SSUT, or SEC
Timing regenerator loop – select the avoiding of loops over the SASE/BITS
clocks:
– SONET: Enable or Disable.
– SDH: Disable, extref1, extref2. or both.
ASAP name – enter an alphanumeric string with 1 to 24 characters to specify the
name of the ASAP (alarm severity assignment profile) that is assigned to timing. A
hyphen is additionally allowed in he name.
...................................................................................................................................................................................................
4
Click Submit.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
8-12
Timing provisioning tasks
To set the synchronization - external timing output
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
8-13
Issue 2, July 2008
See notice on first page
Timing provisioning tasks
To
set the synchronization - system timing
...................................................................................................................................................................................................................................
When to use
Use this task to set the system timing clock mode, or to modify or to remove the
related attributes..
Related information
For a more detailed explanation, please refer to the description of the SET-SYNCN
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Timing References.
In the Function field, select Set Synchronization - System Timing.
Click Go.
Result: The Set Synchronization - System Timing page is displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
•
•
System identifier – select the access identifier system to separate the parameters
related to assigned timing references.
Clock mode – select Free Running or Locked to specify the provisioned
operational mode of the system timing.
Sync status messaging mode – select Enable or Disable to enable or disable the
SSM protocol.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
8-14
Timing provisioning tasks
•
•
To set the synchronization - system timing
ASAP name – enter an alphanumeric string with 1 to 24 characters to specifies the
name of the ASAP (alarm severity assignment profile) that is assigned to timing. A
hyphen is additionally allowed in the name.
Wait to restore – specify the provisioned wait to restore timer used for all timing
ports for revertive switching. This is the amount of time it takes to switch from
lower priority to higher priority references.
– SONET: either an alphanumeric value set 0SEC, 20SEC, 99 (infinite), or 0MIN
to 60MIN in 1 minute steps.
– SDH: either an alphanumeric value set 0SEC or 0MIN to 60MIN in 1 minute
steps.
The values “0SEC” and “0MIN” can be used for SONET and SDH to provision a
zero wait to restore time.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
8-15
Issue 2, July 2008
See notice on first page
Timing provisioning tasks
To
release the synchronization switch (REF)
...................................................................................................................................................................................................................................
When to use
Use this task to release (clear) timing reference switching.
Related information
For a more detailed explanation, please refer to the description of the
RLS-SYNCNSW-REF command in the LambdaUnite ® MSS Operations System
Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Timing References.
In the Function field, select Release Synchronization Switch REF.
Click Go.
Result: The Release Synchronization Switch REF page is displayed.
...................................................................................................................................................................................................
3
In the field Destination, select the timing reference to which the command relates
(extref1, extref2 or line1 to line6).
...................................................................................................................................................................................................
4
Click Submit.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
8-16
Timing provisioning tasks
To release the synchronization switch (REF)
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
8-17
Issue 2, July 2008
See notice on first page
Timing provisioning tasks
To
release the synchronization switch (MOD)
...................................................................................................................................................................................................................................
When to use
Use this task to release (clear) the forced request on the timing mode so that it will
return to the provisioned locked mode from the holdover mode.
Related information
For a more detailed explanation, please refer to the description of the
RLS-SYNCNSW-MOD command in the LambdaUnite ® MSS Operations System
Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Timing References.
In the Function field, select Release Synchronization Switch MOD.
Click Go.
Result: The Release Synchronization Switch MOD page is displayed.
...................................................................................................................................................................................................
3
Click Submit.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
8-18
Timing provisioning tasks
To release the synchronization switch (MOD)
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
8-19
Issue 2, July 2008
See notice on first page
Timing provisioning tasks
To
operate the synchronization switch (MOD)
...................................................................................................................................................................................................................................
When to use
Use this task to request a change from the provisioned synchronization mode to forced
holdover state.
Related information
For a more detailed explanation, please refer to the description of the
OPR-SYNCNSW-MOD command in the LambdaUnite ® MSS Operations System
Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Timing References.
In the Function field, select Operate Synchronization Switch MOD.
Click Go.
Result: The Operate Synchronization Switch MOD page is displayed.
...................................................................................................................................................................................................
3
In the field Switch command, select Forced Switch to force system timing from the
locked mode to the holdover mode (clock backup request).
...................................................................................................................................................................................................
4
Click Submit.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
8-20
Timing provisioning tasks
To operate the synchronization switch (MOD)
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
8-21
Issue 2, July 2008
See notice on first page
Timing provisioning tasks
To
release the synchronization switch (OUTREF)
...................................................................................................................................................................................................................................
When to use
Use this task to release (clear) external output timing switch (for SDH only).
Related information
For a more detailed explanation, please refer to the description of the
RLS-SYNCNSW-OUTREF command in the LambdaUnite ® MSS Operations System
Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Timing References.
In the Function field, select Release Synchronization Switch OUTREF.
Click Go.
Result: The Release Synchronization Switch OUTREF page is displayed.
...................................................................................................................................................................................................
3
In the field Destination, select the timing reference to which the command relates
(line1 to line6).
...................................................................................................................................................................................................
4
Click Submit.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
8-22
Timing provisioning tasks
To release the synchronization switch (OUTREF)
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
8-23
Issue 2, July 2008
See notice on first page
Timing provisioning tasks
To
operate the synchronization switch (REF)
...................................................................................................................................................................................................................................
When to use
Use this task to request the NE to operate manual or forced synchronization reference
protection switch or to lockout synchronization reference.
Related information
For a more detailed explanation, please refer to the description of the
OPR-SYNCNSW-REF command in the LambdaUnite ® MSS Operations System
Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Timing References.
In the Function field, select Operate Synchronization Switch REF.
Click Go.
Result: The Operate Synchronization Switch REF page is displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
Switch command – specify the desired switching function:
–
–
Lock out timing reference – the reference which is addressed by the
“Destination” parameter, will be locked out by the user and cannot be used as a
timing reference signal until the lockout is cleared.
Forced switch – to force selection of the external timing output determined by
the “Destination” parameter.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
8-24
Timing provisioning tasks
–
To operate the synchronization switch (REF)
Manual switch – a manual selection of the external timing output determined by
the “Destination” parameter.
–
•
Clear wait-to-restore period – the reference which is addressed by the
“Destination” parameter will be terminated. The signal status will return to
normal.
Destination – select the timing reference to which the command relates extref1,
extref2, or (line1 to line6).
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
8-25
Issue 2, July 2008
See notice on first page
Timing provisioning tasks
To
operate the synchronization switch (OUTREF)
...................................................................................................................................................................................................................................
When to use
Use this task to request the NE to operate manual or forced synchronization reference
protection switch or external timing output protection switch (for SDH only), to
lockout synchronization reference, or external output timing (for SDH only) switching.
Related information
For a more detailed explanation, please refer to the description of the
OPR-SYNCNSW-OUTREF command in the LambdaUnite ® MSS Operations System
Engineering Guide.
Procedure
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Timing References.
In the Function field, select Operate Synchronization Switch OUTREF.
Click Go.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
8-26
Timing provisioning tasks
To operate the synchronization switch (OUTREF)
Result: The Operate Synchronization Switch OUTREF page is displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
Switch command – specify the desired switching function:
–
•
Lock out timing reference – the reference which is addressed by the
“Destination” parameter, will be locked out by the user and cannot be used for
external timing output until the lockout is cleared.
– Forced switch – to force selection of the external timing output determined by
the “Destination” parameter.
– Manual switch – a manual selection of the external timing output determined by
the “Destination” parameter.
Destination – select the timing reference to which the command relates (line1 to
line6).
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
8-27
Issue 2, July 2008
See notice on first page
9
Traffic provisioning concepts
9
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter presents concept information related to traffic provisioning on
LambdaUnite ® MSS network elements using Lucent OMS.
Contents
SDH/SONET traffic provisioning concepts
9-2
Cross-connections
9-2
Lower-order cross-connections (LOXC)
9-8
Path protection (SNCP/UPSR)
9-11
Line protection (MSP/APS)
9-13
Ring protection (MS-SPRing/BLSR)
9-15
Dual node interworking / Dual ring interworking (DNI/RNI)
9-20
Ethernet traffic provisioning concepts
9-21
TransLAN ® Ethernet over SDH implementation
9-21
Virtual concatenation
9-23
Virtual LAN
9-25
Tagging schemes
9-27
Spanning tree protocol
9-28
Link path through
9-30
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
9-1
Issue 2, July 2008
See notice on first page
Traffic provisioning concepts
SDH/SONET traffic provisioning concepts
Cross-connections
...................................................................................................................................................................................................................................
Cross-connection shapes
The supported cross-connection shapes (as shown in the graphical display of a
cross-connection) are listed in the following table:
Cross-connection
shape
Diagram
Management system
symbol
Simple (uni), a
unidirectional
point-to-point
connection
from port ID 1
to port ID 1
source
destination
Simple (bi), a
bidirectional
point-to-point
connection
from port ID 1
to port ID 1
source
destination
Add-drop A (uni), part
of a unidirectional path
protection scheme
from port ID 1
W
to port ID 1
from port ID 2
Add-drop Z (uni), part
of a unidirectional path
protection scheme
Add-drop (bi), part of a
bidirectional path
protection scheme
P
from port ID 1
path 1
to port ID 1
path 2
to port ID 2
from port ID 1
path 1
from port ID 2
W
P
path 2
add/drop
to port ID 1
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
9-2
Traffic provisioning concepts
Cross-connection
shape
Double add-drop (bi),
part of a bidirectional
path protection scheme
Cross-connections
Diagram
Management system
symbol
PPG 2 output
adjunct PPG 2 output
Ring 1
from port ID 1
W
from port ID 2
P
Path
protection
group 1
Path
protection
group 2
W
P
to port ID 1
to port ID 2
Ring 2
PPG 1 output
adjunct PPG 1 output
Interconnect-W (bi)
from port ID 1
to/from
terminating node
from port ID 2
W
P
to/from other
interconnecting node
to/from other ring
to port ID 1
Interconnect-P (bi)
from port ID 1
to/from
terminating node
from port ID 2
W
P
to/from other
interconnecting node
to/from other ring
to port ID 1
Interfaces and ports
The LambdaUnite ® MSS add/drop multiplexer in its basic configuration is a single
shelf that interfaces electrical STM-1 and optical STM-1/OC-3, STM-4/OC-12,
STM-16/OC-48, STM-64/OC-192, and STM-256/OC-768 lines to an
SDH/SONET-standard MS-SPRing/BLSR protected ring. It has 32 universal slots that
support flexible electrical and optical port unit mixing.
Definitions
Port A physical transmission interface, consisting of both an input and an output,
which may be used to carry traffic between network elements. Operational
differences between ports determined by port provisioning include pointer
processing, fault and performance monitoring, path maintenance (for example
unequipped, AIS, RDI), cross-connections (supported rates), and protection
switching.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
9-3
Issue 2, July 2008
See notice on first page
Traffic provisioning concepts
Cross-connections
Port protection group A user-provisioned association of optical interface ports which
is used for protection in a particular type of network configuration. The following
types of port protection groups are defined:
•
•
•
•
•
•
•
•
4-fiber MS-SPRing port protection group used for STM-64 and STM-16 1+1
MS-SPRing
4-fiber MS-SPRing port protection group used for STM-64 and STM-16 1+1
MS-SPRing transoceanic protocol
2-fiber MS-SPRing port protection group used for STM-256, STM-64, and STM-16
1+1 MS-SPRing
1+1 MSP port protection group used for STM-64, STM-16, STM-4, and STM-1
1+1 MSP
1:1 MSP port protection group used for STM-64, STM-16, STM-4 and STM-1 1:1
MSP
2-fiber BLSR port protection group used for OC-768, OC-192, and OC-48 1+1
BLSR
4-fiber BLSR port protection group used for OC-192 and OC-48 1+1 BLSR
1+1 APS port protection group used for OC-192, OC-48, OC-12, and OC-3 1+1
APS
The operations on a port protection group include the provisioning, control, and status
of the protection switching.
Tributary A path-level unit of bandwidth within a port, or the signal(s) being carried
in this unit of bandwidth, e.g. a VC-3/STS-1 or VC-4/STS-3 within an
STM-N/OC-M port.
Cross-connection A configurable SDH/SONET path-level interconnection within a
network element between input and output tributaries of specific ports.
Cross-connection leg A one-way connection provisioned from one input tributary to
one output tributary. Each leg is identified as an entity by its input and output
tributaries, its cross-connection rate, and the type of cross-connection it is part of.
A leg pair is a pair of cross-connection legs which are reported as a two-way
connection between two tributaries.
Transmission interfaces
LambdaUnite ® MSS includes the following electrical and optical port units:
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
9-4
Traffic provisioning concepts
Cross-connections
Interface type
Transmission rate
Wavelength
Optical
STM-256/OC-768
1.5 µm (long reach)
1.3 µm (intra office)
LambdaXtreme ® Transport
compatible (64 colors)
STM-64/OC-192
1.5 µm (long reach)
1.5 µm (intermediate reach)
1.3 µm (intra office)
LambdaXtreme ® Transport
compatible (128 colors)
OLS 1.6T compatible (80 colors)
passive WDM compatible (16 colors)
IEEE802.ae 1000GBASE-EW WAN
PHY interworking
STM-16/OC-48
1.5 µm (long reach)
1.3 µm (long reach)
1.3 µm (short reach / intra office)
passive WDM compatible (32 colors)
Electrical
STM-4/OC-12
1.3 µm (intermediate reach)
STM-1/OC-3
1.3 µm (intermediate reach)
GE1/SX4, 1 GbEthernet
1000BASE-SX
GE10PL1, 1 Gb Ethernet, 10 Gb
Ethernet
1000BASE-SX
STM-1
intra office electrical interface
Each unit contains eight independent
unidirectional ports.
Switch capacity
The total full non-blocking switch capacity is 320 Gbps (6144 STS-1/2048 VC-4s).
The total full non-blocking lower order switch capacity is 40 Gbps (for example,
16.128 bidirectional or 32.256 unidirectional cross-connected VT1.5 signals).
Additionally also overhead information from SDH/SONET I/O ports may be
transparently switched. The switch is based on a bit sliced architecture providing this
very high capacity on a single pack.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
9-5
Issue 2, July 2008
See notice on first page
Traffic provisioning concepts
Cross-connections
Cross-connection levels
The following cross-connection levels are supported in LambdaUnite ® MSS:
•
•
•
•
•
•
•
•
•
•
VC-3
VC-4
VC-4-4c (concatenated VC-4)
VC-4-16c (concatenated VC-4)
VC-4-64c (concatenated VC-4)
STS-1
STS-3
STS-12
STS-48
STS-192
The following cross-connection levels are supported in the LOXC application of the
LambdaUnite ® MSS:
•
•
•
LOVT1 (SONET)
LOVC3 (SDH)
LOVC12 (SDH).
Cross-connection types supported by the LOXC application
The LOXC application supports the following cross-connection types
•
•
•
1WAY:
Unprotected unidirectional cross-connection
2WAY:
Unprotected bidirectional cross-connection
1WAYPROT:
Protected unidirectional cross-connection
Output mode
The cross-connection output mode is a provisionable parameter
•
•
for the destination-to-source direction, and/or
for the source-to-destination direction.
If some of the facilities are not in place whenever the cross-connection is being
established, then you can provision this field as terminated-AIS or terminated-IDLE
(DS3) / unequipped (SDH/SONET) and a terminated-AIS or terminated-IDLE (DS3) /
unequipped (SONET) signal will be inserted to function as a keep-alive signal.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
9-6
Traffic provisioning concepts
Cross-connections
If all of the involved facilities are in place when the cross-connection is established,
the field should be provisioned as NORMAL. The end-to-end signal path is then
established and the signal can be passed.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
9-7
Issue 2, July 2008
See notice on first page
Traffic provisioning concepts
Lower-order
cross-connections (LOXC)
...................................................................................................................................................................................................................................
Overview
This section gives an overview about the features related to lower-order
cross-connections (LOXC).
Signal rates
The main purpose of the LOXC function is to cross-connect lower-order tributaries on
the following levels:
•
•
•
VT1.5 (SONET),
VC-12 (SDH),
(LO) VC-3 (SDH).
For this purpose, substructured higher-order signals need to be terminated before the
embedded lower-order signals can be cross-connected.
Supported signals with lower-order substructure are:
•
•
STS-1 (SONET) carrying VT1.5 signals,
VC-4 (SDH) carrying LO VC-3 or VC-12 signals (or a mix of it).
Any type of concatenated signal is not supported (despite VC-4 could be interpreted as
STS-3C).
Connectivity types
The LOXC function supports following types of cross-connections:
•
•
•
uni-/bidirectional unprotected cross-connections
1:2 broadcasting
AU3/AU4 conversion (only hardware prepared).
Configuration specifications
The following figure shows an example for the switching of lower-order
cross-connections between an STM-16 unit and an STM-4 unit (switching on
lower-order VC-3 level) and an STM-1 unit (switching on VC-12 level).
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
9-8
Traffic provisioning concepts
Lower-order cross-connections (LOXC)
LOXC unit
1
STM-16 unit
STM-4 unit
m+1
VC-4
1
VC-4
1
/2/
LO-XC
(VC-3)
7
/1/
HO-XC
(VC-4)
VC-4 sink
HO-XC
(VC-4)
4
VC-4 source
LO-XC
(VC-12)
STM-1 unit
/3/
16
m
n
(96)
HO-XC
(VC-4)
1
HO cross-connection on VC-4 level via (HO) XC-pack
VC-12 timeslot
(LO-)VC-3 timeslot
Restrictions
For configuring a lower-order cross-connection the following rules have to be
considered:
•
•
•
•
For LOXC/1 a switch capacity of max. 96 VC-4 equivalents is available which
corresponds to 15G.
For LOXC40G2S/1 a switch capacity of max. 768 × 768 VC-3 (lower-order),
16128 × 16128 VC-12, or 21504 × 21504 VT1.5 equivalents is available which
corresponds to 40 G.
To activate the lower-order cross-connect unit (LOXC), depending on the type of
LOXC used, the switching capacity of the respective circuit pack has to be set to
– 15 Gbps, in the case of an LOXC/1,
– 40 Gbps, in the case of an LOXC40G2S/1.
The System Interface Standard Default of all ports to be used for a lower-order
cross-connection must be set to same value, either SDH or SONET.
Lower-order VC access for MS-SPRing
The system supports the provisioning of cross-connections on LO-VC level from, to,
and between MS-SPRing ports. It is also supported to enter source and destination
node information for that HO-VC the cross-connected LO-VC is part of.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
9-9
Issue 2, July 2008
See notice on first page
Traffic provisioning concepts
Lower-order cross-connections (LOXC)
Important! This feature does not ask for HO-VC unsquelching (node type 2) or
LO-VC squelching (node type 3) as this is not standardized for SDH.
Important! The same provisioning (LO-CCs from, to, and between MS SPRING
ports) has to be rejected for SONET BLSR ports
Important! This feature does not include input legs of LO path protected
cross-connections from MS-SPRing ports.
Mapping schemes
For LambdaUnite ® MSS the following mappings are supported:
•
•
SDH:
VC-12 and VC-3 – this means according to the SDH multiplex scheme:
– VC-12 → TU-12 (3×) → TUG-2 (7×) → TUG-3 (3×) → VC-4 → AU-4
– VC-3 → TU-3 → TUG-3 (3×) → VC-4 → AU-4
SONET:
VT1.5 – this means according to the SONET multiplex scheme:
– VT1.5 (4×) → VT group → STS-1
– SDH: 33 // 6312 // 4212-13 // 2112-13-2112 // 13-4212 // 23-2112 // / 2112-23
– SONET: 281122
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
9-10
Traffic provisioning concepts
Path
protection (SNCP/UPSR)
...................................................................................................................................................................................................................................
Principles
The principle of a path protection is based on the duplication of the signals to be
transmitted and the selection of the best signal available at the path connection
termination. The two (identical) signals are routed over two different path segments,
one of which is defined as the main path and the other as standby path. The same
applies to the opposite direction. The system only switches to the standby path if the
main path is faulty.
The object associated to a path-protected cross-connection topology that is provisioned
to provide path-level protection switching for all the constituent signals carried by the
cross-connection is called path protection group. A path protection group consists of
one or more constituent path selectors. LO path protection groups always consist of
only one constituent path selector.
LambdaUnite ® MSS supports both, SONET and SDH path protection features:
•
•
SDH: subnetwork connection protection (SNCP)
SONET: unidirectional path-switched ring (UPSR)
SNCP
SNCP is providing path-level protection for individual VC-N circuits that are routed
independently across any network (meshed, rings or mixed). It may be applied at any
path layer in a layered network. It can be used to protect a portion of a path between
two connection points (CPs) or between a CP and a termination connection point
(TCP), or the full end-to-end path between two TCPs.
SCNP is a dedicated 1+1 protection architecture in which the traffic is permanently
bridged onto two SNCs at the transmit end, carried through any number of facilities of
any type, and selected from one of the two SNCs at the receive end. One SNC is
called the working SNC and the other, the protection SNC.
LambdaUnite ® MSS supports two types of SNCP:
•
Inherently monitored subnetwork connection protection (SNC/I)
SNC/I protection, general, protects against failures in the server layer. The
protection process and the defect detection process are performed by two adjacent
layers. The server layer performs the defect detection process, and forwards the
status to the client layer by means of the server signal fail (SSF) signal. This means
AU-4 or STS-1 defects are defects and the switch is triggered by the SSF signal.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
9-11
Issue 2, July 2008
See notice on first page
Traffic provisioning concepts
Path protection (SNCP/UPSR)
The LOXC application supports SNC/I for the following cross connection types:
–
•
VC-12
– (LO) VC-3
Non-intrusively monitored subnetwork connection protection (SNC/N)
SNC/N protection, generally, protects against failures in the server layer and
against failures and degradation in the client layer. This means the non-intrusive
monitor function on the received side detects signal fail (SF) and signal degrade
(SD) events on the incoming signal and triggers the switch.
The LOXC application supports SNC/N for the following cross connection types:
– VC-12 (SDH)
– (LO) VC-3
UPSR
UPSR is typically a SONET ring architecture. It provides path-level protection for
STS-N circuits within in physical ring network. The ring is usually comprised of
unprotected lines at the same OC-N rate which are connected in a ring topology.
Typically all (or most) of the circuits within the ring are path-protected. The UPSR
provides redundant bandwidth to protect services against node failures or other failures
conditions. UPSR operates by bridging an identical STS-N path signal in both
directions around the ring, and then selecting the better of the two signals to drop from
the ring, based on a signal quality hierarchy. As for SNCP, the path selection is based
on purely local information, for example on path layer indications including path layer
defects and maintenance signals.
LambdaUnite ® MSS supports UPSR protection, also within logical ring applications.
UPSR on lower order tributaries are supported for VT1.5 connections.
A logical ring is formed by bridging the incoming signal at a source node, diversely
routing the two paths through a SONET network, and selecting the “better” of the two
diversely routed paths at the destination node. The paths may traverse over any type of
physical linear, mesh, or ring network.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
9-12
Traffic provisioning concepts
Line
protection (MSP/APS)
...................................................................................................................................................................................................................................
Principles
In line protection switching, the complete (physical) transmission path between two
multiplexers is duplicated. This means that a separate optical interface unit is
connected in each multiplexer for the main (working) and standby (protection) section.
LambdaUnite ® MSS supports both, SONET and SDH line protection features.
•
•
SDH: 1+1 multiplex section protection (MSP) on STM-64, STM-16, STM-4 and
STM-1 interfaces
SONET: 1+1 linear automatic protection switch (APS) on OC-192, OC-48, OC-12
and OC-3 interfaces
1+1 MSP/APS functional description
In case of a 1+1 MSP/APS each main line is assigned to one standby line. As for other
types of protection switching the signals are duplicated in the transmit direction. In the
receive direction, this type of switching either selects, depending on the signal quality,
the input signals of the main section or that of the standby section for transmission.
The network elements are equipped with an MSP function which carries out the
selection and changeover processes. The switching activities are monitored by the
K1-K2 byte. This takes place in the receive direction on the circuit pack, which is
connected to the standby section.
The following figure illustrates the schematic diagram of a 1+1 line protection:
Working line
Protection line
Network Element
Mode of operation
In the LambdaUnite ® MSS systems the 1+1 MSP/APS operate unidirectional or
bidirectional in non-revertive or revertive mode.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
9-13
Issue 2, July 2008
See notice on first page
Traffic provisioning concepts
Line protection (MSP/APS)
1:1 MSP protection functional description
For STM-64, STM-16, STM-4, and STM-1 optical ports, a 1:1 MSP protection is
possible. In a 1:1 MSP configuration low-priority traffic can be transmitted via the
protection port as long as no protection switch occurs. If the traffic of the working
section has to be switched to the protection section, the low-priority traffic is lost (1:1
MSP with preemptible protection access). The K1 and K2 bytes of the SOH within the
protection section define the automatic protection switch (APS) protocol as defined in
ITU-T G.841.
The MSP 1:1 protection is very similar to the MSP 1+1 protection. The difference is
that MSP 1:1 supports extra traffic on the protection port. The protection group will
retrieve the tributary data from the tributaries of the working port and forward it to the
protection port.
Mode of operation
In the LambdaUnite ® MSS system, the 1:1 MSP is working in revertive mode. It can
be established as bidirectional protection.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
9-14
Traffic provisioning concepts
Ring
protection (MS-SPRing/BLSR)
...................................................................................................................................................................................................................................
Principles
A ring protection is a self-healing ring configuration in which traffic is bidirectional
between each pair of adjacent nodes and is protected by redundant bandwidth on the
bidirectional lines that interconnect the nodes in the ring. Because traffic flow is
bidirectional between nodes, traffic can be added at one node and dropped at the next
without traveling around the entire ring. This leaves the spans between other nodes
available for additional traffic. Therefore, with many traffic patterns a bidirectional ring
can carry much more traffic than the same facilities could carry if configured for a
unidirectional ring.
LambdaUnite ® MSS supports both, SONET and SDH ring protection features.
•
•
SDH: multiplex section shared protection ring (MS-SPRing)
SONET: bidirectional line switched ring (BLSR)
Transoceanic protocol (TOP)
LambdaUnite ® MSSsupports 4-fiber MS-SPRing transoceanic protocol protection
schemes on the 40-Gbps and the 10-Gbps interfaces. The protection scheme complies
with ITU-T Rec. G.841.
This section defines the support of undersea cable applications in an SDH network
using a 4-fiber MS-SPRring configuration. These applications frequently encounter
distances between nodes that are greater than the overall circumference designed for
the MS-SPRing (that is > 1200 km). This application is the transoceanic protocol
without extra traffic (TOP-WO) and the transoceanic protocol with restoration of extra
traffic (TOP+EX). Extra traffic is allowed during normal conditions and is preempted
when a protection switch is requested. The TOP+EX preempts the extra traffic initially,
but re-establishes extra traffic assigned to protection bandwidth that is not required for
restoration of the failed services. The extra traffic is re-established as part of the
protection switching processing.
MS-SPRing protection schemes
The following MS-SPRing protection schemes can be configured:
•
•
•
2-fiber MS-SPRing on STM-256, STM-64, and STM-16 interfaces
4-fiber MS-SPRing on STM-64 and on STM-16 interfaces
4-fiber MS-SPRing with transoceanic protocol on STM-64 and on STM-16
interfaces
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
9-15
Issue 2, July 2008
See notice on first page
Traffic provisioning concepts
Ring protection (MS-SPRing/BLSR)
The protection scheme complies with ITU-T Rec. G.841 and provides in a future
release also “extra traffic” on STM-64 and STM-16 interfaces in the MS-SPRing
configuration. 4-fiber MS-SPRing for the STM-256 interfaces will be supported in
future.
Configuration rules
A 4-fiber MS-SPRing group can only be provisioned successfully, if there is no line
timing reference assigned to the protection port of the spans of the MS-SPRing group
(east protection port or west protection port).
In a 2-fiber or 4-fiber MS-SPRing the total number of nodes may not exceed 16, not
more than one node is allowed per each NE in the same ring.
BLSR protection schemes
The following BLSR protection schemes can be configured:
•
•
2-fiber BLSR on OC-768, OC-192 and on OC-48 interfaces
4-fiber BLSR on OC-192 and on OC-48 interfaces
The protection scheme complies with the ANSI T1.105.01 Standard and provides in a
future release also preemptible protection access (PPA). 4-fiber BLSR for the OC-768
and on the OC-48 interfaces will be supported in future.
Configuration rules
A 4-fiber BLSR group can only be provisioned successfully, if there is no line timing
reference assigned to the protection port of the spans of the BLSR group (east
protection port or west protection port).
In a 2-fiber or 4-fiber BLSR the total number of nodes may not exceed 16, not more
than one node is allowed per each NE in the same ring.
Traffic disposition
The following figure shows working and protection traffic disposition in a
LambdaUnite ® MSS 2-fiber MS-SPRing/BLSR.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
9-16
Traffic provisioning concepts
Ring protection (MS-SPRing/BLSR)
NE
Self-healing rings
LambdaUnite ® MSS MS-SPRings/BLSRs are self healing, that means transport is
automatically restored after node or fiber failures.
In case of a 2-fiber 10Gbps MS-SPRing/BLSR, each line carries 32 VC-4/STS-3c
equivalent time slots of working capacity plus 32 VC-4/STS-3c equivalent time slots of
protection capacity. For 2-fiber 2.5 Gbps MS-SPRing/BLSR, the working and
protection capacity is eight VC-4/STS-3c equivalents time slots.
In the event of a fiber or node failure, service is restored by switching traffic from the
working capacity of the failed line to the protection capacity in the opposite direction
around the ring.
Traffic flow example
The following figure shows normal (non-protection-switched) traffic flow in a
LambdaUnite ® MSS 2-fiber MS-SPRing/BLSR.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
9-17
Issue 2, July 2008
See notice on first page
Traffic provisioning concepts
Ring protection (MS-SPRing/BLSR)
NE
Protection switching
When a line-level event triggers a protection switch, the affected nodes switch traffic
on to protection capacity and transport it to its destination by looping it back the other
way around the ring. Service is reestablished on the protection capacity in less than
50 ms after detection of the failure (for signal fail conditions in rings without existing
protection switches or extra traffic).
Fiber cut example
The following figure illustrates a 2-fiber MS-SPRing/BLSR protection switch that
results from a fiber cut:
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
9-18
Traffic provisioning concepts
Ring protection (MS-SPRing/BLSR)
NE
Protection traffic flow
In the previous example, traffic going from node A to node C that normally passed
through node E and node D on “working 2” capacity, is switched onto the “protection
2” capacity of the line leaving node E in the opposite direction. The traffic loops back
around the ring via node B, C, and D (where the loopback switch is active) to node C.
Similarly, traffic going from node C to node A that normally passed through node D
and node E on “working 1” capacity is switched on to the “protection 1” capacity of
the line leaving node D in the opposite direction.
The same approach is used for a node failure. For example, if node D were to fail,
nodes C and E would perform loopback protection switches to provide an alternate
route for ring traffic.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
9-19
Issue 2, July 2008
See notice on first page
Traffic provisioning concepts
Dual
node interworking / Dual ring interworking (DNI/RNI)
...................................................................................................................................................................................................................................
Overview
Dual node interworking (DNI) and dual ring interworking (DRI) are configurations that
provide path-level protection for selected STM-N or OC-M circuits that are being
carried through two rings. Protection for the route between the two rings is provided
by interconnecting the rings at two places.
Each circuit that is provisioned with DNI/DRI protection is dual-homed, meaning it is
duplicated and subsequently terminated at two different nodes on a ring. The two
interconnecting nodes in each ring do not need to be adjacent.
The self-healing mechanisms of the two rings remain independent and together protect
against simultaneous single failures on both rings (not affecting the interconnections).
The DNI/DRI configuration additionally protects against failures in either of the
interconnections between the rings, whether the failure is in a facility or an
interconnection node.
DNI/DRI is a network topology whereby two rings are interconnected at two nodes on
each ring. It provides a high degree of survivability of the traffic crossing from one
ring to the other.
Drop and continue
Drop and continue is a method used in one ring for interconnecting with another ring.
One of the interconnecting nodes dual feeds the traffic both toward the other ring and
toward the other interconnecting node within the same ring, so that the same traffic is
transmitted to the other ring at two different nodes. The implementation of the drop
and continue method depends on the type of the ring. It is different in a
BLSR/MS-SPRing and in a UPSR/SNCP ring.
The DRI functionality is compliant with ANSI T1.105.01 and Telcordia
GR-1230-CORE and GR-1400-CORE standards. The DNI functionality is also
compliant with ITU-T G.842 standard.
DNI/DRI SNCP or UPSR
LambdaUnite ® MSS supports DNI/DRI between two SNCP or UPSR protected rings.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
9-20
Traffic provisioning concepts
Ethernet traffic provisioning concepts
® Ethernet over SDH implementation
TransLAN
...................................................................................................................................................................................................................................
Overview
This section describes in brief some related features of LambdaUnite ® MSS:
•
•
•
•
•
•
•
•
•
•
•
Virtual concatenation
Link Capacity Adjustment Scheme (LCAS)
Virtual LAN
Repeater mode
VLAN tagging
Multipoint mode
VLAN trunking
Spanning Tree Protocol (STP)
Rapid spanning tree protocol (rSTP)
Generic VLAN Registration Protocol
Link path through (LPT)
In addition, it is highly recommended to consult the TransLAN ® Ethernet SDH
Transport Solution Applications and Planning Guide, 365-377-002 (109608364) when
planning to use LambdaUnite ® MSS for Ethernet applications.
TransLAN ® principles
TransLAN ® is the collective term for the Ethernet SDH Transport Solution which
includes the transport of Ethernet (up to 10 Mbps), Fast Ethernet (100 Mbps), and
Gigabit Ethernet (1 Gbps) payload data over an SDH network.
The TransLAN ® Ethernet cards allow direct interconnection of data equipment over an
SDH transport network. The external data equipment could be an Ethernet switch, an
IP router, or a host system such as a user PC or a web server.
The TransLAN ® implementations all use standardized protocols to transport Ethernet
frames over the SDH network. First, the generic framing procedure (GFP) or the
proprietary Ethernet over SDH (EoS) method, a pre-standard GFP on several first
generation TransLAN ® card types, is used to encapsulate the Ethernet frames into the
SDH transmission payload. Secondly, virtual concatenation and LCAS are used to
allocate a flexible amount of WAN bandwidth for the transport of Ethernet frames.
TransLAN ® supports IEEE 802.3 Ethernet frames as well as “Ethernet II” frames
(“DIX frames”).
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
9-21
Issue 2, July 2008
See notice on first page
Traffic provisioning concepts
TransLAN ® Ethernet over SDH implementation
Although optimized for IP, TransLAN ® is an Ethernet transport technology. It is
transparent to all layer 3 protocols (IP, IPX, DECnet, etc.).
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
9-22
Traffic provisioning concepts
Virtual
concatenation
...................................................................................................................................................................................................................................
Principles
The GE1 interface supported by LambdaUnite ® MSS allows you to transport Gigabit
Ethernet (GbE) signals over SONET/SDH networks by encapsulating Ethernet packets
in virtually concatenated Synchronous Payload Envelopes (SPEs, SONET) or Virtual
Containers (VCs, SDH).
The following figure shows the principle of virtual concatenation in a point-to-point
Gigabit Ethernet (GbE) application example. Protection of the STS-1-Kv/VC-4-Kv
traffic is possible via UPSR/SNCP, via 1+1 line APS / 1+1 MSP and in ring topologies
via BLSR/MS-SPRing protection schemes.
Network element
Ethernet
frame
LAN
VC-4-7v
WAN
Network element
Ethernet
VC-4-7v frame
WAN
LAN
The H4 POH byte is used for the sequence and multi-frame indication specific for
virtual concatenation.
Due to different propagation delay of the virtual containers a differential delay will
occur between the individual virtual containers. This differential delay has to be
compensated and the individual virtual containers have to be re-aligned for access to
the contiguous payload area. The LambdaUnite ® MSS re-alignment process covers at
least a differential delay of 32 ms.
Link Capacity Adjustment Scheme
Link Capacity Adjustment Scheme (LCAS) is an extension to virtual concatenation that
allows dynamic changes in the number of STS-1/VC-4 channels per connection. In
case channels are added or removed by management actions this will happen without
loosing any customer traffic. LCAS allows a bandwidth service with scalable
throughput in normal operation mode. In case of failure the connection will not be
dropped completely only the affected STS-1s/VC-4s. The remaining channels will
continue carrying the customer traffic. The implemented LCAS provides automatic
decrease of bandwidth in case of link failure and reestablishment after link recovery.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
9-23
Issue 2, July 2008
See notice on first page
Traffic provisioning concepts
Virtual concatenation
The following unidirectional and bidirectional virtual concatenations are supported:
•
•
STS-1-Kv, where K = 1 up to 21 in steps of 1
VC-4-Kv, where K = 1 up to 7 in steps of 1.
The GE1 circuit pack allows to transport Gigabit Ethernet signals efficiently over
SONET or SDH networks by encapsulating Ethernet packets in virtually concatenated
VC-4 or STS-1s, using the LCAS. This protection-by-load-sharing feature allows for
efficient use of protection bandwidth, that can be added/removed hitlessly for Ethernet
applications.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
9-24
Traffic provisioning concepts
Virtual
LAN
...................................................................................................................................................................................................................................
Principles
Virtual Local Area Networks (VLANs) can be used to establish broadcast domains
within the network as routers do, but they cannot forward traffic from one VLAN to
another. Routing is still required for inter-VLAN traffic. Optimal VLAN deployment is
predicated on keeping as much traffic from traversing the router as possible.
VLAN supports the following advantages:
•
•
•
•
Easy provisioning of VLANs
Consistency of the VLAN membership information across the network
Optimization of VLAN broadcast domains in order to save bandwidth
Isolated service for different customers.
The operator configures VLANs on LAN ports, and GVRP takes care of configuring
VLANs on Wide Area Network (WAN) ports in the most optimized way.
Repeater mode
The simplest form of Ethernet transport is to transparently forward all frames on the
WAN that are transmitted by the end user via the LAN; this mode is called repeater
mode (also referred to as promiscuous mode or no-tag mode). In this mode minimal
provisioning is necessary.
Multipoint mode
LambdaUnite ® MSS supports Ethernet multipoint applications for specific network
topologies, for example if an end user has more than 2 sites that need to be connected.
It is also possible to support multiple end users on the same Ethernet network, sharing
the available bandwidth on the WAN ports over the SONET/SDH network.
The virtual switch implemented on the GE1 interface is a logical grouping of Ethernet
ports and Virtual Concatenation Group (VCG) ports that share interconnect and a
common set of properties. The virtual switch is automatically instantiated as soon as
the VLAN tagging mode is set to IEEE802.1Q multipoint mode. All 4 LAN ports and
all 4 WAN ports of the GE1 circuit pack are part of the single virtual switch.
Regarding multipoint Ethernet service a more general terminology is needed to cover
the functions of LAN and WAN ports. The new application focused terms are:
•
•
•
•
customer LAN ports (the default for LAN ports)
network WAN ports (the default for WAN ports)
network LAN ports
customer WAN ports.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
9-25
Issue 2, July 2008
See notice on first page
Traffic provisioning concepts
Virtual LAN
By default, network ports participate in STP and GVRP, and customer ports have a
PVID and a Valid VLAN list assigned. LAN ports default to customer port role and
WAN ports to network role. All default values can be overridden.
VLAN trunking
Trunking applications are those applications where traffic of multiple end users is
handed-off via a single physical Ethernet interface to a router or switch for further
processing. This scenario is also called “back-hauling”, since all traffic is transported to
a central location, for example a point-of-presence (PoP) of a service provider.
Trunking applications can be classified into two topology types, trunking in the
hub-node and distributed aggregation in the access network.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
9-26
Traffic provisioning concepts
Tagging
schemes
...................................................................................................................................................................................................................................
Principles
LambdaUnite ® MSS systems support these tagging schemes:
•
•
IEEE 802.1Q VLAN tagging
Transparent tagging
IEEE 802.1Q VLAN tagging
All frames on the network links have a single VLAN tag. This tag is either the tag that
was created by the end user equipment; or it is inserted on the ingress “customer” port
(the default VLAN id) by the TransLAN ® switch. On egress customer ports the earlier
inserted VLAN tag is removed if a default VLAN id is provided on that port; it should
be the same VLAN id as on the associated ingress ports. To ensure customer isolation,
you must allocate VLANs to customers and to the customer ports, and ensure that
VLANs don’t overlap. The IEEE 802.1Q VLAN tagging scheme supports VLAN
trunking, i.e. traffic from multiple different end users is multiplexed over one physical
interface towards an IP router in an ISP POP. End user identification and isolation is
done via the VLAN tag.
Transparent tagging
The “transparent tagging” scheme, also known as “double tagging” or “VPN tagging”,
is a Lucent Technologies proprietary tagging scheme.
All frames that enter the network are prefixed with a customer identification (CID) tag.
Each customer port on the network is assigned a CID. As all frames are prefixed, there
is no difference between end user frames that were originally VLAN tagged or
untagged, only the CID is used in Ethernet switching decisions. There is no need for
an operator to coordinate the end user VLAN schemes, but CIDs must be assigned
consistently per customer over the whole Ethernet network. VLAN trunking is not
supported, due to the proprietary tagging scheme.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
9-27
Issue 2, July 2008
See notice on first page
Traffic provisioning concepts
Spanning
tree protocol
...................................................................................................................................................................................................................................
Principles
The spanning tree protocol (STP) is a standard Ethernet method for eliminating loops
and providing alternate routes for service protection. Standard STP depends to
information sharing among Ethernet switches/bridges to reconfigure the spanning tree
in the event of a failure. The STP algorithm calculates the best loop-free path
throughout the network. STP defines a tree that spans all switches in the network; it
e.g. uses the capacity available bandwidth on a link (path cost) to find the optimum
tree. It forces redundant links into a standby (blocked) state. If a link fails or if a STP
path cost changes the STP algorithm reconfigures the Spanning Tree topology and may
reestablish previously blocked links. The STP also determines one switch that will be
the root switch; all leaves in the Spanning Tree extend from the root switch.
Rapid spanning tree protocol
Rapid spanning tree protocol (rSTP) reduces the time that the STP protocol needs to
reconfigure after network failures. Instead of several tens of seconds, rSTP can
reconfigure in less than a second. The actual reconfiguration time depends on several
parameters, the two most prominent are the network size and complexity. IEEE802.1w
describes the standard implementation for rSTP.
Generic VLAN registration protocol
Generic VLAN registration protocol (GVRP) is an additional protocol that simplifies
VLAN assignment on network ports and ensures consistency among switches in a
network. Further it prevents unnecessary broadcasting of Ethernet frames by
forwarding VLAN frames only to those parts of the network that have customer ports
with that VLAN ID.
The operator configures VLANs on customer ports, and GVRP will take care of
configuring VLANs on network ports – in the most optimized way. Note that GVRP
and Spanning Tree Protocol interact with each other. After a stable Spanning Tree is
determined (at initialization or after a reconfiguration due to a failure) the GVRP
protocol will recompute the best VLAN assignments on all network ports, given the
new spanning tree topology.
The provisioned VLANs on customer ports are called static VLAN entries; the VLANs
assigned by GVRP are called dynamic VLAN entries. The dynamic VLAN entries
need not be stored in NE’s database.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
9-28
Traffic provisioning concepts
Spanning tree protocol
GVRP can be enabled (default) or disabled per virtual switch:
•
•
In the enabled case up to 247 VLANs can be supported through GVRP; an alarm
will be raised if more then 247 VLANs are provisioned on an Ethernet network.
This limitation depends on the processor performance.
If GVRP is disabled, up to 4093 VLANs per Gigabit Ethernet circuit pack port are
supported.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
9-29
Issue 2, July 2008
See notice on first page
Traffic provisioning concepts
Link
path through
...................................................................................................................................................................................................................................
Principles
The Gigabit Ethernet interfaces on the LambdaUnite ® MSS network elements support
the so-called link pass through (LPT) mode.
The LPT mode can be used to enable or improve network protection schemes on the
equipment external to the TransLAN ® systems.
The LPT mode can be enabled or disabled per GbE port.
Important! The LPT mode is only supported on GbE ports (LAN ports) that
operate in a strict one-to-one association with a WAN port using GFP
encapsulation.
Important! Link path through (LPT) is not supported by the Gigabit Ethernet
transmission unit GE1.
Please refer to the following figure for clarification and further reference.
B
SDH/SONET network
A
GE10PL1
4
GE10PL1
5
2
3
1
If an upstream GbE fiber failure (e.g. a fiber cut) or equipment failure (1) is detected
at node A, then a Client Signal Fail (CSF) indication is inserted into the
GFP-encapsulated signal (2). If such a CSF indication or a Server Signal Fail (SSF)
condition (due to a failure on the transmission line (3) for example) is detected at node
B (4), then this can be used to trigger the inhibition of the transmitter at the LAN
egress port (5) as a consequent action.
Important! Please note that once the LPT mode is activated on a LAN port, any
requests to have more than two ports on the associated virtual switch will be
rejected. In order to increase the number of ports on the virtual switch, the LPT
mode first has to be disabled.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
9-30
10
Traffic provisioning tasks
10
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter informs about how to perform the most common tasks related to traffic
provisioning.
Contents
Provisioning of cross-connections
10-4
To view all cross-connections
10-4
To view lower-order cross-connections
10-8
To view higher-order cross-connections
10-12
To add an uncorrelated lower-order cross-connection
10-16
To add an uncorrelated higher-order cross-connection
10-19
To modify a lower-order cross-connection’s topology
10-22
To modify a higher-order cross-connection’s topology
10-26
To modify a cross-connection’s parameters
10-30
To change a higher-order cross-connection from ONNS to traditional
mode
10-33
To roll the input of a lower-order cross-connection from one tributary
port to another
10-35
To roll the input of a higher-order cross-connection from one tributary
port to another
10-38
To delete a cross-connection
10-41
To retrieve ONNS to UPSR/SNCP constructs
10-44
To add an ONNS to UPSR/SNCP construct
10-46
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-1
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
Overview
To delete an ONNS to UPSR/SNCP construct
10-48
Provisioning of path protection groups (SNCP, UPSR)
10-50
To view a list of path protection groups (SNCP, UPSR)
10-50
To modify a path protection group (SNCP, UPSR)
10-52
To operate a path protection group switch (SNCP, UPSR)
10-54
To operate an SNCP VC-4 protection group switch on constituent
members
10-56
Provisioning of MSP protection groups
10-58
To view a list of 1+1 or 1x1 MSP protection groups
10-58
To add a 1+1 MSP protection group
10-59
To add a 1x1 MSP protection group
10-61
To modify a 1+1 or 1x1 MSP protection group
10-63
To delete a 1+1 or 1x1 MSP protection group
10-65
To operate an MSP protection switch
10-67
Provisioning of APS protection groups
10-69
To view a list of 1+1 or 1x1 APS protection groups
10-69
To add a 1+1 APS protection group
10-70
To add a 1x1 APS protection group
10-72
To modify a 1+1 or 1x1 APS protection group
10-74
To delete a 1+1 or 1x1 APS protection group
10-76
To operate an APS protection switch
10-78
Provisioning of MS-SPRing protection groups
10-80
To view a list of 2-fiber MS-SPRing protection groups
10-80
To add a 2-fiber MS-SPRing protection group
10-81
To modify a 2-fiber MS-SPRing protection group
10-83
To delete a 2-fiber MS-SPRing protection group
10-85
To operate a 2-fiber MS-SPRing protection switch
10-87
To view a list of 4-fiber MS-SPRing protection groups
10-89
To add a 4-fiber MS-SPRing protection group
10-90
To modify a 4-fiber MS-SPRing protection group
10-92
To delete a 4-fiber MS-SPRing protection group
10-94
To operate a 4-fiber MS-SPRing protection switch
10-96
Provisioning of BLSR protection groups
10-98
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-2
Traffic provisioning tasks
Overview
To view a list of 2-fiber BLSR protection groups
10-98
To add a 2-fiber BLSR protection group
10-99
To modify a 2-fiber BLSR protection group
10-101
To delete a 2-fiber BLSR protection group
10-103
To operate a 2-fiber BLSR protection switch
10-105
To view a list of 4-fiber BLSR protection groups
10-107
To add a 4-fiber BLSR protection group
10-108
To modify a 4-fiber BLSR protection group
10-110
To delete a 4-fiber BLSR protection group
10-112
To operate a 4-fiber BLSR protection switch
10-114
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-3
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
Provisioning of cross-connections
To
view all cross-connections
...................................................................................................................................................................................................................................
When to use
Use this task to view information on existing cross-connection in the NE.
Related information
For a more detailed explanation, please refer to the description of the RTRV-CRS-ALL
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Cross-connections.
In the Function field, select Retrieve Cross-connections ALL.
Click Go.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-4
Traffic provisioning tasks
To view all cross-connections
Result: The Retrieve Cross-connections ALL page is displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
•
Input Access Identifier – enter a logical port identifier or copy the logical port
identifier from the Ports page to specify the source of the cross-connection. Note:
To view all cross-connections enter 1-1-#-#-all-all-all-all.
Protection Group Name – enter an alphanumeric user-defind string of up to 24
characters to identify a path protection group or let this field empty. Upper and
lower case, spaces and periods are allowed. Value must be included in quotes.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
...................................................................................................................................................................................................
5
The output parameters for this function are:
•
•
•
•
•
•
in_aid
– input access identifier
Specifies the tributary which is the source of the cross-connection.
out_aid – output identifier
Specifies the tributary which is the sink of the cross-connection.
in_aid2 – input access identifier 2
This parameter is applicable to and is present for path-protected cross-connections
only and specifies either the source of the protection leg or the source of the
working leg.
rate – equivalent to the input parameter “modifier”
Indicates the cross-connection rate.
loca – location-a
Specifies the TID of the node at which service is added to the BLSR (bidirectional
line-switched ring). This parameter is required for BLSR THROUGH,
INTER-BLSR and DROP connections only. The “loca” parameter value is an
empty string for ADD and non-BLSR connections. A 2-way cross-connection is
considered to be a DROP if the “out_aid” is a non BLSR tributary.
locastate – squelch map data status for “location-a”
Indicates the validity and the source of the “loca” value.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-5
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
•
•
•
•
•
•
•
•
•
•
•
To view all cross-connections
locz
– location-z
specifies the TID of the node at which service is dropped from the BLSR
(bidirectional line-switched ring). This parameter is required for BLSR THROUGH,
INTER-BLSR and ADD connections. The “locz” parameter value is an empty
string for DROP and non-BLSR connections. A 2-way cross-connection is
considered to be a ADD if the “in_aid” is a non BLSR tributary.
loczstate – squelch map data status for “location-z”
Indicates the validity and the source of the “locz” value.
lpbkstat – loopback-status
Specifies whether a cross-connection loopback exists on the input tributary or the
output tributary of the cross-connection.
omode – output mode
Specifies the output mode of the cross-connection.
repleg – reported leg pair
Provides compact information about the leg(s) of cross-connections.
rtnomode – return output mode
Specifies the output mode for the return direction of the cross-connection.
rtntaccstat – return test access status
Indicates indicates whether the input tributary of the return direction
(destination-to-source) of a 2-way cross-connection is cross-connected or bridged to
a test access tributary of a test session. In the case of a 1-way cross-connection the
parameter shall be omitted.
rtnxcappl – return cross-connection application
This parameter is a numeric value which indicates the application for which the
return cross-connection is used in the context of compound cross-connection
topologies.
rtnxcnum – return cross-connection number
This parameter is a multiple-digit number identifying the cross-connection number
for the return direction (destination to source i.e. “out_aid” to “in_aid”) of a 2-way
cross-connection.
taccstat – test access status
Indicates whether the input tributary of a 1-way cross-connection or the input
tributary of the source-to-destination direction of a 2-way cross-connection is
crossconnected or bridged to a test access tributary of a test session.
xcappl – cross-connection application
This parameter is a numeric value which indicates the application for which the
cross-connection is used in the context of compound cross-connection topologies.
The parameter is not further processed in the NE, but only stored (when
establishing or modifying the cross-connection) and returned when retrieving the
cross-connection.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-6
Traffic provisioning tasks
•
•
To view all cross-connections
xcnum
– cross-connection number
This parameter is a multiple digit number, identifying each leg in a specific
compound cross-connection.
xconcls – cross-connection class
Identifies, whether the cross-connection has been setup in the TRADITIONAL way
by an operator via the “ENT-CRS” command or via the NN application as part of
an ENT-PATH command. This parameter therefore also indicates who is the owner
of the cross-connection and can modify or delete it.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-7
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To
view lower-order cross-connections
...................................................................................................................................................................................................................................
When to use
Use this task to view information on existing lower-order cross-connections in the NE.
Related information
For a more detailed explanation, please refer to the description of the
RTRV-CRS-{modifier} command in the LambdaUnite ® MSS Operations System
Engineering Guide.
For {modifier} select:
•
LOVT1.5, LOVC3, or LOVC12.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Cross-connections.
In the Function field, select Retrieve Cross-connection Low Order {layer},
where {layer}:
• VT1.5, VC-3, or VC-12
5. Click Go.
1.
2.
3.
4.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-8
Traffic provisioning tasks
To view lower-order cross-connections
Result: The Retrieve Cross-connection Low Order {layer} page is displayed. The
respective {layer} page depends on the selection of the correcponding {layer} refer
to item 4 of this step.
...................................................................................................................................................................................................
3
In the field Input Access Identifier – enter a logical port identifier or copy the logical
port identifier from the Ports page to specify the source of the cross-connection.
Note: To view all cross-connections enter 1-1-#-#-all-all-all-all.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
...................................................................................................................................................................................................
5
The output parameters for this function are:
•
•
•
•
•
•
•
in_aid
– input access identifier
Specifies the tributary which is the source of the cross-connection.
out_aid – output identifier
Specifies the tributary which is the sink of the cross-connection.
in_aid2 – input access identifier 2
This parameter is applicable to and is present for path-protected cross-connections
only and specifies either the source of the protection leg or the source of the
working leg.
rate – equivalent to the input parameter “modifier”
Indicates the cross-connection rate.
loca – location-a
Specifies the TID of the node at which service is added to the BLSR (bidirectional
line-switched ring ). This parameter is required for BLSR THROUGH,
INTER-BLSR and DROP connections only. The “loca” parameter value is an
empty string for ADD and non-BLSR connections. A 2-way cross-connection is
considered to be a DROP if the “out_aid” is a non BLSR tributary.
locastate – squelch map data status for “location-a”
Indicates the validity and the source of the “loca” value.
locz – location-z
specifies the TID of the node at which service is dropped from the BLSR
(bidirectional line-switched ring ). This parameter is required for BLSR
THROUGH, INTER-BLSR and ADD connections. The “locz” parameter value is
an empty string for DROP and non-BLSR connections. A 2-way cross-connection is
considered to be a ADD if the “in_aid” is a non BLSR tributary.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-9
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
•
•
•
•
•
•
•
•
•
•
•
•
To view lower-order cross-connections
loczstate
– squelch map data status for “location-z”
Indicates the validity and the source of the “locz” value.
lpbkstat – loopback-status
Specifies whether a cross-connection loopback exists on the input tributary or the
output tributary of the cross-connection.
omode – output mode
Specifies the output mode of the cross-connection.
repleg – reported leg pair
Provides compact information about the leg(s) of cross-connections.
rtnomode – return output mode
Specifies the output mode for the return direction of the cross-connection.
rtntaccstat – return test access status
Indicates indicates whether the input tributary of the return direction
(destination-to-source) of a 2-way cross-connection is cross-connected or bridged to
a test access tributary of a test session. In the case of a 1-way cross-connection the
parameter shall be omitted.
rtnxcappl – return cross-connection application
This parameter is a numeric value which indicates the application for which the
return cross-connection is used in the context of compound cross-connection
topologies.
rtnxcnum – return cross-connection number
This parameter is a multiple-digit number identifying the cross-connection number
for the return direction (destination to source i.e. “out_aid” to “in_aid”) of a 2-way
cross-connection.
taccstat – test access status
Indicates whether the input tributary of a 1-way cross-connection or the input
tributary of the source-to-destination direction of a 2-way cross-connection is
crossconnected or bridged to a test access tributary of a test session.
xcappl – cross-connection application
This parameter is a numeric value which indicates the application for which the
cross-connection is used in the context of compound cross-connection topologies.
The parameter is not further processed in the NE, but only stored (when
establishing or modifying the cross-connection) and returned when retrieving the
cross-connection.
xcnum – cross-connection number
This parameter is a multiple digit number, identifying each leg in a specific
compound cross-connection.
xconcls – cross-connection class
Identifies, whether the cross-connection has been setup in the TRADITIONAL way
by an operator via the “ENT-CRS” command or via the NN application as part of
an ENT-PATH command. This parameter therefore also indicates who is the owner
of the cross-connection and can modify or delete it.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-10
Traffic provisioning tasks
To view lower-order cross-connections
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-11
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To
view higher-order cross-connections
...................................................................................................................................................................................................................................
When to use
Use this task to view information on existing higher-order cross-connections in the NE.
Related information
For a more detailed explanation, please refer to the description of the
RTRV-CRS-{modifier} command in the LambdaUnite ® MSS Operations System
Engineering Guide.
For {modifier} select:
•
•
STS1, STS12, STS192, STS3, or STS48,
VC3, VC4, VC416C, VC44C, or VC464C.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1. In the NE type field, select a type of NE (if not already present).
2. In the NE name field, select the name of the target NE (if not already present).
3. In the Category field, select Cross-connections.
4. In the Function field, select Retrieve Cross-connection {layer},
where {layer}:
• STS-1, STS-12c, STS-192c, STS-3c, or STS-48c,
• VC-3, VC-4, VC-4-16c, VC-4-4c, or VC-4-64c.
5. Click Go.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-12
Traffic provisioning tasks
To view higher-order cross-connections
Result: The Retrieve Cross-connection {layer} page is displayed. The respective
{layer} page depends on the selection of the correcponding {layer} refer to item 4
of this step.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
•
Input Access Identifier – enter a logical port identifier or copy the logical port
identifier from the Ports page to specify the source of the cross-connection. Note:
To view all cross-connections enter 1-1-#-#-all-all-all-all.
Protection Group Name – enter an alphanumeric user-defind string of up to 24
characters to identify a path protection group or let this field empty. Upper and
lower case, spaces and periods are allowed. Value must be included in quotes.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
...................................................................................................................................................................................................
5
The output parameters for this function are:
•
•
•
•
•
•
in_aid – input access identifier
Specifies the tributary which is the source of the cross-connection.
out_aid – output identifier
Specifies the tributary which is the sink of the cross-connection.
in_aid2 – input access identifier 2
This parameter is applicable to and is present for path-protected cross-connections
only and specifies either the source of the protection leg or the source of the
working leg.
rate – equivalent to the input parameter “modifier”
Indicates the cross-connection rate.
loca – location-a
Specifies the TID of the node at which service is added to the BLSR (bidirectional
line-switched ring ). This parameter is required for BLSR THROUGH,
INTER-BLSR and DROP connections only. The “loca” parameter value is an
empty string for ADD and non-BLSR connections. A 2-way cross-connection is
considered to be a DROP if the “out_aid” is a non BLSR tributary.
locastate – squelch map data status for “location-a”
Indicates the validity and the source of the “loca” value.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-13
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
•
•
•
•
•
•
•
•
•
•
•
To view higher-order cross-connections
locz
– location-z
specifies the TID of the node at which service is dropped from the BLSR
(bidirectional line-switched ring ). This parameter is required for BLSR
THROUGH, INTER-BLSR and ADD connections. The “locz” parameter value is
an empty string for DROP and non-BLSR connections. A 2-way cross-connection is
considered to be a ADD if the “in_aid” is a non BLSR tributary.
loczstate – squelch map data status for “location-z”
Indicates the validity and the source of the “locz” value.
lpbkstat – loopback-status
Specifies whether a cross-connection loopback exists on the input tributary or the
output tributary of the cross-connection.
omode – output mode
Specifies the output mode of the cross-connection.
repleg – reported leg pair
Provides compact information about the leg(s) of cross-connections.
rtnomode – return output mode
Specifies the output mode for the return direction of the cross-connection.
rtntaccstat – return test access status
Indicates indicates whether the input tributary of the return direction
(destination-to-source) of a 2-way cross-connection is cross-connected or bridged to
a test access tributary of a test session. In the case of a 1-way cross-connection the
parameter shall be omitted.
rtnxcappl – return cross-connection application
This parameter is a numeric value which indicates the application for which the
return cross-connection is used in the context of compound cross-connection
topologies.
rtnxcnum – return cross-connection number
This parameter is a multiple-digit number identifying the cross-connection number
for the return direction (destination to source i.e. “out_aid” to “in_aid”) of a 2-way
cross-connection.
taccstat – test access status
Indicates whether the input tributary of a 1-way cross-connection or the input
tributary of the source-to-destination direction of a 2-way cross-connection is
crossconnected or bridged to a test access tributary of a test session.
xcappl – cross-connection application
This parameter is a numeric value which indicates the application for which the
cross-connection is used in the context of compound cross-connection topologies.
The parameter is not further processed in the NE, but only stored (when
establishing or modifying the cross-connection) and returned when retrieving the
cross-connection.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-14
Traffic provisioning tasks
•
•
To view higher-order cross-connections
xcnum
– cross-connection number
This parameter is a multiple digit number, identifying each leg in a specific
compound cross-connection.
xconcls – cross-connection class
Identifies, whether the cross-connection has been setup in the TRADITIONAL way
by an operator via the “ENT-CRS” command or via the NN application as part of
an ENT-PATH command. This parameter therefore also indicates who is the owner
of the cross-connection and can modify or delete it.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-15
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To
add an uncorrelated lower-order cross-connection
...................................................................................................................................................................................................................................
When to use
Use this task to establish an uncorrelated lower-order cross-connection between
tributaries in the NE.
Important! In the standard way of operation it is not necessary and not
recommended to add cross-connections separately in the network elements. Lucent
OMS creates the necessary cross-connections automatically with the
implementation of network connections.
The “{modifier}” indicates the cross-connection “rate” of the tributary for which the
command is applied to. There is no difference if the “rate” is specified as a
SONET-rate or as SDH-rate for the establishment of the cross-connection.
Related information
For a more detailed explanation, please refer to the description of the
ENT-CRS-{modifier} command in the LambdaUnite ® MSS Operations System
Engineering Guide.
For {modifier} select:
•
LOVT1, LOVC3, or LOVC12.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
In
In
In
In
the
the
the
the
NE type field, select a type of NE (if not already present).
NE name field, select the name of the target NE (if not already present).
Category field, select Cross-connections.
Function field, select Enter Cross-connection Low Order {layer},
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-16
Traffic provisioning tasks
To add an uncorrelated lower-order cross-connection
where {layer}:
• VT1.5, VC-3, or VC-12
5. Click Go.
Result: The Enter Cross-connection Low Order {layer} page is displayed. The
respective {layer} page depends on the selection of the correcponding {layer} refer
to item 4 of this step.
...................................................................................................................................................................................................
3
Change the entries or selections for any of the fields that are modifiable:
•
•
•
•
•
•
•
•
Input port identifier – enter a low order logical port identifier or copy the logical
port identifier from the Ports page to specify the source of the cross-connection.
Note:
– In case of a 1-way cross-connection, the source of a cross-connection is
unambiguous. In this case the cross-connection will be retrieved by the
RTRV-CRS, which has the identical “in_aid”.
– In case of a 2-way cross-connection, the source is not defined (the source could
be the “in_aid” or “out-aid” of the cross-connection). In this case both aids
(“in_aid” or “out-aid”) of the cross-connection can be used as the “in_aid”
parameter of the RTRV-CRS command.
Output port identifier – enter a low order logical port identifier or copy the
logical port identifier from the Ports page to specify the tributary which is the sink
of the cross-connection.
Crossconnection topology – select 1 way, 2 way, or 1 way path protected to
specify the topology of the cross-connection to be established.
Protection leg input port ID – enter a low order logical port identifier or copy the
logical port identifier from the Ports page to specify the source of the protection
leg. This parameter is applicable to path-protected cross-connections only.
Hold off timer (msec) – enter either a value from 0 to 99 ms in 1 step
increments or a value from 100 to 10000 ms in 100 step increments to specify the
value of the hold-off timer for automatic protection switching. This parameter is
applicable to path-protected cross-connections only and shall be omitted for non
path-protected cross-connections.
Output mode – select Normal output, Unequipped signal, or AIS signal to specify
the output mode of the cross-connection.
Path protection group name – enter an alphanumeric user-defind string of up to
24 characters to identify a path protection group. Upper and lower case, spaces and
periods are allowed. Value must be included in quotes.
Revertive mode enable – select either a single parameter Enable, or Disable to
specify whether the path protection operates in revertive mode or
non-revertive-mode.This parameter is applicable to path-protected cross-connections
only and shall be omitted for non path-protected cross-connections.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-17
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
•
•
•
•
•
•
•
To add an uncorrelated lower-order cross-connection
Return output mode – select Normal output, Unequipped signal, or AIS signal.
This parameter is only applicable for 2-way cross-connections and is omitted for
1-way and path-protected cross-connections.
SNCP Type – select SNCI, SNCN, or Not applicable to specify the SNCP mode,
that means the switch criteria used for automatic protection switching. This
parameter is mandatory for path-protected cross-connections and only applicable to
them. The parameter shall be omitted for non path-protected cross-connections.
Wait to restore time (min) – enter a value from 0 min. to 60 min. to specify the
value of the wait-to-restore time for automatic protection switching. This parameter
is applicable to path-protected cross-connections only and is omitted for non
path-protected cross-connections.
Crossconnection application – enter a numeric value from 0 to 255 to indicate
the application for which the cross-connection is used in the context of compound
cross-connection topologies.
Crossconnection number – enter a 12-digit numeric value to identify each leg in
a specific compound cross-connection. Compound cross-connections are a
composition of several atomic cross-connections in order to form complex
scenarios.
Source node NE name – enter a string of up to 20 characters to specify the TID
of the node at which service is added to the BLSR (bidirectional line-switched
ring). This parameter is required for BLSR. In addition the special character
underscore (“_”) and the password characters are allowed.
Destination node NE name – enter a string of up to 20 characters to specify the
TID of the node at which service is dropped from the BLSR (bidirectional
line-switched ring). This parameter is required for BLSR. In addition the special
character underscore (“_”) and the password characters are allowed.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-18
Traffic provisioning tasks
To
add an uncorrelated higher-order cross-connection
...................................................................................................................................................................................................................................
When to use
Use this task to establish an uncorrelated higher-order cross-connection between
tributaries in the NE.
Important! In the standard way of operation it is not necessary and not
recommended to add cross-connections separately in the network elements. Lucent
OMS creates the necessary cross-connections automatically with the
implementation of network connections.
The “{modifier}” indicates the cross-connection “rate” of the tributary for which the
command is applied to. There is no difference if the “rate” is specified as a
SONET-rate or as SDH-rate for the establishment of the cross-connection.
Related information
For a more detailed explanation, please refer to the description of the
ENT-CRS-{modifier} command in the LambdaUnite ® MSS Operations System
Engineering Guide.
For {modifier} select:
•
•
STS1, STS12, STS192, STS3, or STS48,
VC3, VC4, VC416C, VC44C, or VC464C.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1. In the NE type field, select a type of NE (if not already present).
2. In the NE name field, select the name of the target NE (if not already present).
3. In the Category field, select Cross-connections.
4. In the Function field, select Enter Cross-connection {layer},
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-19
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To add an uncorrelated higher-order cross-connection
where {layer}:
•
STS-1, STS-12c, STS-192c, STS-3c, or STS-48c,
• VC-3, VC-4, VC-4-16c, VC-4-4c, or VC-4-64c.
5. Click Go.
Result: The Enter Cross-connection {layer} page is displayed. The respective
{layer} page depends on the selection of the correcponding {layer} refer to item 4
of this step.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
•
•
•
•
•
•
Input port identifier – enter a logical port identifier or copy the logical port
identifier from the Ports page to specify the source of the cross-connection.
Note:
– In case of a 1-way cross-connection the source of a cross-connection is
unambiguous. In this case the cross-connection will be retrieved by the
RTRV-CRS, which has the identical “in_aid”.
– In case of a 2-way cross-connection the source is not defined (the source could
be the “in_aid” or “out-aid” of the cross-connection). In this case both aids
(“in_aid” or “out-aid”) of the cross-connection can be used as the “in_aid”
parameter of the RTRV-CRS command.
Output port identifier – enter a logical port identifier or copy the logical port
identifier from the Ports page to specify the tributary which is the sink of the
cross-connection.
Crossconnection topology – select 1 way, 2 way, or 1 way path protected to
specify the topology of the cross-connection to be established.
Protection leg input port ID – enter a logical port identifier or copy the logical
port identifier from the Ports page to specify the source of the protection leg. This
parameter is applicable to path-protected cross-connections only.
Hold off timer (msec) – enter either a value from 0 to 99 ms in 1 step increments
or a value from 100 to 10000 ms in 100 step increments to specify the value of
the hold-off timer for automatic protection switching. This parameter is applicable
to path-protected cross-connections only and shall be omitted for non
path-protected cross-connections.
Source node NE name – enter a string of up to 20 characters to specify the TID
of the node at which service is added to the BLSR (bidirectional line-switched
ring). This parameter is required for BLSR. In addition the special character
underscore (“_”) and the password characters are allowed.
Protection source node NE name – enter a string of up to 20 characters to
specify the TID associated with “in_aid2” of the protection leg of a path-protected
cross-connection. In addition the special character underscore (“_”) and the
password characters are allowed.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-20
Traffic provisioning tasks
•
•
•
•
•
•
•
•
•
To add an uncorrelated higher-order cross-connection
Destination node NE name – enter a string of up to 20 characters to specify the
TID of the node at which service is dropped from the BLSR (bidirectional
line-switched ring). This parameter is required for BLSR. In addition the special
character underscore (“_”) and the password characters are allowed.
Output mode – select Normal output, Unequipped signal, or AIS signal to specify
the output mode of the cross-connection.
Path protection group name – enter an alphanumeric user-defind string of up to
24 characters to identify a path protection group. Upper and lower case, spaces and
periods are allowed. Value must be included in quotes.
Revertive mode enable – select either a single parameter Enable, or Disable to
specify whether the path protection operates in revertive mode or
non-revertive-mode.This parameter is applicable to path-protected cross-connections
only and shall be omitted for non path-protected cross-connections.
Return output mode – select Normal output, Unequipped signal, or AIS signal.
This parameter is only applicable for 2-way cross-connections and is omitted for
1-way and path-protected cross-connections.
SNCP Type – select SNCI, SNCN, or Not applicable to specify the SNCP mode,
that means the switch criteria used for automatic protection switching. This
parameter is mandatory for path-protected cross-connections and only applicable to
them. The parameter shall be omitted for non path-protected cross-connections.
Wait to restore time (min) – enter a value from 0 min. to 60 min. to specify the
value of the wait-to-restore time for automatic protection switching. This parameter
is applicable to path-protected cross-connections only and is omitted for non
path-protected cross-connections.
Crossconnection application – enter a numeric value from 0 to 255 to indicate
the application for which the cross-connection is used in the context of compound
cross-connection topologies.
Crossconnection number – enter a 12-digit numeric value to identify each leg in
a specific compound cross-connection. Compound cross-connections are a
composition of several atomic cross-connections in order to form complex
scenarios.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-21
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To
modify a lower-order cross-connection’s topology
...................................................................................................................................................................................................................................
When to use
Use this task to modify a lower-order cross-connection’s topology between a 1-way
point-to-point cross-connection and a path-protected cross-connection.
Important! In the standard way of operation it is not necessary and not
recommended to modify cross-connections separately in the network elements.
Lucent OMS deletes the cross-connections automatically with the modification of
network connections.
The “{modifier}” indicates the cross-connection “rate” of the tributary for which the
command is applied to.
For a 1-way point-to-point to a path-protected conversion, the existing point-to-point
cross-connection leg is converted into a single atomic path-protected cross-connection
between the logical input AID of the existing point-to-point cross-connection, the
specified protection logical input AID and logical output AID of the existing
point-to-point cross-connection. The leg comprised of the AIDs of the existing
point-to-point cross-connection shall be designated as the path protection group
working leg at the time the cross-connection is converted.
If the command is applied to a 2-way cross-connection it will be split up automatically
in two 1-way cross-connections. The command will be executed on the specified in_aid
to out_aid direction, the reverse direction will remain unprotected. Refer also to
chapter Detailed behaviour for more.
For a path-protected to a 1-way point-to-point conversion, it can be selected, which
logical input AID of the existing legs (working leg or the protection leg) of the
path-protected cross-connection shall stay as logical input AID of the created
point-to-point cross-connection. This can be done by specifying the surviving leg of the
existing path protection group as working leg at the time the cross-connection is
converted.
Related information
For a more detailed explanation, please refer to the description of the
CNVT-CCT-{modifier} command in the LambdaUnite ® MSS Operations System
Engineering Guide.
For {modifier} select:
•
LOVT1, LOVC3, or LOVC12.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-22
Traffic provisioning tasks
To modify a lower-order cross-connection’s topology
CAUTION
Service-disruption hazard
Modification of a cross-connection may be traffic affecting.
Before starting to modify a cross-connection, make sure that it is not in use. The traffic
provided on the respective path must have previously been removed (for example
rerouted to another path) before modifying any of the cross-connections included in
that path.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
In
In
In
In
the
the
the
the
NE type field, select a type of NE (if not already present).
NE name field, select the name of the target NE (if not already present).
Category field, select Cross-connections.
Function field, select Convert Cross-connection Topology Low Order
{layer},
where {layer}:
• VT1.5, VC-3, or VC-12
5. Click Go.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-23
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To modify a lower-order cross-connection’s topology
Result: The Convert Cross-connection Topology Low Order {layer} page is
displayed. The respective {layer} page depends on the selection of the
correcponding {layer} refer to item 4 of this step.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
•
•
•
•
•
•
•
•
Input port identifier – enter a low order logical port identifier or may copy the
logical port identifier from the ports page to specify
– 1-way Point-to-Point to a path-protected conversion, the source of the
unprotected cross-connection.
– respectively path-protected to a 1-way point-to-point conversion, the AID of the
input leg which shall stay as source of the created unprotected cross-connection.
Output port identifier – enter a low order logical port identifier or copy the
logical port identifier from the Ports page to specify the sink of the
cross-connection.
Protection leg input port ID – enter a low order logical port identifier or copy the
logical port identifier from the Ports page to specify the input leg for a
path-protected to a 1-way Point-to-Point conversion which shall be dropped.
New cross connect topology – select either a single parameter 1 way, or
1 way path protected to specify the new cross-connection topology.
Hold off timer (msec) – enter a value from 0 to 99 ms in 1 step increments or a
value from 100 to 10000 ms in 100 step increments to specify the “hold-off time”
for automatic protection switching used by the protection state machine.
New input port identifier – enter a low order logical port identifier or copy the
logical port identifier from the Ports page to specify the source aid of the new leg
when converting from a point-to-point to a path-protected cross-connect.
New source node NE name – enter a string of up to 20 characters to specify the
new source TID if the “newinaid” is in a BLSR protection group. It specify that
add node which is related to the protection leg input. “newloca” will be stored as
the “loca2” parameter. In addition the special character underscore (’_’) and the
password characters are allowed.
Original cross connect topology – select either a single parameter 1 way, or
1 way path protected to specify the original cross-connection topology.
Revertive mode enable – select either a single parameter Enable, or Disable to
specify whether revertive or non-revertive mode is used as operation mode of the
protection group. The value “ENABLE” is used if the protection group operates in
revertive mode. The value “DISABLE” is used if the protection group operates in
non-revertive mode.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-24
Traffic provisioning tasks
•
•
•
•
To modify a lower-order cross-connection’s topology
SNCP Type – select either a single parameter SNCI, SNCN, or Not applicable to
specify the type of the path protection w.r.t. switch criteria used by the protection
state machine. The value SNCI (Inherent) is used if server signal fail is used as
switch criteria. The value SNCN (Non-Instrusive) is used if server signal fail and
defects supervised by a non-intrusive path monitor are used as switch criteria. The
value “Not applicable” is used if one of the tributary inputs is related to a port
operating in SONET mode.
Wait to restore time (min) – enter a value from (0 to 60) min to specify the wait
to restore time used by the protection state machine operating in revertive mode.
Crossconnection application – enter a numeric value from (0 to 255) to indicate
the application for which the cross-connection is used in the context of compound
cross-connection topologies.
Crossconnection number – enter a 12-digit numeric value to identify each leg in
a specific compound cross-connection. Compound cross-connections are a
composition of several atomic cross-connections in order to form complex
scenarios.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-25
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To
modify a higher-order cross-connection’s topology
...................................................................................................................................................................................................................................
When to use
Use this task to modify a higher-order cross-connection’s topology between a 1-way
point-to-point cross-connection and a path-protected cross-connection.
Important! In the standard way of operation it is not necessary and not
recommended to modify cross-connections separately in the network elements.
Lucent OMS deletes the cross-connections automatically with the modification of
network connections.
The “{modifier}” indicates the cross-connection “rate” of the tributary for which the
command is applied to.
For a 1-way point-to-point to a path-protected conversion, the existing point-to-point
cross-connection leg is converted into a single atomic path-protected cross-connection
between the logical input AID of the existing point-to-point cross-connection, the
specified protection logical input AID and logical output AID of the existing
point-to-point cross-connection. The leg comprised of the AIDs of the existing
point-to-point cross-connection shall be designated as the path protection group
working leg at the time the cross-connection is converted.
If the command is applied to a 2-way cross-connection it will be split up automatically
in two 1-way cross-connections. The command will be executed on the specified in_aid
to out_aid direction, the reverse direction will remain unprotected. Refer also to
chapter Detailed behaviour for more.
For a path-protected to a 1-way point-to-point conversion, it can be selected, which
logical input AID of the existing legs (working leg or the protection leg) of the
path-protected cross-connection shall stay as logical input AID of the created
point-to-point cross-connection. This can be done by specifying the surviving leg of the
existing path protection group as working leg at the time the cross-connection is
converted.
Related information
For a more detailed explanation, please refer to the description of the
CNVT-CCT-{modifier} command in the LambdaUnite ® MSS Operations System
Engineering Guide.
For {modifier} select:
•
•
STS1, STS12, STS192, STS3, or STS48,
VC3, VC4, VC416C, VC44C, or VC464C.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-26
Traffic provisioning tasks
To modify a higher-order cross-connection’s topology
CAUTION
Service-disruption hazard
Modification of a cross-connection may be traffic affecting.
Before starting to modify a cross-connection, make sure that it is not in use. The traffic
provided on the respective path must have previously been removed (for example
rerouted to another path) before modifying any of the cross-connections included in
that path.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Cross-connections.
In the Function field, select Convert Cross-connection Topology {layer},
where {layer}:
• STS-1, STS-12c, STS-192c, STS-3c, or STS-48c,
• VC-3, VC-4, VC-4-16c, VC-4-4c, or VC-4-64c.
5. Click Go.
1.
2.
3.
4.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-27
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To modify a higher-order cross-connection’s topology
Result: The Convert Cross-connection Topology {layer} page is displayed. The
respective {layer} page depends on the selection of the correcponding {layer} refer
to item 4 of this step.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
•
•
•
•
•
•
•
•
•
Input port identifier – enter a logical port identifier or copy the logical port
identifier from the Ports page to specify
– 1-way Point-to-Point to a path-protected conversion, the source of the
unprotected cross-connection.
– respectively path-protected to a 1-way point-to-point conversion, the AID of the
input leg which shall stay as source of the created unprotected cross-connection.
Output port identifier – enter a logical port identifier or copy the logical port
identifier from the Ports page to specify the sink of the cross-connection.
Protection leg input port ID – enter a logical port identifier or copy the logical
port identifier from the Ports page to specify the input leg for a path-protected to a
1-way Point-to-Point conversion which shall be dropped.
New cross connect topology – select either a single parameter 1 way, or
1 way path protected to specify the new cross-connection topology.
Hold off timer (msec) – enter a value from 0 to 99 ms in 1 step increments or a
value from 100 to 10000 ms in 100 step increments to specify the “hold-off time”
for automatic protection switching used by the protection state machine.
New input port identifier – enter a logical port identifier or copy the logical port
identifier from the Ports page to specify the source aid of the new leg when
converting from a point-to-point to a path-protected cross-connect.
New source node NE name – enter a string of up to 20 characters to specify the
new source TID if the “newinaid” is in a BLSR protection group. It specify that
add node which is related to the protection leg input. “newloca” will be stored as
the “loca2” parameter. In addition the special character underscore (’_’) and the
password characters are allowed.
Original cross connect topology – select either a single parameter 1 way, or
1 way path protected to specify the original cross-connection topology.
Path protection group name – enter an alphanumeric user-defind string of up to
24 characters to identify a path protection group. Upper and lower case, spaces and
periods are allowed. Value must be included in quotes.
Revertive mode enable – select either a single parameter Enable, or Disable to
specify whether revertive or non-revertive mode is used as operation mode of the
protection group. The value “ENABLE” is used if the protection group operates in
revertive mode. The value “DISABLE” is used if the protection group operates in
non-revertive mode.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-28
Traffic provisioning tasks
•
•
•
•
To modify a higher-order cross-connection’s topology
SNCP Type – select either a single parameter SNCI, SNCN, or Not applicable to
specify the type of the path protection w.r.t. switch criteria used by the protection
state machine. The value SNCI (Inherent) is used if server signal fail is used as
switch criteria. The value SNCN (Non-Instrusive) is used if server signal fail and
defects supervised by a non-intrusive path monitor are used as switch criteria. The
value “Not applicable” is used if one of the tributary inputs is related to a port
operating in SONET mode.
Wait to restore time (min) – enter a value from (0 to 60) min to specify the wait
to restore time used by the protection state machine operating in revertive mode.
Crossconnection application – enter a numeric value from (0 to 255) to indicate
the application for which the cross-connection is used in the context of compound
cross-connection topologies.
Crossconnection number – enter a 12-digit numeric value to identify each leg in
a specific compound cross-connection. Compound cross-connections are a
composition of several atomic cross-connections in order to form complex
scenarios.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-29
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To
modify a cross-connection’s parameters
...................................................................................................................................................................................................................................
When to use
Use this task to modify cross-connection parameters.
Important! In the standard way of operation it is not necessary and not
recommended to modify cross-connections separately in the network elements.
Lucent OMS deletes the cross-connections automatically with the modifiycation of
network connections.
Related information
For a more detailed explanation, please refer to the description of the
ED-CRS-{modifier} command in the LambdaUnite ® MSS Operations System
Engineering Guide.
For lower-order cross-connections {modifier} select:
•
LOVT1, LOVC3, or LOVC12.
For higher-order cross-connections{modifier} select:
•
•
STS1, STS12, STS192, STS3, or STS48,
VC3, VC4, VC416C, VC44C, or VC464C.
CAUTION
Service-disruption hazard
Modification of a cross-connection may be traffic affecting.
Before starting to modify a cross-connections parameters, make sure that it is not in
use. The traffic provided on the respective path must have previously been removed
(for example rerouted to another path) before modifying any of the cross-connections
included in that path.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-30
Traffic provisioning tasks
To modify a cross-connection’s parameters
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
In
In
In
In
the
the
the
the
NE type field, select a type of NE (if not already present).
NE name field, select the name of the target NE (if not already present).
Category field, select Cross-connections.
Function field, select:
Edit Cross-connection Low Order {layer}, where {layer}
•
VT1.5, VC-3, or VC-12.
Edit Cross-connection {layer}, where {layer}
• STS-1, STS-12c, STS-192c, STS-3c, or STS-48c,
• VC-3, VC-4, VC-4-16c, VC-4-4c, or VC-4-64c.
5. Click Go.
Result: The Edit Cross-connection Low Order {layer} page respective the Edit
Cross-connection {layer} page depending on the selection of the correcponding
{layer} of item 4 of this step is displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
Input port identifier – enter a low order logical port identifier or copy the logical
port identifier from the Ports page to specify the source of the cross-connection.
•
Output port identifier – enter a low order logical port identifier or copy the
logical port identifier from the Ports page to specify the tributary which is the sink
of the cross-connection.
•
•
•
Source node NE name – enter a string of up to 20 characters to specify the TID
of the node at which service is added to the BLSR (bidirectional line-switched
ring). In addition the special character underscore (’_’) and the password characters
are allowed.
Destination node NE name – enter a string of up to 20 characters to specify the
TID of the node at which service is dropped from the BLSR (bidirectional
line-switched ring). This parameter is required for BLSR. In addition the special
character underscore (’_’) and the password characters are allowed.
Output mode – select a single parameter Normal output, Unequipped signal, or
AIS signal to specify the output mode of the cross-connection.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-31
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
•
•
To modify a cross-connection’s parameters
Crossconnection application – enter a numeric value from (0 to 255) to indicate
the application for which the cross-connection is used in the context of compound
cross-connection topologies.
Crossconnection number – enter a 12-digit numeric value to identify each leg in
a specific compound cross-connection. Compound cross-connections are a
composition of several atomic cross-connections in order to form complex
scenarios.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-32
Traffic provisioning tasks
To change a higher-order cross-connection from ONNS to
traditional
mode
...................................................................................................................................................................................................................................
When to use
Use this task to change a higher-order cross-connection from ONNS to traditional
mode by setting the cross-connection class parameter to “TRADITIONAL”.
Important! In the standard way of operation it is not necessary and not
recommended to change cross-connections separately in the network elements.
Lucent OMS deletes the cross-connections automatically with the change of
network connections.
Related information
For a more detailed explanation, please refer to the description of the
ED-NNCRS-{modifier} command in the LambdaUnite ® MSS Operations System
Engineering Guide.
For {modifier} select:
•
•
STS1, STS12, STS192, STS3, or STS48,
VC3, VC4, VC416C, VC44C, or VC464C.
CAUTION
Service-disruption hazard
Modification of a cross-connection may be traffic affecting.
Before starting to change a cross-connections parameters, make sure that it is not in
use. The traffic provided on the respective path must have previously been removed
(for example rerouted to another path) before changing any of the cross-connections
included in that path.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-33
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To change a higher-order cross-connection from ONNS to
traditional mode
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Cross-connections.
In the Function field, select Edit NN Cross-connection {layer},
where {layer}:
• STS-1, STS-12c, STS-192c, STS-3c, or STS-48c,
• VC-3, VC-4, VC-4-16c, VC-4-4c, or VC-4-64c.
5. Click Go.
1.
2.
3.
4.
Result: The Edit NN Cross-connection {layer} page depending on the selection of
the correcponding {layer} of item 4 of this step is displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
Input port identifier – enter a logical port identifier or copy the logical port
identifier from the Ports page to specify the source of the cross-connection.
•
Output port identifier – enter a logical port identifier or copy the logical port
identifier from the Ports page to specify the tributary which is the sink of the
cross-connection.
•
Cross connection class – select Traditional to identify whether the
cross-connection has been switched explicitly on the traditional way via an
ENT-CRS command or implicitly via setting up an ONNS path.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-34
Traffic provisioning tasks
To roll the input of a lower-order cross-connection from one
tributary
port to another
...................................................................................................................................................................................................................................
When to use
Use this task to roll the input of a cross-connection from a given tributary to another
tributary while leaving the output unchanged.
Important! In the standard way of operation it is not necessary and not
recommended to roll cross-connections separately in the network elements. Lucent
OMS deletes the cross-connections automatically with the roll modification of
network connections.
The “{modifier}” indicates the cross-connection “rate” of the tributary for which the
command is applied to. There is no difference if the “rate” is specified as a
SONET-rate or as SDH-rate for the deleting of the old and establishing of the new
cross-connection.
Related information
For a more detailed explanation, please refer to the description of the
ENT-ROLL-{modifier} command in the LambdaUnite ® MSS Operations System
Engineering Guide.
For {modifier} select:
•
LOVT1, LOVC3, or LOVC12.
CAUTION
Service-disruption hazard
Rolling of a cross-connection may be traffic affecting.
Before starting to roll a cross-connection, make sure that it is not in use. The traffic
provided on the respective path must have previously been removed (for example
rerouted to another path) before rolling any of the cross-connections included in that
path.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-35
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To roll the input of a lower-order cross-connection from
one tributary port to another
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Cross-connections.
In the Function field, select Enter Roll Low Order {layer},
where {layer}:
• VT1.5, VC-3, or VC-12
5. Click Go.
1.
2.
3.
4.
Result: The Enter Roll Low Order {layer} page depending on the selection of the
correcponding {layer} of item 4 of this step is displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
Input port identifier – enter a low order logical port identifier or copy the logical
port identifier from the Ports page to specify the source of the cross-connection.
•
Output port identifier – enter a low order logical port identifier or copy the
logical port identifier from the Ports page to specify the sink of the
cross-connection.
•
•
New input port identifier – enter a low order logical port identifier or copy the
logical port identifier from the Ports page to specify the source of the new
cross-connection to be established
New source node NE name – enter a string of up to 20 characters to specify the
new source TID if the “newinaid” is in a BLSR protection group. In addition the
special character underscore (’_’) and the password characters are allowed.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-36
Traffic provisioning tasks
To roll the input of a lower-order cross-connection from
one tributary port to another
•
Crossconnection application – enter a numeric value from (0 to 255) to indicate
•
the application for which the cross-connection is used in the context of compound
cross-connection topologies.
Crossconnection number – enter a 12-digit numeric value to identify each
cross-connection leg in a specific compound cross-connection. topology. This
parameter is optional – if not entered, the default is used.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-37
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To roll the input of a higher-order cross-connection from one
tributary
port to another
...................................................................................................................................................................................................................................
When to use
Use this task to roll the input of a cross-connection from a given tributary to another
tributary while leaving the output unchanged.
Important! In the standard way of operation it is not necessary and not
recommended to roll cross-connections separately in the network elements. Lucent
OMS deletes the cross-connections automatically with the roll modification of
network connections.
The “{modifier}” indicates the cross-connection “rate” of the tributary for which the
command is applied to. There is no difference if the “rate” is specified as a
SONET-rate or as SDH-rate for the deleting of the old and establishing of the new
cross-connection.
Related information
For a more detailed explanation, please refer to the description of the
ENT-ROLL-{modifier} command in the LambdaUnite ® MSS Operations System
Engineering Guide.
For {modifier} select:
•
•
STS1, STS12, STS192, STS3, or STS48,
VC3, VC4, VC416C, VC44C, or VC464C.
CAUTION
Service-disruption hazard
Rolling of a cross-connection may be traffic affecting.
Before starting to roll a cross-connection, make sure that it is not in use. The traffic
provided on the respective path must have previously been removed (for example
rerouted to another path) before rolling any of the cross-connections included in that
path.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-38
Traffic provisioning tasks
To roll the input of a higher-order cross-connection from
one tributary port to another
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Cross-connections.
In the Function field, select Enter Roll {layer},
where {layer}:
• STS-1, STS-12c, STS-192c, STS-3c, or STS-48c,
• VC-3, VC-4, VC-4-16c, VC-4-4c, or VC-4-64c.
5. Click Go.
1.
2.
3.
4.
Result: The Enter Roll {layer} page depending on the selection of the
correcponding {layer} of item 4 of this step is displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
•
•
•
•
Input port identifier – enter a logical port identifier or copy the logical port
identifier from the Ports page to specify the source of the cross-connection.
Output port identifier – enter a logical port identifier or copy the logical port
identifier from the Ports page to specify the sink of the cross-connection.
New input port identifier – enter a logical port identifier or copy the logical port
identifier from the Ports page to specify the source of the new cross-connection to
be established
New source Node NE name – enter a string of up to 20 characters to specify the
new source TID if the “newinaid” is in a BLSR protection group. In addition the
special character underscore (’_’) and the password characters are allowed.
New path protection group name – enter an alphanumeric user-defind string of
up to 24 characters to specify the name of the new path protection group. This
parameter is applicable if a leg of a path-protected cross-connection is rolled – the
parameter in this case is optional and if not entered the default is used. For non
path-protected cross-connection this parameter does not apply and is omitted.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-39
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To roll the input of a higher-order cross-connection from
one tributary port to another
•
Crossconnection application – enter a numeric value from (0 to 255) to indicate
•
the application for which the cross-connection is used in the context of compound
cross-connection topologies.
Crossconnection number – enter a 12-digit numeric value to identify each
cross-connection leg in a specific compound cross-connection. topology. This
parameter is optional – if not entered, the default is used.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-40
Traffic provisioning tasks
To
delete a cross-connection
...................................................................................................................................................................................................................................
When to use
Use this task to delete a cross-connection in the NE.
Important! In the standard way of operation it is not necessary and not
recommended to delete cross-connections separately in the network elements.
Lucent OMS deletes the cross-connections automatically with the deletion of
network connections.
The “{modifier}” indicates the cross-connection “rate” of the tributary for which the
command is applied to. There is no difference if the “rate” is specified as a SONET
rate or as an SDH-rate for the deletion of the cross-connection
Related information
For a more detailed explanation, please refer to the description of the
DEL-CRS-{modifier} command in the LambdaUnite ® MSS Operations System
Engineering Guide.
For lower-order cross-connections {modifier} select:
•
LOVT1, LOVC3, or LOVC12.
For higher-order cross-connections {modifier} select:
•
•
STS1, STS12, STS192, STS3, or STS48,
VC3, VC4, VC416C, VC44C, or VC464C.
CAUTION
Service-disruption hazard
Deletion of a cross-connection may be traffic affecting.
Before starting to delete a cross-connections parameters, ensure that it is not in use.
The traffic provided on the respective path must have previously been removed (for
example rerouted to another path) before deleting any of the cross-connections
included in that path.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-41
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To delete a cross-connection
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
In
In
In
In
the
the
the
the
NE type field, select a type of NE (if not already present).
NE name field, select the name of the target NE (if not already present).
Category field, select Cross-connections.
Function field, select:
Delete Cross-connection Low Order {layer}, where {layer}
•
VT1.5, VC-3, or VC-12.
Delete Cross-connection {layer}, where {layer}
• STS-1, STS-12c, STS-192c, STS-3c, or STS-48c,
• VC-3, VC-4, VC-4-16c, VC-4-4c, or VC-4-64c.
5. Click Go.
Result: The Delete Cross-connection Low Order {layer} page respective the
Delete Cross-connection {layer} page depending on the selection of the
corresponding {layer} of item 4 of this step is displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
•
Input port identifier – enter either a low order logical port identifier or only a
logical port identifier or copy the respective logical port identifier from the Ports
page to specify the source of the cross-connection.
Output port identifier – enter either a low order logical port identifier or only a
logical port identifier or copy the respective logical port identifier from the Ports
page to specify the tributary which is the sink of the cross-connection.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-42
Traffic provisioning tasks
•
•
To delete a cross-connection
Crossconnection topology – select either a single parameter 1 way, 2 way, or
1 way path protected to specify the topology of the cross-connection to be
established.
Protection leg input port ID – enter either a low order logical port identifier or
only a logical port identifier or copy the respective logical port identifier from the
Ports page to specify the source of the protection leg. This parameter is applicable
to path protected cross-connections only.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-43
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To
retrieve ONNS to UPSR/SNCP constructs
...................................................................................................................................................................................................................................
When to use
Use this task to retrieve ONNS to UPSR/SNCP constructs.
Related information
For a more detailed explanation, please refer to the description of the RTRV-OUC
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Cross-connections.
In the Function field, select Retrieve ONNS to UPSR/SNCP Constructs,
Click Go.
Result: The Retrieve ONNS to UPSR/SNCP Constructs is displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
Working port identifier – enter a port identifier or copy the port identifier from
the Ports page to specify the working tributary of the OUC.
•
OUC directionality – enter either a single parameter Bidirectional, Unidirectional
add, or Unidirectional drop to specify the directionality of the OUC.
...................................................................................................................................................................................................
4
Click Submit.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-44
Traffic provisioning tasks
To retrieve ONNS to UPSR/SNCP constructs
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
...................................................................................................................................................................................................
5
The output parameters for this function are:
•
•
•
wrk_aid – working tributary access identifier
Specifies the working tributary of the OUC.
prt_aid – protection tributary access identifier
Specifies the protection tributary of the OUC.
ouc_dir – OUC directionality
Specifies the directionality of the OUC.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-45
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To
add an ONNS to UPSR/SNCP construct
...................................................................................................................................................................................................................................
When to use
Use this task to add an ONNS to UPSR/SNCP construct.
Important! In the standard way of operation it is not necessary and not
recommended to add cross-connections separately in the network elements. Lucent
OMS creates the necessary cross-connections automatically with the
implementation of network connections.
Related information
For a more detailed explanation, please refer to the description of the ENT-OUC
command in the LambdaUnite ® MSS Operations System Engineering Guide.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1.
2.
3.
4.
5.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of the target NE (if not already present).
In the Category field, select Cross-connections.
In the Function field, select Enter ONNS to UPSR/SNCP Constructs,
Click Go.
Result: The Enter ONNS to UPSR/SNCP Constructs page is displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
•
Working port identifier – enter a port identifier or copy the port identifier from
the Ports page to specify the working tributary of the OUC.
Protection port identifier – enter a port identifier or copy the port identifier from
the Ports page to specify the protection tributary of the OUC.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-46
Traffic provisioning tasks
•
•
•
•
•
•
To add an ONNS to UPSR/SNCP construct
OUC directionality – select Bidirectional, Unidirectional add, or Unidirectional
drop to specify the directionality of the OUC.
Hold off timer (msec) – enter either a numeric value from 0 ms to 99 ms in 1 ms
step increments or a value from 100 to 10000 ms in 100 ms step increments to
specify the value of the hold-off timer to specify the hold-off time for automatic
protection switching used by the protection state machine of the path protection
groups created via OUC creation.
Revertive mode enable – select Enable or Disable to specify whether revertive or
non-revertive mode is used as operation mode of the protection groups created via
OUC creation. “Enable” is used if the protection operates in revertive mode,
“Disable” is used if the protection operates in non-revertive mode.
SNCP Type – select SNCI, SNCN, or Not applicable to specify the type of the path
protection related to switch criteria used by the protection state machine of the path
protection groups created via OUC creation.
Wait to restore time (min) – enter a numeric value from 0 min. to 60 min. to
specify wait-to-restore time used by the protection state machine operating in
revertive mode of the path protection groups created via OUC creation.
Crossconnection application – enter a numeric value from 0 to 255 to indicate
the application for which the cross-connection is used in the context of compound
cross-connection topologies.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-47
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To
delete an ONNS to UPSR/SNCP construct
...................................................................................................................................................................................................................................
When to use
Use this task to delete an ONNS to UPSR/SCCP construct.
Important! In the standard way of operation it is not necessary and not
recommended to delete cross-connections separately in the network elements.
Lucent OMS deletes the cross-connections automatically with the deletion of
network connections.
Related information
For a more detailed explanation, please refer to the description of the DEL-OUC
command in the LambdaUnite ® MSS Operations System Engineering Guide.
CAUTION
Service-disruption hazard
Deletion of a cross-connection may be traffic affecting.
Before starting to delete a cross-connection, make sure that it is not in use. The traffic
provided on the respective path must have previously been removed (for example
rerouted to another path) before deleting any of the cross-connections included in that
path.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → NE Management
Functions.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Session → NE Management
Functions.
Result: The NE Management Functions page is displayed.
...................................................................................................................................................................................................
2
Do the following:
1. In the NE type field, select a type of NE (if not already present).
2. In the NE name field, select the name of the target NE (if not already present).
3. In the Category field, select Cross-connections.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-48
Traffic provisioning tasks
To delete an ONNS to UPSR/SNCP construct
4. In the Function field, select Delete ONNS to UPSR/SNCP Constructs,
5. Click Go.
Result: The Delete ONNS to UPSR/SNCP Constructs is displayed.
...................................................................................................................................................................................................
3
Change the entries or selections for any modifiable fields that you wish to update.
•
•
Working port identifier – enter a port identifier or copy the port identifier from
the Ports page to specify the working tributary of the OUC.
OUC directionality – enter a single parameter Bidirectional, Unidirectional add, or
Unidirectional dropp to specify the directionality of the OUC to be deleted.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the NE Management Functions page. The bottom panel of the NE
Management Functions page now shows the network element’s response to the
submitted function.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-49
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
Provisioning of path protection groups (SNCP,
UPSR)
To
view a list of path protection groups (SNCP, UPSR)
...................................................................................................................................................................................................................................
When to use
Use this task to view a list of path protection groups.
LambdaUnite ® MSS supports both, SONET and SDH path protection features:
•
•
SDH: subnetwork connection protection (SNCP)
SONET: unidirectional path-switched ring (UPSR)
Lucent OMS displays the settings and options for one network type at a time. To
switch between the SDH flavor and the SONET flavor of the user interface, use the
respective options in My Preferences → Preferences → Application Preferences
→ Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → Protection
Groups.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1.
2.
3.
4.
5.
6.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group name field, type the protection group name (optional).
In the Protection group type field, select SNCP or UPSR, respectively.
In the Rate field, select the port rate (optional). The default selection is All.
Click Search.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-50
Traffic provisioning tasks
To view a list of path protection groups (SNCP, UPSR)
Result: The Protection Groups page is populated with a list of path protection
groups in the NE that meet your search criteria.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-51
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To
modify a path protection group (SNCP, UPSR)
...................................................................................................................................................................................................................................
When to use
Use this task to modify a path protection group.
LambdaUnite ® MSS supports both, SONET and SDH path protection features:
•
•
SDH: subnetwork connection protection (SNCP)
SONET: unidirectional path-switched ring (UPSR)
Lucent OMS displays the settings and options for one network type at a time. To
switch between the SDH flavor and the SONET flavor of the user interface, use the
respective options in My Preferences → Preferences → Application Preferences
→ Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path:
Network Elements → Protection Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1. In the NE type field, select a type of NE (if not already present).
2. In the NE name field, select the name of a target NE (if not already present).
3. In the Protection group name field, type the protection group name (optional).
4. In the Protection group type field, select SNCP or UPSR, respectively.
5. In the Rate field, select the port rate (optional). The default selection is All.
6. Click Search.
Result: The Protection groups page is populated with a list of protection groups
in the NE that meet your search criteria.
...................................................................................................................................................................................................
3
Click the radio button next to the path protection group you wish to modify. From the
Go menu, select Modify protection group and click Go.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-52
Traffic provisioning tasks
To modify a path protection group (SNCP, UPSR)
Result: The Protection group general information page is displayed.
...................................................................................................................................................................................................
4
Change the entries or selections for any modifiable fields that you wish to update.
•
•
•
•
•
Path protection group name – enter a text string with 1 to 24 characters to
specify the path protection group name. This parameter is only used with VC-4
applications.
Wait to restore time (Minute) – enter a value from 0 min. to 60 min. in 1 min.
increments to specify the wait-to-restore time used in the revertive mode. If the
revertive mode is set to “Disabled”, this field is not available.
Revertive mode – select Enabled or Disabled.
Holdoff timer (Milli.Sec) – enter a value to specify the hold-off time for automatic
protection switching used by the protection state machine.
– VC-12, LO-VC-3, VT1.5: from 0 to 100 ms in 25 ms increments, or from 100
to 10000 ms in 100 ms increments
– HO-VC-3, VC-4, STS- : from 0 to 100 ms in 1 ms increments, or from 100 to
10000 ms in 100 ms increments
SNC protection type – select SNCI, SNCP, or Not Applicable to specify the type
of the path protection.
...................................................................................................................................................................................................
5
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Modify Protection Group page, and the SNCP protection group is
modified.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-53
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To
operate a path protection group switch (SNCP, UPSR)
...................................................................................................................................................................................................................................
When to use
Use this task to operate a path protection group switch.
LambdaUnite ® MSS supports both, SONET and SDH path protection features:
•
•
SDH: subnetwork connection protection (SNCP)
SONET: unidirectional path-switched ring (UPSR)
Lucent OMS displays the settings and options for one network type at a time. To
switch between the SDH flavor and the SONET flavor of the user interface, use the
respective options in My Preferences → Preferences → Application Preferences
→ Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path:
Network Elements → Protection Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1. In the NE type field, select a type of NE (if not already present).
2. In the NE name field, select the name of a target NE (if not already present).
3. In the Protection group name field, type the protection group name (optional).
4. In the Protection group type field, select SNCP or UPSR, respectively.
5. In the Rate field, select the port rate (optional). The default selection is All.
6. Click Search.
Result: The Protection Groups page is populated with a list of path protection
groups in the NE that meet your search criteria.
...................................................................................................................................................................................................
3
Click the radio button next to the path protection group you wish to execute a
protection switch. From the Go menu, select Operate protection switch and click Go.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-54
Traffic provisioning tasks
To operate a path protection group switch (SNCP, UPSR)
Result: The Operate Protection Switch page is displayed.
...................................................................................................................................................................................................
4
CAUTION
Service-disruption hazard
A forced switch to a faulty section or lockout of protection could cause a traffic
interruption.
Perform a forced switch only to a section which is working fault-free.
From the Switch Operation menu, select the switch command you wish to execute:
Manual switch{, Forced switch{, Lockout, or Clear.
...................................................................................................................................................................................................
5
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Protection Switch page, and the protection switch is executed.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-55
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To operate an SNCP VC-4 protection group switch on
constituent
members
...................................................................................................................................................................................................................................
When to use
Use this task to view and/or operate an subnetwork connection protection (SNCP)
VC-4 protection group switch on constituent members (manual to working).
Before you begin
Make sure that the SDH flavor of the management system user interface is active. To
change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path:
Network Elements → Protection Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1.
2.
3.
4.
5.
6.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group name field, type the protection group name (optional).
In the Protection group type field, select SNCP.
In the Rate field, select VC-4, VC-4-4c, VC-4-16c, or VC-4-64c.
Click Search.
Result: The Protection Groups page is populated with a list of protection groups
in the NE that meet your search criteria.
...................................................................................................................................................................................................
3
Click the radio button next to the SNCP VC-4 protection group you wish to view
and/or execute a protection switch. From the Go menu, select View/Operate
Protection Switch On Constituent Members and click Go.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-56
Traffic provisioning tasks
To operate an SNCP VC-4 protection group switch on
constituent members
Result: The Constituent Member Protection Groups page is displayed.
...................................................................................................................................................................................................
4
CAUTION
Service-disruption hazard
A forced switch to a faulty section or lockout of protection could cause a traffic
interruption.
Perform a forced switch only to a section which is working fault-free.
Click the radio button next to the constituent member protection group you wish
execute a protection switch. From the Go menu, select the desired switch command
Manual switch{, Forced switch{, Lockout, or Clear and click Go.
Result: A confirmation window is displayed asking you to confirm the protection
switch.
...................................................................................................................................................................................................
5
Click Yes.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Constituent Member Protection Groups page, and the constituent
member protection group switch is executed.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-57
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
Provisioning of MSP protection groups
To
view a list of 1+1 or 1x1 MSP protection groups
...................................................................................................................................................................................................................................
When to use
Use this task to view a list of 1+1 or 1x1 multiplex section protection (MSP)
protection groups.
Before you begin
Make sure that the SDH flavor of the management system user interface is active. To
change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → Protection
Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1.
2.
3.
4.
5.
6.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group name field, type the protection group name (optional).
In the Protection group type field, select 1+1 MSP or 1x1 MSP.
In the Rate field, select the port rate (optional). The default selection is All.
Click Search.
Result: The Protection Groups page is populated with a list of protection groups
in the NE that meet your search criteria.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-58
Traffic provisioning tasks
To
add a 1+1 MSP protection group
...................................................................................................................................................................................................................................
When to use
Use this task to add a 1+1 multiplex section protection (MSP) protection group in an
NE. To prepare a fully functional protected multiplex section, a matching MSP
protection group has to be established in the NE on the opposite end of the multiplex
section as well. After the MSP protection groups have been set up on both sides, the
protected multiplex section can be added as a network connection.
Before you begin
Make sure that the SDH flavor of the management system user interface is active. To
change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → Protection
Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Click on the New tool in the toolbar.
Result: The Add Protection Group page is displayed.
...................................................................................................................................................................................................
3
Do the following:
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group type field, select 1+1 MSP.
In the Rate field, select STM-1, STM-4, STM-16, or STM-64. When the rate has
been selected, the panel Protection group parameters opens.
5. In the Protection group name field, enter a number between 001 and 999.
6. In the Working field, select a working port AID. If not selectable, this parameter is
unavailable. If the APS protocol (item 8) is set to “Optimized”, the field name
changes to Primary.
1.
2.
3.
4.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-59
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To add a 1+1 MSP protection group
7. In the Protection field, select a protection port AID. If not selectable, this
parameter is unavailable. If the APS protocol (item 8) is set to “Optimized”, the
field name changes to Secondary.
8. In the APS protocol field, select Bidirectional, Unidirectional, or Optimized.
9. In the Revertive mode field, select Enabled or Disabled. If the APS protocol
(item 8) is set to “Optimized”, this field is unavailable.
10. In the Wait to restore time field, select a value from 0 to 60 min. in 1 step
increments to specify the wait-to-restore time used in the revertive mode. If the
Wait to restore time (item 9) is “Disabled”, this field is unavailable.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Add Protection Group page, and the MSP protection group is
added.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-60
Traffic provisioning tasks
To
add a 1x1 MSP protection group
...................................................................................................................................................................................................................................
When to use
Use this task to add a 1x1 multiplex section protection (MSP) protection group in an
NE. To prepare a fully functional protected multiplex section, a matching MSP
protection group has to be established in the NE on the opposite end of the multiplex
section as well. After the MSP protection groups have been set up on both sides, the
protected multiplex section can be added as a network connection.
Before you begin
Make sure that the SDH flavor of the management system user interface is active. To
change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → Protection
Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Click on the New tool in the toolbar.
Result: The Add Protection Group page is displayed.
...................................................................................................................................................................................................
3
Do the following:
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group type field, select 1x1 MSP.
In the Rate field, select STM-1, STM-4, STM-16, or STM-64. When the rate has
been selected, the panel Protection group parameters opens.
5. In the Protection group name field, enter a number between 001 and 999.
6. In the Working field, select a working port AID. If not selectable, this parameter is
unavailable.
1.
2.
3.
4.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-61
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To add a 1x1 MSP protection group
7. In the Protection field, select a protection port AID. If not selectable, this
parameter is unavailable.
8. In the APS protocol field, leave the default selection (Bidirectional) unchanged.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Add Protection Group page, and the MSP protection group is
added.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-62
Traffic provisioning tasks
To
modify a 1+1 or 1x1 MSP protection group
...................................................................................................................................................................................................................................
When to use
Use this task to modify a 1+1 or 1x1 multiplex section protection (MSP) protection
group.
Before you begin
Make sure that the SDH flavor of the management system user interface is active. To
change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path:
Network Elements → Protection Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1.
2.
3.
4.
5.
6.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group name field, type the protection group name (optional).
In the Protection group type field, select 1+1 MSP or 1x1 MSP.
In the Rate field, select the port rate (optional). The default selection is All.
Click Search.
Result: The Protection Groups page is populated with a list of protection groups
in the NE that meet your search criteria.
...................................................................................................................................................................................................
3
Click the radio button next to the MSP protection group you wish to modify. From the
Go menu, select Modify protection group and click Go.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-63
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To modify a 1+1 or 1x1 MSP protection group
Result: The Modify Protection Group page is displayed.
...................................................................................................................................................................................................
4
Change the entries or selections for any modifiable fields that you wish to update.
•
•
•
•
Wait to restore time (Minute) – select a value from 0 to 60 min. in 1 step
increments to specify the wait-to-restore time used in the revertive mode. If the
Revertive mode field selection is “Disabled”, this field is unavailable.
Alarm severity assignment profile – enter a string with 1 to 24 characters to
specify a pre-defined alarm severity assignment profile (ASAP) to be used for the
protection group in question. An ASAP is a list of alarms which can occur in a
network element and which each have an alarm severity assigned.
DCC line/MS protection mode – select Enabled or Disabled to specify whether
the line/MS DCC channel is switched as part of the line/MS protection group.
DCC section/RS protection mode – select Enabled or Disabled to specif,
whether the section/RS DCC channel is switched as part of the line/MS protection
group.
...................................................................................................................................................................................................
5
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Modify Protection Group page, and the MSP protection group is
modified.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-64
Traffic provisioning tasks
To
delete a 1+1 or 1x1 MSP protection group
...................................................................................................................................................................................................................................
When to use
Use this task to delete a 1+1 or 1x1 multiplex section protection (MSP) protection
group.
Before you begin
Make sure that the SDH flavor of the management system user interface is active. To
change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path:
Network Elements → Protection Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1.
2.
3.
4.
5.
6.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group name field, type the protection group name (optional).
In the Protection group type field, select 1+1 MSP or 1x1 MSP.
In the Rate field, select the port rate (optional). The default selection is All.
Click Search.
Result: The Protection Groups page is populated with a list of protection groups
in the NE that meet your search criteria.
...................................................................................................................................................................................................
3
CAUTION
Service-disruption hazard
Deletion of a protection could cause a traffic interruption.
Click the radio button next to the MSP protection group you wish to delete. From the
Go menu, select Delete protection group and click Go.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-65
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To delete a 1+1 or 1x1 MSP protection group
Result: A confirmation window is displayed asking you to confirm the deletion.
...................................................................................................................................................................................................
4
Click Yes.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Protection Groups page, and the protection group is deleted.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-66
Traffic provisioning tasks
To
operate an MSP protection switch
...................................................................................................................................................................................................................................
When to use
Use this task to execute a multiplex section protection (MSP) protection switch.
Before you begin
Make sure that the SDH flavor of the management system user interface is active. To
change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path:
Network Elements → Protection Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1.
2.
3.
4.
5.
6.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group name field, type the protection group name (optional).
In the Protection group type field, select 1+1 MSP or 1x1 MSP.
In the Rate field, select the port rate (optional). The default selection is All.
Click Search.
Result: The Protection Groups page is populated with a list of protection groups
in the NE that meet your search criteria.
...................................................................................................................................................................................................
3
Click the radio button next to the MSP protection group for which you wish to execute
a protection switch. From the Go menu, select Operate protection switch and click
Go.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-67
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To operate an MSP protection switch
Result: The Protection Switch page is displayed.
...................................................................................................................................................................................................
4
CAUTION
Service-disruption hazard
A forced switch to a faulty section or lockout of protection could cause a traffic
interruption.
Perform a forced switch only to a section which is working fault-free.
From the Switch Operation menu, select the switch command you wish to execute
(Manual switch{, Forced switch{, Lockout, or Clear).
...................................................................................................................................................................................................
5
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Protection Switch page, and the MSP protection switch is executed.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-68
Traffic provisioning tasks
Provisioning of APS protection groups
To
view a list of 1+1 or 1x1 APS protection groups
...................................................................................................................................................................................................................................
When to use
Use this task to view a list of 1+1 or 1x1 automatic protection switch (APS) protection
groups.
Before you begin
Make sure that the SONET flavor of the management system user interface is active.
To change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → Protection
Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1.
2.
3.
4.
5.
6.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group name field, type the protection group name (optional).
In the Protection group type field, select 1+1 APS or 1x1 APS.
In the Rate field, select the port rate (optional). The default selection is All.
Click Search.
Result: The Protection Groups page is populated with a list of protection groups
in the NE that meet your search criteria.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-69
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To
add a 1+1 APS protection group
...................................................................................................................................................................................................................................
When to use
Use this task to add a 1+1 automatic protection switch (APS) protection group in an
NE. To prepare a fully functional protected multiplex section, a matching APS
protection group has to be established in the NE on the opposite end of the multiplex
section as well. After the APS protection groups have been set up on both sides, the
protected multiplex section can be added as a network connection.
Before you begin
Make sure that the SONET flavor of the management system user interface is active.
To change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → Protection
Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Click on the New tool in the toolbar.
Result: The Add Protection Group page is displayed.
...................................................................................................................................................................................................
3
Do the following:
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group type field, select 1+1 APS.
In the Rate field, select OC-3, OC-12, OC-48, or OC-192. When the rate has been
selected, the panel Protection group parameters opens.
5. In the Protection group name field, enter a number between 001 and 999.
6. In the Working field, select a working port AID. If not selectable, this parameter is
unavailable. If the APS protocol (item 8) is set to “Optimized”, the field name
changes to Primary.
1.
2.
3.
4.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-70
Traffic provisioning tasks
To add a 1+1 APS protection group
7. In the Protection field, select a protection port AID. If not selectable, this
parameter is unavailable. If the APS protocol (item 8) is set to “Optimized”, the
field name changes to Secondary.
8. In the APS protocol field, select Bidirectional, Unidirectional, or Optimized.
9. In the Revertive mode field, select Enabled or Disabled. If the APS protocol
(item 8) is set to “Optimized”, this field is unavailable.
10. In the Wait to restore time field, select a value from 0 to 60 min. in 1 step
increments to specify the wait-to-restore time used in the revertive mode. If the
Wait to restore time (item 9) is “Disabled”, this field is unavailable.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Add Protection Group page, and the APS protection group is added.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-71
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To
add a 1x1 APS protection group
...................................................................................................................................................................................................................................
When to use
Use this task to add a 1x1 automatic protection switch (APS) protection group in an
NE. To prepare a fully functional protected multiplex section, a matching APS
protection group has to be established in the NE on the opposite end of the multiplex
section as well. After the APS protection groups have been set up on both sides, the
protected multiplex section can be added as a network connection.
Before you begin
Make sure that the SONET flavor of the management system user interface is active.
To change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → Protection
Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Click on the New tool in the toolbar.
Result: The Add Protection Group page is displayed.
...................................................................................................................................................................................................
3
Do the following:
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group type field, select 1x1 APS.
In the Rate field, select OC-3, OC-12, OC-48, or OC-192. When the rate has been
selected, the panel Protection group parameters opens.
5. In the Protection group name field, enter a number between 001 and 999.
6. In the Working field, select the working port AID. If not selectable, this parameter
is unavailable.
1.
2.
3.
4.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-72
Traffic provisioning tasks
To add a 1x1 APS protection group
7. In the Protection field, select a protection port AID. If not selectable, this
parameter is unavailable.
8. In the APS protocol field, leave the default selection (Bidirectional) unchanged.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Add Protection Group page, and the APS protection group is added.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-73
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To
modify a 1+1 or 1x1 APS protection group
...................................................................................................................................................................................................................................
When to use
Use this task to modify a 1+1 or 1x1 automatic protection switch (APS) protection
group.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path:
Network Elements → Protection Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1.
2.
3.
4.
5.
6.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group name field, type the protection group name (optional).
In the Protection group type field, select 1+1 APS or 1x1 APS.
In the Rate field, select the port rate (optional). The default selection is All.
Click Search.
Result: The Protection Groups page is populated with a list of protection groups
in the NE that meet your search criteria.
...................................................................................................................................................................................................
3
Click the radio button next to the APS protection group you wish to modify. From the
Go menu, select Modify protection group and click Go.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-74
Traffic provisioning tasks
To modify a 1+1 or 1x1 APS protection group
Result: The Modify Protection Group page is displayed.
...................................................................................................................................................................................................
4
Change the entries or selections for any modifiable fields that you wish to update.
•
•
•
•
Wait to restore time (Minute) – select a value from 0 to 60 min. in 1 step
increments to specify the wait-to-restore time used in the revertive mode. If the
Revertive mode field selection is “Disabled”, this field is unavailable.
Alarm severity assignment profile – enter a string with 1 to 24 characters to
specify a pre-defined alarm severity assignment profile (ASAP) to be used for the
“protection group” in question. An ASAP is a list of alarms which can occur in a
network element and which each have an alarm severity assigned.
DCC line/MS protection mode – select Enabled or Disabled to specify whether
the line/MS DCC channel is switched as part of the line/MS protection group.
DCC section/RS protection mode – select Enabled or Disabled to specif,
whether the section/RS DCC channel is switched as part of the line/MS protection
group.
...................................................................................................................................................................................................
5
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Modify Protection Group page, and the APS protection group is
modified.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-75
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To
delete a 1+1 or 1x1 APS protection group
...................................................................................................................................................................................................................................
When to use
Use this task to delete a 1+1 or 1x1 automatic protection switch (APS) protection
group.
Before you begin
Make sure that the SONET flavor of the management system user interface is active.
To change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path:
Network Elements → Protection Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1.
2.
3.
4.
5.
6.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group name field, type the protection group name (optional).
In the Protection group type field, select 1+1 APS or 1x1 APS.
In the Rate field, select the port rate (optional). The default selection is All.
Click Search.
Result: The Protection Groups page is populated with a list of protection groups
in the NE that meet your search criteria.
...................................................................................................................................................................................................
3
CAUTION
Service-disruption hazard
Deletion of a protection could cause a traffic interruption.
Click the radio button next to the APS protection group you wish to delete. From the
Go menu, select Delete protection group and click Go.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-76
Traffic provisioning tasks
To delete a 1+1 or 1x1 APS protection group
Result: A confirmation window is displayed asking you to confirm the deletion.
...................................................................................................................................................................................................
4
Click Yes.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Protection Groups page, and the protection group is deleted.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-77
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To
operate an APS protection switch
...................................................................................................................................................................................................................................
When to use
Use this task to execute an automatic protection switch (APS) protection group switch.
Before you begin
Make sure that the SONET flavor of the management system user interface is active.
To change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path:
Network Elements → Protection Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1.
2.
3.
4.
5.
6.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group name field, type the protection group name (optional).
In the Protection group type field, select 1+1 APS or 1x1 APS.
In the Rate field, select the port rate (optional). The default selection is All.
Click Search.
Result: The Protection Groups page is populated with a list of protection groups
in the NE that meet your search criteria.
...................................................................................................................................................................................................
3
Click the radio button next to the APS protection group for which you wish to execute
a protection switch. From the Go menu, select Operate protection switch and click
Go.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-78
Traffic provisioning tasks
To operate an APS protection switch
Result: The Protection Switch page is displayed.
...................................................................................................................................................................................................
4
CAUTION
Service-disruption hazard
A forced switch to a faulty section or lockout of protection could cause a traffic
interruption.
Perform a forced switch only to a section which is working fault-free.
From the Switch Operation menu, select the switch command you wish to execute
(Manual switch{, Forced switch{, Lockout, or Clear).
...................................................................................................................................................................................................
5
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Protection Switch page, and the APS protection switch is executed.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-79
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
Provisioning of MS-SPRing protection groups
To
view a list of 2-fiber MS-SPRing protection groups
...................................................................................................................................................................................................................................
When to use
Use this task to view a list of 2-fiber multiplex section-shared protection ring
(MS-SPRing) protection groups.
Before you begin
Make sure that the SDH flavor of the management system user interface is active. To
change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → Protection
Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1.
2.
3.
4.
5.
6.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group name field, type the protection group name (optional).
In the Protection group type field, select 2F MSSPRING.
In the Rate field, select the port rate (optional). The default selection is All.
Click Search.
Result: The Protection Groups page is populated with a list of protection groups
in the NE that meet your search criteria.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-80
Traffic provisioning tasks
To
add a 2-fiber MS-SPRing protection group
...................................................................................................................................................................................................................................
When to use
Use this task to add a 2-fiber multiplex section-shared protection ring (MS-SPRing)
protection group in an NE.
A requirement for this kind of protection is an enabled MS DCC on both line sides in
each NE. To prepare a fully functional 2-fiber multiplex section-shared protection ring,
a matching MS-SPRing protection group has to be established in all NEs of the ring
configuration. After the MS-SPRing protection groups have been set up on all NEs, the
management system automatically add the ring without any user intervention when
certain conditions are met. When the ring is automatically added, the ring is added to
the database, and the Network Map is updated with the new ring.
Before you begin
Make sure that the SDH flavor of the management system user interface is active. To
change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → Protection
Groups.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Click on the New tool in the toolbar.
Result: The Add Protection Group page is displayed.
...................................................................................................................................................................................................
3
Do the following:
1.
2.
3.
4.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group type field, select 2F MSSPRING.
In the Rate field, select STM-16, STM-64, or STM-256. When the rate has been
selected, the Protection group parameters panel opens.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-81
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To add a 2-fiber MS-SPRing protection group
5. In the Protection group name field, enter a number between 001 and 999.
6. In the Ring ID field, enter up to 15 alphanumeric and/or special characters (for
example “~{Ring25}”).
7. In the East field, select the east port AID. If not selectable, this parameter is
unavailable.
8. In the West field, select the west port AID. If not selectable, this parameter is
unavailable.
9. In the Auto ring discovery field, select Enabled or Disabled.
10. In the Automatic squelch map calculation field, select Enabled or Disabled.
11. In the Ring circuit alarm mode field, select Enabled or Disabled.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Add Protection Group page, and the 2-fiber MS-SPRing protection
group is added.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-82
Traffic provisioning tasks
To
modify a 2-fiber MS-SPRing protection group
...................................................................................................................................................................................................................................
When to use
Use this task to modify a 2-fiber multiplex section-shared protection ring (MS-SPRing)
protection group.
Before you begin
Make sure that the SDH flavor of the management system user interface is active. To
change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path:
Network Elements → Protection Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1.
2.
3.
4.
5.
6.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group name field, type the protection group name (optional).
In the Protection group type field, select 2F MSSPRING.
In the Rate field, select the port rate (optional). The default selection is All.
Click Search.
Result: The Protection groups page is populated with a list of protection groups
in the NE that meet your search criteria.
...................................................................................................................................................................................................
3
Click the radio button next to the MS-SPRing protection group you wish to modify.
From the Go menu, select Modify protection group and click Go.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-83
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To modify a 2-fiber MS-SPRing protection group
Result: The Modify Protection Group page is displayed.
...................................................................................................................................................................................................
4
Change the entries or selections for any of the fields that are modifiable:
•
•
•
•
•
•
Ring ID – enter a text string with 1 to 15 characters to specify the ring ID.
Wait to restore time (Minute) – select a value from 0 to 12 min. in 1 step
increments or 99 (infinite) to specify the wait-to-restore time for ring switches in
revertive mode.
Alarm severity assignment profile – enter a string with 1 to 24 characters to
specify a pre-defined alarm severity assignment profile (ASAP) to be used for the
protection group in question. An ASAP is a list of alarms which can occur in a
network element and which each have an alarm severity assigned.
Auto ring discovery – select Enabled or Disabled. If this parameter is enabled,
the automatic ring discovery algorithm will assign nodeID values to each node in
the ring and construct the necessary ring map information. All nodes in the ring
must be Lucent Technologies network elements. If disabled, the user will assign the
Node ID value manually.
Automatic squelch map calculation – select Enabled or Disabled. If this
parameter is enabled, the automatic squelch map calculation is switched on. If
disabled, the function is switched off. If the rate of the protection group is
STM-256, this field is not available.
Ring circuit alarm mode – select Enabled or Disabled to enable or disable ring
circuit alarms for the local 2-fiber MS-SPRing protection group. If the rate of the
protection group is STM-256, this field is not available.
...................................................................................................................................................................................................
5
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Modify Protection Group page, and the 2-fiber MS-SPRing
protection group is modified.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-84
Traffic provisioning tasks
To
delete a 2-fiber MS-SPRing protection group
...................................................................................................................................................................................................................................
When to use
Use this task to delete a 2-fiber multiplex section-shared protection ring (MS-SPRing)
protection group.
Before you begin
Make sure that the SDH flavor of the management system user interface is active. To
change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path:
Network Elements → Protection Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1.
2.
3.
4.
5.
6.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group name field, type the protection group name (optional).
In the Protection group type field, select 2F MSSPRING.
In the Rate field, select the port rate (optional). The default selection is All.
Click Search.
Result: The Protection Groups page is populated with a list of protection groups
in the NE that meet your search criteria.
...................................................................................................................................................................................................
3
CAUTION
Service-disruption hazard
Deletion of a protection could cause a traffic interruption.
Click the radio button next to the MS-SPRing protection group you wish to delete.
From the Go menu, select Delete protection group and click Go.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-85
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To delete a 2-fiber MS-SPRing protection group
Result: A confirmation window is displayed asking you to confirm the deletion.
...................................................................................................................................................................................................
4
Click Yes.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Protection Groups page, and the MS-SPRing protection group is
deleted.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-86
Traffic provisioning tasks
To
operate a 2-fiber MS-SPRing protection switch
...................................................................................................................................................................................................................................
When to use
Use this task to execute a 2-fiber multiplex section-shared protection ring (MS-SPRing)
protection switch (manual to working).
Before you begin
Make sure that the SDH flavor of the management system user interface is active. To
change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path:
Network Elements → Protection Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1.
2.
3.
4.
5.
6.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group name field, type the protection group name (optional).
In the Protection group type field, select 2F MSSPRING.
In the Rate field, select the port rate (optional). The default selection is All.
Click Search.
Result: The Protection Groups page is populated with a list of protection groups
in the NE that meet your search criteria.
...................................................................................................................................................................................................
3
Click the radio button next to the MS-SPRing protection group for which you wish to
execute a protection switch. From the Go menu, select Operate protection switch and
click Go.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-87
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To operate a 2-fiber MS-SPRing protection switch
Result: The Protection Switch page is displayed.
...................................................................................................................................................................................................
CAUTION
4
Service-disruption hazard
A forced switch to a faulty section or lockout of protection could cause a traffic
interruption.
Perform a forced switch only to a section which is working fault-free.
Change the entries or selections for any modifiable fields that you wish to update.
•
•
•
Switch type – select Span or Ring to specify what type of protection switching is
used for the MS-SPRing protection group.
Destination side – select East or West to specify the destination ring side to
which the switch command is to be applied.
Switch operation – select the switch command you wish to execute. Depending on
the selection of the Switch type the following values are possible:
– for switch type “Span”: Lockout or Clear.
– for switch type “Ring”: Forced, Manual, or Clear.
...................................................................................................................................................................................................
5
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Protection Switch page, and the 2-fiber MS-SPRing protection
switch is executed.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-88
Traffic provisioning tasks
To
view a list of 4-fiber MS-SPRing protection groups
...................................................................................................................................................................................................................................
When to use
Use this task to view a list of 4-fiber multiplex section-shared protection ring
(MS-SPRing) protection groups.
Before you begin
Make sure that the SDH flavor of the management system user interface is active. To
change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → Protection
Groups.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1.
2.
3.
4.
5.
6.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group name field, type the protection group name (optional).
In the Protection group type field, select 4F MSSPRING.
In the Rate field, select the port rate (optional). The default selection is All.
Click Search.
Result: The Protection Groups page is populated with a list of protection groups
in the NE that meet your search criteria.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-89
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To
add a 4-fiber MS-SPRing protection group
...................................................................................................................................................................................................................................
When to use
Use this task to add a 4-fiber multiplex section-shared protection ring (MS-SPRing)
protection group in an NE.
A requirement for this kind of protection is an enabled MS DCC on both line sides in
each NE. To prepare a fully functional 2-fiber multiplex section-shared protection ring,
a matching MS-SPRing protection group has to be established in all NEs of the ring
configuration. After the MS-SPRing protection groups have been set up on all NEs, the
management system automatically add the ring without any user intervention when
certain conditions are met. When the ring is automatically added, the ring is added to
the database, and the Network Map is updated with the new ring.
Before you begin
Make sure that the SDH flavor of the management system user interface is active. To
change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → Protection
Groups.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Click on the New tool in the toolbar.
Result: The Add Protection Group page is displayed.
...................................................................................................................................................................................................
3
Do the following:
1.
2.
3.
4.
In
In
In
In
the
the
the
the
NE type field, select a type of NE (if not already present).
NE name field, select the name of a target NE (if not already present).
Protection group type field, select 4F MSSPRING.
Rate field, select STM-16, or STM-64. When the rate has been selected, the
Protection group parameters panel opens.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-90
Traffic provisioning tasks
To add a 4-fiber MS-SPRing protection group
5. In the Protection group name field, enter a number between 001 to 999.
6. In the Ring ID field, enter up to 15 alphanumeric and special characters (for
example “~{Ring25}”).
7. In the East working field, select the east port AID. If not selectable, this parameter
is unavailable.
8. In the East protection field, select the east port AID for protection group. If not
selectable, this parameter is unavailable.
9. In the West field, select the west port AID. If not selectable, this parameter is
unavailable.
10. In the West protection field, select the west port AID for protection group. If not
selectable, this parameter is unavailable.
11. In the Ring protection protocol field the following selections depending on the
Rate selection (item 4) are possible:
• for rate type “STM-16”: Standard, or Transoceanic
• for rate type “STM-64”: Standard, Transoceanic-shortened, or
Transoceanic-TOPEX
12. In the Auto ring discovery field, select Enabled or Disabled.
13. In the Automatic squelch map calculation field, select Enabled or Disabled.
14. In the Ring circuit alarm mode field, select Enabled or Disabled.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Add Protection Group page, and the 4-fiber MS-SPRing protection
group is added.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-91
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To
modify a 4-fiber MS-SPRing protection group
...................................................................................................................................................................................................................................
When to use
Use this task to modify a 4-fiber multiplex section-shared protection ring (MS-SPRing)
protection group.
Before you begin
Make sure that the SDH flavor of the management system user interface is active. To
change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path:
Network Elements → Protection Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1.
2.
3.
4.
5.
6.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group name field, type the protection group name (optional).
In the Protection group type field, select 4F MSSPRING.
In the Rate field, select the port rate (optional). The default selection is All.
Click Search.
Result: The Protection groups page is populated with a list of protection groups
in the NE that meet your search criteria.
...................................................................................................................................................................................................
3
Click the radio button next to the MS-SPRing protection group you wish to modify.
From the Go menu, select Modify protection group and click Go.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-92
Traffic provisioning tasks
To modify a 4-fiber MS-SPRing protection group
Result: The Modify Protection Group page is displayed.
...................................................................................................................................................................................................
4
Change the entries or selections for any modifiable fields that you wish to update.
•
In the Ring protection protocol field the following selections depending on the
Rate selection are possible:
– for rate type “STM-16”: Standard, or Transoceanic
– for rate type “STM-64”: Standard, Transoceanic-shortened, or
Transoceanic-TOPEX
•
•
•
•
•
•
•
New Ring ID – enter a text string with 1 to 15 characters to specify the new ring
identification name.
Wait to restore time (Minute) – select a value from 0 to 12 min. in 1 step
increments or 99 (infinite) to specify the wait-to-restore time for ring switches in
revertive mode.
Auto ring discovery – select Enabled or Disabled. If this parameter is enabled,
the automatic ring discovery algorithm will assign nodeID values to each node in
the ring and construct the necessary ring map information. All nodes in the ring
must be Lucent Technologies network elements. If disabled, the user will assign the
Node ID value manually.
Automatic squelch map calculation – select Enabled or Disabled. If this
parameter is enabled, the automatic squelch map calculation is switched on. If
disabled, the function is switched off.
Ring circuit alarm mode – select Enabled or Disabled to enable or disable ring
circuit alarms for the local 4-fiber MS-SPRing protection group.
Alarm severity assignment profile – enter a string with 1 to 24 characters to
specify a pre-defined alarm severity assignment profile (ASAP) to be used for the
“protection group” in question. An ASAP is a list of alarms which can occur in a
network element and which each have an alarm severity assigned.
Span wait to restore – select a value 0 to 12 min. in 1 step increments or 99
(infinite) to specify the wait to restore time for span switches used by the
protection state machine operating in revertive mode.
...................................................................................................................................................................................................
5
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Modify Protection Group page, and the 4-fiber MS-SPRing
protection group is modified.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-93
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To
delete a 4-fiber MS-SPRing protection group
...................................................................................................................................................................................................................................
When to use
Use this task to delete a 4-fiber multiplex section-shared protection ring (MS-SPRing)
protection group.
Before you begin
Make sure that the SDH flavor of the management system user interface is active. To
change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path:
Network Elements → Protection Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1.
2.
3.
4.
5.
6.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group name field, type the protection group name (optional).
In the Protection group type field, select 4F MSSPRING.
In the Rate field, select the port rate (optional). The default selection is All.
Click Search.
Result: The Protection Groups page is populated with a list of protection groups
in the NE that meet your search criteria.
...................................................................................................................................................................................................
3
CAUTION
Service-disruption hazard
Deletion of a protection could cause a traffic interruption.
Click the radio button next to the MS-SPRing protection group you wish to delete.
From the Go menu, select Delete protection group and click Go.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-94
Traffic provisioning tasks
To delete a 4-fiber MS-SPRing protection group
Result: A confirmation window is displayed asking you to confirm the deletion.
...................................................................................................................................................................................................
4
Click Yes.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Protection Groups page, and the MS-SPRing protection group is
deleted.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-95
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To
operate a 4-fiber MS-SPRing protection switch
...................................................................................................................................................................................................................................
When to use
Use this task to execute a 4-fiber multiplex section-shared protection ring (MS-SPRing)
protection switch (manual to working).
Before you begin
Make sure that the SDH flavor of the management system user interface is active. To
change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path:
Network Elements → Protection Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1.
2.
3.
4.
5.
6.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group name field, type the protection group name (optional).
In the Protection group type field, select 4F MSSPRING.
In the Rate field, select the port rate (optional). The default selection is All.
Click Search.
Result: The Protection Groups page is populated with a list of protection groups
in the NE that meet your search criteria.
...................................................................................................................................................................................................
3
Click the radio button next to the MS-SPRing protection group you wish to execute a
protection switch. From the Go menu, select Operate protection switch and click Go.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-96
Traffic provisioning tasks
To operate a 4-fiber MS-SPRing protection switch
Result: The Protection Switch page is displayed.
...................................................................................................................................................................................................
CAUTION
4
Service-disruption hazard
A forced switch to a faulty section or lockout of protection could cause a traffic
interruption.
Perform a forced switch only to a section which is working fault-free.
Change the entries or selections for any modifiable fields that you wish to update.
•
•
•
Switch type – select Span or Ring to specify what type of protection switching is
used for the MS-SPRing protection group.
Destination side – click the radio button East or West to specify the destination
ring side to which the switch command is to be applied.
Switch operation – select the switch command you wish to execute. Depending on
the selection of the Switch type the following values are possible:
– for switch type “Span”: Forced, Manual, Lockout, or Clear.
– for switch type “Ring”: Forced, Manual, or Clear.
...................................................................................................................................................................................................
5
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Protection Switch page, and the MS-SPRing protection switch is
executed.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-97
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
Provisioning of BLSR protection groups
To
view a list of 2-fiber BLSR protection groups
...................................................................................................................................................................................................................................
When to use
Use this task to view a list of 2-fiber bidirectional line switched ring (BLSR)
protection groups.
Before you begin
Make sure that the SONET flavor of the management system user interface is active.
To change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path: Network Elements → Protection
Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1.
2.
3.
4.
5.
6.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group name field, type the protection group name (optional).
In the Protection group type field, select 2F BLSR.
In the Rate field, select the port rate (optional). The default selection is All.
Click Search.
Result: The Protection Groups page is populated with a list of protection groups
in the NE that meet your search criteria.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-98
Traffic provisioning tasks
To
add a 2-fiber BLSR protection group
...................................................................................................................................................................................................................................
When to use
Use this task to add a 2-fiber bidirectional line switched ring (BLSR) protection group
in an NE.
A requirement for this kind of protection is an enabled MS DCC on both line sides in
each NE. To prepare a fully functional 2-fiber bidirectional line switched ring, a
matching BLSR protection group has to be established in all NEs of the ring
configuration. After the BLSR protection groups have been set up on all NEs, the
management system automatically add the ring without any user intervention when
certain conditions are met. When the ring is automatically added, the ring is added to
the database, and the Network Map is updated with the new ring.
Before you begin
Make sure that the SONET flavor of the management system user interface is active.
To change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → Protection
Groups.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Click on the New tool in the toolbar.
Result: The Add Protection Group page is displayed.
...................................................................................................................................................................................................
3
Do the following:
1.
2.
3.
4.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group type field, select 2F BLSR.
In the Rate field, select OC-48, OC-192, or OC-768. When the rate has been
selected, the Protection group parameters panel opens.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-99
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To add a 2-fiber BLSR protection group
5. In the Protection group name field, enter a number between 001 and 999.
6. In the Ring ID field, enter up to 15 alphanumeric and/or special characters (for
example “~{Ring25}”).
7. In the East field, select the east port AID. If not selectable, this parameter is
unavailable.
8. In the West field, select the west port AID. If not selectable, this parameter is
unavailable.
9. In the Auto ring discovery field, select Enabled or Disabled.
10. In the Automatic squelch map calculation field, select Enabled or Disabled.
11. In the Ring circuit alarm mode field, select Enabled or Disabled.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Add Protection Group page, and the BLSR protection group is
added.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-100
Traffic provisioning tasks
To
modify a 2-fiber BLSR protection group
...................................................................................................................................................................................................................................
When to use
Use this task to modify a 2-fiber bidirectional line switched ring (BLSR) protection
group.
Before you begin
Make sure that the SONET flavor of the management system user interface is active.
To change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path:
Network Elements → Protection Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1.
2.
3.
4.
5.
6.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group name field, type the protection group name (optional).
In the Protection group type field, select 2F BLSR.
In the Rate field, select the port rate (optional). The default selection is All.
Click Search.
Result: The Protection groups page is populated with a list of protection groups
in the NE that meet your search criteria.
...................................................................................................................................................................................................
3
Click the radio button next to the BLSR protection group you wish to modify. From
the Go menu, select Modify protection group and click Go.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-101
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To modify a 2-fiber BLSR protection group
Result: The Modify Protection Group page is displayed.
...................................................................................................................................................................................................
4
Change the entries or selections for any modifiable fields that you wish to update.
•
•
•
•
•
•
Ring ID – enter a text string with 1 to 15 characters to specify the ring ID.
Wait to restore time (Minute) – select a value from 0 min. to 12 min. in 1 min.
step increments or 99 (infinite) to specify the wait-to-restore time for ring switches
in revertive mode.
Alarm severity assignment profile – enter a string with 1 to 24 characters to
specify a predefined alarm severity assignment profile (ASAP) to be used for the
protection group in question. An ASAP is a list of alarms which can occur in a
network element and which each have an alarm severity assigned.
Auto ring discovery – select Enabled or Disabled. If this parameter is enabled,
the automatic ring discovery algorithm will assign node ID values to each node in
the ring and construct the necessary ring map information. All nodes in the ring
must be Lucent Technologies network elements. If disabled, the user will assign the
node ID value manually.
Automatic squelch map calculation – select Enabled or Disabled. If this
parameter is enabled, the automatic squelch map calculation is switched on. If
disabled, the function is switched off. If the rate of the protection group is
“OC-768”, this field is unavailable.
Ring circuit alarm mode – select Enabled or Disabled to enable or disable ring
circuit alarms for the local 2-fiber MS-SPRing protection group. If the rate of the
protection group is “OC-768”, this field is unavailable.
...................................................................................................................................................................................................
5
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Modify Protection Group page, and the 2-fiber BLSR protection
group is modified.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-102
Traffic provisioning tasks
To
delete a 2-fiber BLSR protection group
...................................................................................................................................................................................................................................
When to use
Use this task to delete a 2-fiber bidirectional line switched ring (BLSR) protection
group.
Before you begin
Make sure that the SONET flavor of the management system user interface is active.
To change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path:
Network Elements → Protection Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1.
2.
3.
4.
5.
6.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group name field, type the protection group name (optional).
In the Protection group type field, select 2F BLSR.
In the Rate field, select the port rate (optional). The default selection is All.
Click Search.
Result: The Protection Groups page is populated with a list of protection groups
in the NE that meet your search criteria.
...................................................................................................................................................................................................
3
CAUTION
Service-disruption hazard
Deletion of a protection could cause a traffic interruption.
Click the radio button next to the BLSR protection group you wish to delete. From the
Go menu, select Delete protection group and click Go.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-103
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To delete a 2-fiber BLSR protection group
Result: A confirmation window is displayed asking you to confirm the deletion.
...................................................................................................................................................................................................
4
Click Yes.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Protection Groups page, and the BLSR protection group is deleted.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-104
Traffic provisioning tasks
To
operate a 2-fiber BLSR protection switch
...................................................................................................................................................................................................................................
When to use
Use this task to execute a 2-fiber bidirectional line switched ring (BLSR) protection
switch (manual to working).
Before you begin
Make sure that the SONET flavor of the management system user interface is active.
To change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path:
Network Elements → Protection Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1.
2.
3.
4.
5.
6.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group name field, type the protection group name (optional).
In the Protection group type field, select 2F BLSR.
In the Rate field, select the port rate (optional). The default selection is All.
Click Search.
Result: The Protection Groups page is populated with a list of protection groups
in the NE that meet your search criteria.
...................................................................................................................................................................................................
3
Click the radio button next to the BLSR protection group you wish to execute a
protection switch. From the Go menu, select Operate protection switch and click Go.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-105
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To operate a 2-fiber BLSR protection switch
Result: The Protection Switch page is displayed.
...................................................................................................................................................................................................
CAUTION
4
Service-disruption hazard
A forced switch to a faulty section or lockout of protection could cause a traffic
interruption.
Perform a forced switch only to a section which is working fault-free.
Change the entries or selections for any modifiable fields that you wish to update.
•
•
•
Switch type – select Span or Ring to specify the type of protection switching used
for the BLSR protection group.
Destination side – click the radio button East or West to specify the destination
ring side to which the switch command shall be applied.
Switch operation – select the switch command you wish to execute. Depending on
the selection of the Switch type the following values are possible:
– for switch type “Span”: Lockout or Clear.
– for switch type “Ring”: Forced, Manual, or Clear.
...................................................................................................................................................................................................
5
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Protection Switch page, and the BLSR protection switch is
executed.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-106
Traffic provisioning tasks
To
view a list of 4-fiber BLSR protection groups
...................................................................................................................................................................................................................................
When to use
Use this task to view a list of 4-fiber bidirectional line switched ring (BLSR)
protection groups.
Before you begin
Make sure that the SONET flavor of the management system user interface is active.
To change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → Protection
Groups.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1.
2.
3.
4.
5.
6.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group name field, type the protection group name (optional).
In the Protection group type field, select 4F BLSR.
In the Rate field, select the port rate (optional). The default selection is All.
Click Search.
Result: The Protection Groups page is populated with a list of protection groups
in the NE that meet your search criteria.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-107
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To
add a 4-fiber BLSR protection group
...................................................................................................................................................................................................................................
When to use
Use this task to add a 4-fiber bidirectional line switched ring (BLSR) protection group
in an NE.
A requirement for this kind of protection is an enabled MS DCC on both line sides in
each NE. To prepare a fully functional 4-fiber bidirectional line switched ring, a
matching BLSR protection group has to be established in all NEs of the ring
configuration. After the BLSR protection groups have been set up on all NEs, the
management system automatically add the ring without any user intervention when
certain conditions are met. When the ring is automatically added, the ring is added to
the database, and the Network Map is updated with the new ring.
Before you begin
Make sure that the SONET flavor of the management system user interface is active.
To change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
Use the object links to follow this path: Network Elements → Protection
Groups.
•
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Click on the New tool in the toolbar.
Result: The Add Protection Group page is displayed.
...................................................................................................................................................................................................
3
Do the following:
1.
2.
3.
4.
In
In
In
In
the
the
the
the
NE type field, select a type of NE (if not already present).
NE name field, select the name of a target NE (if not already present).
Protection group type field, select 4F BLSR.
Rate field, select OC-48, or OC-192. When the rate has been selected, the
Protection group parameters panel opens.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-108
Traffic provisioning tasks
To add a 4-fiber BLSR protection group
5. In the Protection group name field, enter a number between 001 to 999.
6. In the Ring ID field, enter up to 15 alphanumeric and special characters (for
example “~{Ring25}”).
7. In the East working field, select the east port AID. If not selectable, this parameter
is unavailable.
8. In the East protection field, select the east port AID for protection group. If not
selectable, this parameter is unavailable.
9. In the West working field, select the west port AID. If not selectable, this
parameter is unavailable.
10. In the West protection field, select the west port AID for protection group. If not
selectable, this parameter is unavailable.
11. In the Ring protection protocol field the following selections depending on the
Rate selection (item 4) are possible:
• for rate type “OC-48”: Standard, or Transoceanic
• for rate type “OC-192”: Standard, Transoceanic-shortened, or
Transoceanic-TOPEX
12. In the Auto ring discovery field, select Enabled or Disabled.
13. In the Automatic squelch map calculation field, select Enabled or Disabled.
14. In the Ring circuit alarm mode field, select Enabled or Disabled.
...................................................................................................................................................................................................
4
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Add Protection Group page, and the BLSR protection group is
added.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-109
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To
modify a 4-fiber BLSR protection group
...................................................................................................................................................................................................................................
When to use
Use this task to modify a 4-fiber bidirectional line switched ring (BLSR) protection
group.
Before you begin
Make sure that the SONET flavor of the management system user interface is active.
To change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path:
Network Elements → Protection Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1.
2.
3.
4.
5.
6.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group name field, type the protection group name (optional).
In the Protection group type field, select 4F BLSR.
In the Rate field, select the port rate (optional). The default selection is All.
Click Search.
Result: The Protection groups page is populated with a list of protection groups
in the NE that meet your search criteria.
...................................................................................................................................................................................................
3
Click the radio button next to the BLSR protection group you wish to modify. From
the Go menu, select Modify protection group and click Go.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-110
Traffic provisioning tasks
To modify a 4-fiber BLSR protection group
Result: The Modify Protection Group page is displayed.
...................................................................................................................................................................................................
4
Change the entries or selections for any modifiable fields that you wish to update.
•
•
•
•
•
•
•
•
In the Ring protection protocol field the following selections depending on the
Rate selection are possible:
– for rate type “OC-48”: Standard, or Transoceanic.
– for rate type “OC-192”: Standard, Transoceanic-shortened, or
Transoceanic-TOPEX.
New Ring ID – enter a text string with 1 to 15 characters to specify the new ring
identification name.
Wait to restore time (Minute) – select a value from 0 to 12 min. in 1 step
increments or 99 (infinite) to specify the wait-to-restore time for ring switches in
revertive mode.
Auto ring discovery – select Enabled or Disabled. If this parameter is enabled,
the automatic ring discovery algorithm will assign nodeID values to each node in
the ring and construct the necessary ring map information. All nodes in the ring
must be Lucent Technologies network elements. If disabled, the user will assign the
Node ID value manually.
Automatic squelch map calculation – select Enabled or Disabled. If this
parameter is enabled, the automatic squelch map calculation is switched on. If
disabled, the function is switched off.
Ring circuit alarm mode – select Enabled or Disabled to enable or disable ring
circuit alarms for the local 2-fiber MS-SPRing protection group.
Alarm severity assignment profile – enter a string with 1 to 24 characters to
specify a pre-defined alarm severity assignment profile (ASAP) to be used for the
protection group in question. An ASAP is a list of alarms which can occur in a
network element and which each have an alarm severity assigned.
Span wait to restore – select a value from 0 to 12 min. in 1 step increments or
99 (infinite) to specify the wait-to-restore time for span switches in revertive mode.
...................................................................................................................................................................................................
5
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Modify Protection Group page, and the 4-fiber BLSR protection
group is modified.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-111
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To
delete a 4-fiber BLSR protection group
...................................................................................................................................................................................................................................
When to use
Use this task to delete a 4-fiber bidirectional line switched ring (BLSR) protection
group.
Before you begin
Make sure that the SONET flavor of the management system user interface is active.
To change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path:
Network Elements → Protection Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1.
2.
3.
4.
5.
6.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group name field, type the protection group name (optional).
In the Protection group type field, select 4F BLSR.
In the Rate field, select the port rate (optional). The default selection is All.
Click Search.
Result: The Protection Groups page is populated with a list of protection groups
in the NE that meet your search criteria.
...................................................................................................................................................................................................
3
CAUTION
Service-disruption hazard
Deletion of a protection could cause a traffic interruption.
Click the radio button next to the BLSR protection group you wish to delete. From the
Go menu, select Delete protection group and click Go.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-112
Traffic provisioning tasks
To delete a 4-fiber BLSR protection group
Result: A confirmation window is displayed asking you to confirm the deletion.
...................................................................................................................................................................................................
4
Click Yes.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Protection Groups page, and the BLSR protection group is deleted.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-113
Issue 2, July 2008
See notice on first page
Traffic provisioning tasks
To
operate a 4-fiber BLSR protection switch
...................................................................................................................................................................................................................................
When to use
Use this task to execute a 4-fiber bidirectional line switched ring (BLSR) protection
switch (manual to working).
Before you begin
Make sure that the SDH flavor of the management system user interface is active. To
change the setting, use the respective options in My Preferences → Preferences
→ Application Preferences → Terminology.
Task
...................................................................................................................................................................................................
1
Do one of the following:
•
•
Use the object links to follow this path:
Network Elements → Protection Groups.
On the Network Map, right-click the NE upon which you wish to execute a
management function. From the Node menu, select Network Element
→ Protection Groups.
Result: The Protection Groups page is displayed.
...................................................................................................................................................................................................
2
Complete the following steps to specify the criteria for your search:
1.
2.
3.
4.
5.
6.
In the NE type field, select a type of NE (if not already present).
In the NE name field, select the name of a target NE (if not already present).
In the Protection group name field, type the protection group name (optional).
In the Protection group type field, select 4F BLSR.
In the Rate field, select the port rate (optional). The default selection is All.
Click Search.
Result: The Protection Groups page is populated with a list of protection groups
in the NE that meet your search criteria.
...................................................................................................................................................................................................
3
Click the radio button next to the BLSR protection group you wish to execute a
protection switch. From the Go menu, select Operate protection switch and click Go.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
10-114
Traffic provisioning tasks
To operate a 4-fiber BLSR protection switch
Result: The Protection Switch page is displayed.
...................................................................................................................................................................................................
CAUTION
4
Service-disruption hazard
A forced switch to a faulty section or lockout of protection could cause a traffic
interruption.
Perform a forced switch only to a section which is working fault-free.
Change the entries or selections for any modifiable fields that you wish to update.
•
•
•
Switch type – select Span or Ring to specify what type of protection switching is
used for the BLSR protection group.
Destination side – click the radio button East or West to specify the destination
ring side to which the switch command shall be applied.
Switch operation – select the switch command you wish to execute. Depending on
the selection of the Switch type the following values are possible:
– for switch type “Span”: Forced, Manual, Lockout, or Clear.
– for switch type “Ring”: Forced, Manual, or Clear.
...................................................................................................................................................................................................
5
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Protection Switch page, and the BLSR protection switch is
executed.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
10-115
Issue 2, July 2008
See notice on first page
11
11
Software
and NE database
management concepts
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter presents concept information related to software update on LambdaUnite ®
MSS network elements using Lucent OMS.
Contents
Functionality description
11-2
Software upgrade
11-5
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
11-1
Issue 2, July 2008
See notice on first page
Software and NE database management concepts
Functionality
description
...................................................................................................................................................................................................................................
Types of NE software
The management system is able to manage the software of NEs in the network.
There are two types of NE software:
•
•
Applications, such as NE generics
Data files, such as NE database versions. These contain the configuration data of
the NE. It is commonly known as management information base (MIB) or as a
backup.
To manage NE software
The management system allows you to manage software in the following ways:
•
•
•
•
Manage
Manage
Manage
Manage
NE
NE
NE
NE
generics on the management system
generics on the NE
database on the management system
database on the NE
In addition, the management system is able to perform tasks associated with software
management on a scheduled basis. The tasks can be scheduled to run as a one-time
activity to be started on a specific day and time or as a periodic activity to be started
on a recurring day and time.
Manage NE generics on the management system
Software management for NE generics on the management system includes the ability
to add an NE generic to the management system from a local removable media, delete
an NE generic from the management system, transfer an NE generic from the
management system to an NE, support file management capabilities for the NE
generics files from the management system, view in-progress NE generic transfers, and
abort in-progress NE generic transfers.
Maximum number of NE generics stored on the management system
The maximum number of NE generics able to be stored on the management system is
six.
Manage NE software generics on NEs
The management system displays the software generics and the attributes that are
present on the NEs. Additionally, the user can transfer a software generic from the
management system to an NE, transfer a software generic from NE to NE, activate a
software generic on an NE, abort an in-progress software transfer, commit an NE
generic and revert to the inactive NE generic.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
11-2
Software and NE database management concepts
Functionality description
An upgrade of an NE generic occurs in the following steps:
1.
2.
3.
4.
5.
“To
“To
“To
“To
“To
add an NE generic to the management system” (p. 12-4)
transfer an NE generic from the management system to an NE” (p. 12-6)
activate an NE generic on an NE” (p. 12-17)
commit an NE generic on an NE” (p. 12-20)
revert an NE generic on an NE” (p. 12-22)
An NE generic can be added to the management system file system from CD-ROM.
For file transfer from CD-ROM, the user simply physically loads the CD-ROM
because the management system can automatically mount the CD-ROM file system. It
is also possible to use other commonly available tools and applications to get software
files into the management system file system (for example, use file transfer software,
such as FTP, to transfer software to the management system over a network).
The management system can store a maximum of six NE generic releases per NE type.
When the maximum is reached, one release must be deleted before another can be
added. The management system does not automatically overwrite the oldest one.
Activate NE generics
This feature allows the user to retrieve the release number of the NE generic that is
active on the NE, retrieve the release number of the NE generic on the NE that is the
standby (that is, the NE generic that resides in the inactive partition of the NE), and
activate the standby NE generic.
Available functions are:
•
•
Activate: Standard – the generic is activated immediately.
Activate: Trial – the generic is activated for a trial phase. It is possible to revert
back to the previous generic together with the restoration of the last matching
database.
When the trial phase is finished successfully, the generic can be committed.
Otherwise it is possible to revert it.
Manage NE database on the management system
An NE database file is a binary image of the complete memory of the NE. Copies of
the NE database file can be backed up onto the management system and used to
perform NE restoration.
NE database backup can be performed on-demand or per a schedule. The Scheduled
Tasks page is used to schedule backups. A default of up to three backup files can be
saved on the management system per NE. When this limit is reached, the oldest file is
overwritten. For smaller networks, it is possible to have more than three backup files.
See your Lucent representative for more information.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
11-3
Issue 2, July 2008
See notice on first page
Software and NE database management concepts
Functionality description
The management system displays the view of NE database stored on the management
system. The user can view the software memory files and their attributes. The user can
also perform other software management tasks such as create an NE database backup
on the management system, and restore NE database from a management system
backup.
Manage NE database on the NE
The management system displays the view of NE database stored on an NE. It allows
the user to view the NE software memory files and their attributes. It also allows the
user to perform other software management tasks, such as create an NE database
backup on the management system, abort in progress NE database transfer, activate NE
database and restore NE database from a management system backup.
Scheduling software management tasks
The management system allows searching for and scheduling the following software
management tasks:
•
•
•
•
•
•
NE database backup
Transfer NE generic from management system to NE
Transfer NE generic from NE to NE
Activate NE generic
Activate NE database
Activate: NE generic and memory
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
11-4
Software and NE database management concepts
Software
upgrade
...................................................................................................................................................................................................................................
Introduction
The NE software is stored on the controller unit of the NE. To upgrade this software
the new software must be downloaded on the NE. This can be done from the
management system.
System controller software
The main unit 1 contains the software to control and support the NE. The
manufacturers executable code (MEC) file contains the complete software package for
one NE. The software in the main unit 1 is also used to provide a basic configuration
to the units connected to the main unit 1. These other assigned units obtain the
appropriate part of the software package from the main unit 1 during the system
start-up or when a unit is inserted.
The main unit 2 (if present) is synchronized (image database only) to main unit 1. If a
provisioning database is present on the main unit 1 card this database will be dropped
immediate after insertion/recovery.
Two memory stores
On the main unit 1 there are two memory stores that can contain each a different
MEC. The store with the software that is executed is called the active store and the
other store is called the backup store. In case of a software upgrade, the management
system downloads a complete software package to the backup store of the main unit 1.
Switch stores
With a switch command from the management system, the software in the backup
store can be made active. The switch command switches between the two stores, thus
the active store becomes the backup store and vice versa.
Diagram
The use of software stores is shown in the following figure:
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
11-5
Issue 2, July 2008
See notice on first page
Software and NE database management concepts
Software upgrade
Store 1
Processor
Store 2
Main unit
Processor
Management system
Program
Store
Units
Network element
Commit the software
After confirmation of a switch command between the active and backup store, the
management system loses its association with the NE for approximately 10 minutes. If
the management system can renew the association with the NE the active store is
committed. If the active store is not committed within two hours after the switch, the
NE will switch back to the old software load.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
11-6
12
12
Software
and NE database
management tasks
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter informs about how to perform the most common tasks related to software
management.
Contents
Tasks related to NE generics
12-3
To view a list of NE generics stored on the management system
12-3
To add an NE generic to the management system
12-4
To delete an NE generic from the management system
12-5
To transfer an NE generic from the management system to an NE
12-6
To schedule the transfer of an NE generic from the management system
to an NE
12-8
To view a list of in-progress transfers of NE generics
12-11
To abort an in-progress NE generic transfer
12-12
To view a list of NE generics stored on an NE
12-15
To activate an NE generic on an NE
12-17
To commit an NE generic on an NE
12-20
To revert an NE generic on an NE
12-22
To schedule NE generic activation
12-24
Tasks related to NE databases
12-28
To view a list of NE database versions stored on the management system
12-28
To view a list of NE database versions stored on an NE
12-31
To back up NE database versions onto the management system
12-32
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
12-1
Issue 2, July 2008
See notice on first page
Software and NE database management tasks
Overview
To schedule the backup of an NE database version onto the management
system
12-37
To restore an NE database version from the management system to an
NE
12-39
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
12-2
Software and NE database management tasks
Tasks related to NE generics
To view a list of NE generics stored on the management
system
...................................................................................................................................................................................................................................
When to use
Use this task to view a list of NE generics stored on the management system.
Task
...................................................................................................................................................................................................
1
Use the object links to follow this path:
•
Network Elements → Software
Result: The Search section of the Software page is displayed.
...................................................................................................................................................................................................
2
In the Software type field, select NE generic.
...................................................................................................................................................................................................
3
In the Software stored on field, select Management system.
...................................................................................................................................................................................................
4
In the NE type field, select a type of NE or select All.
...................................................................................................................................................................................................
5
Click Search.
Result: The list at the bottom of the Software page is populated with a list of the
NE generics stored on the management system that meet your search criteria.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
12-3
Issue 2, July 2008
See notice on first page
Software and NE database management tasks
To
add an NE generic to the management system
...................................................................................................................................................................................................................................
When to use
Use this task to add an NE generic to the management system.
Task
...................................................................................................................................................................................................
1
Insert the CD-ROM that contains the NE generic into the CD-ROM drive of the server.
...................................................................................................................................................................................................
2
Use the object links to follow this path:
•
Network Elements → Software
Result: The Search section of the Software page is displayed.
...................................................................................................................................................................................................
3
In the Software operation field, select Add NE generic to management system and
click Go.
Result: The Add NE Generic to Management System page is displayed.
...................................................................................................................................................................................................
4
In the NE type field, select a type of NE.
...................................................................................................................................................................................................
5
Click Submit.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Add NE Generic to Management System page, and the NE generic
is added to the management system. The management system logs this activity in
the User Activity Log. The CD-ROM is unmounted automatically, and the user can
push the “Eject” button to retrieve the CD-ROM from the drive.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
12-4
Software and NE database management tasks
To
delete an NE generic from the management system
...................................................................................................................................................................................................................................
When to use
Use this task to delete an NE generic from the management system.
Task
...................................................................................................................................................................................................
1
Use the object links to follow this path:
•
Network Elements → Software
Result: The Search section of the Software page is displayed.
...................................................................................................................................................................................................
2
In the Software type field, select NE generic.
...................................................................................................................................................................................................
3
In the Software stored on field, select Management system.
...................................................................................................................................................................................................
4
In the NE type field, select a type of NE or select All.
...................................................................................................................................................................................................
5
Click Search.
Result: The list at the bottom of the Software page is populated with a list of the
NE generics stored on the management system that meet your search criteria.
...................................................................................................................................................................................................
6
Click the radio button next to the NE generic that you wish to delete. From the Go
menu, select Delete NE generic from management system and click Go.
Result: A confirmation window is displayed.
...................................................................................................................................................................................................
7
Confirm that you want to proceed with the deletion.
Result: A progress indication followed by a confirmation is issued in the Message
section of the Software page, and the software is deleted from the management
system. The management system logs this activity in the User Activity Log.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
12-5
Issue 2, July 2008
See notice on first page
Software and NE database management tasks
To transfer an NE generic from the management system to an
NE
...................................................................................................................................................................................................................................
When to use
Use this task to transfer an NE generic from the management system to an NE.
Important! The transfer of an NE generic from the management system to an NE
is a lengthy process that may take up to a few hours to complete.
Before you begin
Because each type of NE has individual requirements (hardware and software) and the
order in which certain steps must be performed is particular to the NE, the
documentation for the NEs should be consulted for software installation and upgrade
procedures.
Task
...................................................................................................................................................................................................
1
In the top navigation bar select My network → Job updates.
Result: The Job Updates page is displayed. The Background Task Status
section of this page allows you to monitor the status of the task.
...................................................................................................................................................................................................
2
Use the object links to follow this path:
•
Network Elements → Software
Result: The Search section of the Software page is displayed.
...................................................................................................................................................................................................
3
In the Software type field, select NE generic.
...................................................................................................................................................................................................
4
In the Software stored on field, select Management system.
...................................................................................................................................................................................................
5
In the NE type field, select a type of NE or select All.
...................................................................................................................................................................................................
6
Click Search.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
12-6
Software and NE database management tasks
To transfer an NE generic from the management system
to an NE
Result: The list at the bottom of the Software page is populated with a list of the
NE generics stored on the management system that meet your search criteria.
...................................................................................................................................................................................................
7
Click the radio button next to the NE generic that you wish to transfer. From the Go
menu, select Download from management system to NE and click Go.
Result: The Download from management system to NE page is displayed.
...................................................................................................................................................................................................
8
Select the NE to which the NE generic will be transferred.
...................................................................................................................................................................................................
9
When downloading the NE Generic to the inactive partition the following questions
will be displayed:
•
Reload if file being transferred is the same as the current inactive release?
Select No if you do not want to transfer the NE Generic to any NE where the
inactive release of the NE is the same as the NE generic being downloaded, else
Yes.
•
Reload if file being transferred is the same as the current active release?
Select No if you do not want to transfer the NE generic to any NE where the
active release of the NE is the same as the NE generic being downloaded, else Yes.
•
Reload if file being transferred is older than the current active release?
Select No if you do not want to transfer the NE generic to any NE where the
active release of the NE is older than the NE generic being downloaded, else Yes.
...................................................................................................................................................................................................
10
Click Submit.
Result: A confirmation window is displayed asking you to confirm the transfer of
the NE generic.
...................................................................................................................................................................................................
11
Click Yes.
Result: The system initiates the software transfer from the management system to
the NE. The management system notes the progress of the operation in the
Background Task Status section of the Job Updates page, and logs this activity
in the User Activity Log.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
12-7
Issue 2, July 2008
See notice on first page
Software and NE database management tasks
To schedule the transfer of an NE generic from the
management
system to an NE
...................................................................................................................................................................................................................................
When to use
Use this task to schedule the transfer of an NE generic from the management system to
an NE.
Task
...................................................................................................................................................................................................
1
Use the object links to follow this path:
•
Network Elements → Software
Result: The Search section of the Software page is displayed.
...................................................................................................................................................................................................
2
In the Software type field, select NE generic.
...................................................................................................................................................................................................
3
In the Software stored on field, select Management system.
...................................................................................................................................................................................................
4
In the NE type field, select a type of NE or select All.
...................................................................................................................................................................................................
5
Click Search.
Result: The list at the bottom of the Software page is populated with a list of the
NE generics stored on the management system that meet your search criteria.
...................................................................................................................................................................................................
6
Click the radio button next to the NE generic to which you want to schedule the
software transfer. From the Go menu, select Schedule download from management
system to NE and click Go.
Result: The Schedule download from management system to NE page is
displayed. It is prepopulated with read-only information about the selected NE
generic and, depending on the NE type. Additional fields may be displayed to
provide further selections.
...................................................................................................................................................................................................
7
From the preselected NE list, select the Available NE to which the NE generic will be
transferred.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
12-8
Software and NE database management tasks
To schedule the transfer of an NE generic from the
management system to an NE
When downloading the NE Generic to the inactive partition, the following questions
will be displayed:
•
Reload if file being transferred is the same as the current inactive release?
Select No if you do not want to transfer the NE generic to any NE where the
inactive release of the NE is the same as the NE generic being downloaded, else
Yes.
•
Reload if file being transferred is the same as the current active release?
Select No if you do not want to transfer the NE generic to any NE where the
active release of the NE is the same as the NE generic being downloaded, else Yes.
•
Reload if file being transferred is the older than the current active release?
Select No if you do not want to transfer the NE generic to any NE where the
active release of the NE is older than the NE generic being downloaded, else Yes.
•
Click Schedule.
Result: The Schedule download from management system to NE page is
displayed. It is prepopulated with read-only information in the Task type and the
task-specific window. Additional fields in the Schedule options window may be
displayed to provide further selections.
...................................................................................................................................................................................................
8
To schedule the frequency, click the calendar icon after the Scheduled Date field.
Result: A Date/Time Chooser window is displayed. Select the scheduled start
date.
...................................................................................................................................................................................................
9
In the Schedule options panel change the entries or selections for any modifiable
fields that you wish to update:
•
•
•
•
•
In the Scheduled time field, enter the time in the format “hh:mm:ss”. The time
entered applies for both the start and end date
In the Scheduled task name field, enter a user defined name for the scheduled
task or allow the system to generate a default value. Note: The scheduled task
name cannot be modified once the task is created.
In the Number of retries field, select the number of times (1 to 4) the scheduled
task will be retried in case of error or no retries.
In the Execution Interval field, select the number of hours this task should be
performed from the drop down list. Possible values are from 1 hour to 12 hours
and Continuous.
In the Retry interval field, select the interval of time that will pass between retries.
Possible values are 1 min. to 60 min.
...................................................................................................................................................................................................
10
Click Submit.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
12-9
Issue 2, July 2008
See notice on first page
Software and NE database management tasks
To schedule the transfer of an NE generic from the
management system to an NE
Result: The scheduled task is added.
E...................................................................................................................................................................................................
ND OF STEPS
Reference
For detailed information about how to view a list of scheduled tasks, how to modify
scheduled tasks, and how to delete scheduled tasks, refer to Lucent OMS Network
Element Management Guide – Tools – Scheduled Tasks.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
12-10
Software and NE database management tasks
To
view a list of in-progress transfers of NE generics
...................................................................................................................................................................................................................................
When to use
Use this task to view a list of in-progress transfers of NE generics.
Task
...................................................................................................................................................................................................
1
Use the object links to follow this path:
•
Network Elements → Software
Result: The Search section of the Software page is displayed.
...................................................................................................................................................................................................
2
In the Software type field, select NE generic.
...................................................................................................................................................................................................
3
In the Software stored on field, select Management system.
...................................................................................................................................................................................................
4
In the NE type field, select a type of NE or select All.
...................................................................................................................................................................................................
5
Click Search.
Result: The list at the bottom of the Software page is populated with a list of the
NE generics stored on the management system that meet your search criteria.
...................................................................................................................................................................................................
6
Click the radio button next to any entry in the list. From the Go menu, select View in
progress NE generic transfers and click Go.
Result: The Software page is displayed, and includes a list of NE generic transfers
that are in-progress and met the search criteria in the previous step.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
12-11
Issue 2, July 2008
See notice on first page
Software and NE database management tasks
To
abort an in-progress NE generic transfer
...................................................................................................................................................................................................................................
When to use
Use this task to abort an in progress NE generic transfer. Both management system to
NE and NE to NE transfers can be aborted.
There are three methods for this task.
Task, method 1: from the In-Progress NE Generic Transfers page
...................................................................................................................................................................................................
1
In the top navigation bar select My network → Job updates.
Result: The Job Updates page is displayed. This page allows you to monitor the
status of the task.
...................................................................................................................................................................................................
2
Use the object links to follow this path:
•
Network Elements → Software
Result: The Search section of the Software page is displayed.
...................................................................................................................................................................................................
3
In the Software type field, select NE generic.
...................................................................................................................................................................................................
4
In the Software stored on field, select Management system.
...................................................................................................................................................................................................
5
In the NE type field, select a type of NE or select All.
...................................................................................................................................................................................................
6
Click Search.
Result: The list at the bottom of the Software page is populated with a list of the
NE generics stored on the management system that meet your search criteria.
...................................................................................................................................................................................................
7
Click the radio button next to any entry in the list. From the Go menu, select View in
progress NE generic transfers and click Go.
Result: The Software page is displayed, and includes a list of NE generic transfers
that are in-progress and met the search criteria in the previous step.
...................................................................................................................................................................................................
8
Click the radio button next to the transfer you wish to halt. From the Go menu, select
Abort NE generic transfer and click Go.
...................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
12-12
Software and NE database management tasks
To abort an in-progress NE generic transfer
Result: The Abort NE generic transfer window opens.
...................................................................................................................................................................................................
9
Click Submit.
Result: A confirmation window is displayed asking you to confirm the halt of the
NE generic transfer.
...................................................................................................................................................................................................
10
Click OK.
Result: The selected NE generic transfer is halted.
The management system notes the progress of two tasks in the Job Updates page.
The original transfer task is marked as failed, and the abort task is marked as
success. The management system logs these activities in the User Activity Log.
E...................................................................................................................................................................................................
ND OF STEPS
Task, method 2: from the list of NE generics stored on an NE
...................................................................................................................................................................................................
1
In the top navigation bar select My network → Job updates.
Result: The Job Updates page is displayed. This page allows you to monitor the
status of the task.
...................................................................................................................................................................................................
2
Use the object links to follow this path:
•
Network Elements → Software
Result: The Search section of the Software page is displayed.
...................................................................................................................................................................................................
3
In the Software type field, select NE generic.
...................................................................................................................................................................................................
4
In the Software stored on field, select NE.
...................................................................................................................................................................................................
5
In the NE type field, select a type of NE.
...................................................................................................................................................................................................
6
Do one of the following:
•
•
In the NE Name field, select the name of NE in question.
In the NE Name field, select All and populate the field NE Generic with the
respective version number.
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
12-13
Issue 2, July 2008
See notice on first page
Software and NE database management tasks
To abort an in-progress NE generic transfer
Click Search.
Result: The list at the bottom of the Software page is populated with a list of the
NE generics stored on the NE.
The following applies to the search results:
• If the search criteria is for a specific NE, the search results table includes
matches in both the active and inactive NE partitions.
• If the search criteria is for a specific NE generic, the list of entries in the search
results table include all NEs that contain an active release matching the search
criteria.
Additionally, the list includes all software generics on any NE that has a
matching software generic in the active release. For example, if the software
generic in the active version of the NE matches the search criteria but the
generic in the inactive partition does not, both still appear in the search results
table. This means that some rows of the table may have a different release than
the selected search criteria.
...................................................................................................................................................................................................
7
Click the radio button next to the transfer you wish to halt. From the Go menu, select
Abort NE generic transfer and click Go.
Result: The Abort NE generic transfer window opens.
...................................................................................................................................................................................................
8
Click Submit.
Result: A confirmation window is displayed asking you to confirm the halt of the
NE generic transfer.
...................................................................................................................................................................................................
9
Click OK.
Result: The selected NE generic transfer is halted.
The management system notes the progress of two tasks in the Job Updates page.
The original transfer task is marked as failed, and the abort task is marked as
success. The management system logs these activities in the User Activity Log.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
12-14
Software and NE database management tasks
To
view a list of NE generics stored on an NE
...................................................................................................................................................................................................................................
When to use
Use this task to view a list of NE generics stored on an NE.
Task
...................................................................................................................................................................................................
1
Use the object links to follow this path:
•
Network Elements → Software
Result: The Search section of the Software page is displayed.
...................................................................................................................................................................................................
2
In the Software type field, select NE generic.
...................................................................................................................................................................................................
3
In the Software stored on field, select NE.
...................................................................................................................................................................................................
4
In the NE type field, select a type of NE.
...................................................................................................................................................................................................
5
Do one of the following:
•
•
In the NE Name field, select the name of NE in question.
In the NE Name field, select All.
– In the field NE generic partition, select either Active or Inactive.
– In the field NE generic type, select Release number, if you want to specify
the release number (for example “5.0.1”) or Item code, if you want to specify
the item code (for example “SCA358”) of the NE generic in question.
– Populate the field NE Generic with the respective version number. The NE
generic label is a hyperlink to the NE Generic Selection page from which to
select the NE generic to include in the search criteria. As an alternative, type in
an NE generic name in the text box.
Click Search.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
12-15
Issue 2, July 2008
See notice on first page
Software and NE database management tasks
To view a list of NE generics stored on an NE
Result: The list at the bottom of the Software page is populated with a list of the
NE generics stored on the NE.
The following applies to the search results:
• If the search criteria is for a specific NE, the search results table includes
matches in both the active and inactive NE partitions.
• If the search criteria is for a specific NE generic, the list of entries in the search
results table include all NEs that contain an active release matching the search
criteria.
Additionally, the list includes all software generics on any NE that has a
matching software generic in the active release. For example, if the software
generic in the active version of the NE matches the search criteria but the
generic in the inactive partition does not, both still appear in the search results
table. This means that some rows of the table may have a different release than
the selected search criteria.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
12-16
Software and NE database management tasks
To
activate an NE generic on an NE
...................................................................................................................................................................................................................................
When to use
Use this task to activate an NE generic on an NE.
Task
...................................................................................................................................................................................................
1
In the top navigation bar select My network → Job updates.
Result: The Job Updates page is displayed. This page allows you to monitor the
status of the task.
...................................................................................................................................................................................................
2
Use the object links to follow this path:
•
Network Elements → Software
Result: The Search section of the Software page is displayed.
...................................................................................................................................................................................................
3
In the Software type field, select NE generic.
...................................................................................................................................................................................................
4
In the Software stored on field, select NE.
...................................................................................................................................................................................................
5
In the NE type field, select a type of NE.
...................................................................................................................................................................................................
6
Do one of the following:
•
•
In the NE Name field, select the name of NE in question.
In the NE Name and the NE generic partition fields, select All.
If you want to specify, select:
– In the field NE generic partition either Active or Inactive.
– In the field NE generic type the Release number (for example “5.0.1”) or the
Item code (for example “SCA358”) of the NE generic in question.
Populate the field NE Generic with the respective version number. The NE
Generic label is a hyperlink to the NE Generic Selection page from which to
select the NE generic to include in the search criteria. As an alternative, type in an
NE generic name in the text box.
Click Search.
...................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
12-17
Issue 2, July 2008
See notice on first page
Software and NE database management tasks
To activate an NE generic on an NE
Result: The list at the bottom of the Software page is populated with a list of the
NE generics stored on the NE.
The following applies to the search results:
• If the search criteria is for a specific NE, the search results table includes
matches in both the active and inactive NE partitions.
• If the search criteria is for a specific NE generic, the list of entries in the search
results table include all NEs that contain an active release matching the search
criteria.
Additionally, the list includes all software generics on any NE that has a
matching software generic in the active release. For example, if the software
generic in the active version of the NE matches the search criteria but the
generic in the inactive partition does not, both still appear in the search results
table. This means that some rows of the table may have a different release than
the selected search criteria.
...................................................................................................................................................................................................
7
Click the radio button next to the NE for which you wish to activate the inactive NE
generic.
From the Go menu, select Activate and click Go.
Result: The Activate NE generic page is displayed. In that page, most of the
fields are pre-populated according to your previous selections.
...................................................................................................................................................................................................
8
Change the entries or selections for any modifiable fields that you wish to update.
•
•
•
Activation type – select Standard if you want to perform a normal activation, or
Trial if the LambdaUnite ® MSS is to be used. Using the option Trial, it is possible
to revert back to the previous generic together with the restoration of the last
matching database.
Activation order – select System default to use the default rules for establishing
the order of NEs within the grouping, or select User defined to place the NE in
the queue using the order defined in the Selected NE list.
Activate NEs – select one of the following radio buttons to determine if the NEs
in a grouping can exit the management system queue as long as resources are
available or if an activation of an NE in the grouping can only be initiated if the
activation of the previous NE in the grouping is complete:
– In parallel – when executing the activation request, the management system
allows all NEs in the grouping to exit the queue as long as resources are
available.
– In series – when executing the activation request, the management system only
allows one NE in the grouping to have an NE generic activation in progress at
a time. All other NE generic activations for NEs in the grouping must remain in
the queue.
....................................................................................................................................................................................................................................
Alcatel-Lucent - Proprietary
365-312-876R8.0.2
See notice on first page
Issue 2, July 2008
12-18
Software and NE database management tasks
•
To activate an NE generic on an NE
Stop on failure – select No to instruct the management system to proceed with
activation requests for all NEs in the grouping regardless of the result of the
activations of other NEs in the grouping. Select Yes to instruct the management
system to fail all other NE activation requests in the queue for the grouping when
any NE activation in the grouping fails. Activation requests in progress at an NE
for other NEs in the grouping are unaffected.
•
Continue if the inactive NE generic is the same as the current active NE
generic – specify whether or not the activation process should continue if the
inactive NE generic is the same as the current active NE generic. If you select no,
when the management system is executing the download request, it does not
attempt to activate software for any NE where the inactive release of the NE is the
same as the active release of the NE.
•
Continue if the inactive NE generic is the older than the current active NE
generic – specify whether or not the activation process should continue if the
inactive NE generic is the older than the current active NE generic. If you select
no, when the management system is executing the download request, it does not
attempt to activate software for any NE where the inactive release of the NE is
older than the active release of the NE.
Click Submit.
Result: The NE generic in the inactive partition is installed in the active partition
and the NE reboots to update the current running version of the software.
The management system notes the progress of the operation in the Job Updates
page, and logs this activity in the User Activity Log.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
365-312-876R8.0.2
Alcatel-Lucent - Proprietary
12-19
Issue 2, July 2008
See notice on first page
Software and NE database management tasks
To
commit an NE generic on an NE
...................................................................................................................................................................................................................................
When to use
Use this task to commit an NE generic that is in trial mode phase on an NE. That way
you terminate the trial phase of a newly installed software.
Task
...................................................................................................................................................................................................
1
In the top navigation bar, select My network → Job updates.
Result: The Job Updates page is displayed. This page allows you to monitor the
status of the task.
...................................................................................................................................................................................................
2
Use the object links to follow this path:
•
Network Elements → Software
Result: The Search section of the Software page is displayed.
...................................................................................................................................................................................................
3
In the Software type field, select NE generic.
........................................................................................................