Professional Documents
Culture Documents
Nokia 8DG09603CAAATQZZA Issue 4 PDF
Nokia 8DG09603CAAATQZZA Issue 4 PDF
8DG09603CAAATQZZA
Issue 4
September 2017
1850 TSS-320/TSS-320H/TSS-160
Legal notice
Nokia is a registered trademark of Nokia Corporation. Other products and company names mentioned herein may be trademarks or
tradenames of their respective owners.
The information presented is subject to change without notice. No responsibility is assumed for inaccuracies contained herein.
© 2017 Nokia.
Security statement
In rare instances, unauthorized individuals make connections to the telecommunications network through the use of remote access
features. In such an event, applicable tariffs require that the customer pay all network charges for traffic. Nokia cannot be responsible for
such charges and will not make any allowance or give any credit for charges that result from unauthorized access.
Limited warranty
Nokia provides a limited warranty for this product. For more information, consult your local Nokia customer support team.
Contents
2 Getting started..............................................................................................................................................49
2.1 Overview ...........................................................................................................................................49
2.2 TL1 and CLI sessions .......................................................................................................................49
10 CLI Procedures...........................................................................................................................................577
10.1 Overview .........................................................................................................................................577
10.2 Administer Autonegotation ..............................................................................................................577
10.3 Administer Ethernet Flow Classifier ................................................................................................580
10.4 Administer ETS to Provider Bridge ETS/PW/VPLS bidirectional flow ............................................582
10.5 Administer ETS-to-ETS bidirectional (port to port configuration) ....................................................585
10.6 Administer In Fiber In Band for Control Plan...................................................................................587
10.7 Administer Traffic Descriptor ...........................................................................................................589
10.8 Color Profile Management .............................................................................................................591
10.9 Ethernet Physical management ......................................................................................................593
10.10 Ethernet Port management (over MAU)..........................................................................................595
10.11 Ethernet Port management (over GFP) ..........................................................................................597
10.12 General Interface Management ......................................................................................................599
10.13 L2 control frames management (in Provider Bridge) ......................................................................600
B Equipment Entities.....................................................................................................................................679
B.1 Equipment provisionable.................................................................................................................679
B.2 Card vs Allowed SFP/XFP ProvisionedType ...................................................................................681
B.3 AIDs ................................................................................................................................................692
B.4 Provisioned Types ...........................................................................................................................693
Glossary ................................................................................................................................................................0
Index ..................................................................................................................................................................714
List of tables
Table 1 Chapter contents ................................................................................................................................22
Table 2 TL1 Special Characters......................................................................................................................34
Table 3 Bit Mapping ........................................................................................................................................44
Table 4 Alarm and cause relationship .............................................................................................................45
Table 5 Necessary tools..................................................................................................................................49
Table 6 Common User Administration Functions ............................................................................................58
Table 7 Equipment Functions..........................................................................................................................58
Table 8 Equipment Provisioning and Deprovisioning......................................................................................59
Table 9 System Information Reports...............................................................................................................59
Table 10 System Administration........................................................................................................................60
Table 11 VCG Functions ...................................................................................................................................61
Table 12 T-MPLS Functions..............................................................................................................................61
Table 13 VC & LOVC Functions........................................................................................................................62
Table 14 SDH Functions ...................................................................................................................................62
Table 15 ODU Functions...................................................................................................................................63
Table 16 OTU Functions ...................................................................................................................................63
Table 17 Ethernet Functions .............................................................................................................................63
Table 18 Maintenance Operation Functions .....................................................................................................64
Table 19 Control Plane Functions .....................................................................................................................64
Table 20 WDM Functions..................................................................................................................................64
Table 21 ATM Functions ...................................................................................................................................65
Table 22 Security Functions..............................................................................................................................65
Table 23 1662 Drop Shelf Equipment Functions...............................................................................................66
Table 24 S320 Shelf Equipment Functions .......................................................................................................66
Table 25 Procedures Required Before Deprovisioning Modules ....................................................................309
Table 26 Housekeeping input characteristics..................................................................................................342
Table 27 Supported features in the modified AIDs..........................................................................................445
Table 28 PST usage rules depending on PWSegment current PST value .....................................................515
Table 29 CCT usage rules depending on PWSegment DIR parameter ..........................................................518
Table 30 CrsPwSeg allowed when FROM=TO ...............................................................................................518
Table 31 PST usage rules depending on TUSegment current PST value ......................................................531
List of figures
Figure 1 LAN cable ............................................................................................................................................49
Figure 2 Connection to the interface ..................................................................................................................50
Figure 3 CMD console selection ........................................................................................................................51
Figure 4 CMD console activation .......................................................................................................................51
Figure 5 Telnet session activation ......................................................................................................................52
Figure 6 Telnet console ......................................................................................................................................53
Figure 7 Logging the system..............................................................................................................................53
Figure 8 Successful login answer ......................................................................................................................54
Figure 9 Command response example ..............................................................................................................55
Figure 10 Functional architecture of the Multiservice ATM Collector card .........................................................69
Figure 11 SSH key management .......................................................................................................................88
Figure 12 SSL key management........................................................................................................................92
Figure 13 PSC set and related CIR,PIR,CBS and PBS relationship ...............................................................228
Figure 14 RADIUS general scenario................................................................................................................230
Figure 15 Facility Loopback .............................................................................................................................241
Figure 16 Terminal Loopback...........................................................................................................................242
Figure 17 1WAY cross-connection ...................................................................................................................268
Figure 18 2WAY cross-connection ...................................................................................................................268
Figure 19 1WAY multicast cross-connection build from single 1WAY cross-connections................................269
Figure 20 1WAY loopback through cross-connect matrix ................................................................................269
Figure 21 Boundary clock schema...................................................................................................................286
Figure 22 Conversion of 1WAY <--> 2WAY cross connection..........................................................................297
Figure 23 Conversion of 1WAYSNCP <--> 2WAYSNCP cross connection......................................................298
Figure 24 Conversion of 1WAY <--> 1WAYSNCP - adding/removing a protection leg ....................................299
Figure 25 Conversion of 2WAYSNCP <--> 2WAY - adding/removing a protection leg ...................................300
Figure 26 Database Types ...............................................................................................................................370
Figure 27 Database Backup and File Transfer to RFS ....................................................................................372
Figure 28 Database Types ...............................................................................................................................376
Figure 29 Database Transfer and Restore from RFS to NE ............................................................................378
Figure 30 Port segregation scenario ................................................................................................................383
Figure 31 S320H enhanced shelf (operator view) ...........................................................................................454
List of procedures
2.2 TL1 and CLI sessions ..............................................................................................................................49
4.12 LSR Tunnel Management (Label swap and Tunnel not Terminated).......................................................82
4.24 Tunnel Protection Management (Label swap and Tunnel not Terminated)..............................................98
9.7 Database backup and restore from remote file server on 1662 subshelf ..............................................569
What's new
This is Issue 4 of the 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release
5.1 TL1 User Provisioning Guide.
Document history is captured in the following table:
Issue Date Reason
4 September 2017 Rebranding.
The command to modify equipment is added with new
3 June 2015
AID's of data cards and packet modules.
2 December 2014 1646 SM drop shelf content update.
1 August 2012 First validated issue of this guide.
Intended audience
This TL1 User provisioning guide provides information and procedures necessary to install, self-
test, and turn up the 1850 Transport Service Switch TSS-320, TSS-320H and TSS-160 system.
Chapter Description
“About this document” Defines and explains the following:
• describes the guide's purpose, intended
audience, and organization
• lists related documentation
• explains how to comment on this document
Chapter 1, “Line Command User's Interface This chapter provides an overview to
Introduction” document and describes the writing
conventions used.
Chapter 2, “Getting started” This chapter contains a procedure to initiate a
TL1 or CLI session.
Chapter 3, “Task Index List (IXL)” This chapter provides IXLs group procedures
by function. Each IXL lists procedures
alphabetically by name and refers the user to
the appropriate procedure number.
Chapter 4, “Nontrouble Procedure (NTP)” This chapter lists the major steps required to
complete a task. This list may be all an
experienced user requires. For an
inexperienced user, each step refers to a DLP.
The steps must be performed in the order
listed.
Chapter 5, “Control Plane Functions” This chapter contain detailed steps and
supporting information required to complete a
task when the Control Plane (CP) is used.
Chapter 6, “Detailed Level Procedure” The Detailed Level Procedures (DLP) contain
detailed steps and supporting information
required to complete a task.
Chapter 7, “S320H Shelf Detailed Level The system supports the provisioning and
Procedure” management of new shelves types (“enhanced
shelf”) to improve cost optimization respect to
the current available for TSS-320 and 160
equipment.
Chapter 8, “ TMPLS/MPLS-TP Detailed Level This chapter provides detailed procedures on
Procedure” TMPLS.
Chapter 9, “1662 Drop Shelf Detailed Level This chapter provides information on 1662
Procedure” Drop shelf DLPs.
Chapter 10, “CLI Procedures” CLI procedures list the major steps required to
complete a task.
Chapter Description
Appendix A, “Software Reference Guide” This Software Reference Guide provides
supplementary information to be used with the
8DG09603BAAATQZZA — 1850 Transport
Service Switch (TSS-320, TSS-320H and
TSS-160) Release 5.1 User Provisioning
Guide.
Appendix B, “Equipment Entities” This chapter describes the details on
equipment entities.
“Glossary” Defines and explains the following:
• Telecommunication terms
• Abbreviations
• Acronyms
Index Contains a list of index references
Safety information
For your safety, this document contains safety statements. Safety statements are given at points
where risks of damage to personnel, equipment, and operation may exist. Failure to follow the
directions in a safety statement may result in serious consequences.
Safety precautions
Admonishments
To avoid hazardous conditions, observe the following admonishments:
DANGER
Optional Content
Possibility of personal injury.
Optional Content added above. Please modify as needed.
WARNING
Optional Content
Possibility of equipment damage.
Optional Content added above. Please modify as needed.
NOTICE
Optional Content
Possibility of service interruption.
Optional Content added above. Please modify as needed.
Recycling/take-back/disposal of product
Electronic products bearing or referencing the displayed symbol, when put on the market within the
European Union, are collected and treated at the end of their useful life, in compliance with
applicable European Union and local legislation. They must not be disposed of as part of unsorted
municipal waste.
The product may contain materials such as heavy metals or batteries. Appropriate disposal of such
materials is necessary to avoid a negative impact on the environment and human health.
Note:In the European Union, a solid bar under the crossed-out wheeled bin indicates that the product was put
on the market after 13 August 2005.
Moreover, in compliance with legal requirements and contractual agreements, where applicable,
Nokia offers to provide for the collection and treatment of Nokia products at the end of their useful
life, or products displaced by Nokia equipment offers.
For information regarding take-back of equipment by Nokia, or for more information regarding the
requirements for recycling/disposal of product:
• Contact your Nokia account manager
• Contact Nokia Asset Recovery (mailto: asset.recovery@nokia.com).
• Contact Nokia Global Sustainability (mailto: sustainability.global@nokia.com).
• Visit Nokia Protecting the Environment (http://company.nokia.com/en/our-activities/protecting-
the-environment).
Conventions used
Italic typeface denotes a particular product line or information product.
Helvetica Bold typeface signifies a window, section, command or parameter used with the TL1
Command Builder.
Helvetica typeface indicates a faceplate or 1850 TSS-320, TSS-320H and TSS-160 label
designation, as in the ACTIVE LED on a circuit pack.
Courier Bold indicates a TL1 command typed in a terminal window by the user, as in
act-user:ALU-TSS-160:ALU01:ctag::1850TSS-160;
Courier typeface indicates the system or PC response to a command.
For the remainder of this document, "1850 TSS-320, TSS-320H and TSS-160" is used in place of
1850 Transport Service Switch TSS-320, TSS-320H and TSS-160 in most cases.
Related information
The following documents provide additional information about the 1850 Transport Service Switch
TSS-320, TSS-320H and TSS-160 Release 5.1:
• 8DG09603AAAATQZZA — 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160)
Release 5.1 Product Information Planning Guide provides information on Equipment description,
composition, features of the equipment, detailed unit description, characteristics, hardware
settings, and documents common units used in the different configurations of the product.
• 8DG09603CAAATQZZA — 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160)
Release 5.1 TL1 User Provisioning Guide provides information on provisioning procedures by
means of TL1.
• 8DG09603DAAATQZZA — 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160)
Release 5.1 TL1 Command Guide provides comprehensive resource to all Translator Language
1 commands.
• 8DG09603FAAATQZZA — 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160)
Release 5.1 Maintenance and Trouble-Clearing Guide provides information on Maintenance and
Troubleclearing procedures.
• 8DG09603GAAATQZZA — 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160)
Release 5.1 Safety Guide provides information and safety guidelines to safeguard against
personal injury and to prevent material damage to the equipment.
• 8DG09603HAAATQZZA — 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160)
Release 5.1 Engineering Rules provides the design constraints for engineering a WDM line
system.
• 8DG09603EAAATQZZA — 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160)
Release 5.1 Command Line Interface Guide provides a comprehensive resource for all the
Command Line Interface commands and user provisioning procedures by means of the CLI.
• 8DG09603BAAATQZZA — 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160)
Release 5.1 User Provisioning Guide provides general Craft Terminal information, screen
descriptions and user provisioning procedures by means of the ZIC.
• 8DG09603JAAATQZZA — 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160)
Release 5.1 Installation and Turn-up Guide (ETSI) provides information on Equipment
Installation.
• 8DG09604AAAAADZZA — 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160)
Release 5.1 Electronic Documentation Library. It contains the electronic format of all the above
listed documents.
Document support
For support in using this or any other Nokia document, contact Nokia at one of the following
telephone numbers:
• 1-888-582-3688 (for the United States)
• 1-630-224-2485 (for all other countries)
Technical support
For technical support, contact your local customer support team. See the Support web site
(https://networks.nokia.com/support/) for contact information.
How to order
To order Nokia documents, contact your local sales representative or use the Nokia Networks
Online Services web site at https://online.networks.nokia.com (https://online.networks.nokia.com).
How to comment
To comment on this document, go to the Online Comment Form (http://infodoc.alcatel-lucent.com/
comments/) or e-mail your comments to the Comments Hotline (mailto:comments@nokia.com).
1.1 Overview
1.1.1 Purpose
This user's guide provides step-by-step procedures to help users perform tasks entering complete
TL1 and CLI commands at the prompt. This user's interface is recommended only for users who are
familiar with TL1 and CLI commands, parameters, and syntax.
Each procedure contains important introductory information that is essential to understanding and
completing the task properly.
Procedures must be started at step 1, and steps must be performed in the order given. Failure to do
so may cause unforeseen hazardous conditions.
1.1.5 Contents
1.1 Overview 29
TL1 and CLI overview 31
1.2 Structure of safety statements 31
1.3 TL1 Command Structure and Syntax 32
1.4 TL1 System Messages 36
1.5 CLI Command Structure and Syntax 39
1.6 Conventions used in CLI command definition 46
1.7 Answers to CLI commands 47
M P L
CAUTION
E
Lifting hazard
SA
Lifting this equipment by yourself can result in injury
due to the size and weight of the equipment.
Always use three people or a lifting device to transport
and position this equipment. [ABC123]
Input parameters specify conditions under which a command executes. Parameters can be either
required or optional. The form screen encloses optional parameters in brackets. Three examples of
input parameters follow:
• The Access Identifier (AID) of a facility or equipment unit
• The state of a facility after provisioning
• The range of a command (if ranging is supported for that command)
When a command contains multiple parameters of the same type in a string, the string is a
parameter block. Colons ( : ) separate parameter blocks. Within a block, commas ( , ) separate
individual parameters.
The cross-connect system generally uses the following parameter types; however, the parameters
in some commands do not conform to this model.
Verb-Modifier1[-Modifier2]:[a]:[b]:[c]:[d]:[e]:[f]:[g];
• a = TID—Target Identifier. The TID is an alphanumeric block of up to 20 characters, the first of
which must be alphabetic. It identifies the processing location for a command. When a value is
not entered, the system defaults to the uppercase Site Identifier (SID) value. When a value is
entered, it must match the SID. If the entered value does not match the SID, the system denies
the command.
• b = AID—Access Identifier. The AID identifies a facility port, removable equipment unit, or other
object entity. Examples of parameters in this field are: From Location, To Location, and Control
Port. Some commands have multiple AID fields (FROM,TO).
• c = CTAG—Correlation Tag. The CTAG is a 1 to 6 alphanumeric block that identifies a
transaction. The CTAG correlates system output messages with the commands that caused the
messages. The CTAG is optional; if a CTAG is not entered, the system automatically assigns
one.
• d = General Block—The general block is not supported and must be empty.
• e = Positional Block—Parameters in the positional block are defined by their position or
sequence in the block. Brackets indicate optional parameter values. Absence of brackets
indicates that the parameter value must be entered. If one or more parameter values is omitted
from the end of the block, the preceding comma associated with the value may be omitted.
However, if an optional parameter value is omitted with other positional parameter values
following, all intervening placeholder commas must be provided to indicate that no value is being
entered for that parameter. The system assumes the default or existing parameter value for
omitted optional parameter values. Parameter value combinations are verified by the system
whether the value is determined from a default value or explicitly entered in the command.
• f = Keyword Block—Parameters in the keyword block are defined by a keyword parameter
name. A value for a keyword parameter is specified by entering the parameter name followed by
an equal sign (=) followed by the parameter value. Keyword parameters may be entered in any
order within the keyword block, but keyword parameters must be separated by a comma. Only
commas separating each keyword parameter are required in the keyword parameter block, but
thekeyword block may not begin or end with a comma. Brackets indicate optional parameters
and their associated comma separators. Absence of brackets indicates that the parameter and
any comma separator must be entered.
• g = State Block—The state parameter block is a positional block with parameters defined by
their position or sequence in the block. The state block defines parameters that relate to the
primary and/or secondary state of equipment. The state block is supported only by commands
that include the state block in the input format of a command. When supported, up to two
parameters are possible for the state block, the PST (primary state) parameter and the SST
(secondary state) parameter. Brackets indicate optional parameter values. Absence of brackets
indicates that the parameter value must be entered. If the SST parameter value is omitted from
the end of the block, the trailing comma associated with it may be omitted. However, if an
optional PST parameter value is omitted with an SST positional parameter value following, the
intervening placeholder comma must be provided to indicate that no value is being entered for
the PST parameter. The system assumes the default parameter value for omitted optional
parameter values.
Keyword parameters require a parameter name assignment with each parameter value. Enter
keyword parameters in any order within a block. Positional parameters must occur in the order
specified by the TL1 command.
In this manual, only required entries and/or parameters are given in the command string. Refer to
the 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command
Guide for optional parameter values.
Special
Description
character
<> Enclosing less-than and greater-than signs are used to enclose a description
of the parameter's domain when this is more understandable than an exact
definition of the domain. For example, < 1 - 6 VALID CTAG CHARACTERS >
describes the CTAG domain of 1-6 case sensitive alphanumeric characters.
{} In syntax statements, paired braces enclose a set of values. Generally,
enclosing braces are used in the notation for the non-parsable command
echo line and in describing an output parameter's value set. The enclosing
braces are not part of the actual input command or output message.
[] In syntax statements, paired brackets enclose an optional command
argument; for example: [TID]. These enclosing brackets are not part of the
actual input command or output message.
The following characters are entered in TL1 commands.
- Hyphen. Separates elements of TL1 command codes. Also combines
elements of a compound parameter.
, Comma. Separates parameter values when multiple values exist.
Special
Description
character
: Colon. Separates the command code segment from the parameters. Also
separates succeeding parameter blocks.
; Semicolon. Terminates a command entry and starts execution.
= Equal sign. Associates a parameter name with the assigned parameter. A
parameter must be entered in uppercase exactly as specified. A value of the
parameter follows the equal sign.
& Ampersand. Groups parameter values in an input command (as list of
parameter values is generated), and combines parameter values in an
output message.
&& Double ampersand. Represents numeric ranging in the last argument value
of a parameter (simple or compound) in an input command. It generates a
sequential range of parameter values, beginning with the first term specified
through the last term specified.
When using the equal sign with positional parameters, the parameter must be entered in the correct
position. If this is not done, the system rejects the command.
Brackets [ ] indicate an optional parameter. Brackets are used in system documentation to indicate
optional parameters. Brackets are not entered as part of a TL1 command.
When using &-grouping, a hyphen may be used after the ampersand. An example of STS-1
&-grouping is: OC3STS1-1-3-2-1&-4&-8-1. This is understood by the system as OC3STS1 ports
OC3STS1-1-3-2-1-1, OC3STS1-1-3-2-4-1, OC3STS1-1-3-2-8-1.
Ranging/Grouping capability is permitted on the last segment of an AID when that segment is
numeric. Specific AID types have additional rules.
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
"<Parsable_Output_Data>" cr lf ]*
[
/*
<Free_Form_Informational_Text>
*/ cr lf ]*
[
/*
Command_Echo>
[<CTAG>]
(<Session_Number>)*
*/ cr lf ]
;
For example:
Unsuccessful response messages have the following general content and format:
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
DENY cr lf
<Error_Code> cr lf
[
/*
<Expanded_Error_Code_Description>
*/ cr lf ]
[
/*
<Informational_Error_Description_Text>
*/]cr lf ]
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf ]
;
For example:
A single or partially successful response message contains an error code, which is a 4-character
mnemonic that indicates the cause of the failure. For example, IISP means "Input, Invalid Syntax or
Punctuation"; PICC means "Privilege, Invalid Command Code." The information displayed in the
successful or partially successful response message varies for different commands. Refer to the
Appendix A, “Software Reference Guide” in the back of this manual for a list of error codes and
definitions.
The following indexes are defined for indicating specific resources inside CLI commands:
1. ace_index An integer value indicating an element of an ACL.
18. ebs_value An integer number, in the range [0-min [64MB, 256 * corresponding_CBS]] with 1
byte granularity.
19. eir_value An integer number, in the range [3 kbit/s ... port line rate] with 1 kbit/s
granularity.
20. eqpt_type It identifies the type of the equipment item.
The possible equipment type are listed in the relevant 1850 Transport Service Switch (TSS-320,
TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.
21. ethertype_value A string composed of four hexadecimal characters.
22. extpointin_naming An integer number in the range [1 ... 8], indicating the specific
Housekeeping Input.
23. extpointout_naming An integer number in the range [1 ... 4], indicating the specific
Housekeeping Output.
24. eventtype_id An integer number, indicating the specific event type (within the allowed set) to
be associated to an output external point working in automatic mode.
25. eventtype_name A string equal to the specific event type string (within the allowed set) to be
associated to an output external point working in automatic mode.
26. filename A string indicating the name of file.
27. filterDbAgeTime_value A value in the set [280sec (default), 70min, 210min, 14h, 56h]
indicating the filtering database Aging Time (see 1850 Transport Service Switch (TSS-320,
TSS-320H and TSS-160) Release 5.1 TL1 User Provisioning Guide).
28. floodinglimit_value The ingress port admitted flooding rate expressed in kbit/s (see
1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 User
Provisioning Guide.
29. group_membership_interval An integer value, measured in seconds, with default value =
260.
30. hh:mm:ss Hour, an integer value in the range [0 ... 23]; minute, an integer value in the range [0
... 59]; second, an integer value in the range [0 ... 59].
31. ipAddr An IP address in string decimal dot-separated format: n.n.n.n
32. ipAddrBitMask An IP address netmask in decimal dot-separated format: n.n.n.n
33. lagsize_value An integer value, in the range [1 .. 16].
34. last_member_query_count An integer value, in the range [1 ... 255] and with default value =
2.
35. last_member_query_interval An integer value, measured in 0.1 seconds, in the range [1
... 255] and with default value = 10 (1sec).
36. macAddr A MAC Address in string hex dash-separated format: xx:xx:xx:xx:xx:xx
37. macBitMask A MAC Address bit mask in string hex dash-separated format:
xx:xx:xx:xx:xx:xx (e.g. FF:FF:E0:00:00:00)
38. maxEthertype_value Same syntax of ethertype_value. It indicates the upper bound of an
EtherType range.
39. maxdscp Same syntax of dscp. It indicates the upper bound of a DSCP range.
40. maxpri Same syntax of pri. It indicates the upper bound of a PRI range.
41. max_response_time An integer value, measured in 0.1seconds, in the range [1 ... 255] and
with default value = 100.
42. maxvlan_id Same syntax of vlan_id. It indicates the upper bound of a VLAN ID range.
43. mstp_instance The MSTP instance identifier. An integer value in the range [1 ... 63].
44. mstp_instance_set An expression using integer values in the range [1 ... 63] and specific
symbols for representing a set of MSTP instance value ranges. For instance 1-3&21 means that
the values 1, 2, 3 and 21 are specified.
45. mtu_value An integer value, indicating the MTU/MRU in byte. MTU/MRU allowed and default
values are listed in the relevant 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-
160) Release 5.1 TL1 User Provisioning Guide.
46. naming The following syntax is used for naming a resource to which a CLI command applies:
• rRsrSslBdDpP, where:
R Rack 1 ..... 7
S Subrack 0 or 1 ..... 7
B Board 0 or 1 ..... 63
D Drawer 0 or 1 ..... 7
P Port 0 or 1 ..... 1023
When a certain field is meaningless for naming a resource, this field is omitted in the naming.
In commands that apply to a board, the naming must have rack, subrack, board¼0
and drawer=port=0; in commands that apply to a port, the naming must have rack, subrack,
board, port¼0.
47. naming_set An expression using integer values in the range [1 ... 4094], ampersand (&) and
hyphen (-) for representing board, drawer or port value ranges; for instance:
• r1sr1sl4-7&18p1-5
means that the ports 1, 2, 3, 4 and 5 of the boards in slots 4, 5, 6, 7 and 18 are specified.
48. naming_set_list A list of naming set as naming_set#1 [naming_set#2 …
naming_set#n] an expression using integer values in the range [1 ... 4094], ampersand (&)
and hyphen (-) for representing board, drawer or port value ranges; for instance:
• r1sr1sl3-6&18p1-3
means that the ports 1, 2 and 3 of the boards in slots 3, 4, 5, 6 and 18
• r1sr1sl7-9&19p4-6
means that the ports 4, 5, 6 of the boards in slots 7, 8, 9 and 19 are specified.
49. neighbor_router_timeout An integer value, measured in seconds, with default value =
260.
50. ne_pri An integer value, in the range [0 ... 65535], indicating the priority value associated with
the Actor's NE.
51. nelocation A string indicating the location of the node.
52. ospfarea_index The ID of the corresponding OSPF area entry.
53. pbs_value An integer number, in the range [0-min to [64 MB, 256 * corresponding_CBS]] with
1 byte granularity.
54. pcause A string representing a probable cause are in the Table 4, “Alarm and cause
relationship” (p. 45).
55. pir_value An integer number, in the range [3 kbit/s ... port line rate] with 1 kbit/s granularity.
56. pkgversion It is a value in the form xx.xx.xx (e.g. 02.11.00) where:
• the first field represents the Major version
• the second field represents the Minor version
• the third field represents the Maintenance version
57. port_lnkaggpri Link Aggregation port priority (2 byte). An integer value in the range [0 ...
255] with default value = 128.
58. port_path_cost The port path cost. Its value depends on the link speed of the port (e.g. if
the link speed of the port is Mbit/s, port_path_cost = an integer value in the range [1 ... 200 000
000] and default value = 20 000 000.
59. port_pri Writable portion of the port identifier (the first 4 bit of 2 byte). An integer value in the
range [0 ... 240] with granularity 16 and default value = 128.
60. pri An integer value in the range [0 ... 7], indicating the Priority (or the lower bound of a PRI
range).
61. pri_set An expression using integer values in the range [0 ... 7], and specific symbols for
representing a set of PRI value ranges which are associated to green in that color profile.
For instance 0-3&5 means that the PRI values 0, 1, 2, 3 and 5 are associated to green in that
color profile.
62. priyellow An integer value in the range [0 ... 7], indicating the Priority of the yellow frames.
63. profile The list of network functionalities enabled on the NE, in the set: 'sdh', 'wdm', 'eth',
'mpls' and 'cp'.
64. ratelimited_value The maximum allowed rate, measured in Kbit/s, configured on
GFP/LAPS ports.
65. region_revision_level The MSTP region revision level. An integer value in the range [0 ...
65535].
66. reporting_interval An integer value, measured in seconds, with default value = 60.
67. resptimeout An integer number, measured in seconds, in the range [0 ... 3600].
68. router_timeout An integer value, measured in seconds, with default value = 260.
69. severity The associated severity in the set: 'critical', 'major', 'minor', 'warning' and
'indeterminate'.
70. transportPortNumber An integer number.
71. user_login A string representing the user login.
72. user_profile The security user profile, in the set: 'administrator', 'constructor', 'operator' and
'viewer'.
73. vlan_id An integer value in the set [1 ... 4094], indicating the VID (or the lower bound of a
VLAN ID range).
74. vlan_set An expression using integer values in the range [1 ... 4094] and specific symbols for
representing a set of VLAN value ranges.
For instance 100-103&2555 means that the VLAN values 100, 101, 102, 103 and 2555 are
specified.
75. yy:mm:dd Year, an integer value in the range [1 ... 99]; month, an integer value in the range [1
... 12]; day, an integer value in the range [1 ... 31].
The following indexes (xxx_userlabel) are defined by the Operator for indicating specific resources
inside CLI commands:
1. acl_userlabel An ASCII string defined by the Operator.
2. alarmprofile_userlabel An ASCII string defined by the Operator.
3. asap_userlabel An ASCII string defined by the Operator.
4. colorprof_userlabel An ASCII string defined by the Operator.
5. extpoint_userlabel An ASCII string defined by the Operator.
6. flow_userlabel An ASCII string defined by the Operator.
7. flowgroup_userlabel An ASCII string defined by the Operator.
8. lag_userlabel An ASCII string defined by the Operator.
9. ne_userlabel An ASCII string defined by the Operator.
10. trafficdescriptor_userlabel An ASCII string defined by the Operator.
11. vlanprof_userlabel An ASCII string defined by the Operator.
12. vlanprotprof_userlabel An ASCII string defined by the Operator.
Alarm pcause
Card Fail rup
Card Mismatch rutm
Card Out rum
Unconfigured Equipment uep
OR Battery Failure batteryfail
Fuse Broken fusebroken
SLC Unreachable icp
LDC Unreachable icp
LAN Alarm lanfailure
Software Mismatch versionmismatch
Excessive Environmental
excessiveenvironmentaltemperature
Temperature
Link Failure receiverfailure
Housekeeping not available housekeepingalarm
PLM plm
TSF tsf
TSD / DEG sdhconcdegrade
LOS los
Alarm pcause
LOF lof
CSF csf
EXM extensionheadermismatch
UPM userpayloadmismatch
URU uru
UAT uat
TCA tca
12. CLI is allowed to perform 'set' operations only if it has granted local access control.
There is one exception: the set operation for requesting the access control itself.
13. When the NE is able to support both "condition" and "change" management function of a certain
parameter, the command, defined in this document for setting that parameter, refers always to
the "change" management function. This policy has to be applied independent of which of the
two management function ("change" or "condition") is referred in the command reference
section.
The CLI is expected to perform most of the CT functionalities. The CLI is not required to be used for
managing the following functionalities:
• Support Domain:
− Event Reporting: the CLI does not manage spontaneous notifications from the NE;
− PM Filtering: the CLI does not manage own filtering criteria for retrieving History Data from
the NE;
− MIB Backup/Restore and SW download: this topics are for future releases.
For managing by CLI the functionalities about file transfer between the NE and a server,
issues about the used transfer protocol (802.1e, FTP, ...) have to be deeply analyzed.
• C&R domain:
− Tunnel management: this functionality is not required in the NE.
2 Getting started
2.1 Overview
2.1.1 Purpose
This chapter contains a procedure to initiate a TL1 or CLI session.
2.1.2 Contents
2.1 Overview 49
2.2 TL1 and CLI sessions 49
2.2.2 Tools
For the these procedures the following tools are necessary:
2.2.3 Procedure
1
Connect the console using the LAN cable as in Table 5, “Necessary tools” (p. 49)) to MT320/
MT160 unit as shown in the following picture.
2
Select Start -> Run path, and in the Run dialogue box select the CMD item in the Open:
combo-box, as shown in the following picture:
3
Press OK button to activate the command console as shown in the following picture:
4
Enter the session to be opened (i.e. telnet) followed by the "Node IP Address" (i.e.
xxx.xxx.xxx.xxx) and the "telnet port number" (i.e. 3083), as shown in the following picture:
5
Press Enter key, and the client area console shows the prompt and the window header shows
the node address, as shown in the following picture:
6
Now it is possible to log the system by means of the "user identifier" and "password identifier"
entering, as shown in the following picture:
ACT-USER::UID:::PID;
where:
• UID = User Identifier, specifies a unique user ID. Valid values for UID are <5-12 VALID UID
CHARACTERS>, case-sensitive alphanumeric characters where the first character must
always be an alphabetic character.
• PID = Password Identifier, specifies the user's login password. Valid values for PID are a
string of <8-12 VALID PID CHARACTERS> case-sensitive alphanumeric characters.
for further details, see 6.57 “Log Into System” (p. 354).
7
The response for a successful access is the following:
8
Now it is possible to enter a command, e.g. with the RTRV-EQPT::ALL; the relevant response
is the following:
END OF STEPS
3.1 Overview
3.1.1 Purpose
IXLs group procedures by function. Each IXL lists procedures alphabetically by name and refers the
user to the appropriate procedure number.
3.1.2 Contents
3.1 Overview 57
3.2 IXL-1: User Administration 58
3.3 IXL-2: Equipment Functions 58
3.4 IXL-3: Equipment Provisioning and Deprovisioning 59
3.5 IXL-4: System Information Reports 59
3.6 IXL-5: System Administration 60
3.7 IXL-6: VCG Functions 60
3.8 IXL-7: T-MPLS/MPLS-TP Functions 61
3.9 IXL-8: VC & LOVC Functions 62
3.10 IXL-9: SDH Functions 62
3.11 IXL-10: ODU Functions 62
3.12 IXL-11: OTU Functions 63
3.13 IXL-12: Ethernet Functions 63
3.14 IXL-13: Maintenance Operation 64
3.15 IXL-14: Control Plane Functions 64
3.16 IXL-15: WDM Functions 64
3.17 IXL-16: ATM Functions 65
3.18 IXL-17:Security Functions 65
3.19 IXL-18: 1662 Drop Shelf Equipment Functions 66
3.20 IXL-19: Enhanced Shelf Equipment Functions 66
FUNCTION
6.2 “Add New User to System” (p. 138)
6.44 “Change User Password” (p. 294)
6.46 “Delete User from System” (p. 308)
6.48 “Disable/Enable User Account” (p. 314)
6.52 “Edit User Profile” (p. 337)
6.58 “Log Out of System” (p. 355)
6.83 “Set System-Wide User Security Parameters” (p. 432)
FUNCTION
6.3 “Administer ASAP” (p. 139)
6.35 “Administer System Configuration” (p. 253)
6.41 “Auto Discovery Function” (p. 284)
6.18 “Administer MAU Facility” (p. 193)
6.21 “Administer NE IP Route” (p. 200)
6.22 “Administer NE IP Tunnel” (p. 203)
6.51 “Display Status and Conditions” (p. 329)
6.53 “Housekeeping Alarms Management” (p. 341)
6.54 “Housekeeping Controls Management” (p. 345)
6.55 “Initialize System Processors” (p. 348)
FUNCTION
6.62 “Perform Audible Alarm Cutoff” (p. 366)
6.63 “Perform Module Protection Switch or Copy Switch” (p. 367)
6.69 “Remove/Restore Equipment” (p. 393)
8.22 “Set Performance Monitoring (PM) Data for T-MPLS” (p. 552)
6.81 “Slave TOD Card Management” (p. 424)
6.59 “Master TOD Card Management” (p. 357)
6.42 “Boundary TOD Card administration” (p. 285)
FUNCTION
6.47 “Deprovision Equipment” (p. 308)
6.67 “Provision Equipment” (p. 385)
6.72 “Retrieve Module Remote Inventory Information” (p. 402)
FUNCTION
6.30 “ Administer Security Log File” (p. 232)
6.49 “Display Alarms” (p. 319)
6.70 “Report Performance Monitoring (PM) Data” (p. 397)
6.74 “Retrieve System Configuration” (p. 406)
FUNCTION
6.75 “Retrieve TL1 Command Syntax” (p. 409)
6.76 “Retrieve User Session Information” (p. 410)
FUNCTION
6.6 “Administer Database Backup” (p. 150)
6.7 “Administer Database Restore ” (p. 152)
6.20 “Administer Network Interface” (p. 199)
6.23 “Administer Network Time Protocol (NTP)” (p. 207)
6.36 “Administer System Timing/BITS” (p. 255)
6.55 “Initialize System Processors” (p. 348)
6.64 “Perform Remote Database Backup” (p. 369)
6.65 “Perform Remote Database Restore” (p. 375)
6.71 “Retrieve and Change Site Identifier” (p. 400)
6.77 “Retrieve/Provision IP Address of NE” (p. 414)
8.22 “Set Performance Monitoring (PM) Data for T-MPLS” (p. 552)
6.82 “Set System Date and Time” (p. 430)
FUNCTION
6.39 “Administer VC Cross-Connection” (p. 267)
6.40 “Administer VCG Facility” (p. 277)
6.56 “LCAS Monitoring” (p. 351)
6.88 “Virtual Concatenation Path Check” (p. 442)
FUNCTION
6.16 “Administer L2 Encapsulation Profile” (p. 186)
6.28 “Administer Per Hop Behaviour Profile (PHBprofile)” (p. 227)
8.7 “Administer T-MPLS Facility Protection Group” (p. 497)
8.8 “Administer T-MPLS Global Network Parameters” (p. 502)
8.10 “Administer T-MPLS OAM (T-MPLS Tunnel protection)” (p. 507)
8.11 “Administer T-MPLS Pseudo Wire” (p. 510)
8.12 “Administer T-MPLS Pseudo Wire Segment” (p. 514)
8.13 “Administer T-MPLS Pseudo Wire Segment Cross-Connection” (p. 517)
8.14 “Administer T-MPLS Traffic Descriptor” (p. 521)
8.15 “Administer T-MPLS Tunnel” (p. 524)
8.16 “Administer TMPLS Tunnels Group” (p. 528)
8.17 “Administer T-MPLS Tunnel Segment” (p. 531)
8.18 “Administer T-MPLS Tunnel Segment Cross-Connection” (p. 535)
8.21 “Report Performance Monitoring (PM) Data for T-MPLS” (p. 550)
8.22 “Set Performance Monitoring (PM) Data for T-MPLS” (p. 552)
6.50 “Display MPLS interface parameters” (p. 328)
8.6 “Administer (T-MPLS/MPLS-TP) DM tool ” (p. 491)
FUNCTION
8.9 “Administer T-MPLS/ MPLS-TP Node configuration” (p. 504)
8.19 “Proactive DM ” (p. 538)
8.20 “ Proactive LM (Synthetic Loss Measurement)” (p. 543)
FUNCTION
6.39 “Administer VC Cross-Connection” (p. 267)
6.45 “Convert a Cross-Connection” (p. 296)
FUNCTION
6.31 “ Administer STMn Facility” (p. 235)
6.32 “Administer STM-n Facility Protection Group” (p. 237)
6.34 “Administer STMn MS-SPRING” (p. 245)
6.84 “Switch STMn Line to Protection” (p. 434)
6.85 “Switch VCn Line to Protection” (p. 437)
FUNCTION
6.25 “Administer ODU2 Facility” (p. 212)
4.17 “ODU2 Deprovisioning” (p. 92)
4.18 “ODU2 Provisioning” (p. 93)
FUNCTION
6.26 “Administer OTU2 Facility” (p. 218)
4.19 “OTU2 Deprovisioning” (p. 94)
4.20 “OTU2 Provisioning” (p. 94)
FUNCTION
6.8 “Administer Ethernet Facility ” (p. 155)
6.18 “Administer MAU Facility” (p. 193)
10.10 “ Ethernet Port management (over MAU)” (p. 595)
10.7 “Administer Traffic Descriptor” (p. 589)
10.16 “VPLS Instance Management” (p. 608)
FUNCTION
6.45 “Convert a Cross-Connection” (p. 296)
FUNCTION
5.2 “Administer T-MPLS Control Plane Global Parameters” (p. 110)
5.4 “Administer Control Plane - IP Route” (p. 115)
5.5 “ Administer Control Plane - Tranport Port” (p. 119)
5.8 “Administer Control Plane Hoplist” (p. 129)
8.14 “Administer T-MPLS Traffic Descriptor” (p. 521)
8.15 “Administer T-MPLS Tunnel” (p. 524)
5.6 “Administer Control Plane - OSPF routing” (p. 122)
FUNCTION
6.10 “Administer Line Optical Connection Management” (p. 163)
6.11 “ Administer PassThrough Optical Connection Management” (p. 167)
FUNCTION
6.12 “ Administer Cascade Optical Connection Management” (p. 171)
6.13 “ Administer ADD/DROP Optical Connection Management” (p. 175)
FUNCTION
4.2 “ATM Protection Provisioning” (p. 68)
6.4 “Administer Duplex Switching Equipment Protection Group” (p. 143)
6.5 “Administer Duplex Switching ATM Protection Group” (p. 147)
FUNCTION
4.13 “NE Secure mode configuration” (p. 83)
4.14 “NE Unsecure mode configuration” (p. 84)
6.29 “Administer Radius server” (p. 229)
6.38 “Administer Users with Security Administrator Privileges” (p. 263)
6.68 “Radius server authentication ordering” (p. 390)
6.78 “Security Defaults Administration” (p. 417)
6.86 “System Access Control (intrusion alarm)” (p. 439)
FUNCTION
9.3 “1662SMC drop shelf management” (p. 559)
9.4 “Administer 1662 Subshelf E1 cards” (p. 561)
9.6 “1662 Subshelf Facilities Administration” (p. 565)
9.7 “Database backup and restore from remote file server on 1662 subshelf” (p. 569)
9.8 “1662 subshelf PM Administration (E1)” (p. 571)
9.9 “1662 subshelf PM Administration (STM4)” (p. 573)
FUNCTION
7.2 “Provision Equipment (S320H)” (p. 451)
7.3 “Administer S320H module” (p. 455)
4.1 Overview
4.1.1 Purpose
NTPs list the major steps required to complete a task. This list may be all an experienced user
requires. For an inexperienced user, each step refers to a DLP. The steps must be performed in the
order listed.
4.1.2 Contents
4.1 Overview 67
4.2 ATM Protection Provisioning 68
4.3 Basic Control Plane TL1 Provisioning sequence 71
4.4 Bicast&Merge provisioning 73
4.5 CP Provisioning 74
4.6 Ethernet Deprovisioning 76
4.7 Ethernet Provisioning 76
4.8 In Fiber In Band for Control Plan Provisioning 77
4.9 LAG Deprovisioning 78
4.10 LAG Provisioning 79
4.11 LER Tunnel Management (Tunnel Terminated) 81
4.12 LSR Tunnel Management (Label swap and Tunnel not Terminated) 82
4.13 NE Secure mode configuration 83
4.14 NE Unsecure mode configuration 84
4.15 SSH keys configuration 85
4.16 SSL keys configuration 88
4.17 ODU2 Deprovisioning 92
4.18 ODU2 Provisioning 93
4.19 OTU2 Deprovisioning 94
4.20 OTU2 Provisioning 94
4.21 PW Stitching Management (Case of label swap) 95
4.22 PW Termination Management (Case of point-to-point) 96
4.2.2 Prerequisites
The node should be equipped with the following boards (and their modules):
• the MultiService Adaptation Card for ATM (PP10GATM)
• the SDH card (for example the 8PSO)
• the DATA card (for example the PP1GE).
Note: In the Procedure example description the cards listed above have been used.
4.2.3 General
4.2.4 Procedures
1
Provision boards and modules. No module provisioning for the ATM board.
For details, refer to 6.67 “Provision Equipment” (p. 385).
Example:
This command creates 32 ATM interfaces (one side TDM and the other side SNMP)
2
TDM side: create the VC4 cross-connection, i.e. between the AUn and the VCn..
For details, refer to 6.39 “Administer VC Cross-Connection” (p. 267).
Example: ENT-CRS-VC4::STM1AU4-1-1-35-1-1,ATMVC4-1-1-19-1;
ENT-CRS-VC4::ATMVC4-1-1-12-1&&-31,STM64AU4-1-1-22-1-1&&-31:::2WAY;
Note: ATM interfaces are in an alarmed state if they are not crossconected (no ENT-CRS-
VC4 is entered on the ATM IF i.e. they are in an UNEQUIPPED state). To view alarms
enter: rtrv-alm-all;
3
On the SNMP (i.e. CLI) side: the ATM interfaces administrative status are UP (it is not possible
to put them down) and they coud be cross-connected only to terminated PW (no VPLS).
4
Create the PW, for details see 4.22 “PW Termination Management (Case of point-to-point)”
(p. 96).
Example:
• ENT-TMPLS-TD::::::CIR=100000,PIR=100000,CBS=12800,PBS=12800;
• ED-TMPLS-PW::PW-1-1-1::::TD-ID=MPLSTD-2,STATUS=ON;
5
Create the ATM on PW cross-connection. For details refer to 8DG09603EAAATQZZA
1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 Command
Line Interface Guide.
Example: This example creates, configures and activates an ATM ETS InFlow and PW-ATM
(or ATM) ETS OutFlow on which it is transported. This command creates also the uni-directional
cross-connection between them, i.e. cross-connection between the mpls port r1sr1sl19d0p1
and the PW pw1 created before:
6
Create the PW on ATM cross-connection, for details refer to 8DG09603EAAATQZZA
1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 Command
Line Interface Guide.
Example: This example allows to create, configure and activate a uni-directional cross-
connection between a PW-ATM ETS InFlow and ATM ETS OutFlow, i.e. cross-connection
between the PW pw1 and the mpls port r1sr1sl19d0p1:
pwatmflowunidir activate pw 1 port2 r1sr1sl19d0p1 outtraffictype gua
7
Create the ATM Protection Group. A duplex switching equipment protection group out of two
unprotected equipment entities is created with the TL1 command: ENT-DX-EQPT. For details
see 6.4 “Administer Duplex Switching Equipment Protection Group” (p. 143)
Example: The example below to create the EPS Protection Group between two Adaptation
Card Packet Modules 10G ENT-DX-EQPT::PP10AD-1-1-5,PP10AD-1-1-6;
8
To manage the ATM Protection Group refer to 6.4 “Administer Duplex Switching Equipment
Protection Group” (p. 143) and to 6.5 “Administer Duplex Switching ATM Protection Group”
(p. 147).
END OF STEPS
4.3.2 Prerequisites
For more information about TL1 command syntax, system responses, and an explanation of error
messages refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1
TL1 Command Guide.
For more information about CLI command syntax, refer to 8DG09603EAAATQZZA —
1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 Command Line
Interface Guide.
To create a control plane link minimum 2 NE are necessary and only point-to-point configuration is
available. Each 1850 TSS-320, TSS-320H and TSS-160 shall be equipped with one or more DATA
boards.
All ports involved in the CP link should have MPLS interface.
The control plane signaling should be in band in fiber.
4.3.3 General
None.
4.3.4 Procedures
TL1 side:
1. Provision board and unit.
For details, refer to 6.67 “Provision Equipment” (p. 385).
2. Provision the Network Interface on a specified DCC channel on an optical port for data
communication purposes. See 6.20 “Administer Network Interface” (p. 199).
CLI side:
• Verify that the ETS ports created in the step before are present, refer to 10.12 “General
Interface Management” (p. 599).
• Retrieve port mau configuration (i.e. in order to see if the ports have same mau
configurations), refer to 10.9 “ Ethernet Physical management” (p. 593).
• Create the mpls port, refer to 10.10 “ Ethernet Port management (over MAU)” (p. 595).
• Activate mpls interface, i.e. enable MPLSIF administrative status, refer to 10.10 “ Ethernet
Port management (over MAU)” (p. 595).
TL1 side:
• Provision the Node IP address, OSPF Area Identifiers, refer to 5.2 “Administer T-MPLS
Control Plane Global Parameters” (p. 110).
• Provision Control Plane Transport Port, refer to 5.5 “ Administer Control Plane - Tranport
Port” (p. 119).
• Provision Control Channels, refer to 5.3 “ Administer Control Plane - Control Routing Port”
(p. 111).
• Provision Traffic Descriptor, refer to 8.14 “Administer T-MPLS Traffic Descriptor” (p. 521).
• Build I-NNI tunnels , refer to 8.15 “Administer T-MPLS Tunnel” (p. 524)
4
Repeat steps 1-3 for the second NE.
END OF STEPS
4.4.2 Prerequisites
None.
4.4.3 General
The procedure explains how to configure the TMPLS Tunnels Group, constituted by two Terminated
Tunnels; one of the two Tunnel is called Working TUNNEL and the other is called Protecting
TUNNEL.
At node level the NE generates TMPLS OAM (the default value is T-MPLS). To change to MPLS-TP
refer to 8.9 “Administer T-MPLS/ MPLS-TP Node configuration” (p. 504).
4.4.4 Procedures
1
Via TL1:
Provision boards and modules.
For details, refer to 6.67 “Provision Equipment” (p. 385).
Via TL1:
1. Create the Traffic Descriptor (CIR E PIR of both Main and Spare Tunnel should be equal),
see 8.14 “Administer T-MPLS Traffic Descriptor” (p. 521).
2. Create the MAIN tunnel, providing as reference the MPLS port interface (see Step 2),
i.e.ADD-GROUP should be default value, see 8.15 “Administer T-MPLS Tunnel” (p. 524)
3. Create the SPARE tunnel, providing as reference the MPLS port interface (see Step 2)
i.e. ADD-GROUP should be set to the TRUE value, see 8.15 “Administer T-MPLS Tunnel”
(p. 524).
Main e Spare should use same INLABEL value.
4. Configure some of the automatic created tunnel parameters (i.e. VTs, Traffic Descriptor,
Tunnel Status).
See 8.15 “Administer T-MPLS Tunnel” (p. 524).
5. Create the TMPLS Tunnel Group, see 8.16 “Administer TMPLS Tunnels Group” (p. 528).
6. Create PW on the MAIN Tunnel, see 4.23 “PW Termination Management (Case of VPLS)”
(p. 97).
7. Create and activate an VPLS instance see 10.16 “VPLS Instance Management” (p. 608)
For details, refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160)
Release 5.1 Command Line Interface Guide.
8. Create, configure and activate ETS InFlow/OutFlow and the Provider Bridge/PW/VPLS
ETS InFlow/OutFlow on which it is transported. Creates also the crossconnection between
them, see 10.4 “ Administer ETS to Provider Bridge ETS/PW/VPLS bidirectional flow ”
(p. 582).
For details, refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160)
Release 5.1 Command Line Interface Guide
END OF STEPS
4.5 CP Provisioning
4.5.1 Purpose
This procedure provides instructions and sequence to provision Control Plane.
4.5.2 Prerequisites
For information about TL1/CLI command syntax, system responses, and an explanation of error
messages refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1
TL1 Command Guide and to 8DG09603EAAATQZZA — 1850 Transport Service Switch (TSS-320,
TSS-320H and TSS-160) Release 5.1 Command Line Interface Guide
To create a control plane link minimum 2 NE are necessary and only point-to-point configuration is
available. Each 1850 TSS-320, TSS-320H and TSS-160 shall be equipped with one or more DATA
boards.
4.5.3 General
Ports involved in a CP can belong to the same data board type and should be allocated in different
NE boards (i.e. minimum configuration shall have 2 NEs). All ports involved in the CP link should
have MPLS interface.
4.5.4 Procedures
1
TL1 side:
Provision board and unit.
For details, refer to 6.67 “Provision Equipment” (p. 385).
CLI side:
• Verify that the ETS ports created in the step before are present, refer to 10.12 “General
Interface Management” (p. 599).
• Retrieve port mau configuration (i.e. in order to see if the ports have same mau
configurations), refer to 10.9 “ Ethernet Physical management” (p. 593).
• Create the mpls port, refer to 10.10 “ Ethernet Port management (over MAU)” (p. 595).
• Activate mpls interface, i.e. enable MPLSIF administrative status, refer to 10.10 “ Ethernet
Port management (over MAU)” (p. 595).
TL1 side:
• Set the Node IP address, OSPF Area Identifiers, refer to 5.2 “Administer T-MPLS Control
Plane Global Parameters” (p. 110).
• Activate the control plane, refer to 5.3 “ Administer Control Plane - Control Routing Port”
(p. 111).
• Activate dataplane interfaces managed by the control plane, refer to 5.5 “ Administer Control
Plane - Tranport Port” (p. 119).
4
Repeat steps 1-3 for the second NE.
END OF STEPS
4.6.2 Prerequisites
If the facility provisioning mode of this NE is automatic, i.e., PROVMODE=AUTOEQ-AUTOFC, then
delete commands cannot be used to erase facilities. In this mode, facility deletion occurs only when
the supporting equipment or logical resource is deleted (see6.35 “Administer System
Configuration” (p. 253))
4.6.3 General
The delete TL1 command deprovisions the specified GBE object entity.
4.6.4 Procedure
1
Deprovision the specified GBE object entity.
For details, refer to 6.8 “Administer Ethernet Facility ” (p. 155).
END OF STEPS
4.7.2 Prerequisites
The node should be equipped with one of the following boards:
• 8XSO
• 10GSO
• 10XANY
• DWLA10X
4.7.3 General
Gigabit Ethernet facilities are associated with ports on a GBE module, and support GBEVCG
facilities for EPL point to point ethernet transmission.
4.7.4 Procedures
1
Provision board.
For details, refer to 6.67 “Provision Equipment” (p. 385).
2
Provision Ethernet facility.
For details, refer to 6.8 “Administer Ethernet Facility ” (p. 155).
END OF STEPS
4.8.2 Prerequisites
The node should be equipped with one of the data boards.
For “Vlan based” In Fiber In Band Management Interface it is verified that the Vlan ID is not already
in use; and for “MPLS label based” In Fiber In Band Management Interface is defined on a MPLS
port and that the MPLS label is not already in use.
Important: the MPLS port should not be active
4.8.3 General
“In Fiber In Band” for management plane applies to both local and/or remote Ethernet interface,
Link Aggregation Interface and MPLS Interfaces, leading to definition of a logical “In Fiber In Band”
management interface:
4.8.4 Procedures
1
Provision board and unit.
For details, refer to 6.67 “Provision Equipment” (p. 385).
2
Verify (CLI side) the unit type provisioned in Step 1.
For details, refer to 10.12 “General Interface Management” (p. 599).
3
Choose (CLI side) the “VLAN based” or “MPLS Label based” In Fiber In Band Management
Interface.
For details, refer to 10.10 “ Ethernet Port management (over MAU)” (p. 595).
For details, refer to 10.15 “ VLAN protocol profile Management ” (p. 605).
4
Define (CLI side) the “VLAN based” or “MPLS label based”In Fiber In Band Management
Interface.
For details, refer to 10.6 “Administer In Fiber In Band for Control Plan” (p. 587).
END OF STEPS
4.9.2 Prerequisites
All services defined for the LAG should be removed before the LAG deletion.
4.9.3 General
LAG is deactivated after removal of the aggregated port set. Ports are removed from LAG with their
administrative status set to down. LAG deactivation is then achieved is similar way.
4.9.4 Procedure
1
Retrieve board and the module.
On CLI side follow the steps below to deprovision the Link Aggregation:
• Unbind ports from LAG see 10.14 “ LAG Management ” (p. 602)
• Disable LAG administrative status see 10.14 “ LAG Management ” (p. 602)
• Delete LAG see 10.14 “ LAG Management ” (p. 602).
• Verify LAG is not present, see 10.12 “General Interface Management” (p. 599)
END OF STEPS
4.9.5
Note: If LAG ETS client type is set then classifier, traffic descriptor and UNI-NNI (and/or NNI-
UNI) crossconnections should be defined (i.e. the LAG should be treated as an ETS
interface).
Note: It must be remarked that, policing rate that can be applied for flooding control should
be:
• On board basis.
A single rate policer is applied to all ingress aggregation ports of a LAG.
• On port basis.
A rate policer is applied to each ingress aggregation port of a LAG. This case happens
when AP ports (Ethernet local interfaces) are located on different boards inside the NE.
4.10.2 Prerequisites
The 1850 TSS-320, TSS-320H and TSS-160 shall be equipped with one or more DATA boards.
Ports involved in a LAG can belong to the same data board or can be allocated in different boards.
• Actor and Partner ports (local and far sides) must be of the same type.
4.10.3 General
The system supports the Link Aggregation (LAG) at the Ethernet side, as specified in IEEE Std.
802.3ad-2000; it is a technique to aggregate many data streams into a single logical link. The
resulting aggregate link will be treated by the system (with regard to instances about IGMP, network
protections, etc.), as a single link.
4.10.4 Procedure
1
Provision board and the module.
For details, refer to 6.67 “Provision Equipment” (p. 385).
END OF STEPS
4.10.5
Note: If LAG ETS client type is set then classifier, traffic descriptor and UNI-NNI (and/or NNI-
UNI) crossconnections should be defined (i.e. the LAG should be treated as an ETS
interface).
Note: It must be remarked that, policing rate that can be applied for flooding control should
be:
• On board basis.
A single rate policer is applied to all ingress aggregation ports of a LAG.
• On port basis.
A rate policer is applied to each ingress aggregation port of a LAG. This case happens
when AP ports (Ethernet local interfaces) are located on different boards inside the NE.
4.11.2 Prerequisites
The 1850 TSS-320, TSS-320H and TSS-160 shall be equipped with one or more DATA boards.
4.11.3 General
At node level the NE generates TMPLS OAM (the default value is T-MPLS). To change to MPLS-TP
refer to 8.9 “Administer T-MPLS/ MPLS-TP Node configuration” (p. 504).
4.11.4 Procedure
1
Via TL1:
Provision boards and modules.
For details, refer to 6.67 “Provision Equipment” (p. 385).
Via TL1:
1. Create the Traffic Descriptor, see 8.14 “Administer T-MPLS Traffic Descriptor” (p. 521).
2. Create the tunnel providing as reference the MPLS IF interface (see Step 2), i.e.creation of
the unique terminated segment, see 8.15 “Administer T-MPLS Tunnel” (p. 524).
3. Configure parameters (VTs, Traffic Descriptor) of automatic created tunnel. See
8.15 “Administer T-MPLS Tunnel” (p. 524).
END OF STEPS
4.12 LSR Tunnel Management (Label swap and Tunnel not Terminated)
4.12.1 Purpose
This procedure provides instructions and sequence to provision an LSR Tunnel (i.e. with label swap
and tunnel not terminated).
4.12.2 Prerequisites
The 1850 TSS-320, TSS-320H and TSS-160 shall be equipped with one or more DATA boards.
4.12.3 General
At node level the NE generates TMPLS OAM (the default value is T-MPLS). To change to MPLS-TP
refer to 8.9 “Administer T-MPLS/ MPLS-TP Node configuration” (p. 504).
4.12.4 Procedure
1
Via TL1:
Provision boards and modules.
For details, refer to 6.67 “Provision Equipment” (p. 385).
Via TL1:
1. Create the Traffic Descriptor, see 8.14 “Administer T-MPLS Traffic Descriptor” (p. 521).
2. Create the first segment, providing as reference the MPLS IF (interface) created in Step 2.
Refer to 8.17 “Administer T-MPLS Tunnel Segment” (p. 531).
3. Create the second segment, providing as reference the MPLS IF (interface) created in
Step 2. Refer to 8.17 “Administer T-MPLS Tunnel Segment” (p. 531).
4. Create the tunnel, i.e.cross-connection between two segments (label swap), see
8.18 “Administer T-MPLS Tunnel Segment Cross-Connection” (p. 535).
5. Modify the created tunnel and to associate to the tunnel a traffic descriptor and defined VTs
(Virtual Transport). See 8.15 “Administer T-MPLS Tunnel” (p. 524).
Note: With TUSEG creation it is possible to provide the indication of the PHB profile
associated to the segment and OAM configuration associated to the segment.
END OF STEPS
4.13.2 General
The NE can work either in secure or unsecure mode: when in secure mode all communications
between the customer and the NE shall be alowed only with strong encryption and cryptographic
protection in order to provide confidentiality, integrity, and replay protection.
By default the NE shall start in UNSECURE mode. This allows backward compatibility towards
existing NMS that do not support encryption.
When the NE is in secure mode, the secure connection between the user and the NE shall be
accomplished by means of mutual authentication, on the basis of the exchange of their public keys.
In this case the NE (SSH/SSL server) shall support preinstalled OS (SSH/SSL client) public keys
and certificate.
The TL1 command SET-ATTR-SECUDFLT shall provide the capability of configuring the NE is
secure or unsecure mode
When the NE is in secure mode it shall support SSH-2 encryption protocol for TL1 and CLI, SSL
encryption for HTTPS.
Note that for what concerns SNMP, “SNMPv3” only shall be supported when in secure mode.
When the NE is in unsecure mode, both “SNMPv2” and “SNMPv3” shall be supported
4.13.4 Procedure
1
Login into the NE using the SECU-admin user.
2
Set the NE SECURE MODE enter:
SET-ATTR-SECUDFLT::::::SECACC=SECURE;
Secure Access for the NE. If access is SECURE, then the system supports secure connections
via encryption; only ports 6084 and 6085 (TL1), 6086 (CLI), 22 (debug port for ROOT access
always with SSH) and 443 (HTTPS) are opened and the NE shall support SNMPv3 and shall
3
Verify the NE secure has been set to SECURE MODE, enter:
RTRV-DFLT-SECU;
When SECACC is set to SECURE the NE shall use SFTP to transfer files to/from the NE.
Select action:
• Establish a SSH2 session using SecureCRT on port 6084 for TL1.
• Establish a SSH2 session using SecureCRT on port 6085 for TL1.
• Establish a SSH2 session using SecureCRT for port 6086 for CLI.
• Access debug port for ROOT access always with SSH for port 22
• Manage NE using SSL protocol https://<ipaddress>:443
Result: Secure connection is created via encryption
Note: When NE secure mode configuration fails (e.g. failed exchange of public-
keys). please configure the NE unsecure mode and update keys manually.
END OF STEPS
4.14.2 General
The NE first installation is done always in UNSECURE mode.
When in unsecure mode all the protocols/ports are available (SSH/SSL/SNMPv3 are available).
4.14.4 Procedure
1
Login into the NE .
2
Set the NE UNSECURE MODE enter:
SET-ATTR-SECUDFLT::::::SECACC=UNSECURE;
If UNSECURE, then the system supports TL1 connections to port 3082 and 3083 (TL1), 1123
(CLI), 22 (debug port for ROOT access always with SSH), 23 (port for telnet) and 80 (http) are
opened.
3
Verify the NE secure has been set to UNSECURE MODE, enter:
RTRV-DFLT-SECU;
Select action:
• Establish a SSH2 session using SecureCRT on port 3082 for TL1.
• Establish a SSH2 session using SecureCRT on port 3083 for TL1.
• Establish a SSH2 session using SecureCRT for port 1123 for CLI.
• Establish a session using telnet for port 23 for CLI.
• Access debug port for ROOT access always with SSH for port 22
• Manage the NE on http://<ipaddress>:80
Note: Connections to ports 6084, 6085 and 6086 are available also in unsecure mode
END OF STEPS
4.15.2 General
The new pair of SSH keys on the NE is used by the NE for establishing new sessions. Because an
SSH session uses asymmetric encryption by means of public & private keys for initial authentication
phase, currently existing sessions remain open and working. The new session is symmetrically
encrypted by means of a common shared secret key, which is exchanged after authentication
completion, and remains valid for the entire session.
The NMS can transfer and install the NMS SSH public key onto the NE via COPY-RFILE.-SECU
TL1 command. The NE adds that key to its own NMS SSH public keys list, in order to accept
connections form that NMS too, from that point on.
4.15.4 Procedure
1
Do you wish to initiate the generate and install a new pair of SSH keys (public and private) for
NE or NMS?
If... Then...
NE Continue with Step 2.
NMS Proceed to Step 6.
2
Login into the NE using the SECU-admin.
3
Enter INIT-SSH-KEY. The NE generates and install a new pair of SSH keys (public and
private) for the NE.
4
The NE transfers and installs the SSH public key onto the NMS:
enter COPY-RFILE-SECU.
The NMS adds that key to its own SSH public keys list, in order to accept connections from that
NE too, from that point on.
Result: REPT^EVT^SECU with CONDTYPE=OSSSHKEY is sent when COPY-RFILE-SECU
with FROM=LOCSSHKEY and TO=RFSSSHKEY is successfully completed.
5
A user with security privileges can retrieve the NE SSH public key, keytype and key-length, by
means of the RTRV-SSH-KEY TL1 command.
6
The NMS generates new SSH keys.
7
The NMS triggers the NE to transfer the NMS SSH public key.
enter COPY-RFILE-SECU.
The NE adds that key to its own SSH public keys list, in order to accept connections from that
NMS too, from that point on.
Result: REPT^EVT^SECU with CONDTYPE=OSSSHKEY shall be sent when
COPY-RFILE-SECU with FROM=RFSSSHKEY and TO=LOCSSHKEY is successfully
completed.
END OF STEPS
4.15.5
4.16.2 General
The generation and installation of NE SSL certificate is initiated by the NMS administrator and only
applies in the case where the NMS is configured to act as a certificate authority (CA) for the
managed network elements.
In order to play the CA role, the NMS has to own a CA-certificate through which all generated end-
entity certificates are signed. According to X.509 standard model, there are two possible kinds of
CA Certificates that an NMS can manage:
• Self-signed CA-certificate: In this case there is no need to manage an external CA and NMS can
generate its own root self-signed CA certificate using which it will sign all end-entity certificates
generated for the NEs.
• Cross-certificate CA-certificate: Not applicable in this release. In this case, an external CA
delivers a CA-certificate (called CA cross-certificate see X.509 for more reference) to NMS
making NMS itself able to act as a second level CA. In practice, a Cross-certificate CA is just
issued by a root CA to a subject, in order to authorize and recognize it as a subordinate-CA and,
as such, making it capable in turn of issuing Public Key certificates. The NMS becomes a trusted
CA in this schema, forming what is generally called a trusted certification chain, able to
consistently generate and issue certificates for end-entity Network Element.
4.16.4 Procedure
1
Login into the NE using the SECU-admin.
2
The NMS requests the that the NE update the certificate.
Result: The NMS creates a self-signature root CA and installs it.
3
NMS triggers the NE to generate a new SSL key pair (public and private), through
INIT-SSL-KEY TL1 command. This step is optional and is triggered only if a new SSL key
generation is necessary. If new key generation is not triggered by NMS, the NE simply uses the
current key in the next steps.
key has been generated. NOTE: The NMS user that issued the INIT-SSL-KEY command is
aware of the new key because of the INIT-SSL-KEY COMPLD response, but
REPT^EVT^SECU is mandatory to notify all network administrators.
4
The NMS triggers the NE to generate a CRS, through INIT-SSL-CSR TL1 command, and
optionally pre-sets some information which the NE is required to specify in the CSR.
A CSR is an encoded (most CSRs are created in the Base-64 encoded PEM format) message
through which a user applies for a certificate. The message is generated on the server that the
certificate and is used and is signed with the applicant private key. A CSR contains the following
information useful to generate the certificate;
• Common Name: Represents the domain name of the server (the NE IP Address).
• Organization: The legal name of the organization (Nokia).
• Organizational Unit: The division of your organization handling the certificate (Optics
Division).
• City/Locality: The city where your organization is located (Rome).
• State/County/Region: The state/region where your organization is located (should not be
abbreviated, Italy)
• Country: The two-letter ISO code for the country where your organization is location (IT).
• Email address: An email address used to contact your organization.
• Public Key: The public key goes into the certificate. Public Key cannot be pre-filled by NMS.
• Private Key: A private key is usually created at the same time that the CSR is created but is
NOT to be included in the CSR and needs to be kept as private information to be never
disclosed.
Note: The NE is obliged to use the information sent by NMS when specified.
Result: NE generates a new CSR in PEM format including the current SSL public key and
when completed sends a notification warning through REPT^EVT^SECU, that the CSR has
been generated.
5
NMS triggers the CSR file transfer upload from the NE to the NMS, through
COPY-RFILE-SECU. The NE starts the CSR file transfer onto the NMS machine location
specified in the COPY-RFILE-SECU.
Result: REPT^EVT^SECU with CONDTYPE=SSLCSR is sent when COPY-RFILE-SECU
with FROM=LOCCSRPEM and TO=RFSCSRPEM is successfully completed.
REPT^EVT^SECU with CONDTYPE=SSLCSR is sent when COPY-RFILE-SECU with
FROM=LOCCSTEXT and TO=RFSCSRTEXT is successfully completed.
6
NMS generates a new "end-entity" X.509 certificate using the information in the NE CRS
(Public Key) and signs it using its own CA certificate.
7
NMS makes a new PEM format certificate available for download by the NE and triggers the NE
itself to download it from a location specified in input parameter, through COPY-RFILE-SECU.
Result: REPT^EVT^SECU with CONDTYPE=SSLCERT is sent when COPY-RFILE-SECU
with FROM=RFSX509PEM and TO=LOCX509PEM is successfully completed.
REPT^EVT^SECU with CONDTYPE=SSLCERT is sent when COPY-RFILESECU with
FROM=RFSX509TEXT and TO=LOCX509TEXT is successfully completed.
8
NE starts downloading the certificate from the NMS machine location specified in the triggering
request. At the end of the file transfer phase, NE sends a notification to NMS, through
REPT^EVT^SECU.
9
NE validates the downloaded certificate and, in case of success, installs it and sends a COMPD
response to the COPY-RFILE-SECU in Step 7. In case a new SSL key generation is called in
the time between a CSR generation request Step 4 and the new certificate installation in this
step, a mismatch would arise in the NE, as the certificate would not be consistent with the key
anymore. In this case NE has to detect the error and to refuse the certificate installation
returning a proper error message (in practice, the COPY-RFILE-SECU at Step 7 is rejected).
10
A user with security privileges shall be able to retrieve the NE SSL public key, keytype and key-
length, by means of the RTRV-SSL-KEY TL1 command.
11
A user with security privileges shall be able to retrieve the NE SSL public X.509 certificate, both
in text and PEM formats, by means of the RTRV-SSL-CERT TL1 command.
12
A user with security privileges shall be able to retrieve the current NE SSL CSR, both in text
and PEM formats, by means of the RTRV-SSL-CSR TL1 command.
END OF STEPS
4.16.5
4.17.2 Prerequisites
None
4.17.3 General
Since the ODU2 object entity is automatically created (on the line side by the system when the
OTU-2 board is inserted and provisioned) the deprovision indicates only a change of state for the
ODU2 object.
The RMV-ODU2 command causes the specified facility client/line to be placed in an out-of-service
state for maintenance purposes.
After the maintenance phase the specified facility client/line can be restored with the RST-ODU2
command.
4.17.4 Procedure
1
Deprovision ODU2 facility.
For details, refer to 6.25 “Administer ODU2 Facility” (p. 212).
2
Restore the ODU2 facility.
For details, refer to 6.25 “Administer ODU2 Facility” (p. 212).
END OF STEPS
4.18.2 Prerequisites
4.18.3 General
The ODU2 object entity is automatically created on the line side by the system when the OTU-2
board is inserted and provisioned.
So, only edit operations are possibile on the ODU2 facility.
4.18.4 Procedure
1
Modify the ODU2 facility created automatically.
END OF STEPS
4.19.2 Prerequisites
None.
4.19.3 General
This procedure provides the instructions to deprovision a specified OTU2 client and line/port or to
change the port state.
4.19.4 Procedure
1
Deprovision the OTU2 facility.
For details, refer to 6.26 “Administer OTU2 Facility” (p. 218).
2
Change the port state.
For details, refer to 6.26 “Administer OTU2 Facility” (p. 218).
END OF STEPS
4.20.2 Prerequisites
The node shall be equipped with one of the following modules:
• DWLA10X
• OTU-2
4.20.3 General
The OTU2 object entity shall be automatically created on the line side by the system when the
OTU-2 or DWLA10X is inserted and provisioned.
The OTU-2 TL1 creation command on the line side is not supported.
If the facility provisioning mode of this NE is automatic, i.e., PROVMODE=AUTOEQAUTOFC, then this
create command cannot be used to enter facilities. In this mode, facilities are automatically entered
when the supporting equipment is entered (see 6.67 “Provision Equipment” (p. 385)).
4.20.4 Procedure
1
Provision the OTU-2 facility.
For details, refer to 6.26 “Administer OTU2 Facility” (p. 218).
END OF STEPS
4.21.2 Prerequisites
The 1850 TSS-320, TSS-320H and TSS-160 shall be equipped with one or more DATA boards.
4.21.3 General
None.
4.21.4 Procedure
1
Via TL1:
Provision boards and modules.
For details, refer to 6.67 “Provision Equipment” (p. 385).
Via TL1:
1. Create the Traffic Descriptor, see 8.14 “Administer T-MPLS Traffic Descriptor” (p. 521).
2. Create the first PW segment over a terminated tunnel or physical interface, i.e. TUSEG or
MPLS IF. Refer to 8.12 “Administer T-MPLS Pseudo Wire Segment” (p. 514).
3. Create the second PW segment over a terminated tunnel or physical interface, i.e. TUSEG
or MPLS IF. Refer to 8.12 “Administer T-MPLS Pseudo Wire Segment” (p. 514).
4. Cross-connect the two segments (label swap), this step creates automatically a PW. Refer
to 8.13 “Administer T-MPLS Pseudo Wire Segment Cross-Connection” (p. 517).
5. Configure some PW parameters (including possible association with TD and VT). Refer to
8.11 “Administer T-MPLS Pseudo Wire” (p. 510).
4
Via CLI:
Create, configure, activate an ETS-to-Provider Bridge PW bidirectional flow, refer to 10.4 “
Administer ETS to Provider Bridge ETS/PW/VPLS bidirectional flow ” (p. 582).
END OF STEPS
4.22.2 Prerequisites
The 1850 TSS-320, TSS-320H and TSS-160 shall be equipped with one or more DATA boards.
4.22.3 General
None.
4.22.4 Procedure
1
Via TL1:
Provision boards and modules.
For details, refer to 6.67 “Provision Equipment” (p. 385).
• Create the mpls port interface, see 10.10 “ Ethernet Port management (over MAU)” (p. 595).
• Activate the mpls port interface, see 10.10 “ Ethernet Port management (over MAU)”
(p. 595).
Via TL1:
1. Create the Traffic Descriptor, see 8.14 “Administer T-MPLS Traffic Descriptor” (p. 521).
2. Create an unique terminated segment over Tunnel or physical interface (i.e. the
“termination” option is chosen for TL1 command). Refer to 8.12 “Administer T-MPLS
Pseudo Wire Segment” (p. 514).
3. Configure some PW parameters (including possible association with TD and VT). Refer to
8.11 “Administer T-MPLS Pseudo Wire” (p. 510).
Note: It is possible to move one PW from one underlying tunnel to another tunnel, see
also8.11 “Administer T-MPLS Pseudo Wire” (p. 510).
4
Via CLI:
Create, configure, activate an ETS to Provider Bridge PW bidirectional flow, refer to 10.4 “
Administer ETS to Provider Bridge ETS/PW/VPLS bidirectional flow ” (p. 582).
END OF STEPS
4.23.2 Prerequisites
The 1850 TSS-320, TSS-320H and TSS-160 shall be equipped with one or more DATA boards.
4.23.3 General
None.
4.23.4 Procedure
1
Via TL1:
Provision boards and modules.
For details, refer to 6.67 “Provision Equipment” (p. 385).
Via TL1:
1. Creation of the Traffic Descriptor, see 8.14 “Administer T-MPLS Traffic Descriptor” (p. 521).
2. Creation of unique terminated segment over Tunnel or physical interface (i.e. the
“termination” option is chosen for TL1 command). Refer to 8.12 “Administer T-MPLS
Pseudo Wire Segment” (p. 514).
3. Configuration of parameters of PW. Refer to 8.11 “Administer T-MPLS Pseudo Wire”
(p. 510).
Via CLI:
• Bind between VPLS instance and PW, refer to 10.16 “VPLS Instance Management” (p. 608).
• Create, configure, activate an ETS to Provider Bridge VPLS bidirectional flow refer to 10.4 “
Administer ETS to Provider Bridge ETS/PW/VPLS bidirectional flow ” (p. 582).
END OF STEPS
4.24.2 Prerequisites
The 1850 TSS-320, TSS-320H and TSS-160 shall be equipped with one or more DATA boards.
In Release 4.0 Tunnel termination is needed.
4.24.3
At node level the NE generates TMPLS OAM (the default value is T-MPLS). To change to MPLS-TP
refer to 8.9 “Administer T-MPLS/ MPLS-TP Node configuration” (p. 504).
4.24.4 General
Scenario in case of protection: when protection is configured, the PW is anyway associated to the
main tunnel.
When switch occurs the relationship between PW and Tunnel doesn’t change (the switching
position is retrievable inside the protection group). It is possible to remove the protection group
leaving two unprotected tunnels.
4.24.5 Procedure
1
Via TL1:
Provision boards and modules.
For details, refer to 6.67 “Provision Equipment” (p. 385).
Via TL1:
1. Create two MPLS Tunnels (not protected), both sharing the same ingress/egress LSR
information and MPLS Tunnel type (bidirectional). See 4.12 “LSR Tunnel Management
(Label swap and Tunnel not Terminated)” (p. 82).
2. Create Tunnel Protection, see 8.7 “Administer T-MPLS Facility Protection Group” (p. 497).
3. Associate the PW and the protected tunnel (pointing to “tunnel index”), see
8.12 “Administer T-MPLS Pseudo Wire Segment” (p. 514).
4. Manage the “Protection status”, see 8.7 “Administer T-MPLS Facility Protection Group”
(p. 497).
END OF STEPS
4.25.2 Prerequisites
Please verify the VCG presence with the TL1 retrieve command (see 6.40 “Administer VCG
Facility” (p. 277)).
4.25.3 General
The DLT-VCG command deletes (unassigns and deprovisions) a specified VCG entity..
4.25.4 Procedure
1
Deprovison local ETS InFlow/OutFlow transparently crossconnected to an ETS InFlow/OutFlow
involved in the VCG CLI side (i.e. Verify CLI side no cross connections are present for the VCG
to deprovision).
For details, refer to 8DG09603EAAATQZZA — 1850 Transport Service Switch (TSS-320, TSS-
320H and TSS-160) Release 5.1 Command Line Interface Guide.
2
Deprovision VC cross connections (i.e. verify TL1 side no VC crossconections are present for
the VCG to deprovision).
For details, refer to 6.39 “Administer VC Cross-Connection” (p. 267).
3
Deactivate the ETS port CLI side.
For details, refer to 10.10 “ Ethernet Port management (over MAU)” (p. 595).
4
Deprovision VCG facility.
For details, refer to 6.40 “Administer VCG Facility” (p. 277).
END OF STEPS
4.26.2 Prerequisites
4.26.3 General
During a Virtual Concatenation Group creation also initial group of SDH Virtual Containers are
assigned to the VCG.
The Type of Virtual Container is specified in VCGTYPE parameter and can be for ETSI: VC4, VC3,
VC12.
The VCG is used to map data on SDH, i.e. to map Ethernet, ATM on SDH.
4.26.4 Procedure
1
Provision board and the module.
For details, refer to 6.67 “Provision Equipment” (p. 385).
2
Provision the VCG facility.
For details, refer to 6.40 “Administer VCG Facility” (p. 277).
3
Verify CLI side.
• that the VCG created on the ETS port is present, refer to 10.12 “General Interface
Management” (p. 599).
• activate the ETS port, refer to 10.11 “Ethernet Port management (over GFP)” (p. 597).
• create the Cross Connection between the ports, refer to 10.5 “ Administer ETS-to-ETS
bidirectional (port to port configuration)” (p. 585).
4
Provision the VC cross connection.
For details, refer to 6.39 “Administer VC Cross-Connection” (p. 267).
For details, refer to 6.40 “Administer VCG Facility” (p. 277) and 6.56 “LCAS Monitoring”
(p. 351).
END OF STEPS
4.27.2 Prerequisites
Verify the VPLS instance presence (see 10.16 “VPLS Instance Management” (p. 608)).
4.27.3 General
The VPLS Service is removed only using CLI commands.
4.27.4 Procedure
1
Delete ETS InFlow/OutFlow and the Provider Bridge/PW/VPLS ETS InFlow/OutFlow on which it
is transported. Creates also the cross connection between them, refer to 10.4 “ Administer ETS
to Provider Bridge ETS/PW/VPLS bidirectional flow ” (p. 582).
For details, refer to 8DG09603EAAATQZZA — 1850 Transport Service Switch (TSS-320, TSS-
320H and TSS-160) Release 5.1 Command Line Interface Guide.
2
Delete VPLS Instance.
For details, refer to 10.16 “VPLS Instance Management” (p. 608).
END OF STEPS
4.28.2 Prerequisites
4.28.3 General
A VPLS Service is a provider service based on “L2VPN” logical model with multi-point connectivity
that makes it possible to interconnect several LAN segments over a VPLS Network (consisting of
fully meshed MPLS Core Pseudowires inside backbone MPLS network).
4.28.4 Procedure
1
Provision board and the module.
For details, refer to 6.67 “Provision Equipment” (p. 385).
2
Change ports involved in VPLS in MPLS ones.
For details, refer to 10.10 “ Ethernet Port management (over MAU)” (p. 595).
3
Activate the VPLS ports.
For details, refer to 10.16 “VPLS Instance Management” (p. 608).
4
Provision the T-MPLS Traffic Descriptor for each Pseudo Wire that will be created for the VPLS.
For details, refer to 8.14 “Administer T-MPLS Traffic Descriptor” (p. 521).
5
Provision the Terminated Pseudo Wire.
For details, refer to 8.11 “Administer T-MPLS Pseudo Wire” (p. 510).
6
Create, activate and configure an ETS traffic descriptor.
For details, refer to 10.7 “Administer Traffic Descriptor” (p. 589).
7
Create and activate an VPLS instance see 10.16 “VPLS Instance Management” (p. 608)
For details, refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160)
Release 5.1 Command Line Interface Guide.
8
Create configure and activate ETS InFlow/OutFlow and the Provider Bridge/PW/VPLS ETS
InFlow/OutFlow on which it is transported. Creates also the cross connection between them,
see 10.4 “ Administer ETS to Provider Bridge ETS/PW/VPLS bidirectional flow ” (p. 582).
For details, refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160)
Release 5.1 Command Line Interface Guide.
END OF STEPS
4.29.2 Prerequisites
The node should be equipped with the following boards (and their modules):
• the UGW card, i.e. 2.5 Gb/s portless Universal Gateway (UGW)
• the SDH card (for example the 8PSO)
• the DATA card (for example the PP1GE).
Note: In current release, only TDM CES function is supported (2.5 Gb/s switching capability)
4.29.3 General
UGW card interfaces with both TDM matrix and Packet matrix which connects to the physical line
cards of TDM and Packet.
The 2.5 Gb/s portless UGW card supports equipment protection, for CES application, via EPS (1+1)
configuration.
The UGW card supports CES (Circuit Emulation Service) capability for DATA application, where a
TDM client (e.g. E1 or T1) is mapped into an upper server layer , that can be :
• TMPLS server layer (TDM over Packet), performing SAToP function (“Structure Agnostic over
Packets”), as per RFC 4553;
• Ethernet server layer (CES over Ethernet: CESoETH), as per MEF-8
Note: Only SDH and PDH signal parameters can be created, modified, deleted and retrieved,
via TL1 interface commands. CES service parameters configuration are provided via SNMP
agent, i.e. via CLI commands.
4.29.4 Procedures
1
Provision boards and modules. No module provisioning for the UGW board.
For details, refer to 6.67 “Provision Equipment” (p. 385).
Example:
2
TDM side: create the VC4 cross-connection, i.e. between the AUn and the VCn..
For details, refer to 6.39 “Administer VC Cross-Connection” (p. 267).
Example: Example with TDM card STM16 (AU4 range: 1 - 16):ENT-CRS-VC4::
STM16AU4-1-1-12-2-1,UGMVC4-1-1-17-2;
3
On the SNMP (i.e. CLI) side: the DATA board interfaces administrative status are UP (it is not
possible to put them down) and they coud be cross-connected only to terminated PW.
4
Create the PW, for details see 4.22 “PW Termination Management (Case of point-to-point)”
(p. 96).
Example:
5
Create the UGW on PW cross-connection. For details refer to 1850 Transport Service Switch
(TSS-320, TSS-320H and TSS-160) Release 5.1 Command Line Interface Guide.
6
Create the PW on UGW cross-connection, for details refer to 1850 Transport Service Switch
(TSS-320, TSS-320H and TSS-160) Release 5.1 Command Line Interface Guide.
7
Create the UGW Protection Group
. A duplex switching equipment protection group out of two unprotected equipment entities is
created with the TL1 command: ENT-DX-EQPT::PPUGW-1-1-12,PPUGW-1-1-19;. For
details see 6.4 “Administer Duplex Switching Equipment Protection Group” (p. 143)
8
To manage the UGW Protection Group refer to 6.4 “Administer Duplex Switching Equipment
Protection Group” (p. 143) .
END OF STEPS
5.1 Overview
5.1.1 Purpose
The Detailed Level Procedures (DLP) described in this chapter contain detailed steps and
supporting information required to complete a task when the CP is used. When a DLP is referenced
from another part of the manual, perform the DLP, then return to the point where the DLP was
referenced.
Command details
5.1.2 Overview
CP ROUTE is a CP session that can manage different Data Plane services (CP instances), in
GMPLS routing environment.
For T-MPLS instance, CP ROUTE will provide following specific parameter set:
• Global CP assignment for T-MPLS network nodes
• IF-IB configuration for IP Control Channel
• ARP management for IP Control Channel
Routing protocols requires minumum basic provisioning set by CP for their operation. The following
set is needed:
• Node IP address and Node Identifier
• Control Channel configuration for routing interfaces support
• Default area and auto-configuration for the routing interfaces
• Transport Port (TPORT) enabling for CP
I.e. Operator should define IP address for network nodes assigned to CP for their management
in routing , signaling and transport port provisioning.
In E-NNI routing environment, node IP is the Router IDentifier for the routing protocol running on
the relevant hierarchical level.
The node IP address, which is the router loopback address (always reachable) is common to
both L0 and L1 levels of the routing hierarchy.
For T-MPLS application , Node IP Address is the Router ID of the OSPF routing protocol.
• Default area routing configuration (Area ID)
This parameter defines the default for the routing area identifier (Area ID) associated to routing
interfaces on the relevant hierarchical level (OSPF or DDRP).
Area ID is in IP address format (32 bit), corresponding to a numeric value starting from 0 to
4294967295 (232 -1) and is expressed in four dot separated numeric string with range {0-255}for
each string.
If not specified backbone area (Area 0 ) is applied at default on such interfaces Default Area ID
can be provisioned separately for I-NNI OSPF and E-NNI OSPF (DDRP).
In T-MPLS instance, only OSPF routing Areas are supported.
• Auto mode setting for the routing interface
CP is able to define the mode setting of routing interfaces, supported by the Control Channel
termination ports .
Operator can select implicit routing protocol enabling supported by the CC termination port class
(I-NNI or ENNI) as the CP “auto mode”. In this way I-NNI OSPF or E-NNI routing protocol is
automatically enabled over an interface, on the base of the configured interface type.
In T-MPLS instance, only OSPF routing interfaces are supported (i.e. port class is I-NNI by
default).
• IP static routes advertisements
Operator is able to define advertise mode of all IP static routes created on local node and added
to the relevant routing table, under CP management.
• Notification events by CP.
Operator should configure notification events by CP relating to the assigned resources (transport
port, routing interface, signaling control)
Depending on the selected mode notification (enabled or disabled) the events from the relevant
resources can trigger notification report to the CP as autonomous messages.
A separate global network assignment to CP is provided for TDM and T-MPLS instances , through
ED-CPGLOBAL and ED-TMPLS-CPGLOBAL commands.
A global network assignment to CP is provided for TDMs through ED-CP-NODE commands.
5.1.6 Contents
5.2.2 Prerequisites
None.
5.2.3 General
The ED-TMPLS-CPGLOBAL command modifies global network parameters assigned to Control
Plane (CP) for TMPLS handling.
5.2.4 Procedure
1
Select action.
To retrieve Control Plane, go to Step 2.
To modify Control Plane parameters, go to Step 3.
To end this procedure, go to Step 4.
2
Retrieve Control Plane information
Enter RTRV-TMPLS-CPGLOBAL:[TID]::[CTAG] ;
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
3
Modify Control Plane parameters
Enter ED-TMPLS-CPGLOBAL::::::[IPADDR=][,OSPFAREAIDDFLT=][,AUTOC
ONFIG=][,ADVERTISE=][,CP-PORTEVNT=][,CP-ROUTPROTEVNT=][,CP-SIGNEVNT=
];
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
where:
IPADDR= Internet Protocol address, it is the IP address of the NE for the Control Plane in
T-MPLS application. The address 0-0-0-0 is not allowed. Neither the network nor the host
portion of the address when viewed in binary format may be all 0s or all 1s.
4
STOP. This procedure is complete.
END OF STEPS
5.3.2 Prerequisites
The Control Channel can be created over MPLS interfaces in In Fiber- In Band (IF-IB)
configuration.
Network node ID must be previously defined by the 8.8 “Administer T-MPLS Global Network
Parameters” (p. 502)
5.3.3 General
IP Control Channel (IPCC) is the communication channel inside the SCN network to carry GMPLS
routing and signaling protocols packets.
Depending on the selected control channel port type (I-NNI or E-NNI) , associated routing interface
will be OSPF or E-NNI routing (DDRP) type.
If “auto mode” is selected with CP global setting, routing protocol is enabled at interface set-up.
5.3.4 Procedure
1
Select action.
To retrieve Control Channel Termination Port information, go to Step 2.
To create Control Channel Termination Port, go to Step 5.
To modify Control Channel Termination Port parameters, go to Step 7.
To delete Control Channel Termination Port, go to Step 9.
To end this procedure, go to Step 10.
2
Retrieve Control Channel Termination Port information
Enter RTRV-CP-COM::AID::::[APPLY=][,ARP-TABLE=];
where: AID = Access IDentifier of the control channel termination port to be retrieved. If ALL is
selected all the control channel termination ports are retrieved. Possible values:
• ALL
• LAN-1 for Customer LAN
• MPLSIF-{1-7}-{1-9}-{2-9,12-19}-{1-10} for Local MPLS Interface
• MPLSIF-{1-7}-{1-9}-{2-9,12-19}-{1-128} for VCG MPLS Interface
• TIPIP-{10-300000} for Virtual Link using IPover IP encapsulation for TMPLS
• TGRE-{10-300000} for Virtual Link using GRE encapsulation for TMPLS
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
3
Examine output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
4
Go to Step 1.
5
Create Control Channel Termination Port
Enter ENT-CP-COM::AID::::[IPADDR=][,MASK=][,PORT-CLASS=][,MTU=]
[,ENCAPS-REMOTE-ID=][,ENCAPS-REMOTE-ADDRESS=][,ARP=][,STATUS=];
where:
• AID = Access IDentifier of the control channel termination port. In IF-IB configuration, MPLS
interfaces are used (local GbE or logical VCG's ). For OF-OOB, T-MPLS instance can use
virtual tunnel encapsulation with TIPIP-n or TGRE-n AID. Possible values as for Step 2 ALL
excluded...
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
6
Go to Step 1.
7
Modify Control Channel Termination Port parameters
Enter ED-CP-COM::AID::::[MTU=][,ARP=][,ARP-TIMEOUT=] [,ARP-FLUSHING=][,
STATUS=];
where:
• AID = Access Identifier, specifies the control channel termination port. Possible values as for
Step 2 ALL excluded..
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
8
Go to Step 1.
9
Delete Control Channel Termination Port
Enter DLT-CP-COM::AID:;
where:
• AID = Access Identifier, specifies an access to the facility. Possible values as for Step 2 ALL
excluded..
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
10
STOP. This procedure is complete.
END OF STEPS
5.4.2 Prerequisites
Network node ID, where this command is applied, must be previously defined by CP via
5.2 “Administer T-MPLS Control Plane Global Parameters” (p. 110) (local node IP address)
In T-MPLS environment, network node ID must be previously defined by the 8.8 “Administer
T-MPLS Global Network Parameters” (p. 502).
A static route entry is provisioned in the routing table with these parameters:
• Destination IP address
• IP subnet mask
• Next hop interface
• Metric
IP destination address, together with IP subnet mask, defines a route to a destination host node or
a subnetwork.
If IP mask is not all “ones” , a route to a subnetwork is defined, and the corresponding field of
destination address must be set to “zero”.
On the other end, all “ones” in subnet mask, define a destination to an host node.
Next hop interface is the IP address of the port to pass through to reach the destination route (host
node or subnetwork). This interface has to be provisioned only if control channel termination ports
have a multiple access through a LAN or a MPLS IF. Metric is the provisioned static route cost
through next hop interface to the destination. Router attached interfaces have a zero metric cost
5.4.5 General
This procedure allows the operator to enter (add) a new static IP route in the IP routing table, by
CP.
• If the AID specifies a STM-n then the NEXTHOP parameter should not be specified.
• If the AID specifies the LAN, then the NEXTHOP parameter must be specified.
Retrieved IP routes can be static routes edited via the ENT-CP-RT command or dynamic routes
generated by OSPF software.
If the operator specifies in the command the destination IP address and mask, only the IP routes
contained in the IP routing table matching those parameters are retrieved.
This command allows the operator to delete a static IP route from the IP routing table. The IP
route’s parameters specified define univocally the entry in the IP routing table that has to be
deleted. If a match with all the specified parameters cannot be found, an error message will be
returned inresponse.
5.4.6 Procedure
1
Select action.
To perform Static routing removal, go to Step 2.
To perform Static routing configuration, go to Step 5.
To perform Static routing removal, go to Step 7
To end this procedure, go to Step 8.
2
Retrieve Control Plane IP Route information
Enter RTRV-CP-RT:::::[DESTADDR],[MASK];
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
3
Examine output, as detailed in the relevant command guide, refer to “Command details”
(p. 107)
4
Go to Step 1.
5
Create Control Plane IP Route
Enter ENT-CP-RT::AID:::DESTADDR,MASK,[NEXTHOP],[METRIC];
where:
• AID = Access IDentifier, specifies the access interface for the static routing. Possible values:
− LAN-1 for Customer LAN
− MPLSIF-{1-7}-{1-9}-{2-9,12-19}-{1-10} for Local MPLS Interface
− MPLSIF-{1-7}-{1-9}-{2-9,12-19}-{1-128} for VCG MPLS Interface
− TIPIP-{10-300000} for Virtual Link using IPover IP encapsulation for TMPLS
6
Go to Step 1.
7
Delete Control Plane IP Route
Enter DLT-CP-RT:::::DESTADDR,MASK;
where:
• DESTADDR = Destination Address, it is the IP address of the destination host or network , in
combination with IP subnet mask (NETMASK). If NETMASK is not all “1” (i.e., a network
route is specified), the host portion of the DESTADDR must be all '0'.. Possible values: {1-99,
101-126,128-223} - {0-255} -{0-255} - {0-255}.
• MASK =IP Mask, it is the IP subnet mask of the route (in the format nnn-nnn-nnnnnn). The
mask 0-0-0-0 is used to specify a default route. Possible values: {0-255} - {0-255} - {0-255} -
{0-255}.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
8
STOP. This procedure is complete.
END OF STEPS
5.5.2 Prerequisites
The Control Channel can be created over MPLS interfaces in In Fiber- In Band (IF-IB)
configuration.
Network node ID must be previously defined by the 8.8 “Administer T-MPLS Global Network
Parameters” (p. 502)
5.5.3 General
In this document, System must be understood as a single Network Element.
In IF-IB (In Fiber -In Band) configuration TE link can be provisioned on the same CC interface. IN
OF-OOB (Out Fiber -Out of Band) configuration TE link can be provisioned on different CC
interfaces.
The REMOTE-PORT-AID parameter must be provisioned together with REMOTE-ROUTER-ADDR
parameter.
The ENT-CP-TPORT command can be also used to create Bundle links. Link Bundling occurs
when there is a set of parallel links between a pair of LSRs.
All component links in a Bundle link must begin and end on the same pair of LSRs.
The Bundle link (in this version) are only unnumbered. Unnumbered Bundle link can created
provisioning AID=BNDL-nnn.
Bundle links are foreseen TMPLS with specific AIDs.
Autodiscovery of remote-peer is NOT supported neither in case of component links nor in case of
bundle links because the mechanism is based on J0. It is not foreseen the use of LMP.
The RTRV-CP-TPORT command retrieves provisioned CP port parameters.
The ED-CP-TPORT command permits CP port parameters editing related to information
provisioned with ENT-CP-TPORT command. The ED-CP-TPORT command can be also used to
edit Bundle links.
5.5.5 Procedure
1
Select action.
To retrieve Control Plane Tranport Port information, go to Step 2.
To create Control Plane Tranport Port, go to Step 4.
To modify Control Plane Tranport Port parameters, go to Step 5.
To delete Control Plane Tranport Port, go to Step 6.
To end this procedure, go to Step 7.
2
Retrieve Control Plane Tranport Port information
Enter RTRV-CP-TPORT::AID::::[SHOW-MODE=][,FILTER=];
where: AID = Access Identifier, specifies an access to the NE CP facility. Possible values:
• MPLSIF-{1-7}-{1-9}-{2-9,12-19}-{1-10} for Local MPLS Interface
• MPLSIF-{1-7}-{1-9}-{2-9,12-19}-{1-128} for VCG MPLS Interface
• TBNDL-{10-109} Bundle Link for TMPLS)
• ALL
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
3
Examine output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<AID>: LINK-ADMIN-STATUS=<value>,LINK-OPER-STATUS=<value>,
PORTCLASS=<value>,REMOTE-PORT-AID=<value>, REMOTE-ROUTER-ADDR=
<value>,[,MAX-BANDWIDTH=<value>][,MAX-RESERVABLE-BANDWIDTH=<value>][,
UNRESERVED-BANDWIDTH=<value>], METRIC=<value>, COLOR=<value>,
SRLGLIST=<value>,SWITCHCAP=<value>, ENCODING-TYPE=<value>[,AUTH=
<value>][,AUTHKEY=<value>]" cr lf
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
4
Create Control Plane Tranport Port
Enter ENT-CP-TPORT:[TID]:AID:[CTAG]:::[LINK-ADMIN-STATUS=][,PORT-CLASS=]
[,BUNDLE-AID=],REMOTE-PORT-AID=[,REMOTE-ROUTER-ADDR=][,MAX-BANDWIDTH=]
[,MAX-RESERVABLE-BANDWIDTH=][,METRIC=][,COLOR=][,SRLG-LIST=][,AUTH=]
[,AUTHKEY=];
where:
• AID = Access Identifier, specifies an access to the facility. Possible values as for Step 2 ALL
excluded.
• REMOTE-PORT-AID= = Access Identifier, specifies an access to the facility on remote NE.
Restrictions: This parameter is mandatory. The facility type referred by this parameter must
be the same of that referred by AID: AID=MPLSIF <--> REMOTE-PORT-AID=MPLSIF
AID=TBNDL <--> REMOTE-PORT-AID=TBNDL
• REMOTE-ROUTER-ADDR = Neighbour router IP address.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
The ENT-CP-TPORT command shall be rejected if the Local Router IP address (it is the IP
address of the NE for the Control Plane.) isn't provisioned.
5
Modify Control Plane Tranport Port parameters
Enter ED-CP-TPORT::AID::::[LINK-ADMIN-STATUS=][,REMOTE-PORT-AID=][,
REMOTE-ROUTER-ADDR=][,MAX-BANDWIDTH=][,MAX-RESERVABLEBANDWIDTH=][,
METRIC=][,COLOR=][,SRLG-LIST=][,AUTH=] [,AUTHKEY=];
where:
• AID = Access Identifier, specifies an access to the facility. Possible values as for Step 2.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
6
Delete Control Plane Tranport Port
Enter DLT-CP-TPORT::AID:;
where:
• AID = Access Identifier, specifies an access to the facility. Possible values as for Step 2.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
7
STOP. This procedure is complete.
END OF STEPS
5.6.2 General
The ED-CP-OSPIF allows the operator to modify the parameters associated to OSPF on each
OSPF enabled interface over control channel termination port.
In T-MPLS application OSPF interface can be accessed through MPLS interfaces or specific virtual
tunnel encapsulation TIPIP or GRE in OF-OOB configuration.
When an interface is created with ENT-CP-COM, default OSPF interface parameters are created.
For details refer to 5.3 “ Administer Control Plane - Control Routing Port” (p. 111)
The ED-CP-OSPIF can modify this parameter set, together with neighbor provisioning for point-to-
multipoint connection type.Moreover this command can optionally provide OSPF packet
authentication with Key ID for MD5 encryption algorithm.
5.6.3
Operator, from CP, could retrieve all configured parameter of all the OSPF interfaces or a specific
one, selecting the relevant AID of the CC termination port that support it.
OSPF interface operational status can be also reported.
Operator, from CP, could retrieve all configured parameter of all the OSPF interfaces or a specific
one, selecting the relevant CPDPR AID.
OSPF interface operational status can be also reported. CP will perform OSPF interface report via
the RTRV-CP-OSPFIF TL1 command. The parameter list that can be retrieved is as follows:
• IP address/network mask
• OSPF Area ID
• OSPF routing timers
• Route metric
• Connection type
• Authentication (Y/N)
• Administrative status
• Operative status
Apart from retrieval of previously configured parameters, in RTRV-CP-OSPFIF CP reports the
operative status of the routing interface as a collection of different states from initial to final ,based
on OSPF routing interface state machine.
5.6.5 Procedure
1
Select action:
1. To modify the OSPF interface parameters, go to Step 2
2
Modify the OSPF interface
Enter:
ED-CP-OSPFIF::AID::::[METRIC=][,OSPFAREA-ID=][,OSPFRETXTI NT=][,
OSPFHELLOINT=][,OSPFDEADINT=][,NEIGHBOR=][,TYPE=][,AUTH=][,AUT
HKEY=][,IFSTATUS=];
where:
• AID = Access Identifier of the OSPF interface bound to control channel termination port
whose OSPF interface parameters are to be edited. Values can be:
− LAN-1 (Customer LAN)
− MPLSIF-{1-7}-{1-9}-{2-9, 12-19}-{1-20} - Local MPLS Interface.
− MPLSIF-{1-7}-{1-9}-{2-9, 12-19}-{1-128} - VCG MPLS Interface.
− TIPIP-{10-300000} - Virtual Link using IPover IP encapsulation for TMPLS.
− TGRE-{10-300000} - Virtual Link using GRE encapsulation for TMPLS.
• OSPFAREA-ID = AID of the OSPF AREA to which the routing interface is connected. If
OSPFAREA-ID=0-0-0-0, the backbone area will be used.
Restriction: OSPFAREA-ID can be set only if the OSPF interface is disabled (IFSTATUS=
OFF).
• NEIGHBOR = It specifies a neighbor interface IP Address for OSPF P2MP connection type.
• TYPE = P2P.
Restrictions: Only Point-to-Point OSPF interfaces are currently supported.
• IFSTATUS = Specifies the administrative state of the OSPF interface, if it is enabled
(IFSTATUS=ON) or if it is disabled (IFSTATUS=OFF). Default value is set to ON at interface
creation
3
To retrieve the parameters associated with OSPF on each OSPF enabled interface over control
channel termination port
Enter:
RTRV-CP-OSPFIF::AID;
AID = Access Identifier of the OSPF interface bound to control channel termination port whose
OSPF interface parameters are to be edited. Values can be:
• ALL - ALL AID.
• LAN-1 - Customer LAN.
• MPLSIF-{1-7}-{1-9}-{2-9, 12-19}-{1-20} - Local MPLS Interface.
• MPLSIF-{1-7}-{1-9}-{2-9, 12-19}-{1-128} - VCG MPLS Interface.
• TIPIP-{10-300000} - Virtual Link using IPover IP encapsulation for TMPLS.
END OF STEPS
5.7.2 General
This command creates a new LSP tunnel that replaces the old LSP tunnel specified by input AID
parameter; then the command moves the traffic from the old LSP tunnel towards the new LSP
tunnel and deletes the old LSP tunnel.
The new created LSP tunnel has the same source and destination of deleting LSP tunnel.
The other old tunnel parameters values can be entered with this command and if not entered they
assume the same values of the deleting LSP tunnel.
The DIR, LAYER, STATUS and REVERT-MODE old tunnel parameters can't be edited and are
copied to the new created tunnel.
It is possible to enter this command without specifying any optional parameter for searching a new,
better path for the new tunnel.
If Tunnel to be replaced is protected then the Operator can reference one of the Tunnels that is part
of "protection scheme" (i.e. Protected, Protecting or Backup Tunnel).
With this command is possible to add or to remove the "Protection" to existing tunnels.
If TD-ID optional parameter is not specified then the new tunnel will have the same band of
replacing tunnel, but can not using the same TD ( because there is an association 1:1 between
Tunnel and TD) then the System will set up a new TD and the operator will find a new tunnel
associated with the new TD-ID. The TD associated with the removed tunnel will be deleted.
This command is used also for changing some Tunnel parameters as HOLD-PRIO, SETUP-PRIO
and HOPLIST-ID; in this case the AID of the Tunnel is maintained.
As result of successful response, the Control Plane automatically assigns the new TUNNEL-AID
output parameter. This output AID values shall be returned also in the TUNNEL-AID output
parameter of REPT^TMPLSRPLCTUNNEL message associated with this command
Command restriction:
Tunnel referenced by AID must have ACD=CP.
Tunnel referenced by AID must have ROLE=HEAD
5.7.4 Procedure
1
Select action:
To perform a Make Before Break changing the old tunnel TD-ID, go to Step 2.
To perform a Make Before Break without changing the old tunnel TD-ID, go to Step 6.
To change some CP tunnel parameters, go to Step 7.
2
Retrieve a TD (Traffic Descriptor) also called MPLS Tunnel Resource Descriptor.
Enter:
RTRV-TMPLS-TD::[AID];
AID = Access Identifier, specifies an access Identifier to the MPLS TD associated to the tunnel
to replace.
3
Examine output.
If new TD parameters for Tunnel are required new Tunnel is created and set up.
4
Create the new TD and it new parameters to associate to the new tunnel.
Enter:
ENT-TMPLS-TD::::::CIR=,CBS=,PIR=,PBS=;
where:
• CIR = MPLS Committed Information Rate. This parameter is valid for Tunnels and
PseudoWires and it is a positive value.
Restrictions: The CIR value must be <= of PIR value.
• CBS = MPLS Committed Burst Size. This parameter is valid for Tunnels and PseudoWires
and it is a positive value.
Restrictions: The CBS value must be <= of PBS value.
• PIR = MPLS Peak Information Rate. This parameter is valid for Tunnels and PseudoWires
and it is a positive value. Restrictions: The PIR value must be >= of CIR value.
• PBS = MPLS Peak Burst Size. This parameter is valid for Tunnels and PseudoWires and it is
a positive value. Restrictions: The PBS value must be >= of CBS value.
5
Examine output: AID = MPLSTD-{1-74000}.
Access Identifier, specifies an access Identifier to the TD that should be used in the next step
(i.e. in the new tunnel creation).
Result: The new TD-ID has to be entered in the OPR-TMPLS-RPLCTUNNEL command
6
To create a new LSP tunnel that replaces the old LSP tunnel (created by CP), enter:
OPR-TMPLS-RPLCTUNNEL::AID::::[TUNNEL-ID]=[,DESCR=][,TD-ID =][,
PHBPROF-AID=][,PROT-TYPE=][,HOPLIST-ID=][,DIVERSITY=][,INCL-ALL=
][,INCL-ANY=][,EXCL-ANY=][,HOLD-PRIO=][,SETUP-PRIO=];
where:
• AID= AID of LSP Tunnel to replace.
The AID is made by six parameters: Rack, Subrack, Tunnel Index, Tunnel Instance, Ingress
LER address, Egress LER address.
• TUNNEL AID for identifying the Tunnel to be replaced.
In case that the Tunnel to be replaced is protected it is possible to enter the AID of the
Protected, Protecting or Backup Tunnel of the protection scheme; the command affects all
the Tunnels involved in the protection scheme
• parameters specified in this OPR command refer to the new Tunnel set up to substitute the
Tunnel identified by the entered AID
• the new created Tunnel has the same SRC-ADDR and DEST-ADDR (Destination Node IP
Address target point of the LSP Tunnel) of the old one
• if the value is not entered for the optional parameters, the default value, that correspond to
the value in the Tunnel to be substituted, is taken
• The HOPLIST-ID = NO-HOPLIST allows requiring a new Tunnel without specifying any
hoplist even if the Tunnel to be replaced has an associated HOPLIST
Note: The DIR, LAYER, STATUS and REVERT-MODE old tunnel parameters can't be
edited and are copied to the new created tunnel.
7
Enter:
RTRV-TMPLS-TUNNEL::AID;
where:
AID = AID of LSP Tunnel that defines TUNNEL AID. It is made by six parameters: Rack,
Subrack, Tunnel Index, Tunnel Instance, Ingress LER address, Egress LER address
8
Examine output.
If the output parameter ACD has the CP value, parameters that can be changed are:
STATUS = Tunnel administrative status.
VT-HEAD = Pointer to Virtual Transport, AID of the Virtual Port resource. VT-HEAD is the VT at
source port in the source - destination direction. The Virtual Transport in fact is a logical entity
associated to an output port.
VT-TAIL = Pointer to Virtual Transport, AID of the Virtual Port resource. VT-TAIL is the VT at
destination port in the destination-source direction. The Virtual Transport in fact is a logical
entity associated to an output port.
Note: ACD = Access Control Domain: Local (MP) or Control Plane. It filters output tunnels
on the basis on who has created them.
9
Enter:
ED-TMPLS-TUNNEL::AID::::[,STATUS=][,VT-HEAD=][,VT-TAIL=];
where:
AID = AID of LSP Tunnel that defines TUNNEL AID. The former is made by six parameters:
Rack, Subrack, Tunnel Index, Tunnel Instance, Ingress LER address, Egress LER address.
STATUS = Tunnel administrative status,
END OF STEPS
5.8.2 Prerequisites
None.
5.8.3 General
The ENT-CPTMPLS-HOPLIST command creates an "Hoplist" entry in Control Plane hop list table
to be used by CP connections for T-MPLS instance. It defines the ERO (Explicit Route Object)
Object message structure in the extended RSVP-TE protocol signaling. Label ERO Sub-Object field
is also set with path constraint (loose/strict) and label to be used along the route.
An Hoplist is composed by a set of entries as hoplist components: these are paths and hops.
Paths are identified by an index (PATH-INDEX); each path represents a route topology between
source and destination nodes. Each path is made by a list of hops, identified by an index (HOP-
INDEX) which describes the hops between nodes in the routing path. The Hoplist itself is identified
by a HOPLIST-ID.
At first entry of an Hoplist creation the user doesn't specify any of these key parameter (HOPLIST-
ID, HOP-INDEX) because they are automatically assigned by CP. Instead, at first entry of an Hoplist
creation, the user can enter the PATH-INDEX.
With this command the user can add new hops in the path specified by PATH-INDEX parameter
value.
In case of successful response the CP shall return these parameters in the output.Furtherly, if user
needs to specifiy more entries (new path or hop), he must enter all the key parameters.
In the hop attributes, the parameters HOP-UNNUM, LABEL-TYPE and LABEL-VALUE are optional;
moreover, if a LABEL field (LABEL-TYPE and LABEL-VALUE) is specified, all the hop attributes
have to be provided: LABEL-TYPE, LABEL-VALUE, HOP-UNNUM, HOP-IP-ADDR
In LOOSE mode , operator is allowed to assign only HOP-IP-ADDR as hop attribute, for legal use.
A hoplist can be made by any number of hops as long as free hops from the pool are available.
It is not possible to add hop when the corresponding PATH is in use: it is not possible to change the
PATH-INDEX = 1 (adding hops) when the HOPLIST-ID is associated to a Tunnel; it is not possible
to change the PATH-INDEX = 2 (adding hops) when the HOPLIST-ID is associated to a PATH-
ONE-TO-ONE or PRC protected Tunnel.
The RTRV-CPTMPLS-HOPLIST command retrieves T-MPLS HOPLIST configuration parameters,
assigned by user in the CP via ENT-CPTMPLS-HOPLIST or ED-CPTMPLSHOPLIST commands.
User can retrieve all data of the Hoplist or its components , filtering on PATH-INDEX and HOP-
INDEX basis.
The ED-CPTMPLS-HOPLIST command allows editing provisioned HOPLIST configuration set-up
assigned by user in the CP via ENT-CPTMPLS-HOPLIST command, for T-MPLS instance. This
command is used to modify the parameter attributes associated to a specific hop location defined
by the key parameters (HOPLIST-ID, PATH-INDEX, HOP-INDEX).
Command restriction: It is not possible to change parameters of an HOPLIST when the
corresponding PATH is in use: it is not possible to change the PATH-INDEX = 1 related hops when
the HOPLIST-ID is associated to a Tunnel; it is not possible to change the PATH-INDEX = 2 related
hops when the HOPLIST-ID is associated to a PATH-ONE-TO-ONE or PRC protected Tunnel.
The DLT-CPTMPLS-HOPLIST command deletes a provisioned T-MPLS HOPLISTor its component
(specific path /hop). This latter is done entering PATH-INDEX /HOP-INDEX parameters in the
command set.
5.8.4 Procedure
1
Select action.
To retrieve T-MPLS Control Plane Hoplist information, go to Step 2.
To create T-MPLS Control Plane Hoplist, go to Step 4.
To modify T-MPLS Control Plane Hoplist parameters, go to Step 5.
To delete T-MPLS Control Plane Hoplist, go to Step 6.
To end this procedure, go to Step 7.
2
Retrieve T-MPLS Global Network Parameters information
Enter RTRV-CPTMPLS-HOPLIST::HOPLIST-ID::::[PATH-INDEX=] [,HOP-INDEX=];
where: HOPLIST-ID =Hoplist Identifier selected by user to retrieve all the parameter list. If ALL
is selected, all the entered HOPLIST-ID will be retrieved. Possible values: ALL or {1-
2147483647}.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
3
Examine output for provisioning information, as detailed in the relevant command guide, refer to
“Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<HOPLIST-ID>::PATH-INDEX=<value>,HOP-INDEX=<value>,HOP-IPADDR=
<value>,HOP-UNNUM=<value>,LABEL-VALUE=<value>,INCLMODE=<value>,
EXPLICIT-MODE=<value>,LOOSE-MODE=<value>"cr lf
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
4
Create T-MPLS Control Plane Hoplist
Enter ENT-CPTMPLS-HOPLIST::::::[HOPLIST-ID=][,PATH-INDEX=][,HOP
-INDEX=],HOP-IP-ADDR=[,HOP-UNNUM=][,LABEL-VALUE=],INCL-MODE=,
EXPLICIT-MODE=,LOOSE-MODE=;
where:
• HOPLIST-ID = Hoplist Identifier. HOPLIST-ID is assigned by system at first entry creation of
the Hoplist
Restrictions: The HOPLIST-ID must be unique in the system.
• HOP-IP-ADDR = Node IP Address (Node ID) for a given indexed hop. It applies to the next
hop node in the routing path. Possible values: {1-99, 101-126,128-223} - {0-255} - {0-255} -
{1-254}.
• INCL-MODE = INCLUDE or EXCLUDE the hop address set for path routing, entered via
HOP-IP-ADDR and HOP-UNNUM parameters.
• EXPLICIT-MODE = Path routing mode selected by user. Possible values:
− EXPLICIT: Path routing is manually assigned by user via HOP-IP-ADDR and HOP-
UNNUM parameters.
− DYNAMIC: Path routing is retrieved from CSPF database.
• LOOSE-MODE = RSVP path constraint selected by user for next destination hop. It applies
on the indexed hop in the Hoplist. If LOOSE mode is selected, operator may specify only
HOP-IP-ADDR for legal use.
Possible values:
− LOOSE: Next hop can be routed via different paths to the destination node.
− STRICT: Next hop is directly connected to the destination node.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
The [HOPLIST-ID=][,PATH-INDEX=] [,HOP-INDEX=] parameters are assigned by system.
5
Modify T-MPLS Control Plane Hoplist parameters
Enter ED-CPTMPLS-HOPLIST::HOPLIST-ID::::PATH-INDEX=,HOP-INDEX=[,
HOP-IP-ADDR=][,HOP-UNNUM=][,LABEL-VALUE=][,INCL-MODE=][,
EXPLICIT-MODE=][,LOOSE-MODE=];
where:
• HOPLIST-ID =Hoplist Identifier selected by user for editing. The HOPLIST-ID must be unique
in the system. Possible values: {1-2147483647}.
• PATH-INDEX = {1-2}. Path Identifier as path index value. Identify a specific path component
in the hoplist identifier (HOPLIST-ID).
PATH-INDEX 1 is used for protected Path, instead PATH-INDEX 2 is used for protecting path.
Restrictions: When the Hoplist with PATH-INDEX = 1 is edited and related HOPLIST-ID is
used by a Tunnel , then the command shall be denied.
When the Hoplist with PATH-INDEX = 2 is edited and related HOPLIST-ID is used by a
PATH-ONE-TO-ONE or PRC protected Tunnel, then the command shall be denied.
• HOP-INDEX = Identifies the hop order for a given routing path across the network, as a
component of an assigned PATH -INDEX. Possible values: {0-1024} range.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
6
Delete T-MPLS Control Plane Hoplist
where:
• HOPLIST-ID =Hoplist Identifier selected by user to remove.. The HOPLIST-ID must be
unique in the system. Possible values: {1-2147483647}.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
7
STOP. This procedure is complete.
END OF STEPS
6.1 Overview
6.1.1 Purpose
The Detailed Level Procedures (DLP) contain detailed steps and supporting information required to
complete a task. When a DLP is referenced from another part of the manual, perform the DLP, then
return to the point where the DLP was referenced.
6.1.2
6.1.3 Contents
6.2.2 Prerequisites
None.
6.2.3 General
Only a user with system administrator privileges can create a user profile entry. If ENT-USER-
SECU executes successfully, the system accepts any association of the UID with a TCP/IP port
number and server IP address. The 1850 TSS-320, TSS-320H and TSS-160 uses port 3083 for
telnet port and port 3082 for raw port.
6.2.4 Procedure
1
Enter ENT-USER-SECU::UID:::PID,CONFIRMPID,[UAP]:[PAGE=][,PCND=][,PCNN=]
[,POINT =][,UOUT=];
where:
• UID={5-12 valid UID characters} specifies a unique user ID.
• PID={8-12 valid PID characters} specifies the user's login password.
• CONFIRMPID=Password Identifier Confirmation, confirms the user’s login password.
• UAP=User Access Privilege (& grouping) granted to this user {CONF (configure), NETADMIN
(network administrator), PROV (provision), READ (read-only), SEC (Security Administrator),
DEBUG (test), NOTMOUT (no inactivity timeout applied to the user)}.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
2
Did system return a successful response?
If yes, go to Step 3.
If no, check error code message and return to Step 1 to retry command.
3
STOP. This procedure is complete.
END OF STEPS
6.3.2 Prerequisites
None.
6.3.3 General
The ASAP is created as a clone of one of the system-defined default ASAP of the entered type. If
no system defined ASAP instance is specified, a clone of the instance 1 shall be created.
The system can support up to 500 total instances of ASAP for all entity types.
6.3.4 Procedure
1
Select action.
To retrieve ASAP information, go to Step 2.
To create ASAP, go to Step 5.
To modify ASAP parameters, go to Step 7.
To replace the assignment of an OLD ASAP with a NEW ASAP, for all of the entity instances
pointing to the entered OLD ASAP, go to Step 9.
To delete ASAP, go to Step 10.
To end this procedure, go to Step 11.
2
Retrieve ASAP information
Enter RTRV-ASAP-PROF:::::[ASAPTYPE]:[USERLABEL=];
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
3
Examine output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
"<ASAP-AID>,<ASAPTYPE>::DFLT=<value>,USERLABEL=<value>" cr lf
[
"::<CONDTYPE>,<NTFCNCDE>,<SRVEFF>,<LOCN>,[<DIRN>]" cr lf]*]* cr lf
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
4
Go to Step 1.
5
Create ASAP
Enter ENT-ASAP-PROF:::::PFTYPE:[DFLT=][,USERLABEL=][,CLONEFROM=];
where:
• PFTYPE = ASAP type for the ASAP that shall be created. Possible values: EQPT, BITS,
TIMING, SECU, GBE, MAU, 10GBE, VCG, OGPORT, OTU, OCH, OTS, OMS, ODUn, STM1,
STM4, STM16, STM64, FC200, FC400, VC4, VC44C, VC416C, VC464C, LOVC3, LOVC12,
TUSEG, E1, PPSIN, PTP, PHASE
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
6
Go to Step 1.
7
Modify ASAP parameters
Enter ED-ASAP-PROF::[ASAP-AID]:::[CONDTYPE],[NTFCNCDE],[SRVEFF],
[LOCN],[DIRN]:[DFLT=][,USERLABEL=];
where:
• ASAP-AID = ASAP identifier, both for factory default {0-1} and for user defined {2-255}.
Possible values: ALL, ASAPEQPT-, ASAPBITS-, ASAPTIMING-, ASAPGBE-, ASAPMAU-,
ASAP10GBE-, ASAPVCG-, ASAPOGPORT-, ASAPOTU-, ASAPOTS-, ASAPOMS-,
ASAPOCH-, ASAPODUn-, ASAPSTM1-/OC3-, ASAPSTM4-/OC12, ASAPSTM16-/OC48-,
ASAPSTM64-/OC192-, ASAPFC200-, ASAPFC400-, ASAPVC4-/STS3-, ASAPVC44C-/
STS12-, ASAPVC416C-/STS48-, ASAPVC464C-/STS192-, ASAPLOVC3-/STS1-,
ASAPLOVC12-, ASAPTUSEG-, ASAPSECU-, ASAPE1-, ASAPPPSIN-, ASAPPTP-, PTP-,
PHASE-
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
8
Go to Step 1.
9
Replace OLD ASAP with the NEW ASAP
Enter ED-ASAP-ASSIGN:[TID]:[OLDASAPAID],[NEWASAPAID]:[CTAG]:::
[OLDUSERLABE L=],[NEWUSERLABEL=];
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
10
WARNING
Optional Content
• Both null and factory default ASAPs cannot be deleted.
• The command can be issued only by users with appropriate privileges.
Delete ASAP
Enter DLT-ASAP-PROF::::::[USERLABEL=];
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
11
STOP. This procedure is complete.
END OF STEPS
6.4.2 General
The ENT-DX-EQPT command creates a duplex switching equipment protection group out of two
unprotected equipment entities. After successful command completion, the two specified equipment
entities protect each other in a one-for-one (duplex) protection mode.
Per convention, the equipment with the lower AID position is the protected equipment, and the
equipment with the higher AID position is the protecting equipment.
The command is denied if the protecting entity is supporting "in Service" facilities.
The DLT-DX-EQPT command deletes a duplex switching equipment protection group. When
successfully executed, the two specified equipment entities continue to operate in unprotected
mode.
The SW-DX-EQPT command performs a copy switch for the specified redundant (duplexed)
equipment. Either copy of equipment can be specified; the command performs a switch regardless
of which copy of equipment is specified (the active copy becomes standby and the standby copy
becomes active).
6.4.4 Procedure
Select action.
• To retrieve information on a duplex switching equipment protection group see Step 2.
• To create a duplex switching equipment protection group see Step 3.
• To delete a duplex switching equipment protection group see Step 5.
• To perform copy switch for redundant equipment, go to Step 4.
• To enable (allow) automatic and manual copy switching for the specified one-for-one
redundant (duplex) equipment, go to Step 6.
2
Retrieve information on a duplex switching equipment protection group
Enter:
RTRV-DX-EQPT::AID;
where:
AID = Equipment Access Identifier, identifies the equipment entity access identifier.
Possible values:
• EC320-{1-7}-{1-9}-{1,20} - Equipment Controller Card TSS-320
• MT320-{1-7}-{1-9}-{10,11} - Matrix and Timing TSS-320
• PP10AD-{1-7}-{1-9}-{2-9,12-19} - Adaptation Card Packet Modules 10G
• PPUGW-{1-7}-{1-9}-{2-9,12-19} - Universal GateWay Card Packet Module 2e5G
• MTSYNTH4-{1-7}-{2}-{6,15}- 2xSTM4 Optical & Matrix Card
• P42E1-{1-7}-{1-9}-{1-6} - 1646DS 42XE1/T1 Card.
• SCC-{1-7}-{1-9}-{7,8} - 1646DS SCC Card.
• ALL - ALL AID.
3
Duplex switching equipment protection group Creation
Enter:
ENT-DX-EQPT::AID1,AID2;
where:
• AID1 = Equipment Access Identifier, identifies the protected equipment entity of the duplex
switching equipment protection group.
Possible values:
− PP10AD-{1-7}-{1-9}-{2-9,12-19} - Adaptation Card Packet Modules 10G
− PPUGW-{1-7}-{1-9}-{2-9,12-19} Universal GateWay Card Packet Module 2e5G
− P42E1-{1-7}-{1-9}-{1,3,5} - 1646DS 42XE1, protected module.
• AID2 = Equipment Access Identifier, identifies the protecting equipment entity of the duplex
switching equipment protection group.
Possible values:
− PP10AD-{1-7}-{1-9}-{2-9,12-19} - Adaptation Card Packet Modules 10G
− PPUGW-{1-7}-{1-9}-{2-9,12-19} Universal GateWay Card Packet Module 2e5G
− P42E1-{1-7}-{1-9}-{2,4,6} - 1646DS 42XE1, protecting module.
4
Perform Copy Switch for Redundant Equipment
Enter SW-DX-EQPT::AID:::[MODE];
where: AID = Equipment Access Identifier, identifies the equipment entity access identifier.
Possible values:
• EC320-{1-7}-{1-9}-{1,20} for Equipment Controller Card TSS-320
• MT320-{1-7}-{1-9}-{10,11} for Matrix and Timing TSS-320
• PP10AD-{1-7}-{1-9}-{2-9,12-19} for Adaptation Card Packet Modules 10G.
• PPUGW-{1-7}-{1-9}-{2-9,12-19} - Universal GateWay Card Packet Module 2e5G
• MTSYNTH4-{1-7}-{2}-{6,15} - 2xSTM4 Optical & Matrix Card
• P42E1-{1-7}-{1-9}-{1-6} - 1646DS 42XE1/T1 Card.
• SCC-{1-7}-{1-9}-{7,8} - 1646DS SCC Card.
Note: Force Mode is NOT allowed for EC320 and MT320 in Main Shelf EPS, and it is
NOT allowed for MTSYNTH4 in Drop Shelf EPS.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
5
Duplex switching equipment protection group Deletion
Enter:
DLT-DX-EQPT::AID1,AID2::::[CMDMDE=];
where:
• AID1 = Equipment Access Identifier, identifies the protected equipment entity of the duplex
switching equipment protection group.
Possible values:
− PP10AD-{1-7}-{1-9}-{2-9,12-19} - Adaptation Card Packet Modules 10G
− PPUGW-{1-7}-{1-9}-{2-9,12-19}- Universal GateWay Card Packet Module 2e5G
− P42E1-{1-7}-{1-9}-{1,3,5} - 1646DS 42XE1, protected module
• AID2 = Equipment Access Identifier, identifies the protecting equipment entity of the duplex
switching equipment protection group.
Possible values:
− PP10AD-{1-7}-{1-9}-{2-9,12-19} - Adaptation Card Packet Modules 10G
− PPUGW-{1-7}-{1-9}-{2-9,12-19}- Universal GateWay Card Packet Module 2e5G
− P42E1-{1-7}-{1-9}-{2,4,6} - 1646DS 42XE1, protecting module
• CMDMDE = Command Mode, identifies the Command Execution Mode.
Possible values:
− NORM
− FRCD.
Note: This command fails when both protection units are in UEQ state and CMDMDE is
specified as FRCD and if the unit specified by AID2 is providing actual service (WRK
secondary state).
6
To enable (allow) automatic and manual copy switching for Redundant Equipment
Enter:
ALW-SWDX-EQPT::AID;
where:
AID = Equipment Access Identifier, identifies the equipment entity access identifier.
END OF STEPS
6.5.2 General
To create, delete, perform a copy switch, enable automatic and manual copy switching refer to
6.4 “Administer Duplex Switching Equipment Protection Group” (p. 143).
Per convention, the equipment with the lower AID position is the protected equipment, and the
equipment with the higher AID position is the protecting equipment.
The command is denied if the protecting entity is supporting "in Service" facilities.
The SW-DX-EQPT command performs a copy switch for the specified redundant (duplexed)
equipment. Either copy of equipment can be specified; the command performs a switch regardless
of which copy of equipment is specified (the active copy becomes standby and the standby copy
becomes active).
This command applies to 1:1 protected modules only (EC320, MT320, PP10AD/ATM).
ALW-SWDX-EQPT enables (allows) automatic and manual copy switching for the specified one-for-
one redundant (duplex) equipment. Either copy of equipment can be specified; the command
enables copy switching on both copies of equipment.
The command applies to the following 1:1 protected modules: PP10AD with
PROVISIONEDTYPE=PP10GATM
INH-SWDX-EQPT disables (inhibits) automatic and manual copy switching for the specified one-for-
one redundant (duplex) equipment. Either copy of equipment can be specified; the command
disables automatic and manual copy switching for both copies of equipment.
It is necessary to issue the ALW-SWDX-EQPT in order to deactivate this inhibit condition.
The command applies to the following 1:1 protected modules: PP10AD with
PROVISIONEDTYPE=PP10GATM
This command sets the SST of PSI and sets the condition type of INHSWDX on the specified AID
and on its mate.
For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 Transport
Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.
6.5.4 Procedure
Select action.
• To retrieve information on a duplex switching ATM protection group see Step 2.
• To delete a duplex switching ATM protection group see Step 5.
• To perform copy switch for redundant ATM equipment, go to Step 4.
• To enable (allow) automatic and manual copy switching for the specified one-for-one
redundant (duplex) equipment, go to Step 6.
• To disable (inhibit) automatic and manual copy switching for the specified one-for-one
redundant (duplex) ATM equipment, go to Step 7.
2
Retrieve information on a duplex switching ATM protection group
Enter:
RTRV-DX-EQPT::AID;
where:
AID = Equipment Access Identifier, identifies the ATM entity access identifier.
Possible values:
• PP10AD-{1-7}-{1-9}-{2-9,12-19} - Adaptation Card Packet Modules 10G
• P42E1-{1-7}-{1-9}-{1-6} - 1646DS 42XE1/T1 Card.
• SCC-{1-7}-{1-9}-{7,8} - 1646DS SCC Card.
• ALL - ALL AID.
Example:
RTRV-DX-EQPT::ALL;
Result:
PP10AD-1-1-6,PP10AD-1-1-9::ACTIVE=PP10AD-1-1-9,CURRREQ=NOREQ
3
Observe output. Possible request switch states (i.e. CURREQ value) are:
1. NOREQ - no request;
2. FAIL- main or spare hardware failure;
3. INHIBIT - operator inhibited the switch, i.e.no switch can been performed.
4
Perform Copy Switch for Redundant Equipment
To perform a MANUAL switch enter:
SW-DX-EQPT::AID:::[MODE];
where:
• AID = Equipment Access Identifier, identifies the equipment entity access identifier.
Possible values:
PP10AD-{1-7}-{1-9}-{2-9,12-19} for Adaptation Card Packet Modules 10G.
• P42E1-{1-7}-{1-9}-{1-6} - 1646DS 42XE1/T1 Card.
• SCC-{1-7}-{1-9}-{7,8} - 1646DS SCC Card.
• MODE = Command Mode, identifies the Command Execution Mode.
Possible values: NORM, FRCD.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
5
Duplex switching ATM protection group Deletion
Enter:
DLT-DX-EQPT::AID1,AID2::::[CMDMDE=];
where:
• AID1 = Equipment Access Identifier, identifies the protected equipment entity of the duplex
switching equipment protection group.
Possible values:
− PP10AD-{1-7}-{1-9}-{2-9,12-19} - Adaptation Card Packet Modules 10G
− P42E1-{1-7}-{1-9}-{1,3,5} - 1646DS 42XE1, protected module
• AID2 = Equipment Access Identifier, identifies the protecting equipment entity of the duplex
switching equipment protection group.
Possible values:
− PP10AD-{1-7}-{1-9}-{2-9,12-19} - Adaptation Card Packet Modules 10G
− P42E1-{1-7}-{1-9}-{2,4,6} - 1646DS 42XE1, protecting module
• CMDMDE = Command Mode, identifies the Command Execution Mode.
Possible values:
− NORM
− FRCD.
Note: This command fails when both protection units are in UEQ state and CMDMDE is
specified as FRCD and if the unit specified by AID2 is providing actual service (WRK
secondary state).
This command can be done also in the following cases:
• the protecting board is ACTIVE
• if the specified one-for-one redundant (duplex) equipment automatic and manual copy
switching has been disabled (inhibited). In this case there is a switchback on the MAIN
and the SPARE reboots.
Example: dlt-dx-eqpt::PP10AD-1-1-6,PP10AD-1-1-9;
6
To enable (allow) automatic and manual copy switching for Redundant Equipment
Enter:
ALW-SWDX-EQPT::AID;
where:
AID = Equipment Access Identifier, identifies the equipment entity access identifier.
Possible value is: PP10AD-{1-7}-{1-9}-{2-9,12-19} - Adaptation Card Packet Modules 10G.
P42E1-{1-7}-{1-9}-{1-6} - 1646DS 42XE1/T1 Card.
Result: This command removes the SST of PSI on the specified AID and on its mate.
Example: ALW-SWDX-EQPT::PP10AD-1-1-6;
7
To disable (inhibit) automatic and manual copy switching for the specified one-for-one
redundant (duplex) ATM equipment
Enter:
INH-SWDX-EQPT::AID;
where:
AID = Equipment Access Identifier, identifies the equipment entity access identifier.
Possible value is: PP10AD-{1-7}-{1-9}-{2-9,12-19} - Adaptation Card Packet Modules 10G.
P42E1-{1-7}-{1-9}-{1-6} - 1646DS 42XE1/T1 Card.
Result: This command sets the SST of PSI and sets the condition type of INHSWDX on the
specified AID and on its mate.
Example: INH-SWDX-EQPT::PP10AD-1-1-6;
END OF STEPS
6.6.2 Prerequisites
None.
6.6.3 General
The ACT-DB-BACKUP command performs a database backup of the primary backup database
(ACT DSK DB) to the secondary backup data base (STDBY DB). The database information backed
up includes provisioning, cross-connection, loopback, and test access information. The system also
writes the system type, the software release identifier, the site identifier, and the backup date and
time stamp to the STDBY DB. The system also writes a Cyclic Redundancy Check (CRC) number,
which is used to validate the accuracy of the data on the backup media.
The CRC is generated and stored on the backup media. If the system database is to be restored
using the data on the media, the system generates a new CRC number by reading the backup data
on the media. If the numbers match, the data's accuracy is validated.
Normal system operation continues during database backup.
If ACT-DB-BACKUP hasn't executed successfully, the system sets the DBF condition. The DBF is
set against the COMMON AID. A DBF condition is cleared by successfully completing a subsequent
ACT-DB-BACKUP command.
A CANC-DB-BACKUP command cancels the backup procedure currently in progress.
6.6.4 Procedure
1
Select action.
To activate database backup, go to Step 2.
To cancel database backup, go to Step 5.
2
Activate Database Backup
Enter ACT-DB-BACKUP;
3
Wait for command to complete, with the following format:
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
4
Go to Step 6.
5
Cancel Database Backup
Enter CANC-DB-BACKUP;
6
STOP. This procedure is complete.
END OF STEPS
6.7.2 Prerequisites
None.
6.7.3 General
The RTRV-DB-LABEL command reads the database label from the selected backup database
stored on the NE (ACT DSK DB or STDBY DB). If STDBY DB is selected and VERIFY is specified
for the VER parameter, a Cyclic Redundancy Check (CRC) verification of the database is
performed. If the calculated CRC and stored CRC do not match, an unsuccessful response (DENY)
message is returned.
The RESTORE-DB command copies the backup database stored on the STDBY DB to the primary
backup database (ACT-DSK-DB) and resets the system to activate the new database.
After the RESTORE-DB command is executed, no TL1 functionality (commands to perform
provisioning, cross-connection, manual protection switching, etc.) is allowed until the restored
database is active in the system.
The database restoral operation verifies the System Type, software release identifier, and Site ID
(SID) of the system against that stored on the STDBY DB. A database restoral with a System Type
mismatch cannot be performed. A database restoral with a software release identifier or SID
mismatch also cannot be performed unless the CMDMDE parameter is set to FRCD.
The database restoral operation also verifies the CRC calculated for the database from the STDBY
DB against the CRC stored for the database. A database restoral with a CRC mismatch cannot be
performed.
6.7.4 Procedure
1
Enter RTRV-DB-LABEL::[AID]:;
where: AID = Access Identifier, identifies the databases to retrieve labels from. Possible values:
STBYDB (The system's secondary backup database) or ACTDSKDB (The system's primary
backup database)
2
Examine output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<AID>:[<SYSTYPE>],[<RLSID>],[<SID>],[<DATE>],[<TIME>][,<CRC>]" cr lf
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
Ensure correct backup for this software version and SID is correct.
3
Restore Database
Enter RESTORE-DB::::::[CMDMDE=];
where: CMDMDE = Command mode identifies the Command Execution Mode. Possible
values:
• FRCD Forced, the database restoral operation is performed regardless of the following:
The BACKUP-DATE and BACKUP-TIME indicated for the STBYDB is older/prior to the
BACKUP-DATE and BACKUP-TIME on the system (represented in label of the Active Local
Primary Hard disk Database).
The SID indicated on the STBY DB does not match the SID of the system.
The software release identifier indicated for the STBYDB does not match the software
release identifier indicated for the system.
• NORM Normal: The command is denied if there is a mismatch between the SID, the software
release identifier, system type or the backup time stamp of the system and the information
stored in the STBYDB.
4
Did RESTORE-DB command complete?
If yes, go to Step 6.
If no, go to Step 5.
5
Contact Nokia for assistance .
6
STOP. This procedure is complete.
END OF STEPS
6.8.2 Prerequisites
An <ETH> facility can be assigned to an ethernet port.
If the facility provisioning mode of this NE is automatic, i.e., PROVMODE = AUTOEQ-AUTOFC,
then commands described in this procedure cannot be used to enter and/or delete facilities. In this
mode, facilities are automatically entered when the supporting equipment is entered (See
6.35 “Administer System Configuration” (p. 253)and 6.67 “Provision Equipment” (p. 385)) and
facility deletion occurs only when the supporting equipment or logical resource is deleted (See
6.35 “Administer System Configuration” (p. 253) ).
6.8.3 General
Gigabit Ethernet facilities are associated with ports on a GBE module, and support GBEVCG
facilities for EPL point to point ethernet transmission.
Executing the procedure causes the primary state transitions for the specified <ETH> port.
Secondary states associated with the GBE after the command is executed depend upon events
detected by the system.
When a <ETH> facility is provisioned to an OOS-MA state, a MAN condition type is set for the
specified <ETH>.
When this command is successfully executed on a port residing on a and 8XSO, 10XAR, or other
multi-rate module, the other possible facilities that could have been provisioned on that port will
enter OOS-AUMA, UAS, DSBLD state.
This command manages gigabit ethernet (GBE) or the ten gigabit ethernet (GBE10) port facilities
on the following modules:
• 10XANY 10 by Any port module
• PP1GESY Data port module with sync capability
• PP1GE Data port module (10 port)
• PP1GEX20 Data port module (20 port)
• PP10GEX2 Data port module (2 port)
• PP10GESY: Data port module with sync capability (GBE)
• DWLA10X: Optical Transponder (client port) for GBE10
• PP10GESY: Data port module with sync capability for GBE10
For GBE facilities this will occur if one of the following conditions is present:
• one of its embedded facilities (VCG) has SDEE condition
• loopback is in effect
6.8.4 Procedure
Select action:
• Retrieve GBE or GBE10 client signal facility, go to Step 2
• Provision GBE or GBE10 client signal facility, go to Step 4
• Deprovision GBE or GBE10 client signal facility, go to Step 5
• Modify GBE or GBE10 client signal facility, go to Step 9
2
Retrieve GBE or GBE10 client signal facility
Enter RTRV-<ETH>::AID;
where:
• <ETH> = GBE or GBE10 client signal facility
• AID = Access identifier of <ETH> facility. Possible values:
− ALL
− GBE-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10 } GBE port on a 10xAny module
− GBE-{1-7}-{1-9}-{2-9,12-19}-{1-10} GBE Port on Packet Module PP1GE or PP1GESY
− GBE-{1-7}-{1-9}-{2-9,12-19}-{1-20} GBE Port on Packet Module PP1GEX20
− GBE10-{1-7}-{1-9}-{2-9,12-19,21-36}-1 10 GBE Port on a DWLA10X
− GBE10-{1-7}-{1-9}-{2-9,12-19}-{1} 10 GBE Port on Packet Module PP10GE or
PP10GESY
− GBE10-{1-7}-{1-9}-{2-9,12-19}-{1,2} 10 GBE Port on Packet Module PP10GEX2
3
Examine output for provisioning information on facility, as detailed in the relevant command
guide, refer to “Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<AID>::[AINSTH=<value>][,AINSTIMER=<value>][,AINSCRIT=<value>][,
PSTCORR=<value>][,PMODE=<value>][,NEGOTN=<value>][,FLOWCONT=<value>]
[,ALMPROF=<value>][,TCAPROF=<value>][,MGRACD=<value>]:<PST>,<SST>"
cr lf
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
4
Provision GBE or GBE10 client signal facility
For details, refer to 6.67 “Provision Equipment” (p. 385).
Ensure that port is in valid state for provisioning (OOS-MA).
5
Deprovision GBE or GBE10 client signal facility
Enter RTRV-<ETH>::AID;
where:
• <ETH> = GBE or GBE10 client signal facility.
• AID = Access identifier of <ETH> facility
6
Examine output for provisioning information on port, as detailed in the relevant command guide,
refer to “Command details” (p. 107).
• for GBE
• for GBE10
7
Does port have PST of IS-NR, OOS-AUMA, OOS-AU, OOS-MA?
If yes, the delete command cannot be performed on the specified <ETH> port. Go to Step 13.
If no, go to Step 8.
8
For details refer to 6.47 “Deprovision Equipment” (p. 308).
Note: When this command is successfully executed, the laser on the affected port shall
be turned OFF
9
Modify GBE or GBE10 client signal facility
Enter RTRV-<ETH>::AID;
where:
• <ETH> = GBE or GBE10 client signal facility.
• AID = Access identifier of <ETH> facility.
10
Examine output for provisioning information on port as detailed in the relevant command guide,
refer to “Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<AID>::[AINSTH=<value>][,AINSTIMER=<value>][,AINSCRIT=<value>][,
PSTCORR=<value>][,PMODE=<value>][,NEGOTN=<value>][,FLOWCONT=<value>]
[,ALMPROF=<value>][,TCAPROF=<value>][,MGRACD=<value>]:<PST>,<SST>"
cr lf
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf];
Possibility of service interruption. Editing port parameters of a traffic bearing port can
adversely affect service.
11
Modify GBE10
Enter ED-GBE10::AID::::[AINSTH=][,PMODE=][,AINSCRIT=][,PSTCORR=][,
S1TRANS=][,TCDLY=][,ALMPROF=][,CMDMDE=]:[PST],[SST];
where:
• AID = Access identifier of <ETH> facility. Possible values as described above.
Note: S1TRANS = This parameter is only valid for ports belonging to PP10GE,
PP10GEX2, and PP10GESY modules. On PP10GE only the value of NONE is supported.
TCDLY= This parameter is only valid for ports belonging to PP10GE, PP10GEX2 and
PP10GESY modules.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
12
Modify GBE
Enter
ED-GBE::AID::::[AINSTH=][,PMODE=][,AINSCRIT=][,PSTCORR=][,CMDMDE=][,
FLOWCONT=][,NEGOTN=][,CSF=][,SSF=][,ALMPROF=][,TCAPROF=][,S1TRANS=][,
TCDLY=]:[PST][,SST];
where.
AID = Access identifier of GBE facility.
S1TRANS = Sync message byte to be transmitted, determines if the transmitted byte will have
the “DUS” message or will have the actual traceability of the signal.
This parameter is only valid for ports belonging to PP1GE, PP1GEX20 and PP1GESY
modules. PP1GE value is restricted to NONE
TCDLY = Transparent Clock Delay, indicates the delay to be considered by IEEE1588v2
protocol for Transparent Clock transport. The delay is due to asymmentrical length of the fiber
on the link. The length difference determines a propagation delay equal to 2*D, where D is the
value to be provisioned.
This parameter is only valid for ports belonging to PP1GE, PP1GEX20, and PP1GESY
modules
13
STOP. This procedure is complete.
END OF STEPS
Class 4: ADDRP, this connection class configures the channel added/dropped in/from DWDM
system. Logically the optical connection moves from MUX Channel to line port of a Transponder or
other tributary card.
Each class must be requested with a separate command issue; more than one class can not be
provided in a single command issue.
Each ENT-EQPT-OCONN command, successfully executed, determines the provisioning of
appropriate facilities, according configuration.
Due Hardware configuration of the MUX devices, not every optical connection class can be set up
sequencially:
• Cascade connection can not be set up if a Passthrough connection is already in place;
• Cascade connection can not be set up if a Drop connection is already in place in L2 band;
• Cascade connection can not be set up if a Line connection is in place for MUX on L2 band; and
viceversa Line connection for a MUX on L2 band can not be set up if it involved in a Cascade
connection.
According the optical classes porvisoned in the command, the following table specifies associated
facilities to be proviosioned.
LEGENDA: M: MUX; L: LOFA; M1: MUX L1; MUX L2; L1 LOFA for MUX L1; L2 LOFA for MUX L2;
LE: LOFA East side; LW: LOFA West side; ME: MUX East side; MW: MUX West side.
INPUT CONN CLASS Facility to be provisioned
LINE ots(L), oms(M), 8 omsoch(M)
CSD ots(M1), oms(M1), 16 omsoch(M1)
PT ots(ME), oms(ME), omsband(ME), ots(MW),
oms(MW), omsband(MW), 8 omsoch(ME), 8
omsoch(MW)
ADDRP ots(M), oms(M), 8 omsoch(M), 1 omsochif(M)
LINE&CSD (Note) ots(L1), oms(M1), 16 omsoch(M1
LINE&PT (Note) ots(M1E), oms(M1E), omsband(M1E),
ots(M1W/M2W), oms(M1W/M2W),
omsband(M1W/M2W), 16 omsoch(M1E), 8
omsoch(M1W/M2W)
LINE&ADDRP (Note) ots(M1), oms(M1), 16 omsoch(M1), 1
omsochif(M1/M2)
CSD&PT (Note) ots(M1E), oms(M1E), omsband(M1E),
ots(M1W/M2W), oms(M1W/M2W),
omsband(M1W/M2W), 16 omsoch(M1E), 8
omsoch(M1W/M2W)
CSD&ADDRP (Note) ots(M1), oms(M1), 16 omsoch(M1), 1
omsochif(M1/M2)
Note: such provisioning is the result of separate ENT-EQPT-OCONN issue, one for each
optical class specified in the column.
6.10.2 General
LINE connection class establishes if the DWDM line is amplified or not; it indicates an optical
connection between a MUX and Line amplifier. If the line is not amplified this optical connection is
not present in the Node itself.
For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 Transport
Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.
Cascade connection can not be set up if a Line connection is in place for MUX on L2 band; and
viceversa Line connection for a MUX on L2 band can not be set up if it involved in a Cascade
connection.
6.10.4 Procedure
1
Retrieve the board supporting optical connection Access Identifiers.
Enter:
RTRV-EQPT-OPORT::[EQPT-AID]::::[OPORT=];
where:
EQPT-AID = Access Identifier identifying the board supporting optical ports.
Value Description
ALL
OT2TDM-{1-7}-{1-9}-{2-9,12-19,21-36} G.709 OTU 10GB Card - Provisioned Type =
1POTU2
DWLA10X-{1-7}-{1-9}-{2-9,12-19,21-36} DWDM Optical Transponder
LOFA-{1-7}-{1-9}-{6-9,12-15} Line Optical Filter and Attenuator
OMDX8-{1-7}-{1-9}-{6-9,12-15} DWDM MUX/DEMUX 8 channels
OPORT = Access Identifier identifying the FROM connector to be cabled. AID can identify one
connector of LINE connection between a MUX and Line amplifier.
Value Description
ALL
LOFOMSPORT-{1-7}-{1-9}-{6-9,12-15}- 1 LOFA OMS Bidir port towards the
multiplexer
OMDOMSPORT-{1-7}-{1-9}-{6-9,12-15} -1 OMS Bidir Port on an OMDX8100 L1 or L2
OMDBANDPORT-{1-7}-{1-9}-{6-9,12-15 OMD BAND Passthrough Bidir Port on an
}-{EXP} OMDX8100 L1 or L2
OMDOCHPORT-{1-7}-{1-9}-{6-9,12-15} OCH Bidir Port on an OMDX8100 L1 or L2
-F{9380, 9370, 9360, 9350, 9330, 9320,
9310, 9300, 9280, 9270, 9260, 9250, 9240,
9230, 9220, 9210, 9200}
OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, OTU2 Bidir Line port, on a DWLA10X
29-36}-L1 module
OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, OTU2 Bidir colored port, on a 1POTU2
29-36}-1 module
Note: LINE connection can be done only between a MUX and Line amplifier.
2
Create the optical connection between a MUX and Line amplifier.
Enter:
ENT-EQPT-OCONN::::::[LNFROM=][,LNTO=];
where:
LNFROM = Access Identifier identifying the FROM connector to be cabled. AID can identify one
connector of LINE connection between a MUX and Line amplifier.
Value Description
LOFOMSPORT-{1-7}-{1-9}-{6-9,12-15}- 1 LOFA OMS Bidir port towards the
multiplexer
OMDOMSPORT-{1-7}-{1-9}-{6-9,12-15} -1 OMS Bidir Port on an OMDX8100 L1 or L2
LNTO = Access Identifier identifying the TO connector to be cabled. AID can identify one
connector of LINE connection between a MUX and Line amplifier.
Value Description
OMDBANDPORT-{1-7}-{1-9}-{6-9,12-15 OMD BAND Passthrough Bidir Port on an
}-{EXP} OMDX8100 L1 or L2
OMDOCHPORT-{1-7}-{1-9}-{6-9,12-15} OCH Bidir Port on an OMDX8100 L1 or L2
-F{9380, 9370, 9360, 9350, 9330, 9320,
9310, 9300, 9280, 9270, 9260, 9250, 9240,
9230, 9220, 9210, 9200}
where:
AID = OTS Access Identifier, specifies the selected OTS facility to which the command is
directed.
OTS facility will be present on the LOFA.
4
Remove an OMDX8 facility
The REMOVE command causes the specified facility to be placed in an out-of-service (OOS-MA
or OOS-AUMA) state for maintenance purposes.
5
Restore an OMDX8 Facility
The RESTORE command causes the specified facility to be placed in an IS or OOS-AU state.
Executing this command causes a state transition for the specified facility from:
• OOS-MA to IS
• OOS-AUMA to OOS-AU.
END OF STEPS
6.11.2 General
PASSTHROUGH: this connection class configures the passthrough between MUX channels. In
case of line terminal configuration, this optical connection is not present.
For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 Transport
Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.
6.11.4 Procedure
1
Retrieve the board supporting optical connection Access Identifiers.
Enter:
RTRV-EQPT-OPORT::[EQPT-AID]::::[OPORT=];
where:
EQPT-AID = Access Identifier identifying the board supporting optical ports.
Value Description
ALL
OT2TDM-{1-7}-{1-9}-{2-9,12-19,21-36} G.709 OTU 10GB Card - Provisioned Type =
1POTU2
DWLA10X-{1-7}-{1-9}-{2-9,12-19,21-36} DWDM Optical Transponder
LOFA-{1-7}-{1-9}-{6-9,12-15} Line Optical Filter and Attenuator
OMDX8-{1-7}-{1-9}-{6-9,12-15} DWDM MUX/DEMUX 8 channels
OPORT = Access Identifier identifying the FROM connector to be cabled. AID can identify one
connector of LINE connection between a MUX and Line amplifier.
Value Description
ALL
LOFOMSPORT-{1-7}-{1-9}-{6-9,12-15}- 1 LOFA OMS Bidir port towards the
multiplexer
OMDOMSPORT-{1-7}-{1-9}-{6-9,12-15} -1 OMS Bidir Port on an OMDX8100 L1 or L2
OMDBANDPORT-{1-7}-{1-9}-{6-9,12-15 OMD BAND Passthrough Bidir Port on an
}-{EXP} OMDX8100 L1 or L2
OMDOCHPORT-{1-7}-{1-9}-{6-9,12-15} OCH Bidir Port on an OMDX8100 L1 or L2
-F{9380, 9370, 9360, 9350, 9330, 9320,
9310, 9300, 9280, 9270, 9260, 9250, 9240,
9230, 9220, 9210, 9200}
OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, OTU2 Bidir Line port, on a DWLA10X
29-36}-L1 module
OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, OTU2 Bidir colored port, on a 1POTU2
29-36}-1 module
2
Enter:
ENT-EQPT-OCONN::::::[PSSTRFROM=][,PSSTRTO=];
where:
PSSTRFROM = Access Identifier identifying the FROM connector to be cabled. AID can identify
only one connector of the passthrough between MUX channels. Connectors can be channel
specific (OMDOCHPORT) or a bundle of channels (OMDBANDPORT).
Value Description
OMDBANDPORT-{1-7}-{1-9}-{6-9,12-15 OMD BAND Passthrough Bidir Port on an
}-{EXP} OMDX8100 L1 or L2
OMDOCHPORT-{1-7}-{1-9}-{6-9,12-15} OCH Bidir Port on an OMDX8100 L1 or L2
-F{9380, 9370, 9360, 9350, 9330, 9320,
9310, 9300, 9280, 9270, 9260, 9250, 9240,
9230, 9220, 9210, 9200}
PSSTRTO = Access Identifier identifying the TO connector to be cabled. AID can identify only
one connector of the passthrough between MUX channels. Connectors can be channel specific
(OMDOCHPORT) or a bundle of channels (OMDBANDPORT).
Value Description
OMDBANDPORT-{1-7}-{1-9}-{6-9,12-15 OMD BAND Passthrough Bidir Port on an
}-{EXP} OMDX8100 L1 or L2
OMDOCHPORT-{1-7}-{1-9}-{6-9,12-15} OCH Bidir Port on an OMDX8100 L1 or L2
-F{9380, 9370, 9360, 9350, 9330, 9320,
9310, 9300, 9280, 9270, 9260, 9250, 9240,
9230, 9220, 9210, 9200}
AID = OTS Access Identifier, specifies the selected OTS facility to which the command is
directed.
4
Remove an OMDX8 facility
The REMOVE command causes the specified facility to be placed in an out-of-service (OOS-MA
or OOS-AUMA) state for maintenance purposes.
5
Restore an OMDX8 Facility
The RESTORE command causes the specified facility to be placed in an IS or OOS-AU state.
• RST-OMSBAND::AID;
where:
AID = Access Identifier, specifies the facility.
i.e. AID value is OMSBAND-{1-7}-{1-9}-{6-9,12-15}-1-1 (OMSBAND Facility on an
OMDX8100 L1 or L2)
• RMV-OMSOCH::AID;
where:
AID = Access Identifier, specifies the facility.
i.e. AID value is OMSOCH-{1-7}-{1-9}-{6-9,12-15}-1-F{9 380, 9370, 9360, 9350, 9330, 9320,
9310, 9300, 9280, 9270, 9260, 9250, 9240, 9230, 9220, 9210, 9200} (OMSOCH facility on an
OMDX8100 L1 or L2).
• RST-OTS::AID;
where:
AID = Access Identifier, specifies the facility.
i.e. AID value is OTS-{1-7}-{1-9}-{6-9,12-15}-1 (OTS Facility on a LOFA or on OMDX8100 L1
or L2)
Executing this command causes a state transition for the specified facility from:
• OOS-MA to IS
• OOS-AUMA to OOS-AU.
END OF STEPS
6.12.2 General
CASCADE: this connection class configures the cascade of MUX/DMUX devices. Cascade has to
be configured, when DWDM system shall operate with channels supported not only by a single type
of MUX.
For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 Transport
Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.
Due Hardware configuration of the MUX devices, not every optical connection class can be set up
sequencially:
• Cascade connection can not be set up if a Passthrough connection is already in place;
• Cascade connection can not be set up if a Drop connection is already in place in L2 band;
• Cascade connection can not be set up if a Line connection is in place for MUX on L2 band; and
viceversa Line connection for a MUX on L2 band can not be set up if it involved in a Cascade
connection.
6.12.4 Procedure
1
Retrieve the board supporting optical connection Access Identifiers.
Enter:
RTRV-EQPT-OPORT::[EQPT-AID]::::[OPORT=];
where:
EQPT-AID = Access Identifier identifying the board supporting optical ports.
Value Description
ALL
OT2TDM-{1-7}-{1-9}-{2-9,12-19,21-36} G.709 OTU 10GB Card - Provisioned Type =
1POTU2
DWLA10X-{1-7}-{1-9}-{2-9,12-19,21-36} DWDM Optical Transponder
LOFA-{1-7}-{1-9}-{6-9,12-15} Line Optical Filter and Attenuator
OMDX8-{1-7}-{1-9}-{6-9,12-15} DWDM MUX/DEMUX 8 channels
OPORT = Access Identifier identifying the FROM connector to be cabled. AID can identify one
connector of LINE connection between a MUX and Line amplifier.
Value Description
ALL
LOFOMSPORT-{1-7}-{1-9}-{6-9,12-15}- 1 LOFA OMS Bidir port towards the
multiplexer
OMDOMSPORT-{1-7}-{1-9}-{6-9,12-15} -1 OMS Bidir Port on an OMDX8100 L1 or L2
OMDBANDPORT-{1-7}-{1-9}-{6-9,12-15 OMD BAND Passthrough Bidir Port on an
}-{EXP} OMDX8100 L1 or L2
Value Description
OMDOCHPORT-{1-7}-{1-9}-{6-9,12-15} OCH Bidir Port on an OMDX8100 L1 or L2
-F{9380, 9370, 9360, 9350, 9330, 9320,
9310, 9300, 9280, 9270, 9260, 9250, 9240,
9230, 9220, 9210, 9200}
OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, OTU2 Bidir Line port, on a DWLA10X
29-36}-L1 module
OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, OTU2 Bidir colored port, on a 1POTU2
29-36}-1 module
2
Enter:
ENT-EQPT-OCONN::::::[CSDFROM=][,CSDTO=];
CSDFROM = Access Identifier identifying the FROM connector to be cabled. AID can identify
only one connector of bidirectional CASCADE connection. This connection class configures the
cascade of MUX/DMUX devices.
Value Description
OMDBANDPORT-{1-7}-{1-9}-{6-9,12-15 OMD BAND Passthrough Bidir Port on an
}-{EXP} OMDX8100 L1 or L2
OMDOMSPORT-{1-7}-{1-9}-{6-9,12-15} -1 OMS Bidir Port on an OMDX8100 L1 or L2
CSDTO = Access Identifier identifying the TO connector to be cabled. AID can identify only one
connector of bidirectional CASCADE connection. This connection class configures the cascade
of MUX/DMUX devices.
Value Description
OMDOMSPORT-{1-7}-{1-9}-{6-9,12-15} -1 OMS Bidir Port on an OMDX8100 L1 or L2
OMDBANDPORT-{1-7}-{1-9}-{6-9,12-15 OMD BAND Passthrough Bidir Port on an
}-{EXP} OMDX8100 L1 or L2
• RTRV-OMSOCH::AID::::[PARMS=];
where:
AID = OMSOCH Access Identifier, specifies the selected OMSOCH facility to which the
command is directed.
• RTRV-OTS::AID::::[PARMS=];
where:
AID = OTS Access Identifier, specifies the selected OTS facility to which the command is
directed.
4
Remove an OMDX8 facility
The REMOVE command causes the specified facility to be placed in an out-of-service (OOS-MA
or OOS-AUMA) state for maintenance purposes.
5
Restore an OMDX8 Facility
The RESTORE command causes the specified facility to be placed in an IS or OOS-AU state.
Executing this command causes a state transition for the specified facility from:
• OOS-MA to IS
• OOS-AUMA to OOS-AU.
END OF STEPS
6.13.2 General
ADDRP: this connection class configures the channel added/dropped in/from DWDM system.
Logically the optical connection moves from MUX Channel to line port of a Transponder or other
tributary card.
For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 Transport
Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.
6.13.4 Procedure
1
Retrieve the board supporting optical connection Access Identifiers.
Enter:
RTRV-EQPT-OPORT::[EQPT-AID]::::[OPORT=];
EQPT-AID = Access Identifier identifying the board supporting optical ports.
Value Description
ALL
OT2TDM-{1-7}-{1-9}-{2-9,12-19,21-36} G.709 OTU 10GB Card - Provisioned Type =
1POTU2
DWLA10X-{1-7}-{1-9}-{2-9,12-19,21-36} DWDM Optical Transponder
LOFA-{1-7}-{1-9}-{6-9,12-15} Line Optical Filter and Attenuator
OMDX8-{1-7}-{1-9}-{6-9,12-15} DWDM MUX/DEMUX 8 channels
OPORT = Access Identifier identifying the FROM connector to be cabled. AID can identify one
connector of LINE connection between a MUX and Line amplifier.
Value Description
ALL
LOFOMSPORT-{1-7}-{1-9}-{6-9,12-15}- 1 LOFA OMS Bidir port towards the
multiplexer
OMDOMSPORT-{1-7}-{1-9}-{6-9,12-15} -1 OMS Bidir Port on an OMDX8100 L1 or L2
OMDBANDPORT-{1-7}-{1-9}-{6-9,12-15 OMD BAND Passthrough Bidir Port on an
}-{EXP} OMDX8100 L1 or L2
OMDOCHPORT-{1-7}-{1-9}-{6-9,12-15} OCH Bidir Port on an OMDX8100 L1 or L2
-F{9380, 9370, 9360, 9350, 9330, 9320,
9310, 9300, 9280, 9270, 9260, 9250, 9240,
9230, 9220, 9210, 9200}
OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, OTU2 Bidir Line port, on a DWLA10X
29-36}-L1 module
OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, OTU2 Bidir colored port, on a 1POTU2
29-36}-1 module
2
Enter:
ENT-EQPT-OCONN::::::[ADDRPFROM=][,ADDRPTO=];
where:
ADDRPFROM = Access Identifier identifying the TO connector to be cabled. AID can identify
only one connector of bidirectional ADDRP connection. This connection class configures the
channel added/dropped in/from DWDM system. Logically the optical connection moves from
MUX Channel to line port of a Transponder or other tributary card.
Value Description
OMDOCHPORT-{1-7}-{1-9}-{6-9,12-15} OCH Bidir Port on an OMDX8100 L1 or L2
-F{9380, 9370, 9360, 9350, 9330, 9320,
9310, 9300, 9280, 9270, 9260, 9250, 9240,
9230, 9220, 9210, 9200}
OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, OTU2 Bidir Line port, on a DWLA10X
29-36}-L1 module
OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, OTU2 Bidir colored port, on a 1POTU2
29-36}-1 module
EXTERNAL
ADDRPTO = Access Identifier identifying the TO connector to be cabled. AID can identify only
one connector of bidirectional ADDRP connection. This connection class configures the channel
added/dropped in/from DWDM system. Logically the optical connection moves from MUX
Channel to line port of a Transponder or other tributary card.
Value Description
OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, OTU2 Bidir Line port, on a DWLA10X
29-36}-L1 module
OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, OTU2 Bidir colored port, on a 1POTU2
29-36}-1 module
OMDOCHPORT-{1-7}-{1-9}-{6-9,12-15} OCH Bidir Port on an OMDX8100 L1 or L2
-F{9380, 9370, 9360, 9350, 9330, 9320,
9310, 9300, 9280, 9270, 9260, 9250, 9240,
9230, 9220, 9210, 9200}
EXTERNAL
• RTRV-OMSBAND::AID::::[PARMS=];
where:
AID = OMSBAND Access Identifier, specifies the selected OMSBAND facility to which the
command is directed.
• RTRV-OMSOCH::AID::::[PARMS=];
where:
AID = OMSOCH Access Identifier, specifies the selected OMSOCH facility to which the
command is directed.
• RTRV-OTS::AID::::[PARMS=];
where:
AID = OTS Access Identifier, specifies the selected OTS facility to which the command is
directed.
4
Remove an OMDX8 facility
The REMOVE command causes the specified facility to be placed in an out-of-service (OOS-MA
or OOS-AUMA) state for maintenance purposes.
5
Restore an OMDX8 Facility
The RESTORE command causes the specified facility to be placed in an IS or OOS-AU state.
Executing this command causes a state transition for the specified facility from:
• OOS-MA to IS
• OOS-AUMA to OOS-AU.
END OF STEPS
6.14.2 Prerequisites
The GBE10 facility to be placed in loopback must have a .PST of OOS-AUMA or OOS-MA and not
have an SST of LPBK (i.e. it is not already in a loopback).
6.14.3 General
The RTRV-LPBK-GBE10 command retrieves the GBE10 facilities that are in a loopback within the
specified range of GBE10 AIDs. The command is executed regardless of the provisioning of the
specified facilities.
The successful response for a RTRV-LPBK-GBE10 contains one line of parsable data, in ascending
order, for each GBE10 facility that is in a loopback within the specified range of AIDs. No output
data is returned for an AID that is not in a loopback.
The OPR-LPBK-GBE10 command establishes a near-end or far-end facility or terminal loopback on
the specified GBE10 facility.
The RLS-LPBK-GBE10 command releases the loopback previously established by an OPR-LPBK-
GBE10 command on the specified GBE10 facility.
To execute a near-end or far-end RLS-LPBK-GBE10, the specified GBE10 must have a PST of IS.
For parameter descriptions of TL1 commands used in this procedure, refer to the “Command
details” (p. 107).
6.14.4 Steps
NOTICE
2
Review the GBE10 loopback diagrams.
3
Select action.
To retrieve current loopback status of GBE10 facility, go to Step 4.
To establish loopback, go to Step 7.
To verify loopback status, go to Step 13.
To release loopback, go to Step 16.
To end this procedure, go to Step 18.
4
Retrieve Loopback Information
Select RTRV-LPBK-GBE10::[AID];
where:
Possible values:
• GBE10-{1-7}-{1-9}-{2-9,12-19,21-36}-1 (10 GBE Port on a DWLA10X)
5
Examine output. One line of information displays for each facility in loopback within specified
range of AIDs. No information displays for facilities that are not in loopback.
6
Go to Step 3.
7
Establish Loopback
Enter RTRV-GBE10::AID; to retrieve the current PST and SST of the GBE10 facility.
where:
AID=GBE10 access identifier
8
Observe output.
9
Select action.
If the PST for the GBE10 facility is IS or OOS-AU, go to Step 10.
If the PST for the GBE10 facility is OOS-AUMA or OOS-MA, go to Step 11.
10
Before establishing a loopback, the facility must be placed out of service.
Enter ED-GBE10::AID:::::OOS;
where:
AID=GBE10 access identifier
11
Enter OPR-LPBK-GBE10::AID:::[LOCN],,,[LPBKTYPE];
where:
AID=OT Client port Access Identifier, specifies the GBE10 facility.
LOCN= Location, identifies the location in which the loopback is performed. Value is: {NEND} -
Near End.
LPBKTYPE= Loopback Type, specifies the type of loopback.
12
Go to Step 3.
13
Verify Loopback Status
Enter RTRV-LPBK-GBE10::[AID]; to verify the GBE10 facility is in loopback status.
where:
AID=OT Client port Access Identifier, specifies the GBE10 facility.
14
Examine output. One line of information displays for each facility in loopback within specified
range of AIDs. No information displays for facilities that are not in loopback.
15
Go to Step 3.
16
Release Loopback
Enter RLS-LPBK-GBE10::AID:::[LOCN],,,[LPBKTYPE]; to release the GBE10 loopback.
where:
AID = GBE10-{1-7}-{1-9}-{2-9,12-19,21-36}-1 (10 GBE Port on a DWLA10X)
LOCN={NEND}
LPBKTYPE={FACILITY, TERMINAL}
17
Enter ED-GBE10::AID:::::IS; to place the facility back in service.
where:
AID=Access identifier of GBE10 facility.
18
STOP. This procedure is complete.
END OF STEPS
6.15.2 Prerequisites
To execute an OPR-LPBK-GBE, the specified GBE must have a PST of OOS-AUMA or OOS-MA
and not have an SST of LPBK (i.e. it is not already in a loopback).
6.15.3 General
The RTRV-LPBK-GBE command retrieves the GBE facilities that are in a loopback within the
specified range of GBE AIDs. The command is executed regardless of the provisioning of the
specified facilities.
The successful response for a RTRV-LPBK-GBE contains one line of parsable data, in ascending
order, for each GBE facility that is in a loopback within the specified range of AIDs. No output data
is returned for an AID that is not in a loopback.
The OPR-LPBK-GBE command establishes a near-end or far-end facility or terminal loopback on
the specified GBE facility.
The RLS-LPBK-GBE command releases the loopback previously established by an OPR-LPBK-
GBE10 command on the specified GBE facility.
To execute a RLS-LPBK-GBE, the specified GBE must have a PST,SST of OOS-AUMA,LPBK or
OOS-MA,LPBK.
For parameter descriptions of TL1 commands used in this procedure, refer to the “Command
details” (p. 107).
6.15.4 Steps
NOTICE
2
Review the GBE loopback diagrams.
3
Select action.
To retrieve current loopback status of GBE facility, go to Step 4.
To establish loopback, go to Step 7.
To verify loopback status, go to Step 13.
To release loopback, go to Step 16.
To end this procedure, go to Step 18.
4
Retrieve Loopback Information
Select RTRV-LPBK-GBE::[AID];
where:
AID=GBE Access Identifier, specifies the GBE facility.
Possible values:
• GBE-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10 } (GBE port on a 10xAny module)
• ALL (ALL AID)
5
Examine output. One line of information displays for each facility in loopback within specified
range of AIDs. No information displays for facilities that are not in loopback.
6
Go to Step 3.
7
Establish Loopback
Enter RTRV-GBE::AID; to retrieve the current PST and SST of the GBE facility.
where:
8
Observe output.
9
Select action.
If the PST for the GBE facility is IS or OOS-AU, go to Step 10.
If the PST for the GBE facility is OOS-AUMA or OOS-MA, go to Step 11.
10
Before establishing a loopback, the facility must be placed out of service.
Enter ED-GBE::AID:::::OOS;
where:
AID=Access identifier of GBE facility.
11
Enter OPR-LPBK-GBE10::AID:::[LOCN],,,[LPBKTYPE];
where:
AID=Access identifier of GBE facility.
LOCN= Location, identifies the location in which the loopback is performed. Value is: {NEND} -
Near End.
LPBKTYPE= Loopback Type, specifies the type of loopback.
12
Go to Step 3.
13
Verify Loopback Status
Enter RTRV-LPBK-GBE::[AID]; to verify the GBE facility is in loopback status.
where:
AID=Access identifier of GBE facility.
14
Examine output. One line of information displays for each facility in loopback within specified
range of AIDs. No information displays for facilities that are not in loopback.
15
Go to Step 3.
16
Release Loopback
Enter RLS-LPBK-GBE::AID:::[LOCN],,,[LPBKTYPE]; to release the GBE loopback.
where:
AID = GBE-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10 } (GBE port on a 10xAny module)
LOCN={NEND}
LPBKTYPE={FACILITY, TERMINAL}
17
Enter ED-GBE::AID:::::IS; to place the facility back in service.
where:
AID=GBE Access Identifier, specifies the GBE facility.
18
STOP. This procedure is complete.
END OF STEPS
6.16.2 Prerequisites
The System shall not permit to modify and/or delete the profile if referenced by a TUSEG and/or
PWSEG.
6.16.3 General
This command permits to define the configuration of MAC DA and other parameters for the
encapsulation of MPLS over ethernet.
In the System there is a pre-defined L2 encapsulation profile identified by L2ENCAPPROF-1 AID,
MAC-DA= all 1 and TAG=UNTAGGED.
The System shall support a maximum of 31 user-defined L2 Encapsulation profiles.
6.16.4 Procedure
1
Select action.
To retrieve L2 Encapsulation Profile information, go to Step 2.
To create L2 Encapsulation Profile, go to Step 5.
To modify L2 Encapsulation Profile parameters, go to Step 7.
To delete L2 Encapsulation Profile, go to Step 9.
To end this procedure, go to Step 10.
2
Retrieve L2 Encapsulation Profile information
Enter RTRV-L2ENCAP-PROF:[TID]:[AID]:[CTAG];
where:
TID = Target IDentifier, identifies the network node TID for the command. Default value is SID.
Valid TID values.
AID = L2 Encapsulation Profile AID. Possible values: ALL or L2ENCAPPROF-{1-32}.
CTAG = Correlation TAG, associates the input command with its output responses.Possible
values are 1-6 Valid CTAG characters.
3
Examine output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
4
Go to Step 1.
5
Create L2 Encapsulation Profile
Enter ENT-L2ENCAP-PROF:[TID]::[CTAG]:::MAC-DA=,TAG=[,VLAN-ID=][,
PRIORITY=] [,DE=];
where:
• TID = Target IDentifier, identifies the network node TID for the command. Default value is
SID. Valid TID values.
• CTAG = Correlation TAG, associates the input command with its output responses.Possible
values are 1-6 Valid CTAG characters.
• MAC-DA = Medium Access Control Address, it is the MAC Destination Address to be used in
case of mapping of MPLS over Ethernet when a switched network is present. Possible values
are 12 hexadecimal characters.
• TAG = Flag Tagged/Untagged. Possible values: UNTAGGED or TAGGED.
• VLAN-ID = This is the VLAN Identifier to be used in case of mapping of MPLS over Ethernet
when a switched network is present (802.1Q mapping). Possible values are {0-4094}.
• PRIORITY = Priority value for TAGGED ethernet frame. Possible values are {0-7}. The
default value is 0.
• DE = Drop Eligible indication according with 802.1ad. The possible values are 0 and 1. The
default value is 0.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
6
Go to Step 1.
WARNING
Optional Content
The System does't permit to modify the profile if referenced by a TUSEG and/or PWSEG.
Optional Content added above. Please modify as needed.
Modify L2 Encapsulation Profile parameters
Enter ED-L2ENCAP-PROF:[TID]:AID:[CTAG]:::[MAC-DA=][,TAG=][,VLAN-ID=][,
PRIORITY=][,DE=];
where:
• AID = L2 Encapsulation Profile AID. Possible values: L2ENCAPPROF-{2-32} - User defined
L2 encapsulation profile.
• VLAN-ID and DE (Drop Eligible indication) are parameters not valid if profile is UNTAGGED.
The parameter values are reffered in Step 5
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
8
Go to Step 1.
WARNING
Optional Content
The System does't permit to delete the profile if referenced by a TUSEG and/or PWSEG.
Optional Content added above. Please modify as needed.
Delete L2 Encapsulation Profile
Enter DLT-L2ENCAP-PROF:[TID]:AID:[CTAG];
where:
• AID = L2 Encapsulation Profile AID. Possible values: L2ENCAPPROF-{2-32}.
The parameter values are reffered in Step 5
10
STOP. This procedure is complete.
END OF STEPS
6.17.2 Prerequisites
The start of the MAC File Collection preparation is allowed when no file collection preparation or file
transfer is in progress. (MACADDCOLLECTIONSTATE equal to READY / EMPTY).
It can be forced when the file preparation is in progress(MACADDCOLLECTIONSTATE equal to
INPREP), but not when the file transfer is in progress (MACADDCOLLECTIONSTATE equal to
FTRUNNING).
6.17.3 General
The mechanism of MAC File Collection is an efficient way of collecting MAC adrresses of the entire
NE in a single file.
After issuing this command the MACADDCOLLECTIONSTATE will become INPREP (in
preparation).
A previously prepared file collection will be no longer available.
The collection of MAC data will be done on the basis of the input filtering, where the input filters
consists of MAC address, port/slot AIDs and FDB IDs.
Ports and slots are not mutually exclusive. A TCAM on board of a SLOTAID learns the triplet Port/
MAC/vsi.
• If only PORTAID is entered, then the command shall start the collection of all the learned triplets
MAC/port/vsi by the TCAM on board of the equipped slots, where port shall be equal to
PORTAID.
• If neither SLOTAID nor PORTAID is entered, then the command shall start the collection of all
the learned triplets MAC/port/vsi by the TCAM on board of the equipped slots, where "port" shall
indicate all the equipped ports.
The MAC File Collection then generated will contain one line (record) fr every retrieved MAC
address in the NE according to the input filtering.
When the MAC File Collection is complete (MACADDCOLLECTIONSTATE equal to READY) the
file is directly available in gzip (compressed) format.
6.17.4
The RTRV-MACGLB-STATUS command retrieves the current status of the MAC File Collection
process.
6.17.5 Procedure
1
Select action.
To retrieve retrieves the current status of the MAC File Collection process, go to Step 2.
To initiates NE globally the preparation of the MAC File Collection, go to Step 7.
2
Retrieve MAC File Collection process Status
Enter RTRV-MACGLB-STATUS;
Result: MACADDCOLLECTIONSTATE Values could be: {EMPTY, READY, INPREP,
FTRUNNING}.
3
Examine output (i.e. MACADDCOLLECTIONSTATE value) before starting MAC File Collection.
4
Is the MACADDCOLLECTIONSTATE = empty?
If yes go to Step 7.
If no, go to Step 5.
5
Is the MACADDCOLLECTIONSTATE value INPREP or FTRUNNING?
If yes, wait until the MACADDCOLLECTIONSTATE becomes READY.
6
Is the MACADDCOLLECTIONSTATE value READY?
To perform a new MAC file collection, go to Step 7.
To retrieve the gzip file, go to Step 8.
7
Start the MAC File Collection
Enter STA-MACGLB:::::[MAC],[PORTAID],[SLOTAID],[FDBIDVLAN],[FDB
IDVPLS],[FDBIDPBB],[TYPE];
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
8
Retrieve the gzip MAC File Collection
END OF STEPS
6.18.2 Prerequisites
The facility provisioning mode of this NE is automatic, i.e., PROVMODE = AUTOEQ-AUTOFC, then
this means that command cannot be used to enter/delete facilities. In this mode, facilities are
automatically entered when the supporting equipment is entered (See 6.35 “Administer System
Configuration” (p. 253)). Besides in this mode, facility deletion occurs only when the supporting
equipment or logical resource is deleted (see 6.35 “Administer System Configuration” (p. 253)).
6.18.3 General
The RTRV-MAU command retrieves the provisioned parameter values, and the current PST,SST
state for the specified MAU port. The MAU port's current provisioned values and conditions (if
provisioned), and state are retrieved from the system database. The command is executed
regardless of the state of the port.
Automatically entered facilities are created with default provisioning, with AINS active.
Provisioning changes may be made to automatically entered facilities using the ED-MAU command.
A MAU (Medium Access Unit) represents the physical layer termination for a sub-set of Ethernet
ports.
6.18.4 Procedure
Select action:
• Retrieve MAU facility information, go to Step 2
• Modify MAU facility parameters, go to Step 4
2
Retrieve MAU facility information
Enter RTRV-MAU::AID;
where: AID = MAU facility
3
Examine output for provisioning information on facility, as detailed in the relevant command
guide, refer to “Command details” (p. 107).
4
Modify MAU facility parameters
Possibility of service interruption. Editing port parameters of a traffic bearing port can
adversely affect service.
5
Enter ED-MAU::AID::::[AINSTH=][,PMODE=][,AINSCRIT=][,PSTCORR=][,CMDMDE=]
[,FLOWCONT=][,NEGOTN=][,CSF=][,SSF=][,ALMPROF=][,TCAPROF=][,S1TRANS=]
[,TCDLY=]:[PST][,SST];
I.e. Sync message byte to be transmitted, determines if the transmitted byte will have the
"DUS" message or will have the actual traceability of the signal.
TCDLY = {-8000 - +8000}. Transparent Clock Delay, indicates the delay to be considered by
IEEE1588v2 protocol for Transparent Clock transport. The delay is due to asymmetrical length
of the fiber on the link. The length difference determines a propagation delay equal to 2*D,
where D is the value to be provisioned.
The parameter applies to the receiver; if length from transmitter to receiver is higher than the
one in the opposite direction, value to be configured is positive; if length from transmitter to
receiver is lower than the one in the opposite direction, value to be configured is negative.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
Note: S1TRANS parameter is only valid for ports belonging to PP1GE, PP1GEX20 and
PP1GESY modules. The parameter value is restricted to NONE for PP1GE and for
electrical FE ports on any module
Note: TCDLY parameter is only valid for ports belonging to PP1GE, PP1GEX20, and
PP1GESY modules
6
STOP. This procedure is complete.
END OF STEPS
6.19.2 Prerequisites
The MAU facility to place in loopback must have a Primary State (PST) of OOS-AUMA or OOS-MA.
6.19.3 General
The RTRV-LPBK-MAU command retrieves the MAU facilities that are in a loopback within the
specified range of MAU AIDs. The command is executed regardless of the provisioning of the
specified facilities.
The successful response for a RTRV-LPBK-MAU contains one line of parsable data, in ascending
order, for each MAU facility that is in a loopback within the specified range of AIDs. No output data
is returned for an AID that is not in a loopback.
The OPR-LPBK-MAU command establishes a near-end or far-end facility or terminal loopback on
the specified MAU facility.
The RLS-LPBK-MAU command releases the loopback previously established by an OPR-LPBK-
MAU command on the specified MAU facility.
To execute a near-end or far-end RLS-LPBK-MAU, the specified MAU must have a PST of IS.
For parameter descriptions of TL1 commands used in this procedure, refer to the “Command
details” (p. 107).
6.19.4 Steps
NOTICE
2
Review the MAU loopback diagrams.
3
Select action.
To retrieve current loopback status of MAU facility, go to Step 4.
To establish loopback, go to Step 7.
To verify loopback status, go to Step 13.
To release loopback, go to Step 16.
To end this procedure, go to Step 19.
4
Retrieve Loopback Information
Select RTRV-LPBK-MAU::[AID];
where:
AID=MAU access identifier
Possible values:
• ALL (ALL AID)
• MAU-{1-7}-{1-9}-{2-9,12-19, 21-36}-{1-10} - MAU port on a 10xAny module.
5
Examine output. One line of information displays for each facility in loopback within specified
range of AIDs. No information displays for facilities that are not in loopback.
6
Go to Step 3.
7
Establish Loopback
Enter RTRV-MAU::AID; to retrieve the current PST and SST of the MAU facility.
where:
AID=MAU access identifier
8
Observe output.
9
Select action.
If the PST for the MAU facility is IS or OOS-AU, go to Step 10.
If the PST for the MAU facility is OOS-AUMA or OOS-MA, go to Step 11.
10
Before establishing a loopback, the facility must be placed out of service.
Enter ED-MAU::AID:::::OOS;
where:
AID=MAU access identifier
11
Enter OPR-LPBK-MAU::AID:::[LOCN],,,[LPBKTYPE];
where:
AID=MAU Access Identifier. Possible value: MAU-{1-7}-{1-9}-{2-9,12-19, 21-36}-{1-10}.
LOCN= Location, identifies the location in which the loopback is performed. Value is: {NEND} -
Near End.
LPBKTYPE= Loopback Type, specifies the type of loopback.
12
Go to Step 3.
13
Verify Loopback Status
Enter RTRV-LPBK-MAU::[AID]; to verify the MAU facility is in loopback status.
where:
AID=MAU Access Identifier
14
Examine output. One line of information displays for each facility in loopback within specified
range of AIDs. No information displays for facilities that are not in loopback.
15
Go to Step 3.
16
Release Loopback
Enter RLS-LPBK-MAU::AID:::[LOCN],,,[LPBKTYPE]; to release the MAU loopback.
where:
AID=MAU Access Identifier
LOCN={NEND}
LPBKTYPE={FACILITY, TERMINAL}
Note: To execute a RLS-LPBK-MAU, the specified MAU must have a PST,SST of OOS-
AUMA,LPBK or OOS-MA,LPBK.
17
Enter ED-MAU::AID:::::IS; to place the facility back in service.
where:
AID=MAU Access Identifier
18
Go to Step 3.
19
STOP. This procedure is complete.
END OF STEPS
6.20.2 Prerequisites
None
6.20.3 General
A maximum of 32 DCC channels (line and/or section DCC) can be provisioned.
The interfaces supporting DCC channels can not be derived by more than 16 boards.
The interfaces supporting DCC channels can not be more than 4 for the same board.
The ENT-NETIF command creates a network interface on a specified DCC channel on an optical
port for data communication purposes. The network interface can be provisioned on the line/MS or
section/RS DCC of the specific STMn facility. The DCC is identified by means of the STM-n AID and
the DCCCHNL parameter.
The ED-NETIF command allows the operator to modify the various network interface parameters
on a specified DCC channel on an optical port for data communication purposes. The network
interface must be first provisioned on the line or section DCC of the specific STMn facility via the
ENT-NETIF command. The DCC is identified by means of the STM-n AID and the DCCCHNL
parameter.
The RTRV-NETIF command retrieves the network interface which uses a specified DCC channel on
an optical port. The network interface can be provisioned on the line or section DCC of the specific
STMn facility. The DCC is identified by means of the STM-n AID and the DCCCHNL parameter.
The DLT-NETIF command deletes the previously defined network interface on a specified DCC
channel on an optical port (via ENT-NETIF) and disables DCC communication on that link. The
network interface can be provisioned on the line or section DCC of the specific STMn facility. The
DCC is identified by means of the STM-n AID and the DCCCHNL parameter.
6.20.4 Procedure
1
Select action.
To retrieve network interface, go to Step 2.
To provision network interface, go to Step 3.
To delete network interface, go to Step 4.
To modify network interface, go to Step 5.
2
Retrieve Network Interface
Enter RTRV-NETIF::AID;
where AID=Access IDentifier, specifies the OCn/STMn or OTS facility.
3
Provision Network Interface
Enter ENT-NETIF::AID::::[DCCCHNL=][,IP=][,INTISIS=][,L2SIDE=][,L3QOS=],
LLMODE= [,OSI=][,OSIAREA=][,CHNLUSEDBY= ];
where AID=Access IDentifier, specifies the OCn/STMn or OTS facility.
Example: In the following example, ENT-NETIF is used to create a TCP/IP over LAPD protocol
stack with the NE being the user side on the Layer 2 connection, and establish that the OSPF
will be used as routing algorithm on the specified Multiplex Section DCC of the STM16 facility:
ENT-NETIF::STM16-1-1-3-1:C000:::DCCCHNL=LINE,IP=Y,L2SIDE=USER,LLMODE =LAPD;
4
Delete Network Interface
Enter DLT-NETIF::AID::::[DCCCHNL=];
where AID=Access IDentifier, specifies the OCn/STMn or OTS facility.
5
Modify Network Interface
Enter ED-NETIF::AID::::[DCCCHNL=][,IP=][,INTISIS=][,L2SIDE=][,OSI=][,
OSIAREA=];
where AID=Access IDentifier, specifies the OCn/STMn or OTS facility.
Example: In the following example, ED-NETIF is used to enable the Integrated IS-IS protocol
on the specified Multiplex Section DCC of the STM16 facility:
ED-NETIF::STM16-1-1-3-1:C000:::DCCCHNL=LINE,INTISIS=Y;
END OF STEPS
6.21.2 Prerequisites
None.
6.21.3 General
This procedure allows the operator to enter (add) and retrieve all the IP routes contained in the IP
routing table.
Retrieved IP routes can be static routes edited via the ENT-NE-IPRT command or dynamic routes
generated by OSPF or Integrated IS-IS software.
If the AID specifies a STM-n then the DCCCHNL parameter must be specified, and the NEXTHOP
parameter should not be specified.
If the AID specifies the LAN, then the NEXTHOP parameter must be specified, and the DCCCHNL
parameters should not be specified.
If the AID specifies the OTS facility, then the DCCCHNL parameters has not be specified.
This procedure allows the operator to delete a static IP route from the IP routing table. The IP
route's parameters specified define univocally the entry in the IP routing table that has to be
deleted. If a match with all the specified parameters cannot be found, an error message will be
returned in response.
Retrieved IP routes can be static routes edited via the 6.21 “Administer NE IP Route” (p. 200)
procedure or dynamic routes generated by OSPF or Integrated IS-IS software.
6.21.4 Procedure
Select action:
• Retrieve IP routes in the IP routing table, go to Step 2
• Provision a new static IP route in the IP routing table, go to Step 5
• Deprovision a new static IP route in the IP routing table, go to Step 6
2
Retrieve IP routes
Enter RTRV-NE-IPRT:::;
3
Examine output for provisioning information on NE, as detailed in the relevant command guide,
refer to “Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
/*
<Command
Echo>
[<CTAG>]
(<Session_Number>)*/ cr lf]
;
4
Ensure that port is in valid state (OOS-MA,UAS).
5
Provision a new static IP route in the IP routing table
Enter ENT-NE-IPRT::AID:::DESTADDR, MASK, [NEXTHOP], [DCCCHNL], [METRIC],
[ADVERTISE];
where:
• AID = Access IDentifier, specifies the STMn/OCn or OTS facility carrying the DCC with the
next hop network interface or identifies the IP Tunnel or Customer LAN. Possible values as
previously described.
• DESTADDR = Destination Address, it is the IP address of the destination host or network (in
the format nnn-nnn-nnn-nnn). The address 0-0-0-0 is used to specify a default route. If
NETMASK is not all '1' (i.e., a network route is specified), the host portion of the DESTADDR
must be all '0'. Possible values as previously described.
• MASK = IP Mask, it is the IP subnet mask of the route (in the format nnn-nnn-nnn-nnn). The
mask 0-0-0-0 is used to specify a default route. Possible values as previously described.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
6
Deprovision a new static IP route in the IP routing table
Enter DLT-NE-IPRT::AID:::DESTADDR,MASK[,DCCCHNL];
where:
• AID = Access IDentifier, specifies the STMn facility carrying the DCC with the next hop
network interface or the IP Tunnel or Management LAN or In-Fiber In-Band interface.
• DESTADDR = Destination Address, it is the IP address of the destination host or network (in
the format nnn-nnn-nnn-nnn). Possible values: {1-99, 101-126,128-223} - {0-255} - {0-255} -
{0-254}.
• MASK = IP Mask, it is the IP subnet mask of the route (in the format nnn-nnn-nnn-nnn).
Possible values: {0-255} - {0-255} - {0-255} - {0-255}.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
7
STOP. This procedure is complete.
END OF STEPS
6.22.2 Prerequisites
None.
6.22.3 General
This procedure allows the operator to create an IP tunnel instance on the NE. The IP tunnel that
has to be created is specified by its AID. If the AID specified matches any of the ID for existing IP
tunnels, an error message will be returned in response.
The supported encapsulation of the IP tunnel are the Nokia proprietary type and Standard
(RFC3147) type recommended by G.7712: CISCO proprietary encapsulation protocol type is not
supported.
The remote OSI System at the other end the tunnel can be addressed either by NSAP address or
by TID; those input parameters are mutually exclusive, but one of those must be specified.
The delete procedure allows the operator to delete an IP tunnel associated with the NE. The IP
tunnel that has to be deleted is specified by its ID parameter. If the ID specified does not match with
any of the ID for existing IP tunnels, an error message will be returned in response.
6.22.4 Procedure
Select action:
• Retrieve an IP tunnel instance on the NE, go to Step 2
• Create an IP tunnel instance on the NE, go to Step 4
• Delete an IP tunnel instance on the NE, go to Step 5
2
Retrieve an IP tunnel instance on the NE
Enter RTRV-NE-IPT::AID:;
where: AID = IP Tunnel Identifier, it is the identifier of the specific IP tunnel to retrieve. Possible
values: ALL for all AID or IPT-{1-128} for Internet Protocol Tunnel.
3
Examine output for provisioning information on NE, as detailed in the relevant command guide,
refer to “Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
/*
<Command
Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
4
Create an IP tunnel instance on the NE
Enter ENT-NE-IPT::AID::::[REMOTENSAP=][,REMOTETID=][,ENCAPTYP=];
where:
• AID = IP Tunnel Identifier, it is the identifier of the specific IP tunnel to retrieve. Possible
values: IPT-{1-128} for Internet Protocol Tunnel.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
5
Delete an IP tunnel instance on the NE
Enter RTRV-NE-IPT::AID:;
where: AID = IP Tunnel Identifier, it is the identifier of the specific IP tunnel to retrieve. Possible
values: ALL (ALL AID) or IPT-{1-128} (Internet Protocol Tunnel).
6
Examine output for provisioning information on NE, as detailed in the relevant command guide,
refer to “Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
/*
<Command
Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
7
Enter DLT-NE-IPT::AID:;
where: AID = IP Tunnel Identifier, it is the identifier of the specific IP tunnel to delete. Possible
values: IPT-{1-128} (Internet Protocol Tunnel).
8
STOP. This procedure is complete.
END OF STEPS
6.23.2 Prerequisites
None
6.23.3 General
NTP servers are used for time of day synchronization when the NTP protocol is enabled. If no NTP
server has been entered and the NTP protocol is enabled, the time-of-day clock will synchronize
with the last known internal clock frequency.
When NTP is enabled, the NE internal time-of-day clock uses the calculated Coordinated Universal
Time (UTC) from the selected NTP server, modified by the user-provisioned offset. All messages,
event reports, logs, and events that carry time stamps use the following time of day: NTP UTC time
+ provisioned offset.
6.23.4 Procedure
1
Enter RTRV-NTP;
2
Examine output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
3
Select action.
To retrieve NTP server IP addresses, go to Step 4.
To provision NTP server IP address, go to Step 7.
To delete NTP server IP address, go to Step 9.
To enable NTP, go to Step 11.
To modify NTP parameters, go to Step 16.
To disable NTP, go to Step 18.
To end this procedure, go to Step 19.
4
Retrieve NTP Server IP Addresses
Enter RTRV-NTP-ADDR;
5
Examine output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"::NETADDR=<value>:<PST>[,SST] " cr lf
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
6
Go to Step 3.
7
Provision NTP Server IP Addresses
Enter ENT-NTP-ADDR::::::NETADDR==x;
where: x = IP address of an NTP server. Possible values: {{0-99,101-126,128-223}-{0-255}-{0-
255}-{0-255}}.
8
Go to Step 3.
9
Delete NTP Server IP Addresses
Enter DLT-NTP-ADDR::::::IP=x;
where: x = IP address of an NTP server to be deleted. Possible values: {{0-99,101-126,128-
223}-{0-255}-{0-255}-{0-255}}.
10
Go to Step 3.
11
Enable NTP
Enter RTRV-NTP-ADDR;
12
Observe output, as described in Step 5.
13
Is an NTP server provisioned?
If yes, go to Step 14.
If no, go to step 7 to provision an NTP server.
14
Enter ED-NTP::::::NTP=[,OFFSET=];
where: NTP = Enable or disable time synchronization from the NTP server. Possible values:
ENABLE or DISABLE. Factory Default is DISABLE
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
15
Go to Step 19.
16
Modify NTP Parameters
Enter ED-NTP::::::[NTP=],OFFSET=;
where OFFSET = Time offset to apply to NTP server UTC time, +/- HH-MM, for all events and
time stamps reported by this NE. Possible values: { +,- }{ 00-23 }-{ 00-59}. Factory default is
+00-00.
17
Go to Step 19.
18
Disable NTP
Enter ED-NTP::::::NTP=DISABLE;
19
STOP. This procedure is complete.
END OF STEPS
6.24.2 General
The NE is able to automatically discover SDH links of its connected neighbors.
Broadcasting of a discovery trace message is enabled for each NE using the SET-PRMTR-NE
command and the TRC_NGHBRDISC parameter. When enabled, the discovery trace message is
sent as the default trace message. Note that provisioning a non-default trace message on an STMn
overrides the sending of the discovery message (See ED-STMn).
The RTRV-NEIGHBORS command retrieves a list of the immediate STMn neighbor(s) of the
specified AID(s), that have been previously captured by reading a discovery trace message
transmitted by the neighbor NE on the received J0 section trace.
The data returned include the neighbor NE host IP address, the AID of the optical port on the
Neighbor NE, and the NE TID, if available.
RTRV-SECTRC retrieves the contents of the Regenerator SectionTrace. This command may be
used to retrieve the “incoming” accepted Regenerator Section Trace, the expected Regenerator
Section Trace as used for the dTIM (Trace Identifier Mismatch) supervision and the “outgoing”
transmitted Regenerator Section Trace that is inserted into the Regenerator Section overhead on
the outgoing signal. The expected and transmitted Regenerator Section Trace is provisioned via the
ED facilities command. If no TRACEMSG has been returned and the command did not fail, the
system will output the /“ /” string.
For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 Transport
Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.
6.24.4 Procedure
1
Enter:
SET-PRMTR-NE::::::[REGION=][,PROVMODE=][,USERLABEL=][,AIN STHDFLT=][,
TRC-NGHBRDISC=];
where:
TRC-NGHBRDISC = Specifies the transmitted section trace default message for STMn.
Possible values:
DISABLE Standard TRC default message is transmitted
(X000000000000000000000000000000)
ENABLE TRC default message is composed as a neighbor discovery message. The NE's host
IP address and the AID of the transmitting facility are encoded on the 16 byte TRC message
according to ITU-G-7714.1.
Note: The setting of this parameter does not affect already provisioned trace messages or
facilities that are being managed by control plane.
2
Enter:
RTRV-NEIGHBORS:AID:::::[FORCEREAD=];
AID = Local AID(s) for which neighbor information is requested.
Possible values:
AID = ALL, STMn.
3
Enter:
RTRV-SECTRC::AID:::[TRCFMT];
AID = Access identifier of the optical facility.
AID = STMn.
END OF STEPS
6.25.2 Prerequisites
Verify the board is in appropriate slot (02 to 09 - 12 to 19 - 21 to 28 - 29 to 36).
6.25.3 General
The ED-ODU2 command is used to edit parameters related to the ODU2 tributary for specified
client/line facility.
The ENT-ODU2 command is not supported. The ODU2 object entity shall be automatically created
on the client side by the system when the Client OTU2 facility os created. The ODU2 object entity
shall be automatically created on the line side by the system when the OT circuit pack is
provisioned.
The ODU2 object entity shall be automatically created on the line side by the system when the
OT2TDM module is provisioned..
6.25.4 Procedure
Select action:
• Retrieve ODU2 tributary for specified client/line facility, go to Step 2
• Provision ODU2 tributary for specified client/line facility, go to Step 4
• Remove and restore ODU2 tributary for specified client/line facility, go to Step 6
• Modify ODU2 tributary for specified client/line facility, go to Step 10
2
Retrieve ODU2 tributary for specified client/line facility
Enter RTRV-ODU2::AID;
where: AID = specifies an access Identifier to the OT client or line port. Possible values:
• ALL for all AID
• OTODU2-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-{C1, L1}-1 for ODU2 facility in an OTU2 on a
DWLA10X module
• OTODU2-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-{L1}-1 for ODU2 facility in an OTU2 on
OT2TDM module.
3
Examine output for provisioning information on port, as detailed in the relevant command guide,
refer to “Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<AID>::[AINSTH=<value>][,AINSTIMER=<value>] [,ALMPROF=<value>][,
TCAPROF=<value>][,MGRACD=<value>]:<PST> [,<SST>]"
cr lf
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
4
Provision ODU2 tributary for specified client/line facility
Ensure that port is in valid state for provisioning (OOS-MA,UAS).
5
The ENT-ODU2 command is not supported. The ODU2 object entity is automatically created on
the client side by the system when the Client OTU2 facility is created (see 6.67 “Provision
Equipment” (p. 385)). The ODU2 object entity shall be automatically created on the line side by
the system when the OT circuit pack is provisioned (see 6.67 “Provision Equipment” (p. 385))..
6
Remove and restore ODU2 tributary for specified client/line facility
Enter RTRV-ODU2::AID;
where: AID = Access Identifier, specifies an access Identifier to the OT client or line port.
Possible values:
• ALL
7
Examine output for provisioning information on port, as detailed in the relevant command guide,
refer to “Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
8
Enter RMV-ODU2::AID:;
where:
• AID = Access Identifier, specifies an access Identifier to the OT client port (client AID).
Possible values: OTODU2-{1-7}-{1-9}-{2-9, 12-19, 21-28,29-36}-{C1, L1}-1 for ODU2 facility
in an OTU2 on a DWLA10X module.
9
Enter RST-ODU2::AID:;
where:
• AID = Access Identifier, specifies an access Identifier to the OT client port. Possible values:
OTODU2-{1-7}-{1-9}-{2-9, 12-19, 21-28,29-36}-{C1, L1}-1 for ODU2 facility in an OTU2 on a
DWLA10X module.
10
Modify ODU2 tributary for specified client/line facility
Enter RTRV-ODU2::AID;
where: AID = Access Identifier, specifies an access Identifier to the OT (client or line) port.
Possible values:
• ALL
• OTODU2-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-{C1, L1}-1 for ODU2 facility in an OTU2 on a
DWLA10X module
• OTODU2-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-{L1}-1 for ODU2 facility in an OTU2 on
OT2TDM module
11
Examine output for provisioning information on port as detailed in the relevant command guide,
refer to “Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
Possibility of service interruption. Editing port parameters of a traffic bearing port can
adversely affect service.
12
Enter ED-ODU2::AID::::[,ALMPROF=][,TCAPROF=]:[PST],[SST];
where: AID = Access Identifier, specifies an access Identifier to the OT (client or line) port.
Possible values:
• ALL
• OTODU2-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-{C1, L1}-1 for ODU2 facility in an OTU2 on a
DWLA10X module
• OTODU2-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-{L1}-1 for ODU2 facility in an OTU2 on
OT2TDM module
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
13
STOP. This procedure is complete.
END OF STEPS
6.26.2 Prerequisites
Verify the board is in appropriate slot (02 to 09 - 12 to 19 - 21 to 28 - 29 to 36).
The ED-OTU2 command is supported for the line ports on the OT2TDM module.
6.26.3 General
The ENT-OTU2 on the line side is not supported. The OTU2 object entity shall be automatically
created on the line side by the system when the OT2TDM or DWLA10X is inserted and provisioned.
If the facility provisioning mode of this NE is automatic, i.e., PROVMODE=AUTOEQ-AUTOFC, then
this command cannot be used to enter facilities. In this mode, facilities are automatically entered
when the supporting equipment is entered (See ED-PRMTR-NE, ENT-EQPT)
Automatically entered facilities are created with default provisioning, with AINS active.
Provisioning changes may be made to an automatically entered OTU2 using the ED-OTU2
command.
Executing an ED-OTU2 command causes the following primary state transitions for the specified
OTM0.2 facility. Secondary states associated with the OTM0.2 facility after the command is
executed depend upon events detected by the system.
Refer to the 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1
Command Guide for details on parameter values.
6.26.4 Procedure
Select action:
• Retrieve OTU2 facility information, go to Step 2
• Provision OTU2 facility, go to Step 4
• Deprovision OTU2 facility, go to Step 6
• Modify OTU2 facility, go to Step 11
2
Retrieve OTU2 facility information
Enter RTRV-OTU2::AID;
where: AID = Access Identifier, specifies an access Identifier to the OT client or line port.
Possible values:
• ALL for all AID
• OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-L1 for OTU2 Line port, OT2TDM or
DWLA10X module
• OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-C1 for Client port on a DWLA10X module -
OTU2, STM-64, 10GE.
3
Examine output for provisioning information on port, as detailed in the relevant command guide,
refer to “Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<AID>::[AINSTH=<value>][,AINSTIMER=<value>] [,FECTYPE=<value>][,
ALMPROF=<value>][,TCAPROF=<value>] [,OTU2CHNL=<value>][,MGRACD=
<value>]:<PST> [,<SST>]" cr lf
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
4
Provision OTU2 facility
5
Enter ENT-OTU2::AID::::[AINSTH=][,FECTYPE=][,ALMPROF=] [,TCAPROF=]:
[PST],[SST];
where:
• AID = Access Identifier, specifies an access Identifier to the OT client or line port. Possible
values:
− OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-C1 for Client port on a DWLA10X module
- OTU2, STM-64, 10GE.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
6
Deprovision OTU2 facility
Enter RTRV-OTU2::AID;
where: AID = Access Identifier, specifies an access Identifier to the OT client or line port.
Possible values:
• ALL
• OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-L1 for OTU2 Line port, OT2TDM or
DWLA10X module
• OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-C1 for Client port on a DWLA10X module -
OTU2, OC192, STM-64, 10GE, 10GFC)
7
Examine output for provisioning information on port, as detailed in the relevant command guide,
refer to “Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
8
Enter DLT-OTU2::AID;
where:
• AID = Access Identifier, specifies an access Identifier to the OT client port (client AID).
Possible values: OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-C1 for Client port on a
DWLA10X module - OTU2, OC192, STM-64, 10GE, 10GFC.
9
Enter RMV-OTU2::AID;
where:
• AID=Access Identifier, specifies an access Identifier to the OT client port (client AID).
Possible values:
− OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-L1 for OTU2 Line port, OT2TDM or
DWLA10X module
− OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-C1 for Client port on a DWLA10X module
- OTU2, OC192, STM-64, 10GE, 10GFC
10
Enter RST-OTU2::AID;
where:
• AID=Access Identifier, specifies an access Identifier to the OT client port (client AID).
Possible values:
− OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-L1 for OTU2 Line port, OT2TDM or
DWLA10X module
− OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-C1 for Client port on a DWLA10X module
- OTU2, OC192, STM-64, 10GE, 10GFC
11
Modify OTU2 facility
Enter RTRV-OTU2::AID;
where: AID = Access Identifier, specifies an access Identifier to the OT (client or line) port.
Possible values:
• ALL
• OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-L1 for OTU2 Line port, or OT2TDM or
DWLA10X module
• OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-C1 for Client port or on a DWLA10X module -
OTU2, STM-64, 10GE )
12
Examine output for provisioning information on port as detailed in the relevant command guide,
refer to “Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
Possibility of service interruption. Editing port parameters of a traffic bearing port can
adversely affect service.
13
Enter ED-OTU2::AID::::[AINSTH=][,FECTYPE=][,ALMPROF=] [,TCAPROF=][,
OTU2CHNL=]:[PST],[SST];
where: AID = Access Identifier, specifies an access Identifier to the OT (client or line) port.
Possible values:
• ALL
• OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-L1 for OTU2 Line port, or OT2TDM or
DWLA10X module
• OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-C1 for Client port or on a DWLA10X module -
OTU2, STM-64, 10GE )
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
14
STOP. This procedure is complete.
END OF STEPS
6.27.2 Prerequisites
To establish an VCn cross-connection, the required facilities must be provisioned. Refer to
6.39 “Administer VC Cross-Connection” (p. 267) to provision VCn facilities.
6.27.3 General
The system supports a 1-way or 2-way protected or unprotected cross-connection between two
VCn facilities. This procedure is used to administer cross-connections between two VCn facilities.
The ENT-CRS-VCn command is used to create an unprotected connection between the specified
VCn facilities.
The ENT-CRSPROT-VCn command is used to create a protected connection between the specified
VCn facilities.
6.27.4 Procedure
1
Select action.
To retrieve VCn path protected cross-connection information, go to Step 2.
To create VCn path protected cross-connection, go to Step 5.
To modify VCn path protected cross-connection, go to Step 6.
To delete VCn path protected cross-connection, go to Step 7.
To end this procedure, go to Step 9.
2
Retrieve VCn/STSn Path Protected Cross-Connection Information
Enter RTRV-CRSPROT-<rate>::AID;
where:
rate
Values are:
• for ETSI: VC4, VC44C, VC416C, VC464C, LOVC12, LOVC3
AID = Access Identifier.
It specifies the selected facility(ies) to which the command is directed. AID of ALL retrieves all
the cross connects in the system.
3
Observe output.
4
Go to Step 1.
5
Create VCn Path Protected Cross-Connection
Enter ENT-CRSPROT-<rate>::FROMPED,FROMPING,TO:::[CCT]:[CKTID=][
,RVRTV=][,RVRTTIM=][,HLDFFTIM=][,PTYPE=];
where:
rate
Values are:
• for ETSI: VC4, VC44C, VC416C, VC464C, LOVC12, LOVC3
FROMPED = AID of connection point;
MVC4TU12-{1-7}-{1-9}-{7}-{1-16}-{1-3}- {1-7}-{1-3} - for TU12 within a MVC4 on SCC card on
1646 Drop shelf
MVC4TU3-{1-7}-{1-9}-{7}-{1-16}-{1-3} - for TU3 within a MVC4 on SCC card on 1646 Drop shelf
Indicates the FROMPED (protected receive side from the network, protected source of cross-
connection) facility of the cross-connection.
FROMPING = AID of connection point.
Indicates the FROMPING (protecting receive side from the network, protecting source of cross-
connection) facility of the cross-connection.
TO = AID of connection point.
MVC4TU12-{1-7}-{1-9}-{7}-{1-16}-{1-3}- {1-7}-{1-3} - for TU12 within a MVC4 on SCC card on
1646 Drop shelf
MVC4TU3-{1-7}-{1-9}-{7}-{1-16}-{1-3} - for TU3 within a MVC4 on SCC card on 1646 Drop shelf
Indicates the TO (transmit side to the network, sink of cross-connection) facility of the cross-
connection.
Other parameters are optional. If a value is not entered for these parameters, the system will
use the default value. Refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-
160) Release 5.1 TL1 Command Guide for details on parameter values.
6
Modify Protected Cross-Connections
ED-CRSPROT-<rate>::FROMPED,FROMPING,TO:::[CCT]:[CKTID=][,RVRTV=][,
RVRTTIM=][,HLDFFTIM=][,PTYPE=];
where:
rate
Values are:
• for ETSI: VC4, VC44C, VC416C, VC464C, LOVC12, LOVC3
FROMPED = AID of connection point.
Indicates the FROMPED (protected receive side from the network, protected source of cross-
connection) facility of the cross-connection.
FROMPING = AID of connection point.
Indicates the FROMPING (protecting receive side from the network, protecting source of cross-
connection) facility of the cross-connection.
TO = AID of connection point.
Indicates the TO (transmit side to the network, sink of cross-connection) facility of the cross-
connection.
7
Delete Protected Cross-Connections
DLT-CRSPROT-<rate>::FROMPED,FROMPING,TO:::[CCT];
where:
rate
Values are:
• for ETSI: VC4, VC44C, VC416C, VC464C, LOVC12, LOVC3
FROMPED = AID of connection point.
Indicates the FROMPED (protected receive side from the network, protected source of cross-
connection) facility of the cross-connection.
FROMPING = AID of connection point.
Indicates the FROMPING (protecting receive side from the network, protecting source of cross-
connection) facility of the cross-connection.
TO = AID of connection point;
Indicates the TO (transmit side to the network, sink of cross-connection) facility of the cross-
connection.
8
Go to Step 1.
9
STOP. This procedure is complete.
END OF STEPS
6.28.2 Prerequisites
None
6.28.3 General
A PHB is the externally observable forwarding behavior applied at a DS-compliant (Diff-Serv) node
belonging to a DS domain.
A set of “data treatments” (defined as PSCs) are requested to be applied to packets on each NE
inside DiffServ domain, where this treatment includes both:
Then a PSC (PHB Scheduling Class) is the grouping of one or more PHBs.
The User can profile the NE forwarding behavior for TUSegment and PWSegment, combining PHB.
The User can uses the following PSCs:
Table below reports MPLS Diff-Serv Forwarding Plane as supported in the System with:
Corresponding Ethernet Forwarding Classes;
In the System already exists the factory default PHB Profile, its AID is PHBPROF-1.
In the System exists also a second factory PHB Profile its AID is PHBPROF-2.
6.28.4 Procedure
1
Enter RTRV-PHB-PROF;
To retrieve one or all Per Hop Behaviour Profile stored in the System.
2
Examine output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
3
Select action.
To provision Per Hop Behaviour Profile, go to Step 4.
To delete Per Hop Behaviour Profile, go to Step 5.
To modify Per Hop Behaviour Profile, go to Step 6.
4
Provision Per Hop Behaviour Profile
Enter ENT-PHB-PROF:::::EXP0,EXP1,EXP2,EXP3,EXP4,EXP5,EXP6,EXP7;
where:
EXPn is the parameter that associates a PHB class to the MPLS packets with EXP=n.
n=[0,7]
5
Delete Per Hop Behaviour Profile
Enter DLT-PHB-PROF::AID;
where:
AID=PHBPROF-{3-16} is the User defined PHB Profile.
AID is the Access Identifier, specifies an access Identifier to the PHB profile. The PHBPROF-1
and PHBPROF-2 can't be deleted because are permanently stored in the system.
Note: Restriction: The PHBPROF-1 and PHBPROF-2 can't be deleted because are
factory profiles stored in the system.
6
Modify Per Hop Behaviour Profile
END OF STEPS
6.29.2 General
RADIUS is a networking protocol, based on RADIUS servers, that provides centralized
Authentication, Authorization and Accounting (AAA) services.
The user sends a connection request to a Network Access Server (NAS), which acts as RADIUS
client and sends a RADIUS access request to the RADIUS server.
The RADIUS server is provisioned with one or more user profiles.
Based on the user profile and user class definitions, the RADIUS server accepts or rejects the NAS
request. In turn the NAS accepts or, respectively, rejects the user connection.
The following Figure shows the general RADIUS scenario.
6.29.4 Procedure
1
Login to NE with SEC (security administrator) user.
2
Configure RADIUS SERVER using:
ENT-RADIUS-SERVER:::::SERVERNUM,STATUS:IPADDR=,[PORT=],SECRET=;
where:
• SERVERNUM = valid server number to provision the server:
− RAD1: RAD1 is first server name.
− RAD2: RAD2 is the second server name.
• STATUS = is RADIUS server status. The valid values are the following:
− ENABLE The RADIUS server is on-line. This is the default value.
− DISABLE The RADIUS server is off-line
• IPADDR = IP address of the specified RADIUS server (RAD1 or RAD2).
• Secret = the shared secret key between the NE and the target RADIUS server. This key shall
be an ascii string between 5 to 32 characters. The secret key must be encrypted on the NE
using AES or 3DES.
Example: The following example illustrates the command and associated output for
provisioning the attributes of a RADIUS server number, IP address, secret key (zxcvbn).
ENT-RADIUS-SERVER::RAD1:132-117-112-192,,zxcvbn;
3
To modify the Radius Server attributes enter:
ED-RADIUS-SERVER:::::SERVERNUM,[STATUS]:[IPADDR=][,PORT=][,SECRET=];
4
Check server parameters have been modified correctly entering:
RTRV-RADIUS-SERVER;
5
Examine the output.
6
Is the RADIUS server status Enable?
If yes, go to Step 3.
If no, go to Step 7
7
To delete the Radius server enter:
DLT-RADIUS-SERVER:::::SERVERNUM;
where:
SERVERNUM = valid server number to provision the server.
END OF STEPS
6.30.2 Prerequisites
Retrieving the security log file and provisioning security log file parameters can only be performed
by administrators with security privileges.
6.30.3 General
The NE stores in the system's disk output buffer the following classes of information:
• any action that changes the security attributes and services
• any action that changes access controls
• any action that changes configuration parameters of the device
• each login attempt and its result
• each logout or session termination (whether remote or console, whether requested or due to
inactivity timeout)
RTRV-AUDIT-SECULOG retrieves the security log entries that were generated by the system
between the specified FRDATM (From Date and Time) to the specified TODATM (To Date and
Time) values and/or commands entered by the specified User (UID).
The SET-ATTR-SECULOG command is used to set the system's disk output buffer for the security
log. The LOGEVENT parameter specifies the list of events that are to be recorded in the security
log.
6.30.4 Procedure
1
Select action.
To provision security log parameters, go to Step 2.
To retrieve security log file, go to Step 7.
2
Provision Security Log Parameters
Enter RTRV-ATTR-SECULOG; to retrieve current security log parameter values.
3
Examine output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"::LOGEVENT=<value>,UPSLG=<value>[,WARN=<value>]" cr lf
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
4
Enter SET-ATTR-SECULOG::::::[,LOGEVENT=][,UPSLG=][,WARN=];
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
5
Enter RTRV-ATTR-SECULOG; to verify changes.
6
Go to Step 9.
7
Retrieve Security Log File
Enter RTRV-AUDIT-SECULOG:::::["FRDATM","TODATM"],[UID];
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
8
Observe output.
9
STOP. This procedure is complete.
END OF STEPS
6.31.2 Prerequisites
An STMn module must be provisioned before STMn facilities can be provisioned. Refer to
6.67 “Provision Equipment” (p. 385) to provision STMn modules.
6.31.3 General
For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 Transport
Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.
6.31.4
1
Enter RTRV-STMn::AID;
where:
STMn=Optical Facility type (STM1, STM4, STM16, STM64)
AID=STMn Access Identifier
2
Examine output for provisioning information on port.
3
Does facility have PST and SST of OOS-MA,UAS?
If yes, go to Step 4.
If no, the ED-STMn command cannot be performed on the specified STMn facility. Go to Step
5.
4
Enter ED-<STMn>:[TID]:AID:[CTAG]:::[AINSTH=][,S1TRANS=][,ALSENB=][,
PMODE=][,AINSCRIT=][,PSTCORR=][,SDSFMODE=][,BRSTINTVL=][,BRSTTH=][,
SDTH=][,SFTH=][,RSBRSTINTVL=][,RSBRSTTH=][,TRCSENTMODE=][,TRC=][,
TRCRCVMODE=][,TRCEXPECTED=][,TRCMON=][,TRCCONSACT=][,ALMPROF=][,
TCAPROF=][,CMDMDE=][,HOS TRUCT=]:[PST],[SST];
where:
STMn=STM1, STM4, STM16, STM64
AID=STMn Access Identifier
Other parameters are optional. If a value is not entered for these parameters, the system will
use the default value. Refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-
160) Release 5.1 TL1 Command Guide for details on parameter values.
Example: In the following example, STM-16 port 1 of slot 5, HOSTRUCT is set to a mix of AU4
and AU4-4c as new payload. All other parameters remain at their previously existing value.
ED-STM16::STM16-1-1-5-1::::HOSTRUCT=4xAU4-2xAU44C-4xAU4;
ED-STM16::STM16-1-1-5-1::::HOSTRUCT==4xAU4-1xAU44C-8xAU4;
Besides specifying the unchanged payload, the operator can also use the DC payload type. In
that case the following command needs to be issued:
ED-STM16::STM16-1-1-5-1::::HOSTRUCT=8xDC-1xAU44C-4xDC;
5
STOP. This procedure is complete.
END OF STEPS
6.32.2 Prerequisites
The working and protection STM-n facilities in facility protection groups must be provisioned.
6.32.3 General
An STM-n facility protection group consists of a pair of adjacent STM-n facilities: one protect facility
and one working facility.
The types of facility protection groups that can be provisioned on a port-pair basis with this
command are:
• 1+1 Linear Multiplex Section Protection (MSP)
• 2 fibre Multiplex Section Shared Protection Ring (MS-SPRing)
A linear 1+1 MSP FFP will consist of two STMn ports (working and protection port) located on two
different cards. The AID of the FFP is using the same slot and port number as the protecting/
protection port.
If linear 1+1 MSP FFP instance is created in the context of this command, then the embedded AUn
tributaries of the protection port will be deleted. If one of these AUn instances is used as PM point,
then the corresponding PM point is also deleted.
A 2 fibre MS-SPRing FFP will consist of two STMn ports (east and west port) located on two
different cards. The AID of the FFP is using the same slot and port number as the east port.
If a 2 fibre MS-SPRing FFP instance is created in the context of this command, then the embedded
AUn tributaries within the protection bandwidth of the east and west port will be deleted. If one of
these AUn instances is used as PM point, then the corresponding PM point is also deleted.
If a 2 fibre MS-SPRing FFP instance is created in the context of this command, then also the
corresponding map instances (i.e. ring map and squelch map) will be created.
No TimeSlot Interchange (TSI) cross connection is allowed for MS-SPRing ports. A TSI cross-
connection is a cross-connection between east working tributary and west working tributary where
the two tributaries are located on different AUG/AU numbers within the STM-n port.
The ED-FFP-<STMn> command modifies characteristics of a STMn fast facility protection group
(FFP) which has been previously provisioned through ENT-FFP-<STMn> command. Upon
successful completion of ED-FFP-<STMn> parameter changes will be applied to the protection
group and the system will send areport database change message.
If the NodeId for the node is changed, then also all entries in squelch and ring map referencing the
old NodeId value needs to be updated in every node within the MS-SPRing.
The DLT-FFP-<STMn> command deletes a STMn facility protection group. Upon completion of the
DLT-FFP-<STMn> command, the protection group is deleted, and the working facilities that have
been disassociated from facility protection function as unprotected facilities. In addition the
protection facility can be used again for normal unprotected traffic.
The DLT-FFP-<STMn> command can only be executed against STMn facilities that are provisioned
as a protection group (e.g., provisioned via the ENT-FFP-<STMn> command). Successful
execution of the DLT-FFP-<STMn> command results in the SST of STBYH, STBYS, and WRK
being cleared on the protecting and working STMn facilities.
The successful completion of a DLT-FFP-<STMn> command for linear 1+1 MSP FFP instance also
creates the embedded AUn tributaries according to the factory default payload structure of the
protection port.
The successful completion of a DLT-FFP-<STMn> command for MS-SPRing FFP instance also
creates the embedded AUn tributaries in the former protection bandwidth according to the factory
default payload structure of the east and west port.
The successful completion of a DLT-FFP-<STMn> command for a MS-SPRing FFP also deletes the
map instances associated with the protection group, i.e. ring map and squelch map.
6.32.4 Procedure
1
Select action.
To retrieve STM-n facility protection group, go to Step 2.
To provision STM-n facility protection group, go to Step 5.
To modify linear STM-n facility protection group attributes, go to Step 7.
To deprovision STM-n facility protection group, go to Step 9.
To end the procedure, go to Step 11.
2
Retrieve STM-n Facility Protection Group
Enter RTRV-FFP-<STMn>::AID;
where:
• <STMn> = rate of the facility protection group used as command modifier. Possible values:
− STM1 for FFP with STM-1 rate.
− STM4 for FFP with STM-4 rate.
− STM16 for FFP with STM16 rate.
− STM64 for FFP with STM-64 rate.
• AID = STM-n facility protection group. Possible values:
− FFPSTM64-{1-7}-{1-9}-{2-9,12-19,21-36 }-1 for STM64 Facility Protection Group
3
Examine output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
"AID::PTYPE=<value>[,RVRTV=<value>][,RVRTTIM=<value>][,HLDFFTTIM
=<value>][,WKG=<value>[,PROTN=<value>][,PSDIRN=<value>][,ACTIVE=
<value>][,CURRREQ=<value>][,PENDREQ=<value>][,EAST=<value>][,WEST=
<value>][,NODEID=<value>][,NODEDESCR=<value>],NODESTATUS=<value>][,
EASTACTIVE=<value>][,EASTCURRREQ=<value>][,EASTPENDREQ=<value>][,
WESTACTIVE=<value>][,WESTCURRREQ=<value>][,WESTPENDREQ=<value>]" cr
lf]*
[
/*
<Command_Echo>
<CTAG>
(<Session_Number>)
*/ cr lf]
;
4
Go to Step 1.
5
Provision STM-n Facility Protection Group
where:
• <STMn> = rate of the facility protection group used as command modifier. Possible values
previously described.
• AID = Access identifier of the FFP. Possible values previously described.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
6
Go to Step 1.
7
Modify Linear STM-n Facility Protection Group Attributes
Enter ED-FFP-<STMn>::AID::::[,RVRTV=][,RVRTTIM=][,HLDFFTTIM=]
[,NODEID=][,NODEDESCR=];
where:
• <STMn> = rate of the facility protection group used as command modifier. Possible values
previously described.
• AID = Access identifier of the FFP. Possible values previously described.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
8
Go to Step 1.
9
Deprovision STM-n Facility Protection Group
Enter DLT-FFP-<STMn>::AID:;
where:
• <STMn> = ate of the facility protection group used as command modifier. Possible values
previously described.
• AID = Access identifier of the FFP. Possible values previously described.
10
Go to Step 1.
11
STOP. This procedure is complete.
END OF STEPS
6.33.2 Prerequisites
The STMn facility to place in loopback must have a Primary State (PST) of OOS-AUMA or OOS-
MA.
6.33.3 General
Loopbacks are test features that can be set to loop a signal back at different points along the signal
path. The system supports two types of STMn loopbacks.
A Facility loopback is a loopback of a signal received from the network before the switch fabric. The
Alarm Indication Signal (AIS) is forwarded to the switch fabric. See Figure 15, “Facility Loopback”
(p. 240).
A terminal loopback is a loopback of a signal received from the switch fabric. The signal is still
forwarded to the network. See Figure 16, “Terminal Loopback” (p. 242).
For parameter descriptions of TL1 commands used in this procedure, refer to the “Command
details” (p. 107).
6.33.4 Steps
NOTICE
2
Review the loopback diagrams in Figures Figure 15, “Facility Loopback” (p. 241) and Figure
16, “Terminal Loopback” (p. 242).
3
Select action.
To retrieve current loopback status of STMn facility, go to Step 4.
To establish STMn loopback, go to Step 7.
To verify loopback status, go to Step 13.
To release loopback, go to Step 16.
To end this procedure, go to Step 19.
4
Retrieve Loopback Information
Select RTRV-LPBK-STMn::[AID];
where:
STMn=Optical facility type (STM1, STM4, STM16, or STM64).
AID=STMn Access Identifier
5
Examine output. One line of information displays for each facility in loopback within specified
range of AIDs. No information displays for facilities that are not in loopback.
6
Go to Step 3.
7
Establish Loopback
Enter RTRV-STMn::AID; to retrieve current PST and SST of facility.
where:
STMn=Optical facility type (STM1, STM4, STM16, or STM64).
AID=STMn Access Identifier
8
Observe output.
9
Select action.
If the PST for the facility is IS or OOS-AU, go to Step 10.
If the PST for the facility is OOS-AUMA or OOS-MA, go to Step 11.
10
Before establishing a loopback, the facility must be placed out of service.
Enter ED-STMn::AID:::::OOS;
where:
STMn = STM1, STM4, STM16, STM64
AID=STMn Access Identifier
11
Enter
OPR-LPBK-STMn::AID:::[LOCN],,,[LPBKTYPE]:[LPBKCONSACT=];
where:
• STMn = The rate of the loopback used as command modifier.
STM1 for a STM-1 loopback
STM4 for a STM-4 loopback
STM16 for a STM-16 loopback
STM64 for a STM-64 loopback
• AID=STMn Access Identifier
Specifies the STM-n port facility. The rate of the port identified by AID must match the
command rate modifier.
• LOCN=NEND
• LPBKTYPE={TERMINAL, FACILITY}
12
Go to Step 3.
13
Verify Loopback Status
Enter RTRV-LPBK-STMn::[AID]; to verify the STMn facility is in loopback status.
where:
STMn=Optical facility type (STM1, STM4, STM16, or STM64).
AID=STMn Access Identifier
14
Examine output. One line of information displays for each facility in loopback within specified
range of AIDs. No information displays for facilities that are not in loopback.
15
Go to Step 3.
16
Release Loopback
Enter RLS-LPBK-STMn::AID:::[LOCN],,,[LPBKTYPE];
where:
STMn=Optical facility type (STM1, STM4, STM16, or STM64).
AID=STMn Access Identifier
LOCN=NEND
LPBKTYPE={TERMINAL, FACILITY}
17
Enter ED-STMn::AID:::::IS; to place the facility back in service.
where:
STMn=Optical facility type (STM1, STM4, STM16, or STM64).
AID=STMn Access Identifier
18
Go to Step 3.
19
STOP. This procedure is complete.
END OF STEPS
6.34.2 Prerequisites
Two STM-16 or STM-64 facilities must be provisioned using the ENT-STMn command, before
protection groups can be established.
To modify MS-SPRING squelch maps and ring maps manually, the automap feature must be
disabled.
6.34.3 General
ENT-FFP-STMn will execute if a pair of STMn facilities in adjacent slots of the 1850 TSS-320, TSS-
320H and TSS-160 node have been previously provisioned, and are not currently operating as a
1+1 MSP protection group.
The 1850 TSS-320, TSS-320H and TSS-160 node supports as many as 20 MS-SPRING STM16
MS-SPRING rings.
• STMn MS-SPRING rings may co-exist with other SNCP protection groups, other 1+1 protection
groups, or other unprotected STMn facilities in the same 1850 TSS-320, TSS-320H and TSS-
160 node.
• Each STMn MS-SPRING node is provided with the following features:
− AUn cross-connects can be configured to go over the MS-SPRING ring using the ENT-CRS-
AU4n command.
− AUn paths can be cross-connected between two STMns as a pass-through connection,
2WAY connection, or DRI connection, or to interconnect two MS-SPRING rings using one
node.
− MS-SPRING Switch initiation criteria includes external initiated switching commands, and
automatic initiated switching request.
− Automatic switching is initiated by the 1850 TSS-320, TSS-320H and TSS-160 node
detecting either MSP channel signaled commands including LP-S, FS-R, MS-R, and
automatic initiated requests including SF-R, SD-R, RR-R, and WTR.
− External switch commands (OPR-PROTNSW-STMn) can be entered to manually initiate
protection switching of MS-SPRING. Refer to 6.32 “Administer STM-n Facility Protection
Group” (p. 237) for procedures to switch STMn line from working to protection and vice versa.
− Line switching occurs within 50 msec after a defect is detected.
− MS-SPRING Dual Ring Interconnection using Working capacity. Provisioning and
deprovisioning of this feature is discussed in the procedure below.
The ENT-FFP-STM16/64 command enables the MS-SPRING operation.
Ring map must be entered via ED-RINGMAP command, and squelch information must be entered
via the ED-SQLMAP command for the MS-SPRING to function properly.
A ring map contains the MS-SPRING topology. It shows the order in which MS-SPRING nodes
appear in the ring. The ED-RINGMAP command is used to edit the MS-SPRING ringmap.
The MS-SPRING node maintains a squelch map containing the entry and exit node IDs for every
provisioned working AU4 path on the ring. The ED-SQLMAP command modifies an entry in the MS-
SPRING squelch map.
The NODEID parameter of the ENT-FFP-STM16/64 command is used to assign an identifier to
each node on a ring. The NODEID is a number from zero to 15; therefore a maximum of 16 nodes
on a 2-fiber MS-SPRING are allowed. The node ID an be edited when both MS-SPRING facilities
are locked out or in the forced switch state. The local node ID can be changed when the auto map
feature is enabled or disabled.
EAST (and/or WEST) parameter of the ENT-FFP-STM16/64 command is used to identify the
access identifier of the east (and/or west) side port of a MS-SPRing FFP.
For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 Transport
Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.
6.34.4
1
Select action.
To provision STMn MS-SPRING Node, go to Step 2.
2
CONFIGURE STM-16 or STM-64 FACILITY IN WORKING SLOT OF STMn PAIR (WEST
FACILITY)
Enter ED-STMn::AID::::[AINSTH=][,S1TRANS=][,ALSENB=][,PMODE=][,
AINSCRIT=][,PSTCORR=][,SDSFMODE=][,BRSTINTVL=][,BRSTTH=][,SDTH=][,
SFTH=][,RSBRSTINTVL=][,RSBRSTTH=][,TRCSENTMODE=][,TRC=][,TRCRCVMODE=]
[,TRCEXPECTED=][,TRCMON=][,TRCCONSACT=][,ALMPROF=][,TCAPROF=][,
CMDMDE=][,HOSTRUCT=]:[PST],[SST]; to provision STM-16 or STM-64 facility in slot of
STMn pair (west facility).
where:
STMn=Optical facility type (STM-16 or STM-64).
AID=STM-16 or STM-64 access identifier
Other parameters are optional. If a value is not entered for these parameters, the system will
use the default value. Refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-
160) Release 5.1 TL1 Command Guide for details on parameter values.
3
Repeat Step 2 to configure protection STMn facility (East facility).
4
Will ring maps and squelch maps be manually entered or automatically learned?
If manually entered, go to Step 11.
If automatically learned, go to Step 5.
5
Enable DCC
Select action.
To enable DCC on line of STMn, go to Step 6.
To enable DCC on section of STMn, go to Step 9.
6
Enter ENT-NETIF::AID::::[DCCCHNL=][,IP=][,INTISIS=][,L2SIDE=][,L3QOS=],
LLMODE=[,OSI=][,OSIAREA=][,CHNLUSEDBY= ];;
where:
AID=Protected (west) STM-16 or STM-64 access identifier
7
Repeat Step 6 for protecting (east) STM-16 or STM-64.
8
Go to Step 9.
9
Enter ENT-NETIF::AID::::[DCCCHNL=][,IP=][,INTISIS=][,L2SIDE=][,L3QOS=],
LLMODE=[,OSI=][,OSIAREA=][,CHNLUSEDBY= ];
where:
AID=Protected (west) STM-16 or STM-642 AID
DCCCHNL=SECTION, DCC Channel is a Section/RS DCC.
10
Repeat Step 9 for protecting (east) STM-16 or STM-64.
11
Enable MS-SPRING Operation
Enter ENT-FFP-<STMn>:[TID]:[AID]:[CTAG]:::PTYPE=[,RVRTV=][,RVRTTIM=][,
HLDFFTTIM=][,WKG=][,PROTN=][,PSDIRN=][,PROTOCOL=][,EAST=][,WEST=][,
NODEID=][,NODEDESCR=]; to enable MS-SPRING node operation.
where:
STMn=Optical facility type (STM-16 or STM-64).
WEST=Access identifier of west STMn in MS-SPRING
EAST=Access identifier of east STMn in MS-SPRING
NODEID=Local node identifier. Must be unique within a MS-SPRING. {0-15}
Other parameters are optional. If a value is not entered for these parameters, the system will
use the default value.
For parameter descriptions of TL1 commands used in this procedure, refer to the
1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1
Command Guide.
12
Modify MS-SPRING Ring Map
Enter RTRV-FFP-STMn::[AID];
where:
STMn=Optical facility type (STM-16 or STM-64)
AID=STM-16/STM-64 access identifier
13
Enter RTRV-RINGMAP::[AID]; to retrieve the existing MS-SPRING ring maps.
where:
AID=STM-16 or STM-64 access identifier or ALL
14
Observe output. Note values of NODEID, and RINGMAP parameters.
15
Enter OPR-PROTNSW-<STMn>::AID:::LOP-S:WEST;
where:
AID=FFPSTM-16 or FFPSTM-64 access identifier of MS-SPRING Facility Protection Group
AID=East STMn facility access identifier
LOP-S: Lockout of Protection-Span (MS-SPRing): This command prevents protection switching
on the entire ring. If any working traffic is using the ring protection channels, this command
causes working traffic to be switched back to the working channels regardless of the condition
of the working channels.
WEST: Execute the requested switch action on the facility/span toward the west side of the MS-
SPRing
16
Enter OPR-PROTNSW-<STMn>::AID:::LOP-S:EAST;
where:
AID=FFPSTM-16 or FFPSTM-64 access identifier of MS-SPRING Facility Protection Group
AID=West STMn facility access identifier
17
Enter ED-RINGMAP::AID::::RINGMAP=;
where:
AID=FFPSTM-16 or FFPSTM-64 access identifier of MS-SPRING Facility Protection Group
RINGMAP=Sequence of node IDs within a MS-SPRING. (0-15) Ampersand (&) grouping is
used to join each node ID value (up to 15 values). The first RINGMAP value defines the node
ID of the adjacent MS-SPRING node (east side). Subsequent RINGMAP values define the
node ID of the MS-SPRING node (in the eastward side). The last RINGMAP value defines the
node ID of the adjacent MS-SPRING node (west side).
Go to Step 13.
18
Enter RTRV-RINGMAP::[AID]; to verify the new ring map.
where:
AID=FFPSTM-16 or FFPSTM-64 access identifier of MS-SPRING Facility Protection Group
19
Enter RLS-PROTNSW-<STMn>:[TID]:AID:[CTAG]::LOP-S:WEST;
where:
AID=FFPSTM-16 or FFPSTM-64 access identifier of MS-SPRING Facility Protection Group
AID=West STMn facility access identifier
LOP-S: Clear a previously existing Lockout of Protection-Span.
WEST Execute the requested clear action on the facility/span toward the west side of the MS-
SPRing
20
Enter RLS-PROTNSW-<STMn>:[TID]:AID:[CTAG]::LOP-S:EAST;
where:
STMn=Optical facility (STM-16 or STM-64)
AID=East STMn facility access identifier
EAST: Execute the requested clear action on the facility/span toward the east side of the MS-
SPRing
21
Every node in the ring needs an entry for the MS-SPRING Ring Map. Are there other nodes to
perform this procedure on in the MS-SPRING Ring?
If yes, go to Step 12.
If no, go to Step 1.
22
Modify MS-SPRING Squelch Map
Enter RTRV-SQLMAP::AID; to retrieve current squelch map.
where:
AID=AU4n access identifier or FFPSTM16/STM-64 facility protection group access identifier
23
Observe output. Note values for ENTRY and EXIT parameters. (A value of 255 means the node
ID is unspecified.)
24
Enter ED-SQLMAP::AID::::ENTRY=,EXIT=;
where:
AID=AU4n or STM16/STM-64 access identifier
ENTRY= Node identifier of the source node for a path in MS-SPRing ring. Node ID (0-15) of the
source node in the MS-SPRING.
EXIT= Node identifier of the destination node for a path in MS-SPRing ring. Node ID (0-15) of
the destination node in the MS-SPRING.
25
Enter RTRV-SQLMAP::AID; to verify the new squelch map.
where:
AID=AU4n or STM16/STM-64 access identifier
26
Every connection of the MS-SPRING requires a squelch map entry. Are there other connections
of the MS-SPRING that need squelch map entries?
If yes, go to Step 27.
If no, go to Step 1.
27
Modify MS-SPRING Node ID
Enter RTRV-FFP-STMn::[AID];
where:
AID=FFPSTM-16 or FFPSTM-64 access identifier of MS-SPRING Facility Protection Group
AID=STM-16/STM-64 access identifier
28
Observe output and note current value of NODEID parameter.
29
Enter OPR-PROTNSW-<STMn>::AID:::LOP-S:WEST;
where:
STMn=Optical facility (STM-16 or STM-64)
AID=East STMn facility access identifier
30
Enter OPR-PROTNSW-<STMn>::AID:::LOP-S:EAST;
where:
STMn=Optical facility (STM-16 or STM-64)
AID=West STMn facility access identifier
31
Enter ED-FFP-STMn::AID::::,NODEID=;
where:
STMn=Optical facility type (STM-16 or STM-64)
32
Enter RLS-PROTNSW--<STMn>::AID:::LOP-S:WEST;
where:
STMn=Optical facility (STM-16 or STM-64)
AID=West STMn facility access identifier
33
Enter RLS-PROTNSW--<STMn>::AID:::LOP-S:EAST;
where:
STMn=Optical facility (STM-16 or STM-64)
AID=East STMn facility access identifier
34
Enter RTRV-FFP-STMn::[AID]; to verify new node ID value.
where:
STMn=Optical facility type (STM-16 or STM-64)
AID=FFPSTM-16/FFPSTM64 facility protection group access identifier
35
Go to Step 1.
36
Deprovision STMn MS-SPRING Facilities
Enter DLT-FFP-STMn::AID; to deprovision MS-SPRING node application.
where:
AID=FFPSTM16/FFPSTM64 facility protection group access identifier
STMn=Optical facility type (STM-16 or STM-64).
Note: The STMn protection pair must be in an unswitched state to allow the protection
pair to be deleted. Clear any switched states on the pair.
37
STOP. This procedure is complete.
END OF STEPS
6.35.2 Prerequisites
After the first ACT-USER, edit the password, close the telnet session login again ACT-USER with
new password and then set the region.
6.35.3 General
The rule that should be followed in the setting of this parameter are:
• No default value, are set
• After the first ACT-USER, if REGION is not set, then SET-PRMTR-NE and RTRV-PRMTR-NE
are the only allowed commands.
• Until REGION is set, auto-provisioning of all but mandatory modules are inhibited.
• Once the global REGION is set and the type of provisioning is also set through PROVMODE
parameter, it cannot be changed without scratching and resetting the database.
• The type of provisioning that is set through PROVMODE parameter could be changed during NE
life without scratching and resetting the database.
• DB backup and restore have to record and check the region. It should not be allowed to restore
an ANSI DB to an ETSI NE.
6.35.4 Procedure
1
At login prompt, enter RTRV-PRMTR-NE;
2
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"::NODETYPE=<value>" cr lf
[
"<AID>:<SYSTYPE>,,<RLSID>,<RLSDATE>,<MTXSIZE>::<STATUS>,<REGION>,
<PROVMODE>,<USERLABEL>" cr lf]+
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
3
Enter SET-PRMTR-NE::::::[REGION=][,PROVMODE=][,USERLABEL=];
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
4
STOP. This procedure is complete.
END OF STEPS
6.36.2 Prerequisites
None.
6.36.3 General
The NE utilizes external Building Integrated Timing Supply (BITS) timing to synchronize the system.
The system is externally timed to either a Primary or Secondary BITS reference. The redundant
synchronization subsystem acts in an active/standby relationship.
DS1 BITS timing enters the system either directly via the backplane (Rear Access Shelf) or via
dedicated front plane integral (a panel just below the fan) (Front Access Shelf). BITS timing is
through-connected to the redundant Clock Reference Unit (CRU). The CRUs reside on the matrix
modules (MT320s/MT160s).
The Active CRU (CRU on the active matrix module) provides the internal equipment master clock
(T0) to every module in the system as output of the T0 filtering process. The T0 filtering process
can be phase locked to different synchronization sources:
• one of two BITS external references, or
• one of two line sync references (optional)
In any operation mode, the Standby CRU (CRU on the standby matrix module) is phase locked to
the same synchronization source selected by the active one. Both CRUs receive the same
reference sources.
The ED-BITS command modifies the provisioning of one or more ports dedicated to BITS facilities
for clock synchronization purposes. A BITS input reference is a DS1 signal.
The OPR-SYNCNSW command causes the clock subsystem to switch to the specified (Primary or
Secondary) clock reference source for system clock synchronization. It is also used to switch the
system timing to internal mode. It is also used to control transitions to and from Internal timing.
6.36.4 Procedure
1
Select action.
To retrieve current BITS timing parameters, go to Step 2.
To edit BITS timing parameters, go to Step 5.
To change the timing reference to a different source, go to Step 7.
2
Retrieve Current BITS Timing Parameters
Enter RTRV-BITS::[AID];
where: AID=specifies the selected BITS facility to which the command is directed, i.e. ALL or
BITS-{1-7}-{1-9}-{0,1} (Default= ALL).
3
Examine output for provisioning information, as detailed in the relevant command guide, refer to
“Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
/*
<Informational_Description_Text>
*/ cr lf]
"<AID>::FMT=<value>[,SABIT=<value>],ALMPROF=<value>,SSMSUPPORT=
<value>:<PST>" cr lf
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf;
4
Go to Step 8.
5
Edit BITS Timing Parameters
Enter ED-BITS::AID::::[CMDMDE=][,LINECDE=][,FMT=][,SABIT=][,ALMPROF=]:
[PST];
where: AID=specifies the selected BITS facility to which the command is directed, i.e. BITS-{1-
7}-{1-9}-{0,1}.
CMDMDE= FRCD or NORM.
6
Go to Step 8.
7
Change Timing Reference
Enter OPR-SYNCNSW:::::SWITCHCMD:SWITCHTO=;
where:
• SWITCHCMD= It specifies the switch command which is requested by the user. The
following switch hierarchy is valid w.r.t. acceptance of the switch commands:
− LOCKOUT is the highest request and always accepted
− FRCD is accepted if no LOCKOUT request is present for the timing reference
− MAN is accepted if no LOCKOUT or FRCD request is present and current reference
status is NORMAL
• SWITCHTO= It specifies the AID of the entity for which the switch command is designated.
Possible values:
− SYNC-{1-7}-{1-9}-0 Timing Node within a Shelf
− EXTREF-{1-7}-{1-9}-{0,1} Timing Reference of a Shelf for an External Timing Input Port
− LINEREFSYS-{1-7}-{1-9}-{0-5} Timing Reference of a Shelf for a Line Port selectable for
System Timing
8
STOP. This procedure is complete.
END OF STEPS
6.37.2 General
The ED-SYNCN command modifies the provisioning for the following entities:
• system timing
The system timing entity controls the timing selection. It covers everything related to the NE
internal clock and the system timing selection process. One instance will be created/deleted in
the context shelf provisioning/de-provisioning.
• timing reference for system timing selection
The timing reference covers a timing source which is used as input for the system timing
selection process. 8 instances are created/deleted in the context shelf provisioning/de-
provisioning (6 line timing references and 2 external timing references)
Each timing reference can be assigned (i.e. connected) to a port. The following port types can be
assigned to a timing reference:
• BITS port (i.e. external timing reference)
• STMn port (i.e. line timing reference)
• Ethernet port (i.e. line timing reference)
The clock reference selections controlled by this command are applied uniformly to both CRUs.
Omitting a reference from assignment, if it is currently the Active reference on CRG, causes CRG to
switch to another reference or to Holdover.
Executing an ED-SYNCN command causes the following primary state transitions for the specified
timing reference.
The RTRV-SYNCN command retrieves provisioning and state information for the following entities:
• system timing (one instance per shelf)
• timing reference (2 external and 6 line timing instances per shelf)
The RMV-SYNCN command causes the specified facility to be placed in an out-of-service (OOS-
MA) state for maintenance purposes.
The command logically removes the system timing reference entity from timing specific alarm
reporting service
Executing a RMV-SYNCN command causes a state transition for the specified system timing
reference from:
• IS-NR to OOS-MA
• OOS-AU to OOS-MA
When a system timing reference is in an OOS-MA state, all timing condition types are cleared and a
MAN condition type is set for the specified system timing reference.
When a system timing reference is in an OOS-MA state, no timing alarms or condition types are
autonomously reported, but system timing reference alarm conditions are monitored.
The RST-SYNCN command causes the specified facility to be placed in an IS-NR state.
The command logically restores the system timing entity to facility specific alarm reporting service.
Executing a RST-SYNCN command causes a state transition for the specified system timing
reference from:
• OOS-MA to IS-NR
When a system timing reference transits from the OOS-MA to an IS-NR state, the MAN condition
type is cleared, any existing system timing reference condition types are set.
6.37.3 Procedure
1
Select action.
To retrieve information on equipment providing Network Element synchronization, go to Step 2.
To retrieve provisioning and state information, go to Step 3.
To edit clock reference parameters, go to Step 5.
To change the timing reference to a different source, go to Step 7.
To remove equipment providing Network Element synchronization, go to Step 7.
To restore equipment providing Network Element synchronization, go to Step 10.
2
Retrieve information on equipment providing Network Element synchronization
Enter:
RD-SYNCN;
Result: The successful response for a RD-SYNCN command contains one or two lines of
parsable output data, listing data for timing entities (matrix boards host the Clock Reference
Units (CRUs) as daughter boards) used by the system.
3
Retrieve provisioning and state information for system timing and timing reference
Enter:
RTRV-SYNCN;
Result:
The successful response for a RTRV-SYNCN command contains for each replied entity one
line of parsable output data. i.e.
• one line for each replied system timing entity
• one line for each replied timing reference entity
4
Change Timing Reference
Enter OPR-SYNCNSW:::::SWITCHCMD:SWITCHTO=;
where:
• SWITCHCMD= It specifies the switch command which is requested by the user. The
following switch hierarchy is valid w.r.t. acceptance of the switch commands:
− LOCKOUT is the highest request and always accepted
5
Edit clock reference parameters
6
Enter:
ED-SYNCN::AID::::[,PROVQL=];
where:
AID = Sync Access Identifier, specifies either the timing node for the system timing entity
(delivering the system timing reference T0) or a timing reference (external or line port
connected to the timing selection process) to which the command is directed.
Possible values
• SYNC-{1-7}-{1-9}-0 (Timing Node within a Shelf)
• EXTREF-{1-7}-{1-9}-{0,1} (Timing Reference of a Shelf for an External Timing Input Port)
• LINEREFSYS-{1-7}-{1-9}-{0-5} (Timing Reference of a Shelf for a Line Port selectable for
System Timing)
PROVQL specifies the provisioned quality level of a timing reference. Two different methods
are supported; i.e. the quality level is either derived from the incoming SSM value or a fixed
quality value is set. The value AUTO is only allowed for ports supporting SSM.
• SEC ETSI quality level value is fixed to SEC (SDH Equipment Clock, specified in G.813
option 1)
Restriction: The parameter is only applicable for the timing reference entity.
7
Logically remove the system timing reference entity
Verify that the system timing reference is not in OOS-MA state
8
Verify that the system timing reference is not being used as the Active reference for one or both
CRUs and the CMDMDEvalue is not equal to NORM.
9
Enter
RMV-SYNCN::AID::[CMDMDE];
where:
AID = Access Identifier, specifies the selected system timing reference facility to which the
command is directed.
10
Logically restore the system timing entity
Verify that the system timing reference is not in OOS-MA state.
11
Enter:
RST-SYNCN::AID;
where:
AID = EXTREF-{1-7}-{1-9}-{0,1} (Timing Reference of a Shelf for an External Timing Input Port).
END OF STEPS
6.38.2 General
The ENT-USER-SECU command is used to create a new user profile in the User Security
Database.
To change a user profile the ED-USER-SECU command, this command is used by a user with
security administrator privileges to edit the existing user profile entry, identified by the User Identifier
(UID), in the User Security Database.
Note: All of the changes to the provisioned values shall be allowed and take effect
immediately, only if the input UID's user is currently not logged on.
The RTRV-USER-SECU command retrieves the user profile entry, identified by the specified UID
"search key", in the User Security Database.
The RTRV-USER-SECU command retrieves both the static user provisioning information, i.e. what
provided by means of ENT/ED-USER-SECU commands (user privilege level, max interval for link
timeout and user provided name) and some dynamic user information (uid status depending on the
result of INH/ALW-USER-SECU issued commands, uid status depending on whether or not the
password is expired and no more possible to be changed and, finally, the time remaining to the
password expiration).
The RTRV-USER-SECU command retrieves all the user profile parameters that are actually active
in that moment, for the entered user/users. In fact, a given user profile could have some parameters
that have been modified at system level, but still not applied to the user profile, because the user
was logged on when the system parameters values have been modified, and the user is still
currently logged on.
The RTRV-USER-SECU command retrieves also those system parameters that are not
provisionable by means of ED/ENT-USER-SECU, but only by means of SET-ATTR-SECUDFLT. For
these system parameters, RTRV-USER-SECU shall report the values that are actually applied in
that moment, for the entered user/users.
Only a user with administrator privileges can retrieve any or all user profile entries. Any other user
can only retrieve their own user profile entry, by means of the command RTRV-USER.
The INH-USER-SECU command shall allow a user with security administrator privileges to inhibit
(i.e., disable) existing users (without deleting the user account), so the users can be denied to get
an authorized session with the system (i.e., the inhibited users cannot log on).
When the INH-USER-SECU command is issued against a logged on user, it shall log off the target
user and inhibit him/her.
The INH-USER-SECU command shall be denied when issued against the user that is issuing the
command itself, that is no auto inhibition is allowed. This also prevents the inhibition of the last
remaining administrative user.
The ALW-USER-SECU command shall allow to reinstate users, so the user can again establish a
session with the system.
The ALW-USER-SECU command allows reinstatement of users that have been disabled by the
following reasons:
• an INH-USER-SECU command
• exceeding the maximum number of invalid login attempts
• user login inactivity (dormant user)
The DLT-USER-SECU command deletes user profiles in the User Security Database, for the
specified User Identifier (UID).
Only the security administrator can delete a user profile entry in the User Security Database (i.e.,
execute a DLTUSER- SECU command).
In addition, the default users profiles, so included the vendor user profile, cannot be deleted.
The security administrator can delete both users having unauthenticated session, i.e. logged off
users, and logged on users.
The deletion of a logged on user shall log off the target user and delete him/her.
When the command is entered to delete a user that exceeded the max number of login attempts, i.e
a user for which an INTRUSION alarm was emitted, the NE also clears the INTRUSION alarm for
that UID.
For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 Transport
Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.
6.38.4 Procedure
Select action:
• Create a new user with “Security Administrator” Privileges, go to Step 2
• Retrieve user with “Security Administrator” Privileges, go to Step 5
• Disable user with “Security Administrator” Privileges, go to Step 6
• Enable user with “Security Administrator” Privileges, go to Step 9
• Change user with “Security Administrator” Privileges, go to Step 11
• Delete user with “Security Administrator” Privileges, go to Step 12
2
New User with Security Administrator Privileges creation
3
Create a new user (for example: USER01) with “Security Administrator” Privileges (set
UAP=SEC), i.e. enter:
ENT-USER-SECU::UID:::PID,CONFIRMPID,[UAP]:[PAGE=][,PCND=] [,PCNN=][,
POINT=][,UOUT=];
where:
• UID = User Identifier, specifies a unique user ID.
• PID = Password Identifier, specifies the user’s login password.
• CONFIRMPID = Password Identifier Confirmation, confirms the user’s login password.
• UAP = User access privilege(s) granted to this user.
Values are:
− CONF (Configure. User may configure the system, performing provisioning and testing of
all IO cards, ports, interfaces and circuits. Users may configure all subsystems which do
not allow for system wide effect. The user may perform nondestructive provisioning of IO
cards, ports and interfaces, initiate test procedures which are not service affecting and
retrieve information about the system)
− NETADMIN (Network Administrator. A network administrator may configure anything in the
system except user accounts)
− PROV (Provision. The user may perform non-destructive provisioning of IO cards, ports
and interfaces, initiate test procedures which are not service affecting and retrieve
information about the system.)
− READ (Read-only. User may retrieve information about the system)
− SEC (Security Administrator. A user with the security privilege flag may create, delete, and
modify user accounts. A security user need not be a network administrator, but can create
user accounts with network administrator privilege. User shall be able to issue all
commands. User shall not be able to use debug and software development tools.)
− DEBUG (Test)
− NOTMOUT (No inactivity timeout applied to the user.)
Other parameters are optional. If a value is not entered for these parameters, the system will
use the default value. Refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-
160) Release 5.1 TL1 Command Guide for details on parameter values.
4
Login to the NE with the new user (for ex.: USER01).
Verify that the command is completed with response ‘COMPLD” and Login is successful.
5
Retrieve user with Security Administrator Privileges
After the login to the NE with the user created (for ex.:USER01).
Enter:
RTRV-USER-SECU::[UID];
where:
UID = User Identifier, specifies a unique user ID.
Values are:
• <5-12 VALID UID CHARACTERS>
• ALL.
Result: Retrieval shows the new user profile created USER01.
Example: The following example illustrates the command, issued by an administrator user, and
associated output for retrieving the user security database entry for user01:
RTRV-USER-SECU::user01;
user01:READ:STATE=ACTIVE,PAGE=60,PCND=7,PCNN=0,POINT=180,PAGEXP=200
6-06-06-00-00-00,UOUT=90,LOGFAIL=0,LAST=1970-01-01-00-00-00,KAMINTVL
=0,MININTVL=15,MXINV=5,TMOUT=15;
In particular:
The User State parameter indicates the user's current inhibit or allow status.
ACTIVE User is currently not inhibited from logging in.
SUSPENDED User is currently inhibited from logging in, or has exceeded max number of
failed login (MXINV), or has entered consecutive invalid login attempts within the minimum
allowed interval (MININTVL).
6
Inhibit to disable user with Security Administrator Privileges
If the user with Security Administrator Privileges (for ex.: USER01) is logged in, please log out
the user.
Observe that the user with Security Administrator Privileges (for ex.: USER01) session is
terminated
7
From ADMIN session Inhibit to disable the user with Security Administrator Privileges (for ex.:
USER01).
Enter:
INH-USER-SECU:::::UID;
where:
UID = User Identifier, specifies a unique user ID.
8
Retrieve to check the user's state.
Result: Retrieval shows the user “USER01” in suspended state (STATE=SUSPENDED).
9
Enable user with Security Administrator Privileges
From ADMIN session enable the user with Security Administrator Privileges (for ex.: USER01).
Enter
ALW-USER-SECU:::::UID;
where:
UID = User Identifier, specifies a unique user ID.
10
Check that the command is completed and that retrieval command shows the user with
Security Administrator Privileges (for ex.: USER01) is in active state (STATE=ACTIVE).
11
Change user with Security Administrator Privileges
Enter:
ED-USERSECU::UID:::[NEWUID],[NEWPID],[CONFIRMPID],[UAP]:[PAGE=][,PCND
=][,PCNN=][,POINT=][,UOUT=][,PRIVPROT=][,AUTHPROT=];
where:
UID = User Identifier, specifies a unique user ID.
Other parameters are optional. If a value is not entered for these parameters, the system will
use the default value. Refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-
160) Release 5.1 TL1 Command Guide for details on parameter values.
12
Delete user with Security Administrator Privileges
Enter:
DLT-USER-SECU::UID;
where:
UID = User Identifier, specifies a unique user ID.
END OF STEPS
6.39.2 Prerequisites
This command is used for ETSI.
6.39.3 General
Multicast cross connections are established by creating of many 1WAY cross connections starting
from the same FROM facility.
If CCT of 1WAY is specified, a one-way cross-connection is established between the receive side
(from the network, source of cross connection) of the FROM facility and the transmit side (to the
network, sink of the cross connection) of the TO facility.
A one-way cross-connect can be established between the receive and transmit side of the same
facility (FROM and TO are identical thereby establishing a loopback through the system's cross-
connect matrix).
If CCT of 2WAY is specified, a two-way cross-connection is established between the FROM and TO
facilities.
If for the FROM or TO facility a LOPOOL is specified a new free modifiable vc4 (MVC4) will be
allocated. This allocated MVC4 will be reported in the command response and data base change
message instead of the LOPOOL.
The connection between lower order PTF facilities can occupy new modifiable vc4 (MVC4) facilities
(e.g. the connection between two VCGLOVC12 entities). Those MVC4 must be free if they are new
allocated. If the MVC4s are really occupied depends of the cross connection strategy of the NE.
(Please see also RTRV-LOPOOL.)
The cross connections supported by this command are shown in the following figures.
If ampersand ranging (&&) is used for an AID, the same CKTID value is applied to each connection
within the AID range.
The ACD Parameter retrievable by RTRV-CRS-<rate> will be set to LOCAL for the cross connection
created by this command.
It is allowed to reenter an existing cross connection. This means FROM and TO are identical to an
already existing cross connection and all other parameter values are identical to this cross
connection. If one of the others parameters deviates, the command will be rejected.
RTRV-CKTID retrieves the FROM and TO ports of a cross connect that has the specific Symbolic
Circuit IDs previously assigned to flag the cross-connects with alpha-numeric IDs (using ENT/ED-
CRS commands).
A separate line of parsable output data is provided for each of the following cross-connect types
containing a CKTID or CKTIDTF parameter matching the input Circuit ID:
1WAY, 1WAYSNCP: One line of data for each one-way cross-connection, including the case of a
one-way bridge connection.
2WAY, 2WAYSNCP: One line of data for each two-way cross-connection. If no cross-connect
containing a CKTID or CKTIDTF parameter matching the input Circuit ID is found, then a COMPLD
message is returned without any output parameters.
6.39.4 Procedure
1
Select action.
To retrieve cross-connection information, go to Step 2.
To create cross-connection, go to Step 5.
To retrieve cross-connection with circuit ID, go to Step 7.
To modify cross-connection, go to Step 10.
To delete cross-connection, go to Step 12.
To end this procedure, go to Step 14.
2
Retrieve Cross-Connection Information
Enter RTRV-CRS::AID:::[RTRVMODE=];
where:
• AID = selected facility(ies) to which the command is directed. AID of ALL retrieves all the
cross connects in the system. Possible values:
− ALL for all AID
− STM1AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8}-1 for AU4 embedded within an STM1
− STM64AU464C-{1-7}-{1-9}-{2-9,12-19,2 1-36}-1-1 for AU4-64c embedded within an
STM64
− STM64AU416C-{1-7}-{1-9}-{2-9,12-19,2 1-36}-1-{1,17,33,49} for AU4-16c embedded
within an STM64
− STM64AU44C-{1-7}-{1-9}-{2-9,12-19,21 -36}-1-{1,5,9,13,17,21,25,29,33,37,41,4
5,49,53,57,61} for AU4-4c embedded within an STM64
− STM64AU4-{1-7}-{1-9}-{2-9,12-19,21-3 6}-1-{1-64} for AU4 embedded within an STM64
− STM16AU416C-{1-7}-{1-9}-{2-9,12-19,2 1-36}-{1-4,5,7}-1 for AU4-16c in an STM16 on a
2G5PSO or 10xANY
− STM16AU44C-{1-7}-{1-9}-{2-9,12-19,21 -36}-{1-4,5,7}-{1,5,9,13} for AU4-4c in anSTM16
on a 2G5SO or 10xANY
− STM16AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4,5,7}-{1-16} for AU4 in an STM16 on a
2G5SO or a 10xANY
− STM4AU44C-{1-7}-{1-9}-{2-9,12-19,21- 36}-{1-8}-1 for AU4-4c embedded within an STM4
− STM4AU4-{1-7}-{1-9}-{2-9,12-19,21-36} -{1-8}-{1-4} for AU4 embedded within an STM4
− MVC4-{1-7}-{1-9}-{21,22,35,36}-{1-64} for Modifiable VC4 on LOA card
− VCGVC4-{1-7}-{1-9}-{2-9,12-19,21-36}-{ 1-10}-{1-7} ETSI (VC4 within a GBE VCG on a
10xAny module)
− VCGVC4-{1-7}-{1-9}-{2-9,12-19, 21-36}-{1,3,5,7,9}-{1-12} ETSI (VC4 in an FC200 VCG on
a 10xAny module- 12xVC4 )
− VCGVC4-{1-7}-{1-9}-{2-9,12-19, 21-36}-{3,7}-{1-24} ETSI (VC4 in an FC400 VCG on a
10xAny module - 24xVC4)
3
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
"<FROM>,<TO>:<CTYPE>,<LEVEL>:[CKTID=<value>][,CKTIDTF=<value>][,
ALTERNATE=<value>][,FROMPING=<value>][,ACD=<value>]:<PST>[,<SST>]" cr
lf]
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
4
Go to Step 1.
5
Create Cross-Connection
Enter ENT-CRS-<rate>::FROM,TO:::[CCT]:[CKTID=];
where:
• <rate> = cross-connection rate on which the command acts. Possible values: VC4, VC44C,
VC416C, VC464C, LOVC12, LOVC3.
• FROM = AID of connection point. Indicates the FROM (receive side from the network, source
of cross-connection) facility of the cross-connection.
Possible values for VC4 rate:
− STM1AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8}-1 for AU4 embedded within an STM1
− STM64AU4-{1-7}-{1-9}-{2-9,12-19,21-3 6}-1-{1-64} for AU4 embedded within an STM64
− STM16AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4,5,7}-{1-16} for AU4 in an STM16 on a
2G5SO or a 10xANY
6
Go to Step 1.
7
Retrieve Cross-Connection with Circuit ID
Enter RTRV-CKTID:::::CKTID;
where: CKTID = Circuit ID to search, 1 to 45 ASCII characters (excluding semi-colon, double
quote, greater than, lesser than and backslash characters) within enclosing double quotes. An
asterisk (*) may be used as a wildcard character.
8
Observe output (output displays all connections containing specified circuit ID), as detailed in
the relevant command guide, refer to “Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
"<FROM>,<TO>:<CTYPE>,<LEVEL>:[CKTID=<value>]
[,CKTIDTF=<value>]:<PST>[,<SST>]" cr lf]
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
9
Go to Step 1.
10
Modify Cross-Connection
Enter ED-CRS-<rate>::FROM,TO:::[CCT]:[CKTID=];
where:
• <rate> = crossconnection rate on which the command acts. Possible values: VC4, VC44C,
VC416C, VC464C, LOVC12, LOVC3.
• FROM = AID of connection point. Indicates the FROM (receive side from the network, source
of cross-connection) facility of the cross-connection. Possible values as referred in Step 5.
• TO = AID of connection point. Indicates the TO (transmit side to the network, sink of cross-
connection) facility of the cross-connection. Possible values as referred in Step 5.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
11
Go to Step 1.
12
NOTICE
Optional Content
Possibility of service interruption. Deleting an active cross-connection always affects service.
Optional Content added above. Please modify as needed.
Delete Cross-Connection
Enter DLT-CRS-<rate>::FROM,TO:::[CCT];
where:
• <rate> = crossconnection rate on which the command acts. Possible values: VC4, VC44C,
VC416C, VC464C, LOVC12, LOVC3.
• FROM = AID of connection point. Indicates the FROM (receive side from the network, source
of cross-connection) facility of the cross-connection. Possible values as referred in Step 5.
• TO = AID of connection point. Indicates the TO (transmit side to the network, sink of cross-
connection) facility of the cross-connection. Possible values as referred in Step 5.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
13
Go to Step 1.
14
STOP. This procedure is complete.
END OF STEPS
6.40.2 Prerequisites
A VCG must be assigned to an ethernet port.
The port must be provisioned first. Refer to the following procedures to provision parent facilities:
• GBE port on 10XANY board: 6.8 “Administer Ethernet Facility ” (p. 155)
• MAU port on 10XANY board: 6.18 “Administer MAU Facility” (p. 193)
Besides the the VCG entity could be a logical VCG for ethernet switching on a PP10AD module
6.40.3 General
The RTRV-VCG command retrieves provisioned values of a specified VCG entity and its current
PST, SST values. The command is executed regardless of the state of the VCG.
The ENT-VCG command creates a Virtual Concatenation Group. The command also assigns initial
group of SDH Virtual Containers to the VCG.
The Type of Virtual Container is specified in VCGTYPE parameter and can be for ETSI: VC4,
LOVC3, LOVC12.
When a VCG is provisioned to an OOS-MA state, a MAN condition type is set for the specified
VCG.
When a VCG is in an OOS-MA, OOS-AUMA state, no VCG condition types are autonomously
reported for the VCG, but VCG alarm conditions are monitored (retrievable with the RTRV-VCG
command).
When a VCG is in an OOS-MA, OOS-AUMA state, no VCG condition types are autonomously
reported for the VCG, but VCG alarm conditions are monitored (retrievable with the RTRV-VCG
command).
If command is successful, path terminations functions in the number of MAXMBR will be created as
members of VCG.
The ED-VCG command is used to enable or disable LCAS on a VCG and also set parameters
related to the LCAS protocol previously provisioned using the ENT-VCG command. RTRV-VCG can
be used to view the parameters.
6.40.4 Procedure
1
Enter RTRV-VCG::AID;
where: AID = VCG Access Identifier, specifies the VCG entity. Possible values:
• ALL for all AID
• VCG-{1-7}-{1-9}-{2-9,12-19}-{1-124} for Logical VCG for ethernet switching on a PP10AD
module
• GBEVCG-{1-7}-{1-9}-{2-9,12-19,21-36}- {1-10} for VCG on a GBE port on a 10xAny module
• MAUVCG-{1-7}-{1-9}-{2-9,12-19,21-36}- {1-10} for VCG on a MAU port on a 10xAny module
• FC200VCG-{1-7}-{1-9}-{2-9,12-19, 21-36}-{1,3,5,7,9} for FC200 VCG on a 10xAny module-
12xVC4 )
• FC400VCG-{1-7}-{1-9}-{2-9,12-19, 21-36}-{3,7} for FC400 VCG on a 10xAny module -
24xVC4)
2
Examine output for provisioning information on port, as detailed in the relevant command guide,
refer to “Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<AID>::ACTMBR=<value>[,HLDOFFTIME=<value>],LCASENABLE=<value>,
MAXMBR=<value>,PROVMBR=<value>[,RSQACKTOUT=<value>][,SDMODE=<value>],
VCGTYPE=<value>[,WTRTIME=<value>][,BIDISERVPROP=<value>][,PRTCLTYPE=
<value>][,MAXDIFFDLY=<value>][,ALMPROF=<value>][,ACD=<value>][,
MGRACD=<value>]:<PST>,<SST>" cr lf
[
/*
<Informational_Description_Text>
*/ cr lf]
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
3
Ensure that port is in valid state for provisioning (OOS-MA, UAS).
4
Enter ENT-VCG::AID::::MAXMBR=,VCGTYPE=[,CSFPROP=][,CSFTYPE=][,PRTCLTY
PE=][,ALMPROF=]:[PST];
where:
• AID = VCG Access Identifier, specifies the VCG entity. Possible values:
ENT-VCG::VCG-1-1-5-32::::MAXMBR=10,VCGTYPE=VC4;
In the following example, VCG number 3 on the 10XANY module in slot 5 is provisioned with 5
VC4 members.
ENT-VCG::GBEVCG-1-1-5-3:::MAXMBR=5, VCGTYPE=VC4;
5
Deprovision VCG facility
Enter RTRV-VCG::AID;
where: AID = VCG Access Identifier, specifies the VCG entity. Possible values:
• VCG-{1-7}-{1-9}-{2-9,12-19}-{1-124} for Logical VCG for ethernet switching on a PP10AD
module
• GBEVCG-{1-7}-{1-9}-{2-9,12-19,21-36}- {1-10} for VCG on a GBE port on a 10xAny module
• MAUVCG-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10} for VCG on a MAU port on a 10xAny module
• FC200VCG-{1-7}-{1-9}-{2-9,12-19, 21-36}-{1,3,5,7,9} for FC200 VCG on a 10xAny module-
12xVC4 )
6
Examine output for provisioning information on port, as detailed in the relevant command guide,
refer to “Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<AID>::ACTMBR=<value>[,HLDOFFTIME=<value>],LCASENABLE=<value>,
MAXMBR=<value>,PROVMBR=<value>[,RSQACKTOUT=<value>][,SDMODE=<value>],
VCGTYPE=<value>[,WTRTIME=<value>][,BIDISERVPROP=<value>][,PRTCLTYPE=
<value>][,MAXDIFFDLY=<value>][,ALMPROF=<value>][,ACD=<value>][,
MGRACD=<value>]:<PST>,<SST>" cr lf
[
/*
<Informational_Description_Text>
*/ cr lf]
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
7
Does port have SST of ACT, BUSY, SDEE, TRM, or UAS?
If yes, DLT-VCG command cannot be performed on the specified VCG port. Go to Step 12.
If no, go to Step 8.
8
Enter DLT-VCG::AID;
where: AID = VCG Access Identifier, specifies the VCG entity. Possible values previously
decribed.
Example: In the following example, VCG number 32 on the Multiservice Collector card in slot 5
is de-provisioned:
DLT-VCG::VCG-1-1-5-32;
In the following example, VCG number 7 on the 10XANY module in slot 5 is de-provisioned:
DLT-VCG::GBEVCG-1-1-5-7;
9
Modify VCG Facility
Enter RTRV-VCG::AID;
where: AID = VCG Access Identifier, specifies the VCG entity. Possible values:
• ALL for all AID
• VCG-{1-7}-{1-9}-{2-9,12-19}-{1-124} for Logical VCG for ethernet switching on a PP10AD
module
• GBEVCG-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10} for VCG on a GBE port on a 10xAny module
• MAUVCG-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10} for VCG on a MAU port on a 10xAny module
• FC200VCG-{1-7}-{1-9}-{2-9,12-19, 21-36}-{1,3,5,7,9} for FC200 VCG on a 10xAny module-
12xVC4 )
• FC400VCG-{1-7}-{1-9}-{2-9,12-19, 21-36}-{3,7} for FC400 VCG on a 10xAny module -
24xVC4)
10
Examine output for provisioning information on port as detailed in the relevant command guide,
refer to “Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<AID>::ACTMBR=<value>[,HLDOFFTIME=<value>],LCASENABLE=<value>,
MAXMBR=<value>,PROVMBR=<value>[,RSQACKTOUT=<value>][,SDMODE=<value>],
VCGTYPE=<value>[,WTRTIME=<value>][,BIDISERVPROP=<value>][,PRTCLTYPE=
<value>][,MAXDIFFDLY=<value>][,ALMPROF=<value>][,ACD=<value>][,
MGRACD=<value>]:<PST>,<SST>" cr lf
[
/*
<Informational_Description_Text>
*/ cr lf]
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
11
Enter ED-VCG::AID::::[MAXMBR=][,HLDOFFTIME=][,LCASENABLE=][,RSQACKTOUT=]
[,SDMODE=][,CSFPROP=][,CSFTYPE=][,ALMPROF=][,MODE=]:[PST];
where: AID = VCG Access Identifier, specifies the VCG entity. Possible values:
• VCG-{1-7}-{1-9}-{2-9,12-19}-{1-124} for Logical VCG for ethernet switching on a PP10AD
module
12
STOP. This procedure is complete.
END OF STEPS
6.41.2 Prerequisites
None.
6.41.3 General
This procedure allows the operator to enable or disable the capability of the node to notify to the
manager its own presence, once it has been put in the network and configures as address.
Successful completion of this command generates a REPT DBCHG (report database change)
autonomous response message.
Successful completion of this command with enabling set, triggers the periodical sent of
autonomous messages with proprietary format towards the network managers. The period is fixed
to 5min.
Successful completion of this command with disabling set, stops the periodical sent of autonomous
message towards the network managers and autodiscovery state is set to idle.
6.41.4 Procedure
1
Enter RTRV-NE-DSCV;
2
Examine output both for enabling and for relevant state information on NE.
3
Enter ED-NE-DSCV:::::ENABLED= ;
4
STOP. This procedure is complete.
END OF STEPS
6.42.2 General
A Boundary Clock has been devised, which terminates the 1588 flow on one receiving link and
then acts as a 1588 GrandMaster for all outgoing links.
When the system operates as Boundary Clock, PTP operates as Slave on a certain port and as
Master on one other (or more) port(s). The Slave Port drives in term of Frequency and/or Phase the
associated Master port(s). Boundary Clock function is activated in order to ensure an efficient
transmission of PTP messages withing a hop-by-hop deployment of a packet network.
6.42.3 Procedure
Select action
• Boundary TOD Card Creation, go to Step 2.
• Phase Synchronization reference configuration, go to Step 16.
• Boundary TOD Card Deletion, go to Step 19.
2
Boundary TOD Card Creation
Enter:
ENT-EQPT::AID::::PROVISIONEDTYPE=PP1588, CKMODE=BC;
where:
• AID = PTP-{1-7}-{1-9}-{2-9,12-19,21-36}. Time Of Day - TOD Card
• CKMODE=BC (Boundary Clock), i.e. it means that the PP1588 card is configured in in
Boundary Clock Configuration.
Result:
Note: PPS-IN, PPS-OUT and PTPSlave can be selected as input for CRU and for
internal Phase Distributor.
For master clock the facility PTPMaster-r-s-b-2 is created:
• automatically the Master clock will be taken form T0 distributed internally by CRU
• automatically the Master phase/TOD will be taken from phase distributed by internal
Phase distributor
3
Select action:
manage PPS-IN port facility, go to Step 4
manage PPS-OUT port facility, go to Step 6
4
For PPS-IN port the facility PPSIN-r-s-b-1 is created and the following parameters can be
provisioned:
ED-PPSIN::AID::::[CMDMDE=][,TOD=][,DLY=][,ALMPROF=]:[PST];
where:
• AID = PPSIN-{1-7}-{1-9}-{2-9, 12-19, 21-36}-1 (Pulse Per Second Input Port).
I.e PPSIN Access Identifier, specifies the input port receiving the PPS signal
• TOD= Time Of Day, determines if the information about Time Of Day shall be expected as
input (i. e. Sink direction) or sent as output (i. e. Source direction). Values are:
Y Yes. Time Of Day info is expected/sent.
N No. Time Of Day info is not expected/sent.
• DLY = Delay, indicates the delay to be considered by IEEE1588v2 protocol for
synchronization. The delay is due to the lenght of the cable on the link. The lenght
determines a propagation delay equal to D [ns], where D is the value to be provisioned. The
parameter applies to the receiver; normally positive values shall be provisioned; but negative
values can be provisioned as well for compensating excessive dalys provisioned at the oter
side transmitter. The unit of measure is nanosecond.
5
Enter:
RTRV-PPSIN::[AID];
The RTRV-PPSIN command retrieves the provisioning and state information of one or more
ports, in the 1588v2 application, dedicated to the reception of the PPS signal.
Result: The successful response for a RTRV-PPSIN command contains one or more lines of
parsable output data, in ascending order, listing the possible timing input ports used by the
system.
6
For PPS-OUT the facility PPSOUT-r-s-b-1 is created and the following parameters can be
provisioned
ED-PPSOUT::AID::::[S1TRANS=][,TOD=][,DLY=];
where:
• AID = PPSOUT-{1-7}-{1-9}-{2-9, 12-19, 21-36}-1 (Pulse Per Second Output Port)
I.e. Access Identifier, specifies the output port transmitting the PPS signal.
• S1TRANS = {ACT, PRC, SSUL, SSUT, SEC, DUS, NONE}.
Sync message byte to be transmitted, determines if the transmitted byte will have the "DUS"
message or will have the actual traceability of the signal.
• TOD= Time Of Day, determines if the information about Time Of Day shall be expected as
input (i. e. Sink direction) or sent as output (i. e. Source direction). Values are:
Y Yes. Time Of Day info is expected/sent.
N No. Time Of Day info is not expected/sent.
• DLY = Delay, indicates the delay to be considered by IEEE1588v2 protocol for
synchronization. The delay is due to the lenght of the cable on the link. The lenght
determines a propagation delay equal to D [ns], where D is the value to be provisioned. The
parameter applies to the receiver; normally positive values shall be provisioned; but negative
values can be provisioned as well for compensating excessive dalys provisioned at the oter
side transmitter. The unit of measure is nanosecond.
7
Enter:
RTRV-PPSOUT::[AID]:;
To retrieve the provisioning and state information of one or more ports, in the 1588v2
application, dedicated to the transmission of the PPS signal.
Result: The successful response for a RTRV-PPSOUT command contains one or more lines
of parsable output data, in ascending order, listing the possible timing output ports used by
the system.
8
Enter:
RTRV-PTPSLAVE:[TID]:[AID]:[CTAG];
the command retrieves the state information of one or more ports, in the 1588v2 application.
Result: The successful response for a RTRV-PTPSLAVE command contains one or more
lines of parsable output data, in ascending order (from lowest specified PTPSLAVE AID to
the largest specified PTPSLAVE AID), for each PTPSLAVE AID specified.
9
Enter:
RTRV-PTPMASTER:[TID]:[AID]:[CTAG];
the command retrieves the state information of one or more ports, in the 1588v2 application.
Result: The successful response for a RTRV-PTPMASTER command contains one or more
lines of parsable output data, in ascending order (from lowest specified PTPMASTER AID to
the largest specified PTPMASTER AID), for each PTPMASTER AID specified.
10
Select action:
To provide input synchronization for the NE via TOD card card (i.e. 1PPS IN or PTP slave clock
port), go to Step 11
To configure the timing reference selected for output synchronization (T4) via TOD card
interface (i.e. 1PPS IN or PTP slave clock port), go to Step 13.
11
Enter:
ED-SYNCN::AID::::[ALMPROF=][,SYNCMSG=][,ASSPORTAID=][,PRO VQL=][,
REFPRIO=]:[PST];
where:
• AID = Sync Access Identifier, specifies either the timing node for the system timing entity
(delivering the system timing reference T0) or a timing reference (external or line port
connected to the timing selection process) to which the command is directed.
Select one of the “LINE REF Identifier ”(LINEREFSYS-1-1- 0...7) to retrieve timing input
source from the line.
• ASSPORTAID = specifies whether the timing reference is assigned to a port and if assigned
it specifies the AID of the port. Value can be:
PPSIN-{1-7}-{1-9}-{2-9,12-19,21-36}-1 (Pulse Per Second Input port)
PTPSLAVE-{1-7}-{1-9}-{2-9,12-19,21-3 6}-1 (PTP 1588 Slave Clock port)
Note: Executing an ED-SYNCN command causes the following primary state transitions
for the specified timing reference.
12
Retrieve provisioning and state information.
Enter:
RTRV-SYNCN::[AID];
13
1588 PPS Input ports can be assigned to synchronization reference for the selection of system
timing output reference T4, as well as other synchronization sources (e.g. BITS, OCn/STMn,
GBE) .
Provisioning is performed by the TL1 ED-SYNCNOUT command.
14
Enter:
ED-SYNCN-OUT::AID::::[ALMPROF=][,SYNCMSG=][,OUTSEL=][,QLT HRESHOLD=][,
REGENLOOPMODE=][,TCLCK=][,ASSPORTAID=][,PROVQL=][,REFPRIO=]:[PST];
where:
• AID = Sync Access Identifier, specifies either the timing node for the output timing entity or
the output timing reference entity to which the command is directed.
Select one of the “LINEREFOUT Identifier” (LINEREFOUT-1-1- 0-..5) to provide configuration
for the TOD card interface reference signal
• TCLCK = Transparent Clock function, determines if transport of Transparent Clock is
disabled or not in the Node.
Values are:
DISABLE Disable. The Transparent clock function is disabled.
1588V2 IEEE1588v2. The Transparent clock function is enabled by means of IEEE1588v2
protocol.
Restriction: The parameter is only applicable for the output timing entity.
• ASSPORTAID = specifies whether the timing reference is assigned to a port and if assigned
it specifies the AID of the port. The following port types can be used for establishing a
connection towards a timing reference.
Valuea are:
PPSIN-{1-7}-{1-9}-{2-9,12-19,21-36}-1 (Pulse Per Second Input port)
PTPSLAVE-{1-7}-{1-9}-{2-9,12-19,21-3 6}-1 (PTP 1588 Slave Clock port)
Result: Executing an ED-SYNCN-OUT command causes the following primary state
transitions for the specified timing reference.
15
Retrieve provisioning and state information.
Enter:
RTRV-SYNCN-OUT::[AID];
16
The Phase configuration applies either to input and output direction.
PTPSlave port and PPS Input port can be assigned to phase reference for the selection of
system phase/TOD reference of all PTPMaster ports and PPSoutput ports.
17
Enter:
ED-PHASE::AID::::[SYNCMSG=][,ASSPORTAID=][,PROVQL=][,REFP RIO=];
where:
• AID = Phase Access Identifier, specifies either the phase node for the system phase entity
(delivering the system phase reference PH0) or a phase reference (PPS or Slave Clock port
connected to the phase selection process) to which the command is directed.
Values are:
PHASE-{1-7}-{1-9}-0 (System Phase within a Shelf)
PHASEREF-{1-7}-{1-9}-{0-7} (Source of Phase Reference of a Shelf selectable for System
Phase)
• SYNCMSG = SYNCMSG, determines if the timing reference selection for system phase is
using sync messaging (SSM Qualities) or not.
Values are:
N Sync Messaging is disabled. System phase reference selection is done only by priorities.
Y Sync Messaging is enabled.
System phase reference selection is done by SSM quality levels as first criteria and by
priorities as second criteria.
• ASSPORTAID = ASSPORTAID specifies whether the phase reference is assigned to a port
and if assigned it specifies the AID of the port. The following port types can be used for
establishing a connection towards a timing reference: PPS Input assigned to a phase
reference
Note: The user is able to select the AID of the phase entity to be modified for the Sync
Messaging (SYNMSG) management , specifying if the phase reference selection for
system phase is using sync messaging (SSM Qualities) or not. (Y/N)
18
To configure PTP clock and ports refer to the the CLI command guide.
Note: After the proper configuration of the 1588 port and parameters it is needed to
configure an ELAN service in order to be able to connect the 1588 port with the “bridge”
function needed to forward / receive packets to / from the network.
19
Slave TOD Card deletion
Note: The steps below should be done using the SNMP or CLI commands.
20
The ETS Cross-connection should be deactivated and deleted, refer to the the CLI command
guide.
21
Management Operator Disabling of PTP protocol over PTP logical Master port via setting of
ieee1588PtpPortDSAdminStatus to Disabled value. See CLI Command Guide.
22
If PPSIN has been configured as input for CRU (T0 and/or T4) or for internal Phase Distributor,
it has to be de-provisioned.
Refer to Step 10.
23
The PTP logical Slave/Master port must be disabled at SNMP side. Please refer to the CLI
command guide.
24
The TOD card shall be logically removed.
Enter:
RMV-EQPT::AID;
or
ED-EQPT::AID:OOS;
where:
• AID = PTP-{1-7}-{1-9}-{2-9,12-19,21-36}. Time Of Day - TOD Card
Note: TOD Card logical removal is mandatory also for avoiding traffic hits upon NGI links
of otherCollector cards eventually present in the shelf.
25
Enter:
DLT-EQPT::AID;
where:
• AID = PTP-{1-7}-{1-9}-{2-9,12-19,21-36}. Time Of Day - TOD Card
Result: The command causes the Deactivation/Deletion of PTP Master logical port (both
SNMP and TL1 side), of PPSIN and PPSOUT ports.
END OF STEPS
6.43.2 Prerequisites
None.
6.43.3 General
In this procedure, enter parameter values only for indicated fields. Leave remaining fields blank for
system defaults.
6.43.4 Procedure
1
Enter RTRV-x::AID;
where:
• x=Facility type (GBE10, GBE, ODU2, OTU2, VCG, MAU, BITS, SYNCN, SYNC-OUT)
• AID=Access Identifier of port to be retrieved
2
Examine output for primary state and secondary state values.
3
Select action.
To remove facility from service, go to Step 4.
To restore facility to service, go to Step 6.
4
Remove Facility
Enter RMV-x::AID;
where:
• x=Facility type (GBE10, GBE, ODU2, OTU2, VCG, MAU, BITS, SYNCN, SYNC-OUT)
• AID=Access Identifier of port to be retrieved
5
Go to Step 7.
6
Restore Facility
Enter RST-x::AID:::SWTCHCMD;
where:
• x=Facility type (GBE10, GBE, ODU2, OTU2, VCG, MAU, BITS, SYNCN, SYNC-OUT)
• AID=Access Identifier of port to be retrieved
7
STOP. This procedure is complete.
END OF STEPS
6.44.2 Prerequisites
The personal User Identification (UID) and current PID for the user must be known.
6.44.3 General
ED-PID is used to change a user's own password, and the user must enter the current UID and
PID.
If a PID or UID has been deactivated or removed, only a System Administrator account user can
enter a new PID or UID database entry.
6.44.4 Procedure
WARNING
Optional Content
This command should be done after the first login to the system, i.e. after the first ACT-USER.
Optional Content added above. Please modify as needed.
Enter ED-PID:[TID]:UID:[CTAG]::OLDPID,NEWPID,CONFIRMPID;
where:
• UID: User Identifier, specifies a unique user ID. Valid values for UID are 5 to 12, case-
sensitive alphanumeric characters where the first character must always be an alphabetic
character. The following special characters are also accepted as valid characters and will be
part of the UID: % (percent sign), + (plus sign), # (pound sign), and _ (under score). Possible
values: 5-12 valid UID characters.
• OLDPID: Old Password Identifier, specifies the user's old login password. Possible values:
8-12 valid PID characters.
• NEWPID: New Password Identifier, specifies the user's new login password. Possible values:
8-12 valid PID characters.
• CONFIRMPID: New Password Identifier Confirmation, confirms the user’s new login
password.
Note: The confirmation password (CONFIRMPID) shall be the same as the entered new
password (NEWPID)
2
Did system return a successful response?
If yes, go to Step 5.
If no, go to Step 3.
3
Check error code message.
WARNING
Optional Content
At the first login the user should change the password.
Consider error code message, and then go to Step 1 for another attempt to change password.
5
STOP. This procedure is complete.
END OF STEPS
6.45.2 Prerequisites
For a join to 2WAY operation resulting in one cross connection of CCT=2WAY is the existence of
two cross connections of CCT=1WAY. This two 1WAY cross connections must connect the same
FROM and TO, but in opposite direction.
For a join 2WAYSNCP operation resulting in one cross connection of CCT=2WAYSNCP is the
existence of one cross connection of CCT=1WAYSNCP and two cross connections of CCT=1WAY.
One 1WAY cross connection must connect the TO and FROMPED facilities of the 1WAYSNCP
cross connection. The other 1WAY cross connection must connect the TO and FROMPING facilities
of the 1WAYSNCP cross connection.
6.45.3 General
Join and split
The CNVT-CCJ-<rate> command joins unidirectional cross connections to one bidirectional cross
connection.
The CNVT-CCS-<rate> splits a bidirectional cross connection into unidirectional cross connections.
The CKTID of the new 2WAYSNCP cross connection will be taken over from the previous
1WAYSNCP cross connection if not provided.
When adding a protection leg (FROMPING) it can be specified which role the existing source
(FROM) will take over, the new FROMPING (NEWFROMPING) or the new FROMPED
(NEWFROMPED). One of the NEWFROMPING or NEWFROMPED in the command parameters
must be the FROM of the original unprotected cross connection.
When adding a protection leg the protection state will be new calculated and may lead to a
protection switch.
When deleting a protection leg it can be specified which leg (FROMPING or FROMPED) will be
the new FROM (NEWFROM) of the unprotected cross connection. The NEWFROM parameter
of the command must be one of the FROMPED or FROMPING of the original path protection
cross connection.
Deleting a protection leg may lead to a reconnection of the new FROM and TO depending of the
protection state.
• 2WAY <--> 2WAYSNCP see Figure 25, “ Conversion of 2WAYSNCP <--> 2WAY - adding/
removing a protection leg” (p. 300)
6.45.3 Procedure
1
Select action.
To join unidirectional cross connections to one bidirectional cross connection, go to Step 2.
To split a bidirectional cross connection into unidirectional cross connections, go to Step 8.
To add a protection leg to a cross connection, go to Step 12.
To removes a protection leg from a cross connection, go to Step 16.
To end this procedure, go to Step 18.
2
Join unidirectional cross connections to one bidirectional cross connection
Enter RTRV-CRS::AID:::[RTRVMODE=];
where:
• AID = selected facility(ies) to which the command is directed. AID of ALL retrieves all the
cross connects in the system. Possible values are described in 6.39 “Administer VC Cross-
Connection” (p. 267).
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
3
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
"<FROM>,<TO>:<CTYPE>,<LEVEL>:[CKTID=<value>]
[,CKTIDTF=<value>][,ALTERNATE=<value>][,FROMPING=<value>][,ACD=
<value>]:<PST>[,<SST>]" cr lf]
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
4
Enter CNVT-CCJ-<rate>::TO::::[CKTID=];
where:
• <rate> = crossconnection rate on which the command acts. Possible values: VC4, VC44C,
VC416C, VC464C, LOVC12, LOVC3.
• TO=AID of the TO facility of the cross connection to be converted. In case of a 2WAY cross
connection both ends of the cross connection can be used for addressing. In case of a join to
2WAY conversion the TO of one of the 1WAY involved cross connections must be addressed.
In case of a join to 2WAYSNCP conversion the TO of the 1WAYSNCP cross connection must
be addressed. All other involved cross connections can be calculated and must exist for a
successful acceptance of the command. Possible values are decribed in 6.39 “Administer
VC Cross-Connection” (p. 267).
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
5
Go to Step 1.
6
Split a bidirectional cross connection into unidirectional cross connections
Enter RTRV-CRS::AID:::[RTRVMODE=];
where:
• AID = selected facility(ies) to which the command is directed. AID of ALL retrieves all the
cross connects in the system. Possible values are described in 6.39 “Administer VC Cross-
Connection” (p. 267).
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
7
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
"<FROM>,<TO>:<CTYPE>,<LEVEL>:[CKTID=<value>]
[,CKTIDTF=<value>][,ALTERNATE=<value>][,FROMPING=<value>][,ACD=
<value>]:<PST>[,<SST>]" cr lf]
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
8
Enter CNVT-CCS-<rate>::TO::::[CKTID=];
where:
• <rate> = crossconnection rate on which the command acts. Possible values: VC4, VC44C,
VC416C, VC464C, LOVC12, LOVC3.
• TO=AID of the TO facility of the cross connection to be converted. In case of a 2WAY cross
connection both ends of the cross connection can be used for addressing. Possible values
are decribed in 6.39 “Administer VC Cross-Connection” (p. 267).
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
9
Go to Step 1.
10
Add a protection leg to a cross connection
Enter RTRV-CRS::AID:::[RTRVMODE=];
where:
• AID = selected facility(ies) to which the command is directed. AID of ALL retrieves all the
cross connects in the system. Possible values are described in 6.39 “Administer VC Cross-
Connection” (p. 267).
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
11
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
"<FROM>,<TO>:<CTYPE>,<LEVEL>:[CKTID=<value>]
[,CKTIDTF=<value>][,ALTERNATE=<value>][,FROMPING=<value>][,ACD=
<value>]:<PST>[,<SST>]" cr lf]
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
12
Enter CNVT-CCTPR-<rate>::TO::::NEWFROMPED=,NEWFROMPING= [,RVRTV=][,
RVRTTIM=][,HLDFFTIM=][,PTYPE=];
where:
• <rate> = crossconnection rate on which the command acts. Possible values: VC4, VC44C,
VC416C, VC464C, LOVC12, LOVC3.
• TO=AID of connection point; Indicates the TO (transmit side to the network, sink of cross-
connection) facility of the cross-connection. It addresses the cross connection to be
converted. Possible values are described in 6.39 “Administer VC Cross-Connection”
(p. 267).
• NEWFROMPED=AID of connection point; Indicates the new FROMPING (protecting receive
side from the network, protecting source of cross-connection) facility of the cross-connection.
If the AID is the same as from the FROM facility of the original cross connection, then this
facility gets the role of the new FROMPED. Possible values are described in
6.39 “Administer VC Cross-Connection” (p. 267).
• NEWFROMPING=AID of connection point; Indicates the new FROMPING (protecting receive
side from the network, protecting source of cross-connection) facility of the cross-connection.
If the AID is the same as from the FROM facility of the original cross connection, then this
facility gets the role of the new FROMPING. Possible values are described in
6.39 “Administer VC Cross-Connection” (p. 267).
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
13
Go to Step 1.
14
Remove a protection leg to a cross connection
Enter RTRV-CRS::AID:::[RTRVMODE=];
where:
• AID = selected facility(ies) to which the command is directed. AID of ALL retrieves all the
cross connects in the system. Possible values are described in 6.39 “Administer VC Cross-
Connection” (p. 267).
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
15
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
"<FROM>,<TO>:<CTYPE>,<LEVEL>:[CKTID=<value>]
[,CKTIDTF=<value>][,ALTERNATE=<value>][,FROMPING=<value>][,ACD=
<value>]:<PST>[,<SST>]" cr lf]
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
16
Enter CNVT-CCTU-<rate>::TO::::NEWFROM=;
where:
• <rate> = crossconnection rate on which the command acts. Possible values: VC4, VC44C,
VC416C, VC464C, LOVC12, LOVC3.
• TO=AID of connection point; Indicates the TO (transmit side to the network, sink of cross-
connection) facility of the cross-connection. It addresses the cross connection to be
converted. Possible values are described in 6.39 “Administer VC Cross-Connection”
(p. 267).
• NEWFROM=AID of connection point; Indicates the new FROM of the cross connection. The
AID must be one of the FROMPED or FROMPING of the original cross connection. In case
the cross connection is converted to a cross connection of type 1WAY or 2WAY the
protection leg will be deleted. Possible values are described in 6.39 “Administer VC Cross-
Connection” (p. 267).
17
Go to Step 1.
18
STOP. This procedure is complete.
END OF STEPS
6.46.2 Prerequisites
The UID must be known before it can be deleted.
6.46.3 General
DLT-USER-SECU command deletes user profiles in the User Security Database, for the specified
User Identifier (UID).
Only the security administrator can delete a user profile entry in the User Security Database. In
addition, the default users profiles, so included the vendor user profile, cannot be deleted.
The security administrator can delete both users having unauthenticated session, i.e. logged off
users, and logged on users. The deletion of a logged on user shall log off the target user and delete
him/her.
6.46.4 Procedure
1
Enter DLT-USER-SECU::UID;
where: UID = User Identifier, specifies a unique user ID. Valid values for UID are 5 to 12, case-
sensitive alphanumeric characters where the first character must always be an alphabetic
character. The following special characters are also accepted as valid characters and will be
part of the UID: % (percent sign), + (plus sign), # (pound sign), and _ (under score).
2
STOP. This procedure is complete.
END OF STEPS
6.47.2 Prerequisites
This procedure is service-affecting if any cross-connections are active on the module. All cross-
connections must be deleted. Once cross-connections are deleted, ports associated with the
module must be deprovisioned. Refer to Table 25, “Procedures Required Before Deprovisioning
Modules” (p. 308) for appropriate procedures.
6.47.3 General
The procedure de-assigns and deprovisions the equipment entity specified by the Access Identifier
(AID), even if equipment is not installed into the system. The following equipment can be deleted
from the system:
• Common units:
− EC320
− Lower Order Adaptation Card 10G
− MT320
− MT160
− PSF320 and POW320
− FAN
• SDH units:
− 10GSO (STM-64) card
− 2.5G (STM-16) module
− 8 Port (STM-1)/(STM-4) Card
− G.709 OTU 10GB Card (OT2TDM)
− 10XANY 10GB 10xGBE Card
• Data units:
− MultiService Adaptation Card (Packet Module 10G)
− Packet Module 10x1GbEthernet (Packet Module 10G)
− Packet Module 1x10GbEthernet (Packet Module 10G)
• WDM units:
− Optical Pre-Amplifer 10G
− Optical Booster 10G Line
− Optical Filter and Attenuator (LOFA)
− DWDM Optical Transponder with Colored XFPs
− CWDM Optical Transponder (2.5G) without Optical Protection
6.47.4 Procedure
1
Select action.
“For SDH board” (p. 310) deprovision, go to Step 2.
“For DATA boards” (p. 312) deprovision, go to Step 7.
“For WDM board” (p. 313) deprovision, go to Step 12.
“For common boards” (p. 314) deprovision, go to Step 17.
“For XFP/SFP Module” (p. 314) deprovision, go to Step 19.
2
For SDH board
Enter RTRV-EQPT::AID; to view equipment service states.
where: AID = Equipment Access Identifier, identifies the equipment entity access identifier.
Possible values:
• 10GSO-{1-7}-{1-9}-{2-9,12-19,21-36} as10G Synchronous Optical
• 2G5SO-{1-7}-{1-9}-{2-9,12-19,21-36} as 2.5G Synchronous Optical
• 8XSO-{1-7}-{1-9}-{2-9,12-19,21-36} as 8 x Synchronous Optical
• OT2TDM-{1-7}-{1-9}-{2-9,12-19,21-36} as G.709 OTU 10GB Card (Provisioned Type =
1POTU2)
• 10XANY-{1-7}-{1-9}-{2-9,12-19,21-36} as 10XANY Card
• XFP-{1-7}-{1-9}-{2-9,12-19,21-36}-1 as XFP on 10GSO modules
• SFP-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} as SFP on 8XSO modules
• SFP-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10} as SFP on 10XANY modules
• LOA10G-{1-7}-{1-9}-{21,22,24,33,35,36} as Lower Order Adaptation Card with EPS
3
What is PST and SST of module to delete?
If IS-NR or OOS-AU, go to Step 4.
If OOS-MA or OOS-AUMA, go to Step 5.
If OOS-MA,UAS, module is already deprovisioned. Go to Step 20.
4
Enter RMV-EQPT::AID:::[MODE];
where: AID=Equipment Access Identifier, identifies the equipment entity access identifier, as
decribed in Step 2
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
5
Enter DLT-EQPT::AID;
where: AID=Equipment Access Identifier, identifies the equipment entity access identifier, as
decribed in Step 2
6
Go to Step 20.
7
For DATA boards
Enter RTRV-EQPT::AID; to view equipment service states.
where: AID = Equipment Access Identifier, identifies the equipment entity access identifier.
Possible values:
• PP1GE-{1-7}-{1-9}-{2-9,12-19} as Packet Module 10x1Gb
• PP10GE-{1-7}-{1-9}-{2-9,12-19} as Packet Module 1x10Gb
• PP10AD-{1-7}-{1-9}-{2-9,12-19} as Adaptation Card Packet Modules 10G
• SFP-{1-7}-{1-9}-{2-9,12-19}-{1-10} as SFP on PP10 modules
• XFP-{1-7}-{1-9}-{2-9,12-19}-1 as XFP on PP10GE modules
8
What is PST and SST of module to delete?
If IS-NR or OOS-AU, go to Step 9.
If OOS-MA or OOS-AUMA, go to Step 10.
If OOS-MA,UAS, module is already deprovisioned. Go to Step 20.
9
Enter RMV-EQPT::AID:::[MODE];
where: AID=Equipment Access Identifier, identifies the equipment entity access identifier, as
decribed in Step 7
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
10
Enter DLT-EQPT::AID;
where: AID=Equipment Access Identifier, identifies the equipment entity access identifier, as
decribed in Step 7
11
Go to Step 20.
12
For WDM board
Enter RTRV-EQPT::AID; to view equipment service states.
where: AID = Equipment Access Identifier, identifies the equipment entity access identifier.
Possible values:
• PRE-{1-7}-{1-9}-{2-9,12-19,21-36} as Preamplifier
• BOOST-{1-7}-{1-9}-{2-9,12-19,21-36} as Booster
• LOFA-{1-7}-{1-9}-{6-9,12-15} as Line Optical Filter and Attenuator
• DWLA10X-{1-7}-{1-9}-{2-9,12-19,21-36} as DWDM Optical Transponder
• CWLA-{1-7}-{1-9}-{6-9,12-15} as CWDM Optical Transponder
• CADM-{1-7}-{1-9}-{6,7,8,9,12,13,14,15} as CWDM OADM
• CMDX-{1-7}-{1-9}-{6-9,12-15} as CWDM MUX/DEMUX
• OMDX8-{1-7}-{1-9}-{6-9,12-15} as DWDM MUX/DEMUX 8 channels
• SFP-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4} as SFP on 2G5SO or on CWLA modules
13
What is PST and SST of module to delete?
If IS-NR or OOS-AU, go to Step 14.
If OOS-MA or OOS-AUMA, go to Step 15.
If OOS-MA,UAS, module is already deprovisioned. Go to Step 20.
14
Enter RMV-EQPT::AID:::[MODE];
where: AID=Equipment Access Identifier, identifies the equipment entity access identifier, as
decribed in Step 12
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
15
Enter DLT-EQPT::AID;
where: AID=Equipment Access Identifier, identifies the equipment entity access identifier, as
decribed in Step 12
16
Go to Step 20.
17
WARNING
Optional Content
EC320 in slot 1 (whatever is the EPS status), working EC320 (whatever is the slot), MT320
(MT160 in Tss160 Shelf), TBUS, POW and FAN cannot be deleted.
Optional Content added above. Please modify as needed.
For common boards
Read the following WARNING.
18
Go to Step 20.
19
WARNING
Optional Content
If an unit is deleted, also all related XFP/SFPs are deleted (if present) even if not logically
removed.
Optional Content added above. Please modify as needed.
For XFP/SFP Module
Read the following WARNING.
20
STOP. This procedure is complete.
END OF STEPS
6.48.2 Prerequisites
The user must have administrator privileges to enable/disable a user account.
6.48.3 General
The INH-USER-SECU command is used by a user with administrator privileges to inhibit (disable)
existing users from logging on to the system. The user account is not deleted.
When the INH-USER-SECU command is issued against a logged on user, it logs off and inhibits the
target user unless the logged on user is a security administrator. In that case, the command is
denied.
The ALW-USER-SECU command is used to reinstate users that have been disabled by the INH-
USER-SECU command.
6.48.4 Procedure
1
Select action.
To disable user account, go to Step 2.
To enable user account, go to Step 8.
2
Disable User Account
Enter RTRV-USER-SECU::[UID];
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
3
Observe output. Verify STATE=ACTIVE, as detailed in the relevant command guide, refer to
“Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
(
"<UID>:<UAP>:STATE=<value>,PAGE=<value>,PCND=<value>,PCNN=<value>,
POINT=<value>,PAGEXP=<value>,UOUT=<value>,LOGFAIL=<value>,LAST=
<value>,KAMINTVL=<value>,MININTVL=<value>,MXINV=<value>,TMOUT=
<value>" cr lf)+
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
4
Enter INH-USER-SECU:::::UID;
where: UID=User Identifier of user to disable. Valid values for UID are 5 to 12, case-sensitive
alphanumeric characters where the first character must always be an alphabetic character. The
following special characters are also accepted as valid characters and will be part of the UID: %
(percent sign), + (plus sign), # (pound sign), and _ (under score). ALL All of the users defined
for the system.
5
Enter RTRV-USER-SECU::[UID];
where: UID=User Identifier of user just disabled
6
Observe output. Verify STATE=SUSPENDED, as detailed in the relevant command guide, refer
to “Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
(
"<UID>:<UAP>:STATE=<value>,PAGE=<value>,PCND=<value>,PCNN=<value>,
POINT=<value>,PAGEXP=<value>,UOUT=<value>,LOGFAIL=<value>,LAST=
<value>,KAMINTVL=<value>,MININTVL=<value>,MXINV=<value>,TMOUT=
<value>" cr lf)+
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
7
Go to Step 13.
8
Enable User Account
Enter RTRV-USER-SECU::[UID];
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
9
Observe output. Verify STATE=SUSPENDED, as detailed in the relevant command guide, refer
to “Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
(
"<UID>:<UAP>:STATE=<value>,PAGE=<value>,PCND=<value>,PCNN=<value>,
POINT=<value>,PAGEXP=<value>,UOUT=<value>,LOGFAIL=<value>,LAST=
<value>,KAMINTVL=<value>,MININTVL=<value>,MXINV=<value>,TMOUT=
<value>" cr lf)+
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
10
Enter ALW-USER-SECU:::::UID;
where: UID=User Identifier of user to disable. Valid values for UID are 5 to 12, case-sensitive
alphanumeric characters where the first character must always be an alphabetic character. The
following special characters are also accepted as valid characters and will be part of the UID: %
(percent sign), + (plus sign), # (pound sign), and _ (under score).
11
Enter RTRV-USER-SECU::[UID];
where: UID=User Identifier of user just enabled
12
Observe output. Verify STATE=ACTIVE, as detailed in the relevant command guide, refer to
“Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
(
"<UID>:<UAP>:STATE=<value>,PAGE=<value>,PCND=<value>,PCNN=<value>,
POINT=<value>,PAGEXP=<value>,UOUT=<value>,LOGFAIL=<value>,LAST=
<value>,KAMINTVL=<value>,MININTVL=<value>,MXINV=<value>,TMOUT=
<value>" cr lf)+
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
13
STOP. This procedure is complete.
END OF STEPS
6.49.2 Prerequisites
None.
6.49.3 General
The alarm conditions to be retrieved can be specified by using the input parameters NTFCNCDE
and/or CONDTYPE as the filter, i.e., existing conditions satisfying all the specified input parameters
will be reported in the message response.
The successful response for a RTRV-ALM-ALL command contains one line of parsable output data
for each alarm condition being reported. If multiple alarm conditions exist, a line of output is
provided for each alarm.
Each equipment entity with alarms is grouped by equipment type and displayed in ascending order
of each of the AID fields (excluding the equipment type field) left to right, and in ascending order by
date and time of occurrence.
Each common (no specific entity) alarm is displayed in ascending order by date and time of
occurrence.
Each facility entity with alarms grouped by facility type is displayed in ascending order of each of
the AID fields (excluding the facility type field, if any) left to right, and in ascending order by date
and time of occurrence.
For standing (i.e. non-transient) Threshold Crossing Alerts the Parameters MONVAL, THLEV and
TMPER will be reported. The parameters contain the values which are provided at the time the
condition are raised.
If there are no alarms to report, the system outputs a COMPLD response.
6.49.4 Procedure
1
Select action.
To retrieve all current NE alarms, go to Step 2.
To retrieve equipment alarms, go to Step 5.
To retrieve all BITS alarms, go to Step 8.
To retrieve facility alarms, go to Step 11.
2
Retrieve All NE Alarms
Enter RTRV-ALM-ALL:::::[NTFCNCDE],[CONDTYPE],[SRVEFF],[LOCN], [DIRN]; to
retrieve the current status of all alarms or conditions.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
3
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
"<AID>,<AIDTYPE>:<NTFCNCDE>,<CONDTYPE>,<SRVEFF>,<OCRDAT>,<OCRTM>,
[<LOCN>],[<DIRN>],[<MONVAL>],[<THLEV>],[<TMPER>]" cr lf]*
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
4
Go to Step 14.
5
Retrieve Equipment Alarms
Enter RTRV-ALM-EQPT::AID:::[NTFCNCDE],[CONDTYPE],[SRVEFF], [LOCN]; to
retrieve the current status of any existing, alarm conditions for the specified equipment AID, or
for the specified AID and any alarm conditions matching the specified combination of
position-defined input parameters.
where: AID = Equipment Access Identifier, identifies the equipment entity access identifier.
Possible values:
• EC320-{1-7}-{1-9}-{1,20} for Equipment Controller Card TSS-320
• MT320-{1-7}-{1-9}-{10,11} for Matrix and Timing TSS-320
• MT160-{1-7}-{1-9}-{10,11} for Matrix and Timing TSS-160
• LOA10G-{1-7}-{1-9}-{21,22,24,33,35,36} for Lower Order Adaptation Card with EPS
• PSF320-{1-7}-{1-9}-{37,39} for Power Supply Filter TSS-320
6
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<AID>[,<AIDTYPE>]:<NTFCNCDE>,<CONDTYPE>,<SRVEFF>,<OCRDAT>,<OCRTM>,
<LOCN>" cr lf
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
7
Go to Step 14.
8
Retrieve All BITS Alarms
Enter RTRV-ALM-BITS::AID:::[NTFCNCDE],[CONDTYPE],[SRVEFF]; to retrieve the
current status of specified BITS facilities.
where:
• ALL for all AID
• BITS-{1-7}-{1-9}-{0,1} for Shelf External Timing Input Port
• BITSOUT-{1-7}-{1-9}-0 for Shelf External Timing Output Port
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
9
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<AID>[,<AIDTYPE>]:<NTFCNCDE>,<CONDTYPE>,<SRVEFF>,<OCRDAT>,<OCRTM>"
cr lf
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
10
Go to Step 14.
11
Retrieve Facility Alarms
• x= LOVCN
Values valid for: LOVC12 command modifier
− VCGLOVC12-{1-7}-{1-9}-{2-9,12-19}-{1-124}-{1-63} for LO VC12 within a logical VCG on
a Multiservice Packet Card
− MVC4TU12-{1-7}-{1-9}-{21,22,35,36}-{1-64}-{1-3}-{1-7}-{1-3} for TU12 embedded within a
Modifiable VC4
− PDHLOVC12-{1-7}-{1-9}-{1-6}-{1-42} for VC12 with E1 client on the PDH Port Module of
1646 shelf
− MVC4TU12-{1-7}-{1-9}-{7}-{1-16}-{1-3}- {1-7}-{1-3} for TU12 within a MVC4 on SCC card
on 1646 Drop shelf.
Values valid for: LOVC3 command modifier
− VCGLOVC3-{1-7}-{1-9}-{2-9,12-19}-{1-24}-{1-24} for LO VC3 within a logical VCG on a
Multiservice Packet Card
− MVC4TU3-{1-7}-{1-9}-{21,22,35,36}-{1- 64}-{1-3} for TU3 embedded within a Modifiable
VC4.
− MVC4TU3-{1-7}-{1-9}-{7}-{1-16}-{1-3} for TU3 within a MVC4 on SCC card on 1646 Drop
shelf
• x= MAU
− MAU-{1-7}-{1-9}-{2-9,12-19, 21-36}-{1-10} for MAU port on a 10xAny module
• x= ODU2
− OTODU2-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-{C1, L1}-1 for ODU2 facility in an OTU2
on a DWLA10X module
• x=FC
− FC200-{1-7}-{1-9}-{2-9,12-19, 21-36}-{1,3,5,7,9} for FC200 port on a 10xAny module
− FC400-{1-7}-{1-9}-{2-9,12-19, 21-36}-{3,7} for FC400 port on a 10xAny module
• x= OGPORT
− OGPORT-{1-7}-{1-9}-{6-9,12-15}-{1-4} for Line port on a CWLA module - STM16
• x= OTU2
− OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-L1 for OTU2 Line port, OT2TDM or
DWLA10X module
− OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-C1 for Client port on a DWLA10X module
- OTU2, OC192, STM-64, 10GE
• x= STMN
− STM1-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} for STM1
− STM4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8 } for STM4
− STM16-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4, 5, 7} for STM16 on a 2G5SO or 10xANY
− OGPORT-{1-7}-{1-9}-{6-9,12-15}-{1-4} for Client port on a CWLA module-STM16
− STM64-{1-7}-{1-9}-{2-9,12-19,21-36}-1 for STM64
− OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-C1 for Client port on a DWLA10X module
- OTU2, OC192, STM-64, 10GE
− STM1-{1-7}-{1-9}-{7,8}-{1} for STM1 on Sub-module on SCC of 1646DS
− STM4-{1-7}-{1-9}-{7,8}-{1} for STM4 on Sub-module on SCC of 1646DS
− STM16-{1-7}-{1-9}-{7,8}-{1} for STM16 on Sub-module on SCC of 1646DS
• x= TIMING
− EXTREF-{1-7}-{1-9}-{0,1} for Timing Reference of a Shelf for an External Timing Input Port
− LINEREFSYS-{1-7}-{1-9}-{0-5} for Timing Reference of a Shelf for a Line Port selectable
for System Timing
− LINEREFOUT-{1-7}-{1-9}-{0-5} for Timing Reference of a Shelf for a Line Port selectable
for Output Timing)
− SYNC-{1-7}-{1-9}-0 for Timing Node within a Shelf
• x= TUSEG
− TUSEG-{1-7}-{1-9}-{1-20000} for Tunnel Segment
• x= VCG.
− GBEVCG-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10} for VCG on a GBE port on a 10xAny
module
− VCG-{1-7}-{1-9}-{2-9,12-19}-{1-124} for Logical VCG for ethernet switching on a PP10AD
module
− MAUVCG-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10} for VCG on a MAU port on a 10xAny
module
− FC200VCG-{1-7}-{1-9}-{2-9,12-19, 21-36}-{1,3,5,7,9} for FC200 VCG on a 10xAny
module- 12xVC4
− FC400VCG-{1-7}-{1-9}-{2-9,12-19, 21-36}-{3,7} for FC400 VCG on a 10xAny module -
24xVC4
• x= VCN.
− VCGVC4-{1-7}-{1-9}-{2-9,12-19, 21-36}-{1,3,5,7,9}-{1-12} for VC4 in an FC200 VCG on a
10xAny module- 12xVC4
− VCGVC4-{1-7}-{1-9}-{2-9,12-19, 21-36}-{3,7}-{1-24} for VC4 in an FC400 VCG on a
10xAny module - 24xVC4
− VCGVC4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10}-{1-7} for VC4 within a VCG on a 10xAny
module
− VCGVC4-{1-7}-{1-9}-{2-9,12-19}-{1-64}-{1-64} for VC4 within a logical VCG on a
Multiservice Packet Card
− MVC4-{1-7}-{1-9}-{21,22,35,36}-{1-64} for Modifiable VC4 on LOA card
− STM4AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8}-{1-4} for AU4 embedded within an STM4
− STM16AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4,5,7}-{1-16} for AU4 in an STM16 on a
2G5SO or a 10xANY
− STM64AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-1-{1-64} for AU4 embedded within an STM64
− STM1AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8}-1 for AU4 embedded within an STM1
− STM4AU44C-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8}-1 for AU4-4c embedded within an STM4
− STM16AU44C-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4,5,7}-{1,5,9,13} for AU4-4c in anSTM16
on a 2G5SO or 10xANY
− STM64AU44C-{1-7}-{1-9}-{2-9,12-19,21-36}-1-
{1,5,9,13,17,21,25,29,33,37,41,45,49,53,57,61} for AU4-4c embedded within an STM64
− STM16AU416C-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4,5,7}-1 for AU4-16c in an STM16 on a
2G5PSO or 10xANY
− STM64AU416C-{1-7}-{1-9}-{2-9,12-19,21-36}-1-{1,17,33,49} for AU4-16c embedded
within an STM64
12
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
"<AID>,<AIDTYPE>:<NTFCNCDE>,<CONDTYPE>,<SRVEFF>,<OCRDAT>,<OCRTM>,
<LOCN>,<DIRN>,[<MONVAL>],[<THLEV>],[<TMPER>]" cr lf]*
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
13
Go to Step 14.
14
STOP. This procedure is complete.
END OF STEPS
6.50.2 Prerequisites
The MPLS port (on DATA side) must be already set.
6.50.3 General
The RTRV-MPLSIF command retrieves MPLS Interface parameters (according to RFC3813
mplsInterfaceTable parameters. This table represents the interfaces that are MPLS capable. An
entry is created for every MPLS capable interface on a LSR). MPLS Interface exists if and only if a
corresponding entry in ifTable exists (with ifType = mpls (166)).
6.50.4 Procedure
1
Enter RTRV-MPLSIF::[AID]::::[SHOW-MODE=];
where:
• AID = Optional parameter. Access Identifier, specifies an access to the MPLS interfaces.
Possible values:
− ALL for all AID
− MPLSIF-{1-7}-{1-9}-{2-9, 12-19}-{1-10} for Local MPLS Interface
− MPLSIF-{1-7}-{1-9}-{2-9, 12-19}-{1-128} for VCG MPLS Interface
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
2
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<AID>::MPLSIF-LABEL-MIN-IN=<value>,MPLSIF-LABEL-MAX-IN=<value>,
MPLSIF-LABEL-MIN-OUT=<value>,MPLSIF-LABEL-MAX-OUT=<value>,
MPLSIF-TOTAL-BAND=<value>,MPLSIF-AVAILABLE-BAND=<value>,
MPLSIF-LABEL-PARTICIPATION-TYPE=<value>,MPLSIF-VT-LIST=<value>:<PST>
"cr lf
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
3
STOP. This procedure is complete.
END OF STEPS
6.51.2 Prerequisites
None.
6.51.3 General
The successful response for a RTRV-COND-ALL command contains one line of parsable output
data for each condition being retrieved. If multiple conditions exist, a line of output is provided for
each.
6.51.4 Procedure
1
Select action.
To retrieve all current NE status and conditions, go to Step 2.
To retrieve equipment status and conditions, go to Step 5.
To retrieve all BITS status and conditions, go to Step 8.
To retrieve facility status and conditions, go to Step 11.
To retrieve fast facility protection status and conditions, go to Step 14.
2
Retrieve all NE status and conditions
Enter RTRV-COND-ALL:::::[CONDTYPE],[LOCN],[DIRN]; to retrieve the current status
of any reported existing standing conditions in the system (alarmed and not alarmed for
Equipment, Facility, and Common AIDs) or any standing conditions matching the specified
combination of position-defined input parameters.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
3
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
"<AID>,<AIDTYPE>:<NTFCNCDE>,<CONDTYPE>,<SRVEFF>,<OCRDAT>,<OCRTM>,
<LOCN>,<DIRN>,[<MONVAL>],[<THLEV>],[<TMPER>]" cr lf]*
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
4
Go to Step 19.
5
Retrieve Equipment status and conditions
Enter RTRV-COND-EQPT::AID:::[CONDTYPE],[LOCN]; to retrieve the current status of
any existing, standing conditions, for the specified equipment AID, in the system (alarmed, not
alarmed, or not reported) or any standing common conditions, for the specified equipment AID,
matching the specified combination of position-defined input parameters.
Where:
• AID = Equipment Access Identifier, identifies the equipment entity access identifier. Refer to
A.2 “Access Identifiers” (p. 611) for details on parameter values.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
6
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<AID>[,<AIDTYPE>]:<NTFCNCDE>,<CONDTYPE>,<SRVEFF>,<OCRDAT>,<OCRTM>,
<LOCN>" cr lf
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
7
Go to Step 19.
8
Retrieve All BITS status and conditions
Enter RTRV-COND-BITS::AID::[CONDTYPE]; to retrieve the current status of any reported
alarmed, not alarmed or not reported standing conditions, for the specified BITS AID, matching
the specified combination of position-defined input parameters.
where:
• AID = BITS Access Identifier, specifies the selected BITS. Possible values:
− ALL (ALL AID)
− BITS-{1-7}-{1-9}-{0,1} Shelf External Timing Input Port
− BITSOUT-{1-7}-{1-9}-0 Shelf External Timing Output Port
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
9
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<AID>[,<AIDTYPE>]:<NTFCNCDE>,<CONDTYPE>,<SRVEFF>,<OCRDAT>,<OCRTM>"
cr lf
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
10
Go to Step 19.
11
Retrieve Facility status and conditions
Enter RTRV-COND-x::AID::[CONDTYPE],[LOCN],[DIRN]; to retrieve the current status
of any reported alarmed, not alarmed, or not reported standing conditions, for the specified AID,
matching the specified combination of position-defined input parameters. All existing conditions
may be retrieved with the RTRV-<x> command. The command is completed regardless of
whether the <x> is provisioned.
where:
• x= GBE, GBE10, MAU, ODU2, OGPORT, OTU2, TIMING, TUSEG, VCG, VCGVC4,MAU,
FC200, FC400, FC200VCG, FC400VCG, LOVCN, STMn/OCn, VCn/STSn
• AID = Access Identifier, specifies the <x> facility. Refer to A.2 “Access Identifiers” (p. 611) for
details on parameter values.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
12
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
"<AID>,<AIDTYPE>:<NTFCNCDE>,<CONDTYPE>,<SRVEFF>,<OCRDAT>,<OCRTM>,
<LOCN>,<DIRN>,[<MONVAL>],[<THLEV>],[<TMPER>]" cr lf]*
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
13
Go to Step 19.
14
Retrieve fast facility protection status and conditions
Enter RTRV-COND-FFP::AID::[CONDTYPE]; to retrieve the current status of any reported
alarmed, not alarmed, or not reported standing conditions, for the specified FFP AID, matching
the specified combination of position-defined input parameters. The command is completed
regardless of whether the FFP is provisioned.
where:
• AID = FFP Access Identifier, specifies the FFP facility in the FFP<x>-Rack-Shelf-Slot-Module
format where x = STM1, STM4, STM16, STM64, TUNNEL Possible values:
− ALL for all AID
− FFPSTM64-{1-7}-{1-9}-{2-9,12-19,21-36}-1 for STM64 Facility Protection Group
− FFPSTM16-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4} for STM16 Facility Protection Group on a
2G5SO or 10xANY
− FFPSTM4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} for STM4 Facility Protection Group
− FFPSTM1-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} for STM1 Facility Protection Group
− FFPTUNNEL-{1-7}-{1-9}{1-4000} for TMPLS TUNNEL Protection Group
− FFPOC192-{1-7}-{1-9}-{2-9,12-19,21-36}-1 for OC192 Facility Protection Group
− FFPOC48-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4, 5, 7} for OC48 Facility Protection Group on
a 2G5SO or 10XANY
− FFPOC12-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} for OC12 Facility Protection Group
− FFPOC3-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} (OC3 Facility Protection Group)
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
15
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<AID>[,<AIDTYPE>]:<NTFCNCDE>,<CONDTYPE>,<SRVEFF>,<OCRDAT>,<OCRTM>[,
<DIRN>]" cr lf
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
16
Go to Step 19.
17
Retrieve conditions log file of the NE.
Enter RTRV-COND-LOG::[AIDTYPE]:::[EVENTYPE]: [FROMDATE=,FROMTIME=],
[TODATE=,TOTIME=]; to retrieve the alarmed or not-alarmed events available in the
conditions log file of the NE. The retrieved data can be filtered on any combination of the
following input parameter: an interval of dates and times, specific AID type, alarm events,
non-alarmed events.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
18
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
"<AID>,<AIDTYPE>:<NTFCNCDE>,<CONDTYPE>,<SRVEFF>,<OCRDAT>,<OCRTM>,
<LOCN>,<DIRN>,[<MONVAL>],[<THLEV>],[<TMPER>]" cr lf]*
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
19
STOP. This procedure is complete.
END OF STEPS
6.52.2 Prerequisites
The user must have administrator privileges to edit a user profile.
6.52.3 General
The ED-USER-SECU command allows a user with administrator privileges to edit the existing user
profile entry, in the User Security Database. The command is denied if the user identified by the
specified UID is currently logged in. The changes take affect immediately.
6.52.4 Procedure
1
Enter RTRV-USER-SECU::[UID];
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
2
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
(
"<UID>:<UAP>:STATE=<value>,PAGE=<value>,PCND=<value>,PCNN=<value>,
POINT=<value>,PAGEXP=<value>,UOUT=<value>,LOGFAIL=<value>,LAST=
<value>,KAMINTVL=<value>,MININTVL=<value>,MXINV=<value>,TMOUT=
<value>" cr lf)+
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
3
Enter RTRV-STATUS;
4
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
(
":<SESSION>,[<UID>]:ADDR=<value>[,LAST=<value>]" cr lf)+
[
/*
<Command
Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
5
Is user to edit logged in?
If yes, user profile cannot be edited. Go to Step 9.
If no, go to Step 6.
6
Enter ED-USER-SECU::UID:::[NEWUID],[NEWPID,CONFIRMPID],,[UAP]:[PAGE=]
[,PCND=][,PCNN=][,POINT=][,UOUT=];
where: UID=User Identifier, specifies a unique user ID. Valid values for UID are <5-12 VALID
UID CHARACTERS>, case-sensitive alphanumeric characters where the first character must
always be an alphabetic character. The following special characters are also accepted as valid
characters and will be part of the UID: % (percent sign), + (plus sign), # (pound sign), and _
(under score).
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
7
Enter RTRV-USER-SECU::[UID];
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
8
Observe output. Verify changes to user profile. All changes to the provisioned values take effect
immediately except for the PID parameter, which takes effect only on the next login for that
user.
9
STOP. This procedure is complete.
END OF STEPS
6.53.2 General
The NE is able to receive and process eight (8) separate customer-defined inputs for fault
conditions arising externally to the NE.
The fault conditions is processed and reported as for internally detected fault conditions. It is
possible to disable the reporting from any input if not used.
Each user alarm input is separately configurable to accept either a closed circuit or open circuit
state as the active alarm condition.
The inputs from the dry contacts are normally used for ”site specific” alarms such as open door,
high temperature, high water level, etc.
The polarity of an external input control determines the relationship between the declaration of an
environmental condition and the physical signal.
6.53.4 Procedure
Select action.
• To retrieve housekeeping alarm information, go to Step 2.
• To retrieve housekeeping alarm condition, go to Step 4.
• To retrieve housekeeping alarm attribute, go to Step 6.
• To set housekeeping alarm attribute, go to Step 8.
2
Retrieve housekeeping alarm information
It retrieves the current state of any existing environmental alarm condition on one external input
point or on all external input points.
Enter
RTRV-ALM-ENV::AID;
where:
• AID = Access Identifier, identifies the entity access identifier.
Possible values:
CPI-{1-7}-{1-9}-1-{1-8} in the Rack-Shelf-Slot-External Input Point format.
ALL
3
Examine output for notification code, alarm type, occurence date/time and alarm,
where:
• NTFCNCDE specifies the notification code for the specified alarm type.
Values are:
− CR critical alarm
− MJ major alarm
− MN minor alarm
− WR warning alarm ALMTYPE
• ALMTYPE specifies the alarm type. Alarm type identifies the type of alarm as provisioned by
SET-ATTR-ENV.
• ALMMSG identifies the alarm message, i.e. the text message associated with the
environmental alarm as set by the SET-ATTR-ENV command.
4
Retrieve housekeeping alarm condition
It retrieves the current status of any existing, standing, housekeeping conditions in the system
(alarmed, not alarmed, or not reported).
Enter:
RTRV-COND-ENV::AID;
where:
• AID = Access Identifier, identifies the entity access identifier.
Possible values:
CPI-{1-7}-{1-9}-1-{1-8} in the Rack-Shelf-Slot-External Input Point format.
ALL
5
Examine output:
where:
• NTFCNCDE identifies the type of alarm generated by the system upon occurrence of the event
identified by the CONDTYPE.
Values are:
− CR critical alarm
− MJ major alarm
− MN minor alarm
− WR warning alarm ALMTYPE
− NA Not Alarmed
− NR Not Reported
• ALMTYPE specifies the alarm type. Alarm type identifies the type of alarm as provisioned by
SET-ATTR-ENV.
• ALMMSG identifies the alarm message, i.e. the text message associated with the
environmental alarm as set by the SET-ATTR-ENV command.
6
Retrieve housekeeping alarm attribute
It retrieves the attributes associated with an environmental alarm. These attributes are included
when an environmental alarm is reported or retrieved.
Enter:
RTRV-ATTR-ENV::AID;
where:
• AID = Access Identifier, identifies the entity access identifier.
Possible values: CPI-{1-7}-{1-9}-1-{1-8} in the Rack-Shelf-Slot-External Input Point format.
7
Examine output:
where:
• NTFCNCDENoTiFiCatioNCoDE. Determines the severity of the alarm type.
Values are:
− CR critical alarm
− MJ major alarm
− MN minor alarm
− WR warning alarm ALMTYPE
− NA Not Alarmed
− NR Not Reported
• ALMTYPE specifies the alarm type. Alarm type identifies the type of alarm as provisioned by
SET-ATTR-ENV.
• ALMMSG identifies the alarm message, i.e. the text message associated with the
environmental alarm as set by the SET-ATTR-ENV command.
• Polarity. Determine when the external control is active. Values are: AHIGH Active high
ALOW Active low
8
Set housekeeping alarm attribute
To define on the input external-control points, an environment alarm type, a corresponding
alarm message text, and a polarity, enter:
SET-ATTR-ENV::AID:::[NTFCNCDE],[ALMTYPE],[ALMMSG],[POLARITY];
where:
• AID = Access Identifier, identifies the entity access identifier.
Possible values: CPI-{1-7}-{1-9}-1-{1-8} in the Rack-Shelf-Slot-External Input Point format.
• NTFCNCDE = NoTiFiCatioN CoDE, specifies the notification code for the specified alarm
type. Possible values: CR or MJ or MN or WR or NA or NR. Default value: NR.
• ALMTYPE = Alarm Type. Valid characters are uppercase letters ([A..Z]), digits ([0..9]) and the
“-" (dash). In addition, the first character must be a letter. Possible values: <0-10 VALID
CHARACTERS>. Default value: previously existing value.
• ALMMSG = Alarm Message. A text string that can be used to describe what the external
input point detects. Factory default is a null string. Possible values: <0-30 CHARACTERS>.
Default value: previously existing value.
• POLARITY = Determines the polarity of the external input point. Possible values: AHIGH
(Active High) or ALOW (Active Low). Default value: previously existing value.
END OF STEPS
6.54.2 General
Operating an external control means that a relay is activated to control some external device.
SET-ATTR-CONT instructs an NE to set the attributes associated with an external control. These
attributes are used when an external control is operated or released. The related input command is
RTRV-ATTR-CONT.
Releasing an external control means deactivating the relay.
In case of the automatic operation, a ConditionType and the associated AID can be configured
which shall trigger the operation of the related contact pair. If the related alarm condition (instance)
is present, then the output will be operated. If the related alarm condition (instance) is cleared, then
the output will be released.
Only the standing ConditionType are considered as possible trigger for CPO automatic option.
A change from the manual to the automatic operation mode can only be executed if the operational
state is released. If the operational state is OPER then the RLS-EXT-CONT command must be
executed prior. The change from automatic to manual operation is always possible - if the
operational state was OPER before the execution of this command then the operational state is set
to its default value implicitly.
OPR-EXT-CONT instructs an NE to operate an external control, such as a relay activation. The
related contact pair is operated continuously.
6.54.3 Procedure
Select action.
• To retrieve housekeeping control information, go to Step 2.
• To retrieve housekeeping control attribute, go to Step 3.
• To set housekeeping control attribute, go to Step 4.
• To operate housekeeping control, go to Step 5.
• To release housekeeping control, go to Step 6.
2
Retrieve housekeeping control information
Enter:
RTRV-EXT-CONT::AID;
where:
AID = CPO-{1-7}-{1-9}-1-{1-4}. Access IDentifier of the external control output points.
Result: Examine the output:
Verify the external control output point:
3
Retrieve housekeeping control attribute
Enter:
RTRV-ATTR-CONT::AID;
where:
AID = Access IDentifier of the external control output points.
CONTTYPE = Control Type.
CONTSTATE = Control State. Identifies if the external control is in the operated state or not.
Values are:
• RLS Released
• OPER Operated
Values are:
• AHIGH Active high
• ALOW Active low
4
Set housekeeping control attribute
To define an external control name, and its polarity, enter:
SET-ATTR-CONT::AID:::[CONTTYPE],[POLARITY]:[OPMODE=][,SEL CONDTYPE=][,
SELAID=];
where:
• AID = Access IDentifier of the external control output point.
AID = CPO-{1-7}-{1-9}-1-{1-4} i.e. External Control Point.
• Polarity = Determines the polarity of the external control output point. Factory Default is
ALOW.
For parameter descriptions of TL1 commands used in this procedure, refer to the
1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1
Command Guide.
5
Operate housekeeping control
The user can de/activate output external-control points.
Enter:
OPR-EXT-CONT::AID;
where:
AID = Access IDentifier of the external control output points.
6
Release housekeeping control
Enter:
RLS-EXT-CONT::AID;
where:
AID = Access IDentifier of the external control output points.
END OF STEPS
6.55.2 Prerequisites
None.
6.55.3 General
This procedure is used to cold start, warm start, and power-on start the processor-based modules
provisioned and installed in the system.
There are three levels of initialization, as defined by the PHASE parameter value:
1. WARM: reload of dynamic data only (db in RAM). It is supported only by MT320/MT160.
2. COLD: reload of dynamic and static data (db and sw). It is supported by MT320/MT160, EC320,
IOC. For IOCs cold restart implies FPGA reloading and may be traffic affecting if the module is
providing service.
3. POWER-ON: full restart (as if unplugged and plugged), including reloading of processor, sw, db
and matrix reinitialization. It is supported only by MT320/MT160, by Packets Processor Car and
it may be traffic affecting..
The procedure can be applied to the following provisioned and equipped modules or the entire NE.
• EC320
• Lower Order Adaptation Card 10G
• MT320
• MT160
• 10GSO (STM-64) card
• 2.5G (STM-16) module
• 8 Port (STM-1)/(STM-4) Card
• G.709 OTU 10GB Card (OT2TDM)
Shelf Types
• UNVRSL320 (Generic 320 type shelf)
• UNVRSL160 (Generic 160 type shelf)
• ALL (MT320/MT160 and all the boards equipped in the NE)
6.55.4 Procedure
1
Select action.
To initialize an individual module, go to Step 2.
To initialize system, go to Step 4.
2
Initialize an Individual Module
Enter INIT-SYS::AID:::PHASE,[MODE];
where:
• AID=Access identifier of equipment entity. Possible values:
− ALL for all equipped board in the NE
− SHELF-{1-7}-{1-9} for Shelf
− EC320-{1-7}-{1-9}-{1,20} for Equipment Controller Card TSS-320
− MT320-{1-7}-{1-9}-{10,11} for Matrix and Timing TSS-320
− MT160-{1-7}-{1-9}-{10,11} for Matrix and Timing TSS-160
− 10GSO-{1-7}-{1-9}-{2-9,12-19,21-36} for 10G Synchronous Optical
− 2G5SO-{1-7}-{1-9}-{2-9,12-19,21-36} for 2.5G Synchronous Optical
− 8XSO-{1-7}-{1-9}-{2-9,12-19,21-36} for 8 x Synchronous Optical
− OT2TDM-{1-7}-{1-9}-{2-9,12-19,21-36} for G.709 OTU 10GB Card - Provisioned Type =
1POTU2
− 10XANY-{1-7}-{1-9}-{2-9,12-19,21-36} for 10XANY Card
− LOA10G-{1-7}-{1-9}-{21,22,24,33,35,36} for Lower Order Adaptation Card with EPS
− PRE-{1-7}-{1-9}-{2-9,12-19,21-36} for Preamplifier
− BOOST-{1-7}-{1-9}-{2-9,12-19,21-36} for Booster
− LOFA-{1-7}-{1-9}-{6-9,12-15} for Line Optical Filter and Attenuator
− DWLA10X-{1-7}-{1-9}-{2-9,12-19,21-36} for DWDM Optical Transponder
− CWLA-{1-7}-{1-9}-{6-9,12-15} for CWDM Optical Transponder
− CADM-{1-7}-{1-9}-{6,7,8,9,12,13,14,15} for CWDM OADM
− CMDX-{1-7}-{1-9}-{6-9,12-15} for CWDM MUX/DEMUX
− OMDX8-{1-7}-{1-9}-{6-9,12-15} for DWDM MUX/DEMUX 8 channels
− PP10AD-{1-7}-{1-9}-{2-9,12-19} for Adaptation Card Packet Modules 10G
− PP1GE-{1-7}-{1-9}-{2-9,12-19} for Packet Module 10x1Gb
− PP10GE-{1-7}-{1-9}-{2-9,12-19} for Packet Module 1x10Gb
• PHASE = identifies the type of restart. Possible values:
− WARM: reload of dynamic data only (db in RAM).
− COLD: reload of dynamic and static data (db and sw). It is supported by MT320/MT160,
EC320, IOC. It is used with AID=ALL for normal full reset of the NE (cold restart of EC320
followed by cold restart of MT320/MT160).
− POWER-ON: full restart (as if unplugged and plugged), including processor restart and
reloading sw and db. It is supported by MT320/MT160. It is used with AID=ALL for
power-on full reset of the NE (cold restart of EC320, power-on restart of MT320/MT160,
cold restart of IOCs).
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
3
Go to Step 5.
4
Initialize System
Enter INIT-SYS::ALL:::PHASE,FRCD;
where:
• PHASE = identifies the type of restart. Possible values above described.
• FRCD = Forced. The command is completed even if the result of its execution is service-
affecting.
5
STOP. This procedure is complete.
END OF STEPS
6.56.2 Prerequisites
None.
6.56.3 General
The procedure monitors the Link Capacity Adjustment Scheme (LCAS) protocol. This procedure
can be performed on any equipment providing virtual concatenation with LCAS functionality.
The monitoring action can be performed regardless of whether the LCAS protocol is enabled or
disabled.
The successful response for a MON-LCAS command contains multiple lines of parsable output
data.
The first line contains information pertaining to the overall virtual concatenation group level followed
by one line each for information regarding each member the Virtual Concatenation group, in the
ascending order of the channel number within the VCG (from 1 to MAXMBR).
The information pertaining to the overall VCG consists of following parameters: WRKTXCHNUM,
WRKRXCHNUM, MSTCHREF, CHFRDIFFDLY, RSACKTX, RSACKRX.
The information pertaining to the each channel in the VCG consists of following parameters:
CHNUM, CTRLPKTTX, CTRLPKTRX, DIFFDLYRX, SQNUMTX, SQNUMRX, CHNSTATETX,
CHNSTATERX.
6.56.4 Procedure
1
Enter MON-LCAS::AID:;
where: AID=VCG Access Identifier, specifies the VCG entity. Possible values:
• VCG-{1-7}-{1-9}-{2,4,6,8,12,14,16,18}-{1-2}-{1-124} for Logical VCG for ethernet switching on
a PP20G module
• GBEVCG-{1-7}-{1-9}-{2-9,12-19,21-36}- {1-10} for VCG on a GBE port on a 10xAny module
• MAUVCG-{1-7}-{1-9}-{2-9,12-19,21-36}- {1-10} for VCG on a MAU port on a 10xAny module)
• FC200VCG-{1-7}-{1-9}-{2-9,12-19, 21-36}-{1,3,5,7,9} for FC200 VCG on a 10xAny module-
12xVC4 )
• FC400VCG-{1-7}-{1-9}-{2-9,12-19, 21-36}-{3,7} for FC400 VCG on a 10xAny module -
24xVC4)
2
Examine output as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
/*
<Informational_Description_Text>
*/ cr lf]
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
3
STOP. This procedure is complete.
END OF STEPS
6.57.2 Prerequisites
The User Identifier (UID) and current Password Identifier (PID) must be known before login can be
accomplished.
6.57.3 General
To access the system via telnet (either with or without the EMA), port 3083 must be used. To access
the system via TCP/IP, port 3082 must be used.
ACT-USER is used to establish a session with the system and log in the specified user.
For system security, the screen displays asterisks (******) in place of the characters entered for the
password. In-progress response messages are not displayed.
A user cannot log in (using ACT-USER) on a terminal where another user is already logged in.
If a user's PID or UID has been deactivated or removed, only a System Administrator account user
can enter a new user password or user account database entry.
6.57.4 Procedure
1
At login prompt, enter ACT-USER:[TID]:UID[,OMSID]:[CTAG]::PID:[HOSTIP=];
where:
• UID = User Identifier, specifies a unique user ID. Valid values for UID are <5-12 VALID UID
CHARACTERS>, case-sensitive alphanumeric characters where the first character must
always be an alphabetic character. The following special characters are also accepted as
valid characters and will be part of the UID: % (percent sign), + (plus sign), # (pound sign),
and _ (under score).
• OMSID is the 1350 OMS operator name and is entered when the command is entered by
EMS ZIC. Valid values for OMSID are an <Alphanumeric string>.
• PID = Password Identifier, specifies the user's login password. Valid values for PID are a
string of <8-12 VALID PID CHARACTERS> case-sensitive alphanumeric characters. The PID
must contain at least three of the following: at least one upper alphabetic character, at least
one lower alphabetic character, at least one numeric character, at least one special character.
The following special characters shall be valid: % (percent sign), + (plus sign), # (pound
sign), and _ (under score). The first character of the PID can be an alphabetic, numeric, or a
valid special character.
• HOSTIP = IP address of the PC hosting the Web Browser for ZIC GUI application. Valid
2
Did system return a successful response?
If no, go to Step 3.
If yes, go to Step 4.
3
System returns error code when current logged-in user enters ACT-USER command. Refer to
A.4 “Codes” (p. 629) in this manual for complete list of error codes and definitions. For security
purposes, system does not return error code when user who is not logged into system enters
unsuccessful ACT-USER command.
Several unsuccessful attempts to log in can cause terminal lockout.
Check parameters for spelling and case-sensitive characters. Go to Step 1 to retry system
login.
4
STOP. This procedure is complete.
END OF STEPS
6.58.2 Prerequisites
None
6.58.3 General
A user can log only their own active User Identification (UID) out of the system. A System
Administrator can log any other user out of the system.
The CANC-USER command unauthenticates a session with the addressed NE (identified by
optional TID parameter)., whether or not that session was previously authenticated by an ACT-
USER command, by logging off the user.
This command is allowed to log-off only the user that issues the command itself and cannot log-off
another user. The log-off of another user is up to users with security administration privileges and it
is realized by means of the CANC-USER-SECU command,
6.58.4 Procedure
1
Select action.
where:
To log out own User Identification (UID), go to Step 2.
To log out other User Identification (UID), go to Step 4.
2
Log Out Own UID
Enter CANC-USER::[UID]:;
where UID = User Identifier, specifies a unique user ID. Valid values for UID are <5-12 VALID
UID CHARACTERS>, case-sensitive alphanumeric characters where the first character must
always be an alphabetic character. The following special characters are also accepted as valid
characters and will be part of the UID: % (percent sign), + (plus sign), # (pound sign), and _
(under score).
3
Go to Step 5. Log Out Other UID
4
Enter CANC-USER-SECU::UID;
where UID = User Identifier, specifies a unique user ID. Valid values for UID are <5-12 VALID
UID CHARACTERS>, case-sensitive alphanumeric characters where the first character must
always be an alphabetic character. The following special characters are also accepted as valid
characters and will be part of the UID: % (percent sign), + (plus sign), # (pound sign), and _
(under score).
5
Observe output.
6
Did system return a successful response?
If yes, go to Step 10.
If no, go to Step 7.
7
Check error code message. Does error code indicate invalid input parameters?
If yes, check input and spelling. Go to Step 4 to retry command.
If no, go to Step 8.
8
Check error code message. Does error code indicate requested operation failed?
If yes, go to Step 4 to retry command.
If no, go to “” (p. 356) to determine next command to execute.
Find appropriate command in this manual or refer to “Command details” (p. 107).
9
Go to Step 10.
10
STOP. This procedure is complete.
END OF STEPS
6.59.2 General
The system supports 1588 clock synchronization for synchronizing equipment clocks across a
service as per IEEE1588 recommendation.
The System supports the Best master clock selection algorithm to provide protection according
IEEE 1588 recommendation.
The purpose of Time of Day feature is to distribute a local 1 second period time of day signal to
other clocks in the network.
The system supports a dedicated card in order to support 1588v2 and Time Of Day management
(TOD card).
The card provides 1 input/output interface providing 1 PPS and TOD signals.
The system provides provisioning of offset value for PPS input/output interface; the configured
value is an estimation for compensating the delay due to the cable length.
PPS input/output interface is supported by a physical interface constituted by a DB9 connector on
the front panel of the TOD Card
PPS monitor output interface transmits 1PPS (1 Pulse Per Second) signal
PPS monitor input interface manages input 1PPS (1 Pulse Per Second) signal.
Note: TOD information via 1588 PTP and TOD information via NTP are managed in parallel
by the Node, since they're used by separate applications which are not in conflict.
The Master clock supports maximum 1000 PTP slave clocks (target).
When one card operates in Master mode and the Master 1588 logical port is configured, the system
allows the user to configure Master 1588 logical master port as:
• VPLS UNI port inside each VPLS Instance;
• Provider Bridge UNI via provisioning of a specific S-VLAN [Range 1..4094] for Master 1588
logical port.
6.59.4 Procedure
Select action
• Master TOD Card Creation, go to Step 2
• Phase Synchronization reference configuration, go to Step 11
• Master TOD Card Deletion, go to Step 14.
2
Master TOD Card Creation
Enter:
ENT-EQPT::AID::::PROVISIONEDTYPE=PP1588, CKMODE=MASTER;
where:
• AID = PTP-{1-7}-{1-9}-{2-9,12-19,21-36}. Time Of Day - TOD Card
• CKMODE=MASTER means that the PP1588 card is configured in Master Clock
Configuration.
Result:
3
Check the card InService state.
Enter:
RTRV-PTPMASTER::[AID];
where:
AID = PTPMASTER-{1-7}-{1-9}-{2-9, 12-19, 21-36}-1
4
Select action:
manage PPS-IN port facility, go to Step 5
manage PPS-OUT port facility, go to Step 8
manage PTP Master port facility, go to Step 10
5
For PPS-IN port the facility PPSIN-r-s-b-1 is created and the following parameters can be
provisioned:
ED-PPSIN::AID::::[CMDMDE=][,TOD=][,DLY=][,ALMPROF=]:[PST];
where:
• AID = PPSIN-{1-7}-{1-9}-{2-9, 12-19, 21-36}-1 (Pulse Per Second Input Port).
PPSIN Access Identifier, specifies the input port receiving the PPS signal
• TOD= Time Of Day, determines if the information about Time Of Day shall be expected as
input (i. e. Sink direction) or sent as output (i. e. Source direction). Values are:
Y Yes. Time Of Day info is expected/sent.
N No. Time Of Day info is not expected/sent.
• DLY = Delay, indicates the delay to be considered by IEEE1588v2 protocol for
synchronization. The delay is due to the length of the cable on the link. The length
determines a propagation delay equal to D [ns], where D is the value to be provisioned. The
parameter applies to the receiver; normally positive values shall be provisioned; but negative
values can be provisioned as well for compensating excessive delays provisioned at the
other side transmitter. The unit of measure is nanosecond.
6
Enter:
RTRV-PPSIN::[AID];
The RTRV-PPSIN command retrieves the provisioning and state information of one or more
ports, in the 1588v2 application, dedicated to the reception of the PPS signal.
Result: The successful response for a RTRV-PPSIN command contains one or more lines of
parsable output data, in ascending order, listing the possible timing input ports used by the
system.
7
Each timing reference can be assigned (i.e. connected) to a port. The PPS IN port (i.e. line
timing reference) can be assigned to a timing reference.
8
For PPS-OUT the facility PPSOUT-r-s-b-1 is created and the following parameters can be
provisioned
ED-PPSOUT::AID::::[S1TRANS=][,TOD=][,DLY=];
where:
• AID = PPSOUT-{1-7}-{1-9}-{2-9, 12-19, 21-36}-1 (Pulse Per Second Output Port)
I.e. Access Identifier, specifies the output port transmitting the PPS signal.
• S1TRANS = {ACT, PRC, SSUL, SSUT, SEC, DUS, NONE}.
Sync message byte to be transmitted, determines if the transmitted byte will have the "DUS"
message or will have the actual traceability of the signal.
• TOD= Time Of Day, determines if the information about Time Of Day shall be expected as
input (i. e. Sink direction) or sent as output (i. e. Source direction). Values are:
Y Yes. Time Of Day info is expected/sent.
N No. Time Of Day info is not expected/sent.
• DLY = Delay, indicates the delay to be considered by IEEE1588v2 protocol for
synchronization. The delay is due to the length of the cable on the link. The length
determines a propagation delay equal to D [ns], where D is the value to be provisioned. The
parameter applies to the receiver; normally positive values shall be provisioned; but negative
values can be provisioned as well for compensating excessive delays provisioned at the
other side transmitter. The unit of measure is nanosecond.
9
Enter:
RTRV-PPSOUT::[AID]:;
To retrieve the provisioning and state information of one or more ports, in the 1588v2
application, dedicated to the transmission of the PPS signal.
Result: The successful response for a RTRV-PPSOUT command contains one or more lines
of parsable output data, in ascending order, listing the possible timing output ports used by
the system.
10
For master clock the facility PTPMaster-r-s-b-2 is created and it can be retrieved entering:
RTRV-PTPMASTER::[AID];
where:
AID = PTPMASTER-{1-7}-{1-9}-{2-9, 12-19, 21-36}-1 i.e. PTP 1588 Master Clock Port) or ALL
AID = Access Identifier, specifies ALL AID or AID of the PTP1588 Master Clock Port.
Result: The RTRV-PTPMASTER command retrieves the state information of one or more
ports, in the 1588v2 application.
The command is executed regardless of the state of the Master port.
The successful response for a RTRV-PTPMASTER command contains one or more lines of
parsable output data, in ascending order (from lowest specified PTPMASTER AID to the largest
specified PTPMASTER AID), for each PTPMASTER AID specified.
11
The Phase configuration applies either to input and output direction.
Provide phase distribution from ToD signal info or from the input PPS interface.
12
Enter:
ED-PHASE::AID::::[SYNCMSG=][,ASSPORTAID=][,PROVQL=][,REFP RIO=];
where:
• AID = Phase Access Identifier, specifies either the phase node for the system phase entity
(delivering the system phase reference PH0) or a phase reference (PPS or Slave Clock port
connected to the phase selection process) to which the command is directed.
Values are:
PHASE-{1-7}-{1-9}-0 (System Phase within a Shelf)
PHASEREF-{1-7}-{1-9}-{0-7} (Source of Phase Reference of a Shelf selectable for System
Phase)
• SYNCMSG = SYNCMSG, determines if the timing reference selection for system phase is
using sync messaging (SSM Qualities) or not.
Values are:
N Sync Messaging is disabled. System phase reference selection is done only by priorities.
Y Sync Messaging is enabled.
System phase reference selection is done by SSM quality levels as first criteria and by
priorities as second criteria.
• ASSPORTAID = ASSPORTAID specifies whether the phase reference is assigned to a port
and if assigned it specifies the AID of the port. The following port types can be used for
establishing a connection towards a timing reference: PPS Input assigned to a phase
reference
Note: The user is able to select the AID of the phase entity to be modified for the Sync
Messaging (SYNMSG) management , specifying if the phase reference selection for
system phase is using sync messaging (SSM Qualities) or not. (Y/N)
13
To configure PTP clock and ports refer to the 1850 Transport Service Switch (TSS-320, TSS-
320H and TSS-160) Release 5.1 Command Line Interface Guide.
Note: After the proper configuration of the 1588 port and parameters configure an ELAN
service to connect the 1588 port with the ‘bridge’ function needed to forward / receive
packets to / from the network.
14
Note: The steps below should be done using the SNMP or CLI commands.
15
The ETS Cross-connection should be deactivated and deleted, refer to the the CLI command
guide.
16
Management Operator Disabling of PTP protocol over PTP logical Master port via setting of
ieee1588PtpPortDSAdminStatus to Disabled value. See CLI Command Guide.
17
If PPSIN has been configured as input for CRU (T0 and/or T4) or for internal Phase Distributor,
it has to be de-provisioned.
18
The PTP logical Master port must be disabled at SNMP side. Please refer to the CLI command
guide.
19
The TOD card shall be logically removed.
Enter:
RMV-EQPT::AID;
or
ED-EQPT::AID:OOS;
where:
• AID = PTP-{1-7}-{1-9}-{2-9,12-19,21-36}. Time Of Day - TOD Card
Note: TOD Card logical removal is mandatory also for avoiding traffic hits upon NGI links
of otherCollector cards eventually present in the shelf.
20
Enter:
DLT-EQPT::AID;
where:
• AID = PTP-{1-7}-{1-9}-{2-9,12-19,21-36}. Time Of Day - TOD Card
Result: The command causes the Deactivation/Deletion of PTP Master logical port (both
SNMP and TL1 side), of PPSIN and PPSOUT ports.
END OF STEPS
The following proposal is aimed to use the values retrieved by DDM for providing degrade
information and are hereafter described:
• The operator/NMS provides a configurable threshold (“delta” with 0.1dB granularity) for each
STM-64 interface.
• The NE monitors via DDM the “Receiver Input Power” and provides a “Warning” alarm when the
“delta” power is above the configured “delta” threshold for three consecutive times.
New alarm requires the introduction of a new standing condition associated to STM64 facility, which
shall be defined as follows:
• CondType: OPT-INTRUSION; Description: Optical Intrusion alarm;
Optical Intrusion alarm reports the measurements which caused the raising of the alarm condition,
they are:
• the last measured received power BEFORE the detection of optical intrusion (Power High);
• the last measured received power AFTER the detection of optical intrusion (Power Low).
It shall be noticed that as long as optical intrusion alarm has been detected and raise notification
has been emitted (i.e. OIDET parameter is equal to RAISED), monitoring of received optical power
on that interface is suspended, because:
• Eventual further decrease of received power shall not cause further raising of alarm notification;
• Eventual further increase of received power shall not cause a clear of the alarm previously
detected.
It shall be noticed that at NE restart all optical intrusion alarms, currently active just before NE
restart, will be raised again without changing Conddescr string respect to the previous alarm
notification.
6.61.2 General
The alarm will be available for STM-64 XFP modules with the max numbers:
• max 16 for 1850 TSS-160
• max 32 for 1850 TSS-320.
6.61.3 Procedure
Select action
• To enable/disable the mechanism for intrusion detection, go to Step 2
• To configure the threshold to trigger the alarm, go to Step 4.
2
Enable/disable the mechanism for intrusion detection
OIDET = Optical Intrusion Detection enabling function, determines if the mechanism of the
optical intrusion detection is disabled or not on the port. Once enabled, if an optical intrusion
event has been detected, the value changes autonomously to raised. Once raised, the alarm
clear notification can be triggered by changing the value to enabled or to disabled. Otherwise
the alarm clear notifcation occurs when global times TOUT-CLR expires, changing the value
from raised to enabled. Possible Values are:
• DISABLED Disabled. The optical intrusion detection is disabled.
• ENABLED Enabled. The optical intrusion detection is enabled.
3
To verify if the optical intrusion detection has been enabled/disabled, enter:
RTRV-STM64::AID;
where:
AID = STM64 Access Identifier, specifies the selected STM64 facility to which the command is
directed.
Result:
The command shows the OIDET output parameter value and format
• DISABLED Disabled. The optical intrusion detection is disabled.
• ENABLED Enabled. The optical intrusion detection is enabled.
• RAISED Raised. An optical intrusion event has been detected.
4
Configure the threshold to trigger the alarm
For the threshold configuration, enter:
ED-STM64::AID::::[,OIDET=][,OITHR=];
OITHR= [+0.1dB +48.2dB STEPSIZE 0.1dB].
Optical Intrusion Threshold, represents the maximum acceptable difference among two
measurements of received power, PRx(tn)-PRx(tn+1); if the calculated value is higher than this
value, then an alarm indication shall be triggered by the port. Unit of measure is dB.
5
To verify if the threshold configuration has been set, enter:
RTRV-STM64::AID;
where:
AID = STM64 Access Identifier, specifies the selected STM64 facility to which the command is
directed.
Result: The command shows the OITHR output parameter value and format
6
For the threshold configuration also the TimeOut of Clear alarm notification should be
defined. Enter:
SET-PRMTR-NE::::::[,TOUT-CLR=];
where:
TOUT-CLR= TimeOut of Clear alarm notification, represents the maximum time that alarm shall
stay on, before sending an esplicit clear alarm notification. Affected Alarms are the ones without
an autonomous alarm clear event. Unit of measure is the Hour.
END OF STEPS
6.62.2 Prerequisites
None
6.62.3 General
The OPR-ACO-COM command is used to cut off the office audible alarm indications without
changing the local alarm reporting. The currently active audible alarm indications will be silenced.
The visual alarm indications are not affected. Future alarm reporting is not be affected and new
audible alarm indications will be provided for any new alarms.
The Alarm Cut Off (ACO) LED is turned on when the OPR-ACO-COM is issued. When the ACO
LED is turned on and a new alarm arrives, it is presented to the audible closures. The ACO LED is
turned off will be turned off only when all the alarms silenced by OPRACO- COM are cleared.
Alarms silenced by the OPR-ACO-COM are not presented to the Audible closures even if they are
still present; only new alarms will be presented to the audible closures.
6.62.4 Procedure
1
Enter OPR-ACO-COM;
2
STOP. This procedure is complete.
END OF STEPS
6.63.2 Prerequisites
For redundant equipment, both copies must be provisioned and in service (IS).
The Protection Group associated to LOA10G is created on LOA10G creation in protection slot: that
is, the Switching mechanism starts when the protection slot is provisioned. In the shelf two
Protection groups are settable: one with slot 24 for protection and slots 21 and 22 as working and
another with slot 33 for protection and slots 35 and 36 as working.
6.63.3 General
Protection switching reduces possible service-effect by switching traffic to an alternate copy.
When a manual protection switch is performed, traffic will not return to the original module until it is
manually switched back.
This command sets the condition type of FRCDWKSWPR if the MODE parameter is set to FRCD.
This command sets the condition type of MANWKSWPR if the MODE parameter is set to NORM.
In order for a SW-TOPROTN-EQPT command to execute, switch to protection must be enabled
and the protection module has to be provisioned regardless of the state of the working module.
Executing a SW-TOPROTN-EQPT command sets a SST of STBYS on the specified module, clears
the SST of STBYH and sets the SST of WRK on the protection module.
6.63.4 Procedure
1
Select action.
To switch LOA10G to protection, go to Step 2.
To switch LOA10G to working, go to Step 4.
To perform copy switch for redundant equipment, go to Step 6.
2
Switch LOA10G to Protection
Enter SW-TOPROTN-EQPT::AID:::[MODE]
where: AID = Equipment Access Identifier, identifies the equipment entity access identifier.
Possible values:
• LOA10G-{1-7}-{1-9}-{21,22,24,33,35,36} for Lower Order Adaptation Card with EPS
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
3
Go to Step 7.
4
Switch LOA10G to Working
Enter SW-TOWKG-EQPT::AID:::[MODE];
where: AID = Equipment Access Identifier, identifies the equipment entity access identifier.
Possible values:
• LOA10G-{1-7}-{1-9}-{21,22,24,33,35,36} for Lower Order Adaptation Card with EPS
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
5
Go to Step 7.
6
Perform Copy Switch for Redundant Equipment
Enter SW-DX-EQPT::AID:::[MODE];
where: AID = Equipment Access Identifier, identifies the equipment entity access identifier.
Possible values:
• EC320-{1-7}-{1-9}-{1,20} for Equipment Controller Card TSS-320
• MT320-{1-7}-{1-9}-{10,11} for Matrix and Timing TSS-320
• MT160-{1-7}-{1-9}-{10,11} for Matrix and Timing TSS-160
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
7
STOP. This procedure is complete.
END OF STEPS
6.64.2 Prerequisites
To perform this procedure the NE being backed up must have IP-based access and the user must
be logged in to that node.
The remote file sever must support an IP connection and FTP.
6.64.3 General
Creation of a database backup occurs on-line without interrupting normal service operation. The
system has several database types. See Figure 26, “Database Types” (p. 370).
• ACTV CPU DB—Database in volatile memory (RAM on the L1 controller)
• ACTV DSK DB—Primary backup database on the NE's disk. This database is also used to
automatically restore the ACTV CPU DB upon system initialization.
• DFLT DB—Factory default configuration provided for the NE during system installation time.
• RFS DB—Remote File Server Database. This database is copied to the STDBY DB during a
successful file transfer operation.
• STDBY DB—Secondary backup database on the NE's disk. This database is created during a
successful backup operation. It is copied to the ACTV DSK DB and ACT CPU DB during a
successful restoration operation. The STDBY DB can also be copied to/from the RFS.
ACT-DB-BACKUP is used to perform a backup of the primary database (ACT DSK DB) to the
secondary database (STDBY DB). The database information backed up includes provisioning and
cross-connection information. ACT-DB-BACKUP will also write the system type, software release
identifier, site identifier, and backup date and time to the STDBY DB.
COPY-RFILE is used to copy database backup files (STDBY DB) from the NE to a specified
Remote File Server (RFS) or from the RFS to the NE.
CANC-COPY-RFILE is used to interrupt a file transfer that is in progress from a previously initiated
COPY-RFILE command. A subsequent COPY-RFILE starts a file transfer from the beginning.
• In case a remote download file transfer is autonomously or manually canceled, all files already
transferred or partially transferred on the NE are removed or otherwise marked as invalid.
• In case a remote upload file transfer is autonomously or manually canceled, partially transferred
files might exist on the RFS after an upload gets canceled. The system does not take care of
these remote files. It is the responsibility of the RFS maintainer in this case to do the clean up, or
to reuse the same storage location for future backups by using the overwrite option.
The following steps describe the basic procedure of creating a remote database backup. Refer to
Figure 27, “Database Backup and File Transfer to RFS” (p. 370).
1. ACT-DB-BACKUP command is sent.
2. COPY-RFILE command is sent.
3. The NE sends a message to the RFS initiating the file transfer.
4. The NE sends messages to the OS indicating the file transfer is on its way (COPY-RFILE
command completion and then REPT COPY RFILE).
5. During the transfer process, messages are sent to the OS to keep it informed of the progress
(REPT COPY RFILE).
6. When the transfer has completed, the NE sends a completion message to the OS (REPT
COPY RFILE).
6.64.4 Procedure
1
Select action.
To perform remote database backup, go to Step 2.
2
Perform Remote Database Backup
Enter ACT-DB-BACKUP;
3
Wait for command to complete, with the following format:
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
4
Enter COPY-RFILE::FROM,TO::::,LOCATION=[,CMDMDE=];
where:
• FROM= Specifies the entity to be transferred. Possible values: STBYDB (The system's
secondary backup database) or RFSDB (A database backup on a Remote File Server) or
RFSSW (A software generic on a remote file server) or LOCPMGLB (Local NE PM Global file
collection) or RFSSCRIPT (A script files collection on a remote file server), LOCFILE (Local
NE single file), or LOCMACGLB (Represents the MAC File Collection in the local NE).
• TO= Specifies the entity that gets created as the result of the command completion. Possible
values: RFSDB (A database backup on a Remote File Server) or STBYDB (The system's
secondary backup database) or STBYSW (The standby software generic on the NE) or
RFSPMGLB (Remote File Server PM Global file collection) or LOCSCRIPT (Local NE script
files collection), RFSFILE (A single file on a remote file server), or RFSMACGLB (The MAC
File Collection on a Remote File Server). The following table shows the allowed combinations
FROM TO
STBYDB RFSDB
RFSDB STBYDB
RFSSW STBYSW
LOCPMGLB RFSPMGLB
RFSSCRIPT LOCSCRIPT
LOCFILE RFSFILE
LOCMACGLB RFSMACGLB
5
Go to “” (p. 374).
6
Cancel Database File Transfer
Enter CANC-COPY-RFILE::FROM,TO:;
where:
• FROM=It specifies the entity to be transferred of the COPY-RFILE to be canceled. Possible
values previously referred in Step 4.
• TO=It specifies the entity that gets created as the result of the command completion of the
COPY-RFILE to be canceled. Possible values previously referred in Step 4..
7
STOP. This procedure is complete.
END OF STEPS
6.65.2 Prerequisites
To perform this procedure the NE being restored must have IP-based access and the user must be
logged in to that node.
The remote file sever must support an IP connection and FTP.
6.65.3 General
The system has several database types. See Figure 28, “Database Types” (p. 376).
• ACTV CPU DB—Database in volatile memory (RAM on the L1 controller)
• ACTV DSK DB—Primary backup database on the NE's disk. This database is also used to
automatically restore the ACTV CPU DB upon system initialization.
• DFLT DB—Factory default configuration provided for the NE during system installation time.
• RFS DB—Remote File Server Database. This database is copied to the STDBY DB during a
successful file transfer operation.
• STDBY DB—Secondary backup database on the NE's disk. This database is created during a
successful backup operation. It is copied to the ACTV DSK DB and ACT CPU DB during a
successful restoration operation. The STDBY DB can also be copied to/from the RFS.
RTRV-RFILE is used to retrieve information related to transferred files (database) on a Remote File
Server (RFS). It reads the system type, the software release stream and number, backup date,
backup time, SID, and database version from the RFSDB. This command is used before doing a
backup to ensure that existing backup information can be overwritten.
COPY-RFILE is used to copy the RFS Database files (RFSDB) to the system Standby Database
(STDBYDB). Before the database is restored, the system verifies that the information in the system
matches information in the description file for the database to be restored. This information includes
the system type, software release stream, software release number, time stamp, and System
Identifier (SID).
The RESTORE-DB command copies the backup database stored on STDBY DB to the primary
backup database (ACTV DSK DB) and resets the system to activate the new database.
The RTRV-DB-LABEL command reads the database label of the selected backup database stored
on the NE (ACT DSK DB or STDBY DB). If STDBY DB is selected and VERIFY is specified for the
VER parameter, a Cyclic Redundancy Check (CRC) verification on the database is performed. If
the calculated CRC and stored CRC do not match, an unsuccessful response (DENY) message is
returned for the RTRV-DB-LABEL command.
The following steps describe the basic procedure of creating a remote database restore. Refer to
Figure 29, “Database Transfer and Restore from RFS to NE” (p. 376).
1. COPY-RFILE command is sent.
2. The NE requests the backup from the RFS and begins storing it on the hard disk.
3. The NE sends messages to the OS indicating the file transfer is on its way (COPY-RFILE
command completion and then REPT COPY RFILE).
4. During the transfer process, messages are sent to the OS to keep it informed ofthe progress
(REPT COPY RFILE).
5. When the transfer has completed, the NE sends a completion message to the OS (REPT
COPY RFILE).
6. The RESTORE-DB command is sent to the NE to start the activation of the restored database.
6.65.4 Procedure
1
Enter RTRV-RFILE::AID::::LOCATION=;
where:
• AID=Identifies the database for which the information is retrieved. Possible values: RFSDB A
database backup on a Remote File Server
• LOCATION= Location indicates the source/destination of the files on an RFS. The syntax of
the url is as follows: "ftp://[<userid>[:<password>]@]<ftphost>[:<port>]/
<url-path>" with:
• userid= The user identifier used for the FTP connection on the RFS.
• password=The user password for the FTP connection on the RFS.
• ftphost=The IP address of the host (the RFS)
• port=The port number to connect to. The default port number for FTP is 21.
• url-path=Details of how the directory where the files reside can be accessed. It has the
following syntax: [/]<cwd1>/<cwd2>/.../<cwdN> where <cwd1> through <cwdN> are
strings that identify directories. The <cwd1>-<cwdN> portion of the <url-path> is interpreted
as a series of FTP commands as each of the cwd elements is to be supplied, sequentially, as
the argument to an FTP CWD (change working directory) command.
2
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<AID>:<SYSTYPE>,<RLSID>,[<SID>],[<DATE>],[<TIME>],[<REGION>]" cr lf
[
/*
<Informational_Description_Text>
*/ cr lf]
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
3
Enter COPY-RFILE::FROM,TO::::,LOCATION=[,CMDMDE=];
where:
• FROM= Specifies the entity to be transferred. Possible values: STBYDB (The system's
secondary backup database) or RFSDB (A database backup on a Remote File Server) or
RFSSW (A software generic on a remote file server) or LOCPMGLB (Local NE PM Global file
collection) or RFSSCRIPT (A script files collection on a remote file server), LOCFILE (Local
NE single file), or LOCMACGLB (Represents the MAC File Collection in the local NE).
• TO= Specifies the entity that gets created as the result of the command completion. Possible
values: RFSDB (A database backup on a Remote File Server) or STBYDB (The system's
secondary backup database) or STBYSW (The standby software generic on the NE) or
RFSPMGLB (Remote File Server PM Global file collection) or LOCSCRIPT (Local NE script
files collection), RFSFILE (A single file on a remote file server), or RFSMACGLB (The MAC
File Collection on a Remote File Server). The following table shows the allowed combinations
FROM TO
STBYDB RFSDB
RFSDB STBYDB
RFSSW STBYSW
LOCPMGLB RFSPMGLB
RFSSCRIPT LOCSCRIPT
LOCFILE RFSFILE
LOCMACGLB RFSMACGLB
4
Wait for command completion message.
5
Enter RESTORE-DB::::::[CMDMDE=];
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
6
Wait for command completion.
7
Enter RTRV-DB-LABEL; to verify newly restored database is present in the system.
The answer of the system will be the following, as detailed in the relevant command guide, refer
to “Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<AID>:[<SYSTYPE>],[<RLSID>],[<SID>],[<DATE>],[<TIME>][,<CRC>]" cr lf
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
8
STOP. This procedure is complete.
END OF STEPS
6.66.2 General
The typical scenario is shown below, with RNEs (TSS3) of different customers. NM shall be able to
communicate with all TSS3, but TSS3 nodes shall not communicate between them:
The system supports configuration of a list of IP addresses, called “port segregation list”, containing
the IP addresses of the machines that are connected to the network and are allowed to
communicate with any other machine’s IP of the network.
ONLY the packets that have EML address as FROM or TO are allowed (all others are discarded).
This would allow to have full secure network (no access at all from external IPs).
The “port segregation list” is configured, and retrieved via TL1 commands (ED-PORTSEGLIST,
RTRV- PORTSEGLIST). It shall be defined for the entire network, i.e. it is not customized for a
single NE.
Note: Port Segregation must not be enabled if the “port segregation list” is empty, since it will
make the NE unreachable.
6.66.4 Procedure
1
To create the port segregation list enter:
ED-PORTSEGLIST:::::CMD:IPADDR=[,IPMASK=];
where:
• CMD= ADD, RMV. Command Code, specifies whether the specified IPADDR shall be added
to the port-segregration list or removed from it.
• IPADDR= {0-255}-{0-255-{0-255}-{0-255}
IP address that shall be added to the port-segregration list or removed from it.
• IPMASK= {0-255}-{0-255-{0-255}-{0-255}
IP subnet mask.
Example: The following example illustrates the command and associated output for adding an
IP address to the pot-segregation list.
ED-PORTSEGLIST:::::ADD:151-98-25-25;
AM1520 03-07-08 10:16:52 M P0c032 COMPLD
/* ED-PORTSEGLIST:::::ADD:151-98-25-25 [P0c032] (1) */
2
To retrieve the current port-segregation list enter:
RTRV-PORTSEGLIST:[TID]::[CTAG];
Result:
OUTPUT PARAMETERS
• IPADDR= {0-255}.{0-255}.{0-255}.{0-255}
Description: IP address in the current port-segregration list. IPMASK= {0-255}.
{0-255}.{0-255}.{0-255}
Description: IP subnet mask.
3
To enable Port Segregation enter:
SET-ATTR-SECUDFLT:::::: [,SECA CC=][,SECPORTMODE=][,PHYSPORTS=];
where:
• SECACC = SECURE. Secure Access for the NE. When the NE is in SECURE mode, only
ports 6084 and 6085 (TL1), 6086 (CLI), 22 (debug port for ROOT access always with SSH)
and 443 (HTTPS) are opened, the NE shall support SNMPv3 and shall use SFTP to transfer
files to/from the NE.
• SECPORTMODE=ENABLE, the NE shall discard all the IP packets with either SA or DA not
matching with any IP address in the current port-segregation list (see ED-PORTSEGLIST).
When the feature is disabled (SECPORTMODE=DISABLE), the NE shall not apply the
port-segregation filter on the IP packets incoming or outgoing through the NE.
END OF STEPS
6.67.2 Prerequisites
The NE is based on three different Main Shelf versions, that is UNVRSL320, UNVRSL160 and
UNVRSL160C. Mandatory equipment shall be automatically provisioned whether present or not.
6.67.3 General
The procedure assigns an equipment object entity at the AID physical location and provisions the
specified equipment (also called pre-provisioning) regardless of whether the equipment is installed
in the system.
Non-mandatory equipment is provisionable regardless of actual presence in the system.
Non-mandatory equipment can be pre-provisioned; the slot is provisioned in advance of a card
being inserted.
The following equipment is non-mandatory and can be pre-provisioned into the system:
• protection EC320
• Lower Order Adaptation Card 10G
• 10GSO (STM-64) card
• 10GSO (OC-192/STM-64) Evolution card
• 2.5G (STM-16) module
• 8 Port (STM-1)/(STM-4) card
• 8 Port Multirate 8xSTM1/4 - 4xSTM16 Card
• 63 E1 Port Card
• 63 E1 Access Card (75 vs 120 ohm)
• 63 E1 Protection Card
• G.709 OTU 10GB Card (OT2TDM)
• G.709 OTU 10GB Card with XFP
• ANYFC 10GB 10 x FC-2/FC-4
• 10XANY 10GB 10xGBE Card
• MultiService Adaptation Card (Packet Module 10G)
• MultiService Adaptation Card for ATM (Packet Module 10G)
• Universal GateWay UGW Adaptation Card (Packet Module 10G)
• Packet Module 10x1GbEthernet (Packet Module 10G)
• Packet Module 20x1GbEthernet
• Packet Module 1x10GbEthernet (Packet Module 10G)
• Packet Module 2x10GbEthernet
• Optical Pre-Amplifer 10G
• Optical Booster 10G Line
• Optical Filter and Attenuator (LOFA)
• DWDM Optical Transponder with Colored XFPs
• CWDM Optical Transponder (2.5G) without Optical Protection
• CWDM Optical Transponder (2.5G) with Optical Protection
• CWDM OADM 4ch w/o OSC coupler
• CWDM OADM 4ch w OSC coupler
• CWDM OADM 2ch w/o OSC coupler
• CWDM OADM 2ch w OSC coupler
• CWDM OADM 1ch w/o OSC coupler
• CWDM OADM 1ch w OSC coupler
• CWDM Mux/Demux 8ch w/o OSC coupler
• CWDM Mux/Demux 8ch with OSC coupler
• CWDM Mux/Demux 2ch with OSC coupler
• CWDM Mux/Demux 1ch with OSC coupler
• DWDM Mux/Demux 8 channels L1 band without S-band input/output
• XFP on 10GSO modules
• SFP on 2G5SO modules
• SFP on 8XSO modules
• SFP on 10XANY modules
• 1000BASE-BX20 (Upstream and Downstream)
• 1000BASE-BX40 (Upstream and Downstream)
• FE 100BASE-BX20 (Upstream and Downstream)
• OC-48/STM-16 40km BiDi (Upstream and Downstream)
Shelf Types
• UNVRSL320 (Generic 320 type shelf)
• UNVRSL160 (Generic 160 type shelf)
• UNVRSL160C (19” 160 type shelf)
6.67.4 Procedure
1
Verify the shelf type entering RTRV-EQPT::ALL;
where ALL means all the AID.
2
Examine the response, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
3
Select action.
For Shelf provision, go to Step 4.
For Unit provision, go to Step 7.
For XFP/SFP module provision, go to Step 10.
4
Shelf provision
where:
• SHELF-{1-7}-{1-9}=Equipment Access Identifier, identifies the equipment entity access
identifier in the {RACK}-{SHELF} format.
• E1M-{1-7}-{2}-{7-14} - 63 E1 Multiplexer Card
• E1ACC-{1-7}-{2}-{3-5,16-18} - 63 E1 Access Card
• E1PR-{1-7}-{2}-{2,19} - 63 E1 EPS Card
• P42E1-{1-7}-{1-9}-{1-6} - 1646DS 42XE1/T1 Card
• SFP-{1-7}-{1-9}-{7}-{1} - 1646DS 1XSTM1/STM4/STM16 Sub-module - Main position
• PROVISIONEDTYPE parameter with the values: UNVRSL320, UNVRSL160 and
UNVRSL160C
• SR2U - 1646SM R2.0 2RU Drop Shelf
• P63E1 - 63 x E1 Port Module
• A63E1A - 63 x E1 Access Module 75ohm unb
• A63E1B - 63 x E1 Access Module 120ohm bal
• LSPROT - 63 x E1 Access Protection Module
• PE1A - 1646DS 42XE1 120 OHM Card
• PE1B - 1646DS 42XE1 75 OHM Card
• M1S1 - 1646DS 1XSTM1 sub-module
• M1S4 - 1646DS 1XSTM4 sub-module
• M1S16 - 1646DS 1XSTM16 sub-module
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
Note:
When a Shelf is provisioned, there are automatically created some Mandatory Equipment
Entities, according to the following list:
• UNVRSL320 Main Shelf Role: EC320 (slot 1), MT320 (slot 10 and 11), PSF320 (slot
37 and 39), TBUS320 (slot 42 and 43), FAN320 (slot 40 and 41)
• UNVRSL160 Main Shelf Role: EC320 (slot 1), MT160 (slot 10 and 11), PSF320 (slot
37 and 39), TBUS320 (slot 42 and 43), FAN320 (slot 40 and 41)
• UNVRSL160C Main Shelf Role: EC320 (slot 1), MT160 (slot 10 and 11), PSFAN (slot
37 and 39), TB160J (slot 42 and 43), FANDRAWER (slot 40 and 41)
• the first ENT command received is the one related to AID Assignment to the Main Shelf, but
at least one of the PARAMETERs SHELFNUM and SHELFROLE is lacking
• the first ENT command received is the one related to AID Assignment to the Main Shelf, and
the assigned AID is different from <SHELF-1-1>
• a Main Shelf is already provisioned and a new ENT-EQPT command has been received with
the PARAMETER SHELFROLE set to MAIN <SHELF-1-1>
• the command is input for an AID which is not a Shelf with Provisioned Type = UNVRSL320 or
UNVRSL160 or UNVRSL160C and at least one PARAMETER among SHELFNUM or
SHELFROLE is set
• the command is input for a Shelf AID which has a Provisioned Type = UNVRSL320 or
UNVRSL160 or UNVRSL160C and the Parameter SHELFNUM is not set
6
Go to Step 7.
7
Unit provision
Verify the unit is in appropriate slot. Refer to Figure 37, “1850 TSS-160 Shelf Slot Locations”
(p. 687) or Figure 38, “1850 TSS-320 Shelf Slot Locations” (p. 690).
8
Enter ENT-EQPT::AID::::[PROVISIONEDTYPE=][,AINSMODE=][,SHELFNUM=][,
SHELFROLE=][,APTMODE=][,VOAMODE=][,APSD1=][,APSD2=][,OPWRL1=][,
OPWRL2=][,VOA=][,EOLSPAN=][,N1=][,PCH1=][,IT=][,LAMBDASET=][,ALMPROF=]
[,CLNTSEL=][,OPWRLOT2=][,SSBIT=]:[PST];
where:
• AID=Equipment Access Identifier, identifies the equipment entity access identifier. Possible
values: refer to B.3 “AIDs” (p. 692) or to “Command details” (p. 107).
• PROVISIONEDTYPE = Nokia mnemonic stored in the Remote Inventory EPROM for the
given equipment.
For possible values please refer to B.4 “Provisioned Types” (p. 693).
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
Note: When the ENT-EQPT command is entered with AID 10GSO/ CWLA/CMDX/
PP10AD/PP10GE/PP1GE/PPUGW/PP1GEX20/PP10GEX2 the related
PROVISIONEDTYPE should be specified
9
Is the board provided with an XFP or SFP module?
If yes, go to Step 10.
If no, go to Step 12.
10
XFP/SFP module provision
Verify the XFP/SFP module on the board (ref. to Table 59, “Supported SFP/XFP Optics
Modules - Client Side” (p. 692)).
11
Enter ENT-EQPT::AID::::PROVISIONEDTYPE=[,AINSMODE=][,SHELFNUM=][,
SHELFROLE=][,APTMODE=][,VOAMODE=][,APSD1=][,APSD2=][,OPWRL1=][,
OPWRL2=][,VOA=][,EOLSPAN=][,N1=][,PCH1=][,IT=][,LAMBDASET=][,ALMPROF=
][,CLNTSEL=][,OPWRLOT2=][,SSBIT=]:[PST];
where:
• AID=Module Access Identifier previously referred in Step 8
• PROVISIONEDTYPE= Nokia mnemonic stored in the Remote Inventory EPROM for the
given equipment. It is mandatory to specifiy this parameter for XFP/SFP modules (ANY-
<type> is used for generic MSA XFP/SFP). For details see B.4 “Provisioned Types” (p. 693).
• The CLNTSEL parameter is a mandatory parameter associated to an SFP/XFP mounted on
the Client side Port of a Transponder Card or mounted on any Port of the 10XANY card with
PROVISIONEDTYPE equal to ANYFC.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
12
STOP. This procedure is complete.
END OF STEPS
6.68.2 General
The following TL1 commands are used to configure and retrieve RADIUS Timeout and Retries:
SET-RADIUS-AUTH RTRV-RADIUS-AUTH
6.68.4 Procedure
1
Login to NE with SEC (security administrator) user.
Select action:
• To configure authentication order as LOCAL go to Step 3
• To configure authentication order as RADIUS go to Step 9
3
Authentication order as LOCAL
Configure user (for example, USER01) with “Security Administrator” Privileges (set UAP=SEC).
For details, refer to 6.38 “Administer Users with Security Administrator Privileges” (p. 263).
4
Configure RADIUS server as first server on NE.For details, refer to 6.29 “Administer Radius
server” (p. 229).
5
Set the user's (USER01) and the RADIUS passwords.
For details, refer to 6.38 “Administer Users with Security Administrator Privileges” (p. 263),
6.29 “Administer Radius server” (p. 229).
Note: Values should be different from the local password stored on the RADIUS server
database
6
Configure authentication order as LOCAL, to perform this operation enter:
SET-RADIUS-AUTH:::::LOCAL:[RETRIES=][,TIMEOUT=];
For parameter descriptions of TL1 commands used in this procedure, refer to the
1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1
Command Guide.
7
To retrieve authentication order enter:
RTRV-RADIUS-AUTH;
8
Authenticate the user “USER01” with local password.
Result: Authentication is accepted.
9
Authentication order as RADIUS
To use RADIUS as authentication server, it is not needed (better, it must be avoided) to
provision the same user on the local DB. In case a user is configured both locally and in the
RADIUS server and the passwords are different, when the user tries to authenticate using
RADIUS password the access is denied, because the check is firstly performed in the local DB
and if the password is wrong the connection is refused.
Configure user (for example, USER01) with “Security Administrator” Privileges (set UAP=SEC).
Refer to 6.38 “Administer Users with Security Administrator Privileges” (p. 263).
10
Configure RADIUS server as first server on NE.For details, refer to 6.29 “Administer Radius
server” (p. 229).
11
Set the user's (USER01) and the RADIUS passwords.
For details, refer to 6.38 “Administer Users with Security Administrator Privileges” (p. 263),
6.29 “Administer Radius server” (p. 229).
Note: Values should be different from the local password stored on the RADIUS server
database
12
Configure authentication order as RADIUS, to perform this operation enter:
SET-RADIUS-AUTH:::::RADIUS:[RETRIES=][,TIMEOUT=];
For parameter descriptions of TL1 commands used in this procedure, refer to the
1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1
Command Guide.
13
To retrieve authentication order enter:
RTRV-RADIUS-AUTH;
14
Authenticate the user “USER01” with radius password
Result: Authentication is accepted.
END OF STEPS
6.69.2 Prerequisites
The user should verify by means of the RTRV-EQPT command the devices presence and state into
the equipment before removing/restoring it.
6.69.3 General
RMV-EQPT causes the specified equipment to be placed in the out-of-service management service
state. The command can be applied to the following equipment:
• EC320
• MT320
• MT160
• PSF320 and POW320
• FAN
• Lower Order Adaptation Card 10G
• 10GSO (STM-64) card
• 2.5G (STM-16) module
• 8 Port (STM-1)/(STM-4) card
• G.709 OTU 10GB Card (OT2TDM)
• ANYFC 10GB 10 x FC-2/FC-4
• 10XANY 10GB 10xGBE Card
• MultiService Adaptation Card (Packet Module 10G)
• Packet Module 10x1GbEthernet (Packet Module 10G)
• Packet Module 1x10GbEthernet (Packet Module 10G)
• Optical Pre-Amplifer 10G
• Optical Booster 10G Line
• Optical Filter and Attenuator (LOFA)
• DWDM Optical Transponder with Colored XFPs
• CWDM Optical Transponder (2.5G) without Optical Protection
• CWDM Optical Transponder (2.5G) with Optical Protection
• CWDM OADM 4ch w/o OSC coupler
• CWDM OADM 4ch w OSC coupler
• CWDM OADM 2ch w/o OSC coupler
• CWDM OADM 2ch w OSC coupler
• CWDM OADM 1ch w/o OSC coupler
• CWDM OADM 1ch w OSC coupler
• CWDM Mux/Demux 8ch w/o OSC coupler
• CWDM Mux/Demux 8ch with OSC coupler
• CWDM Mux/Demux 2ch with OSC coupler
• CWDM Mux/Demux 1ch with OSC coupler
• DWDM Mux/Demux 8 channels L1 band without S-band input/output
• XFP on 10GSO modules
• SFP on 2G5SO modules
• SFP on 8 port (STM-1)/(STM-4) modules (8XSO)
• SFP on 10XANY modules
Executing a RMV-EQPT command causes a primary state transition from IS or OOS-AU to
OOS-MA or OOS-AUMA respectively. Secondary states associated with the equipment entity before
and after the command is executed depend upon events detected by the system.
A MODE parameter (NORM/FRCD) is used to specify if the command has to be completed or not.
A module which is NOTswitched to protection (regardless of whether the ports are provisioned on it
or paths are cross connected) can be logically removed only with the MODE parameter set to
FRCD
When the RMV-EQPT command is entered for an active module, only the MODE=FRCD is
accepted, and it is up to the operator to manually execute the switch to the other copy before or
after the logical removal of the module.
A forced removal may result in an interruption of traffic.
During a successful removal of an IOC/SFP/XFP, the laser(s) of the affected STMn shall remain on.
Because of the potential service impact, the user should switch traffic away from a module before
performing a RMV-EQPT.
This command causes a clear message to be sent for any condition that has already been
autonomously reported. It prevents any subsequent conditions declared against the equipment from
being autonomously reported but the conditions are still retrievable.
The RST-EQPT command causes the specified equipment to be placed in the IS or OOS-AU
primary state. Secondary states associated with the equipment entity before and after the
command is executed depend upon events detected by the system.
This command allows any active condition declared against the equipment to be autonomously
reported.
Neither intrusive diagnostics nor SW downloads are done during a restore operation.
A forced restoral is allowed setting MODE parameter to FRCD.
6.69.4 Procedure
1
Select action.
To remove equipment, go to Step 2.
To restore equipment, go to Step 9.
2
Remove Equipment
Enter RTRV-EQPT::AID; to view equipment service states.
where:
• AID=Equipment Access Identifier, identifies the equipment entity access identifier. Possible
values:
− EC320-{1-7}-{1-9}-{1,20} for Equipment Controller Card TSS-320
− 10GSO-{1-7}-{1-9}-{2-9,12-19,21-36} for 10G Synchronous Optical
− 2G5SO-{1-7}-{1-9}-{2-9,12-19,21-36} for 2.5G Synchronous Optical
− 8XSO-{1-7}-{1-9}-{2-9,12-19,21-36} for 8 x Synchronous Optical
− OT2TDM-{1-7}-{1-9}-{2-9,12-19,21-36} for G.709 OTU 10GB Card - Provisioned Type =
1POTU2
3
What is PST of module to remove?
If IS-NR or OOS-AU, go to Step 4.
If OOS-MA or OOS-AUMA, module is already removed from service. Go to Step 12.
4
Is 10GSO, 2G5SO, 8XSO, SFP, or XFP, to be removed?
If yes, go to Step 5.
If no, go to Step 7.
A forced removal may result in an interruption of traffic.
5
Go to Step 7.
6
Switch module to protection. Refer to 6.63 “Perform Module Protection Switch or Copy Switch”
(p. 367).
7
Enter RMV-EQPT::AID:::[MODE];
where:
• AID=Access Identifier of specified equipment as previously referred.
• MODE= NORM (Normal, the command is denied if the result of its execution is service-
affecting) or FRCD (Forced, the command is completed even if the result of its execution is
service-affecting).
8
Go to Step 12.
9
Restore Equipment
Enter RTRV-EQPT::AID; to view equipment service states as previously referred.
10
What is PST of module to restore?
If OOS-MA or OOS-AUMA, go to Step 11.
If IS-NR or OOS-AU, module is already restored to service. Go to Step 12
11
Enter RST-EQPT::AID:::[MODE];
where:
• AID=Access Identifier of specified equipment as previously referred.
• MODE= NORM (Normal, the command is denied if the result of its execution is service-
affecting) or FRCD (Forced, the command is completed even if the result of its execution is
service-affecting).
12
STOP. This procedure is complete.
END OF STEPS
6.70.2 Prerequisites
None.
6.70.3 General
PM commands operate only on provisioned ports.
PM commands are used to monitor defect conditions, and can be used to track system efficiency.
By tracking efficiency, users can recognize gradual deterioration of system performance.
RTRV-PM-x retrieves facility PM current and/or historical data 15-minute or 1-day PM data that
corresponds to the facility PM data collection registers.
INIT-REG-x initializes the current 15-minute and current 1-day PM collection registers for the
monitored parameters.
6.70.4 Procedure
1
Select action.
To retrieve PM data, go to Step 2.
To initialize PM data collection register, go to Step 5.
To initialize PM data collection register, go to Step 5.
To end this procedure, go to Step 7.
2
Retrieve PM Data
Enter RTRV-PM-x::AID:::[MONTYPE],[MONLEV],[LOCN],[DIRN],[TMPER],
[MONDAT],[MONTM],[NUM15MIN],[NUM1DAY];
where:
• x= GBE10, GBE, ODU2, OTU2, MAU, STM1, STM4, STM16, STM64, VC4, VC44C,
VC416C, VC464C, LOVC12, LOVC3.
• AID=Access Identifier, identifies the entity access identifier. Only valid sdhFacility / AID
combinations are allowed, all other shall be rejected.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
3
Examine output for PM information, as detailed in the relevant command guide, refer to
“Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
"<AID>,<AIDTYPE>:<MONTYPE>,<MONVAL>/<MONLEV>,<VLDTY>,<LOCN>,<DIRN>,
<TMPER>,<MONDAT>,<MONTM>,<ELTM>" cr lf]
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
4
Go to Step 1.
5
Initialize PM Data Collection Register
Enter INIT-REG-x::AID:::[MONTYPE],[MONVAL],[LOCN],[DIRN],[TMPER];
where:
• x= GBE10, GBE, ODU2, OTU2, MAU, STM1, STM4, STM16, STM64, VC4, VC44C,
VC416C, VC464C, LOVC12, LOVC3.
• AID=Access Identifier, identifies the entity access identifier. Possible values: refer to
A.2 “Access Identifiers” (p. 611) according to the facility.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
6
Go to Step 1.
7
STOP. This procedure is complete.
END OF STEPS
6.71.2 Prerequisites
None.
6.71.3 General
The site identifier appears in command response messages, and is used as the target identifier
when addressing an NE through a TL1 gateway. In this procedure, enter parameter values only for
indicated fields. Leave remaining fields blank for system defaults.
The RTRV-HDR command retrieves the system's output response (site) header. The output
response header consists of the Site Identifier (SID) and the current date and local time. A special
version of this command, using the PC option, is available to assist in discovery of the TIDs of
Remote NEs connected to a Gateway NE via OSI over DCC. The PC option also returns the NE
type and software release number. If an NSAP address but not a TID is known for an NE, then the
TID can be returned by using the NSAP address in the command.
The SET-SID command is used to set the Site Identifier (SID) code that is compared to any Target
Identifier (TID) value entered in a command.
6.71.4 Procedure
1
Select action.
To retrieve current site identifier, go to Step 2.
To change site identifier, go to Step 4.
2
Retrieve Site Identifier
Enter RTRV-HDR:::::[PC];
Examine output to determine current site identifier, which appears on the first line, as detailed in
the relevant command guide, refer to “Command details” (p. 107).
cr lf lf
<CTAG>
COMPLD cr lf
"<SID>,,1850TSS320,,MN,,,<RLSNUM>" cr lf
[
/*
<Command
Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
3
Go to Step 5.
4
Change Site Identifier
Enter SET-SID:::::SID;
where: SID= Site Identifier, identifies the new SID. The SID value shall follow the same syntax
rules as the TID value. That is, the SID value can be either up to 20 noncase-sensitive
alphanumeric characters, including the special hyphen (-) character, or up to 20 characters
quoted string.
If it is a non quoted string, the hyphen (-) is the only special character allowed. The SID must
start with a letter and shall end with an alphanumeric character. Consecutive hyphens (-) shall
not be allowed. Number of hyphens shall be not greater than 4. If a lower-case character string
is entered for the SID, it is automatically converted to an uppercase character string for
comparison to any TID value entered in a command.
If it is a quoted string, any character is allowed, included any special character, and no case
conversion is applied.
On initial turnup, the NE shall automatically generate an unique SID, using the last 5
hexadecimal characters of the NE's MAC address and appending them to the PLEASE- SET-
SID name.
This SID will be updated (by reading the MAC address from the appropriate NE hardware
module) and stored in the NE's database during any cold restart of the NE, as long as the SID
is already set to PLEASE-SET-SID- xxxxx, or a default database is created.
5
STOP. This procedure is complete.
END OF STEPS
6.72.2 Prerequisites
None
6.72.3 General
The RTRV-RI command retrieves the remote inventory information for any module physically
present in the system regardless the provisioning state.
If the specified board supports a downloadable firmware, the command will retrieve the firmware
version currently running on the module. If the module does not support a downloadable firmware,
a value of "NA" is returned.
If the specified AID is MDL-x-x-x[-x], the command retrieves the remote inventory of a module which
is plugged-in whether the equipment is provisioned or not. If the AID is unassigned, the AID in the
output will be MDL-x-x-x[-x]. If the AID is assigned, the AID in the output will be the AID of the actual
module that has been assigned in the slot.
6.72.4 Procedure
1
Enter RTRV-RI::AID;
where: AID=Equipment Access Identifier, identifies the equipment entity access identifier. MDL
is used to identify a generic non mandatory module (whether it is provisioned or not. ). The
Inventory of all the NE is retrieved selecting AID=ALL. The Inventory of all the items plugged
inside a Shelf is retrieved selecting AID=SHELF-1-7-1-9 or AID=MDL-1-7-1-9. Possible values:
• ALL for all AID
• SHELF-{1-7}-{1-9} for the Shelf
• EC320-{1-7}-{1-9}-{1,20} for Equipment Controller Card TSS-320
2
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<AID>::[COMPANY=/"<value>/"][,MNEMONIC=/"<value>/"][,CLEI=/"<value>
/"][,PARTNUM=/"<value>/"][,SWPARTNUM=/"<value>/"][,FACTORY=/"<value>
/"][,SERIAL=/"<value>/"][,DATE=<value>][,EXTRADATA=/"<value>/"]"
cr lf
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
3
STOP. This procedure is complete.
END OF STEPS
6.73.2 Prerequisites
None
6.73.3 General
The RTRV-SECTRC retrieves the contents of the Regenerator SectionTrace using the 16-byte
frame format as defined in G.707. This command may be used to retrieve the "incoming" accepted
Regenerator Section Trace, the expected Regenerator Section Trace as used for the dTIM (Trace
Identifier Mismatch) supervision and the "outgoing" transmitted Regenerator Section Trace that is
inserted into the Regenerator Section overhead on the outgoing signal. The expected and
transmitted Regenerator Section Trace is provisioned via the ED facilities command. If no
TRACEMSG has been returned and the command did not fail, the system will output the /"/" string..
Two retrieval formats are permitted for the incoming trace: TEXT and HEX. The NE supports
provisioning of normal TL1 section trace messages, but it is possible to retrieve incoming messages
in hex format that may be generated by other NEs.
6.73.4 Procedure
1
Enter RTRV-SECTRC::AID:::[INCMSGFMT];
where:
• AID=Access identifier of the optical facility. Possible values:
− Client port on a DWLA10X module - OTU2, STM-64, 10GE
− STM1
− STM4
− STM16 on a 2G5SO or 10xANY
− STM64
− Client port on a DWLA10X module - OTU2, STM-64, 10GE , 10GFC
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
2
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
3
STOP. This procedure is complete.
END OF STEPS
6.74.2 Prerequisites
None.
6.74.3 General
The procedure retrieves general system level configuration information that consists of the following
parameters:
• System type
• Software release identifier
• Software release date
• Matrix size
• System restart status
6.74.4 Procedure
1
Enter RTRV-PRMTR-NE; to retrieve system configuration parameters.
2
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"::NODETYPE=<value>" cr lf
[
"<AID>:<SYSTYPE>,,<RLSID>,<RLSDATE>,<MTXSIZE>::<STATUS>,<REGION>,
<PROVMODE>,<USERLABEL>" cr lf]+
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
3
An example output is shown below:
4
STOP. This procedure is complete.
END OF STEPS
6.75.2 Prerequisites
None.
6.75.3 General
The RTRV-TL1-SYNTAX command is used to retrieve the syntax of a TL1 command, including a
description of the command parameters.
The CMDHDR parameter indicates the command header for which syntax is requested (e.g. SET-
ATTR-OC3).
6.75.4 Procedure
1
Enter RTRV-TL1-SYNTAX:::::CMDHDR;
where: CMDHDR= The command header for which syntax is requested (example: SET-
PMMODE-GBE)
2
Observe output. as follows, as detailed in the relevant command guide, refer to “Command
details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
/* INPUT-FORMAT */ cr lf
[
/*
<Command
Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf
;
3
STOP. This procedure is complete.
END OF STEPS
6.76.2 Prerequisites
None.
6.76.3 General
The procedure retrieves the user profile entry for the specified user. It retrieves both the static user
provisioning information and dynamic user information.
• Static user provisioning information—Information provided by means of the ENT/ED-USER-
SECU commands such as user privilege level, max interval for link timeout, and user provided
name. Refer to 6.2 “Add New User to System” (p. 138)and 6.52 “Edit User Profile” (p. 337).
• Dynamic user information—Information such as the UID status depending on the result of INH/
ALW-USER-SECU issued commands, UID status depending on whether or not the password is
expired and can no longer be changed, and the time remaining for password expiration. Refer to
6.48 “Disable/Enable User Account” (p. 314).
The system administrator or Nokia account user can retrieve any or all user profile entries. Any
other user can only retrieve their own user profile entry by using the command RTRV-USER.
The RTRV-STATUS command retrieves the address information on all active (connected) and/or
authenticated (logged on) users. The address information (ADDR parameter) consists of either the
user TCP/IP address, if the user is connected by TCP/IP, or the string "DCC", if the user is
connected by means of DCC.
6.76.4 Procedure
1
Select action.
To retrieve user profile information for other user, go to Step 2.
To retrieve own user profile information, go to Step 5.
2
Retrieve user profile information
Enter RTRV-USER-SECU::[UID];
where: UID=User Identifier, specifies a unique user ID. Possible values for UID are: 5 to 12,
case-sensitive alphanumeric characters where the first character must always be an alphabetic
character. The following special characters are also accepted as valid characters and will be
part of the UID: % (percent sign), + (plus sign), # (pound sign), and _ (under score) or ALL for
all of the users defined for the system.
3
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
(
"<UID>:<UAP>:STATE=<value>,PAGE=<value>,PCND=<value>,PCNN=<value>,
POINT=<value>,PAGEXP=<value>,UOUT=<value>,LOGFAIL=<value>,LAST=
<value>,KAMINTVL=<value>,MININTVL=<value>,MXINV=<value>,TMOUT=
<value>" cr lf)+
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
4
Go to Step 7.
5
Retrieve own user profile information
Enter RTRV-USER::[UID];
where: UID=User Identifier, specifies a unique user ID. Possible values for UID are: 5 to 12,
case-sensitive alphanumeric characters where the first character must always be an alphabetic
character. The following special characters are also accepted as valid characters and will be
part of the UID: % (percent sign), + (plus sign), # (pound sign), and _ (under score).
6
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<UID>:<UAP>:STATE=<value>,PAGE=<value>,PCND=<value>,PCNN=<value>,
POINT=<value>,PAGEXP=<value>,UOUT=<value>,LOGFAIL=<value>,LAST=
<value>,KAMINTVL=<value>,MININTVL=<value>,MXINV=<value>,TMOUT=
<value>" cr lf
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
7
Enter RTRV-STATUS;
8
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
(
":<SESSION>,[<UID>]:ADDR=<value>[,LAST=<value>]" cr lf)+
[
/*
<Command
Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
9
STOP. This procedure is complete.
END OF STEPS
6.77.2 Prerequisites
None
6.77.3 General
The NE has one provisionable IP address for all external IP communications via ethernet, local
LAN, and DCC.
The ED-IP-ADDR command sets the TCP/IP stack parameters and controls whether the TCP/IP
stack is enabled/disabled on the NE. Once enabled, TL1 commands may be sent to the NE using
an IP interface.
6.77.4 Procedure
1
Select action.
To retrieve IP address of NE, go to Step 2.
To provision IP address of NE, go to Step 5.
To end this procedure, go to Step 9.
2
Retrieve IP Address of NE
Enter RTRV-IP-ADDR;
3
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"::NEIP=<value>,MASK=<value>,MACADDR=<value> " cr lf
[
/*
<Command
Echo>
[<CTAG>]
(<Session_Number>)*/ cr lf]
;
4
Go to Step 1.
5
Provision IP Address of NE
Enter ED-IP-ADDR::::::[NEIP=][,MASK=];
where:
• NEIP= Internet Protocol address, it is the IP address of the NE. The address 0-0-0-0 is not
allowed. Neither the network nor the host portion of the address when viewed in binary
format may be all 0s or all 1s. Possible values: {1-99, 101-126,128-223} - {0-255} - {0-255} -
{1-254}.
• MASK= Mask, it is the subnet mask of the network the NE is connected to. The mask, in
binary representation, must contain a contiguous string of 1s (the network portion) and a
contiguous string of 0s (the host portion). Possible values: {128-255} - {0-255} - {0-255} - {0-
255}.
6
Enter RTRV-IP-ADDR;
7
Observe output and verify change was made.
8
Go to Step 1.
9
STOP. This procedure is complete.
END OF STEPS
This procedure is used by users with sufficient Security Level privileges to modify and retrieve:
• the provisioned values for the System-Wide user security information
• the security log.
6.78.2 General
The SET-ATTR-SECUDFLT command allows a user with sufficient Security Level privileges to
provision the following values:
• password minimum aging (minimum interval before a user can change the password)
• grace period after the password expiration (interval, after the password expiration, to change the
password)
• number of times that a user can login after the password expiration
• password obsolescence interval (interval after which an expired password can be reused)
• user link inactivity timeout (max interval that the User Session link is inactive, with regards to
user TL1 input, before a user session link time-out occurs)
• user login inactivity timeout (max interval that the User is inactive, without log in the NE, before
that userID is disabled)
• maximum number of failed login attempts
• maximum interval between consecutive failed login attempts
• maximum number of simultaneous sessions for any user
• SECURE/UNSECURE NE mode.
• ICMP enable/disable.
• DHCP enable/disable on CT port.
• Physical ports enable/disable, except Q and F ports. F cannot be disabled (only DHCP can be
disabled on this port) and Q can be disabled via ED-LAN command.
Most of the above described parameters (PAGE, PCNN, PCND, POINT and UOUT) can also be
provisioned on a user basis, by the commands ENT-USER-SECU and ED-USER-SECU.
So the following rule shall be applied for the provisioning of these parameters:
• unless a parameter is specified when entering or editing a user, the value shall be considered
NULL and the system value takes precedence. This way you can change the global value and all
users are affected unless they have had their parameters specifically set.
For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 Transport
Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.
6.78.3 Procedure
1
Login in to NE with an authorized user (i.e. SEC Privileged User, for ex.: USER01).
2
To retrieve provisioned values for the system-wide user security information, enter:
RTRV-DFLT-SECU:[TID]::[CTAG];
Result: Command is completed and retrieval shows system wide security information,
3
To modify system-wide provisioned values, enter:
SET-ATTRSECUDFLT::::::[PAGE=][,PCND=][,PCNN=][,POINT=][,MININTVL=][,
MXINV=][,TMOUT=][,UOUT=][,KAMINTVL=][,MAXSESSION=][,SECACC=][,ICMP=][,
DHCP=] [,PHYSPORTS=];
For parameter descriptions of TL1 commands used in this procedure, refer to the
1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1
Command Guide.
4
Observe the changes entering the retrieve command.
5
To retrieve the parameters in use for the security log enter:
RTRV-ATTR-SECULOG:[TID]::[CTAG];
Result: The list of events that, upon their occurrence, are included in the securitylog (i.e.,
events that are specified for logging, if they occur).
6
To set the parameters in use for the security log enter:
SET-ATTR-SECULOG::::::[LOGEVENT=][,UPSLG=][,WARN=];
Other parameters are optional. If a value is not entered for these parameters, the system will
use the default value. Refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-
160) Release 5.1 TL1 Command Guide for details on parameter values.
END OF STEPS
6.79.2 Prerequisites
None.
6.79.3 General
PM commands operate only on provisioned ports.
6.79.4 Procedure
1
Execute the 6.70 “Report Performance Monitoring (PM) Data” (p. 397) procedure in order to
retrieve the Performance Monitoring data collection for the GBE10, GBE, ODU2, OTU2, MAU,
SDH facilities.
2
Examine output to determine current PM mode, as referred in 6.70 “Report Performance
Monitoring (PM) Data” (p. 397) procedure.
3
Enter SET-PMMODE-x::AID:::LOCN,MODETYPE,[PMSTATE],[DIRN]: [TMPER=];
where:
• x= GBE10, GBE, ODU2, OTU2, MAU, STM1, STM4, STM16, STM64, VC4, VC44C,
VC416C, VC464C, LOVC12, LOVC3.
• AID=Access Identifier, identifies the entity access identifier. Possible values:
− OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-C1 for Client port on a DWLA10X module
- OTU2,, STM-64, 10GE, 10GFC
− GBE-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10 } for GBE Port
− MAU-{1-7}-{1-9}-{2-9,12-19, 21-36}-{1-10} for MAU port on a 10xAny module
− OTODU2-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-{C1, L1}-1 for ODU2 facility in an OTU2on
a DWLA10X module
− OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-L1 for OTU2 Line port,OT2TDM or
DWLA10X module
− STM1-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} for an STM1
− STM4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8} for an STM4
− STM16-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4, 5, 7} for an STM16 on a 2G5SO or 10xANY
− STM64-{1-7}-{1-9}-{2-9,12-19,21-36}-1 for an STM64
− OTPORT-{1-7}-{1-9}-{2-9, 12-19, 21-28, 29-36}-C1 for Client port on a DWLA10X module
- OTU2, STM-64, 10GE)
− STM1AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8}-1 for an AU4 embedded within an STM1
− STM64AU4-{1-7}-{1-9}-{2-9,12-19,21-3 6}-1-{1-64} for an AU4 embedded within an
STM64
− STM16AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4,5,7}-{1-16} for an AU4 in an STM16 on a
2G5SO or a 10xANY
− STM4AU4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8}-{1-4} for an AU4 embedded within an STM4
− VCGVC4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10}-{1-7} for a VC4 within a VCG on a 10xAny
module
− VCGVC4-{1-7}-{1-9}-{2-9,12-19}-{1-64}-{1-64} for a VC4 within a logical VCG on a
Multiservice Packet Card)
− MVC4-{1-7}-{1-9}-{21,22,35,36}-{1-64} for a Modifiable VC4 on LOA card
− STM64AU44C-{1-7}-{1-9}-{2-9,12-19,21-36}-1-
{1,5,9,13,17,21,25,29,33,37,41,45,49,53,57,61} for an AU4-4c embedded within an
STM64
− STM16AU44C-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-4,5,7}-{1,5,9,13} for an AU4-4c in
anSTM16 on a 2G5SO or 10xANY
− STM4AU44C-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-8}-1 for an AU4-4c embedded within an
STM4
4
STOP. This procedure is complete.
END OF STEPS
6.80.2 Prerequisites
None.
6.80.3 General
PM commands operate only on provisioned ports.
PM commands are used to monitor signal overhead that is used to track system efficiency. By
tracking efficiency, users can recognize gradual deterioration of system performance.
The ENT-TH-PROF command creates a new TCA profile instance of a specified profile type.
The new instance of TCAP is created as a clone of the factory default TCAP of the specified type.
The system can support up to 128 total instances of TCA profile for all facility types.
Note, however, internally creating a new TL1 instance may use in the supporting hardware
resources of more than one profile. Depending of the created profile types and their relation to the
supporting HW, the total number of profiles or number of profiles for special types may be reduced.
This may lead to a rejection of the command before the maximum number of 128 profiles is created
for a specific type.
OCn/STMn VCn, LOVCn profile types may use internally 2 instances.
GBE , MAU profile types may use internally 1,5 profile instances.
The RTRV-TH-PROF command retrieves the values of thresholds for the specified monitored types
in a specified profile.
(Only for ETSI application): the command reports a raise threshold (THLEV) and a clear threshold
(THLEVCL).
The clear threshold will be only reported if supported. Only for 15 minutes timer periods the clear
threshold may be supported.
The ED-TH-PROF command modifies values of thresholds for the specified monitored types in a
specified profile.
Only MONTYPES that belong to the profile type of the specified TCAP instance can be modified.
(Only for ETSI applications): the clear threshold (THLEVCL) can be only entered if supported. Only
for 15 minutes timer periods the clear threshold may be supported.
The successful response for an ED-TH-PROF command contains lines of parsable output data for
each montype specified.
6.80.4 Procedure
1
TCA profile instance information
Enter RTRV-TH-PROF::[TCA-AID]:::[PFTYPE][:USERLABEL=]; to retrieve current
threshold levels for the facility.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
2
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[[
"<TCA-AID>,<AIDTYPE>::DFLT=<value>,USERLABEL=<value>"] cr lf
[
"::<MONTYPE>,<LOCN>,<THLEV>,<TMPER>:[DIRN=<value>][,THLEVCL=<value>]"
cr lf]*]* cr lf
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
3
Examine output for threshold information.
4
TCA profile instance creation
Enter:
ENT-TH-PROF:::::PFTYPE:[DFLT=][,USERLABEL=];
where:
• PFTYPE = TCA profile type which new instance is being created.
Possible values:
− {OTU2} (OTU2 profile type)
− {STM1, STM4, STM16, STM64, VC4, VC44C, VC416C, VC464C, LOVC3, LOVC12} ETSI
(SDH profile types)
5
TCA profile instance change
Enter ED-TH-PROF::[TCA-AID]:::[LOCN],[DFLT]:[MONTYPE-TMPER=][,T
HLEV=][,USERLABEL=][,DIRN=][,THLEVCL=];
where:
• TCA-AID= TCA-AID input parameter should be specified only for changing the USERLABEL,
otherwise it should not be entered and it has not any impact on command behavior
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
6
TCA profile instance deletion
DLT-TH-PROF::[TCA-AID]::::[USERLABEL=];
where:
TCA-AID = TCA profile ID which is being deleted. The TCA ID consists of leading string THP
followed by profile type and the digit 2-n for n profiles supported.
Note: The user label assigned to a TCA profile instance required if TCA-AID hasn't been
entered.
7
STOP. This procedure is complete.
END OF STEPS
6.81.2 General
Running BMCA, Slave is able to establish as well as all concurring Masters, which one will be the
Active Master inside a clock domain; it will then answer to this one, without performing any local
selection.
In case of PTP over UDP, each Slave port is able to communicate with Unicast signalling only with
a single Master clock.
Redundancy is obtained, at system level, configuring two slave ports (i.e. TOD Slave Card), each
one belonging to a different clock domain.
The selection among different PTP clock sources (i.e. Master clock) is performed by A-BMCA
mechanism.
The slave clock might be outputted to external equipment via 1pps + ToD interface.
The system supports maximum 4 (as target value) PTP masters for each PTP slave clock.
6.81.3 Procedure
Select action
• Slave TOD Card Creation, go to Step 2
• Phase Synchronization reference configuration, go to Step 9
• Slave TOD Card Deletion, go to Step 12.
2
Slave TOD Card Creation
Enter:
ENT-EQPT::AID::::PROVISIONEDTYPE=PP1588, CKMODE=SLAVE;
where:
• AID = PTP-{1-7}-{1-9}-{2-9,12-19,21-36}. Time Of Day - TOD Card
• CKMODE=SLAVE means that the PP1588 card is configured in Slave Clock Configuration.
Result:
Note: PPS-IN, PPS-OUT and PTPSlave can be selected as input for CRU and for
internal Phase Distributor.
3
Select action:
4
For PPS-IN port the facility PPSIN-r-s-b-1 is created and the following parameters can be
provisioned:
ED-PPSIN::AID::::[CMDMDE=][,TOD=][,DLY=][,ALMPROF=]:[PST];
where:
• AID = PPSIN-{1-7}-{1-9}-{2-9, 12-19, 21-36}-1 (Pulse Per Second Input Port).
I.e PPSIN Access Identifier, specifies the input port receiving the PPS signal
• TOD= Time Of Day, determines if the information about Time Of Day shall be expected as
input (i. e. Sink direction) or sent as output (i. e. Source direction). Values are:
Y Yes. Time Of Day info is expected/sent.
N No. Time Of Day info is not expected/sent.
• DLY = Delay, indicates the delay to be considered by IEEE1588v2 protocol for
synchronization. The delay is due to the lenght of the cable on the link. The lenght
determines a propagation delay equal to D [ns], where D is the value to be provisioned. The
parameter applies to the receiver; normally positive values shall be provisioned; but negative
values can be provisioned as well for compensating excessive dalys provisioned at the oter
side transmitter. The unit of measure is nanosecond.
Note: In addition PPS-IN can be selected as input for CRU and for internal Phase
Distributor.
5
Enter:
RTRV-PPSIN::[AID];
The RTRV-PPSIN command retrieves the provisioning and state information of one or more
ports, in the 1588v2 application, dedicated to the reception of the PPS signal.
Result: The successful response for a RTRV-PPSIN command contains one or more lines of
parsable output data, in ascending order, listing the possible timing input ports used by the
system.
6
For PPS-OUT the facility PPSOUT-r-s-b-1 is created and the following parameters can be
provisioned
ED-PPSOUT::AID::::[S1TRANS=][,TOD=][,DLY=];
where:
• AID = PPSOUT-{1-7}-{1-9}-{2-9, 12-19, 21-36}-1 (Pulse Per Second Output Port)
I.e. Access Identifier, specifies the output port transmitting the PPS signal.
• S1TRANS = {ACT, PRC, SSUL, SSUT, SEC, DUS, NONE}.
Sync message byte to be transmitted, determines if the transmitted byte will have the "DUS"
message or will have the actual traceability of the signal.
• TOD= Time Of Day, determines if the information about Time Of Day shall be expected as
input (i. e. Sink direction) or sent as output (i. e. Source direction). Values are:
Y Yes. Time Of Day info is expected/sent.
N No. Time Of Day info is not expected/sent.
• DLY = Delay, indicates the delay to be considered by IEEE1588v2 protocol for
synchronization. The delay is due to the lenght of the cable on the link. The lenght
determines a propagation delay equal to D [ns], where D is the value to be provisioned. The
parameter applies to the receiver; normally positive values shall be provisioned; but negative
values can be provisioned as well for compensating excessive dalys provisioned at the oter
side transmitter. The unit of measure is nanosecond.
7
Enter:
RTRV-PPSOUT::[AID]:;
To retrieve the provisioning and state information of one or more ports, in the 1588v2
application, dedicated to the transmission of the PPS signal.
Result: The successful response for a RTRV-PPSOUT command contains one or more lines
of parsable output data, in ascending order, listing the possible timing output ports used by
the system.
8
Enter:
RTRV-PTPSLAVE:[TID]:[AID]:[CTAG];
the command retrieves the state information of one or more ports, in the 1588v2 application.
Result: The successful response for a RTRV-PTPSLAVE command contains one or more
lines of parsable output data, in ascending order (from lowest specified PTPSLAVE AID to
the largest specified PTPSLAVE AID), for each PTPSLAVE AID specified.
9
The Phase configuration applies either to input and output direction.
PTPSlave port and PPS Input port can be assigned to phase reference for the selection of
system phase/TOD reference of all PTPMaster ports and PPSoutput ports.
10
Enter:
ED-PHASE::AID::::[SYNCMSG=][,ASSPORTAID=][,PROVQL=][,REFP RIO=];
where:
• AID = Phase Access Identifier, specifies either the phase node for the system phase entity
(delivering the system phase reference PH0) or a phase reference (PPS or Slave Clock port
connected to the phase selection process) to which the command is directed.
Values are:
PHASE-{1-7}-{1-9}-0 (System Phase within a Shelf)
PHASEREF-{1-7}-{1-9}-{0-7} (Source of Phase Reference of a Shelf selectable for System
Phase)
• SYNCMSG = SYNCMSG, determines if the timing reference selection for system phase is
using sync messaging (SSM Qualities) or not.
Values are:
N Sync Messaging is disabled. System phase reference selection is done only by priorities.
Y Sync Messaging is enabled.
System phase reference selection is done by SSM quality levels as first criteria and by
priorities as second criteria.
• ASSPORTAID = ASSPORTAID specifies whether the phase reference is assigned to a port
and if assigned it specifies the AID of the port. The following port types can be used for
establishing a connection towards a timing reference: PPS Input assigned to a phase
reference
Note: The user is able to select the AID of the phase entity to be modified for the Sync
Messaging (SYNMSG) management , specifying if the phase reference selection for
system phase is using sync messaging (SSM Qualities) or not. (Y/N)
11
To configure PTP clock and ports refer to the the CLI command guide.
Note: After the proper configuration of the 1588 port and parameters it is needed to
configure an ELAN service in order to be able to connect the 1588 port with the ‘bridge’
function needed to forward / receive packets to / from the network.
12
Slave TOD Card deletion
Note: The steps below should be done using the SNMP or CLI commands.
13
The ETS Cross-connection should be deactivated and deleted, refer to the the CLI command
guide.
14
Management Operator Disabling of PTP protocol over PTP logical Master port via setting of
ieee1588PtpPortDSAdminStatus to Disabled value. See CLI Command Guide.
15
If PPSIN has been configured as input for CRU (T0 and/or T4) or for internal Phase Distributor,
it has to be de-provisioned.
16
The PTP logical slave port must be disabled at SNMP side. Please refer to the CLI command
guide.
17
The TOD card shall be logically removed.
Enter:
RMV-EQPT::AID;
or
ED-EQPT::AID:OOS;
where:
• AID = PTP-{1-7}-{1-9}-{2-9,12-19,21-36}. Time Of Day - TOD Card
Note: TOD Card logical removal is mandatory also for avoiding traffic hits upon NGI links
of otherCollector cards eventually present in the shelf.
18
Enter:
DLT-EQPT::AID;
where:
• AID = PTP-{1-7}-{1-9}-{2-9,12-19,21-36}. Time Of Day - TOD Card
Result: The command causes the Deactivation/Deletion of PTP Master logical port (both
SNMP and TL1 side), of PPSIN and PPSOUT ports.
END OF STEPS
6.82.2 Prerequisites
None.
6.82.3 General
The procedure retrieves the system's output response (site) header. The output response header
consists of the site identifier (SID) and the current system date and local time.
The ED-DAT command sets the system date and time. Changing the system date or time could
result in partial or incomplete PM data.
The ED-DAT command is not allowed if NTP is enabled.
6.82.4 Procedure
1
Select action.
To retrieve system date and time, go to Step 2.
To change system date and time, go to Step 5.
2
Retrieve System Date and Time
Enter RTRV-HDR:::::[PC];
3
Examine output to determine current date and time, which appears on the first line, as detailed
in the relevant command guide, refer to “Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
4
Is it necessary to change date and time?
If yes, go to Step 5.
If no, go to Step 7.
5
Change System Date and Time
Enter ED-DAT:::::DATE,TIME;
where:
• DATE=identifies the new system date in the format of <YY>-<MM>-<DD>.
• TIME=identifies the new system time in the format of <HH>-<MM>-<SS>. The entered value
should be the actual desired local time to be displayed by the NE, not modified by any offset.
6
Go to Step 2 in order to check the changes.
7
STOP. This procedure is complete.
END OF STEPS
6.83.2 Prerequisites
None.
6.83.3 General
Most of the described parameters (PAGE, PCNN, PCND, POINT and UOUT) can also be
provisioned on a user basis, by the commands ENT-USER-SECU and ED-USER-SECU. So the
following rule shall be applied for the provisioning of these parameters: unless a parameter is
specified when entering or editing a user, the value shall be considered <null> and the system
value takes precedence. This way you can change the global value and all users are affected
unless they have had their parameters specifically set.
Note: In the rule above must be considered that, however, the changes to system values shall
take effect immediately only on currently not logged on users, while for logged on users they
shall take effect only after logout. Anyway, the modified system values shall be retrievable by
RTRV-DFLT-SECU.
6.83.4 Procedure
1
Select action.
To retrieve default security parameters, go to Step 2.
To set default security parameters, go to Step 5.
2
Retrieve Default Security Parameters
Enter RTRV-DFLT-SECU;
3
Observe output, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
":/"DEFAULTS
/":PAGE=<value>,PCND=<value>,PCNN=<value>,POINT=<value>,KAMINTVL=
<value>,MAXSESSION=<value>,MININTVL=<value>,MXINV=<value>,TMOUT=
<value>,UOUT=<value>" cr lf
[
/*
<Command
Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
4
Is it necessary to change parameters?
If yes, go to Step 5.
If no, go to Step 6.
5
Set Default Security Parameters
Enter SET-ATTR-SECUDFLT::::::[PAGE=][,PCND=][,PCNN=][,POINT=]
[,MININTVL=][,MXINV=][,TMOUT=][,UOUT=][,KAMINTVL=] [,MAXSESSION=];
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
6
STOP. This procedure is complete.
END OF STEPS
6.84.2 Prerequisites
STMn facilities must be provisioned. Refer to 6.31 “ Administer STMn Facility” (p. 235).
STMn facilities must be provisioned as a facility protection group (FFP). Refer to 6.32 “Administer
STM-n Facility Protection Group” (p. 237).
6.84.3 General
When initiating a protection switch using OPR-PROTNSW-STMn, options for the switch command
(SWTCHCMD) parameter available for STM-1, STM-4, STM-16, and STM-64 are: FRCD,,
LOCKOUT, MAN.
• Lockout of Protection (LOCKOUT) keeps traffic on the working facility. If traffic is on the protect
facility when the command is issued, traffic switches to the working facility and remains there
until the lockout is released. For this switch command, the protect AID must be specified. A
Lockout overrides a Forced Switch and a Manual Switch.
• Forced Switch (FRCD) forces traffic to either the working facility or the protect facility. Specifying
a working AID forces the traffic to the protect facility, and specifying a protect AID forces traffic to
the working facility in the case of Linear MSP. A Forced Switch overrides a Manual Switch.
• Manual Switch (MAN) moves traffic to either the working facility or the protect facility. Specifying
a working AID moves the traffic to the protect facility, and specifying a protect AID moves traffic
to the working facility.
Additional switch commands are available for STM-16 and STM-64 facilities: FRCD-R, LOP-S,
LOW-R, and MAN-R.
• Forced Switch of working to Protection-Ring (FRCD-R) is applicable to AIDs in a 2FMS-SPRING
protection group. This command performs the ring switch from the working channels to the
protection channels for the span between the node at which this command is initiated and the
adjacent node. This switch occurs regardless of the state of the protection channels, unless the
ring is satisfying a higher priority request than the forced switch such as lockout of protection.
• Lockout of Protection-Span (LOP-S) is applicable to AIDs in a 2FMS-SPRING protection group.
This command prevents protection switching on the entire ring. If any working traffic is using the
ring protection channels, this command causes working traffic to be switched back to the
working channels regardless of the condition of the working channels.
• Manual Switch of Working to Protection-Ring (MAN-R) is applicable to AIDs in a 2FMS-SPRING
protection group. This command performs the ring switch from working channels to the
protection channels for the span between the node at which this command is initiated and the
adjacent node.
• LOW-R (MS-SPRING) Lockout of working channels - ring switch. This command shall prevent
the working channels over the addressed span from accessing the protection channels for a ring
switch by disabling the node's capability to request a ring switch for the working channels on the
addressed span. If any working channel is already on protection, the ring switch is dropped
regardless of the condition of the working channels. If no other request area active on the ring,
the No Request code is transmitted (this is because the lockout of protection - all spans
command applies only to the protection channel and not the working channels. This command
has no impact on the use of the protection channels for any other span (e.g., the node can go
into pass-through mode). Note that this command is not signalled on the MSP channel.
The RINGID parameter of the ENT-FFP-STM16/STM64 command must be properly provisioned if
automatic learning of squelch maps and ring maps is enabled. This parameter identifies a MS-
SPRING within a shelf and must be unique to the system and common across a MS-SPRING. It
has no significance when the automatic learning protocol is not enabled.
For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 Transport
Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.
6.84.4
1
Select action.
To retrieve information on STMn facilities and FFP, go to Step 2.
To initiate STMn switch to protection, go to Step 7.
To release STMn switch to protection, go to Step 9.
To end this procedure, go to Step 11.
2
Retrieve Information on STMn Facilities and FFP
Enter RTRV-STMn::[AID];
where:
STMn=Optical facility type (STM1, STM4, STM16, or STM64).
AID=STMn Access Identifier
3
Examine output. Note states and other pertinent information.
4
Enter RTRV-FFP-STMn::[AID];
where:
STMn=Optical facility type STM1, STM4, STM16, or STM64).
5
Examine output. The output response displays FFP information about the specified AID. No
information displays for ports that are not in an FFP group.
6
Go to Step 1.
7
Perform STMn Protection Switch
Enter OPR-PROTNSW-STMn::AID:::SWTCHCMD;
where:
STMn=Optical facility type (STM1, STM4, STM16, or STM64).
AID=STMn Access Identifier
SWTCHCMD={FRCD, LOCKOUT, MAN} for Linear protections
8
Go to Step 1.
9
Release STMn Protection Switch
Enter RLS-PROTNSW-STMn::AID;
where:
STMn=Optical facility type (STM1, STM4, STM16, or STM64).
AID=STMn Access Identifier
10
Go to Step 1.
11
STOP. This procedure is complete.
END OF STEPS
6.85.2 Prerequisites
VC-n path facilities must be provisioned.
STM-n facilities that support the VC-n must be provisioned for SNCP/UPSR.
6.85.3 General
OPR-PROTNSW-<rate> will be used for initiating of switch commands for SNCP or UPSR.. The
command initiates external switch requests for path protected cross-connections of type
2WAYSNCP and 1WAYSNCP. The command requests the system to switch the path selector to the
protected or protecting path of the SNCP. User switch requests initiated with this command remain
active until they are released via the RLS-PROTNSW-<rate> command or overridden by a higher
priority protection switch request.
When initiating a protection switch using OPR-PROTNSW-<rate>, three options for the switch
command (SWTCHCMD) parameter are available: LOCKOUT, FRCD, and MAN. When the
command executes, the path selector switches to the specified destination facility (WKG -
FROMPED/PREFFERED or PROTN - FROMPING/ALTERNATE). If the new external request is
higher priority than the current request for the group and in the event that the switch/selector is
already at the destination position, then no switch actually occurs, but the switch state and
conditions are updated to match the new current request.
For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 Transport
Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.
6.85.4
1
Select action.
To retrieve information on VC-n facilities, go to Step 2.
To retrieve VC-n cross-connections, go to Step 5.
To perform VC-n switch to protection, go to Step 8.
To release VC-n switch to protection, go to Step 10
To end this procedure, go to Step 12.
2
Retrieve Information on VC-n Facilities
Enter RTRV-VCn::[AID];
where:
VCn/STSn=Facility type{VC4, VC44C, VC416C, VC464C, LOVC12, LOVC3)
3
Examine output. Note states and other pertinent information.
4
Go to Step 1.
5
Retrieve VC-n Cross-Connections
Enter RTRV-CRS-VCn/STSn::AID;
where:
VCn/STSn=Facility type{VC4, VC44C, VC416C, VC464C, LOVC12, LOVC3)
AID=VCn facility access identifier
6
Examine output. Note active cross-connections.
7
Go to Step 1.
8
Perform VCn Protection Switch
Enter OPR-PROTNSW-<rate>::AID:::SWTCHCMD;
where:
rate=VCn/STSn Facility type, i.e. VC4, VC44C, VC416C, VC464C, LOVC12, LOVC3.
AID=VCn facility access identifier
SWTCHCMD=Switch command (LOCKOUT, FRCD, MAN)
9
Go to Step 1.
10
ReleaseVC-n Protection Switch
Enter RLS-PROTNSW-<rate>::AID;
where:
rate=VCn Facility type, i.e. VC4, VC44C, VC416C, VC464C, LOVC12, LOVC3.
AID=VCn/STSn facility access identifier
11
Go to Step 1.
12
STOP. This procedure is complete.
END OF STEPS
6.86.2 General
The ED-SECU command is used by an user with security administrator privileges to change the
ASAPSECU assignment for the AID SECU, which supports the INTRUSION alarm.
When the ASAPSECU assignment is changed, the NE recalculates the INTRUSION severity
according to the new assigned ASAPSECU contents.
If the same userID tries unsuccessfully (wrong password) to connect to the same NE for a
configurable number of times, the NE performs the following actions:
• locks out the user ID until the user ID is re-enabled by a security administrator using ALW-USER-
SECU. The lockout shall be accomplished in the same way as for the maximum number of
invalid login attempts
• records in the security log the IP address of the source along with the user ID
• reports an intrusion standing condition (REPT ALM SECU and REPT EVT SECU TL1
autonomous messages shall provide this functionality. See Table SECU-2 for all supported
security conditions).
The RTRV-ALM-SECU command retrieves the current status of any security alarmed standing
condition. The only security standing condition supported in this release is INTRUSION.
In this release, the INTRUSION condition can be assigned with alarm severity only (see ED-SECU).
If multiple INTRUSION alarms exist, multiple parsable output data are reported, with a single line of
parsable output data for each SECU-UID, with CONDDESCR indicating the UID, and associated
remote port address, for which the INTRUSION has been detected.
An INTRUSION alarm is cleared when the UID - for which INTRUSION has been arised - is deleted
or reallowed. The UID is deleted, via DLT-USER-SECU, when the secu admin considered the
INTRUSION a real attack, while is re-allowed, via ALW-USER-SECU, when the secu admin
considered the INTRUSION a simple mistake by a valid UID.
For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 Transport
Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.
6.86.3 Procedure
1
Login as ADMIN user and create new ASAP for the secu admin.
2
Set Notification Code to one of the possible values (Cleared Alarm, Critical Alarm, Major Alarm,
Minor alarm, Warning alarm) for INTRUSION condition.
Note: Notification Code, identifies the type of alarm generated by the system upon
occurrence of the event identified by the CONDTYPE. CL Cleared Alarm CR Critical alarm
MJ Major alarm MN Minor alarm WR Warning Alarm
3
Login as an user with security administrator privileges.
4
The user with security administrator privileges changes the ASAPSECU in order to arise the
INTRUSION alarm.
To associate new ASAP to SECU enter:
ED-SECU::[AID]::::ALMPROF=;
where:
ALMPROF = is the userlabel which identifies the Alarm Severity Assignment profile (ASAP)
name.
5
Enter: RTRV-ALM-SECU::[AID]:::[NTFCNCDE],[SECUCONDTYPE];
the CONDDESCR parameter within the output data indicates all UIDs, and associated remote
port address, for which the INTRUSION has been detected.
7
Enter:
DLT-USER-SECU::UID;
where.
8
Enter:
ALW-USER-SECU:::::UID;
where.
UID = User Identifier, specifies a unique user ID.
Result: The NE clears the INTRUSION alarm for that UID.
END OF STEPS
Administrator with security administration privileges, (that means with UAP including SEC) is able
to:
• Add users to the NE and delete users from the NE,
• Edit and retrieve the security information of any user,
• Change the password of other users without entering the old password,
• Logoff a particular user
• Obtain user info about the user currently logged on to the NE (included users that are logged
with DEBUG,CLI and ZIC sessions),
• Inhibit and allow users,
• Set system wide user security attributes and retrieve the security information about
authenticated and unauthenticated session.
A normal user (i.e., a user without security administration privileges, that means with UAP not
including SEC) is able to:
• Establish a session with the NE (logon),
• Change own user password,
• Obtain own user info,
• Retrieve system wide user security attributes,
• Retrieve command privilege partitioning,
• Terminate the session (logoff),
• Execute accessible/privileged NE command language requests.
6.88.2 Prerequisites
None.
6.88.3 General
The ways are provided for enabling/disabling VCG members:
• the first one, via NUMPATH parameter, addresses a range of members;
• the second one, via PROVMBRID parameter, addresses a single member. This second way can
be allowed only if LCAS is enabled.
Both NUMPATH and PROVMBRID parameters can not be specified at the same time in the
command.
The command is denied if the NUMPATH exceeds the maximum number of members within the
addressed VCG.
6.88.4 Procedure
1
Enter CNTRL-VCPATH::AID::::ACTSTATE=[,NUMPATH=][,PROVMBRID=];
where:
• AID=VCG Access Identifier, specifies the VCG entity. Possible values:
− VCG-{1-7}-{1-9}-{2-9,12-19}-{1-124} (Logical VCG for ethernet switching on a PP10AD
module)
− GBEVCG-{1-7}-{1-9}-{2-9,12-19,21-36}- {1-10} (VCG on a GBE port on a 10xAny module)
− MAUVCG-{1-7}-{1-9}-{2-9,12-19,21-36}- {1-10} (VCG on a MAU port on a 10xAny module)
• ACTSTATE = Activation State. The state to which the addressed paths are set to. Possible
values:
− ACTIVE Active State. The paths are set to VCACT state thereby allowing traffic to flow
through the path.
− IDLE Idle State. The paths are set to VCIDLE state thereby stopping traffic to flow through
the path.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
Example: In the following example, all the members of the VCG number 3 on the Multiservice
collector card in slot 5 are being disabled from sending traffic.
CNTRL-VCPATH::VCG-1-3-5-3::::ACTSTATE=IDLE,NUMPATH=ALL;
In the following example, all the members of the VCG number 7 on the 10XANY module in slot
5 are being disabled from sending traffic.
CNTRL-VCPATH::GBEVCG-1-1-5-7::::ACTSTATE=IDLE,NUMPATH=ALL;
2
Examine output.
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
/*
<Informational_Description_Text>
*/ cr lf]
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
3
STOP. This procedure is complete.
END OF STEPS
This procedure provides instructions for the operator to change the following provisioned and
operating cards:
• PP1GE or PP1GESY card with 10x1GE ports, into a PP1GEX20 or PP1GE20E card with
20x1GE ports, saving all the Transmission provisioning over the original ports (Modify 10G to
20G).
• PP10GE or PP10GESY card with 1x10GE port, into a PP10GEX2 or PP10GE2E card with
2x10GE ports, saving all the Transmission provisioning over the original ports (Modify 10G to
20G).
• PP10GE2E (enhanced) card with 2x10GE ports, into a PP10GE10 card with 10x10GE ports,
saving all the Transmission provisioning over the original ports (first 2 ports on the new card).
• PP10GE2E (enhanced) card with 2x10GE ports, into a PP10GE6 card with 6x10GE ports,
saving all the Transmission provisioning over the original ports (first 2 ports on the new card).
6.89.2 General
This Equipment CARD Change (provisioning and physical) must be supported saving any NE & NM
side current configuration on the supported transmission services.
All the involved cards (original and final ones) must be part of the current NE release card list.
The command is denied even if one feature available in the modified card, is not available in the
new card.
The following table depicts the features that are available or not available, comparing the AID to be
modified with the allowed new AID.
The MODIFY-EQPT command prepares the addressed card for modifying the AID and
PROVISIONEDTYPE parameters with a following execution command.
The MODIFY-EXEC command executes ALL the pending NE card modifications for the new AID and
PROVISIONEDTYPE parameters.
The operation is called Modify Equipment or Density Upgrade, and is performed in the following
phases:
• Preparation phase (started with the TL1 command MODIFY-EQPT on each interested PP Card)
• Execution phase (started with the TL1 command MODIFY-EXEC for addressing the related NE
Upgrade)
During the modify phases, the following equipment commands are denied on the cards/SFPs
involved in the change:
• DLT-EQPT (deletion)
• ED-EQPT (edit)
• ENT-EQPT (creation)
• INIT-SYS (restart)
6.89.3 Procedure
1
Enter RTRV-EQPT::ALL;
where ALL means all the AID.
2
Examine the response and determine which card you want to change.
Original card Modified card
PP1GE PP1GEX20 or PP1GE20E
PP10GE PP10GEX2 or PP10GE2E
PP10GEX2 PP10GE6 or PP10GE10
3
To remove the card from the shelf, enter MODIFY-EQPT:[TID]:AID:[CTAG]:::NEWAID=,
NEWPROVISIONEDTYPE=:;
where:
• AID = Equipment Access Identifier, identifies the equipment entity access identifier.
− PP1GE-{1-7}-{1-9}-{2-9,12-19} UNIV (Packet Module 10x1Gb)
− PP10GE-{1-7}-{1-9}-{2-9,12-19} UNIV (Packet Module 1x10Gb)
− PP10GEX2-{1-7}-{1-9}-{2-9,12-19} ENH (Packet Module 2x10Gb)
• NEWAID = Equipment Access Identifier, identifies the equipment entity access identifier.
− PP1GEX20-{1-7}-{1-9}-{2-9,12-19} UNIV (Packet Module 20x1Gb)
− PP10GEX2-{1-7}-{1-9}-{2-9,12-19} UNIV (Packet Module 2x10Gb)
− PP10GE10-{1-7}-{1-9}-{2,4,6,8,12,14,16,18} ENH (Packet Module 10x10Gb)
4
Enter RTRV-MODIFY-EQPT:[TID]:AID:[CTAG]; to view the pending AID and
PROVISIONEDTYPE parameter modifications set with the MODIFY-EQPT command.
5
Enter MODIFY-EXEC:[TID]::[CTAG]::[MODE];
where:
• MODE = Nokia Command Mode, identifies the Command Execution Mode.
− NORM Normal, the command is denied if the result of its execution is service affecting.
− FRCD Forced, the command is completed even if the result of its execution is service-
affecting.
Result: Both the Shelf Controllers are restarted. The autonomous notification,
REPT^MODIFY, with the output parameters: MODIFYCMD=; STATUS=; RESULT=, is sent at
the start and completion of processing of the command.
6
Insert the new card into the vacant slot and wait for it to initialize.
7
Enter RTRV-EQPT::ALL; and verify that the AID and PROVISIONEDTYPE match the new
card.
8
STOP. This procedure is complete.
END OF STEPS
6.89.5 Purpose
This procedure provides instructions for the operator to change the following provisioned and
operating cards:
• PP1GEX20 (legacy) card with 20x1GE ports, into a PP1GE20E (enhanced) card with 20x1GE
ports, saving all the Transmission provisioning over the original ports (Modify 20G to 20G).
• PP10GEX2 (legacy) card with 2x10GE ports, into a PP10GE2E (enhanced) card with 2x10GE
ports, saving all the Transmission provisioning over the original ports (Modify 20G to 20G).
6.89.6 General
This Equipment CARD change (provisioning and physical) must be supported saving any NE & NM
side current configuration on the supported transmission services.
All the involved cards (original and final ones) must be part of the current NE release card list.
The cards PP1GEX20 to PP1GE20E and PP10GEX2 to PP10GE2E are compatible.
RTRV-COMPATIBLE and ED-EQPT commands are used to modify the cards.
The RTRV-COMPATIBLE command retrieves all the provisioned type values allowed to an
provisioned/unprovisioned slot, pim or port.
If the addressed AID is provisioned, the output is a sequence of rows, one for each provisioned type
value:
• Allowed by the ED-EQPT command as a substitute for the current provisioned type (that is
without deleting and re-entering the addressed AID). (Logically compatible)
• The output parameter MDFTYPE in this case, is returned with the value CHNGTYPE.
The ED-EQPT command modifies provisioning parameters for the specified equipment.
Ability to modify the provisioned module type is supported by the provisioned type parameter. This
is a limited capability to allow substitution of compatible module types in certain cases or to change
XFP/SFP features (short/long/intraoffice haul and so on).
6.89.7 Procedure
Perform the following steps:
1
To retrieve the compatible cards, enter RTRV-COMPATIBLE:[TID]:AID:[CTAG];
where:
AID = Equipment Access Identifier, identifies the equipment entity access identifier.
• PP1GEX20-{1-7}-{1-9}-{2-9,12-19} (Packet Module 20x1Gb)
• PP10GEX2-{1-7}-{1-9}-{2-9,12-19} (Packet Module 2x10Gb)
2
To modify the retrieved compatible cards, enter ED-EQPT:[TID]:AID:[CTAG]:::
[PROVISIONEDTYPE=][,AINSMODE=][,ALMPROF=] [,CMDMDE=][,APTMODE=][,
VOAMODE=][,APSD1=][,APSD2=][,OPWRL1=][,OPWRL2=][,VOA=][,EOLSPAN=]
[,N1=][,PCH1=][,IT=][,LAMBDASET=][,OPWRLOT2=][,SSBIT=]:[PST];
where:
• AID = Equipment Access Identifier, identifies the equipment entity access identifier.
− PP1GEX20-{1-7}-{1-9}-{2-9,12-19} (Packet Module 20x1Gb)
− PP10GEX2-{1-7}-{1-9}-{2-9,12-19} (Packet Module 2x10Gb)
• PROVISIONED TYPE = AID of the provisioned type.
− PP1GEX20 UNIV Packet Module 20x1GbEthernet (Packet Module 20G)
− PP1GE20E Packet Module 20x1GbEthernet Evolution (20G)
− PP10GEX2 UNIV Packet Module 2x10GbEthernet (Packet Module 20G)
− PP10GE2E Packet Module 2x10GbEthernet Evolution (20G)
For parameter descriptions of TL1 commands used in this procedure, refer to the
1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1
Command Guide
3
Enter RTRV-EQPT::ALL; and verify that the AID and PROVISIONEDTYPE match the new
card.
4
STOP. This procedure is complete.
END OF STEPS
7.1 Overview
7.1.1 Purpose
The system supports the provisioning and management of a new shelf type (“enhanced shelf”) to
improve cost optimization respect to the current available for TSS-320 equipment.
The new shelf model is referenced as S320H for comparison respectively with current supported
model (UNVRSL320).
The Detailed Level Procedures (DLP) contains detailed steps and supporting information required
to complete a task.
When a DLP is referenced from another part of the manual, perform the DLP, then return to the
point where the DLP was referenced.
7.1.2 Contents
7.2.2 Prerequisites
The Enhanced Shelf version is S320H (ENH Shelf 320). Mandatory equipment shall be
automatically provisioned whether present or not.
7.2.3 General
The procedure assigns an equipment object entity at the AID physical location and provisions the
specified equipment (also called pre-provisioning) regardless of whether the equipment is installed
in the system.
Non-mandatory equipment can be provisioned regardless of actual presence in the system.
Non-mandatory equipment can be pre-provisioned; the slot is provisioned in advance of a card
being inserted.
New shelves types (“enhanced shelf”) have been introduced to improve cost optimization respect to
the current available for TSS-320 equipment. The new shelf model is referenced as S320H for
comparison respectively with current supported model (UNVRSL320):
The AINSMODE parameter is used to specify if an alarm is generated due to an unplugged module.
A value of AINS indicates no alarm is generated due to an unplugged module. A value of NOWAIT
indicates an alarm is generated due to an unplugged module.
The PROVISIONEDTYPE parameter identifies the Nokia mnemonic stored in the Remote Inventory
EPROM for the module. It is mandatory to specify this parameter for XFP/SFP modules.
The value ANY is used for generic XFP/SFP.
Once equipment is provisioned, ED-EQPT can be used to alter parameters.
7.2.4 Procedure
1
Verify the shelf type entering RTRV-EQPT::ALL;
where ALL means all the AID.
2
Examine the response, as detailed in the relevant command guide, refer to “Command details”
(p. 107).
3
Select action.
For Shelf provision, go to Step 4.
For Unit provision, go to Step 7.
For XFP/SFP module provision, go to Step 10.
4
Shelf provision
where:
• SHELF-{1-7}-{1-9}=Equipment Access Identifier, identifies the equipment entity access
identifier in the {RACK}-{SHELF} format.
• PROVISIONEDTYPE parameter with the value S320H for ENH Shelf 320 HT
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
Note:
When a Shelf is provisioned, the following Mandatory Equipment Entities are
automatically created:
• MXEC320 (Slot ID 1-20 is associated to Slot 10-11)
• PSF320H (slot IDs: 37 and 39)
• TBUS320 (slot IDs: 42 and 43)
• FAN320H (slot ID 40)
• new EOS card housekeeping (Slot ID 45)
6
Go to Step 7.
7
Unit provision
Verify the unit is in appropriate slot. Refer to the figures below:
8
Enter ENT-EQPT::AID::::[PROVISIONEDTYPE=][,AINSMODE=][,SHELFNUM=][,
SHELFROLE=][,LAMBDASET=][,ALMPROF=][,CLNTSEL=][,OPWRLOT2=][,SSBIT=]:
[PST];
where:
• AID=Equipment Access Identifier, identifies the equipment entity access identifier. Possible
values: refer to B.3 “AIDs” (p. 692) or to “Command details” (p. 107).
• PROVISIONEDTYPE = Nokia mnemonic stored in the Remote Inventory EPROM for the
given equipment.
For possible values please refer to B.4 “Provisioned Types” (p. 693).
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
For Card's administration details please refer to 7.3 “Administer S320H module” (p. 455).
9
Is the board provided with an XFP or SFP module?
If yes, go to Step 10.
If no, go to Step 12.
10
XFP/SFP module provision
Verify the XFP/SFP module on the board (ref. to Table 59, “Supported SFP/XFP Optics
Modules - Client Side” (p. 692)).
11
Enter ENT-EQPT::AID::::PROVISIONEDTYPE=[,AINSMODE=][,SHELFNUM=][,
SHELFROLE=][,APTMODE=][,VOAMODE=][,APSD1=][,APSD2=][,OPWRL1=][,
OPWRL2=][,VOA=][,EOLSPAN=][,N1=][,PCH1=][,IT=][,LAMBDASET=][,ALMPROF=
][,CLNTSEL=][,OPWRLOT2=][,SSBIT=]:[PST];
where:
• AID=Module Access Identifier previously referred in Step 8
• PROVISIONEDTYPE= Nokia mnemonic stored in the Remote Inventory EPROM for the
given equipment. It is mandatory to specify this parameter for XFP/SFP modules (ANY-
<type> is used for generic MSA XFP/SFP). For details see B.4 “Provisioned Types” (p. 693).
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
12
STOP. This procedure is complete.
END OF STEPS
7.3.2 General
New shelf equipment for TSS-320 is provisioned with TDM, (High Order), ODU or Packet Module
cards with enhanced switching capability (including optical cards from PSS equipment), taking into
account that:
• The even slots (2, 4, 6, etc..) shall support a potential traffic capability up to 100 Gb/s
• The odd slots (3,5,7 ,etc.) shall support a potential traffic capability up to 60 Gb/s
Note: The potential switching capability of the new TSS-320 shelf (full equipped) shall be
extended up to 1280 Gb/s (160Gb/s x 8) 4)
The following card types (from Rel.4.0) are not supported in the new shelf: · LOA10G,
LOFA1111, CWLA, CADM, CMDX, OMDX8
Two new 20GbE Packet Module enhanced cards are present, (1 slot wide ) optimized for cost
reduction:
• 20x1GbE enhanced card with pluggable SFP modules.
The 20x1GbE enhanced card supports 100-FX physical SFP module type and it is capable to
perform Ethernet loopback facility (both line and internal)
• 2x10GbE enhanced card with pluggable XFP modules.
The 2x10GbE enhanced card supports OTU-2 termination (HW ready) and it is capable to
perform Ethernet loopback facility (both line and internal)
The system provides provisioning and management of a server card in order to support 1588v2 and
Time of Day functionality (TOD card).
The ED-EQPT command modifies provisioning parameters for the specified equipment.
Executing an ED-EQPT command with a specific PST value causes state transitions for the
specified module.
If the PST is set to IS the command behaves like RST-EQPT, with the same capabilities and
restrictions described for that command, causing the specified equipment to be placed in the IS or
OOS-AU primary state.
If the PST is set to OOS the command behaves like RMV-EQPT, with the same capabilities and
restrictions described for that command, causing a primary state transition from IS or OOS-AU to
OOS-MA or OOS-AUMA respectively.
Note: The auto-provisioning functionality, that is the automatic board provisioning after its
plugging-in, is activated or not according to the PROVMODE parameter value set with the
SET-PRMTR-NE command.
7.3.4 Procedure
Select action:
• To retrieve board information, go to Step 2.
• To provision boards, go to Step 5.
• To remove boards, go to Step 10.
• To restore boards, go to Step 17.
2
Retrieve board information
Enter:
RTRV-EQPT::ALL;
AID=ALL, means that all the equipments residing in the NE, both provisioned and not-
provisioned, are returned.
3
Observe output.
4
Go to Step 1.
5
Provision board
Enter ENT-EQPT::AID::::[PROVISIONEDTYPE=][,AINSMODE=][,SHELFNUM=][,
SHELFROLE=][,LAMBDASET=][,ALMPROF=][,CLNTSEL=][,OPWRLOT2=][,SSBIT=]:
[PST];
where:
• AID=Equipment Access Identifier, identifies the equipment entity access identifier. Possible
values see “Procedure” (p. 457).
• PROVISIONEDTYPE = Nokia mnemonic stored in the Remote Inventory EPROM for the
given equipment.
For possible values please refer to “Procedure” (p. 457).
6
Retrieve the provisioned card and verify its state. For details see Step 2.
7
Observe output.
Note: Executing an ENT-EQPT causes a primary state transition for the specified
equipment entity, as follows:
• If PST=IS to OOS-AU
• If PST=OOS to OOS-AUMA
8
Go to Step 1.
9
Modify board parameter value
Enter:
ED-EQPT::AID::::[PROVISIONEDTYPE=][,AINSMODE=][,ALMPROF=][,LAMBDASET=]
[,OPWRLOT2=][,SSBIT=]:[PST];
where:
• AID = Equipment Access Identifier, identifies the equipment entity access identifier
• PROVISIONEDTYPE = The Nokia mnemonic stored in the Remote Inventory EPROM for the
given equipment.
• PST = Primary State, specifies the primary state to which the equipment is set. Possible
values are: IS, OOS.
For possible AID and PROVISIONEDTYPE values please refer to “Procedure” (p. 457).
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
Example: The following command performs logical removal for the module 10GSO-1-1-5.
ED-EQPT:: 10GSO-1-1-5:::::OOS;
10
Remove board
RTRV-EQPT::AID;
where:
• AID = Equipment Access Identifier, identifies the equipment entity access identifier
11
Observe output.
12
Is the equipment entity is already in OOS-MA or OOS-AUMA state?
If YES, go to Step 1.
13
Is the module active or NOT switched to protection?
Select:
• Yes, go to Step 14.
• No, go to Step 15
14
A module which is NOT switched to protection (regardless of whether the ports are provisioned
on it or paths are cross connected) can be logically removed only with the MODE parameter set
to FRCD. the same for an active module, only the MODE=FRCD is accepted, and it is up to the
operator to manually execute the switch to the other copy before or after the logical removal of
the module.
15
Enter:
RMV-EQPT::AID:::NORM;
16
Go to Step 1.
17
Restore board
Enter:
RTRV-EQPT::AID;
where:
• AID = Equipment Access Identifier, identifies the equipment entity access identifier
18
Observe output.
19
To place in the IS or OOS-AU primary state specified equipment, enter
RST-EQPT::AID:::[MODE];
where:
• AID = Equipment Access Identifier, identifies the equipment entity access identifier
• MODE = Command Mode, identifies the Command Execution Mode. Values are:
NORM Normal, the command is denied if the result of its execution is service-affecting.
FRCD Forced, the command is completed even if the result of its execution is
service-affecting. Forced mode is used also to force a transition from OOS-AUMA,FLT to
OOS-AU,FLT state.
END OF STEPS
8.1 Overview
8.1.1 Purpose
The Detailed Level Procedures (DLP) contains detailed steps and supporting information required
to complete a task. When a DLP is referenced from another part of the manual, perform the DLP,
then return to the point where the DLP was referenced.
8.1.2 Contents
8.2.2 General
The loopback functionality on Terminal MEP and MIPs are supported for the following purposes:
• In-Service Diagnostic Test: it provides information only about the reachability of specified
destination.
• On-demand bidirectional connectivity verification: this implies the verification that in the
indicated destination there is the match of the expected MEG/MEP IDs
It is possible to insert Test TLV with PRBS payload in the Loopback OAM PDU.
When the LBM packet is sent to a target MEP, following configurations shall be possible:
• Target MEP ID
• PHB
• Packet Length
• LBM packet interval
• Start Date & TIME, and End Date & TIME, or Number of LBM frames to be sent
• Whether Requesting MEP ID shall be included or not in transmitted LBM frame (this optionally
and implies the activation of bidirectional connectivity verification).
• Whether Test TLV shall be included or not in transmitted LBM frame with the possibility to
configure Test-Type
When the LBM packet is sent to a target MIP, the source MEP MUST know the hop count to the
target MIP and set the TTL field accordingly.
In case of connectivity verification the configuration of the following parameters is needed for the
MIP:
• MEG ID
• Expected MEP ID
Besides when the LBM packet is sent to a target MIP the following configurations shall be possible:
• TTL (Time To Live)
• Target MIP-ID (includes Node and Port Identifiers).
• PHB
• Packet Length
• LBM packet interval
• Start Date & TIME, and End Date & TIME, or Number of LBM frames to be sent Activation of
bidirectional connectivity verification (this can be done only if the source MEP and the target
MIP have been configured with all expected parameters).
• Whether Test TLV shall be included or not in transmitted LBM frame with the possibility to
configure Test-Type.
It is possible to have more LoopBack Tool instances from this TUSEG (=MEP) to different MEP/MIP
with the following restrictions:
• one tool for each <AID, TARGET-MEPID>
• one tool for each <AID, TARGET-MEPID, DISCOVERY>
• one tool for each <AID, TARGET-MIPID>
• one tool for each <AID, TARGET-MIPID, DISCOVERY>
The System can send max 1024 LBM packets for this LB-Tool.
8.2.4 LB Output
The RTRV-TMPLS-ODLB-OUTPUT command retrieves the measurement results from the on-
demand loop back instance entered with ENT-TMPLS-ODLB/ED-TMPLS-ODLB command.
For one on-demand LB instance with LB-TOOL-STATE==RUNING, it shall return the snapshot
value of the measurement counters at the time when RTRV-TMPLS-ODLBOUTPUT command is
issued.
For one on-demand LB instance with LB-TOOL-STATE==CONFIGURED, it shall return the current
value of the measurement counters collected by the instance during last run.
8.2.6 Procedure
Select action:
• To configure the LB tool, go to Step 2
• To start/stop the LB tool, go to Step 3.
• To delete the LB tool, go to Step 7.
• To change the LB tool, go to Step 4.
• To retrieve the LB data, go to Step 10.
• To retrieve LB measurement results, go to Step 11.
2
To configure the LB tool
Enter:
ENT-TMPLS-ODLB:[TID]:AID:[CTAG]::[TARGET-MEPID]:[LB-PHB=][,PERIOD=][
,SEND-PKT-NUM=][,PKT-LENGTH=][,START-TIME=][,END-TIME=][,SRC-ID=][,T
TL=][,TARGET-MIPID=][,TARGET-MIPICC=][,DISCOVERY=][,TEST-TLV=][,TEST
-TYPE=];
where:
• AID = AID of the Terminated TMPLS facility where the LB-Tool has to be configured.
It is required that the TUSEG involved must have:
− DIR = BIDIR
− MEP = enable
− TYPE=TERMINATED
− OAM-TYPE=MPLS_TP
that
It is required that for that terminated TUSEG
• TARGET-MEPID = MEP Identifier of peer MEP where MPLS-TP LBM is sent; {0 - 8191} this
is in alternative to TARGET-MIPID or DISCOVERY; no default
• LB-PHB = one of the PHB in the PHB-PROF for that Tunnel
• PERIOD = from 5 sec to 10 sec with step of 1 sec
• SEND-PKT-NUM= number LBM packet to be sent, from when the ACTION = ENABLE {1 –
1024} default = 1
• PKT-LENGTH = from 45 to 1500 bytes
• START-TIME = date and time when the sending LBM packets interval begins
• END-TIME = date and time when the sending LBM packets interval ends
• SRC-ID = to indicate whether Requesting MEP ID TLV shall be included or not {ENABLE,
DISABLE} default = DISABLE
• TTL = Time To Live used to identify the MIP where the LBM packet has to be sent back (node
where the TTL expires)
• TARGET-MIPID = MIP Identifier of the MIP where MPLS-TP LBM is sent: this is in alternative
to TARGET-MEPID or DISCOVERY; no default
• TARGET-MIPICC = ITU-T Carrier Code for LoopBack Tool to be inserted in LBM packet. This
parameter is used to complete the TARGET-MIPID
• DISCOVERY = to indicate if the ingress or egress MIP has to be addressed in the discovery
case this is in alternative to TARGET-MEPID or TARGET-MIPID; no default
• TEST-TLV = it enables the insertion of the Test TLV in the Loopback packet ENABLE,
DISABLE default = DISABLE
• TEST-TYPE = Pattern Type value that it is included in the optional Test TLV identifing the Test
pattern type.
Note: It is not possible to have Loopback to MIP/MEP at the same time as DISCOVERY
tool from a TUSEG.
Example: Creating LB-Tool:
ENT-TMPLS-ODLB::TUSEG-1-1-10:OAM99::200:LB-PHB=EF,PERIOD=5,
SEND-PKTNUM= 20,PKT-LENGTH=250,SRC-ID=ENABLED;
3
To start/stop the LB tool
Enter:
SET-TMPLS-ODOAM::AID::::[TOOL=][,ACTION=];
where:
• AID =
− ALL , If AID=ALL then the Operator will use TOOL parameters as filter to modulate
command behavior.
Restrictions:If AID=ALL then the Operator must enter TOOL parameter. If AID<>ALL the
TOOL parameter can't be entered.
− OD2WAYDMS-(1..1000). AID of “On Demand OAM 2 Way DM-Tool Sender”
− ODLBS-{1-512} On Demand OAM LB-Tool Sender
• TOOL= OD2WAYDMS, ODLBS. With this parameter the Operator can chose the OAM Tool
when AID=ALL
Restrictions: This parameter can be entered only if AID=ALL.
• ACTIONS = ENABLE, STOP. With this parameter the Operator can start/stop OAM tool.
For Sender OAM-Tool:
− ENABLE The tool is enabled and uses the parameters configured with the ENT/ED
command, that is the MEP begins to send and receive packet depending on the
configured SEND-PKT-NUM or according to the START-TIME value
Note: Restrictions:
If ACTION=ENABLE and the tool is RUNNING then the command will be refused.
If ACTION=STOP and the tool is CONFIGURED then the command will be refused.
This is a “general” command that can be used for enabling/stopping also other On Demand
tools.
4
To change the LB tool settings
Retrieve OAM On Demand LB-Tool information entered with ENT-TMPLS-ODLB command.
Enter:
RTRV-TMPLS-ODLB::[AID]:::[TERM-AID];
where:
AID = ODLBS-{1-512} - On Demand OAM LB-Tool Sender.
5
Examine output.
Is the NE-LB-TOOLS output parameter value CONFIGURED?
If YES, go to Step 6.
If NO, go to Step 1.
6
Enter
ED-TMPLS-ODLB::AID::::[TARGET-MEPID=][,LB-PHB=][,PERIOD=]
[,SEND-PKT-NUM=][,PKT-LENGTH=][,START-TIME=][,END-TIME=][,SRC-ID=][,
TTL=][,TARGET-MIPID=][,TARGET-MIPICC=][,DISCOVERY=][,TEST-TLV=][,TES
T-TYPE=];
where:
AID = ODLBS-{1-512} -On Demand OAM LB-Tool Sender.
TARGET-MEPID = The MEP Identifier of peer MEP where MPLS-TP LBM is destinated for.
Note: Restrictions
If TARGET-MIPID=NOTARGET and DISCOVERY=NODISCOVERY then this parameter
must be entered with a valid numeric value.
If NOTARGET value is used for this parameter then TARGET-MIPID or DISCOVERY
parameter must be exclusively edited with TARGET-MIPID<>NOTARGET or
DISCOVERY<>NODISCOVERY.
If the entered LB-Tools already exists for the value pair (AID, TARGET-MEPID), then the
command shall be denied.
LB-PHB = PHB value associated to LBM packets
Note: Restrictions: The chosen LB-PHB must be present into PHB profile used by
Terminated TMPLS Facility where the LB-Tool has been configured.
TARGET-MIPID = MIP Identifier of the MIP where MPLS-TP LBM is sent. The TARGET-MIPID
is composed by two ID:
MIP-NODEID parameter definition of ED-TMPLS-GLOBAL command.
IF-NUM: {1-7}-{1-9}-{1-63}-{1-1024} AID of the physical interface.
7
To delete the LB tool
Enter:
RTRV-TMPLS-ODLB::[AID]:::[TERM-AID];
where:
AID = ODLBS-{1-512} - On Demand OAM LB-Tool Sender.
8
Examine output.
Is the NE-LB-TOOLS output parameter value CONFIGURED?
If YES, go to Step 9.
If NO, go to Step 1.
9
Enter:
DLT-TMPLS-ODLB]:AID;
where:
AID = ODLBS-{1-512} - On Demand OAM LB-Tool Sender.
10
To retrieve the DM data
Enter:
RTRV-TMPLS-ODLB::[AID]:::[TERM-AID];
where:
AID = ODLBS-{1-512} - On Demand OAM LB-Tool Sender.
TERM-AID = AID of the Terminated TMPLS facility where the LB-Tool has been configured.
Result:
11
Retrieve LB tool measurement results
Enter:
RTRV-TMPLS-ODLB::[AID]:::[TERM-AID];
where:
AID = ODLBS-{1-512} - On Demand OAM LB-Tool Sender.
12
Examine output.
Is the NE-LB-TOOLS output parameter value CONFIGURED?
If YES, Step 13.
If NO, go to Step 15.
13
Enter:
RTRV-TMPLS-ODLBOUTPUT::AID;
where:
AID = ODLBS-{1-512} - On Demand OAM LB-Tool Sender.
14
Examine output. It returns the current value of the measurement counters collected by the
instance during last run.
15
If the NE-LB-TOOLS output parameter value is Runningthen enter:
RTRV-TMPLS-ODLBOUTPUT::AID;
where:
AID = ODLBS-{1-512} - On Demand OAM LB-Tool Sender.
16
Examine output. It returns the snapshot value of the measurement counters at the time when
RTRV-TMPLS-ODLBOUTPUT command is issued.
END OF STEPS
8.3.2 General
The loopback functionality on Terminal MEP and MIPs are supported.
On-demand bidirectional connectivity verification: this implies the verification that in the
indicated destination there is the match of the expected MEG/MEP IDs
When the LBM packet is sent to a target MEP, following configurations shall be possible:
• Target MEP ID
• PHB
• Packet Length
• LBM packet interval
• Start Date & TIME, and End Date & TIME, or Number of LBM frames to be sent
• Whether Requesting MEP ID shall be included or not in transmitted LBM frame (this optionally
and implies the activation of bidirectional connectivity verification).
• Whether Test TLV shall be included or not in transmitted LBM frame with the possibility to
configure Test-Type
When the LBM packet is sent to a target MIP, the source MEP MUST know the hop count to the
target MIP and set the TTL field accordingly.
In case of connectivity verification the configuration of the following parameters is needed for the
MIP:
• MEG ID
• Expected MEP ID
Besides when the LBM packet is sent to a target MIP the following configurations are possible:
• TTL (Time To Live)
• Target MIP-ID (includes Node and Port Identifiers).
• PHB
• Packet Length
• LBM packet interval
• Start Date & TIME, and End Date & TIME, or Number of LBM frames to be sent Activation of
bidirectional connectivity verification (this can be done only if the source MEP and the target
MIP have been configured with all expected parameters).
• Whether Test TLV shall be included or not in transmitted LBM frame with the possibility to
configure Test-Type.
8.3.4 Procedure
1
Check if global network parameters assigned to T-MPLS should be changed.
Enter:
RTRV-TMPLS-GLOBAL;
2
Examine output.
3
Enter:
ED-TMPLS-GLOBAL::::::[OAM-CVPERIOD-SEL=][,PHBRANGE-SEL=]
[,OAM-TYPE-SEL=] [,OAM-RX-DETECT=][,CHANNELTYPE=][,PROLM-MODE-BIT=]
[,LBR-TIMEOUT=][,ICC-LB=][,MIP-NODEID];
where:
• OAM-CVPERIOD-SEL = Selector of values range for CV Period into OAM CV frames. The
default value for this parameter is 4.
• PHB-RANGE-SEL = Selector of the default value for PHBPROF (PHBPROF-1 or
PHBPROF-2) for creation of new TUSEGs, PWSEGs and TUNNELs. The default value for
this parameter is 1.
• OAM-TYPE-SEL = MPLS_TP. It is the OAM type default selector. I.e. T-MPLS or MPLS_TP
• LBR-TIMEOUT = The Time-out timer for receiving LBR frames. Unit: Seconds. The default
value for this parameter is 5.
• ICC-LB = ITU-T Carrier Code for LoopBack Tool to be inserted in Replying MIP ID TLV. The
default value for this parameter is the string "000000".
• MIP-NODEID = Node-ID for MIP addressing. It is a 32 bit number entered using IP Address
format. The choosen value must be unique in the network. The initial value for this parameter
is 0-0-0-0. When the MIP-NODEID is uqual to 0-0-0-0 then the System will use the IP
address value of this NE as Node-ID for MIP LoopBack addressing.
4
Create the Terminated TMPLS facility(i.e. TUSEG) specified by AID should be MPLS_TP,
BIDIR, MEP=ENABLE.
Enter:
ENT-TMPLS-TUSEG:::::PORT,[TYPE],[DIR],[USERNAME]: [L2ENCAPPROF-AID=][,
INLABEL=][,OUTLABEL=][,PHBPROF-AID=][,OAMPHB-AID=] [,MEP=][,MEG-ID=][,
MEP-ID=][,EXPMEP-ID=][,CVRX=][,CVTX=][,CVPERIOD=][,CVPHB=]
[,ALMPROF=][,ADD-GROUP=][,OAM-TYPE=] [,TCAPROF=][,RDI-SD=][,
MIPING-EXPMEP-ID][,MIPEGR-EXPMEP-ID];
where:
• PORT = AID of the port which is server of the MPLS TUSegment.
• TYPE = TERMINATION.
• DIR = BIDIR
• MEP=ENABLE
• OAM-TYPE=MPLS_TP
• MEP-ID= {0-8191}. Transmitted MEP value, integer associated to Source TUSegment
Termination (MEP_ID in T-MPLS CV OAM frame identifying the transmitting MEP).
This parameter is unique inside MEG_ID
Restrictions: If provisioned, this parameter must be different from EXPMEP-ID
• EXPMEP-ID= {0-8191}. Expected MEP value associated to Sink TUSegment Termination,
also called Peer MEP-ID.
Restrictions: If provisioned, this parameter must be different from MEP-ID.
• MIPING-EXPMEP-ID= {0-8191}. EXPMEP-ID for ingress MIP associated to this TUSEG. The
value of this parameter is used as expected MEP by MIPs.
• MIPEGR-EXPMEP-ID== {0-8191}.EXPMEP-ID for egress MIP associated to this TUSEG.
The value of this parameter is used as expected MEP by MIPs.
Select action:
• To perform the Connectivity verification loopback (TARGET = MEP), go to Step 6.
• To perform the Connectivity verification loopback (TARGET = MIP), go to Step 7.
• To perform the Connectivity verification loopback - No test TLV, go to Step 8.
• To perform the Connectivity verification loopback - Test TLV without CRC, go to Step 9.
• To perform the Connectivity verification loopback - Test TLV with CRC enabled, go to Step
10.
6
Connectivity verification loopback (TARGET = MEP)
Enter:
ENT-TMPLS-ODLB::AID:::[TARGET-MEPID]:[,SRC-ID=][,T TL=][,DISCOVERY=];
where:
• AID = AID of the Terminated TMPLS facility where the LB-Tool has to be configured.
Remember: It is required that the TUSEG involved must have:
− DIR = BIDIR
− MEP = enable
− TYPE=TERMINATED
− OAM-TYPE=MPLS_TP
• TARGET-MEPID = MEP Identifier of peer MEP where MPLS-TP LBM is sent; {0 - 8191} this
is in alternative to TARGET-MIPID or DISCOVERY;
• SRC-ID = ENABLE. It indicates whether Requesting MEP ID TLV shall be included or not
{ENABLE, DISABLE}
• TTL = 255. Time To Live used to identify the MIP where the LBM packet has to be sent back
(node where the TTL expires)
• DISCOVERY = NODISCOVERY. It indicates if the ingress or egress MIP has to be
addressed in the discovery case this is in alternative to TARGET-MEPID or TARGET-MIPID;
Note: It is not possible to have Loopback to MIP/MEP at the same time as DISCOVERY
tool from a TUSEG.
7
Connectivity verification loopback (TARGET = MIP)
Enter:
ENT-TMPLS-ODLB::AID::::[,SRC-ID=][,TTL=][,TARGET-MIPID=][,DISCOVERY=];
where:
• AID = AID of the Terminated TMPLS facility where the LB-Tool has to be configured.
Remember: It is required that the TUSEG involved must have:
− DIR = BIDIR
− MEP = enable
− TYPE=TERMINATED
− OAM-TYPE=MPLS_TP
• TARGET-MIPID = MIP Identifier of the MIP where MPLS-TP LBM is sent.
Restrictions: If TARGET-MEPID=NOTARGET and DISCOVERY=NODISCOVERY then this
parameter must be entered with a valid MIP-NODEID and IF-NUM.
If TARGET-MEPID<>NOTARGET then this parameter can't be entered If DISCOVERY<>
NODISCOVERY then this parameter can't be entered.
If the entered LB-Tools already exists for the triple values (AID, TARGET-MIPID,
TARGET-MIPICC), then the command shall be denied.
• SRC-ID = ENABLE. It indicates whether Requesting MEP ID TLV shall be included or not
{ENABLE, DISABLE}
• TTL = 255. Time To Live used to identify the MIP where the LBM packet has to be sent back
(node where the TTL expires)
• DISCOVERY = NODISCOVERY. It indicates if the ingress or egress MIP has to be
addressed in the discovery case this is in alternative to TARGET-MEPID or TARGET-MIPID;
Note: It is not possible to have Loopback to MIP/MEP at the same time as DISCOVERY
tool from a TUSEG.
8
Connectivity verification loopback - No test TLV
To perform CV loopback without TLV on MEP/MIP targert or with the Discovery feature enabled,
enter:
ENT-TMPLS-ODLB::AID:::[TARGET-MEPID]:[,SRC-ID=][,T TL=][,PKT-LENGTH=]
[,TARGET-MIPID=][,DISCOVERY=][,TEST-TLV=];
where:
• AID = AID of the Terminated TMPLS facility where the LB-Tool has to be configured.
Remember: It is required that the TUSEG involved must have:
− DIR = BIDIR
− MEP = enable
− TYPE=TERMINATED
− OAM-TYPE=MPLS_TP
• TARGET-MEPID = MEP Identifier of peer MEP where MPLS-TP LBM is sent; {0 - 8191} this
is in alternative to TARGET-MIPID or DISCOVERY;
• SRC-ID = ENABLE. It indicates whether Requesting MEP ID TLV shall be included or not
{ENABLE, DISABLE}
• TTL = 255. Time To Live used to identify the MIP where the LBM packet has to be sent back
(node where the TTL expires)
• PKT-LENGTH = 101, 104 – 1500 (Default = 101).
This parameter is used to define the length of the LBM frames to be sent.
Restrictions: If TEST-TLV = DISABLE and SRC-ID = ENABLE then PKT-LENGTH ≥ 101
and ≠ (102, 103)
• TARGET-MIPID = MIP Identifier of the MIP where MPLS-TP LBM is sent.
Restrictions: If TARGET-MEPID=NOTARGET and DISCOVERY=NODISCOVERY then this
parameter must be entered with a valid MIP-NODEID and IF-NUM.
If TARGET-MEPID<>NOTARGET then this parameter can't be entered If DISCOVERY<>
NODISCOVERY then this parameter can't be entered.
If the entered LB-Tools already exists for the triple values (AID, TARGET-MIPID,
TARGET-MIPICC), then the command shall be denied.
• DISCOVERY = It indicates if the ingress or egress MIP has to be addressed in the discovery
case this is in alternative to TARGET-MEPID or TARGET-MIPID;
• TEST-TLV = DISABLE.
This parameter enables the insertion of the Test TLV in the Loopback packet.
9
Connectivity verification Test TLV without CRC
To perform CV loopback without TLV on MEP/MIP targert or with the Discovery feature enabled,
enter:
ENT-TMPLS-ODLB::AID:::[TARGET-MEPID]:[,SRC-ID=][,T TL=][,PKT-LENGTH=]
[,TARGET-MIPID=][,DISCOVERY=][,TEST-TLV=][,TEST-TYPE=];
where:
• AID = AID of the Terminated TMPLS facility where the LB-Tool has to be configured.
Remember: It is required that the TUSEG involved must have:
− DIR = BIDIR
− MEP = enable
− TYPE=TERMINATED
− OAM-TYPE=MPLS_TP
• TARGET-MEPID = MEP Identifier of peer MEP where MPLS-TP LBM is sent; {0 - 8191} this
is in alternative to TARGET-MIPID or DISCOVERY;
• SRC-ID = ENABLE. It indicates whether Requesting MEP ID TLV shall be included or not
{ENABLE, DISABLE}
• TTL = 255. Time To Live used to identify the MIP where the LBM packet has to be sent back
(node where the TTL expires)
• PKT-LENGTH = 105 – 1500 (Default = 105).
This parameter is used to define the length of the LBM frames to be sent.
Restrictions: If TEST-TLV = ENABLE and SRC-ID = ENABLE and TEST-TYPE = 0, 2 then
PKT-LENGTH ≥ 105
• TARGET-MIPID = MIP Identifier of the MIP where MPLS-TP LBM is sent.
Restrictions: If TARGET-MEPID=NOTARGET and DISCOVERY=NODISCOVERY then this
parameter must be entered with a valid MIP-NODEID and IF-NUM.
If TARGET-MEPID<>NOTARGET then this parameter can't be entered If DISCOVERY<>
NODISCOVERY then this parameter can't be entered.
If the entered LB-Tools already exists for the triple values (AID, TARGET-MIPID,
TARGET-MIPICC), then the command shall be denied.
• DISCOVERY = It indicates if the ingress or egress MIP has to be addressed in the discovery
case this is in alternative to TARGET-MEPID or TARGET-MIPID;
• TEST-TLV = ENABLE.
This parameter enables the insertion of the Test TLV in the Loopback packet.
• TEST-TYPE = 0, 2. Pattern Type value that it is included in the optional Test TLV identifing
the Test pattern type.
Where:
0 = Null signal (all-zeros) without CRC-32.
2 = PRBS 2-31-1 without CRC-32.
10
Connectivity verification Test TLV with CRC enabled
To perform CV loopback without TLV on MEP/MIP targert or with the Discovery feature enabled,
enter:
ENT-TMPLS-ODLB::AID:::[TARGET-MEPID]:[,SRC-ID=][,T TL=][,PKT-LENGTH=]
[,TARGET-MIPID=][,DISCOVERY=][,TEST-TLV=][,TEST-TYPE=];
where:
• AID = AID of the Terminated TMPLS facility where the LB-Tool has to be configured.
Remember: It is required that the TUSEG involved must have:
− DIR = BIDIR
− MEP = enable
− TYPE=TERMINATED
− OAM-TYPE=MPLS_TP
• TARGET-MEPID = MEP Identifier of peer MEP where MPLS-TP LBM is sent; {0 - 8191} this
is in alternative to TARGET-MIPID or DISCOVERY;
• SRC-ID = ENABLE. It indicates whether Requesting MEP ID TLV shall be included or not
{ENABLE, DISABLE}
• TTL = 255. Time To Live used to identify the MIP where the LBM packet has to be sent back
(node where the TTL expires)
• PKT-LENGTH = 109 – 1500 (Default = 109).
This parameter is used to define the length of the LBM frames to be sent.
Restrictions: If TEST-TLV = ENABLE and SRC-ID = ENABLE and TEST-TYPE = 1, 3 then
PKT-LENGTH ≥ 109
• TARGET-MIPID = MIP Identifier of the MIP where MPLS-TP LBM is sent.
Restrictions: If TARGET-MEPID=NOTARGET and DISCOVERY=NODISCOVERY then this
parameter must be entered with a valid MIP-NODEID and IF-NUM.
If TARGET-MEPID<>NOTARGET then this parameter can't be entered If DISCOVERY<>
NODISCOVERY then this parameter can't be entered.
If the entered LB-Tools already exists for the triple values (AID, TARGET-MIPID,
TARGET-MIPICC), then the command shall be denied.
• DISCOVERY = It indicates if the ingress or egress MIP has to be addressed in the discovery
case this is in alternative to TARGET-MEPID or TARGET-MIPID;
• TEST-TLV = ENABLE.
This parameter enables the insertion of the Test TLV in the Loopback packet.
• TEST-TYPE = 1, 3. Pattern Type value that it is included in the optional Test TLV identifing
the Test pattern type.
Where:
1 = Null signal (all-zeros) with CRC-32.
3 = PRBS 2-31-1 with CRC-32.
END OF STEPS
8.4.2 General
The loopback functionality on Terminal MEP and MIPs are supported.
In-Service Diagnostic Test: it provides information only about the reachability of specified
destination.
• LB-PHB parameter value is into PHB profile used by this Terminated TMPLS facility
• START-TIME is not antecedent to “Current System Date-Time”
• END-TIME is not antecedent or equal to START-TIME
• START-TIME/END-TIME parameter is not entered together with SEND-PKT-NUM parameter
• TARGET-MEPID=NOTARGET and TARGET-MIPID=NOTARGET and
DISCOVERY=NODISCOVERY not an accettable value
• the Terminated TMPLS facility(i.e. TUSEG) specified by AID should be MPLS_TP, BIDIR,
MEP=ENABLE.
8.4.4 Procedure
1
Check if global network parameters assigned to T-MPLS should be changed.
Enter:
RTRV-TMPLS-GLOBAL:[TID]::[CTAG];
2
Examine output.
3
Enter:
ED-TMPLS-GLOBAL:[TID]::[CTAG]:::[OAM-CVPERIOD-SEL=][,PHB-RANGE-SEL=]
[,OAM-TYPE-SEL=][,OAM-RX-DETECT=][,CHANNEL-TYPE=][,PROLM-MODE-BIT=][,
LBR-TIMEOUT=][,ICC-LB=][,MIP-NODEID=][,APSRING-CHANNEL-TYPE=][,CHAN
NEL-TYPE-RX1=][,CHANNEL-TYPE-RX2=][,APSRING-CHANNEL-TYPE-RX1=][,APSR
ING-CHANNEL-TYPE-RX2=][,IGNORE-SEC-BIT=][,STATUS-BIT=];
where:
• OAM-CVPERIOD-SEL = Selector of values range for CV Period into OAM CV frames. The
default value for this parameter is 4.
• PHB-RANGE-SEL = Selector of the default value for PHBPROF (PHBPROF-1 or
PHBPROF-2) for creation of new TUSEGs, PWSEGs and TUNNELs. The default value for
this parameter is 1.
• OAM-TYPE-SEL = MPLS_TP. It is the OAM type default selector. I.e. T-MPLS or MPLS_TP
• LBR-TIMEOUT = The Time-out timer for receiving LBR frames. Unit: Seconds. The default
value for this parameter is 5.
• ICC-LB = ITU-T Carrier Code for LoopBack Tool to be inserted in Replying MIP ID TLV. The
default value for this parameter is the string "000000".
• MIP-NODEID = Node-ID for MIP addressing. It is a 32 bit number entered using IP Address
format. The choosen value must be unique in the network. The initial value for this parameter
is 0-0-0-0. When the MIP-NODEID is uqual to 0-0-0-0 then the System will use the IP
address value of this NE as Node-ID for MIP LoopBack addressing.
4
Create the Terminated TMPLS facility(i.e. TUSEG) specified by AID should be MPLS_TP,
BIDIR, MEP=ENABLE.
Enter:
ENT-TMPLS-TUSEG:[TID]::[CTAG]::PORT,[TYPE],[DIR],[USERNAME]:
[L2ENCAPPROF-AID=][,INLABEL=][,OUTLABEL=][,PHBPROF-AID=][,OAMPHB-AID=]
[,MEP= ][,MEG-ID=][,MEP-ID=][,EXPMEP-ID=][,CVRX=][,CVTX=][,CVPERIOD=]
[,CVPH B=][,ALMPROF=][,ADD-GROUP=][,PS-DDM-SD=][,OAM-TYPE=][,
PROSLMCVTX=][,PROSLMCVRX=][,PROLM-PLP=][,PROLM-SD-CROSSTH=][,
PROLM-SD-CLEARTH=][,P RODM=][,PRODM-PHB=][,PRODM-PERIOD=][,
PRODM-PKT-LENGTH=][,TCAPROF=][, RDI-SD=][,MIPING-EXPMEP-ID=][,
MIPEGR-EXPMEP-ID=][,RING=];
where:
• PORT = AID of the port which is server of the MPLS TUSegment.
• TYPE = TERMINATION.
• DIR = BIDIR
• MEP=ENABLE
• OAM-TYPE=MPLS_TP
• MEP-ID= {0-8191}. Transmitted MEP value, integer associated to Source TUSegment
Termination (MEP_ID in T-MPLS CV OAM frame identifying the transmitting MEP).
This parameter is unique inside MEG_ID
Restrictions: If provisioned, this parameter must be different from EXPMEP-ID
• EXPMEP-ID= {0-8191}. Expected MEP value associated to Sink TUSegment Termination,
also called Peer MEP-ID.
Restrictions: If provisioned, this parameter must be different from MEP-ID.
• MIPING-EXPMEP-ID= {0-8191}. EXPMEP-ID for ingress MIP associated to this TUSEG. The
value of this parameter is used as expected MEP by MIPs.
• MIPEGR-EXPMEP-ID== {0-8191}.EXPMEP-ID for egress MIP associated to this TUSEG.
The value of this parameter is used as expected MEP by MIPs.
Select action:
• To perform the Diagnostic loopback (TARGET = MEP), go to Step 6.
• To perform the Diagnostic loopback (TARGET = MIP), go to Step 7.
• To perform the Diagnostic loopback - No test TLV, go to Step 8.
• To perform the Diagnostic loopback - Test TLV without CRC, go to Step 9.
• To perform the Diagnostic loopback - Test TLV with CRC enabled, go to Step 10.
6
Diagnostic loopback (TARGET = MEP)
Enter:
ENT-TMPLS-ODLB::AID:::[TARGET-MEPID]:[,SRC-ID=][,T TL=][,DISCOVERY=];
where:
• AID = AID of the Terminated TMPLS facility where the LB-Tool has to be configured.
Remember: It is required that the TUSEG involved must have:
− DIR = BIDIR
− MEP = enable
− TYPE=TERMINATED
− OAM-TYPE=MPLS_TP
• TARGET-MEPID = MEP Identifier of peer MEP where MPLS-TP LBM is sent; {0 - 8191} this
is in alternative to TARGET-MIPID or DISCOVERY;
• SRC-ID = DISABLE. It indicates whether Requesting MEP ID TLV shall be included or not
{ENABLE, DISABLE}
• TTL = 255. Time To Live used to identify the MIP where the LBM packet has to be sent back
(node where the TTL expires)
• DISCOVERY = NODISCOVERY. It indicates if the ingress or egress MIP has to be
addressed in the discovery case this is in alternative to TARGET-MEPID or TARGET-MIPID;
Note: It is not possible to have Loopback to MIP/MEP at the same time as DISCOVERY
tool from a TUSEG.
7
Diagnostic loopback (TARGET = MIP)
Enter:
ENT-TMPLS-ODLB::AID::::[,SRC-ID=][,TTL=][,TARGET-MIPID=][,DISCOVERY=];
where:
• AID = AID of the Terminated TMPLS facility where the LB-Tool has to be configured.
Remember: It is required that the TUSEG involved must have:
− DIR = BIDIR
− MEP = enable
− TYPE=TERMINATED
− OAM-TYPE=MPLS_TP
• TARGET-MIPID = MIP Identifier of the MIP where MPLS-TP LBM is sent.
Restrictions: If TARGET-MEPID=NOTARGET and DISCOVERY=NODISCOVERY then this
parameter must be entered with a valid MIP-NODEID and IF-NUM.
If TARGET-MEPID<>NOTARGET then this parameter can't be entered If DISCOVERY<>
NODISCOVERY then this parameter can't be entered.
If the entered LB-Tools already exists for the triple values (AID, TARGET-MIPID,
TARGET-MIPICC), then the command shall be denied.
• SRC-ID = DISABLE. It indicates whether Requesting MEP ID TLV shall be included or not
{ENABLE, DISABLE}
• TTL = {1-255}. Time To Live used to identify the MIP where the LBM packet has to be sent
back (node where the TTL expires)
• DISCOVERY = NODISCOVERY. It indicates if the ingress or egress MIP has to be
addressed in the discovery case this is in alternative to TARGET-MEPID or TARGET-MIPID;
Note: It is not possible to have Loopback to MIP/MEP at the same time as DISCOVERY
tool from a TUSEG.
8
Diagnostic loopback - No test TLV
To perform CV loopback without TLV on MEP/MIP targert or with the Discovery feature enabled,
enter:
ENT-TMPLS-ODLB::AID:::[TARGET-MEPID]:[,SRC-ID=][,T TL=][,PKT-LENGTH=]
[,TARGET-MIPID=][,DISCOVERY=][,TEST-TLV=];
where:
• AID = AID of the Terminated TMPLS facility where the LB-Tool has to be configured.
Remember: It is required that the TUSEG involved must have:
− DIR = BIDIR
− MEP = enable
− TYPE=TERMINATED
− OAM-TYPE=MPLS_TP
• TARGET-MEPID = MEP Identifier of peer MEP where MPLS-TP LBM is sent; {0 - 8191} this
is in alternative to TARGET-MIPID or DISCOVERY;
• SRC-ID = DISABLE. It indicates whether Requesting MEP ID TLV shall be included or not
{ENABLE, DISABLE}
• TTL = 255. Time To Live used to identify the MIP where the LBM packet has to be sent back
(node where the TTL expires)
• PKT-LENGTH = 45, 48 – 1500(Default = 45).
This parameter is used to define the length of the LBM frames to be sent.
Restrictions: If TEST-TLV = DISABLE and SRC-ID = DISABLE then PKT-LENGTH ≥ 45 and
≠ (46, 47)
• TARGET-MIPID = MIP Identifier of the MIP where MPLS-TP LBM is sent.
Restrictions: If TARGET-MEPID=NOTARGET and DISCOVERY=NODISCOVERY then this
parameter must be entered with a valid MIP-NODEID and IF-NUM.
If TARGET-MEPID<>NOTARGET then this parameter can't be entered If DISCOVERY<>
NODISCOVERY then this parameter can't be entered.
If the entered LB-Tools already exists for the triple values (AID, TARGET-MIPID,
TARGET-MIPICC), then the command shall be denied.
• DISCOVERY = It indicates if the ingress or egress MIP has to be addressed in the discovery
case this is in alternative to TARGET-MEPID or TARGET-MIPID;
• TEST-TLV = DISABLE.
This parameter enables the insertion of the Test TLV in the Loopback packet.
9
Diagnostic loopback - Test TLV without CRC
To perform CV loopback without TLV on MEP/MIP targert or with the Discovery feature enabled,
enter:
ENT-TMPLS-ODLB::AID:::[TARGET-MEPID]:[,SRC-ID=][,T TL=][,PKT-LENGTH=]
[,TARGET-MIPID=][,DISCOVERY=][,TEST-TLV=][,TEST-TYPE=];
where:
• AID = AID of the Terminated TMPLS facility where the LB-Tool has to be configured.
Remember: It is required that the TUSEG involved must have:
− DIR = BIDIR
− MEP = enable
− TYPE=TERMINATED
− OAM-TYPE=MPLS_TP
• TARGET-MEPID = MEP Identifier of peer MEP where MPLS-TP LBM is sent; {0 - 8191} this
is in alternative to TARGET-MIPID or DISCOVERY;
• SRC-ID = DISABLE. It indicates whether Requesting MEP ID TLV shall be included or not
{ENABLE, DISABLE}.
• TTL = 255. Time To Live used to identify the MIP where the LBM packet has to be sent back
(node where the TTL expires)
• PKT-LENGTH = 49 – 1500 (Default = 49).
This parameter is used to define the length of the LBM frames to be sent.
Restrictions: If TEST-TLV = ENABLE and SRC-ID = DISABLE and TEST-TYPE = 0, 2 then
PKT-LENGTH ≥ 49
• TARGET-MIPID = MIP Identifier of the MIP where MPLS-TP LBM is sent.
Restrictions: If TARGET-MEPID=NOTARGET and DISCOVERY=NODISCOVERY then this
parameter must be entered with a valid MIP-NODEID and IF-NUM.
If TARGET-MEPID<>NOTARGET then this parameter can't be entered If DISCOVERY<>
NODISCOVERY then this parameter can't be entered.
If the entered LB-Tools already exists for the triple values (AID, TARGET-MIPID,
TARGET-MIPICC), then the command shall be denied.
• DISCOVERY = It indicates if the ingress or egress MIP has to be addressed in the discovery
case this is in alternative to TARGET-MEPID or TARGET-MIPID;
• TEST-TLV = ENABLE.
This parameter enables the insertion of the Test TLV in the Loopback packet.
• TEST-TYPE = 0, 2. Pattern Type value that it is included in the optional Test TLV identifing
the Test pattern type.
Where:
0 = Null signal (all-zeros) without CRC-32.
10
Diagnostic Loop - Test TLV with CRC enabled
To perform CV loopback without TLV on MEP/MIP targert or with the Discovery feature enabled,
enter:
ENT-TMPLS-ODLB::AID:::[TARGET-MEPID]:[,SRC-ID=][,T TL=][,PKT-LENGTH=]
[,TARGET-MIPID=][,DISCOVERY=][,TEST-TLV=][,TEST-TYPE=];
where:
• AID = AID of the Terminated TMPLS facility where the LB-Tool has to be configured.
Remember: It is required that the TUSEG involved must have:
− DIR = BIDIR
− MEP = enable
− TYPE=TERMINATED
− OAM-TYPE=MPLS_TP
• TARGET-MEPID = MEP Identifier of peer MEP where MPLS-TP LBM is sent; {0 - 8191} this
is in alternative to TARGET-MIPID or DISCOVERY;
• SRC-ID = DISABLE. It indicates whether Requesting MEP ID TLV shall be included or not
{ENABLE, DISABLE}
• TTL = 255. Time To Live used to identify the MIP where the LBM packet has to be sent back
(node where the TTL expires)
• PKT-LENGTH = 101, 104 – 1500 (Default = 101).
This parameter is used to define the length of the LBM frames to be sent.
Restrictions: If TEST-TLV = ENABLE and SRC-ID = DISABLE and TEST-TYPE = 1, 3 then
PKT-LENGTH ≥ 53
• TARGET-MIPID = MIP Identifier of the MIP where MPLS-TP LBM is sent.
Restrictions: If TARGET-MEPID=NOTARGET and DISCOVERY=NODISCOVERY then this
parameter must be entered with a valid MIP-NODEID and IF-NUM.
If TARGET-MEPID<>NOTARGET then this parameter can't be entered If DISCOVERY<>
NODISCOVERY then this parameter can't be entered.
If the entered LB-Tools already exists for the triple values (AID, TARGET-MIPID,
TARGET-MIPICC), then the command shall be denied.
• DISCOVERY = It indicates if the ingress or egress MIP has to be addressed in the discovery
case this is in alternative to TARGET-MEPID or TARGET-MIPID;
• TEST-TLV = ENABLE.
This parameter enables the insertion of the Test TLV in the Loopback packet.
• TEST-TYPE = 1, 3. Pattern Type value that it is included in the optional Test TLV identifing
the Test pattern type.
Where:
1 = Null signal (all-zeros) with CRC-32.
END OF STEPS
8.5.2 General
The system supports the capability to retrieve the MIP-IDs of intermediate MIP: a LBM message is
sent with a configured TTL and specifying if ingress or egress MIP ID has to be discovered.
In the LBR the Loopback Initiator will retrieve the MIP ID and will report it to operator.
The system reports the MEP-ID in case the TTL is greater than the number of spans crossed by the
LSP Tunnel.
• the Terminated TMPLS facility(i.e. TUSEG) specified by AID should be MPLS_TP, BIDIR,
MEP=ENABLE.
Note: It is not possible to have Loopback to MIP/MEP at the same time as DISCOVERY tool
from a TUSEG. It is possible the following:
• one tool for each <AID, TARGET-MEPID,DISCOVERY>
• one tool for each <AID, TARGET-MIPID,DISCOVERY>
8.5.5 Procedure
1
Check if global network parameters assigned to T-MPLS should be changed.
Enter:
RTRV-TMPLS-GLOBAL;
2
Examine output.
3
Enter:
ED-TMPLS-GLOBAL::::::[OAM-CVPERIOD-SEL=][,PHBRANGE-SEL=]
[,OAM-TYPE-SEL=] [,OAM-RX-DETECT=][,CHANNELTYPE=][,PROLM-MODE-BIT=]
[,LBR-TIMEOUT=][,ICC-LB=][,MIP-NODEID];
where:
• OAM-CVPERIOD-SEL = Selector of values range for CV Period into OAM CV frames. The
default value for this parameter is 4.
• PHB-RANGE-SEL = Selector of the default value for PHBPROF (PHBPROF-1 or
PHBPROF-2) for creation of new TUSEGs, PWSEGs and TUNNELs. The default value for
this parameter is 1.
• OAM-TYPE-SEL = MPLS_TP. It is the OAM type default selector. I.e. T-MPLS or MPLS_TP
• LBR-TIMEOUT = The Time-out timer for receiving LBR frames. Unit: Seconds. The default
value for this parameter is 5.
• ICC-LB = ITU-T Carrier Code for LoopBack Tool to be inserted in Replying MIP ID TLV. The
default value for this parameter is the string "000000".
• MIP-NODEID = Node-ID for MIP addressing. It is a 32 bit number entered using IP Address
format. The choosen value must be unique in the network. The initial value for this parameter
is 0-0-0-0. When the MIP-NODEID is uqual to 0-0-0-0 then the System will use the IP
address value of this NE as Node-ID for MIP LoopBack addressing.
4
Create the Terminated TMPLS facility(i.e. TUSEG) specified by AID should be MPLS_TP,
BIDIR, MEP=ENABLE.
Enter:
ENT-TMPLS-TUSEG:::::PORT,[TYPE],[DIR],[USERNAME]: [L2ENCAPPROF-AID=][,
INLABEL=][,OUTLABEL=][,PHBPROF-AID=][,OAMPHB-AID=] [,MEP=][,MEG-ID=][,
MEP-ID=][,EXPMEP-ID=][,CVRX=][,CVTX=][,CVPERIOD=][,CVPHB=]
[,ALMPROF=][,ADD-GROUP=][,OAM-TYPE=] [,TCAPROF=][,RDI-SD=][,
MIPING-EXPMEP-ID][,MIPEGR-EXPMEP-ID];
where:
• PORT = AID of the port which is server of the MPLS TUSegment.
• TYPE = TERMINATION.
• DIR = BIDIR
• MEP=ENABLE
• OAM-TYPE=MPLS_TP
• MEP-ID= {0-8191}. Transmitted MEP value, integer associated to Source TUSegment
Termination (MEP_ID in T-MPLS CV OAM frame identifying the transmitting MEP).
This parameter is unique inside MEG_ID
Restrictions: If provisioned, this parameter must be different from EXPMEP-ID
• EXPMEP-ID= {0-8191}. Expected MEP value associated to Sink TUSegment Termination,
also called Peer MEP-ID.
Restrictions: If provisioned, this parameter must be different from MEP-ID.
• MIPING-EXPMEP-ID= {0-8191}. EXPMEP-ID for ingress MIP associated to this TUSEG. The
value of this parameter is used as expected MEP by MIPs.
• MIPEGR-EXPMEP-ID== {0-8191}.EXPMEP-ID for egress MIP associated to this TUSEG.
The value of this parameter is used as expected MEP by MIPs.
Select action:
• To perform the Discovery loopback (TARGET = MEP), go to Step 6.
• To perform the Discovery loopback (TARGET = MIP), go to Step 7.
6
Discovery loopback (TARGET = MEP)
Enter:
ENT-TMPLS-ODLB::AID:::[TARGET-MEPID]:[,SRC-ID=][,T TL=][,DISCOVERY=];
where:
• AID = AID of the Terminated TMPLS facility where the LB-Tool has to be configured.
Remember: It is required that the TUSEG involved must have:
− DIR = BIDIR
− MEP = enable
− TYPE=TERMINATED
− OAM-TYPE=MPLS_TP
• TARGET-MEPID = NOTARGET.
Restrictions:
If TARGET-MIPID=NOTARGET and DISCOVERY=NODISCOVERY then this parameter must
be entered with a valid numeric value.
If TARGET-MIPID<>NOTARGET then this parameter can't be entered.
If DISCOVERY<>NODISCOVERY then this parameter can't be entered.
If the entered LB-Tools already exists for the value pair (AID, TARGET-MEPID), then the
command shall be denied.
• SRC-ID = DISABLE. It indicates whether Requesting MEP ID TLV shall be included or not
{ENABLE, DISABLE}
• TTL = {1-255}. Time To Live used to identify the MIP where the LBM packet has to be sent
back (node where the TTL expires)
• DISCOVERY = INGRESS EGRESS. It indicates if the ingress or egress MIP has to be
addressed in the discovery case this is in alternative to TARGET-MEPID or TARGET-MIPID;
Restrictions:
− If TARGET-MEPID=NOTARGET and TARGET-MIPID=NOTARGET then this parameter
must be entered and the allowed values are {INGRESS, EGRESS}
− If TARGET-MEPID<>NOTARGET then this parameter can't be entered. If the entered LB-
Tools already exists for the value pair (AID, DISCOVERY), then the command shall be
denied.
− If TARGET-MIPID<>NOTARGET then this parameter can't be entered.
7
Discovery loopback (TARGET = MIP)
Enter:
ENT-TMPLS-ODLB::AID:::[TARGET-MEPID]:[,SRC-ID=][,TTL=][,TARGET-MIPID=]
[,DISCOVERY=];
where:
• AID = AID of the Terminated TMPLS facility where the LB-Tool has to be configured.
Remember: It is required that the TUSEG involved must have:
− DIR = BIDIR
− MEP = enable
− TYPE=TERMINATED
− OAM-TYPE=MPLS_TP
• TARGET-MEPID = NOTARGET.
Restrictions:
If TARGET-MIPID=NOTARGET and DISCOVERY=NODISCOVERY then this parameter must
be entered with a valid numeric value.
If TARGET-MIPID<>NOTARGET then this parameter can't be entered.
If DISCOVERY<>NODISCOVERY then this parameter can't be entered.
If the entered LB-Tools already exists for the value pair (AID, TARGET-MEPID), then the
command shall be denied.
• SRC-ID = DISABLE. It indicates whether Requesting MEP ID TLV shall be included or not
{ENABLE, DISABLE}
• TTL = {1-255}. Time To Live used to identify the MIP where the LBM packet has to be sent
back (node where the TTL expires)
• TARGET-MIPID = NOTARGET.
Restrictions:
If TARGET-MEPID=NOTARGET and DISCOVERY=NODISCOVERY then this parameter
must be entered with a valid MIP-NODEID and IF-NUM.
If TARGET-MEPID<>NOTARGET then this parameter can't be entered
If DISCOVERY<>NODISCOVERY then this parameter can't be entered.
If the entered LB-Tools already exists for the triple values (AID, TARGET-MIPID,
TARGET-MIPICC), then the command shall be denied.
• DISCOVERY = INGRESS, EGRESS. It indicates if the ingress or egress MIP has to be
addressed in the discovery case this is in alternative to TARGET-MEPID or TARGET-MIPID;
Restrictions:
− If &-grouping addressing is used then NODISCOVERY value can't be used together with
INGRESS value.
− If &-grouping addressing is used then NODISCOVERY value can't be used together with
EGRESS value
− If TARGET-MEPID=NOTARGET and TARGET-MIPID=NOTARGET then this parameter
must be entered and the allowed values are {INGRESS, EGRESS}
− If TARGET-MEPID<>NOTARGET then this parameter can't be entered. If the entered LB-
Tools already exists for the value pair (AID, DISCOVERY), then the command shall be
denied.
− If TARGET-MIPID<>NOTARGET then this parameter can't be entered.
END OF STEPS
8.6.2 General
The ENT-TMPLS-OD2WAYDM command creates On Demand OAM 2-Way DM (Delay
Measurement) tool.
OAM OD2WAYDM (OAM On Demand 2-Way DM) Tools are of two types:
• SENDER DM-Tool. MEP point that sends DMM packets and make measurement when receives
back DMR packets received from the symmetrical tool RDMT (i.e. from peer MEP point).
• RESPONDER DM-Tool. MEP point that sends back DMR packets when receives DMM packet
sent by SDMT.
The Operator, with this command, can create only SENDER DM-Tool because RESPONDER DM-
Tools are explicitly enabled to responding when the MEP point receives DMM packets.
A DM-Tools is identified by AID, DM-PHB parameters values.
When the Operator wants START/STOP a DM-Tool he will use SET-TMPLS-ODOAM command
specifying TOOL parameter proper value.
So, the SET-TMPLS-ODOAM command enables/disables or stops On Demand OAM tools.
Note: Command restriction: OAM tool referenced by this command must be previously
entered trough ENT-TMPLS-<tool> command.
The DLT-TMPLS-OD2WAYDM command deletes On Demand OAM 2-Way DM (Delay
Measurement) tools.
With this command the Operator can delete SENDER DM-Tools.
When the Operator wants STOP a Sender DM-Tool it will use SET-TMPLS-ODOAM command but
not this command.
When a SENDER DM-Tool is deleted then also its file containing Delay Measurement data will be
erased.
The T-MPLS DM tool is available on demand. The T-MPLS DM tool is a T-MPLS OAM tool available
for Tunnels only (no PW).
Up to 512 instance of the DM tool are available on each 10G packet module.
MEL = 0 for DMM/DMR packets.
It is possible to enable the transmission of DM packets at TUSEG level, for each pair <TUSEG
with MEP enabled, PHB>
When the transmission of T-MPLS DM is enabled on one <TUSEG, PHB> pair, automatically also
the reception of DMR is enabled.
Upon reception of one DMR, NE shall check whether there is an active T-MPLS DM instance for
this DMR. Otherwise, the DMR shall be dropped
Results are available in file format, one file for each <TUSEG, PHB> pair.
The maximum tolerated delay between one DMM and its corresponding DMR is 10 seconds. If the
DMR packet is received beyond that interval, it shall be dropped.
T-MPLS 2-way DM is based on “not aligned” source and sink nodes (they have independent clocks
– frequency aligned).
8.6.3 DM Output
The output file, obtained using the configuration and SET command for running the tool, contains
• the collected DM data for the OD2WAYDMS-xxx from the [START-TIME] to the [END-TIME] with
[PERIOD] interval (or considering [SEND-PKT-NUM] packets)
• the collected DM data for the OD2WAYDMS-xxx from the [START-TIME] to the time when the
SET command is entered again with ACTION = STOP
The file is available for reading at the end of the measurement interval o after a stop and also
during the measurement (updated with defined periodicity)
When the DM instance is deleted using the DLT command, also the corresponding output file is
deleted.
Output data for the same DM tool (identified by the AID) but from different runs are appended
• max length depend on the memory available, a report (REPT TMPLSODOAM) is sent when 90%
of the available memory is used. If the max available memory is used the writing in the file is
stopped
• when one or more parameters are edited or the measurement is stopped and restarted the
associated changes are written in the output file
Needed provisioning in order to enable on-demand T-MPLS DMM on one <TUSEG, PHB> pair:
• PHB for that DM
• period: 1 sec, 10 sec, 1 minutes (default), 10 minutes
• start date and time, which shall be later than current system time
• end date and time, which shall be greater than start date and time
• packet number as alternative to start and end (number of tool packet to be sent)
• packet length: min 64 – max 1500 byte; random length between 64 and 1500 option required
Note: At node level the NE generates TMPLS OAM (the default value is T-MPLS). To
change to MPLS-TP refer to 8.9 “Administer T-MPLS/ MPLS-TP Node configuration”
(p. 504).
8.6.5 Procedure
Select action:
• To configure the DM tool, see Step 2.
• To dis/enable the DM tool, see Step 3.
• To delete the DM tool, see Step 5.
• To change the DM tool, see Step 4.
2
To configure the DM tool
Enter:
ENT-TMPLS-OD2WAYDM::AID:::[DM-PHB]:[PERIOD=][,SEND-PKT-NUM=]
[,PKT-LENGTH=][,START-TIME=][,END-TIME=] ;
where:
• AID = TUSEG where the tool has to be entered.
It is required that DIR = BIDIR for that TUSEG for the 2-way measurement.
It is required that MEP = enable for that terminated TUSEG
• DM-PHB = one of the PHB in the PHB-PROF for that Tunnel;
Note: it is not possible to configure more than one tool for a TUSEG with the same PHB;
• START-TIME = date and time (yy/mm/dd, hh/min/sec) when the sending DMM packets
interval begins
Note: start time has to be ≥ current local time (default = current local time)
• END-TIME = date and time (yy/mm/dd, hh/min/sec) when the sending DMM packets interval
ends
Note: end time has to be > start time (default = current local time + 1 min)
• SEND-PKT-NUM = number of tool packet DMM to be sent, from when the ACTION =
ENABLE (default = to be entered)
Note:
SEND-PKT-NUM is in alternative to START-TIME and END-TIME;
If no value is entered for the 3 parameter, default used is start-time = current local time and
end-time = current local time + 1 min
• PERIOD = 1 sec, 10 sec, 1 minute (default), 10 minutes.
• PKT-LENGTH = from {0, 41-1500} byte. I.e. Length in byte of DMM packet to send.
The allowed minimum value and the default value of this parameter is related to OAM-TYPE
parameter value of ENT-TMPLS-TUSEG command. The minimum/default value is:
− 41 if OAM-TYPE=T-MPLS
− 45 if OAM-TYPE=MPLS-TP
PKT-LENGTH=0 means a random length between 41 and 1500 byte
3
To dis/enable the DM tool
Enter:
SET-TMPLS-ODOAM::AID::::[TOOL=][,ACTION=];
where:
• AID =ALL , OD2WAYDMS-(1..1000). AID of “On Demand OAM Tool”
If AID=ALL then the Operator will use TOOL parameters as filter to modulate command
behavior.
Restrictions:If AID=ALL then the Operator must enter TOOL parameter. If AID<>ALL the
TOOL parameter can't be entered.
• TOOL = OD2WAYDMS. With this parameter the Operator can chose the OAM Tool when
AID=ALL
• ACTIONS = ENABLE, STOP. With this parameter the Operator can start/stop OAM tool.
For Sender OAM-Tool:
− ENABLE the tool is enabled, using the parameter configured with the ENT/ED command,
that is depending on the configured START-TIME or according to the SEND-PKT-NUM
value the MEP begins to send and receive packet.
− STOP stop sending/receiving DM packets.
This is a “general” command that can be used for enabling/stopping also other On Demand
tools.
4
To change the DM tool
Enter:
ED-TMPLS-OD2WAYDM:[TID]:AID:[CTAG]::[DM-PHB=] [,PERIOD=] [,
SEND-PKT-NUM=] [,PKT-LENGTH=][,START-TIME=][,END-TIME=] ;
where:
• AID = OD2WAYDMS-{1-10000} (On Demand OAM 2 Way DM-Tool Sender)
Restrictions: The Operator can reference only SENDER DM-Tools that have
DM-TOOL-STATE=CONFIGURED.
• DM-PHB= {EF, HIGH2, AF21, AF22, AF41, AF42, DE-G, DE-Y} or {EF, HIGH2, AF1, AF2,
AF3, AF4, DE, LOW2}, i.e. PHB value associated to DMM packets.
Restrictions: This parameter can be edited only if DM-TOOL-STATE=CONFIGURED (see
RTRV-TMPLS-OD2WAYDM command). The chosen DM-PHB must be present into PHB
profile used by Terminated TMPLS Facility where the DM-Tool has been configured. If
already exists a tool defined on Terminated TMPLS Facility with chosen DM-PHB value then
the command will be refused.
• PERIOD = Period for the transmission of DMM packets.
Restrictions: This parameter can be edited only if DM-TOOL-STATE=CONFIGURED (see
RTRV-TMPLS-OD2WAYDM command).
• SEND-PKT-NUM = Number of DMM packets to send.
Restrictions: This parameter can be edited only if DM-TOOL-STATE=CONFIGURED (see
RTRV-TMPLS-OD2WAYDM command). The System can send max 10.000 DMM packets for
this DM-Tool
• PKT-LENGTH = Length in byte of DMM packet to send.
Restrictions: This parameter can be edited only if DM-TOOL-STATE=CONFIGURED (see
RTRV-TMPLS-OD2WAYDM command).
• START-TIME = This parameter is used to establish when Sender DM-Tool starts to send
5
To delete the DM tool
Enter:
DLT-TMPLS-OD2WAYDM:[TID]:AID:[CTAG];
where:
AID = OD2WAYDMS-{1..10000}. AID of “On Demand OAM 2-Way DM-Tool”
Note:
• the sender tool can be deleted only if it is in CONFIG status (not in RUNNING and
ENABLED)
• the output file corresponding to the deleted DM tool are cancelled
6
To retrieve the DM data
Enter:
RTRV-TMPLS-OD2WAYDM:[TID]:[AID]:[CTAG]::[TERM-AID],[DM-PHB];
where:
AID = OD2WAYDMS-{1..1000}, ALL. AID of “On Demand OAM 2-Way DM-Tool”
AID or at least one of the two [TERM-AID],[DM-PHB] parameter are used for identifying the tool
default = ALL.
No one among the [TERM-AID],[DM-PHB] can’t be entered together with the AID.
7
Observe the output for SENDER tool:
OD2WAYDMS-xxxx
where DM-TOOL-STATE:
• CONFIGURED: for sender only; the creation and configuration has been done, but the tool is
not enabled so if the START-TIME is reached no packet is sent;
• ENABLED: for sender only; the sender tool has been enabled using the SET command with
ACTION = ENABLE; the tool is actually not running because current time < START- TIME or
not running because current time > END-TIME
• RUNNING: the sender tool is sending DMM packets
END OF STEPS
8.7.2 Prerequisites
None.
8.7.3 General
The ENT-FFP-TMPLS command creates a facility protection group. The following types of facility
protection group can be provisioned with (T)MPLS tunnels as protection group members with this
command:
• linear (revertive/non-revertive) bidirectional 1:1 (T)MPLS
A bidirectional 1:1 (T)MPLS FFP will consist of two tunnels (working and protection tunnel). The AID
of the FFP will be returned as output.
Note: Command restriction: The System will refuse the ENT-FFP-TMPLS command if one
of the specified tunnel (WKG or PROTN) which should become member of the new FFP is
already a member of a TMPLS GROUP previously created with the ENT-TMPLS-GROUP
command. The System will refuse the ENT-FFP-TMPLS command if at Board-Level the
reservation of resources to be used for PW in case of protection switching to the Protecting
Tunnel has as consequence the reaching of the maximum number of MPLS PW that can be
created on the card: there is a resources pool to be shared in general at NNI (for BIDIR o
UNIDIR_OUT Tunnel and PW, <port,VLAN>).
The RTRV-FFP-TMPLS command retrieves provisioned parameter values, pertaining to the
specified FFP protection group. The RTRV-FFP-TMPLS command is executed regardless of the
state of the specified facility.
The RTRV-FFP-TMPLS command retrieves provisioned parameter values and the current switching
state for all the provisioned facility protection groups.
This command return also the Access Control Domain to know if the FFP has been created
manually (by means this procedure) or via control plane (please refer to 8.15 “Administer T-MPLS
Tunnel” (p. 524)).
The ED-FFP-TMPLS command modifies the FFP protection group previously provisioned through
ENT-FFP-TMPLS. It allows the user to change facility protection group attributes: Wait_To_Restore
time value and Hold-off timer value. Upon successful completion of ED-FFP-TMPLS, parameter
changes will be applied to the protection switching group and the system will send a REPT DBCHG
(report database change) message to all non-originator users.
The DLT-FFP-TMPLS command deletes a (T)MPLS facility protection group. Upon completion of
the DLT-FFP-TMPLS command, the protection group is deleted, and the working facilities that have
been disassociated from facility protection function as unprotected facilities. In addition the
protection facility can be used again for normal unprotected traffic.
The RLS-PROTNSW-TMPLS command is used to clear a protection switch request on a TMPLS
FFP group.
The OPR-PROTNSW-TMPLS command is used to initiate protection commands for provisioned
facility protection groups.
The OPR-PROTNSW-TMPLS command can be used for the following FFP types:
• 1:1 (T) MPLS Protection
User requests initiated with this command remain active until released via the RLS-PROTNSW-
TMPLS command or overridden by a higher priority protection switch request (i.e., Lockout or a SF
condition on the working or protection tunnel, or a forced switch request on the working or
protection tunnel).
Assignment of protection resources is made in response to automatic or user initiated requests.
The RLS-PROTNSW-TMPLS command can be used for the following FFP types:
• 1:1 TMPLS Protection
On successful completion of this command, the system will reassess the switching conditions which
are present of the FFP group identified by the specified by the AID, and will honor the highest
priority request. This request may not have been honored earlier because of an earlier requested
higher priority protection switch command.
If the FFP is provisioned to work in revertive mode and the current switch request state is Wait-To-
Restore, the RLS-PROTNSW-TMPLS will terminate the wait-to-restore timer and therefore the
service will be switched back to working.
Note: At node level the NE generates TMPLS OAM (the default value is T-MPLS). To
change to MPLS-TP refer to 8.9 “Administer T-MPLS/ MPLS-TP Node configuration”
(p. 504).
8.7.5 Procedure
1
Select action.
To retrieve T-MPLS Facility Protection Group information, go to Step 2.
To create T-MPLS Facility Protection Group, go to Step 5.
To modify T-MPLS Facility Protection Group parameters, go to Step 7.
To delete T-MPLS Facility Protection Group, go to Step 9.
To initiate protection commands for provisioned T-MPLS Facility Protection Groups, go to Step
10
To clear a protection switch request on a TMPLS FFP group, go to Step 11
To end this procedure, go to Step 12.
2
Retrieve T-MPLS Facility Protection Group information
Enter RTRV-FFP-TMPLS::AID:;
where: AID =Access identifier of the FFP to retrieve. Possible values: ALL or FFPTUNNEL-{1-
7}-{1-9}-{1-4000} in the Rack, Shelf, FFP index, format.
3
Examine output for provisioning information, as detailed in the relevant command guide, refer to
“Command details” (p. 107).
4
Go to Step 1.
5
Create T-MPLS Facility Protection Group
Enter ENT-FFP-TMPLS::::::WKG=,PROTN=[,LAYER=][,RVRTTIM=][,PTYPE
=][,RVRT=][,HLDFFTTIM=][,APSPHB=][,FFP-ID=];
where:
• WKG = Access identifier of the working tunnel. Possible values: TUNNEL-{1-7}-{1-9}-{1-
10000}-{0-65535}-{0-255}-{0-255}-{0-255}-{0-255}-{0-255}-{0-255}-{0-255}-{0-255} in the
Rack, Shelf, FFP Id, FFP Instance format.
Restriction: The Tunnel used as TUNNEL-WKG can’t be referenced by a TUSEG with
ADD-GROUP = TRUE. The bandwidth of the protecting tunnel should always be >= respect
to the bandwidth of the protected tunnel If the working TUNNEL has STATUS=OFF then the
command shall be rejected.
• PROTN = Access identifier of the protecting tunnel. Possible values: TUNNEL-{1-7}-{1-9}-{1-
10000}-{0-65535}-{0-255}-{0-255}-{0-255}-{0-255}-{0-255}-{0-255}-{0-255}-{0-255} in the
Rack, Shelf, FFP Id, FFP Instance format.
Restriction: The Tunnel used as TUNNEL-PROTN can’t be referenced by a TUSEG with
ADD-GROUP = TRUE. The bandwidth of the protecting tunnel should always be >= respect
to the bandwidth of the protected tunnel If the protecting TUNNEL has STATUS=OFF then
the command shall be rejected.
• RVRT= Determines if the protection shall be revertive or not.
Y = Automatically reverts to working.
N = Doesn't revert automatically.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
6
Go to Step 1.
7
Modify T-MPLS Facility Protection Group parameters
Enter ED-FFP-TMPLS::AID::::[RVRTTIM=][,HLDFFTTIM=][,APSPHB=][,FFP-ID=];
where:
• AID =Access identifier of the FFP to edit. Possible values: FFPTUNNEL-{1-7}-{1-9}-{1-4000}
in the Rack, Shelf, FFP index, format.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
8
Go to Step 1.
WARNING
Optional Content
The deletion can only be executed against TUNNEL facilities that are provisioned as a
protection group (e.g., provisioned via the ENT-FFP-TMPLS command).
Delete T-MPLS Facility Protection Group
Enter DLT-FFP-TMPLS::AID:::[KEEP];
• AID =Access identifier of the FFP to delete. Possible values: FFPTUNNEL-{1-7}-{1-9}{1-
4000} in the Rack, Shelf, FFP index, format.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
10
To initiate protection commands for provisioned T-MPLS Facility Protection Groups
Enter OPR-PROTNSW-TMPLS::AID:::SWTCHCMD[,DESTINATION];
where:
• AID = Access identifier of the FFP to switch. Possible value: FFPTUNNEL-{1-7}-{1-9}-{1-
4000} - TMPLS TUNNEL Protection Group
• SWTCHCMD={FRCD, LOCKOUT, MAN }
Default: Entry required Addressing: None Description: Switch Command to be performed.
− FRCD=Forced Switch: If the DESTINATION identifies the protection line, a Forced Switch
to protection tunnel occurs. A Forced Switch to protection switches the specified channel
to the protection line unless a request of equal or higher priority is in effect.
− LOCKOUT= Lockout of Protection. A lockout of protection prevents the channel from
switching to the protection tunnel. If already switched to the protection side, a switch back
to working occurs.
− MAN=Manual Switch: If the DESTINATION identifies the protection tunnel, a Manual
Switch to protecting tunnel occurs. A Manual Switch to protection switches the specified to
the protection tunnel unless a request of equal or higher priority is in effect. If the
DESTINATION identifies the working tunnel, a Manual switch to working occurs. A Manual
Switch to working switches the specified channel back from the protection tunnel to the
working unless a request of equal or higher priority is in effect.
• DESTINATION={WKG, PROTN}
− WKG: Execute the requested switch action such that service ends up on the working
section of the protection group
− PROTN: Execute the requested switch action such that service ends up on the protection
section of the protection group.
Note: The following items have to be taken into account for protection states and
condition types:
• All WTR (Wait-To-Restore) values will only occur if revertive switching is supported and
provisioned at least on one end
• DNR (Do Not Revert) value will only occur if non-revertive switching is supported and
provisioned at least on one end.
11
To clear a protection switch request on a TMPLS FFP group
Enter RLS-PROTNSW-TMPLS::AID;
where:
AID = FFPTUNNEL-{1-7}-{1-9}{1-4000}
Note: A clear command will clear only those externally initiated commands issued at that
node. The clear command (i.e. RLS-PRONTSW) , will clear the WTR if the node is in
WTR state.
12
STOP. This procedure is complete.
END OF STEPS
8.8.2 Prerequisites
None.
8.8.3 General
The ED-TMPLS-GLOBAL command modifies global network parameters assigned to T-MPLS.
The RTRV-TMPLS-GLOBAL command retrieves all the global network parameters assigned to
T-MPLS by the ED-TMPLS-GLOBAL command.
8.8.4 Procedure
1
Select action.
To retrieve T-MPLS Global Network Parameters information, go to Step 2.
To modify T-MPLS Global Network Parameters, go to Step 5.
To end this procedure, go to Step 7.
2
Retrieve T-MPLS Global Network Parameters information
Enter RTRV-TMPLS-GLOBAL:::;
3
Examine output for provisioning information, as detailed in the relevant command guide, refer to
“Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
4
Go to Step 1.
5
Modify T-MPLS Global Network Parameters
Enter ED-TMPLS-GLOBAL::::::[OAM-CVPERIOD-SEL=][,PHB-RANGE-SEL=][,
OAM-TYPE-SEL=][,OAM-RX-DETECT=][,CHANNEL-TYPE=][,PROLM-MODE-BIT=];
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
6
Go to Step 1.
7
STOP. This procedure is complete.
END OF STEPS
8.9.2 Prerequisites
None.
8.9.3 General
The ED-TMPLS-GLOBAL command modifies global network parameters assigned to T-MPLS.
The RTRV-TMPLS-GLOBAL command retrieves all the global network parameters assigned to
T-MPLS by the ED-TMPLS-GLOBAL command.
8.9.6
8.9.7 Procedure
1
Select action.
To retrieve T-MPLS OAM Packets type information, go to Step 2.
To modify OAM Packets type, go to Step 5.
To perform T-MPLS to MPLS-TP migration, go to Step 7.
To end this procedure, go to Step 10.
2
Retrieve T-MPLS Global Network Parameters information
Enter RTRV-TMPLS-GLOBAL:::;
3
Examine output for provisioning information, as detailed in the relevant command guide, refer to
“Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
4
Go to Step 1.
5
Modify T-MPLS OAM Packets type
Enter ED-TMPLS-GLOBAL::::::[,OAM-TYPE-SEL=][,OAM-RX-DETECT=][,
CHANNEL-TYPE=][,PROLM-MODE-BIT=];
where
• OAM-TYPE-SEL = OAM type default selector. Default values valid at NE Level. This is the
default value assigned to the TUSegment OAM-TYPE parameter (if it is not specified by the
Operator); therefore it is possible to change the OAM type with TUSegment granularity (see
OAM-TYPE parameter of ENT-TMPLS-TUSEG command). The default value is T-MPLS.
Possible values are: T-MPLS, MPLS_TP
• OAM-RX-DETECT = General selection for OAM packets detection. The default value is
BOTH.
Possible values are:
BOTH T-MPLS and MPLS_TP. I.e. the receiver MEP accepts both “OAM T-MPLS packets”
and “MPLS_TP OAM packets”.
TYPE-SEL OAM packets type selected by OAM-TYPE-SEL parameter. I.e. the receiver MEP
accepts only “OAM packets type” established by OAM-TYPE-SEL parameter value.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
6
Go to Step 1.
7
The migration from T-MPLS to MPLS-TP can be done without interruption of the data traffic and
without spurious alarms, using the T-MPLS/MPLS-TP OAM configurability at node and MEP
levels.
8
Set first the parameter (at node level) that allows receiving both T-MPLS and MPLS-TP OAM
packets, enter:
ED-TMPLS-GLOBAL::::::[,OAM-TYPE-SEL=];
Possible values are: T-MPLS, MPLS_TP
9
Then it is possible to change the OAM packet generation from T-MPLS to MPLS-TP (default for
node or Tunnel granularity) without detecting alarms at receiving side.
Enter:
ED-TMPLS-GLOBAL::::::[,OAM-RX-DETECT=];
Possible values for the OAM-RX-DETECT parameter are:
BOTH T-MPLS and MPLS_TP. I.e. the receiver MEP accepts both “OAM T-MPLS packets” and
“MPLS_TP OAM packets”.
TYPE-SEL OAM packets type selected by OAM-TYPE-SEL parameter. I.e. the receiver MEP
accepts only “OAM packets type” established by OAM-TYPE-SEL parameter value.
It is not necessary to change the configuration in swap nodes, T-MPLS FDI continues
to be correctly received in termination nodes
10
STOP. This procedure is complete.
END OF STEPS
8.10.2 Prerequisites
In order to enable the T-MPLS Tunnel protection, it is required to create the Protection Group (see
8.7 “Administer T-MPLS Facility Protection Group” (p. 497)), constituted by a Protected (Main) Unit
and a Protecting (Spare) Unit. It is requested that the two tunnels, that assume the role of Main Unit
and Spare Unit, have been already created and activated (see 8.18 “Administer T-MPLS Tunnel
Segment Cross-Connection” (p. 535)).
PWs can be previously mapped only in the Tunnel that becomes the Protected one, the tunnel that
assumes the role of Protecting Unit must not have PWs mapped on.
The Protected and Protecting Tunnels terminates at the same node and have different T-MPLS
Tunnel labels.
The two Tunnels have the same bandwidth, use the same PHB Profile and the same Traffic
Descriptor.
PWs are mapped/demapped to/from the Protected (main) Unit. Information about the active Tunnel,
that is the tunnel that is currently carrying traffic in the Protection Group, can be retrieved, together
with other information about the Protection Group configuration and status.
It is required that before creating the Protection Group, bidirectional MEPS are created and
activated for both tunnels in the Protection Group
8.10.3 General
The Connectivity Verification (CV) function can be used in the switching criteria definition.
In order to use the CV functionality, it is required to activate the capability to send and process the
CV packets in the MEP_Source and MEP_Sink points for Tunnels in the Protection Group.
As consequence of the Protection Group activation, the system automatically activates the T-MPLS
APS OAM, in order to control protection switching operations and synchronize the actions at the
two ends of the protection domain.
The OAM APS packets are inserted/received on the Protecting (spare) Tunnel only.
By default the OAM APS packets are inserted periodically every 5 sec; in case of status change of
the protection end point 3 APS packets are inserted every 3.3 ms.
Another parameter to be configured, at Protection Group level, is the PHB for the generated APS
packets.
The other parameters that are to be configured, at Protection Group level, are the following:
• Hold-off time: time to wait before the activation of the protection switching.
• Wait-to-Restore time: fixed period of time that elapses before a normal traffic signal can use the
working path again, in revertive mode of operation.
8.10.4 Procedure
1
Bidirectional tunnels in the Protection Group creation
2
On the far end NE repeat Step 1, i.e.:
MEP-ID=spare_expmep_id,EXPMEP-ID=spare_mep_id,CVRX=ENABLE,CVTX=
ENABLE,CVPERIOD=spare_cv_period
3
Create the tunnels Traffic Descriptors and change Tunnels STATUS to ON, for details see
4.11 “ LER Tunnel Management (Tunnel Terminated)” (p. 81)
4
Create the bidirectional 1:1 (T)MPLS FFP of two tunnels (working and protection tunnel) with
the ENT-FFP-TMPLS command, for details see 8.7 “Administer T-MPLS Facility Protection
Group” (p. 497).
5
Create PWs on the Protected (main) Unit.
For details refer to 4.23 “PW Termination Management (Case of VPLS)” (p. 97) and to
4.22 “PW Termination Management (Case of point-to-point)” (p. 96)
END OF STEPS
8.11.2 Prerequisites
PW creation can be performed only via Management Plane (static) (see 8.11 “Administer T-MPLS
Pseudo Wire” (p. 510) ).
At the first time it is necessary to create the MPLS port, and the traffic descriptor which must be
associated with the Pseudo Wire.To make operative the Pseudo Wire the ED-TMPLS-PW
command must be used (with the TD and Status as ON).
8.11.3 General
Via ENT-TMPLS-PWSEG providing as reference the Tunnel Segment Index or (in case of PW
directly over physical link) the physical Interface Index a new entry is created (ifType =166). This
entry will mainly be used as "logical port" in case of VPLS (bridge port).
In case of PW termination:
• the “termination” option is chosen for TL1 command .
− in case of point-to-point: the ETS flows is associated to the PW
− in case of VPLS: the binding between VPLS instance and PW is performed.
• Via ED-TMPLS-PW (giving PW AID) it is possible to provide a Traffic Descriptor (for CAC
purposes) and association to Virtual Transport (VT).
• It is possible to move one PW from one underlying tunnel to another tunnel via ED-TMPLS-PW
(providing PW AID).
8.11.4 Procedure
1
Select action.
To retrieve T-MPLS Pseudo Wire information, go to Step 2.
To create T-MPLS Pseudo Wire, go to Step 5.
To modify T-MPLS Pseudo Wire, go to Step 7.
To delete T-MPLS Pseudo Wire, go to Step 10.
To end this procedure, go to Step 11.
2
RetrieveT-MPLS Pseudo Wire information
Enter RTRV-TMPLS-PW::AID:;
where: AID = AID of PW that defines PW AID. Possible values: ALL or PW-{1-7}-{1-9}-{1-64000}
in the Rack, Shelf, PW index, format.
3
Examine output for provisioning information on Pseudo Wire, as detailed in the relevant
command guide, refer to “Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<AID>:[,DESCR=<value>][,TD-ID=<value>][,SEGFROM-AID=<value>][,
SEGTOAID=<value>][,ROLE=<value>][,STATUS=<value>][,STATE=<value>][,
VT-HEAD=<value>][,VT-TAIL=<value>]" cr lf
[
/*
<Command_Echo>
<CTAG>
(<Session_Number>)
*/ cr lf]
;
4
Go to Step 1.
5
Create T-MPLS Pseudo Wire
Enter ENT-TMPLS-PWSEG:::::PORT,[TYPE],[DIR],[USERNAME]:
[L2ENCAPPROF-AID=][,INLABEL=][,OUTLABEL=][,PHBPROF-AID=] [,CW=];
where:
• PORT = AID of the port which is server of the MPLS PWSegment. The server can be also a
TUSegment. If the parameter refers to a port, it must be already provisioned. If the parameter
refers to a TUSegment, it must be already defined and TYPE must be equal to
TERMINATION. Possible values: MPLSIF-{1-7}-{1-9}-{2-9, 12-19}-{1-10} for Local MPLS
Interface or MPLSIF-{1-7}-{1-9}-{2-9, 12-19}-{1-128} for VCG MPLS Interface or TUSEG-{1-
7}-{1-9}-{1-20000} for Tunnel Segment.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
6
Go to Step 1.
NOTICE
8
Does Pseudo Wire Termination involved for point-to-point services?
If yes, erase services (For details, refer to 8DG09603EAAATQZZA — 1850 Transport Service
Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 Command Line Interface Guide).
If no, go to Step 1.
9
Does Pseudo Wire Termination associated to VPLS?
If yes, erase services and VPLS facility (For details, refer to 8DG09603EAAATQZZA —
1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 Command
Line Interface Guide
If no, go to Step 1.
10
Does Pseudo Wire involved in PW swapping?
If yes, see 8.13 “Administer T-MPLS Pseudo Wire Segment Cross-Connection” (p. 517).
If no, go to Step 1.
11
Delete T-MPLS Pseudo Wire Segment
Does Pseudo Wire Segment is active?
If yes, see WARNING.
If no, go to Step 12.
12
Enter DLT-TMPLS-PW::AID;
where: AID = AID of PW that defines PW AID. Possible values: ALL or PW-{1-7}-{1-9}-{1-64000}
in the Rack, Shelf, PW index, format.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
13
STOP. This procedure is complete.
END OF STEPS
8.12.2 Prerequisites
A Packet Card has to be created (see 6.67 “Provision Equipment” (p. 385) )
8.12.3 General
The ENT-TMPLS-PWSEG command creates a Pseudo Wire Segment.
Successful completion of this command generates automatically a Pseudo Wire only if
TYPE=TERMINATION. The PW parameters can be modified using ED-TMPLS-PW command. The
PW can be deleted using DLT-TMPLS-PW command.
8.12.4 Procedure
1
Select action.
To retrieve T-MPLS Pseudo Wire Segment information, go to Step 2.
To create T-MPLS Pseudo Wire Segment, go to Step 5.
To modify T-MPLS Pseudo Wire Segment, go to Step 7.
To delete T-MPLS Pseudo Wire Segment, go to Step 10.
To end this procedure, go to Step 11.
2
RetrieveT-MPLS Pseudo Wire Segment information
Enter RTRV-TMPLS-PWSEG::[AID]:::[USERNAME];
where:
• AID = Access Identifier, specifies an access to the T-MPLS PWSegments entered. This
parameter will be used when the User want retrieve complete list of PWSegments entered on
this LSR (AID=ALL) or a single PWSegment or a range of PWSegments. If the user uses this
parameter then he can't use USERNAME parameter. Possible values: ALL or PWSEG-{1-7}-
{1-9}-{1-128000} in the Rack, Shelf, PWSegment Id, format. Default value: ALL if
USERNAME parameter not provided.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
3
Examine output for provisioning information on Pseudo Wire Segment, as detailed in the
relevant command guide, refer to “Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
4
Go to Step 1.
5
Create T-MPLS Pseudo Wire Segment
Enter ENT-TMPLS-PWSEG:::::PORT,[TYPE],[DIR], [USERNAME]:
[L2ENCAPPROF-AID=][,INLABEL=][,OUTLABEL=] [,PHBPROF-AID=][,CW=]:[PST];
where:
• PORT = AID of the port which is server of the MPLS PWSegment. The server can be also a
TUSegment. If the parameter refers to a port, it must be already provisioned. If the parameter
refers to a TUSegment, it must be already defined and TYPE must be equal to
TERMINATION. Possible values: MPLSIF-{1-7}-{1-9}-{2-9, 12-19}-{1-10} for Local MPLS
Interface or MPLSIF-{1-7}-{1-9}-{2-9, 12-19}-{1-128} for VCG MPLS Interface or TUSEG-{1-
7}-{1-9}-{1-20000} for Tunnel Segment.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
6
Go to Step 1.
7
Modify T-MPLS Pseudo Wire Segment
Enter ED-TMPLS-PWSEG::AID:::[PORT],[DIR],[USERNAME]: [L2ENCAPPROF-AID=]
[,INLABEL=][,OUTLABEL=][,PHBPROF-AID=] [,CW=];
where: AID = Access IDentifier, specifies an access to the facility. Possible values: PWSEG-{1-
7}-{1-9}-{1-128000}.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
8
Go to Step 1.
9
Delete T-MPLS Pseudo Wire Segment
Does Pseudo Wire Segment involved in a cross-connection or in client services?
If yes, see WARNING.
If no, go to Step 10.
10
Enter DLT-TMPLS-PWSEG::AID:;
where: AID = Access IDentifier, specifies an access to the facility. Possible values: PWSEG-{1-
7}-{1-9}-{1-128000}.
11
STOP. This procedure is complete.
END OF STEPS
8.13.2 Prerequisites
None.
8.13.3 General
The ENT-TMPLS-CRSPWSEG command creates a cross-connect entity and establishes a one-
way, two-way cross-connection between the specified PWSegments.
Successful completion of this command generates automatically a PW (see 8.11 “Administer
T-MPLS Pseudo Wire” (p. 510) ).
The System supports a maximum of 64000 MPLS PWSegment cross connects.
The System supports the PWSegment cross connections satisfying rules described into following
Table 29, “CCT usage rules depending on PWSegment DIR parameter” (p. 517) and Table 30,
“CrsPwSeg allowed when FROM=TO” (p. 518).
8.13.4 Procedure
1
Select action.
To retrieve T-MPLS Pseudo Wire Segment Cross-Connection information, go to Step 2.
2
Retrieve T-MPLS Pseudo Wire Segment Cross-Connection information
Enter RTRV-TMPLS-CRSPWSEG::AID:;
where: AID = PWSegment AID, specifies the selected PWSegment facility to which the
command is directed. This parameter is used when the User want retrieve complete list of
PWSegment cross connections entered on this LSR (AID=ALL) or cross connections where the
PWSegment, specified by AID, is involved.. Possible values: ALL or PWSEG-{1-7}-{1-9}-{1-
128000} in the Rack, Shelf, PWSegment index, format.
3
Examine output for provisioning information on Pseudo Wire Segment Cross-Connection, as
detailed in the relevant command guide, refer to “Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<FROM>,<TO>:<CCT>" cr lf
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
4
Go to Step 1.
5
Create T-MPLS Pseudo Wire Segment Cross-Connection
Enter ENT-TMPLS-CRSPWSEG::FROM,TO:::[CCT];
where:
• FROM = PWSegment AID, identifies the FROM entity of the cross-connection. The
referenced PWSegment must have TYPE=SWAP. Possible values: PWSEG-{1-7}-{1-9}-{1-
128000}.
• TO = PWSegment AID, identifies the TO entity of the cross-connection. The referenced
PWSegment must have TYPE=SWAP. Possible values: PWSEG-{1-7}-{1-9}-{1-128000}.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
6
Go to Step 1.
7
Modify T-MPLS Pseudo Wire Segment Cross-Connection parameters
Enter ED-TMPLS-CRSPWSEG::FROM,TO:::CCT;
where:
• FROM = PWSegment AID, identifies the FROM entity of the cross-connection. Possible
values: PWSEG-{1-7}-{1-9}-{1-128000}.
• TO = PWSegment AID, identifies the TO entity of the cross-connection. Possible values:
PWSEG-{1-7}-{1-9}-{1-128000}.
• CCT = Cross-connect Type, identifies the type of cross-connect. Possible values:
− 1WAY One-Way, identifies an unidirectional cross-connection between the selected
FROM and TO facility PWSegments.
− 2WAY Two-Way, identifies a bi-directional cross-connection between the selected FROM
and TO facility PWSegments.
Default value: previously existing value.
8
Go to Step 1.
WARNING
Optional Content
A pseudowire can be deleted only if its STATUS = OFF (see 8.11 “Administer T-MPLS Pseudo
Wire” (p. 510)).
After this command, all the corresponding PWSEG and CRSPWSEG are deleted.
10
STOP. This procedure is complete.
END OF STEPS
8.14.2 Prerequisites
None.
8.14.3 General
A TD can be associated:
• to Tunnels using the 8.15 “Administer T-MPLS Tunnel” (p. 524) procedure.
• to PseudoWires using 8.11 “Administer T-MPLS Pseudo Wire” (p. 510) procedure.
A TD is the a set of CIR, CBS, PIR and PBS parameters used by the System for bandwidth checks
related to "port bit rate" or "Virtual Transport port bit rate" on which Tunnels/PseudoWires are
defined.
The User can use the following parameter for conditioning MPLS packets:
• CIR and PIR values are used for CAC checks with respect to both input Ethernet flows and
output VT bandwidth. CBS and PBS values are used only for CAC checks with respect to the
corresponding parameters of the input Ethernet flows.
When the TD will be referenced by a Tunnel (or PseudoWire) then System will check if CIR <=
(transport port bandwidth) on which the Tunnel (or PseudoWire) is defined. All CAC checks are
involved when this TD is used by a Tunnel (PseudWire).
8.14.4 Procedure
1
Select action.
To retrieve T-MPLS Traffic Descriptor information, go to Step 2.
To create T-MPLS Traffic Descriptor, go to Step 5.
To modify T-MPLS Traffic Descriptor parameters, go to Step 7.
2
RetrieveT-MPLS Traffic Descriptor information
Enter RTRV-TMPLS-TD::[AID]:;
where: AID = Access Identifier, specifies an access Identifier to the MPLS TD. Possible values:
ALL or MPLSTD-{1-10000}. Default value: ALL.
3
Examine output for provisioning information on T-MPLS Traffic Descriptor, as detailed in the
relevant command guide, refer to “Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
"<AID>:: CIR=<value>,CBS=<value>,PIR=<value>,PBS=<value>,
INUSE=<value> cr lf
[
/*
<Command
Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
4
Go to Step 1.
5
Create T-MPLS Traffic Descriptor
Enter ENT-TMPLS-TD::::::CIR=,CBS=,PIR=,PBS=;
where:
• CIR = MPLS Committed Information Rate. This parameter is valid for Tunnels and
PseudoWires and it is a positive value. The CIR value must be <= of PIR value. If this TD is
used by a Tunnel or by a PseudoWire, then CIR parameter value variation is constrained to
verification of CAC checks. Possible values: <POSITIVE INTEGER> expressed in kbit/sec.
• CBS = MPLS Committed Burst Size. This parameter is valid for Tunnels and PseudoWires
and it is a positive value. The CBS value must be <= of PBS value. If this TD is used by a
Tunnel or by a PseudoWire, then CBS parameter value variation is constrained to verification
of CAC checks. Possible values: <POSITIVE INTEGER> expressed in byte.
• PIR = MPLS Peak Information Rate. This parameter is valid for Tunnels and PseudoWires
and it is a positive value. The PIR value must be >= of CIR value. If this TD is used by a
Tunnel or by a PseudoWire, then PIR parameter value variation is constrained to verification
of CAC checks. Possible values: <POSITIVE INTEGER> expressed in kbit/sec.
• PBS = MPLS Peak Burst Size. This parameter is valid for Tunnels and PseudoWires and it is
a positive value. The PBS value must be >= of CBS value. If this TD is used by a Tunnel or
by a PseudoWire, then PBS parameter value variation is constrained to verification of CAC
checks. Possible values: <POSITIVE INTEGER> expressed in byte.
6
Go to Step 1.
NOTICE
Optional Content
Possibility of service interruption. Editing port parameters of a traffic bearing port can adversely
affect service.
If this TD is used by a Tunnel or by a PseudoWire, then CIR, PIR, CBS, PBS parameters value
variation is constrained to verification of CAC checks.
Optional Content added above. Please modify as needed.
Modify T-MPLS Traffic Descriptor parameters
Enter ED-TMPLS-TD::AID::::[CIR=][,CBS=][,PIR=][,PBS=];
where: AID = Access Identifier, specifies an access Identifier to the MPLS TD. Possible values:
MPLSTD-{1-10000}.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
8
Go to Step 1.
WARNING
Optional Content
The system is reject the command if TD is currently used (INUSE=YES) by a Tunnel or a
PseudoWire
Optional Content added above. Please modify as needed.
Delete T-MPLS Traffic Descriptor
Does Traffic Descriptor in use?
If yes, see WARNING.
If no, go to Step 10.
10
Enter DLT-TMPLS-TD::AID:;
where: AID = Access Identifier, specifies an access Identifier to the MPLS TD. Possible values:
MPLSTD-{1-10000}.
11
STOP. This procedure is complete.
END OF STEPS
8.15.2 Prerequisites
None.
8.15.3 General
The ENT-TMPLS-TUNNEL creates an LSP tunnel between source and destination point and uses
extended RSVP-TE protocol for signaling. In the LSP Tunnel set-up, input parameters for LSP
bandwidth and hop list routing are taken from TD-ID/ HOPLIST-ID values entered via ENT-
TMPLS-TD (see 8.14 “Administer T-MPLS Traffic Descriptor” (p. 521))
As result of successful response, the Control Plane automatically assigns a TUNNEL AID output
parameter to the main tunnel and, if protection is requested, a TUNNEL AID to the spare tunnel.
The former has the lower value of the Tunnel Instance parameter (that is 1) and the latter has the
highest value of the Tunnel Instance parameter (that is 2). The MEP (with default values) are
created but it is needed anyway (via 8.17 “Administer T-MPLS Tunnel Segment” (p. 531) ) to
configure MEP and MEG identifiers.
The RTRV-TMPLS-TUNNEL command retrieves TMPLS TUNNEL parameters entered with ENT-
TMPLS-TUNNEL TL1 command or edited with ED-TMPLS-TUNNEL.
Operator can retrieve routing path to destination node in different conditions (configured, computed,
actual) and issue path calculation command, based on present constrain status of the tunnel used
in a connection service. Path calculation allows user to know which will be the route before the
service is committed On the other hand, when service is active, operator can trigger calculation of
the route without affecting actual path and check difference with the "computed" path, based on
constrains status at tunnel commit.
As output parameter, the command can return also the ACD (Access Control Domain) to know if the
tunnel has been created manually (see 8.17 “Administer T-MPLS Tunnel Segment” (p. 531) and
8.18 “Administer T-MPLS Tunnel Segment Cross-Connection” (p. 535) ) or via control plane (by
means of this procedure).
The DLT-TMPLS-TUNNEL command removes a LSP Tunnel assigned by CP and by MP. Tunnel
removal is done with graceful deletion at source node. After this command, all the corresponding
TUSEG and CRSTUSEG are deleted.
8.15.4 Procedure
1
Select action.
To retrieve T-MPLS Tunnel information, go to Step 2.
To create T-MPLS Tunnel, go to Step 5.
To modify T-MPLS Tunnel, go to Step 7.
To delete T-MPLS Tunnel, go to Step 9.
To end this procedure, go to Step 10.
2
Retrieve T-MPLS Tunnel information
Enter RTRV-TMPLS-TUNNEL::AID::::[TUNNEL-ID=][,ACD=][,SHOW-DETAI
LS=][,PORT=];
where: AID = AID of LSP Tunnel that defines TUNNEL AID. It is made by six parameters: Rack,
Subrack, Tunnel Index, Tunnel Instance, Ingress LER address, Egress LER address..
Possible values: ALL or TUNNEL-{1-7}-{1-9}-{1-10000}-{1-64}-{0-255}-{0-255}-{0-255}-{0-255}-
{0-255}-{0-255}-{0-255}-{0-255} in the Rack, Shelf, Tunnel Id, Tunnel Instance format. Default
value: ALL
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
3
Examine output for provisioning information on tunnel, as detailed in the relevant command
guide, refer to “Command details” (p. 107).
Example: RTRV-TMPLS-TUNNEL::ALL::::SHOW-DETAILS=ALL;
NE162BA 10-07-14 17:08:30 M 35 COMPLD
TUNNEL-1-1-1-2-20-0-0-10-20-0-0-13:TUNNEL-ID=,ACD=CP,DIR=BIDIR,TD-ID=
MPLSTD-1,SEGTO-AID=TUSEG-1-1-2,PROT-TYPE=FULL-REROUTE,LAYER=PSC,
SRC-ADDR=20-0-0-10,DEST-ADDR=20-0-0-13,INCL-ALL=0,INCL-ANY=0,EXCL-ANY=
0,ROLE=HEAD,PRIMARY-ID=2,SETUP-PRIO=7,HOLD-PRIO=0,DIVERSITY=SRLG,
RESTORED-HOPLIST=3,TOTAL-UP-TIME=17084,PRIMARY-UP-TIME=17084,
INSTANCE-UP-TIME=17084,PATH-CHANGES=0,LAST-PATH-CHANGE=0,
CREATION-TIME=10-07-14-17-00-30,STATE-CHANGES=1,STATUS=ON,STATE=UP
TUNNEL-1-1-1-2-20-0-0-10-20-0-0-13::HOP-IPADDR=20-0-0-11,HOP-UNNUM=
MPLSIF-1-1-16-3
4
Go to Step 1.
5
Create T-MPLS Tunnel information
Enter ENT-TMPLS-TUNNEL::::::TUNNEL-ID=[,DESCR=][,DIR=],TD-ID=[,
HOPLIST-ID=][,PROT-TYPE=][,LAYER=][,SRC-ADDR=],DEST-ADDR=[,INCL-ALL=]
[,INCL-ANY=][,EXCL-ANY=][,REPLACE=][,STATUS=][,PHBPROF-AID=][,
REVERT-MODE=][,HOLD-PRIO=][,SETUP-PRIO=][,DIVERSITY=];
where:
• TUNNEL-ID = Tunnel Identifier assigned by user in the Control Plane. In case of protected
Tunnel, the TUNNEL-ID parameter value for the BackUp-Tunnel will be assigned
automatically by the System. Possible values: <1-30 VALID NAME CHARACTERS>.
• TD-ID = Traffic Descriptor Identifier (assigned by user in the Control Plane). It defines
bandwidth profile for the LSP tunnel. TD identifier can be recovered by means of the
8.14 “Administer T-MPLS Traffic Descriptor” (p. 521) procedure. For Packet connection only
PSC is supported. Command shall be rejected if matching TD could not be found. Possible
values: MPLSTD-{1-10000}.
6
Go to Step 1.
NOTICE
Optional Content
Possibility of service interruption. Editing port parameters of a traffic bearing port can adversely
affect service.
Optional Content added above. Please modify as needed.
Modify T-MPLS Tunnel
Enter ED-TMPLS-TUNNEL::AID::::[TUNNEL-ID=][,DESCR=][,TD-ID=][,
PROT-TYPE=][,STATUS=][,VT-HEAD=][,VT-TAIL=][,REVERT-MODE=];
where: AID = AID of LSP Tunnel that defines TUNNEL AID. Ingress LER address, Egress LER
address. Possible values: TUNNEL-{1-7}-{1-9}-{1-10000}-{0-6553 5}-{0-255}-{0-255}-{0-255}-
{0-255}-{0-25 5}-{0-255}-{0-255}-{0-255} in the Rack, Shelf, Tunnel Id, Tunnel Instance format.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
Go to Step 1.
CAUTION
Optional Content
It is not possible to put STATUS = OFF for a TUNNEL if this TUNNEL is part of a FFP.
It is not possible to put STATUS = OFF for a TUNNEL if there are PWs with STATUS = ON
referencing this TUNNEL.
Optional Content added above. Please modify as needed.
Delete T-MPLS Tunnel
Does tunnel has active or protected?
If no, go to Step 9.
9
Enter DLT-TMPLS-TUNNEL::[AID];
where:
• AID = AID of LSP Tunnel that defines TUNNEL AID. It is made by six parameters: Rack,
Subrack.Tunnel Id, Tunnel Instance, Ingress LER address, Egress LER address.
i.e. TUNNEL-{1-7}-{1-9}-{1-10000}-{0-65535}-{0-255}-{0-255}-{0-255}-{0-255}-{0-25
5}-{0-255}-{0-255}-{0-255}
Note: This command will be refused when the Tunnel is active, when the tunnel is
protected.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
10
STOP. This procedure is complete.
END OF STEPS
8.16.2 Prerequisites
This functionality is available for Tunnels only, they can be unidirectional or bidirectional.
8.16.3 General
ENT-TMPLS-GROUP creates an association between two Terminated Tunnels. When the TYPE of
association is BICASTANDMERGE the bicast function is implemented in the OUT direction and the
merge function is implemented in the IN direction - it is defined for Interworking scope of TSS-320
with TSS-40, when “Single Node Ring Closure” and/or “Single Node Multi Ring Closure” feature is
required.
Two Tunnels are associated; at the egress direction the traffic is bicasted, that is the same traffic is
sent on both Tunnels, at the ingress direction the traffic is received from two ports and the two
associated Tunnels are merged, actually in this interworking application packets are received only
from one port, one direction in normal condition, from the other direction in case of ring protection
activated in another node of the network.
The functionality is implemented creating and configuring the TMPLS Tunnels Group, constituted by
two already created Terminated Tunnels; one of the two Tunnel is called Working TUNNEL and the
other is called Protecting TUNNEL.
The two Tunnels associated in the TMPLS-GROUP share the same label in the ingress direction
(INLABEL), and have two different labels in the egress direction (OUTLABEL). The Tunnel used as
protecting has a specific characteristic, that is the possibility to share the ingress label with one
normal Tunnel. It is mandatory for the operator to provide this INLABEL to the Protecting TUSEG.
Furthermore the Protecting Tunnel has not the possibility to have PW attached or been used as
protecting Tunnel in a ProtectionGroup for 1:1 T-MPLS Linear Protection.
Up to 4K TMPLS Tunnels Group are available in 1850 TSS-320, TSS-320H and TSS-160.
PWs are attached to working TUNNEL using the TUSEG referenced by the Working Tunnel as port.
The only service that can be associated to PWSEG in Tunnels that are part of TMPLS Tunnels
Group is the VPLS
Up to 2000 bidirectional PWSegment can be attached to Working Tunnels that are part of MPLS-
GROUP.
When TMPLS-GROUP is deleted, the association between Tunnels is deleted and the two Tunnels
(TUNNEL-WKG and TUNNEL-PROTN) remain separate.
The DLT-TMPLS-GROUP command removes a "Tunnels Group". Upon completion of this
command, the TMPLS Tunnels Group is deleted, and the working and protecting facilities remain
disassociated. The working tunnel can be used as a normal Tunnel, instead PW can’t be connected
to the protecting Tunnel, because it has the referenced TUSEG with ADD-GROUP = TRUE. Using
the DLT-TMPLS-TUNNEL the two Tunnels can be deleted.
With regard to the OAM funcionality, the transmission of CV packets is unidirectional, in the egress
direction from the TSS320 where the Bicast&Merge is implemented.
In this TSS320 the transmission of CV have to be enabled on both Tunnels where the traffic is
bicasted (CV_TX = ENABLE); these CV packets are received and processed by TSS40s in the ring
for alarm detection.
Whereas the reception of CV from the ring has to be disabled (CV_RX = DISABLE) in the TSS320
implementing the Bicast&Merge and the transmission of CV packets has to be disabled in TSS40s
in the ring.
8.16.4 Procedure
1
Select action.
To retrieve TMPLS Tunnels Group information, go to Step 2.
To create TMPLS Tunnels Group, go to Step 4.
To delete TMPLS Tunnels Group, go to Step 6.
To end this procedure, go to Step 7.
2
Retrieve TMPLS Tunnels Group information
Enter RTRV-TMPLS-GROUP::[AID];
where: AID = AID of Tunnels Group. Possible values: ALL or TUNNELGROUP-{1-7}-{1-9}-{1-
4000}
The command returns the TUNNEL AIDs involved in the GROUP and the behavior Type of the
"Tunnels Group".
3
Go to Step 1.
4
Create TMPLS Tunnels Group
Enter ENT-TMPLS-GROUP:[TID]::[CTAG]:::TUNNEL-WRK=,TUNNEL-PROT= [,TYPE=];
where:
• TUNNEL-WRK = Tunnel AID.Restrictions: Tunnel Identifier for TUNNEL-WRK can't be the
same of Tunnel Identifier chosen for TUNNEL-PROT. The Tunnel chosen must be
TERMINATED, with ADD-GROUP = FALSE and its INLABEL must be equal to INLABEL of
the Tunnel chosen as TUNNEL-PROT
• TUNNEL-PROT = Tunnel AID. .Restrictions: Tunnel Identifier for TUNNEL-PROT can't be the
same of Tunnel Identifier chosen for TUNNEL-WRK. The Tunnel chosen must have ADD-
GROUP =TRUE and its INLABEL must be equal to INLABEL of the Tunnel chosen as
TUNNEL-WRK
• TYPE = BICAST&MERGE. Tunnels Group behavior type.
Note: Beginning in Release 4.0, the BICAST&MERGE behavior is the only supported for
"Tunnels Grouping".
If Tunnels are bidirectional then the traffic is "Bicast and Merge". When the Tunnels are
unidirectional, the traffic is bicasted if the correspondent TUSEG have DIR = UNIDIROUT,
the traffic is merged if the correspondent TUSEG have DIR = UNIDIRIN
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
5
Go to Step 1.
6
Delete TMPLS Tunnels Group
Enter DLT-TMPLS-GROUP::AID;
where:
• AID = Possible values: ALL or TUNNELGROUP-{1-7}-{1-9}-{1-4000} (Tunnels Group)
7
STOP. This procedure is complete.
END OF STEPS
8.17.2 Prerequisites
A Packet Card has to be created (see 6.67 “Provision Equipment” (p. 385) )
8.17.3 General
The ENT-TMPLS-TUSEG command shall create a TUSegment to be used on 1850 TSS-320, TSS-
320H and TSS-160 product.
Successful completion of this command generates automatically a TUNNEL only if
TYPE=TERMINATION. The TUNNEL parameters can be modified using ED-TMPLS-TUNNEL
command. This TUSegment will be automatically deleted when the TUNNEL will be deleted.
The System shall support a maximum of 20000 MPLS TUSegment.
The command might be refused if OAM resources are not available: the system shall check if
bandwidth reserved to OAM or total number of OAM points exceed value specified.
The System shall not permit to edit parameters of a TUSegment involved in a cross-connection.
Note: At node level the NE generates TMPLS OAM (the default value is T-MPLS). To
change to MPLS-TP refer to 8.9 “Administer T-MPLS/ MPLS-TP Node configuration”
(p. 504).
8.17.4 Procedure
1
Select action.
To retrieve T-MPLS Tunnel Segment information, go to Step 2.
To create T-MPLS Tunnel Segment, go to Step 5.
2
Retrieve T-MPLS Tunnel Segment information
Enter RTRV-TMPLS-TUSEG::[AID]:::[USERNAME];
where:
• AID = specifies an access to the TUSegment entered. This parameter will be used when the
User want retrieve complete list of TUSegments entered on this LSR (AID=ALL) or a single
TUSegment or a range of TUSegments. If the user uses this parameter then he can't use
USERNAME parameter. Possible values: ALL or TUSEG-{1-7}-{1-9}-{1-20000} in the Rack,
Shelf, TUSegment Id, format. Default value: ALL if USERNAME parameter not provided.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
3
Examine output for provisioning information on Tunnel Wire Segment, as detailed in the
relevant command guide, refer to “Command details” (p. 107).
Example: RTRV-TMPLS-TUSEG::TUSEG-1-1-10:TS002;
ALU-01 03-07-19 09:08:33 M TS002 COMPLD
TUSEG-1-1-10: MPLSIF-1-1-2-4, TERMINATION, BIDIR,TESTUNNEL:
INLABEL=1024, OUTLABEL=10024, PHBPROF-AID=PHBPROF-1, OAMPHB-AID=
OAMPHB-2, MEP=ENABLE, MEG-ID=/"Rome-Milan/", MEP-ID=100, EXPMEP-ID=
200, CVRX=ENABLE, CVTX=ENABLE, CVPERIOD=10ms, CVPHB=EF, ACD=CP,
ALMPROF=tunnelasap-1, ADD-GROUP=FALSE, PS-DDM-SD=ENABLED,OAM-TYPE=
T-MPLS, PROSLMCVTX=DISABLE, PROSLMCVRX=DISABLE,PROLM-PLP=6,
PROLM-SD-CROSSTH=10, PROLM-SD-CLEARTH=10,PRODM=ENABLE, PRODM-PHB=EF,
PRODM-PERIOD=1m,PRODM-PKT-LENGTH=64,TCAPROF=tunneltcap-1,RDI-SD=
ENABLE:IS
4
Go to Step 1.
5
Create T-MPLS Tunnel Segment
Enter ENT-TMPLS-TUSEG:[TID]::[CTAG]::PORT,[TYPE],[DIR],[USERNAME]:
[L2ENCAPPROF-AID=][,INLABEL=][,OUTLABEL=][,PHBPROF-AID=][,OAMPHB-AID=]
[,MEP=][,MEG-ID=][,MEP-ID=][,EXPMEP-ID=][,CVRX=][,CVTX=][,CVPERIOD=][,
CVPHB=][,ALMPROF=][,ADD-GROUP=][,PS-DDM-SD=][,OAM-TYPE=][,PROSLMCVTX=]
[,PROSLMCVRX=][,PROLM-PLP=][,PROLM-SD-CROSSTH=][,PROLM-SD-CLEARTH=][,
PRODM=][,PRODM-PHB=][,PRODM-PERIOD=][,PRODM-PKT-LENGTH=][,TCAPROF=][,
RDI-SD=];
where:
• PORT = AID of the port which is server of the MPLS TUSegment. The parameter must refer
to a provisioned port. Possible values: MPLSIF-{1-7}-{1-9}-{2-9, 12-19}-{1-10} for Local MPLS
Interface or MPLSIF-{1-7}-{1-9}-{2-9, 12-19}-{1-128} for VCG MPLS Interface.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
Note: The maximum number of MPLS TUSegments that can be created at Board-Level
depends on the available resources: there is a resources pool to be shared in general at
NNI (for BIDIR o UNIDIR_OUT Tunnel and PW, <port, VLAN>).
6
Go to Step 1.
NOTICE
Optional Content
Possibility of service interruption. Editing port parameters of a traffic bearing port can adversely
affect service.
8
Go to Step 1.
WARNING
Optional Content
10
Enter DLT-TMPLS-TUSEG::AID:;
where: AID = Access IDentifier, specifies an access to the TUSegment facility. Possible values:
TUSEG-{1-7}-{1-9}-{1-20000}.
Result: After DLT-TMPLS-TUSEG command successfully execution, all the OAM-Tools
defined on this TUSeg (see ENT-TMPLS-ODXXX commands and related) will be deleted
11
STOP. This procedure is complete.
END OF STEPS
8.18.2 Prerequisites
None.
8.18.3 General
The ENT-TMPLS-CRSTUSEG command creates a cross-connect entity and establishes a one-way,
two-way cross-connection between the specified TUSegments.
Successful completion of this command generates automatically a TUNNEL (see 8.15 “Administer
T-MPLS Tunnel” (p. 524) ).
The System supports a maximum of 10000 MPLS TUSegment cross connects.
The System supports the TUSegment cross connections satisfying rules described into following
Table 32, “CCT usage rules depending on TUSegment DIR parameter” (p. 534) and Table 33,
“CrsTuSeg allowed when FROM=TO” (p. 535).
8.18.4 Procedure
1
Select action.
To retrieve T-MPLS Tunnel Segment Cross-Connection information, go to Step 2.
To create T-MPLS Tunnel Segment Cross-Connection, go to Step 5.
To modify T-MPLS Tunnel Segment Cross-Connection parameters, go to Step 7.
To delete T-MPLS Tunnel Segment Cross-Connection, go to Step 10.
To end this procedure, go to Step 11.
2
Retrieve T-MPLS Tunnel Segment Cross-Connection information
Enter RTRV-TMPLS-CRSTUSEG::AID:;
where: AID =TUSegment AID, specifies the selected TUSegment facility to which the command
is directed. This parameter will be used when the User want retrieve complete list of
TUSegment cross connections entered on this LSR (AID=ALL) or cross connections where the
TUSegment, specified by AID, is involved.
Possible values: ALL or TUSEG-{1-7}-{1-9}-{1-20000} in the Rack, Shelf, TUSegment index,
format.
3
Examine output for provisioning information on Tunnel Segment Cross-Connection, as detailed
in the relevant command guide, refer to “Command details” (p. 107).
Example: RTRV-TMPLS-CRSTUSEG::TUSEG-1-1-10:TS002;
4
Go to Step 1.
5
Create T-MPLS Tunnel Segment Cross-Connection
Enter ENT-TMPLS-CRSTUSEG::FROM,TO:::[CCT];
where:
• FROM = TUSegment AID, identifies the FROM entity of the cross-connection. The referenced
TUSegment must have TYPE=SWAP. Possible values: TUSEG-{1-7}-{1-9}-{1-20000}.
• TO = TUSegment AID, identifies the TO entity of the cross-connection. The referenced
TUSegment must have TYPE=SWAP. Possible values: TUSEG-{1-7}-{1-9}-{1-20000}.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
Example: ENT-TMPLS-CRSTUSEG::TUSEG-1-1-10,TUSEG-1-1-20:TS001;
ALU-01 03-07-19 09:08:33 M TS001 COMPLD
TUNNEL-AID=1-1-1-120-1-0-0-0-0-0-0-0-0
6
Go to Step 1.
WARNING
Optional Content
The System supports the PWSegment cross connections satisfying rules described into Table
32, “CCT usage rules depending on TUSegment DIR parameter” (p. 535) and Table 33,
“CrsTuSeg allowed when FROM=TO” (p. 535).
The command will be refused if the TUNNEL associated to this cross connection has
STATUS=ON (see 8.15 “Administer T-MPLS Tunnel” (p. 524) )..
Modify T-MPLS Tunnel Segment Cross-Connection parameters
Enter ED-TMPLS-CRSTUSEG::FROM,TO:::CCT;
where:
• FROM = TUSegment AID, identifies the FROM entity of the cross-connection. Possible
values: TUSEG-{1-7}-{1-9}-{1-20000}.
• TO = TUSegment AID, identifies the TO entity of the cross-connection. Possible values:
TUSEG-{1-7}-{1-9}-{1-20000}.
• CCT = Cross-connect Type, identifies the type of cross-connect. Possible values:
− 1WAY One-Way, identifies an unidirectional cross-connection between the selected
FROM and TO facility TUSegments.
− 2WAY Two-Way, identifies a bi-directional cross-connection between the selected FROM
and TO facility TUSegments.
8
Go to Step 1.
WARNING
Optional Content
10
STOP. This procedure is complete.
END OF STEPS
8.19 Proactive DM
8.19.1 Purpose
This procedure provides the instructions to configure, enable/disable the Proactive DM tool at
TUSEG level on the 1850 TSS-320, TSS-320H and TSS-160 product.
8.19.2 General
The 1850 TSS-320, TSS-320H and TSS-160 supports the possibility to enable the transmission of
DMM packets at bidir TUSEG level, for each <TUSEG, PHB> pair.
It is possible to run one or more (up to 8) on-demand delay measurement tool on each MEP,
differentiated by the PHB.
It is possible to run a single proactive delay measurement tool on each MEP, for a specific PHB.
Proactive and On-demand DM tools can coexists on the same MEP, but is not possible to enable
both tools for the same PHB at the same time.
When the transmission of T-MPLS/MPLS-TP DMM is enabled on one <TUSEG, PHB> pair,
automatically also the reception of DMR is enabled.
It is required that the MEP is created for the terminated TUSEG in order to set the DM tool.
The T-MPLS/MPLS-TP DMM responder capability, that is the capability to send back the DMR
packet when the DMM one is received, is automatically present when a MEP is created on the
TUSEG from this release onwards.
The parameter provided for the provisioning of both Proactive and On-Demand DMM tool for a
<TUSEG, PHB> pair are:
the period for the generation of the DMM packets (1 sec, 10 sec, 1 minutes, 10 minutes). The
default value for period is 1 minute
packet length (min 64 - max 1500 bytes);: this is the length of the DM PDU + T-MPLS header or the
DM PDU + ACH and GAL in MPLS-TP casegenerated DMM/DMR packets; also a random length
(between 64 45 and 1500 bytes) option (with single polynomial algorithm TBC) is supported
Note: At node level the NE generates TMPLS OAM (the default value is T-MPLS). To
change to MPLS-TP refer to 8.9 “Administer T-MPLS/ MPLS-TP Node configuration”
(p. 504).
8.19.4 Procedure
1
Select action.
To enable/disable the Proactive DM functionality , go to Step 2.
To enable/freeze/disable the PM data collection for the facility, go to Step 7
To reset PM collection register to zero value, go to Step 9.
To retrieve the current 15-minute and/or 1-day PM state, go to Step 10.
To end this procedure Step 11.
2
Enable/disable the DM functionality
Enter:
RTRV-TMPLS-TUSEG::[AID]:::[USERNAME];
where:
AID = Access Identifier, specifies an access to the TUSegment entered. This parameter will be
used when the User want retrieve complete list of TUSegments entered on this LSR (AID=ALL)
or a single TUSegment or a range of TUSegments.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
3
Examine output as detailed in the relevant command guide, refer to “Command details”
(p. 107).
4
If no Proactive DM parameters have been configured on the tunnel, first change the tunnel
administrative status. Enter:
ED-TMPLS-TUNNEL::AID::::STATUS=OFF;
where:
AID = TUNNEL-{1-7}-{1-9}-{1-10000}-{0-6553 5}-{0-255}-{0-255}-{0-255}-{0-255}-{0-25 5}-{0-
255}-{0-255}-{0-255}.
AID of LSP Tunnel that defines TUNNEL AID. The former is made by six parameters: Rack,
Subrack, Tunnel Index, Tunnel Instance, Ingress LER address, Egress LER address.
5
Configure the DM on the terminated tunnel, enter:
ED-TMPLS-TUSEG::AID::::MEP=enable[,MEG-ID= ][,MEP-ID=][,EXPMEP-ID=],
CVRX=ENABLE,CVTX=ENABLE[,CVPERIOD=][,OAM-TYPE=][,PRODM=][,PRODM-PHB=]
[,PRODM-PERIOD=][,PRODM-PKT-LENGTH=];
where:
• AID = TUSEG-{1-7}-{1-9}-{1-20000}. Access IDentifier, specifies an access to the
TUSegment facility.
• MEP = ENABLE, DISABLE.
For enabling MEP function (only for termination TUSegment), the direction of MEP is
according to the direction of TUSegment. For a MEP sink point, it enables the capability to
process the received CV packets and generate the correspondent alarms.
• MEG-ID= MEG, 13 ASCII chars string.
6
Change the tunnel administrative status to ON. Enter:
ED-TMPLS-TUNNEL::AID::::STATUS=ON;
where:
AID = TUNNEL-{1-7}-{1-9}-{1-10000}-{0-6553 5}-{0-255}-{0-255}-{0-255}-{0-255}-{0-25 5}-{0-
255}-{0-255}-{0-255}.
AID of LSP Tunnel that defines TUNNEL AID. The former is made by six parameters: Rack,
Subrack, Tunnel Index, Tunnel Instance, Ingress LER address, Egress LER address.
7
To enable/freeze/disable the PM data collection for the facility
Enter:
SET-TMPLSPM-PRODM::AID:::[PMSTATE][,LOCN]:[TMPER=];
where:
• AID = TUSEG-{1-7}-{1-9}-{1-20000}.
• PMSTATE = {ON, OFF, DISABLED}
PM State, specifies whether the PM data collection is enabled or disabled.
Allowed values are:
− ON PM collection for all MONTYPE is enabled. The command resets counters. Current
data and History data are retrievable.
− OFF PM collection for all MONTYPE is disabled. Current data and History data are
retrievable.
− DISABLED PM collection for all MONTYPE is disabled. Current data and History data are
not retrievable.
At facility creation default value for PM collection is DISABLED.
When PMSTATE changes from ON to DISABLED, counters are not retrievable because
resources are released.
When PMSTATE changes from ON to OFF, collection is stopped but counters are
retrievable.
When PMSTATE changes from OFF to ON, counters are cleared (0) and collection starts
again.
When PMSTATE changes from OFF to DISABLE, counters are not retrievable because
resources are released.
When PMSTATE changes from DISABLE to OFF (or ON) , counters resources are
allocated for data collection.
When facility is deleted collection is stopped and counters resource are released.
When, on the facility referenced by AID, the OAM Tool becomes DISABLED then
collection is stopped and counters resource are released.
Note: PM can be enabled for DM only if the proactive DM tool has been enabled for the
associated termination (for TUSEG only in Rel 4.0)
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
8
To verify the settings done in the step before, enter
RTRV-TMPLSPM-PRODM::AID::::[MONTYPE=][,MONLEV=][,TMPER=] [,MONDAT=][,
MONTM=][,NUMMIN=][,NUMDAY=][,LOCN=];
where:
AID = ALL (All facilities with OAM DM enabled) or TUSEG-{1-7}-{1-9}-{1-20000} (Tunnel
Segment)
This command retrieves the current 15-minute and/or 1-day PM data corresponding to the PM
data collection register(s) selected for the specified facility.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
9
To reset PM collection register to zero value for the near-end/far-end side pertaining to the
facility specified by AID
Enter:
INIT-TMPLSPM-PRODM::AID::::[MONTYPE=][,LOCN=][,TMPER=];
where:
• AID = TUSEG-{1-7}-{1-9}-{1-20000}.
The command fails if the PM facility has PMSTATE=DISABLED.
10
Enter:
RTRV-PMMODE-PRODM::AID::::[TMPER=][,LOCN=];
where:
AID = ALL (All facilities with OAM tool enabled) TUSEG-{1-7}-{1-9}-{1-20000} (Tunnel
Segment).
11
STOP. This procedure is complete.
END OF STEPS
8.20.2 General
To enable the SLM functionality the system sets the LM Mode bit in the Flags byte of CV/CCM
packet to “1”. The position of the LM Mode bit in the reserved bits of the Flags in the CV/CCM
packet is configurable at node level. By default the LM Mode bit is transported in bit 4 of the Flags.
Max 128 SLM instances (Ethernet + T-MPLS/MPLS-TP) per 10G Packet Processor:
• 128 SLM on 10Gb card
• 128 + 128 SLM on 20Gb card
The activation of Connectivity Verification only or Connectivity Verification and Synthetic Loss
Measurement functionalities have to be done considering two different parameters in the TL1
commands:
• in order to enable the Connectivity Verification only the CVTX/CVRX parameters are to be used;
• in order to enable both Connectivity Verification and Synthetic Loss Measurement (that uses the
same CV/CCM packets) the PROSLMCVTX/PROSLMCVRX parameters are to be used
PM counters can be enabled for SLM only if the proactive SLM tool has been enabled for the
associated termination (for TUSEG only in Rel 4.0), see
Note: At node level the NE generates TMPLS OAM (the default value is T-MPLS). To
change to MPLS-TP refer to 8.9 “Administer T-MPLS/ MPLS-TP Node configuration”
(p. 504).
8.20.5 Procedure
1
Select action.
To change Proactive LM (SLM) global settings, go to Step 2.
To enable/disable the Proactive LM (SLM) functionality , go to Step 6.
To enable/freeze/disable the PM data collection for the facility, go to Step 12
To reset PM collection register to zero value, go to Step 14.
To retrieve the current 15-minute and/or 1-day PM state, go to Step 15.
To end this procedure Step 16.
2
To change Proactive LM (SLM) global settings
Enter RTRV-TMPLS-GLOBAL;
3
Examine output as detailed in the relevant command guide, refer to “Command details”
(p. 107).
4
Enter:
ED-TMPLS-GLOBAL::::::[OAM-CVPERIOD-SEL=][,PHB-RANGE-SEL=][,
OAM-TYPE-SEL=][,OAM-RX-DETECT=][,CHANNEL-TYPE=][,PROLM-MODE-BIT=];
where:
• OAM-CVPERIOD-SEL = Selector of values range for CV Period into OAM CV frames. The
default value for this parameter is 4.
• OAM-TYPE-SEL= T-MPLS, MPLS_TP.
General default value for all TUSEG in the NE default = T-MPLS.
Then it is possible to change the OAM selection with TUSEG granularity (see TUSEG
command).
• OAM-RX-DETECT = General selection for OAM packets detection. The default value is
BOTH.
• CHANNEL-TYPE = Channel Type in the ACH MPLS-TP OAM header (default = 0x7FFA)
• PROLM-MODE-BIT=Which bit to use in CV packets "flag byte" to indicate the PROactive LM
Mode. The default value is 4.
For more details refer to 8.9 “Administer T-MPLS/ MPLS-TP Node configuration” (p. 504).
5
Go to Step 1.
6
Enable/disable the SLM functionality
Enter:
RTRV-TMPLS-TUSEG::[AID]:::[USERNAME];
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
7
Examine output as detailed in the relevant command guide, refer to “Command details”
(p. 107).
8
If no Proactive LM parameters have been configured on the tunnel, first change the tunnel
administrative status. Enter:
ED-TMPLS-TUNNEL::AID::::STATUS=OFF;
where:
AID = TUNNEL-{1-7}-{1-9}-{1-10000}-{0-6553 5}-{0-255}-{0-255}-{0-255}-{0-255}-{0-25 5}-{0-
255}-{0-255}-{0-255}.
AID of LSP Tunnel that defines TUNNEL AID. The former is made by six parameters: Rack,
Subrack, Tunnel Index, Tunnel Instance, Ingress LER address, Egress LER address.
9
Configure the SLM on the terminated tunnel, enter:
where:
• AID = TUSEG-{1-7}-{1-9}-{1-20000}. Access IDentifier, specifies an access to the
TUSegment facility.
• MEP = ENABLE, DISABLE.
For enabling MEP function (only for termination TUSegment), the direction of MEP is
according to the direction of TUSegment. For a MEP sink point, it enables the capability to
process the received CV packets and generate the correspondent alarms.
• MEG-ID= MEG, 13 ASCII chars string.
• ,MEP-ID = Transmitted MEP value, integer associated to Source TUSegment Termination.
This parameter is unique inside MEG_ID.
• EXPMEP-ID = {0-8191}. Expected MEP values list, integer associated to Sink TUSegment
Termination, also called PeerMEP-ID. In case of p2p TUSegment, this is only one integer
number. In case of p2mp TUSegment, this parameter represents the list of expected MEP-ID.
• CVPERIOD{0.1ms,0.5ms,1ms,3.33ms,10ms,20ms, 50ms,100ms,1s,10s,1m,10m}. Period
(1/Frequency) of CV packet transmission
• PROSLMCVTX = {ENABLE/DISABLE}
Enabling/disabling proactive loss measurement and connectivity verification over TUSEG.
Enable Proactive CVTX + SLM functionality in Tx direction LM-Mode bit is set to 1 for
Transmitted CV packets(synthetic LM)
• PROSLMCVRX = {ENABLE/DISABLE}
Enabling/disabling proactive loss measurement and connectivity verification over TUSEG.
Enable Proactive CVRX + SLM functionality in Rx direction LM-Mode bit =1 is expected for
Received CV packets(synthetic LM)
• PROLM-PLP = {4,5,6,7,8,9}. Proactive LM Packet Loss Probability. Six values are defined in
the range from 1E-4 to 1E-9
• PROLM-SD-CROSSTH= {2-10}. Cross Threshold for proactive LM based SD monitoring
• PROLM-SD-CLEARTH= {2-10}. Clear Threshold for proactive LM based SD monitoring
• TCAPROF = The PM Threshold Crossing Alert (TCA) profile name to use with this facility.
• RDI-SD ={ENABLE/DISABLE}. Enabling/disabling RDI sending in case of Signal Degrade
detected on the TUSEG using SLM tool. This parameter is meaningful for a terminated
TUSEG with MEP = ENABLE and PROSLMCVTX=ENABLE and PROSLMCVTX=ENABLE.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
10
Note: PROSLMCVTX and PROSLMCVRX parameter are used to enable both Synthetic Loss
Measurement and Connectivity Verification tools.
It should be considered that, when enabled:
• accepted CVPERIOD are 0.1ms, 0.5ms, 1ms, 3.33ms, 10ms, 100ms
• both CVTX and PROSLMCVTX can’t be ENABLE at the same time
• both CVRX and PROSLMCVRX can’t be ENABLE at the same time
• MEG-ID, MEP-ID, EXPMEP-ID, CVPERIOD, CVPHB are the parameter used when CV
or PROSLMCV are enabled
• in order to enable the dual-ended SLM functionality both PROSLMCVTX and
PROSLMCVRX should be ENABLE
Note: Note: the 0.1ms, 0.5ms, 1ms are CV PERIOD values accepted only for enabled
SLM tool (when PROSLMCVTX = ENABLE or PROSLMCVRX = ENABLE)
11
Change the tunnel administrative status to ON. Enter:
ED-TMPLS-TUNNEL::AID::::STATUS=ON;
where:
AID = TUNNEL-{1-7}-{1-9}-{1-10000}-{0-6553 5}-{0-255}-{0-255}-{0-255}-{0-255}-{0-25 5}-{0-
255}-{0-255}-{0-255}.
AID of LSP Tunnel that defines TUNNEL AID. The former is made by six parameters: Rack,
Subrack, Tunnel Index, Tunnel Instance, Ingress LER address, Egress LER address.
12
To enable/freeze/disable the PM data collection for the facility
Enter:
SET-TMPLSPM-<tool>::AID:::[PMSTATE][,LOCN]:[TMPER=];
where:
• tool = {PRODM, PROLM}.
The parameter defines the command option for proactive DM or proactive LM.
• AID = TUSEG-{1-7}-{1-9}-{1-20000}.
• PMSTATE = {ON, OFF, DISABLED}
PM State, specifies whether the PM data collection is enabled or disabled.
Allowed values are:
− ON PM collection for all MONTYPE is enabled. The command resets counters. Current
data and History data are retrievable.
− OFF PM collection for all MONTYPE is disabled. Current data and History data are
retrievable.
− DISABLED PM collection for all MONTYPE is disabled. Current data and History data are
not retrievable.
At facility creation default value for PM collection is DISABLED.
When PMSTATE changes from ON to DISABLED, counters are not retrievable because
resources are released.
When PMSTATE changes from ON to OFF, collection is stopped but counters are
retrievable.
When PMSTATE changes from OFF to ON, counters are cleared (0) and collection starts
again.
When PMSTATE changes from OFF to DISABLE, counters are not retrievable because
resources are released.
When PMSTATE changes from DISABLE to OFF (or ON) , counters resources are
allocated for data collection.
When facility is deleted collection is stopped and counters resource are released.
When, on the facility referenced by AID, the OAM Tool becomes DISABLED then
collection is stopped and counters resource are released.
Note: PM can be enabled for SLM only if the proactive LM tool has been enabled for the
associated termination (for TUSEG only in Rel 4.0)
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
13
To verify the settings done in the step before, enter
RTRV-TMPLSPM-PROLM::AID::::[MONTYPE=][,MONLEV=][,TMPER=] [,MONDAT=][,
MONTM=][,NUMMIN=][,NUMDAY=][,LOCN=];
where:
AID = ALL (All facilities with OAM LM enabled) or TUSEG-{1-7}-{1-9}-{1-20000} (Tunnel
Segment)
This command retrieves the current 15-minute and/or 1-day PM data corresponding to the PM
data collection register(s) selected for the specified facility.
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
14
To reset PM collection register to zero value for the near-end/far-end side pertaining to the
facility specified by AID
Enter:
INIT-TMPLSPM-PROLM::AID::::[MONTYPE=][,LOCN=][,TMPER=];
where:
• AID = TUSEG-{1-7}-{1-9}-{1-20000}.
The command fails if the PM facility has PMSTATE=DISABLED.
15
Enter:
RTRV-PMMODE-PROLM::AID::::[TMPER=][,LOCN=];
where:
AID = ALL (All facilities with OAM tool enabled) TUSEG-{1-7}-{1-9}-{1-20000} (Tunnel
Segment).
16
STOP. This procedure is complete.
END OF STEPS
8.21.2 Prerequisites
The System supports only the initial value 0 to be set in the cleared counters.
8.21.3 General
PM commands operate only on provisioned ports.
PM commands are used to monitor defect conditions, and can be used to track system efficiency.
By tracking efficiency, users can recognize gradual deterioration of system performance.
RTRV-TMPLSPM-<SEG> retrieves the current 15-minute (60-minute) and/or 1-day PM data
corresponding to the PM data collection register(s) selected for the specified facility.
INIT-TMPLSPM-<SEG> initializes (reset register to zero value) the current 15/60-Minute or current
1-Day (specified by TMPER parameter) PM collection register (counters) for the near-end side
pertaining to the specified Segment. The historical counters aren't cleared.
8.21.4 Procedure
1
Select action.
To retrieve PM data, go to Step 2.
To initialize PM data collection register, go to Step 5.
To end this procedure, go to Step 7.
2
Retrieve PM Data
where:
• SEG= identifies the type of segment. PWSEG (pseudo wire segment) or TUSEG (tunnel
segment)
• AID = Access Identifier, identifies the entity access identifier. Possible values:
− ALL (all AID)
− PWSEG-{1-7}-{1-9}-{1-128000} (Pseudowire Segment)
− TUSEG-{1-7}-{1-9}-{1-20000} (Tunnel Segment)
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
3
Examine output for PM information, as detailed in the relevant command guide, refer to
“Command details” (p. 107).
cr lf lf
<SID>
<YY-MM-DD>
<HH:MM:SS> cr lf
M
<CTAG>
COMPLD cr lf
[
"<AID>:<PMSTATE>[,<MONTYPE>,<MONVAL>,<VLDTY>,<TMPER>,<MONDAT>,
<MONTM>]" cr lf]
[
/*
<Command_Echo>
[<CTAG>]
(<Session_Number>)
*/ cr lf]
;
4
Go to Step 1.
5
Initialize PM Data Collection Register
Enter INIT-TMPLSPM-<SEG>::AID::::[MONTYPE=][,TMPER=];
where:
• SEG= identifies the type of segment. PWSEG (pseudo wire segment) or TUSEG (tunnel
segment)
• AID = Access Identifier, identifies the entity access identifier. Possible value:
− PWSEG-{1-7}-{1-9}-{1-128000} (Pseudowire Segment)
− TUSEG-{1-7}-{1-9}-{1-20000} (Tunnel Segment)
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
6
Go to Step 1.
7
STOP. This procedure is complete.
END OF STEPS
8.22.2 Prerequisites
None.
8.22.3 General
The SET-TMPLSPM-<SEG> command enables/freezes/disables the PM data collection for the
PseudoWire or Tunnel Segment facility.
The System supports only Near-End PseudoWire and Tunnel Segment PM counters.
This command retrieves the current 15-minute (60-minute) and/or 1-day PM data corresponding to
the PM data collection register(s) selected for the specified facility.
The successful response for this command contains lines of parsable output data for each
provisioned AID specified. No output data is provided if the <SEG> is not provisioned or if PM
counters aren't started (PMSTATE=DISABLED) No output data is provided if the date and time
specified exceeds the available collection periods (i.e., exceeds 8 hours of 15-minute PM registers
or 7 days for 1-day PM registers).
The RTRV-TMPLSPM-<SEG> command retrieves the current and/or historical 15-minute (60-
minute) and/or 1-day PM data corresponding to the PM data collection register(s) selected for the
specified <SEG> facility.
If AID=ALL is specified, all the (enabled) <SEG> PM counters residing in the NE should be
returned.
For each monitored counter, the current and/or up to thirty-two (32) 15-minute historical PM
registers, or the current and/or up to seven (7) 1-day historical PM registers or both 15-minute and
1-day PM registers can be retrieved.
Alternatively, if PM-GRANULARITY=60, for each monitored counter, the current and/or up to thirty-
two (32) 60-minute historical PM registers, or the current and/or up to seven (7) 1-day historical PM
registers or both 60-minute and 1-day PM registers can be retrieved.
8.22.4 Procedure
1
Execute the 8.21 “Report Performance Monitoring (PM) Data for T-MPLS” (p. 550) procedure
in order to retrieve the Performance Monitoring data collection for the PseudoWire or Tunnel
Segment facility.
2
Examine output to determine current PM mode, as referred in 8.21 “Report Performance
Monitoring (PM) Data for T-MPLS” (p. 550) procedure.
3
Enter SET-TMPLSPM-<SEG>::AID:::[PMSTATE]:[TMPER=];
where:
• SEG= identifies the type of segment. PWSEG (pseudo wire segment) or TUSEG (tunnel
segment)
• AID = Access Identifier, identifies the entity access identifier. Possible value:
− PWSEG-{1-7}-{1-9}-{1-128000} (Pseudowire Segment)
− TUSEG-{1-7}-{1-9}-{1-20000} (Tunnel Segment)
The parameters between square brackets are optional. If a value is not entered for these
parameters, the system will use the default value, refer to “Command details” (p. 107).
4
STOP. This procedure is complete.
END OF STEPS
9.1 Overview
9.1.1 Purpose
The Detailed Level Procedures (DLP) contains detailed steps and supporting information required
to complete a task. When a DLP is referenced from another part of the manual, perform the DLP,
then return to the point where the DLP was referenced.
9.1.2 Contents
The non-reachability via-LAN of the Synth4 Controller should raise an ICP (CONTBUS)
ConditionType.
1662 subshelf should be provisioned with SYNTH4 modules , 63XE1 module and companion
access modules
New shelf:
• Drop Shelf AID: SHELF-1-2
• Drop Shelf ProvisionedType75ohm access: PDHACCSSHLF
• Drop Shelf ProvisionedType120ohm access: PDHACCSSHLF120
On creation of Drop Shelf and so of MTSYNTH4, the following Facilities and Connections are
autocreated
• STM4-1-2-{6,15}-{1,2}
• FFPSTM4-1-2-{6}-{1,2}(for MSP)
• STM4AU4-1-2-{6}-{1,2}-{1-4}
• MVC4-1-2-{6}-{1-6}
• A fixed Cross Connection between 6xMVC4 and 8xSTM4AU4
• MVC4TU12-1-2-{6}-{1-6}-{1-3}-{1-7}-{1-3}
• A fixed Mapping of 6x63xMVC4TU12 into the 6xMVC4
9.3.2 General
The Drop shelf should be provisioned using the ENT-EQPT command.
The RTRV-FSVDATA command addressed to a Drop Shelf will retrieve all the firmware/software/
configuration file versions of the addressed shelf.
The RTRV-LNKMTX-STATUS command retrieves the status (fail/nofail) of the NGI links from/to all
the IOC (eg.E1M) slots to/from the matrix (eg MSYNTH4) slots.
9.3.4 Procedure
Select action:
• Provision the 1662 subshelf, go to Step 2
• Deprovision the 1662 subshelf, go to Step 5
• Modify the 1662 subshelf parameters, go to Step 4
2
Provision the 1662 subshelf
Enter:
ENT-EQPT::SHELF-1-2:::: PROVISIONEDTYPE= PDHACCSSHLF/PDHACCSSHLF120,
SHELFROLE=NOMAIN;
For parameter descriptions of TL1 commands used in this procedure, refer to the .
3
Enter:
RTRV-EQPT::AID;
The command addressed to a Drop Shelf retrieves all the provisioned equipment information
related to the same shelf (e.g. the Shelf Type) and to the Equipment Entities provisioned in it.
4
Modify the 1662 subshelf
Enter:
ED-EQPT::AID::::[,ALMPROF=]:[PST];
where:
• AID = 1662 subshelf. Access Identifier
• ALMPROF = The Alarm Severity Assignement profile (ASAP) name to use with this
equipment entity
• PST = Primary State, specifies the primary state to which the equipment is set.
Note: ASAP profile is the ONLY parameter that could be changed. Other parameters
editing is denied
For parameter descriptions of TL1 commands used in this procedure, refer to the .
5
Delete the 1662 subshelf
Enter:
RTRV-EQPT::SHELF-1-2;
6
The specified equipment entity must be in an OOS-[AU]MA state.
If not enter the remove command:
RMV-EQPT::SHELF-1-2;
7
Enter:
RTRV-EQPT::SHELF-1-2;
Result: The specified equipment entity state changed in OOS-[AU]MA state.
8
Deprovision the shelf using the following command:
DLT-EQPT::SHELF-1-2;
END OF STEPS
• 63 E1 Protection Card
9.4.2 Procedure
Select action
• To create E1 port module E1M, go to Step 2.
To delete E1 port module E1M, go to Step 3.
• create E1 protection module E1PR, go to Step 4.
To delete E1 protection module E1PR, go to Step 5.
• create E1 access module E1ACC, go to Step 6
To delete E1 access module E1ACC, go to Step 7.
• Create a pair of E1M and E1ACC module, go to Step 8
• Create a pair of E1PR and E1ACC module, go to Step 9
2
E1 port module E1M creation
Enter:
ENT-EQPT::AID::::[PROVISIONEDTYPE=][,AINSMODE=][,ALMPROF=][,SSBIT=]:
[PST];
where:
• AID = E1M-{1-7}-{2}-{7-14} ETSI (63 E1 Multiplexer Card).
I.e. The Equipment Access Identifier, identifies the equipment entity access identifier
• PROVISIONEDTYPE = P63E1 ETSI 63 x E1 Port Module.
No other Autocreation is implied.
For parameter descriptions of TL1 commands used in this procedure, refer to the .
3
E1 port module E1M deletion
where:
• AID = E1M-{1-7}-{2}-{7-14} ETSI (63 E1 Multiplexer Card).
I.e. The Equipment Access Identifier, identifies the equipment entity access identifier
4
E1 protection module E1PR creation
Enter:
ENT-EQPT::AID::::[PROVISIONEDTYPE=][,AINSMODE=][,ALMPROF=][,SSBIT=]:
[PST];
where:
• AID = E1PR-{1-7}-{2}-{2,19} ETSI (63 E1 EPS Card)
I.e. The Equipment Access Identifier, identifies the equipment entity access identifier
• PROVISIONEDTYPE = LSPROT - ETSI 63 x E1 Access Protection Module
No other Autocreation is implied.
5
E1 protection module E1PR deletion
where:
• AID = E1PR-{1-7}-{2}-{2,19} ETSI (63 E1 EPS Card)
I.e. The Equipment Access Identifier, identifies the equipment entity access identifier
6
E1 access module E1ACC creation
Enter:
ENT-EQPT::AID::::[PROVISIONEDTYPE=][,AINSMODE=][,ALMPROF=][,SSBIT=]:
[PST];
where:
• AID = E1ACC-{1-7}-{2}-{3-5,16-18} ETSI (63 E1 Access Card)
I.e. The Equipment Access Identifier, identifies the equipment entity access identifier
• PROVISIONEDTYPE = A63E1A/A63E1B: i.e. ETSI 63 x E1 Access Module 75ohm unb/
ETSI 63 x E1 Access Module 120ohm bal
No other Autocreation is implied.
7
E1 access module E1ACC deletion
DLT-EQPT::AID;
where:
• AID = E1ACC-{1-7}-{2}-{3-5,16-18} ETSI (63 E1 Access Card)
I.e. The Equipment Access Identifier, identifies the equipment entity access identifier
8
Create a pair of E1M and E1ACC module
Provision 63XE1 module on 1662 subshelf and its companion access module in working slots.
As soon as a pair E1M-E1ACC is created with ENT-EQPT, also all the related (fixed)
connections are created (i.e. 2WAY connections from VC12 on E1M-E1ACC to TU12 on
SYNTH).
9
Create a pair of E1PR and E1ACC module
As soon as a pair E1PR-E1ACC spare is created with ENT-EQPT, also all the related EPS
group is created.
END OF STEPS
When the subshelf is deleted all the above mentioned facilities, FFPS and crossconnections are
automatically deleted.
Six PTF instances of MODVC4 are automatically created/deleted on a 1662 subshelf when the
shelf is provisioned. These MODVC4s have limited fixed capabilities and are always terminated in
63 TU12s.
63 instances of PDHLOVC12 are automatically creted/deleted on a 1662 sub shelf whenever a
63xE1 module is provisioned. These facilities have limited fixed capabilities and are always
terminated in 63 E1s.
9.6.2 General
The ED-TUn command modifies the specified facility parameter values for a previously auto-
created tributary instance in the context of PTF provisioning (i.e. LO payload structure) provisioning.
An TUn instance represents the management view of the following SDH transmission functions:
• HO/LO Adaptation Function (individual sink/source function)
• Ingress LO Non-Intrusive Monitor (NIM)/Path Overhead Monitor (POM)
• Egress LO Non-Intrusive Monitor (NIM)/Path Overhead Monitor (POM)
The ED-E1 command modifies the specified facility parameter values previously provisioned via
autoprovisioning.
For an E1 located on a 1662 sub shelf, provisioning is restricted to the following parameters:
AINSTH, ALMPROF, PST and SST
Ingress and egress directions are defined by the following conventions: Egress side is always the
side received from the internal TDM matrix/cross-connect and Ingress side is always received from
the physical port or packet source
For parameter descriptions of TL1 commands used in this procedure, refer to the 1850 Transport
Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 TL1 Command Guide.
9.6.3 Procedure
Select action:
• to manage STM4 attributes, go to Step 2
• to manage 1662 subshelf STM4AU4 facility, go to Step 4
• to manage 1662 subshelf MVC4 and LOVC12 facilities, go to Step 6.
• to manage 1662 subshelf TU12 facilities, go to Step 8
• to manage 1662 subshelf E1 facilities (i.e.:RTRV-E1 , ED-E1), go to Step 10
• to retrieve 1662 subshelf STM4 FFP information (i.e.:RTRV-FFP-STM4), go to Step 12
2
Manage STM4 attributes
Enter:
ED-STM4::AID::::[AINSTH=][,PMODE=][,AINSCRIT=][,PSTCORR=][,ALMPROF=][,
TCAPROF=][,CMDMDE=]:[PST],[SST];
where:
AID = STM4-{1-7}-{2}-{6,15}-{1-2} (STM4 on an SYNTH4 on PDH ACC shelf).
Above are present only the STM4 editable parameters.
3
Enter:
RTRV-STM4::AID;
where:
AID = STM4-{1-7}-{2}-{6,15}-{1-2} (STM4 on an SYNTH4 on PDH ACC shelf).
Result: Ouput retrievable parameters are: PORTTYPE, AINSTIMER, CAPLIST, MGRACD,
FFPAID.
4
Manage 1662 subshelf STM4AU4 facility
Enter:
ED-AU4::AID::::[AINSTH=][,ALM PROF=][,TCAPROF=][,CMDMDE=]:[PST],[SST];
where:
AID = AU4 for AU4 tributary.
Above are present only the AU4 editable parameters.
5
Enter:
RTRV-AU4::AID;
where:
AID = AU4 for AU4 tributary..
Result: Ouput retrievable parameters are: AINSTIMER, MGRACD.
6
Manage 1662 subshelf MVC4 and LOVC12 facilities
Enter:
ED-PTF::AID::::[AINSTH=][,ALMPROF=][,TCAPROF=][,CMDMDE=]:[PST],[SST];
where:
AID = PTF Access Identifier, specifies the PTF facility.
7
Enter:
RTRV-PTF::AID::::PTFTYPE=,PTFRATE=[,PARMS=][,TRCFMT=];
AID = PTF Access Identifier, specifies the PTF facility.
8
Manage 1662 subshelf TU12 facilities
(i.e.:RTRV-TU12 , ED-TU12),
Enter:
ED-TU12::AID::::[AINSTH=][,ALMPROF=][,CMDMDE=]:[PST],[SST];
where:
9
Enter:
RTRV-TU12::AID::::[PARMS=][,TRCFMT=];
where:
AID = MVC4TU12-{1-7}-{2}-{6}-{1-6}-{1-3}-{1- 7}-{1-3} (TU12 within a MVC4 on SYNTH4
module on a 1662 PDH access shelf).
Result: Ouput retrievable parameters are: AINSTIMER, MGRACD.
10
Manage 1662 subshelf E1 facilities
Enter:
ED-E1::AID::::[AINSTH=][,CMDMDE=][,ALMPROF=]:[PST],[SST];
where:
AID = E1-{1-7}-{2}-{8-10, 11-13}-{1-63} (E1 on the PDH Access shelf E1 Port Module)
E1-{1-7}-{1-9}-{1-6}-{1-42} - E1 on the PDH Port Module of 1646 shelf
Above are present only the AU4 editable parameters.
11
Enter:
RTRV-E1::AID::::[PARMS=];
where:
AID = E1-{1-7}-{2}-{8-10, 11-13}-{1-63} (E1 on the PDH Access shelf E1 Port Module)
Result: Ouput retrievable parameters are: AINSTIMER, MGRACD, PORTTYPE.
12
Retrieve 1662 subshelf STM4 FFP information
RTRV-FFP-STM4::AID;
where:
FFPSTM4-{1-7}-{2}-15-{1-2} (STM4 Facility Protection Group on PDH Access Shelf)
Result: Ouput retrievable parameters are: PTYPE, WKG, PROTN, PSDIRN, PROTOCOL,
ACTIVE,CURRREQ.
END OF STEPS
9.7 Database backup and restore from remote file server on 1662
subshelf
9.7.1 Purpose
Use this procedure to perform the database backup and restore from remote file server.
9.7.2 General
The ACT-DB-BACKUP command performs a backup of the primary backup data base (ACT DSK
DB) to the secondary backup data base (STBYDB).
The RTRV-DB-LABEL command reads the database label of the selected backup database stored
on the NE (ACT DSK DB or STBYDB).
The RTRV-RFILE command is used to read information related to transferred files (i.e. database)
on a Remote File Server.
9.7.4 Procedure
1
Initiate database backup
Enter:
ACT-DB-BACKUP;
The ACT-DB-BACKUP command is executed for creating an standby database.
2
Observe the ACT-DB-BACKUP command response.
3
Check completion of database back up reported by REPT DB msg.
4
Retrieve the DB label, enter:
RTRV-DB-LABEL;
Result: Retrieval shows that the database date and time are the latest backup date and
time.
5
Check the time and date. It should be the latest date and time of back up.
6
Upload the file to the RFS.
Execute the command:
COPY-RFILE::STBYDB,RFSDB::::LOCATION=;
i.e.:
the backup is transferred from the standby to the RFS with the format with the specific location.
7
Retrieve the contents on the RFS: via and verify the date and time is for the most recent
transfer.
RTRV-RFILE::AID::::LOCATION=;
where:
AID = Identifies the database for which the information is retrieved.
Possible values are:
RFSDB - A database backup on a Remote File Server
Location indicates the source/destination of the transferred files on an RFS. The syntax of the
url is as follows:
“ftp ://[<userid>[:<password>]@]<ftphost>[:<port>]/<url_path>”
Result: Retrieval shows that the database backup is created on the RFS and the date and
time are for last transfer.
8
The database on the RFS can be downloaded to the standby via:
COPY-RFILE:: RFSDB,STBYDB::::LOCATION=;
with the location specified.
Result: the database has been downloaded onto the standby.
9
Retrieve the DB label:
RTRV-DB-LABEL;
10
Check the time and date. It should be the latest date and time of back up.
Result: Retrieval shows the backup date and time are the most recent date and time.
11
Enter:
RESTORE-DB;
the downloaded database has been restored on the primary database backup
12
Verify that this database is correct.
13
Enter:
RTRV-DB-LABEL::ACTDSKDB;
and
RTRV-RFILE::AID::::LOCATION=;
These commands are executed on the primary and RFS to check for the database information.
14
Check that all services are restored.
END OF STEPS
9.8.2 General
Commands are valid for ETSI region only.
The RTRV-PMMODE-E1 command retrieves the PM mode setting (whether PM data collection is
enabled) for the specified facility.
The SET-PMMODE-E1 command sets the mode of PM data collection for the specified facility.
9.8.4 Procedure
1
To check the PM state enter:
RTRV-PMMODE-E1::AID:::[LOCN],[DIRN]:[TMPER=];
where:
AID = ALL, i.e. Access Identifier, identifies the entity access identifier. Only valid sdhFacility/AID
combinations are allowed, all other shall be rejected.
Result: The command returns the PM State. Default PM state is disabled.
2
To “enable”or “disable” PM state enter:
SET-PMMODE-E1::AID:::LOCN,MODETYPE,[PMSTATE],[DIRN]:[TMPER=];
where:
AID = ALL, i.e. Access Identifier, identifies the entity access identifier. Only valid sdhFacility/AID
combinations are allowed, all other shall be rejected.
LOCN = Location specifies the location where PM data collection is to be enabled or disabled.
Values are:
• ALL PM for all applicable parameters is configured
• P PM for E1 parameters is configured.
The previous values are applicable for E1 facility.
PMSTATE = {ON, OFF, DISABLED}. PM State, specifies whether the PM data collection for the
specified mode type is enabled or disabled.
3
Repeat Step 1 to check if the PM state has been enabled/disabled on E1.
4
Check PM data is collected. Enter:
RTRV-PM-E1::AID:::[MONTYPE],[MONLEV],[LOCN],[DIRN],[TMPER],[MONDAT],
[MONTM],[NUM15MIN],[NUM1DAY];
where:
AID = ALL, i.e. Access Identifier, identifies the entity access identifier. Only valid sdhFacility/AID
combinations are allowed, all other shall be rejected.
5
To enable both 15-min and 1-day PM.
END OF STEPS
9.9.2 General
Commands are valid for ETSI region only.
The RTRV-PMMODE-STM4 command retrieves the PM mode setting (whether PM data collection
is enabled) for the specified facility.
The SET-PMMODE-STM4 command sets the mode of PM data collection for the specified facility.
9.9.3 Procedure
1
To check the PM state enter:
RTRV-PMMODE-STM4::AID:::[LOCN],[DIRN]:[TMPER=];
where:
AID = STM4-{1-7}-{2}-{6,15}-{1-2} (STM4 on an SYNTH4 on PDH ACC shelf)
Result: The command returns the PM State. Default PM state is disabled.
2
To “enable”or “disable” PM state enter:
SET-PMMODE-STM4::AID:::LOCN,MODETYPE,[PMSTATE],[ DIRN]:[TMPER=];
where:
AID = Access Identifier, identifies the entity access identifier. Only valid sdhFacility / AID
combinations are allowed, all other shall be rejected. Possible values:
• STM4-{1-7}-{2}-{6,15}-{1-2} (STM4 on an SYNTH4 on PDH ACC shelf)
• STM4AU4-{1-7}-{1-9}-{2-9,12-19,21-36} -{1-8}-{1-4} (AU4 embedded within an STM4)
• MVC4-{1-7}-{2}-{6}-{1-6} (MVC4 on an SYNTH4 on 1662 PDH Access shelf)
• MVC4TU12-{1-7}-{1-9}-{21,22,35,36}-{1 -64}-{1-3}-{1-7}-{1-3} (TU12 embedded within a
Modifiable VC4)
• PDHLOVC12-{1-7}-{2}-{8-10, 11-13}-{1-63} (VC12 with E1 client on the PDH Access shelf E1
Port Module)
LOCN = Location specifies the location where PM data collection is to be enabled or disabled.
Values are:
• ALL PM for all applicable parameters is configured
• {S, L, P}, i.e.:
P PM for Path parameters is configured.
S PM for RS parameters is configured
L PM for MS parameters is configured
The previous values are applicable for STM4 facility.
PMSTATE = {ON, OFF, DISABLED}. PM State, specifies whether the PM data collection for the
specified mode type is enabled or disabled.
3
Repeat Step 1 to check if the PM state has been enabled/disabled on STM4.
4
Check PM data is collected. Enter:
RTRV-PM-STM4::AID:::[MONTYPE],[MONLEV],[LOCN],[D IRN],[TMPER],
[MONDAT],[MONTM],[NUM15MIN],[NUM1DAY];
where:
AID = Access Identifier, identifies the entity access identifier. Only valid sdhFacility / AID
combinations are allowed, all other shall be rejected. Possible values:
• STM4-{1-7}-{2}-{6,15}-{1-2} (STM4 on an SYNTH4 on PDH ACC shelf)
• STM4AU4-{1-7}-{1-9}-{2-9,12-19,21-36} -{1-8}-{1-4} (AU4 embedded within an STM4)
• MVC4-{1-7}-{2}-{6}-{1-6} (MVC4 on an SYNTH4 on 1662 PDH Access shelf)
• MVC4TU12-{1-7}-{1-9}-{21,22,35,36}-{1 -64}-{1-3}-{1-7}-{1-3} (TU12 embedded within a
Modifiable VC4)
• PDHLOVC12-{1-7}-{2}-{8-10, 11-13}-{1-63} (VC12 with E1 client on the PDH Access shelf E1
Port Module)
5
To enable both 15-min and 1-day PM.
END OF STEPS
10 CLI Procedures
10.1 Overview
10.1.1 Purpose
CLI procedures list the major steps required to complete a task.
10.1.2 Contents
Note: This command does not apply to Optical FE and 10GE interfaces, since they do not
support autonegotation, and to Electrical 1GE interfaces, since they support mandatory
autonegotation. It applies to Electrical FE and optical 1GE interfaces that support configurable
autonegotation.
10.2.2 Prerequisites
The node shall be equipped with data modules.
10.2.3 General
The 1850TSS at the startup has autonegotation disabled on interface mau.
Specifically, the System shall operate, the FE/GE autonegotation process, as follows:
• full duplex capability shall be supported by the System
• one locally supported speed is assumed as provisioned by manager.
• both symmetric/asymmetric “pause function” shall be supported and advertised.
The management system is required to also set a “default MAU mode” to which the MAU must
revert when the autonegotation is disabled.
The management system can, at any time, force an autonegotation restart.
10.2.4 Procedure
1
Select action:
To retrieve the autonegotation value, go to Step 2
To enable or disable the autonegotation, go to Step 3
To restart the autonegotation between network devices, go to Step 4
To set the autonegotiation capability to be advertised, go to Step 5
For details, refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160)
Release 5.1 Command Line Interface Guide.
2
Retrieve the autonegotation value
Enter interface position namingsetlist localeth show autoneg
where
• namingsetlist is one or more ports on which autonegotation should be retrieved
3
Enable or disable the autonegotation
Enter interface position namingsetlist localeth autoneg {enable |
disable}
where:
namingsetlist is one or more ports on which autonegotation should be enabled or disabled
4
Restart autonegotation
Enter interface position namingsetlist localeth autoneg restart
where:
namingsetlist is one or more ports on which autonegotation should be restarted.
5
Set autonegotation
Enter interface position namingsetlist localeth
autonegadvertisedcapability [10 | 100 | 1000 | 10&100 | 10&100&1000]
[nopause | asympause | asym&sympause]
where:
namingsetlist is one or more ports on which autonegotation parameters should be modified.
6
STOP. This procedure is complete.
END OF STEPS
10.3.2 Prerequisites
The 1850TSS shall be equipped with one or more DATA boards. The first Ethernet Flow Classifier is
automatically created by default during the ETS flow creation.
Generally users adds classifiers to the first one that is defined when an ETS InFlow is created. The
creation of a Classifier criteria requires corresponding ETS InFlow (with Ethernet or ATM as Service
Type) to be both previously created and activated.
10.3.3 General
10.3.4 Procedure
1
Select action
To create, configure and activate an ETS InFlow classifier a go to Step 2.
To remove an ETS InFlow classifier go to Step 3.
To get an ETS InFlow classifier information go to Step 4.
2
Create, configure and activate an ETS InFlow classifier
Before adding a inflow classifier an ETS InFlow should exist, see 10.4 “ Administer ETS to
Provider Bridge ETS/PW/VPLS bidirectional flow ” (p. 582).
Enter:
inflowclassifier add flowuserlabel [vlan {vlan_id[maxvlan_id] |
dontcare| untagged }] [pri {pri[maxpri] | dontcare | untagged }] [dscp
{dscp[maxdscp] | dontcare | noip}] [etype {ethertype_value | dontcare
}] }] [vpi {vpi_id[maxvpi_id] }] [vci {vci_id[maxvci_id] }]
where
flowuserlabel is the ETS InFlow name.
ETS Classifier Criteria with IP as EtherType specific value is allowed only on ETS ports
supporting ETS Classifier Criteria’s over VLAN Priority (either specific or range):
ETS Classifier Criteria with IP as EtherType specific value is mutually exclusive (on the same
ETS port) with ETS Classifier Criteria's over DSCP (either specific or range).
Default values:
• If VLAN, PRI or DSCP parameter is absent, it is set to “dontcare”
• If the optional maximum value for either VLAN, PRI or DSCP is absent, the corresponding
SNMP attribute is set to 0.
• VLAN untagged implicitly means also PRIO untagged.
3
Retrieve ETS InFlow classifier
Enter inflowclassifier show flowuserlabel
This command gets information for each defined classifier (also including classifier index). The
information can be scoped to classifiers for a certain ETS InFlow by indicating the flow user
label.
The output is something like:
4
Remove ETS InFlow classifier
Enter
Note: Attention during this operation only the ETS flow classifier is removed not the ETS
InFlow
Note: Attention during this operation if the default ETS flow classifier is removed all
packets are dropped at ingress.
END OF STEPS
10.4.2 Prerequisites
The 1850TSS shall be equipped with one or more DATA boards.
10.4.3 General
ETS Flow Management This section exploits below NE functional blocks involved in Traffic
classification and ETS Flow Management (Figure 2) and their mapping with NE Functional
architecture:
• Classifier.
• ETS Flow Meter/Policer.
• ETS Flow Cross Connector.
• ETS Flow Adapter.
The figure below exploits below NE functional blocks involved in Traffic classification and ETS Flow
Management and their mapping with NE Functional architecture:
Configuration concerns:
• optional classification mode. It is based on PRI bits (default value) or IP DSCP bits;
• Classifier definition and association. User can add later new classifiers for this ETS InFlow;
• traffic descriptor association to the ETS InFlow. It carries information of CoS and traffic descriptor
parameters;
• traffic descriptor association to the ETS Provider Bridge InFlow. It carries information of CoS with
null traffic descriptor parameters. If not present, the same CoS of the ETS InFlow in the
corresponding bidirectional connection is used ;
• a choice among: SVID definition for the Provider Bridge ETS InFlow/OutFlow; or PW for PW
ETS InFlow/OutFlow; OR VPLS Id for VPLS ETS InFlow//OutFlow; output Interface for Ethernet
ETS InFlow/OutFlow;
• management of the received L2 control frames (tunneled or discarded) for the ETS InFlow L2
control frames, configured to be discarded at the ETS flow level will be classified as not
belonging to the ETS flow by the ETS classifier.
L2 control frames, configured to be either tunneled or selectively tunneled at the ETS flow level,
will be classified as belonging to the ETS flow only if they match all the other ETS classifier
criteria.
• Policing management for the ETS InFlow. It can be either color blind, IETF color-aware, MEF
color-aware without coupling flag, (for future releases) MEF color aware with coupling flag or
disabled. Default value for ETS Ethernet InFlow: color blind; default value for any (VPLS,
Provider Bridge, PW) InFlow: disabled;
• color profile association to the ETS InFlow. If this parameter is absent, a color profile with drop
precedence = “green” for any priority/dscp is associated by default to the ETS InFlow;
• VLAN pop enabling/disabling on the ETS InFlow. If this parameter is absent, pop operation is
disabled by default.
• VLAN push configuration on the ETS OutFlow.
• ETS Crossconnection setup.
10.4.4 Procedure
1
Select action:
To create, configure and activate an ETS InFlow/OutFlow with the Provider Bridge/PW/VPLS
ETS InFlow/OutFlow go to Step 2.
To retrieve ETS InFlow/OutFlow with the Provider Bridge/PW/VPLS ETS InFlow/OutFlow go to
Step 3.
To change an already created ETS InFlow go to Step 4.
To delete a ETS InFlow/OutFlow with the Provider Bridge/PW/VPLS ETS InFlow/OutFlow go to
Step 5.
2
Create, configure and activate an ETS InFlow/OutFlow and the Provider Bridge/PW/VPLS/ETS
ETS InFlow/OutFlow
To create, configure and activate an ETS InFlow/OutFlow and the Provider Bridge/PW/VPLS/
ETS ETS InFlow/OutFlow on which it is transported. Besides, the command below creates also
the cross-connection between them.
Enter pbflowbid activate flowuserlabel port {naming | lagnumber}
trafficdescriptor trafficdescriptoruserlabel
For details refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release
5.1 Command Line Interface Guide
3
Retrieve ETS InFlow/OutFlow with the Provider Bridge/PW/VPLS ETS InFlow/OutFlow
Enter:
pbflowbid show [flowuserlabel] [flowtype { pb | pw | vpls }]
To get the list of all defined ETS InFlow/OutFlow with the Provider Bridge/PW/VPLS ETS
InFlow/OutFlow on which they are transported.
4
To change an already created ETS InFlow
Enter:
pbflowbid config flowuserlabel [l2ctrlframe ctrlframe32bits {pass |
drop}] [trafficdescriptor trafficdescriptoruserlabel]
To change:
• whether the L2 control frames should be tunneled or discarded by an already created ETS
InFlow. Since transport network is based on Provider Bridge, the L2 control frames with MAC
DA equal to 01-80-C2-00-00-08 must be discarded, independent on user configuration.
• traffic descriptor association to the ETS InFlow. It carries information of CoS and traffic
descriptor parameters. Note that CoS of Traffic Descriptor cannot change.
5
Delete a ETS InFlow
Enter:
pbflowbid delete flowuserlabel
To delete an ETS InFlow/OutFlow and the Provider Bridge/VPLS/PW ETS InFlow/OutFlow on
which it is transported and corresponding cross-connections, see 10.4 “ Administer ETS to
Provider Bridge ETS/PW/VPLS bidirectional flow ” (p. 582)
END OF STEPS
10.5.2 Prerequisites
The 1850TSS shall be equipped with one or more DATA boards.
10.5.3 General
A ETS flow can be defined as a unidirectional traffic stream that shares a common forwarding and
QoS behavior on the transport network. The granularity of ETS flow definition depends on the
transport network and service details.
Enter
to retrieve
• the specified flow or all configured flows (if no flow optional parameter is not specified) or for all
10.5.4 Procedure
1
Select action:
To create, configure and activate a port to port configuration, go to Step 2
To retrieve the ETS InFlow/OutFlow couples list, go to Step 3
To delete a couple of ETS InFlow/OutFlow and the transparent connection between them, go to
Step 4.
2
To create, configure and activate a port to port configuration
Configuration concerns
• Classifier definition: default classifier is applied, i.e. don’t care of VLAN, PRI or DSCP values.
No other classifier can be added by user, see also 10.3 “ Administer Ethernet Flow
Classifier” (p. 580).
In “Port to Port Service” both creation and activation operations of default classifier criteria on
an Ethernet port are requested to be performed before activation of ETS Cross-connection;
• traffic descriptor association: BE NULL traffic descriptor is applied, see also 10.7 “Administer
Traffic Descriptor” (p. 589).
• management of the received L2 control frames: all control frames are tunneled, see also
10.13 “ L2 control frames management (in Provider Bridge)” (p. 600).
• Policy management: it is disabled.
• color profile association: default color profile (drop precedence= green for any priority) is
applied, see also 10.8 “Color Profile Management ” (p. 591).
• VLAN pop enabling/disabling: it is disabled.
• VLAN push configuration: it is disabled by default.
• ETS Crossconnection setup, see also 10.4 “ Administer ETS to Provider Bridge ETS/PW/
VPLS bidirectional flow ” (p. 582).
Enter portportbid activate flowuserlabel port1 naming port2 naming
For details refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release
5.1 Command Line Interface Guide
3
Retrieve the list of ETS InFlow/OutFlow couples that are transparently connected.
Enter:
portportbid show [flow_userlabel].
4
Delete a couple of ETS InFlow/OutFlow and their transparent connection
Enter:
pbflowbid delete flowuserlabel.
END OF STEPS
10.6.2 Prerequisites
The configuration of either dynamic or static routing is performed ONLY via TL1 command (see
5.2 “Administer T-MPLS Control Plane Global Parameters” (p. 110)) and is supposed to be
independent from:
• Administrative state of “In fiber In Band” Interface for management plane,
• Choice of either dynamic or static routing over “In fiber In Band” Interface for control plane.
10.6.3 General
• Raising/Clear of “In Fiber In-Band” Management Interface failure alarm due to underlying data-
link layer failures.
The management plane packets (IP packets), on each local/remote Ethernet port, can be routed in
3 different ways:
1. Static routing;
2. Through OSPF Routing;
3. Through Integrated IS-IS Routing.
10.6.4 Procedures
1
Select action.
To retrieve IF-IB information go to Step 4.
To create a IF-IB go to Step 2.
To delete IF-IB go to Step 3.
2
Create and activate IF-IB
Enter: infiberinband activate port {naming| lagnumber} [vlan vlan_id |
mnglabel mgmt_label] [ppp {enable | disable}] [routingprot
{static|isis}] [ratelimited dcn_ratelimited_value]
where
• vlan_id: an integer value in the set [0-4094], indicating the VID (or the lower bound of a VLAN
ID range)
• mgmt_label: Unsigned32 (0..4294967295) identifying MPLS Label for Management Plane
An example:
3
Delete IF-IB
This command allows to delete IF-IB management interface (either Ethernet or Link
Aggregation interface):
Enter: infiberinband delete port {naming | lagnumber}
where
• namingmust have rack, subrack, board≠0 and drawer=port=0; in commands that apply to a
port, the naming must have rack, subrack, board, port≠0;
4
Retrieve IF-IB
Enter: infiberinband show [port {naming | lagnumber}]
Note: If the optional parameter is absent, this command retrieves detailed information
about all configured DCN management interfaces (either Ethernet or Link Aggregation
interface). The user can retrieve detailed information of only a single DCN management
interface by providing its naming.
END OF STEPS
10.7.2 Prerequisites
The System shall support the Traffic Descriptor change (i.e. values of the corresponding IETF
Bandwidth Profile parameters PIR, CIR, PBS, CBS) associated to an incoming traffic flow.
This operation shall be hitless if it does not cause the change of traffic class:
• Regulated⇒ regulated;
• guaranted ⇒guaranteed;
• best effort ⇒best effort.
If the operation causes the Ethernet Traffic Descriptor type change, Input Ethernet Flow (input ETS)
is requested to be previously deactivated.
10.7.3 General
ETS QoS Management of incoming Ethernet traffic is requested to rely on the Association of a
Traffic Descriptor to an input ETS Flow or to a group of input ETS Flows according to Traffic
descriptor types and depending from specific ingress logical interface (ingress UNI, ingress IWI,
ingress Provider Bridge Virtual Interface):
NULL Traffic Descriptor binds an Enhanced Ethernet Forwarding Class (the same as associated to
Enhanced ETS traffic Descriptor) to an ETS Flow for PHB enforcement purposes, without any
enforcement in terms of both ETS Policing/Metering and ETS CAC Policies to be applied over that
ETS Flow.
NULL Traffic Descriptor is able to represent Input (Colored) PHB tightly coupled with input ETS
Flow, BOTH as input parameters for ETS cross-connections.
NE functions to handle (inside ETS Layer) outgoing Ethernet traffic are requested to take into
account:
• adopted Traffic Descriptor (either ETS Traffic Descriptor or NULL Traffic Descriptor);
• specific output logical interface (MPLS VC LSP, UNI/IWI, Provider Bridge Virtual interface) at
egress from ETS Layer.
For details, refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1
Command Line Interface Guide.
10.7.4 Procedure
1
Select action
To create, configure and activate a traffic descriptor go to Step 2
To retrieve traffic descriptor go to Step 3
To modify traffic descriptor go to Step 4
To delete a traffic descriptor go to Step 5.
2
Create, configure and activate an ETS traffic descriptor
Enter trafficdescriptor activate trafficdescriptoruserlabel traffictype
{bk| be | reg(4) | reg(3) | reg | reg(1)| gua(2) | gua | group} cir
cir_value {pir pir_value | eir eir_value} cbs cbs_value {pbs pbs_value
| ebs ebs_value} [admittedmcrate admitted _mc_rate] [admittedunknrate
admitted_unkn_rate] [trafficmctype {bk| be | reg(4) | reg(3) | reg |
reg(1)| gua(2) | gua | group}] [trafficunktype {bk| be | reg(4) |
reg(3) | reg | reg(1)| gua(2) | gua | group}]
It is possible specifying the parameters according to IETF (i.e. considering PIR and PBS) or
MEF (i.e. considering EIR and EBS).
SNMP parameters are set according to MEF definition, using the relations: PIR=CIR+EIR,
PBS=EBS.
3
Retrieve an ETS traffic descriptor
Enter trafficdescriptor show [trafficdescriptor_userlabel ] .
This command shows the following information for an ETS traffic descriptor:
• Traffic type
• Traffic parameters
• status
4
Delete an ETS traffic descriptor.
Enter trafficdescriptor delete trafficdescriptoruserlabel.
Where:
trafficdescriptor_userlabel is a value that can be retrieved see Step 3.
5
Configure an ETS traffic descriptor
Enter:
Note: SNMP parameters are set according to MEF definition via the relations:
PIR=CIR+EIR, PBS= EBS.
END OF STEPS
10.8.2 Prerequisites
The 1850TSS shall be equipped with one or more DATA boards.
10.8.3 General
The color-aware mode assumes that incoming ETS Traffic has been pre-colored (as green, yellow
or red). The behavior of the color-aware ETS policing algorithms implemented according to MEF
with or without the coupling flag.
10.8.4 Procedure
1
Select action:
To create, configure and activate a color profile go to Step 2
To delete a color profile go to Step 4.
To retrieve a color profile go to Step 3
2
Create, configure and activate a color profile
Enter colorprofile activate colorprofuserlabel {pri {allg | ally | allr
| priset [g | y | r] [.... priset [g | y | r]] } | dscp {default |
allg | ally | allr | dscpset [g | y | r][…. dscpset [g | y | r]] }}
where
• priset: the specified PRI values (up to 8 different priority values), associated to “green”(g)
by default) are set to any supported drop precedence values (green, yellow, red);
• dscpset: the specified DSCP values (up to 64 different DSCP values), associated to
green(g) by default) are set to any supported drop precedence values (green, yellow, red)
3
Retrieve a color profile
Enter
colorprofile show [colorprofuserlabel]
where:
If colorprofuserlabel is not specified the list of color profiles with their drop precedence
information is shown.
4
Delete a color profile
The Delete Color Profile Management Function is possible if no input ETS Flow is referring
Colour Profile Object to be deleted, see 10.4 “ Administer ETS to Provider Bridge ETS/PW/
VPLS bidirectional flow ” (p. 582)
Enter colorprofile delete colorprofuserlabel
where:
colorprofuserlabel can be retrieved, see Step 3
END OF STEPS
10.9.2 Prerequisites
The node should be equipped with one of the following boards:
• only optical GE (1000BaseX-FD)
• (from Rel.3.0 onward) Electrical GE interface.
10.9.3 General
The steps below explain how to to set the default MAU type for interface and retrieve its
information.
10.9.4 Procedure
1
Set the default interface MAU type
This operation can be performed only when the administrative status of supporting Ethernet
interface is down.
To verify Ethernet interface administrative status refer to 10.10 “ Ethernet Port management
(over MAU)” (p. 595)
Is the port administrative status is “up”?
If yes go to Step 2
If no, go to Step 3
2
Enter:
interface position namingsetlist localeth deactivate
where:
namingsetlist is one or more ports configured that should be deactivated.
3
If the port administrative status is down enter:
interface position namingsetlist localeth defaulttype {10 | 100 | 1000
}
where:
namingsetlist is one or more ports configured with TL1 configuration commands.
4
Retrieve general MAU information
Enter:
interface position namingsetlist localeth show mauinfo
where:
namingsetlist is one or more ports configured with TL1 configuration commands.
END OF STEPS
10.10.2 Prerequisites
10.10.3 General
Below the description of some of the Ethernet local port management operations:
• administratively enable/disable a Ethernet local port;
• port type configuration and its port maximum MTU/MRU configuration;
• Ethernet port information retrievement;
For details, refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1
Command Line Interface Guide.
10.10.4 Procedure
1
Select action:
Retrieve Ethernet local port information, go to Step 2
Activate/Deactivate Ethernet local port, go to Step 3
Configure Ethernet local port type, go to Step 4
Configure Ethernet local port maximum MTU/MRU, go to Step 5
Configure some Ethernet local port parameters using a single command, go to Step 6
2
Retrieve Ethernet local port information
Enter interface position namingsetlist localeth show ethinfo
where:
namingsetlist is one or more ports configured with TL1 configuration commands.
3
Activate/Deactivate Ethernet local port
Enter interface position namingsetlist localeth {activate | deactivate}
where:
namingsetlistis one or more ports (configured with TL1 configuration commands) on which
activation or deactivation should been down.
Activate is used to enable the Ethernet local port, i.e. sets the port adminstatus “UP”.
Deactivate is used to disable the Ethernet local port, i.e. sets the port adminstatus “DOWN”.
Go to Step 1.
4
Configure the port type
To configure the Ethernet local port type first deactivate the port administrative status, see Step
3.
The default Ethernet local port type is ETS.
Enterinterface position namingsetlist localeth portservice {ets |
bridge | mpls}
5
Configure Ethernet local port maximum MTU/MRU
Enter interface position namingsetlist localeth maxmtu mtuvalue
where:
namingsetlistis one or more ports (configured with TL1 configuration commands) on which
MTU/MRU should be changed.
6
Configure an Ethernet local port using a single command
Enter interface position namingsetlist localeth config [defaulttype {10
| 100 | 1000 }] [portservice {ets | bridge| mpls}][maxmtu mtuvalue]
[defaultflowcontrol {nopause | asympause | asym&sympause}]
see steps before to understand the command.
END OF STEPS
10.11.2 Prerequisites
10.11.3 General
Below the description of some of the Ethernet remote port management operations:
• administratively enable/disable a Ethernet remote port;
• port type configuration and its port maximum MTU/MRU configuration;
• Ethernet remote port information retrievement;
For details, refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1
Command Line Interface Guide.
10.11.4 Procedure
1
Select action:
Retrieve Ethernet remote port information, go to Step 2
Activate/Deactivate Ethernet remote port, go to Step 3
2
Retrieve Ethernet remote port information
Enter interface position namingsetlist remoteeth show ethinfo
where:
namingsetlist is one or more ports configured with TL1 configuration commands.
3
Activate/Deactivate Ethernet remote port
Enter interface position namingsetlist remoteeth {activate | deactivate}
where:
namingsetlistis one or more ports (configured with TL1 configuration commands) on which
activation or deactivation should been down.
Activate is used to enable the Ethernet remote port, i.e. sets the port adminstatus “UP”.
Deactivate is used to disable the Ethernet remote port, i.e. sets the port adminstatus
“DOWN”.
Go to Step 1.
4
Configure the port type
To configure the Ethernet remote port type first deactivate the port administrative status, see
Step 3.
The default Ethernet remote port type is ETS.
5
Configure Ethernet remote port maximum MTU/MRU
Enter interface position namingsetlist remoteeth maxmtu mtu_value
where:
namingsetlistis one or more ports (configured with TL1 configuration commands) on which
MTU/MRU should be changed.
6
Configure an Ethernet remote port using a single command
Enter interface position namingsetlist remoteeth config [portservice
{ets | bridge| mpls |iw }][maxmtu mtuvalue]
see steps before to understand the command.
END OF STEPS
10.12.2 Prerequisites
None.
10.12.3 General
Below the list of the configured interfaces information retrievable:
• the administrative status
• the interface type
• the Ethernet port client layer
• the traffic port enabling
• the operational status
• the line rate
• the traffic rate to which transmission is limited (only for remote ethernet port)
• the ingress port admitted flooding rate (i.e. the threshold value of received admitted bandwidth,
generating flooding traffic, on this ingress interface).
For details, refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1
Command Line Interface Guide.
10.12.4 Procedure
END OF STEPS
10.13.2 Prerequisites
Provider Bridge is installed and one or more data boards are configured. Before the L2 control
frames configuration the Administrative Status of all underlying local/remote ethernet interface is
requested to be “down”.
10.13.3 General
This Management function permits to configure the common behaviour Layer 2 Control frames (i.e.
whether to tunnel or discard) that applies to all the InFlows (with Ethernet as Service Type)
associated on a ETS interface (local Ethernet interface, remote Ethernet interface, LAG Interface).
By default all the Layer 2 Control frames with the exception of BOTH Pause and Slow Protocol
frames are tunnelled.
• Pause frames must always be discarded (or processed in the EFC block);
• Slow Protocol frames are requested to be discarded as default behaviour: it is up to operator to
enabled tunnelling of Slow Protocol frames, changing “on per port basis” default behaviour.
This change can be applied on any active ETS interface (e.g. an Ethernet/LAG interfaces
configured in promiscuous mode with an ETS client type) and forces an automatic change (in
charge of NE) on the actual layer 2 control frame disposition on all the active InFlows associated to
the ETS interface.
Incoming L2 control frames (received from NE incoming either (local/remote) Ethernet interface or
LAG Interface) are recognized by looking at their MAC Destination Address field. Customer L2
Control Protocols received on UNI/ETH-IWI can be either tunnelled or discarded according to the
service configuration. At Provider Bridge UNI for security reasons any received Provider BPDU
frame is always discarded from NE (there is not configuration option for this behaviour).
For details, refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1
Command Line Interface Guide.
10.13.4 Procedure
1
Select action:
Manage L2 control frames go to Step 3
Retrieve L2 control frames information go to Step 4.
2
Verify the port type is ETS and its administrative status is UP, see 10.10 “ Ethernet Port
management (over MAU)” (p. 595).
3
Manage L2 control frames
Enter interface position namingsetlistlagnumberset l2ctrlframe
ctrlframe32bits {pass | drop}.
where:
ctrlframe32bits identifies the control frame types for managing their passing through or
discarding
4
Retrieve L2 control frames information
To get the L2 control frames management (tunneled or discarded) associated to a certain
Ethernet port defined as ETS port.
Enter interface position namingsetlistlagnumberset show l2ctrlframe
This Management function retrieves the default behaviour for Layer 2 Control frames (i.e.
whether to tunnel or discard) that applies to all the InFlows (with Ethernet as Service Type)
associated on a ETS interface (local Ethernet interface, remote Ethernet interface, LAG
Interface).
END OF STEPS
10.14.2 Prerequisites
The 1850TSS320 shall be equipped with one or more DATA boards. Ports involved in a LAG can
belong to the same data board or can be allocated in different boards.
10.14.3 General
Link Aggregation feature allows to increase dynamically the available bandwidth of a “virtual”
Ethernet interface , called LAG (Link Aggregation Group), by adding or removing a set of one or
more physical ports , the “Aggregation Ports” (AP), of the same speed and configuration (MAU
setting) :
• Full duplex mode
• Speed : 1 or10Gbp, 10 or 100Mb/s speed are foreseen in future release.
• Auto-negotiation mode (enable/disable)
Aggregation port set and LAG Group are bind together by an unique identification parameter, called
“key”. Limit for the number of aggregated ports is set by LAG size (max size =16).
Two LAG’s interfacing each other as peer system are designated to be an “Aggregation System” :
local LAG is the “Actor” where the remote end represents the “Partner”. Each pair of ports
belonging to an Aggregation System is referred to be an “Aggregation Link”(AL).
Link Aggregation Control Plane layer is in charge to configure and manage Link Aggregation
function via a Slow Data Protocol (i.e. it has lower priority respect to RTSTP one), called LACP
(Link Aggregation Control Protocol). Messages are exchanged between peer through LAPDU
format packets
10.14.4 Procedure
1
Select action:
To create a Link aggregation group go to Step 2
To bind local Ethernet ports to a Link aggregation group go to Step 3
To modify a Link Aggregation group go to Step 4
To unbind a local Ethernet ports belonging to a Link aggregation group go to Step 5.
To remove a Link aggregation group go to Step 6.
2
Link Aggregation creation
Enter linkagg activate lagnumber adminkey adminkey_value [ets | bridge]
[size lagsize_value] [vlanprotprof vlanprotprof_userlabel]
[trafficstatus {enable | disable}] [asap asap_userlabel] [lagname
lag_userlabel] [neprio ne_pri] [hashingkey hash_mask_id] [lacp {enable
| disable}]
where:
Lagnumber is the LAG number that identifies the LAG (i.e. Lag100)
adminkey_value is “key” associated to the lag Lagnumber (i.e. Ports belonging to the same
LAG have the same key value)
If not specified in the command, the NE sets the optional parameter by default values (e.g.:
client type is set to ETS, LAG size is set to 8, ASAP, traffic status=“enabled”, enabled LACP, <
MAC Destination Address, MAC Source Address bit mask >).
When operator does not set the NE Priority, the value currently applied to other LAGs is used.
3
Bind local Ethernet ports to a LAG
Enter:
linkagg port naming_set_l ist bind lagnumber [pri port_lnkaggpri]
where:
Lagnumber is the LAG number that identifies the LAG (i.e. Lag100) it is set during the Lag
creation/activation command see STEP 2.
If port priority is not specified, it is set to the default value (0x80)
4
Modification LAG parameters
Enter:
linkagg config lagnumber [ets | bridge] [size lagsize_value]
[vlanprotprof vlanprotprof_userlabel] [trafficstatus {enable |
disable}] [floodinglimit floodinglimit_value] [asap asap_userlabel]
[lagname lag_userlabel] [adminstate {enable | disable}][hashingkey
hash_mask_id] [lacp {enable | disable}]
where:
Lagnumber is the LAG number that identifies the LAG (i.e. Lag100) it is set during the Lag
creation/activation command see STEP 2.
5
Unbind a local Ethernet port from a LAG
Enter:
linkagg port naming_set_list unbind
This operation changes the administrative port status to down.
6
Remove a LAG
Enter:
linkagg delete lagnumber_set
where:
lagnumber_set is a one or more lagnumber.
7
Retrieve LAG
Enter:
linkagg show [lagnumber_set]
To get the list of all configured link aggregation groups (user label and administrative key) with
the component LAG ports
END OF STEPS
10.15.2 Prerequisites
The 1850TSS should be equipped with one or more data boards.
10.15.3 General
This Management function permits to associate a VLAN Protocol Profile to an underlying (local/
remote) Ethernet interface: incoming Ethernet frames, received on that Ethernet interface and
matching that “per interface” VLAN Protocol Type, are handled as VLAN Tagged frame (QTagged,
PTagged or STagged). If no VLAN Protocol Profile is associated to this Ethernet interface, Default
VLAN Protocol Type (0x8100) is implicitly associated.
Briefly, the association between Vlan protocol Profile and port can be done in two different ways:
• create first the vlan profile and then create the association between the port and the vlan profile
(i.e. two CLI commands are used to perform this operation);
• or create and activate the association and vlan profile using a single CLI command.
For details, refer to 1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1
Command Line Interface Guide.
10.15.4 Procedure
1
Select action
To create a vlan protocol profile go to Step 2.
To delete vlan protocol profile go to Step 3.
To retrieve a vlan protocol profile information go to Step 4.
To associate ports to a Vlan profile go to Step 5
2
Create and activate VLAN protocol profile
Enter vlanprotprofile activate vlanprotprofuserlabel [type
ethertypevalue]
where:
vlanprotprofuserlabel is a mnemonic string to address the VLAN.
If EtherType is not specified, it is initiated with EtherType=0x8100
Vlan profile can be created during Vlan profile port association see Step 5
The ethertype is an hexadecimal value for the provider protocol-type (PT) that is inserted into
the 2 bytes field of the Stacked VLAN shim header; the value identifies the network provider
and has to be 2 bytes long in hexadecimal notation; the third non-included byte is forced by
default to “0x”.
The PT is used to recognize the type of different VLAN frames, i.e. if they are “SVlan tagged” or
others; by default, an hex value of 88A8 is interpreted as SVlan tagged.
Frames with PT value different than this will be treated as not SVlan tagged. An hex value of
8100 is interpreted as QVlan tagged. Other values of PT will be interpreted as generic Stacked
Vlan frames, used to interwork among different network providers
3
Delete VLAN protocol profile
Retrieve the Vlan profile name, go to Step 4
Enter vlanprotprofile delete vlanprotprofuserlabel
where
vlanprotprofuserlabel is a mnemonic string that addresses the VLAN.
4
Retrieve VLAN protocol profile
5
Associate a Vlan profile to an ETS port
• To create a Vlan profile and associate it to an ETS port enter:
interface position namingsetlistlagnumberset vlanprotprofile
activate vlanprotprofuserlabel [type ethertypevalue]
where:
vlanprotprofuserlabel is a mnemonic string to address the VLAN.
If ethertypevalue is not specified, it is initiated with EtherType=0x8100
• To associate a VLAN protocol profile to an Ethernet port configured as ETS port: incoming
Ethernet frames, received on that Ethernet interface and matching that VLAN EtherType, are
handled as VLAN Tagged frame (either QTagged or PTagged).
Enter:
interface position namingsetlistlagnumberset vlanprotprofile bind
vlanprotprofuserlabel
vlanprotprofuserlabel is a mnemonic string to address the VLAN
where:
• To associate the default VLAN protocol profile to an Ethernet port configured as ETS port.
Enter
END OF STEPS
10.16.2 Prerequistes
A Packet Card has to be created.
10.16.3 General
A VPLS Service is a provider service based on “L2VPN” logical model with multipoint connectivity
that makes it possible to interconnect several LAN segments over a VPLS Network (consisting of
fully meshed MPLS Core Pseudo-wires inside backbone MPLS network).
10.16.4 Procedures
1
Select action.
To retrieve VPLS instance information, go to Step 5.
To create VPLS instance, go to Step 2.
2
Create a VPLS Instance
This command creates a VPLS Instance. It specifies VPN Id (example 100:10), VPLS Instance
Egress Ports (Individual, Aggregated, PW).
Enter: vpls activate vplsuserlabel [portset namingsetlistlagnumberset ]
[pwset pwset]
An example:
vpls activate vp1 portset r1sr1sl12p8,lag33 pwset 5&7&16
3
Delete a VPLS Instance
This command deletes a VPLS Instance
Enter: vpls delete vplsuserlabel
4
Configure some VPLS Instance attributes
5
Retrieve a VPLS Instance information
This command gets a VPLS Instance entry information including the port role for each port
belonging to VPLS.
Enter: vpls show [vplsuserlabel]
6
Add elements to a VPLS Instance
This command adds both (either) UNI and (or) Core/Spoke MPLS PW’s to a created VPLS
Instance.
Enter: vpls add vplsuserlabel [portset namingsetlistlagnumberset] [pwset
pwset] [spokepwset pwset]
7
Remove elements to a VPLS Instance
This command removes both (either) UNI and (or) Core/Spoke MPLS PW’s from a created
VPLS Instance.
Enter: vpls remove vplsuserlabel [portset namingsetlistlagnumberset]
[pwset pwset] [spokepwset pwset]
END OF STEPS
A.1 Introduction
A.1.1
This Software Reference Guide provides supplementary information to be used with the
1850 Transport Service Switch (TSS-320, TSS-320H and TSS-160) Release 5.1 User Provisioning
Guide.
• A.2 “Access Identifiers” (p. 611) defines the access identfiers for equipment and facilities.
• A.3 “States” (p. 627) defines primary and secondary states for equipment and facilities.
• A.4 “Codes” (p. 629) lists all codes including condition types, errors, and equipment- and facility-
level default conditions.
• A.5 “Security” (p. 652)explains system security, which prevents unauthorized access to system
commands and determines each user's access level.
• A.6 “Performance Monitoring” (p. 656) lists PM parameters supported in the system, parameter
maximum values and threshold levels, and factory defaults for each parameter.
The general forms of the Input/Output (I/O) facilities are listed in the following requirements, where:
optional fields are enclosed in parentheses
• where: facility = the facility type
• where: bay# = the number of the bay within the system.
• where: shelf# = the number of the shelf within the specified bay.
• where: slot# = the number of the slot or position within the shelf in which either the PIM or the
facility is present.
VCG carrying SDH stream on L2 Aggregator cards with PIMMS are of the form:
• facility-bay#-shelf#-slot#-PIM#-(VCG#)-(VC4#)-(TU3#)-(TU12#)
− where: bay# = the number of the bay within the system.
− where: shelf# = the number of the shelf within the specified bay.
− where: slot# = the number of the slot or position within the shelf.
− where: PIM# = the PIM number within the slot,
− where VCG# = the VC group number on the L2 aggregator
− where VC4# = the VC4 facility number within the VC group.
− where TU3# = the TU3 facility number within the VC4.
− where TU12# = the TU12 facility number within the TU3.
VCGs and its PTFs for units without PIMMS are from:
• facility-bay#-shelf#-slot#-(VCG#)-(VC4#)-(TU3#)-(TU12#)
− where: bay# = the number of the bay within the system.
− where: shelf# = the number of the shelf within the specified bay.
− where: slot# = the number of the slot or position within the shelf.
− where VCG# = the VC group number on the L2 aggregator
− where VC4# = the VC4 facility number within the VC group.
− where TU3# = the TU3 facility number within the VC4.
− where TU12# = the TU12 facility number within the TU3.
− where: GBE# = the Gigabit Ethernet port number within the card (that's the same as the SFP
number).
Up to 8 of the 10 GBE ports can be provisioned at a given time (see CFG RRS for details).
The syntax for NE External Input Timing Port access identifiers in TL1 commands, responses, or
messages is:
• BITS-bay#-shelf#-port#
− where: bay# = the number of the bay within the system.
− where: shelf# = the number of the shelf within the specified bay.
− where: port# = the port number of the timing source: 0 = Port A on the TC, 1 = Port B on the
TC.
BITS AID is used for functions related to the NE external timing input port (signal source) on
the main shelf. (The main shelf would not have a TREFIN AID)
The syntax for External Timing Reference for the System Timing access identifiers in TL1
commands, responses, or messages is:
• EXTREF-bay#-shelf#-ref#
− where: bay# = the number of the bay within the system.
− where: shelf# = the number of the shelf within the specified bay.
− where: ref# = the number of the external timing reference: There are 2 external timing
references supported with the numbers 0,1.
The syntax for Line Timing Reference for the System Timing access identifiers in TL1 commands,
responses, or messages is:
• LINEREFSYS-bay#-shelf#-ref#
− where: bay# = the number of the bay within the system.
− where: shelf# = the number of the shelf within the specified bay.
− where: ref# = the number of the line timing reference: There are 6 line timing references
supported with the numbers 0,1,2,3,4,5.
The syntax for Line Timing Reference for the Output Timing access identifiers in TL1 commands,
responses, or messages is:
• LINEREFOUT-bay#-shelf#-ref#
− where: bay# = the number of the bay within the system.
− where: shelf# = the number of the shelf within the specified bay.
− where: ref# = the number of the line timing reference: There are 6 line timing references
supported with the numbers 0,1,2,3,4,5.
The syntax for NE Timing Node access identifiers in TL1 commands, responses, or messages is:
• SYNC-bay#-shelf#-ref#
− where: bay# = the number of the bay within the system.
− where: shelf# = the number of the shelf within the specified bay.
− where: ref# = 0, because there is only one timing node supported in the system, which will be
represented by this AID.
The syntax for equipment identifiers (i.e. equipment AIDs) in TL1 commands, responses, or
messages is:
• Equipment name-bay#-shelf#-slot#-(PIM#/SFP/XFP#)-(SFP/XFP#)
− where: equipment name = the circuit pack mnemonic/name
− where: bay# = the number of the bay within the system.
− where: shelf# = the number of the shelf within the specified bay.
− where: slot# = the number of the slot or position within the shelf in which the equipment is
present.
− where: PIM#/SFP/XFP# = the PIM number within the slot -or- the SFP number within the slot
-or- theXFP number within the slot. This is an optional parameter used only for pluggable
modules.
− where: SFP/XFP# = the SFP number within the PIM -or- the XFP number within the PIM. This
is an optional parameter used only for pluggable modules within PIM for L2 Aggregator
boards.
The syntax for ASAP (Alarm Severity Assigned Profile) identifiers in TL1 commands or responses
is:
• ASAP name-ASAP index#
− where: ASAP name = the ASAP type mnemonic/name
− where: ASAP index# = the number of the ASAP instance for that ASAP type.
ASAP indexes 0 and 1 are related to, respectively, the null and the factory default ASAP
instances, while the other indexes are assigned by the NE at the ASAP instances creation.
The syntax for THP (THreshold Profile) identifiers in TL1 commands or responses is:
• THP name-THP index#
− where: THP name = the THP type mnemonic/name
− where: THP index# = the number of the THP instance for that THP type
THP indexes 0 and 1 are related to, respectively, the null and the factory default THP
instances, while the other indexes are assigned by the NE at the THP instances creation.
The AID of the VC4 belonging to a logical VCG on a Multiservice Collector Card is:
• VCGVC4-{1-7}-{1-9}-{2-9,12-19}-{1-64}-{1-64} (VC4 within a logical VCG on a
Multiservice Packet Card)
The AID of the Lower Order VC3 belonging to a logical VCG a Multiservice Collector Card is:
• VCGLOVC3-{1-7}-{1-9}-{2-9,12-19}-{1-24}-{1-24} (LO VC3 within a logical VCG on
a Multiservice Packet Card)
The AID of the Lower Order VC12 belonging to a logical VCG a Multiservice Collector Card is:
• VCGLOVC12-{1-7}-{1-9}-{2-9,12-19}-{1-124}-{1-63} (LO VC12 within a logical VCG
on a Multiservice Packet Card)
The AID of the VCG on a GBE port on the 10XANY module is:
• GBEVCG-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10} (VCG on a GBE port on a 10xAny
module)
The AID of the VCG on a MAU port on the 10XANY module is:
• MAUVCG-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10} (VCG on a MAU port on a 10xAny
module)
The AID of the VC4 in a VCG on a GBE port on a 10xAny module is:
• VCGVC4-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-10}-{1-7} (VC4 within a VCG on a
10xAny module)
The following requirements refer to Ethernet facilities
The AID for the Shelf External Timing INPUT References is:
• BITS-{1-7}-{1-9}-{0,1} (Shelf External Timing Input Port)
The AID for the Shelf External Timing OUTPUT References is:
• BITSOUT-{1-7}-{1-9}-0 (Shelf External Timing Output Port)
The AID for the Timing Reference of a Shelf for an External Timing Input Port is:
• EXTREF-{1-7}-{1-9}-{0,1} (Timing Reference of a Shelf for an External Timing Input Port)
The AID for the Timing Reference of a Shelf for a Line Port selectable for System Timing is:
• LINEREFSYS-{1-7}-{1-9}-{0-5} (Timing Reference of a Shelf for a Line Port selectable for
System Timing)
The AID for the Timing Reference of a Shelf for a Line Port selectable for Output Timing is:
• LINEREFOUT-{1-7}-{1-9}-{0-5} (Timing Reference of a Shelf for a Line Port selectable for
Output Timing)
The port number of the SFP shall correspond to the port number of the optical facility or the optical/
electrical Ethernet port that it is feeding.
The AID for a MultiService Adaptation Card (Packet Module 10G) is:
• PP10AD-{1-7}-{1-9}-{2-9,12-19} (Adaptation Card Packet Modules 10G)
The AID for a Packet Module 10x1GbEthernet (Packet Module 10G) is:
• PP1GE-{1-7}-{1-9}-{2-9,12-19} (Packet Module 10x1Gb)
The AID for a Packet Module 1x10GbEthernet (Packet Module 10G) is:
• PP10GE-{1-7}-{1-9}-{2-9,12-19} (Packet Module 1x10Gb)
The AID for DWDM Optical Transponder with Colored XFPs is:
• DWLA10X-{1-7}-{1-9}-{2-9,12-19,21-36} (DWDM Optical Transponder)
The AID for a CWDM Optical Transponder (2.5G) without Optical Protection is:
• CWLA-{1-7}-{1-9}-{6-9,12-15} (CWDM Optical Transponder)
The AID for CWDM OADM 4ch w/o OSC coupler is:
• CADM-{1-7}-{1-9}-{6,7,8,9,12,13,14,15} (CWDM OADM)
The AID for a CWDM Mux/Demux 8ch w/o OSC coupler is:
• CMDX-{1-7}-{1-9}-{6-9,12-15} (CWDM MUX/DEMUX)
The AID for DWDM Mux/Demux 8 channels L1 band without S-band input/output is:
• OMDX8-{1-7}-{1-9}-{6-9,12-15} (DWDM MUX/DEMUX 8 channels)
The AID for a Virtual Transport for Local MPLS Interfac is:
• VT-{1-7}-{1-9}-{2-9, 12-19}-{1-10}-{1-4095} (Virtual Transport for Local MPLS
Interface)
The AID for a Virtual Transport for VCG MPLS Interface is:
• VT-{1-7}-{1-9}-{2-9, 12-19}-{1-128}-{1-4095} (Virtual Transport for VCG MPLS
Interface)
The AID for a User defined OAM Experimental Bit Profile is:
• OAMPHB-{2-8} (User defined OAM PHB Profile)
The generic AID of a traffic bearing equipment that is not yet provisioned is:
• MDL-{1-7}-{1-9} (Generic Shelf AID)
• MDL-{1-7}-{1-9}-{1-39} (Generic Module AID)
The AID of the manual area address for DCC purposes is:
• MAADDR-1 (Manual Area Address)
The AID of the Level 1 Routing that identifies a reachable Level 1 Intermediate System is:
• L1ROU (Level 1 Routing address)
The AID of the Level 2 Routing that identifies a reachable Level 2 Intermediate System is:
• L2ROU (Level 2 Routing address)
The generic AID used to address all entities in a particular command is:
• ALL (ALL AID)
The AIDs for representing the PM Global File collection at the local NE is:
• LOCPMGLB (Local NE PM Global file collection)
The AIDs for representing the PM Global File collection at the Remote File Server is:
• RFSPMGLB (Remote File Server PM Global file collection)
A.3 States
A.3.1
This section defines the Primary States (PSTs) and Secondary States (SSTs) used in the
1850 TSS-320, TSS-320H and TSS-160.
If an entity is out of service (OOS), the PST indicates whether the out-of-service condition is due to
an external management command (from an OS or user interface) or is caused by the system
because of an internal event, or both.
When provisioning an entity and specifying a PST value in a command, the PST name is shortened
to IS (in service) or OOS, but the full PST name (for example, OOS-AUMA) is used when provided
in output response messages.
A.4 Codes
A.4.1 Equipment Condition Type Codes
Refer to Table 37, “1850 TSS-320, TSS-320H and TSS-160 Equipment Condition Types” (p. 629)
for equipment and system condition type codes for the 1850 TSS-320, TSS-320H and TSS-160
configuration. The DESCRIPTION column identifies the relationship between equipment and
condition type. The EQUIPMENT column lists applicable equipment for each condition.
Table 37 1850 TSS-320, TSS-320H and TSS-160 Equipment Condition Types (continued)
Table 37 1850 TSS-320, TSS-320H and TSS-160 Equipment Condition Types (continued)
Table 37 1850 TSS-320, TSS-320H and TSS-160 Equipment Condition Types (continued)
Table 37 1850 TSS-320, TSS-320H and TSS-160 Equipment Condition Types (continued)
Table 38 1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition Type Codes
Table 38 1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition Type
Codes (continued)
Table 38 1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition Type
Codes (continued)
Table 38 1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition Type
Codes (continued)
Table 38 1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition Type
Codes (continued)
Table 38 1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition Type
Codes (continued)
Table 38 1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition Type
Codes (continued)
Table 38 1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition Type
Codes (continued)
Table 38 1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition Type
Codes (continued)
Table 38 1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition Type
Codes (continued)
Table 38 1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition Type
Codes (continued)
Table 38 1850 TSS-320, TSS-320H and TSS-160 Configuration Facility Condition Type
Codes (continued)
CODE DEFINITION
DMAF Dynamic Memory Allocation Failed
EANS Equipage, Access Not Supported
EATN Equipage, Not valid for Access Type
EFON Equipage, Feature Option Not provided
ENEQ Equipage, Not EQuipped
ENFE Equipage, FEature Not provided
ENPM Equipage, Not equipped for Performance Monitoring
ENRE Equipage, Not Recognized Equipage
ENRI Equipage, Not equipped for Retrieving specified Information
ENTL Equipage, Not Terminate and Leave
EQWT EQuipage, Wrong Type
ERLC Equipage, Red-Lined Circuit
CODE DEFINITION
ESPG Equipage, Software ProGram
IBEX Input, Block EXtra
IBMS Input, Block MiSsing
IBNC Input, Block Not Consistent
ICNV Input, Command Not Valid
IDMS Input, Data MiSsing
IDNC Input, Data Not Consistent,
IDNV Input, Data Not Valid,
IDRG Input, Data RanGe
IEAE Input, Entity Already Exists
IENE Input, Entity Does Not Exist
IIAC Input, Invalid ACcess identifier
IICT Input, Invalid Correlation Tag
IIDT Input, Invalid DaTa parameter
IIFM Input, Invalid data ForMat
IIPG Input, Invalid Parameter Grouping
IISP Input, Invalid Syntax or Punctuation
IITA Input, Invalid TArget identifier
INUP Input, Non-null Unimplemented Parameter
IPEX Input, Parameter EXtra
IPMS Input, Parameter MiSsing
IPNC Input, Parameter Not Consistent
IPNV Input, Parameter Not Valid
ISCH Input, Syntax invalid CHaracter (new Jul95)
ISPC Input, Syntax invalid PunCtuation
ITSN Input, invalid/inactive Test Session Number
MERR Multiple ERRors
PICC Privilege, Invalid Command Code
PIUI Privilege, Illegal User Identity
CODE DEFINITION
PLNA Privilege, Login Not Active
RABY Resource, All taps BusY
RCBY Resource, Circuit BusY
RCIN Resource, requested Circuit Id does Not exist
RENI Resource, Exceeded supported Number of profile Instances
RNBY Resource, Ne is BusY
RTBY Resource, requested Tap BusY
RTEN Resource, requested Tap does Not Exist
RTUB Resource, Test Unit Busy
SAAL Status, Already ALlowed
SAAS Status, Already ASsigned
SABT Status, ABorTed
SACS Status, Access unit Can't Sync on facility signal
SADC Status, Already DisConnected
SAIN Status, Already INhibited
SAIS Status, Already In Service
SAIU Status, All In Use
SAMS Status, Already in Maintenance State
SAOP Status, Already OPerated
SAOS Status, Already Out of Service
SAPR Status, Already in PRotection state
SAPV Status, Already ProVisioned
SARB Status, All Resources Busy
SARL Status, Already ReLeased
SATF Status, Automatic Test Failed
SAWS Status, Already in Working State
SCAT Status, Circuit Already connected to another Tap
SCSN Status, invalid Command SequeNce
SDAS Status, Diagnosis Already Started
CODE DEFINITION
SDBE Status, internal DataBase Error
SDFA Status, Duplex unit FAiled
SDLD Status, Duplex unit LockeD
SDNA Status, Duplex unit Not Available
SDNC Status, Data Not Consistent
SDNS Status, Diagnosis Not Started yet
SDNV Status, Data Not Valid
SEIS Supporting Equipment in Invalid State
SNCC Status, Not Cross-Connected
SNIS Status, Not In-Service
SNOS Status, Not currently Out of Service
SNPV Status, Not ProvVsioned
SNSR Status, No Switch Request outstanding
SNVS Status, Not in Valid State
SOSE Status, Operating System Error
SPFA Status, Protection unit FAiled
SPLD Status, Protection unit LockeD
SRAC Status, Requested Access Configuration is invalid
SRBY Status, Resource BusY
SRCI Status, Requested Command(s) Inhibited
SRCN Status Requested CoNdition already exists
SROF Status, Requested Operation Failed,
SRQN Status, iNvalid ReQuest
SRSD Status, Remote Session Dropped
SRTO Status, Reply Timeout Occurred
SSCE Status, Systemic Communication Error
SSRD Status, Switch Request Denied
SSRE Status, System Resources Exceeded
STTI STatus, Tap Idle
CODE DEFINITION
SWFA Status, Working unit FAiled
CODE DEFINITION
IBEX Input, Block EXtra
ICNV Input, Command Not Valid
IDNV Input, Data Not Valid
IDRG Input, Data RanGe
IIAC Input, Invalid ACcess identifier
IICT Input, Invalid Correlation Tag
IISP Input, Invalid Syntax or Punctuation
IITA Input, Invalid TArget identifier
IPEX Input, Parameter EXtra
IPMS Input, Parameter MiSsing
IPNV Input, Parameter Not Valid
PICC Privilege, Invalid Command Code
SARB Status, All Resources Busy
SDBE Status, internal DataBase Error
SROF Status, Requested Operation Failed
SSRE Status, System Resources Exceeded
A.5 Security
A.5.1
TL1 commands are used to control the 1850 TSS-320, TSS-320H and TSS-160 and to optimize its
operation and maintenance. Unauthorized use of these commands can degrade or completely
destroy the functionality of the system. Security is concerned with two major sources of
inappropriate use of system commands:
• Intruders who may maliciously take control of the system with the intent of damaging or disabling
the system
• Authorized users who use commands with which they are either unfamiliar or that are outside
their scope of responsibility
System security, when properly set up, effectively prevents unauthorized users from accessing
system commands, responses, and messages. This includes both preventing intruders from
accessing the system and restricting authorized users from using TL1 commands that are outside
their scope of responsibility.
The security scheme is based on setting up security values to restrict access to the system and its
resources. This section describes how the system administrator uses security measures to
proactively establish and maintain local security policies and practices.
All new systems are shipped with default security values. Before customizing the security scheme
by altering default values, the system administrator should read this section completely. Major
topics include the following:
• Controlling system access
• Controlling access to system resources
• Obtaining security audit information
The warning message is created and edited using the SET-ATTR-SECULOG command.
If the UID and PID are not acceptable, the system denies access. The response to a denied login
intentionally provides no additional information to the user. This prevents an intruder from
discovering the ACT-USER command syntax, then repeatedly attempting login until a valid UID and
corresponding PID is discovered.
The user-security database is limited to 512 users. New systems are shipped with the following pre-
existing users:
• admin
• breaker10
• breaker11
Password Aging
The system uses password aging to require users to change their passwords periodically. This
feature is enabled by setting the Password Aging Interval (PAGE) parameter of the SET-ATTR-
SECUDFLT command to a nonzero number. This system-wide parameter applies to all users. This
number specifies the number of days that a user's PID is aged before the system prompts the user
to change to a new password. The user must use the ED-PID command to enter a new PID before
the grace period ends and the number of extra logins during the grace period expires. The grace
period is determined by the PCND parameter and the number of extra logins is determined by the
PCNN parameter.
ED-PID:[TID]:UID:[CTAG]::OLDPID,NEWPID;
To prevent PID discovery through trial and error, PIDs must meet the requirements described in
“Entering New Users” (p. 653).
Automatic Logout
The system automatically logs out and disconnects inactive user sessions after a specified period
of inactivity. Inactivity is defined as lack of user input. The inactivity interval is provisionable per user
via the User Session Activity Link TimerOut parameter (TMOUT). The longest interval allowed is
999 minutes. A value of 0 disables automatic logout (no user session link time-out will occur).
Seven security levels are defined in the system, as following listed from lowest to highest priority:
• READ (Read only)—User may retrieve information about the system.
• DEBUG—User may initiate test procedures which are not service affecting and retrieve
information about the system.
• PROV (provisioning)—The user may perform non-destructive provisioning of I/O cards, ports
and interfaces, initiate test procedures which are not service affecting, and retrieve information
about the system.
• CONF (configure)—User may configure the system, performing provisioning and testing of all I/O
cards, ports, interfaces, and circuits.
Users may configure all subsystems which do not allow for system wide effect. The user may
perform nondestructive provisioning of I/O cards, ports and interfaces, initiate test procedures
which are not service affecting, and retrieve information about the system.
• NETADMIN (network administrator)—A network administrator may configure anything in the
system except user accounts.
• SEC (security administrator)—A user with the security privilege flag may create, delete, and
modify user accounts. A security user need not be a network administrator (but can create user
accounts with network administrator privilege). He/she is able to issue all commands. He/she is
not able to use debug and software development tools.
• NOTMOUT (no link timeout)—No inactivity timeout applied to the user.
Only the default user NOKIA has, beside all the security administrator privileges, the capability of
using debug and software development tools, for debug and maintenance purposes.
A user with security administrator privileges is able to disable and enable the NOKIA user, by
means of the TL1 command INH-USER-SECU and ALW-USERSECU.
The ENT-USER-SECU TL1 command supports the functionality of assigning security levels.
Command Privileges
The NE supports the ability for a user with sufficient Security Level privileges to change the
Command Security Level assigned to a specified external command. The ED-CMD-SECU TL1
command provides this functionality.
The security command access privilege level (CAP) of the following commands is SEC and it
cannot be changed by the ED-CMD-SECU command:
• Editing Command Privileges (ED-CMD-SECU)
• Entering a User (ENT-USER-SECU)
• Editing a User Security Parameters (ED-USER-SECU)
• Deleting a User (DLT-USER-SECU)
reports daily error accumulations and at 15-minute intervals. PM also compares the error counts
with user-defined thresholds and issues a REPT EVT (report event) message when any error count
crosses its defined threshold.
Each register marks accumulation data with an associated validity (VLDTY) flag. The system sets
the VLDTY flag to one of the following values:
• LONG—Data accumulated over longer time than the indicated time period
• PRTL—Partial, Data accumulated over some portion of the time period
• ADJ—Adjusted, data has been manually adjusted or initialized
• NA—Not available, data not available during entire accumulation period
• OFF—Data accumulation turned off for the entire time period
• COMPL—Complete, data accumulated during the entire accumulation period
The LONG validity flag is set if the time of day is changed and it results in the current data
collection period to be longer than the normal accumulation period by 10 seconds or more.
The PRTL validity flag is set if the PM data is collected only for part of the accumulation period due
to:
• Failure (lasting more than 10 seconds) of a module involved in PM collection
• Board initialization (via INIT-SYS) occurs without equipment protection during the accumulation
period
• PM collection is disabled for part of the accumulation period and some data is available
• The time of day is changed (via ED-DAT) and it results in the current data collection to be shorter
than the normal accumulation period by 10 seconds or more
The ADJ validity flag is set when PM data in the current register is manually initialized.
The NA validity flag is set if the corresponding PM data collection is prevented for the entire
accumulation period due to:
• Inability to fetch the PM data from the I/O module
• Board initialization (via INIT-SYS) occurs without equipment protection at or after the end of the
accumulation period
The OFF validity flag is set if PM collection is disabled for the entire collection period.
The COMPL validity flag is set under all other conditions. It indicates that data was accumulated
over the entire period.
The validity flag is not set as a result of register saturation.
The order of priority of the validity flags is OFF, NA, ADJ, PRTL, LONG, COMPL in descending
order.
RTRV-PM-rr can be used to automatically execute and display 15-minute and daily reports as
follows:
• Immediately or at a designated date and time
• At a single port, range of ports, or all ports
Parameters monitored by the system (MONTYPEs) vary according to facility and are referred in:
• Table 45, “GBE PM Parameters” (p. 659)
• Table 46, “OTU2 PM Parameters” (p. 660)
• Table 47, “ODU2 PM Parameters” (p. 660)
• Table 48, “10GBE PM Parameters” (p. 661)
• Table 49, “10GFC PM Parameters” (p. 661)
• Table 50, “STM-n (n = 1, 4, 16, 64) PM Parameters” (p. 661)
• Table 51, “VC4n (n = 4C, 16C, 64C) PM Parameters” (p. 662)
• Table 52, “LOVCn (n = 3, 12) PM Parameters” (p. 663)
• Table 53, “MAU PM Parameters” (p. 665)
For each facility type and MONTYPE there are default and maximum threshold levels. Refer to the
1850 TSS-320, TSS-320H and TSS-160 Commands and Messages manual (PN 3EM19286AA).
• Ethernet
EIFE Ethernet Incoming Frames with Errors
EINB Ethernet Incoming Number of Bytes
EINF Ethernet Incoming Number of Frames
EONB Ethernet Outgoing Number of Bytes
EONF Ethernet Outgoing Number of Frames
• Path Bidirectional
BBE-HOVC-EG Background Block Errors - Bidirectional Far End Higher
Order VC Path Egress
BBE-HOVC-FE Background Block Errors - Bidirectional Far End Higher
Order VC Far End
BBE-HOVC-IN Background Block Errors - Bidirectional Far End Higher
Order VC Path Ingress
BBE-HOVC-NE Background Block Errors - Bidirectional Far End Higher
Order VC Near End
ES-HOVC-EG Error Second - Bidirectional Far End Higher Order VC
Path Egress
ES-HOVC-FE Error Second - Bidirectional Far End Higher Order VC
Far End
ES-HOVC-IN Error Second - Bidirectional Far End Higher Order VC
Path Ingress
ES-HOVC-NE Error Second - Bidirectional Far End Higher Order VC
Near End
SES-HOVC-EG Severely Error Second - Bidirectional Far End Higher
Order VC Path Egress
SES-HOVC-FE Severely Error Second - Bidirectional Far End Higher
Order VC Far End
ES-HOVC-IN Severely Error Second - Bidirectional Far End Higher
Order VC Path Ingress
SES-HOVC-NE Severely Error Second - Bidirectional Far End Higher
Order VC Near End
UAS-HOVC-BI Unavailable Seconds - Bidirectional Far End Higher
Order VC Path
• Path Bidirectional
BBE-LOVC-EG Background Block Errors - Bidirectional Far End Lower
Order VC Path Egress
BBE-LOVC-FE Background Block Errors - Bidirectional Far End Lower
Order VC Far End
BBE-LOVC-IN Background Block Errors - Bidirectional Far End Lower
Order VC Path Ingress
BBE-LOVC-NE Background Block Errors - Bidirectional Far End Lower
Order VC Near End
ES-LOVC-EG Error Second - Bidirectional Far End Lower Order VC
Path Egress
ES-LOVC-FE Error Second - Bidirectional Far End Lower Order VC
Far End
ES-LOVC-IN Error Second - Bidirectional Far End Lower Order VC
Path Ingress
ES-LOVC-NE Error Second - Bidirectional Far End Lower Order VC
Near End
SES-LOVC-EG Severely Error Second - Bidirectional Far End Lower
Order VC Path Egress
SES-LOVC-FE Severely Error Second - Bidirectional Far End Lower
Order VC Far End
ES-LOVC-IN Severely Error Second - Bidirectional Far End Lower
Order VC Path Ingress
SES-LOVC-NE Severely Error Second - Bidirectional Far End Lower
Order VC Near End
B Equipment Entities
Executing an ENT-EQPT causes a primary state transition for the specified equipment entity, as
follows:
• If PST=IS to OOS-AU
• If PST=OOS to OOS-AUMA
It is mandatory to specify PROVISIONEDTYPE parameter when XFP/SFP is provisioned, to
distinguish XFP/SFP specific features (short/long/intraoffice haul, wavelength,...).
It is also possible to specify PROVISIONEDTYPE = ANY-<type>as generic value for SFP/XFP to
allow a generic MSA SFP/XFP to work without mismatch alarms. ANY-DATAS is the standard mode
of provisioning a DATA SFP; ANY-DATAX is the standard mode of provisioning a DATA XFP.
The command allows to configure with the SSBIT parameter the generated SS bit value in SONET/
SDH signals per card. Contained ports that do not generate a SONET/SDH signal ignore this
parameter.
It is mandatory to specify PROVISIONEDTYPE parameter when a Shelf is provisioned, to
distinguish its specific application (TDM/Data Switch, WDM Switch, WDM Amplifier...).
If a Shelf is entered, the mandatory cards will be autocreated and creation notifications are sent.
The auto-provisioning functionality, that is the automatic board provisioning after its plugging-in, is
activated or not according to the PROVMODE parameter value set with the SET-PRMTR-NE
command.
The creation of an IOC equipment should cause the creation of a set of supported (default)
facilities, according to the association table defined in the <Facility Auto-Creation Table document>.
The successful completion of the command shall cause REPT DBCHG autonomous messages.
In order for ENT-EQPT commands to be accepted by the node, the node's Main Shelf must be
provisioned.
Table 55 SFPs and the XFPs ProvisionedType allowed per IOC Card
Table 55 SFPs and the XFPs ProvisionedType allowed per IOC Card (continued)
Table 55 SFPs and the XFPs ProvisionedType allowed per IOC Card (continued)
Table 55 SFPs and the XFPs ProvisionedType allowed per IOC Card (continued)
Note: (*) MTSYNTH4 and its SFPs are in this Table only for reference: they really are
automatically provisioned at Drop Shelf Creation, and so not provisionable with ENT-EQPT
command
REQUIRED/
MODULE FUNCTION SIZE CARD SLOTS
OPTIONAL
S160 Shelf 1/0 NA
EC320 Equipment controller H 1/1 1- 20
MT160 Matrix (160G) DF 1/1 10 - 11
PSF320 Power Supply 2/0 37 - 39
FAN Fan Subsystem 2/0 40 - 41
TBUS160 ISPB Termination Bus 2/0 42 - 43
1P10GSO 1x10G Sysnc Optical H
4P2G5SO 4x2.5G Sysnc Optical H
8PSO 8x155/622M Sysnc Optical H
OTU-2 1xOTU-2 port slim H
10XANY 10XANY H 0/16 12 to 19 - 29 to 36
BOOST10G Booster +10dBm LC H
PRE10G Preamplifier 10Gb/s LC Ch. 34 H
DWLA10X Single Port 11G Pluggable OT H
OPS Optical Protection Switch H
LOA10G Lower Order adapter 10G H 0/3 33, 35, 36
PP1GE 1x10GE Packet module F 0/8
PP10GE 10x1GE Packet module F
12 to 19
Adaptation Card Packet
PP10AD F
Modules 10G
LOFA1111 Optical Amplifier 17 dBm F
0/4 12 to 15
OMDX8100 1x8 Mux/Demux H
See Figure 38, “1850 TSS-320 Shelf Slot Locations” (p. 690) for drawings of the 1850 TSS-160
shelf showing slot locations.
40 37 42-43 39
Fan Tray 1 (MAIN) 20 (SPARE)
19 36
18 35
17 34
16 33
15 32
14 31
13 30
12 29
11
41 10
Fan Tray
REQUIRED/
MODULE FUNCTION SIZE CARD SLOTS
OPTIONAL
S320 Shelf 1/0 NA
EC320 Equipment controller H 1/1 1- 20
MT320 Matrix (320G) DF 1/1 10 - 11
PSF320 Power Supply 2/0 37 - 39
FAN Fan Subsystem 2/0 40 - 41
TBUS320 ISPB Termination Bus 2/0 42 - 43
REQUIRED/
MODULE FUNCTION SIZE CARD SLOTS
OPTIONAL
1P10GSO 1x10G Sysnc Optical H
4P2G5SO 4x2.5G Sysnc Optical H
8PSO 8x155/622M Sysnc Optical H
OTU-2 1xOTU-2 port slim H
02 to 09 - 12 to 19
10XANY 10XANY H 0/32 - 21 to 28 - 29 to
36
OPS Optical Protection Switch H
DWLA10X Single port 11G pluggable OT H
BOOST10G Booster +10dBm LC H
PRE10G Preamplifier 10Gb/s LC Ch. 34 H
21, 22, 24, 33, 35,
LOA10G Lower Order adapter 10G H 0/6
36
PP1GE 1x10GE Packet module F
PP10GE 10x1GE Packet module F
0/16 02 to 09 - 12 to 19
Adaptation Card Packet
PP10AD F
Modules 10G
REQUIRED/
MODULE FUNCTION SIZE CARD SLOTS
OPTIONAL
CWLA3 Dual CWLA3 card N
CWLA3OP Dual CWLA3OP card N
CMDX8 2-fiber 8-channel MDX2 N
2-fiber 8-channel MDX2 w/
CMDX8S N
1310 filter
2-fiber 1 channel MDX w/
CMDX1S N
1310 filter
2-fiber 2-channel MDX w/
CMDX2S N
1310 filter
OADM 1 channel (1470
CADM1 N
to1610 nm)
OADM2 1 channel (1470 to 0/8 06 to 09 - 12 to 15
CADM1S N
1610 nm)
OADM 2-channel (1470 to
CADM2 N
1610 nm)
OADM2 2-channel (1470 to
CADM2S N
1610 nm)
OADM 4-channel (1470 to
CADM4 N
1610 nm)
CADM4S OADM 4-channel (1470 to N
1610 nm) w/ 1310 nm filter
OMDX8100 1x8 Mux/Demux F
LOFA1111 Optical Amplifier 17 dBm F
See Figure 38, “1850 TSS-320 Shelf Slot Locations” (p. 690) for drawings of the 1850 TSS-320
shelf showing slot locations.
40 Upper Fan
Tray
MAIN
37
1 2 3 4 5 6 7 8 9 12 13 14 15 16 17 18 19
10 11
38
SPARE
20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 39
41 Lower Fan
Tray
LINE Side
Unit
Q.ty & Type Allowed Type
PP1GE 10-SFP Colored: SS162C, SL162C
Any data: ANY-DATAS
Electrical: ETHEMR
PP10GE 1-XFP Colored: XL-642C
Any data: ANY-DATAX
LINE Side
Unit
Q.ty & Type Allowed Type
1P10GSO 1-XFP Black&White: XI-641, XI-642, XI-643, XI-645,
XS-641, XS-642, XS-643, XS-645, XL-641, XL-642,
XL-643, XV-642, XV-643
Colored: XL-642C
Any TDM: ANY-OM10G
4P2G5SO 4-SFP Black&White: SS-161AR, SI-161, SS-161, SS-162,
SL-161, SL-162
Colored: SS162C, SL162C
Any TDM: ANY-OM2G5
8PSO 8-SFP Black&White: SI-11, SS-11, SL-11, SL-12, SS-41,
SL-41, SL-42
Any TDM: ANY-OM155, ANY-OM622
10XANY 10-SFP Black&White: SI-11, SS-11, SL-11, SL-12, SS-41,
SL-41, SL-42, SS-161AR, SI-161, SS-161, SS-162,
SL-161, SL-162
Colored: SS162C, SL162C
Any TDM: ANY-OM155, ANY-OM622, ANY-OM2G5
Any data: ANY-DATAS
Any fiber channel ANYFC 10GB 10 x FC-2/FC-4
SI-FC4AR FC/2FC/4FC SN-I 850 nm port
SL-FC4AR FC/2FC/4FC LC-L 1310 nm port
Electrical: ETHEMR
OptFastEth: 100FXETH
OT2TDM 1-TUNABLE MSA Lambda Value
DWLA10X 1-XFP Colored: XL-642C
CWLA3(OP) 2-SFP Colored: SS162C, SL162C
CLIENT Side
Unit
Q.ty & Type Allowed Type
DWLA10X 1-XFP Black&White: XI-641, XI-642, XI-643, XI-645,
XS-641, XS-642, XS-643, XS-645, XL-641, XL-642,
XL-643, XV-642, XV-643
Colored: XL-642C
Any TDM: ANY-OM10G
Any data: ANY-DATAX (Only for CLNTSEL=
[]10GBE)
CWLA3(OP) 2-SFP Black&White: SS-161AR, SI-161, SS-161, SS-162,
SL-161, SL-162
Colored: SS162C, SL162C
Any TDM: ANY-OM2G5
B.3 AIDs
B.3.1
• BOOST-{1-7}-{1-9}-{2-9,12-19,21-36} (Booster)
• LOFA-{1-7}-{1-9}-{6-9,12-15} (Line Optical Filter and Attenuator)
• DWLA10X-{1-7}-{1-9}-{2-9,12-19,21-36} (DWDM Optical Transponder)
• CWLA-{1-7}-{1-9}-{6-9,12-15} (CWDM Optical Transponder)
• CADM-{1-7}-{1-9}-{6,7,8,9,12,13,14,15} (CWDM OADM)
• CMDX-{1-7}-{1-9}-{6-9,12-15} (CWDM MUX/DEMUX)
• OMDX8-{1-7}-{1-9}-{6-9,12-15} (DWDM MUX/DEMUX 8 channels)
• PP10AD-{1-7}-{1-9}-{2-9,12-19} (Adaptation Card Packet Modules 10G)
• PPUGW-{1-7}-{1-9}-{2-9,12-19} (Universal GateWay Card Packet Module 2e5G)
• PP1GE-{1-7}-{1-9}-{2-9,12-19} (Packet Module 10x1Gb)
• PP1GEX20-{1-7}-{1-9}-{2-9,12-19} (Packet Module 20x1Gb)
• PP10GE-{1-7}-{1-9}-{2-9,12-19} (Packet Module 1x10Gb)
• PP10GEX2-{1-7}-{1-9}-{2-9,12-19} (Packet Module 2x10Gb)
• SFP-{1-7}-{1-9}-{2-9,12-19}-{1-10} (SFP on PP10 modules)
• SFP-{1-7}-{1-9}-{2-9,12-19}-{1-20} (SFP on PP20x1 modules)
• XFP-{1-7}-{1-9}-{2-9,12-19}-1 (XFP on PP10GE modules)
• XFP-{1-7}-{1-9}-{2-9,12-19}-{1-2} (XFP on PP2x10GE modules)
• XFP-{1-7}-{1-9}-{2-9,12-19,21-36}-{1-2} (XFPs on DWLA10X Transponder)
• P42E1-{1-7}-{1-9}-{1-6} (1646DS 42XE1/T1 Card)
• SFP-{1-7}-{1-9}-{7}-{1} (1646DS 1XSTM1/STM4/STM16 Sub-module - Main position)
Glossary
Numerics
1+1
The 1+1 protection switching architecture protects against failures of the optical transmit/receive
equipment and their connecting fiber facility. One bidirectional interface (two fibers plus associated OLIUs
on each end) is designated "service," and the other is designated "protection." In each direction, identical
signals are transmitted on the service and protection lines ("dual-fed"). The receiving equipment monitors
the incoming service and protection lines independently, and selects traffic from one line (the "active"
line) based on performance criteria and technician/OS control. In 1+1 both service and protection lines
could be active at the same time (service in one direction, protection in the other).
A
AC
Alarm Cutoff
ACD
Access Control Domain
ACO
Alarm Cutoff and Test
ACT-
Activate command
Active
Active identifies a 1+1 protected line which is currently selected by the receiver at either end as the
payload carrying signal or a 1x1 or 1xN protected circuit pack that is currently carrying service. (See
Standby).
AID
Access Identifier
AIS
Alarm Indication Signal
AIS (Alarm Indication Signal)
A code transmitted downstream in a digital network that shows that an upstream failure has been
detected and alarmed.
ALW-
Allow command
ANSI
American National Standards Institute
APS
Automatic Protection Switch
ARP
Address Resolution Protocol
ASCII
American Standard Code for Information Interchange
ASCII (American Standard Code for Information Interchange)
A standard 8-bit code used for exchanging information among data processing systems and associated
equipment.
AUTO
Automatic
AUTO
One possible state of a service interface port. In this state, the port will automatically be put "in service" if
a good incoming signal is detected on the port.
Automatic Protection Switch
A feature that allows another synchronization source to be automatically selected and the
synchronization source provisioning to be automatically reconfigured in the event of a synchronization
source failure or network synchronization change, for example, a fiber cut.
Available Time
In performance monitoring, the 1-second intervals.
B
BER
Bit Error Ratio
BER (Bit Error Ratio)
The ratio of bits received in error to the total bits sent.
BIP
Bit Interleaved Parity
BIP (Bit Interleaved Parity)
A method of error monitoring over a specified number of bits, that is BIP-3 or BIP-8.
BITS
Building Integrated Timing Supply
BITS (Building Integrated Timing Supply)
A single clock that provides all the DS1 and DS0 synchronization references required by clocks in a
building.
BP
Backplane Error
BRI
Basic Rate Interface
Broadband
Any communications channel with greater bandwidth than a voice channel; sometimes used
synonomously with wideband. Also refers to signals at the DS3/E3 (44.736 Mb/s) and higher. Wideband
refers to lower rates (i.e. DS1, VT1.5, etc.).
CAC
Carrier Access Code
CANC-
Cancel command
CBS
Committed Burst Size
CC
Clear Channel
CCITT
International Telephone and Telegraph Consultative Committee
CCITT (International Telephone and Telegraph Consultative Committee)
An international advisory committee under United Nations' sponsorship that has composed and
recommended for adoption worldwide standards for international communications. Recently changed to
the International Telecommunications Union Telecommunications Standards Sector (ITU-TSS).
CCT
Cross-connection Type.
CIR
Committed Information Rate
CKTID
FROM and TO Circuit ID
CLI
Command Line Interface
CLK
Clock
CMISE
Common Management Information Service Element
CMOS
Complementary Metal Oxide Semiconductor
CNVT-
Convert command
CP
Control Plane
CR
Critical (alarm status)
CRS
Cross Connection
CV
Code Violations
CV (Coding Violation)
A performance monitoring parameter.
D
DB
Data Base
DCC
Data Communications Channel
DCC (Data Communications Channel)
The embedded overhead communications channel in the line. It is used for end-to-end communications
and maintenance. It carries alarm, control, and status information between network elements in a
network.
DCE
Data Communications Equipment
DCE (Data Communications Equipment)
In a data station, the equipment that provides the signal conversion and coding between the data
terminal equipment (DTE) and the line. The DCE may be separate equipment or an integral part of the
DTE or of intermediate equipment. A DCE may perform other functions usually performed at the network
end of the line.
Default Provisioning
The parameter values that are preprogrammed as shipped from the factory.
Demultiplexing
A process applied to a multiplexed signal for recovering signals combined within it and for restoring the
distinct individual channels of these signals.
DEMUX
Demultiplexer
Digital Multiplexer
Equipment that combines time-division multiplexing several digital signals into a single composite digital
signal.
DLP
Detailed Level Procedure
DLT-
Delete command
DRI
Dual Ring Interworking
DRI (Dual Ring Interworking)
Two ring networks interconnected at two common nodes.
E
ED-
Edit command
EEPROM
Electrically-Erasable Programmable Read-Only Memory
EIA
Electronic Industries Association
EMC
Electromagnetic Compatibility
EMI
Electromagnetic Interference
ENT-
Enter command
EOOF
Excessive Out of Frame
EPROM
Erasable Programmable Read-Only Memory
EQPT
Equipment
ERO
Explicit Route Object
ES
Errored Seconds
ES (Errored Seconds)
A performance monitoring parameter.
ESD
Electrostatic Discharge
ESF
Extended Super Frame
ESF (Extended Super Frame)
The format for a DS1 signal.
F
FCC
Federal Communications Commission
FE
Far End
FE (Far End)
Any other network element in a maintenance subnetwork other than the one the user is at or working on.
Also called remote.
FE ID
Far End Identification
FEBE
Far End Block Error
FEBE (Far End Block Error)
An indication returned to the near-end transmitting node that an errored block has been detected at the
far end.
FEPROM
Flash EPROM
FEPROM (Flash EPROM)
Nonvolatile Electrically-erasable Programmable Read-Only Memory.
FERF
Far End Receive Failure
FERF (Far End Receive Failure)
An indication returned to the transmitting terminal that the receiving terminal has detected an incoming
section failure.
FIT
Failures in 10-9 hours of operation.
Free Running
An operating condition of a clock in which its local oscillator is not locked to an internal synchronization
reference and is using no storage techniques to sustain its accuracy.
G
GBE
Gigabit Ethernet
GNE (Gateway Network Element)
A network element that has an active X.25 link. Can also be a DSNE.
GRE
Generic Routing Encapsulation
GUI
Graphical User Interface
H
HECI
Humans Equipment Catalog Item
Holdover
An operating condition of a network element in which its local oscillator is not locked to any
synchronization reference but is using storage techniques to maintain its accuracy with respect to the last
known frequency comparison with a synchronization reference.
I
I/O
Input/Output
IC (Internal Clock)
Used in synchronization messaging.
ID
Identifier
ID
See shelf ID and site ID.
IEC
International Electrotechnology Commission
IF-IB
In Fiber - In Band
IF-OOB
In Fiber - Out Of-Band
INH-
Inhibit command
INIT-
Initialize command
IP
Internet Protocol
IPIP
IP in IP encapsulation
IS
In Service
IS (In Service)
One possible state of a DS or DS3/E3 port. Other possible states are "auto" (automatic) and "nmon" (not
monitored).
ISCI
Intershelf control Interface
ISDN
Integrated Services Digital Network
ISI
Intershelf Interface
ISO
International Standards Organization
ISP
Internet Service Provider
J
Jitter
Timing jitter is defined as short-term variations of the significant instants of a digital signal from their ideal
positions in time.
L
L
Line parameters
LAN
Local Area Network
LAPD
Link Access Procedure "D"
LCAS
Link Capacity Adjustment Scheme
LED
Light-Emitting Diode
LED (Light Emitting Diode)
Used on a circuit pack faceplate to show failure (red) or service state. It is also used to show the alarm
and status condition of the system.
LER
Label Edge Router
Local
See Near-End.
LOF
Loss of Frame
LOF (Loss of Frame)
A failure to synchronize to an incoming signal.
LOP
Loss of Pointer
LOS
Loss of Signal
LOS (Loss of Signal)
The complete absence of an incoming signal.
LPBK
Loopback
LSR
Label Switching Router
M
MAC
MAC layer parameters to be monitored
MAU
Medium Access Unit
MD
Mediation Device
MJ
Major Alarm
MN
Minor Alarm
MON-
Monitor command
MPLS
Multi-Protocol Label Switching
MSSPRING
Multiplex Section Switching Protection Ring
MTBF
Mean Time Between Failures
Multiplexing
The process of combining several distinct digital signals into a single composite digital signal.
MUX
Multiplex
N
NE
Near End
NE
Network Element
NE (Near End)
The network element the user is at or working on. Also called local.
NE (Network Element)
The basic building block of a telecommunications equipment within a telecommunication network that
meets standards. Typical internal attributes of a network element include: onr or more high- and low-
speed transmission ports, built-in intelligence, synchronization and timing capability, and access
interfaces for use by technicians and/or operation systems. In addition, a network element may also
include a time slot interchanger.
NMON
Not Monitored (provisioning state)
NNI
Network-Network Interface
Node
A node is a line terminating element.
Non-Revertive
A protection switching mode in which, after a protection switch occurs, the equipment remains in its
current configuration after any failure conditions that caused a protection switch to occur clear or after
any external switch commands are reset. See Revertive.
NSA
Not Service Affecting
NSAP
Network Services Access Point
NSAP (Network Services Access Point)
An address that identifies a network element. Used for maintenance subnetwork communication using
the OSI protocol.
NTP
Network Time Protocol
O
O
Optical analog parameters
OAM&P
Operations, Administration, Maintenance, and Provisioning
OF-OOB
Out of Fiber -Out Of-Band
OLIU
Optical Line Interface Unit
OOF
Out of Frame
OPR-
Operate command
OS
Operations System
OS (Operations System)
A central computer-based system used to provide operations, administration, and maintenance functions.
OSI
Open Systems Interconnection
OSI (Open Systems Interconnection)
Referring to the OSI reference model, a logical structure for network operations standardized by the
Internation Standards Organization (ISO).
OSP
Outside Plant
OSPF
Open Shortest Path First
OTN
Optical Transport Node
P
P-bit
Performance Bit
Pass Through
Paths that are cross-connected directly across an intermediate node in a ring network.
PBS
Peak Burst Size
PC
Personal Computer
PCU
Power Conversion Unit
PID
Password Identifier
PINFET
Positive Intrinsic Negative Field Effect Transistor
PIR
Peak Information Rate
PJC
Pointer Justification Count
Plesiochronous Network
A network that contains multiple maintenance subnetworks, each internally synchronous and all
operating at the same nominal frequency, but whose timing may be slightly different at any particular
instant.
PLL
Phase-Locked Loop
PM
Performance Monitoring
PM (Performance Monitoring)
Measures the quality of service and identifies degrading or marginally operating systems (before an
alarm would be generated).
POH
Path Overhead
POP
Points of Presence
Port
The physical, electrical, or optical interface on a system.
PROT
Protection
Protection Line
The protection line is the pair of fibers (one transmit and one receive) that carry the APS channel (K1 and
K2 bytes in the line overhead).
PRS
Primary Reference Source
PST
Primary State
PSU
Power Supply Unit
PVC
Permanent Virtual Circuit
PW
Pseudo Wire
PWR
Power
PXC
Path Cross-Connection
R
RAM
Random Access Memory
RD-
Read command
Remote
See Far-End (FE).
RESTORE-
Restore command
Revertive
A protection switching mode in which, after a protection switch occurs, the equipment returns to the
nominal configuration (that is, the service equipment is active, and the protection equipment is standby)
after the clearing of any failure conditions that caused a protection switch to occur or after any external
switch commands are reset. See Non-Revertive.
Ring
A configuration of nodes comprised of network elements connected in a circular fashion. Under normal
conditions, each node is interconnected with its neighbor and includes capacity for transmission in either
direction between adjacent nodes. Path switched rings use a head-end bridge and tail-end switch. Line
switched rings actively reroute traffic over a protection line.
RLS-
Release command
RMV-
Remove command
RS232
Serial interface
RST-
Restore command
RSVP-TE
Resource ReserVation Protocol – Traffic Engineering
RT
Remote Terminal
RT (Remote Terminal)
An unstaffed equipment enclosure that may have a controlled or uncontrolled environment.
RTRV-
Retrieve command
S
S
Section parameters
SA
Service Affecting
SD
Signal Degrade
SDH
Synchronous Digital Hierarchy
SEFS
Severely Errored Frame Seconds
SEO
Single-Ended Operations
SES
Severely Errored Seconds
SES (Severely Errored Seconds)
This performance monitoring parameter is a second in which a signal fail occurs, or more than a preset
amount of coding violations (dependent on the type of signal) occurs.
SET-
Set command
SF
Super Frame
SF (Super Frame)
The format for DS1 signals.
SID
Site Identifier
SLA
Service Level Agreements
SNCP
SubNetwork Connection Protection
SPE
Synchronous Payload Envelope
SST
Secondary State
STA-
Start command
Standby
Standby identifies a 1+1 protected line which is not currently selected by the receiver at either end as the
payload carrying signal, or 1x1 or 1xN protected circuit pack that is not currently carrying service. See
Active.
Status
The indication of a short-term change in the system.
STM
Synchronous Transfer Mode
STP-
Stop command
SW-
Switch command
SWTCH
Switch
T-MPLS
Transport - Multi-Protocol Label Switching
TABS
Telemetry Asynchronous Byte Serial (Protocol)
TARP
Target ID Address Resolution Protocol
TCA
Threshold-Crossing Alert
TCA (Threshold Crossing Alert)
A condition set when a performance monitoring counter exceeds a user-selected threshold. A TCA does
not generate an alarm but is available on demand through the CIT and causes a message to be sent to
NMA via the TL1 interface.
TCP/IP
Transmission Control Protocol/Internet Protocol
TD
Traffic Descriptor
TDM
Time Division Multiplexing
TID
Target Identifier
TL1
Transaction Language 1
TL1 (Transaction Language 1)
A Telcordia Technologies machine-to-machine communications language that is a subset of ITU-TSS,
formerly CCITT's, human-machine language.
TLB
Timing Looped Back
TSA
Time Slot Assignment
TSI
Time Slot Interchange
TSO
Technical Support Organization
U
UAS
Unavailable Seconds
UAS (Unavailable Seconds)
In performance monitoring, the count of seconds in which a signal is declared failed or, in which, 10
consecutively severely errored seconds (SES) occurred, until the time when 10 consecutive non-SES
occur.
UID
User Identifier
UNI
User Network Interface
Unidirectional
A protection switching mode in which the system at each end of an optical span monitors both service
and protection lines and independently chooses the best signal (unless overridden by an equipment
failure or by an external request, such as a forced switch or lockout). In a system that uses unidirectional
line switching, both the service and protection lines may be active simultaneously, with one line carrying
traffic in one direction and other line carrying traffic in the other direction. For a 1+1 protection scheme
the K1 and K2 bytes in the line overhead are used to convey to the far end which line the near-end
receiver has chosen, so that an "active" indication may be made at the far end.
UPSR
Unidirectional Path Switched Ring
USB
Universal Serial Bus
V
VCG
Virtual Concatenation Group
VCn
Virtual Container of n order
VLAN
Virtual Local Area Network
VLSI
Very Large Scale Integration
VM
Violation Monitor
VoIP
Voice over Internet Protocol
VPN
Virtual Private Network
VT
Virtual Tributary
W
WAN
Wide Area Network
WDM
Wavelength Division Multiplexing
ZIC
Zero Installation Craft terminal
Index
A
administer
GBE loopback 183
GBE10 loopback 179
MAU loopback 195
STMn/OCn loopback 241
Autonegotation 577
I
In-Fiber/In-Band
IF-IB 587
L
LAG
Aggregation Ports 602
M
MAU 593